Proposal template

Announcements
1

1. Proposer Details

  • Proposer’s project name
  • Proposer’s email
  • Proposer’s X account (you will be required to make a post from the X account provided for verification purposes)
  • Best Telegram Handle for questions/fixes (remember to enable DMs from non-contacts)

The proposer should be affiliated with the protocol or at least one of the tokens in the contract.

2. Protocol Details

  • Your Protocol Name

  • Protocol Description

  • Protocol audits links

  • Protocol URL (link to dApp)

  • Protocol Logo URL (image must be 1024x1024 and non-transparent)

3. Reward Vault and Staking Token Details

  • Vault Name (Example: iBGT on Infrared)

  • Reward Vault Address: (insert only the contract address)

  • Logo URL: Vault Image 1024x1024 and non-transparent

  • Staking Token Address

  • Submit a Google Sheet link identifying addresses controlling more than 20% of the Staking Token supply. Template: https://docs.google.com/spreadsheets/d/1UBQpxLNfO0R1kWUWqsIKbilH3z2kphXGIr3GUelLZC8/edit?usp=sharing

  • Is the Staking Token located on BEX?

  • Specify the protocol where the Staking Token is located (Ex: BEX, Kodiak, YourOwnProtocol)

  • Link to where the Staking Token is located

  • Existing Liquidity / TVL (if it is a DEX pool the TVL should be at least $50K in a major ecosystem asset)

  • Describe how a user should acquire this staking token

  • Reward Duration address

This address will manage the Reward Vault duration, i.e. the number of days over which BGTs are distributed to stakers. Note that:

  • default duration is 7 days - i.e. BGTs are distributed over 7 days.
  • it can be adjusted within a range of 3 to 7 days.
  • changing the duration affects your vault’s APR.

4. Tokens Information

For each token in the pool/staking token, please provide

  • Name
  • Symbol
  • Token Contract Addresses (on Berachain and bridging addresses if cross-chain):
    chain / address

5. Incentive Tokens

Only up to three tokens can be whitelisted for use as incentives in a Reward Vault. Indicate which tokens will be used and provide all relevant information below.

Required Data for Incentive Tokens:

  • Name

  • Symbol

  • (if the name and symbol match one of the tokens already provided or a major token, skip the next steps)

  • Token Contract Addresses (on Berachain and bridging addresses if cross-chain):
    chain / address

  • Tokenomics, Distribution, and Vesting (links to official docs, website, etc.)

  • Identify any address(es) controlling more than 10%in un
    (address / type: team, foundation, investor, etc.)

  • Does the project issuing the token have any relationship with current Berachain validators?

  • If yes, which ones?

  • Total Supply Cap (if any)

  • Circulating Supply

  • Token Type:
    (Governance, Utility, Memecoin, Stablecoin, LST, Other)

  • If either token is a native stablecoin, LST, or governance token, provide extra details on Use case, Redemption mechanics, Peg stability

  • Are token contracts upgradable?

  • Token Control: (Multisig/Single Owner/RBAC/Permissionless/Governance)

  • Additional details on Token Control

  • Is the token contract verified?

  • Is the token a standard ERC20 or any functions have been customized? (e.g. transfer, balance, mint, burn…)
    (If custom, provide a link to an audit.)

  • Can the token be paused?

Additional Requirements:

  • Specify how many tokens per week you plan to allocate for incentives
  • Specify for how many weeks you plan to allocate incentives
  • Outline how decisions about token incentives are made (DAO, multi-sig, etc.).
  • Incentive Manager address (this address will manage the incentive token, being able to add incentive tokens to the reward vault and change the incentive rate)

6. Growth, Community & Ecosystem Impact

Why This Contract Matters:

  • How will this contract benefit Berachain?
  • Will it deepen liquidity for a major ecosystem token (e.g., BERA, core stable asset)?
  • Does it enable important trading pairs that drive adoption or integrate with other Berachain projects?

Potential Volume / TVL:

  • Provide metrics or estimates on liquidity you expect to attract.
  • Highlight any known liquidity commitments. (If you or partners plan to seed the contract, provide proof of funds or a statement of intent.)

Synergies with Other Protocols:

  • Will this contract feed into any yield aggregators, lending markets, or liquid staking derivatives on Berachain?

Marketing / Promotion:

  • Are there plans to co-market with another project to bootstrap liquidity?

Long-Term Vision:

  • How could this reward vault evolve over time? (E.g., eventually becoming a core liquidity pair or a major stable pool for the chain.)

7. Verification

Please post the following text with the provided X account:

“Submitted Reward Vault Request for [Contract Name] on protocol [Protocol Name] with incentive tokens [incentive token 1], [incentive token 2]”

Final Reminder

A successful RFRV hinges on demonstrating:

  1. Security: Low smart contract and token risk.
  2. Demand: Community and liquidity providers want this pair.
  3. Ecosystem Benefit: Increases volume, TVL, or strategic positioning for Berachain.

Make sure to cover these points clearly to maximize your chances of passing the governance vote / RFRV!