Background
BIP-812 Establishing the Balancer Alliance Program has officially passed on snapshot as of April 14, 2025. Given the elaborate structure of the initiative and need for external DAOs to participate on the Balancer forum to be included, the purpose of this post is to provide a template for Alliance proposals going forward. In doing so this will reduce ambiguity of expectations of partners, as well as provide clear evaluation criteria for the Balancer community as to if a partners proposal is worth approving. The template is not fixed our required to be utilized, it is meant only to guide potential Alliance members towards communicating their request and value add to the ecosystem transparently.
Proposal Template
[Project Name] Balancer Alliance Program Proposal
Team Safe Address: 0x9ff471F9f98F42E5151C7855fD1b5aa906b1AF7e will receive if any revenue share if this proposal is passed by the Balancer governance process.
Why [Project Name] Qualifies to be a Balancer Alliance Member
In this section presenting details regarding successful pool deployments on Balancer, inclusive of TVL milestones, revenue milestones, incentives spent on prior or ongoing initiatives, and any historic details of your DAO/teams use of Balancer should be included. Referencing data via dune or similar dashboards in encouraged.
Greater market details outside of Balancer such as total protocol size, competing DEX pool details, and why focusing on growing liquidity on Balancer is a top priority in your DEX expansion or consolidation strategy. Any relevant information such as targeting migration of TVL from Balancer V2 or any competing DEX to Balancer V3 is appreciated in this section.
Proposed Alliance Pool List and Incentive Structure
For specific partners with grandfathered pools please state specifically in this section to enable the revenue sharing for this pool with our without incentives. For reference qualified E1 pools must have earned >1M USD in protocol fees for Balancer per the relevant revenue dashboard.
Grandfather pools are limited to the following Balancer V2 deployments:
- Aave-wstETH
- wstETH-wETH
- rETH-wETH
- ezETH-wETH
- RDNT-wETH
For any E2, or not yet qualified pool, please include information similar to the below with any additional context as needed.
| Asset Pairing | Network | Pool Address | Incentive Token | Expected $/week | # of weeks |
|---|---|---|---|---|---|
| Token1/Token2 | Ethereum | 0x0000 | BAL | 2000 | 16 |
| Token3/Token4 | Arbitrum | 0x0001 | BAL | 750 | 20 |
| Token5/Token6 | Gnosis | 0x0002 | AURA | 1250 | 12 |
Cold Start Allocation
In this section, DAOs can request up to 10,000 USD in BAL tokens to kickstart their teams veBAL position.
Highlight or reiterate historic loyalty to your use of Balancer via the commitment to the DEX as a primary liquidity source, high revenue generation, or high incentive spend for your project.
Confirm your team is prepared to pair wETH from your treasury or balance sheet to pair with BAL when depositing into the veBAL system.
This section is not required and can be opted out of if desired.
Special Considerations
If there are any specific considerations for your proposal which stray from the Alliance framework, such as
- Leveraging different incentive strategies or core pool redirection requests
- Utilizing an EOA or unique contract for holding veBAL instead of a Safe
- Any other potential exception
Please describe it here for the community to provide feedback on.