StargateDAO Capital Allocation to Intent Based Systems

Introduction

The Stargate protocol has emerged as the most successful bridge in DeFi, processing over $5.5B a month at peak during 2025. Its success is largely attributed to its liquidity pool-based architecture and Hydra, together ensuring efficient and seamless cross-chain asset transfers.

However, the market has also indicated demand for alternative bridge architectures that prioritise speed over decentralisation. These models typically rely on centralised liquidity providers, faster execution mechanisms, and other trade-offs that sacrifice some aspects of decentralisation for faster settlement.

One of the biggest challenges intent-based solutions face is the cost and speed of rebalancing liquidity. Many protocols struggle with efficiently moving liquidity across chains while maintaining competitive costs for users. Some solutions involve paying LPs to rebalance manually, utilising centralised exchanges like Binance, or relying on third-party market makers.

Stargate could hold a unique advantage in this system due to its ability to rebalance liquidity at low cost through Stargate V2 (where fees are simply accrued back to the DAO). This built-in mechanism significantly reduces operational costs of rebalancing, enhancing profitability and making it a competitive solution for cross-chain liquidity movement. By extending its liquidity pool-based architecture with an intents-based system, Stargate can offer both capital-efficient transfer of size and fast, near-instant cross-chain swaps, positioning it as the default platform for bridging value across multiple chains.

Proposal

StargateDAO should allocate up to $20m of its treasury to intents-based bridging systems to capitalise on the abovementioned advantages. By leveraging Protocol Owned Liquidity, a Stargate funded solver can potentially offer larger size and better spreads. The solver will hold the relevant inventory based on market demand and opportunities to outperform the competitors. Stargate should integrate any funded system directly into its own front-end.

To maintain transparency, the Stargate Foundation will provide quarterly updates on the movement of this capital, including detailed reports on returns and performance.

Execution

StargateDAO would allocate $20m of inventory to intent-based systems. The inventory in the form of USDC, and ETH, will be withdrawn from Stargate’s pools (as per portfolio consolidation proposal).

The capital can be withdrawn back to the treasury at any point through a subsequent proposal.

3 Likes

Adopting an intent-based system for Stargate is definitely needed to stay competitive.

I have the following initial questions:

  1. Will the Solver operate under Stargate brand?

  2. Will the Solver be a third-party entity, not directly managed by the Stargate Foundation? If so, this adds a trust assumption for an external party, which raises concerns to me.

  3. Is it accurate to assume the Solver will prioritize transaction volume over profit, focusing on low fees?

  4. Will Stargate Bridge be the exclusive bridge for the Solver to rebalance liquidity? This should work under normal conditions with adequate liquidity in Stargate’s pools, but in cases of significant capital inflows to a specific chain, rebalancing could become expensive or infeasible.

  5. Withdrawing $20 million from the treasury to fund the Solver will diminish the capacity of Stargate’s liquidity pools to meet bridging demands. Additionally, we’ll require additional LP incentives, combined with minimal expected profit, raise questions about the necessity of this approach. Is additional funding necessary, particularly since some solvers are already leveraging Stargate for rebalancing?

  6. What is the estimated timeline for developing and implementing this intent-based system?

3 Likes
  1. How does this intents system position Stargate to capture market share from competitors like Across or LI.FI long-term? Will it drive net new bridge volume to scale network effects, or could it cannibalize existing pool usage?
  2. On Risks to Core Liquidity and Scaling: With $20M pulled from pools, how will the team mitigate reduced bridging capacity during high-demand periods? Could this hinder scaling the core bridge, and are there plans for additional LP incentives without diluting existing rewards?
  3. On Implementation Details and Timeline: What’s the roadmap for building/integrating this solver (e.g., tech stack, on-chain vs. off-chain components)? How long until it’s live in the frontend?
  4. On Trust, Decentralization, and Risks: If the solver is third-party or not fully managed by the Foundation, how will we ensure alignment with DAO interests (e.g., via smart contract audits or slashing mechanisms)?
2 Likes

A few questions:

  1. Could you share more details about the “Stargate-funded solver”? Is this a third party or an internal project worked on by Stargate?

  2. Can you please share the exact breakdown of how the $20m will be used? What are the operational costs involved, fees that the protocol will take, etc.

  3. What kind of risks do you anticipate and what kind of risk mitigation processes have you put in place for this?

Appreciate all the questions and comments guys. We’ll collect all the questions this week and answer all of them in a series of replies next week.

2 Likes

1. How will the DAO know if the intent-based system is actually working well?

Will there be clear metrics or updates showing how it’s performing — like returns, usage, speed, or risk? How do we track if this is better than just using the current system?


2. Which protocols will be chosen for this, and what does that process look like?

Will the community be able to suggest or vote on which intent-based solvers get integrated? And can teams from the ecosystem apply to be part of it?


3. Is this a one-time experiment or part of a bigger shift for Stargate?

Is this $20M move just to test the waters, or does it mean Stargate is moving more seriously into intent-based bridging long-term?

1 Like

The Stargate Foundation has collected the above questions and attempted to respond to all of them below. Please let us know if there are follow-ups or unanswered questions.

Q: Will the solver operate under the Stargate Brand

A: No it will not initially. The idea is to fund solvers that align closely with Stargate, and use Stargate for balancing where possible. But broadly capturing the opportunity available for a well-capitalised DAO like Stargate.

Q. Will the Solver be a third-party entity, not directly managed by the Stargate Foundation? If so, this adds a trust assumption for an external party, which raises concerns to me.

A: The solvers could be managed by a third party. The Stargate Foundation will conduct necessary on the teams, and legal agreements will be entered that protect the capital provided. The Foundation will facilitate this process.

Q. Is it accurate to assume the Solver will prioritize transaction volume over profit, focusing on low fees?

A: The Solver will prioritise serving the markets needs at competitive rates. Stargate V2 as a protocol serves users who are looking for low fees, and the idea with this proposal is to capture other areas of the market - e.g. sub-second speed, or swaps.

Q: Will Stargate Bridge be the exclusive bridge for the Solver to rebalance liquidity? This should work under normal conditions with adequate liquidity in Stargate’s pools, but in cases of significant capital inflows to a specific chain, rebalancing could become expensive or infeasible.

A: Yes. Stargate should be the exclusive bridge for rebalancing unless Stargate is not able to facilitate the rebalancing. When there are significant inflows, this would not be an issue as the rebalancing will be the opposite direction of where the inflows are occurring.

Q: Will withdrawing $20 million from the treasury to fund the Solver will diminish the capacity of Stargate’s liquidity pools to meet bridging demands.

A: This $20m will be a mix of assets from DAO wallets and liquidity pools. The protocol currently has ~$500m TVL and more than sufficient liquidity to ensure its pools are able to meet bridging demands and support Hydra. The success of Hydra has put the StargateDAO in a position to consider proposals like this.

The Stargate Foundation sees this as a fundamentally valuable expansion. Fees generated from a combined bridge and swap via solver execution are materially higher than those earned through Stargate’s current pool-based transfer model. Intents-based swaps also allow Stargate to serve a broader market and unlock a new revenue stream for the DAO. By owning the full intent-swap flow, the Stargate DAO can capture value across the entire transaction funnel, whereas in external solver systems that only use Stargate for rebalancing, the DAO captures just the rebalancing fees.

Q: Will additional LP incentives be required for Stargate’s liquidity pools.

A: No. Additional LP incentives will not be required for Stragate to divert funds to bootstrap the solver. As mentioned, there is more than sufficient liquidity to meet current bridging demands.

Q: Estimated timeline?

A: Late Q3.

Q: How does this intents system position Stargate to capture market share from competitors like Across or LI.FI long-term? Will it drive net new bridge volume to scale network effects, or could it cannibalize existing pool usage?

A: This intent system positions Stargate to compete directly with other intent-based solutions by expanding beyond Transfers to also offer Swaps. It enhances Stargate’s execution stack adding intents alongside OFTs, pool-based bridging, Hydra (canonical bridging and issuance), API access, and more, delivering a complete solution for token movement.

While some flow may shift from pool-based transfers, this would primarily reflect users prioritizing speed over cost. The DAO benefits from higher-margin intent flows, and the broader adoption of intents is expected to drive significant net-new volume and network effects, far outweighing any potential cannibalization

Q: Which kind of metrics will Stargate use to assess the $20Millions intent -based system’s performance in the quarterly reports ?

A: In quarterly treasury reports to the DAO, we’ll track the average basis points (bps) earned per transaction through the solver, compared to pool-based bridging, to assess performance. Additionally, yield generated from the $20M allocation will provide insight into the solver’s overall profitability.

Q: Can you please share the exact breakdown of how the $20m will be used? What are the operational costs involved, fees that the protocol will take, etc.

A: All $20m in assets will be used as inventory for the solver to facilitate intent-based swaps.

Q: What kind of risks do you anticipate and what kind of risk mitigation processes have you put in place for this?

A: Some risks include the solver funded by Stargate not working as well as it is intended to, resulting in the potential of opportunity cost to the DAO. The Foundation will carry out extensive due diligence, as well as enter any necessary legal agreements to protect the DAO when/where possible.

Another potential risk vector involves vulnerabilities in the smart contract. To mitigate this, the Foundation will conduct thorough audits, if needed, to ensure the security and integrity of the solver’s inventory.

Q: Will the community be able to suggest or vote on which intent-based solvers get integrated? And can teams from the ecosystem apply to be part of it?

A: Absolutely - this proposal is just opening up the DAO to using capital in this manner. Token holders are the ultimate decider, and this will hopefully result in fruitful relationships for the StargateDAO.

Q: Is this $20M move just to test the waters, or does it mean Stargate is moving more seriously into intent-based bridging long-term?

A: It is not the intention of this proposal to deploy the full amount of capital in one go, rather to set up the ability for the DAO to get more seriously involved into capital provision and earning on the DAO treasury.

2 Likes

I suggest that the first thing should be speed, not the number of ecosystems. The second is the rate. A low rate will attract a large number of users. The third is the problem feedback mechanism. There should be bridge communication and response communication tools.

vote https://snapshot.box/#/s:stgdao.eth/proposal/0xcb6cf828878e7286a146543790de8e836320b1f651661855e7fe60f79d8ec328