[TEMP CHECK] — Opening BIM to the Stellar Ecosystem

Proposals
, ,
1

Author: @LP17 – @BIMLabs
Date: [20/04/2026]

Summary of the Proposal

This TEMP CHECK aims to gather community sentiment on opening the BIM ecosystem to the Stellar ecosystem through the integration of key Stellar-native infrastructure and DeFi protocols into BIM Exchange.

The proposal includes:

  • Integration of Stellar Wallets Kit to support Stellar wallets inside the BIM environment

  • Integration of Soroswap, a Stellar-native DEX / aggregator layer for token swaps and liquidity routing

  • Integration of DeFindex, a Stellar-based yield infrastructure for wallets and DeFi applications

  • Opening XLM buy and sell flows through BIM’s own solutions and third-party fiat providers

  • Enabling bridging toward the Stellar ecosystem, including access to XLM and Stellar USDC

  • Confirming that, thanks to a Stellar grant awarded to BIM, BIM should not require DAO budget support for team operations during 2026, except in a force majeure scenario

If community feedback is positive, a formal BIP will be submitted for Snapshot vote.

Context

BIM has been awarded a grant from the Stellar ecosystem.
The exact amount will be communicated later, at the discretion of the recipient and in accordance with Stellar grant communication and disclosure constraints as currently applicable.

This grant creates an opportunity not only to support BIM’s operations, but also to expand BIM strategically toward an ecosystem with strong adoption in regions where BIM aims to grow, especially:

  • Africa

  • Latin America

Stellar is widely used for payments, transfers, and accessible financial applications, making it a relevant ecosystem for BIM’s expansion strategy.

In this context, the proposal is to open BIM Exchange to the Stellar ecosystem by integrating three core components from the Stellar stack:

  1. Stellar Wallets Kit — a wallet connection library designed to support Stellar wallets through a single integration layer

  2. Soroswap — positioned as the first DEX aggregator on Stellar and also documented as a Soroban-based AMM and aggregation layer for trading and liquidity access

  3. DeFindex — plug-and-play yield infrastructure for Stellar wallets and DeFi apps, including automated stablecoin vault tooling and a revenue-sharing model

Proposal Details

:one: Stellar Wallet Integration

BIM would integrate Stellar Wallets Kit as the wallet connectivity layer for the Stellar ecosystem.

This would allow BIM to support Stellar wallets through one unified library, simplifying the user experience and reducing integration complexity.

Objective:
Enable BIM users to connect Stellar-compatible wallets directly within the BIM environment.

:two: Soroswap Integration

BIM would integrate Soroswap as the first major Stellar-native DeFi trading layer within the platform.

Soroswap provides swap and liquidity routing infrastructure on Stellar / Soroban and is documented as both a DEX and an aggregation layer.

Potential outcomes:

  • Access to Stellar-native swaps

  • Better routing for Stellar ecosystem liquidity

  • Stronger interoperability between BIM and Soroban-based DeFi

:three: DeFindex Integration

BIM would integrate DeFindex as a yield layer for Stellar-based stablecoin and DeFi strategies.

DeFindex positions itself as yield infrastructure for Stellar wallets and DeFi apps, with automated vault SDKs and partner revenue-sharing features.

Objective:
Expand BIM’s product scope beyond pure trading by adding access to Stellar-native yield infrastructure.

:four: XLM Buy / Sell Enablement

BIM would open support for buying and selling XLM through:

  • BIM’s own exchange flows

  • Existing and future third-party providers

This would make Stellar assets directly accessible through BIM and improve BIM’s relevance for users in markets where Stellar is already widely used.

:five: Bridge Access Toward Stellar

The proposal also includes opening bridge functionality toward the Stellar ecosystem so users may bridge assets into:

  • XLM

  • USDC on Stellar

The current expectation is that this bridge component may be connected through infrastructure associated with the Stellar grant ecosystem, potentially including Soroswap-related infrastructure, although the final implementation path may still evolve before deployment.

Treasury & DAO Budget Impact

A key point of this TEMP CHECK is that the Stellar grant is expected to support BIM operations for the full year 2026.

As a result, the team states that no DAO budget request should be needed during 2026, except in the event of force majeure.

This means:

  • Team operational runway is expected to be secured through end of 2026

  • DAO treasury pressure should be significantly reduced

  • Ecosystem expansion can proceed without an additional governance budget burden during that period

Strategic Rationale

This proposal strengthens BIM’s positioning as:

  • A multi-ecosystem exchange

  • A protocol expanding beyond EVM-only infrastructure

  • A gateway to regions where Stellar already has strong adoption

  • A more capital-efficient DAO, thanks to external ecosystem funding

It supports:

  • Expansion into Africa and Latin America

  • Access to a new user base

  • Support for XLM and Stellar-native assets

  • Wallet, DeFi, swap, and yield functionality within one broader ecosystem strategy

  • Reduced dependence on DAO treasury spending for 2026

Risks & Considerations

  • Dependency on third-party Stellar-native infrastructure

  • Technical complexity of non-EVM ecosystem integration

  • UX complexity when adding new wallet and bridge flows

  • Final bridge implementation partner may change before deployment

  • Grant communication constraints limit what can be disclosed publicly at this stage

A technical validation and implementation review would be required before activation.

Question to the Community

:backhand_index_pointing_right: Are you in favor of opening BIM Exchange to the Stellar ecosystem through the integration of Stellar wallet infrastructure, Soroswap, DeFindex, XLM buy/sell support, and bridge access to Stellar assets, while acknowledging that the Stellar grant should cover BIM team operations through 2026 without requiring DAO budget support except in a force majeure situation?

Next Steps

If community sentiment is positive:

  • A formal BIP will be drafted

  • Technical scope and rollout phases will be finalized

  • The final Stellar bridge implementation partner will be confirmed before deployment

Discussion

Please share your feedback, questions, concerns, or suggestions below so the proposal can be refined before moving to a formal DAO vote.

2 Likes
2

This is a well-aligned expansion, but it’s not automatically a net positive unless execution is disciplined. Here’s a structured take:

  1. Strategic Fit — Strong but Intent Matters
    Opening BIM to the Stellar ecosystem makes sense if the goal is true multi-ecosystem liquidity, not just adding another chain.
    Stellar’s strength isn’t DeFi dominance, it’s payments, remittances, and real-world usage, especially in Africa and LATAM. That aligns with BIM’s positioning as an accessibility-focused exchange layer.
    The key question:
    Is BIM integrating Stellar to deepen utility, or just to expand surface area?
    If it’s the former, this is a high-signal move.
  2. Infrastructure Stack — but Interdependent
    The combination of:
    Stellar Wallets Kit (access layer)
    Soroswap (liquidity + routing)
    DeFindex (yield layer)
    …creates a full vertical stack (wallet → trade → earn).
    That’s powerful in theory, but introduces stack dependency risk:
    If Soroswap liquidity is thin → routing quality suffers
    If DeFindex yields aren’t competitive → idle capital leaves
    If wallet UX is fragmented → onboarding friction increases
    This isn’t just integration, it’s reliance on an emerging ecosystem stack.
  3. Liquidity Reality — The Make-or-Break Factor
    The success of this integration will depend less on tech and more on:
    Depth and reliability of Stellar-native liquidity
    Without sufficient liquidity:
    Aggregation becomes inefficient
    Slippage increases
    BIM loses its execution advantage
    It would be useful to clarify:
    Expected liquidity sources (organic vs incentivized)
    Whether BIM will bootstrap liquidity or rely fully on partners
  4. Bridge Design — Critical Risk Surface
    Bridging is where most failures in DeFi occur.
    The proposal leaves flexibility on the bridge provider, which is understandable but also introduces uncertainty.
    Key considerations:
    Is this a canonical bridge, liquidity network, or synthetic representation?
    What are the security assumptions?
    How is finality and settlement risk handled between EVM ↔ Stellar?
    This part deserves deeper technical transparency before a BIP.
  5. UX Complexity — Underrated Challenge
    Supporting:
    New wallet standards
    Non-EVM flows
    Bridging + swaps + yield
    …can easily fragment the user experience.
    If not abstracted properly, users will face:
    More decisions
    More steps
    More failure points
    The win condition:
    Stellar integration should feel invisible, not additive.
  6. Treasury Impact — Clear Positive (with a Caveat)
    The grant covering operations through 2026 is a strong advantage:
    Reduces DAO sell pressure
    Extends runway
    Allows focus on product vs fundraising
    However:
    Lack of disclosed grant size introduces uncertainty
    “Force majeure” clause should be better defined to avoid governance ambiguity
    Still, this is net positive for capital efficiency.
  7. Expansion Thesis — but Execution-Dependent
    Targeting Africa and LATAM via Stellar is logical given:
    Existing payment rails
    Familiarity with XLM-based transfers
    Lower barrier to entry vs EVM
    But expansion won’t come from integration alone:
    Distribution, partnerships, and local onboarding matter more than infrastructure.
    Final Position
    Support with conditions.
    This is a strategically sound proposal, but its success hinges on:
    Proven liquidity depth
    Secure and well-defined bridge architecture
    Clean UX abstraction
    Reduced dependency risk across the Stellar stack
    Suggested Additions Before BIP breakdown of bridge design and security model
    Expected liquidity metrics or partner commitments
    UX flow previews or simplification strategy
    Clearer definition of grant scope boundaries
    If executed well, this could position BIM as a true cross-ecosystem liquidity hub rather than just another multi-chain interface.
    If executed poorly, it risks becoming overextended across weak integrations.
    The direction is right, the details will decide everything.
2 Likes
3

This is a strong strategic move for BIM.

Expanding into Stellar opens access to real adoption in regions like Africa and Latin America, while integrations like Soroswap and DeFindex add trading depth and yield opportunities.

The biggest advantage is the Stellar grant covering 2026 operations, reducing pressure on the DAO treasury.

There are some risks (technical complexity, UX, third-party reliance), but they’re manageable with proper execution.

My position: In favor.

2 Likes
4

Thank you for your support

5

Excellent news and amazing opportunity for BIM Exchange growth!!! Let’s integrate Stellar ecosystem :ok_hand:t3:

1 Like
6

I’m in support of this.

Opening BIM to Stellar makes sense for growth and liquidity, and access to Soroswap, DeFindex is a good add. The grant covering ops till 2026 is also a big win.

But I need some clarity here​:backhand_index_pointing_down:

>Who’s the bridge partner and how secure is it?

>Are we rolling this out in phases?

>Hw are user funds protected during bridging?

7

Who’s the bridge partner and how secure is it?
The final bridge partner is not locked in yet. It will be confirmed before deployment. Security is a key condition here: BIM will only activate bridging after a full technical validation of the selected infrastructure.

Are we rolling this out in phases?
Yes, absolutely. The rollout will happen step by step, protocol by protocol, so each integration can be tested, validated, and improved before expanding the scope.

How are user funds protected during bridging?
By keeping the rollout progressive and limiting exposure at launch. Bridging will only be enabled once the infrastructure is validated, with a controlled initial scope and strong technical review to reduce protocol and execution risk.

8

BIP052 : Snapshot