Below are the distribution guidelines for eligible teams/individuals in Berachain’s Request for Broposal (RFB) program. 

Teams are expected to keep records on how their BERA was deployed, as well as the impact of those deployments toward project product-market-fit in the ecosystem. Submission of these records will be a requirement for participation of RFB teams in any future Berachain programs. 

Teams that are most successful and thoughtful in their integration of Proof of Liquidity and their broader plans for distribution of their BERA allocations will be viewed more favorably in their eligibility for future Berachain incentive programs. Failure to adhere to these guidelines will result in immediate termination of support from the Berachain Foundation and blacklisting from participation in future planned programs.

RFA (1.69% of Total Supply)

Teams that qualified for RFA are expected to use their allocations across two categories: 

• Mainnet Allocation, to help acquire users, drive growth, and find product-market fit for new deployments on Berachain (70+% of Total RFB allocation, which includes Testnet Users already distributed).. 
• Team/Treasury Allocation, to fund new product development, sustain team salaries, and cover operational costs for applications (10-15% of Total RFB allocation, which includes Testnet Users already distributed).

There are also a few high-level guidelines that teams are expected to adhere to for distribution: 

1. Teams may not use their mainnet allocation for Pool2 rewards - e.g. using BERA to incentivize pools with native governance tokens. 

• The only exception is for Pool2 with rewards vaults via Proof of Liquidity that have been approved by governance. In this instance, BERA can be used to incentivize the rewards vault, but no more than 5% of mainnet allocation can be used for this purpose. 

2. Teams should focus on using their BERA to incentivize rewards vaults on liquidity pools through Proof of Liquidity. While not doing so, but following other guidelines, isn’t a breach of the guidelines, teams that are most effective in following this guideline will receive a weighting boost for subsequent Berachain programs.
3. Teams should distribute tokens over the bootstrapping phase and lifecycle of their project (expected 6+ months). Failure to do so, or meaningfully accelerating the distribution timeline (ie. in a single month), will result in said team being blacklisted from future Berachain token programs. 

The Testnet portion (0.31% of total supply) was set on Genesis (has been in users’ wallets since launch), and is not included in the 1.69% above. 

RFC (0.35% of Total Supply)

Individual contributors that qualified for RFC via social, educational, or community contributions are able to use their BERA allocations to continue the work they have done to date and continue growing their communities. This should ideally be targeted toward usage and discovery of new applications & products in the Berachain ecosystem, with a focus on education and new content creation. 

Teams that qualified for RFC via social, education, or community contributions are expected to use funds for the purpose stated in the application (growth of the existing community) - failure to do so will result in termination & blacklisting.