RFRV: BREAD/OHM Kodiak Island

Reward Vaults
1

Reward Vault Request for BREAD/OHM Kodiak Island

1. Proposer Details

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

For example if the contract is a $EXAMPLE / $BERA pool on XYZ DEX, the proposer should be affiliated with the protocol (XYZ DEX) or one of the tokens in the pool (in this case, $EXAMPLE).

  • Affiliation (protocol / one of the tokens in the contract): Protocol
  1. Protocol Details
  1. Contract/Pool Details
  • Contract Name: BREAD/OHM island
  • Contract Address: 0xd9a747880393f7c33cef1aea36909b36d421f7e5
  • Contract Type / Configuration: kodiak island
  • Describe how the contract works: LP token can be minted/burned by providing or withdrawing liquidity into the island
  • Contract Fees: Typical Kodiak island fees
  • Existing Liquidity / TVL: $1M
  • Identify any address(es) controlling more than 10% of the contract shares: The Yield farms owns 99% of island tokens
  • Is the contract upgradable?: Yes
  • Contract Control: Multisig
  • Is the contract verified?: Yes
  • Can the contract be paused?: Yes, dependent on alerts from Hyper Native security monitoring system and other risk control systems in place for asset management
  • Does the contract rely on oracles?: No

4. Token Details

Provide the following details for each token in the contract (up to 5):

For Non-Major Tokens:

Token 1:

  • Name: BREAD
  • Symbol: BREAD
  • Contract Addresses (on Berachain and bridging addresses if cross-chain): 0x0003eedfdd020bf60d10cf684abac7c4534b7ead
  • Tokenomics, Distribution, and Vesting (links to official docs, website, etc.): Baking and Burning | Baker DAO
  • Identify any address(es) controlling more than 10%: liquidity pool, yield farm
  • Does the project issuing the token have any relationship with current Berachain validators?: Yes
  • Total Supply Cap: N/A
  • Circulating Supply: 3,670,756
  • Token Type: Other
  • Provide extra details (e.g. Use case, Redemption mechanics, Peg stability): minted and burned on an up-only bonding curve
  • Are token contracts upgradable?: no
  • Token Control: Multisig
  • Is the token contract verified?: Yes
  • Is the token a standard ERC20 or any functions have been customized?: ERC20 with custom functions
  • Can the token be paused?: No

Token 2:

  • Name: OHM
  • Symbol: OHM
  • Contract Addresses (on Berachain and bridging addresses if cross-chain): 0x18878Df23e2a36f81e820e4b47b4A40576D3159C
  • Tokenomics, Distribution, and Vesting (links to official docs, website, etc.): https://docs.olympusdao.finance/
  • Identify any address(es) controlling more than 10%: Olympus treasury
  • Does the project issuing the token have any relationship with current Berachain validators?: Yes
  • Total Supply Cap: N/A
  • Circulating Supply: 18,238,441
  • Token Type: Utility/governance
  • Provide extra details (e.g. Use case, Redemption mechanics, Peg stability):
  • Are token contracts upgradable?: no
  • Token Control: Multisig
  • Is the token contract verified?: Yes
  • Is the token a standard ERC20 or any functions have been customized?: ERC20
  • Can the token be paused?: No

5. Token / Project Background / Incentive Token Whitelist

Only two 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 Token:

  • Name: OHM
  • Symbol: OHM
  • Name: wrapped BERA
  • Symbol: wBERA

Additional Requirements:

  • Specify how many tokens per week you plan to allocate for incentives: 500 wBERA per week target for incentives (net value using both OHM and wBERA)
  • Specify for how many weeks you plan to allocate incentives: 3 month initial duration with target to renew & adjust incentives
  • Outline how decisions about token incentives are made (DAO, multi-sig, etc.): multisig
  • Incentive Manager address for wBERA (this address will manage the incentive token, being able to add incentive tokens to the reward vault and change the incentive rate): 0xa9592b702e8bbf6485136e94ee84af263cc3a69b
    • Incentive Manager address for OHM (this address will manage the incentive token, being able to add incentive tokens to the reward vault and change the incentive rate): 0x91494D1BC2286343D51c55E46AE80C9356D099b5

6. Growth, Community & Ecosystem Impact

Why This Contract Matters:

  • How will this contract benefit Berachain?: Will deepen liquidity for BREAD/OHM
  • Will it deepen liquidity for a major ecosystem token (e.g., BERA, core stable asset)?: Yes, OHM
  • Does it enable important trading pairs that drive adoption or integrate with other Berachain projects?: Yes, it will drive the adoption of both OHM - large stable asset, and BREAD, a BERA derivative

Potential Volume / TVL:

  • Provide metrics or estimates on liquidity you expect to attract: current TVL is 1m, with estimated 2-3m TVL
  • Highlight any known liquidity commitments. (If you or partners plan to seed the contract, provide proof of funds or a statement of intent.): no external capital commitments

Synergies with Other Protocols:

  • Will this contract feed into any yield aggregators, lending markets, or liquid staking derivatives on Berachain?: synergies with Kodiak, Yeet, and Olympus

Marketing / Promotion:

  • Are there plans to co-market with another project to bootstrap liquidity?: Yes, co-marketing with Kodiak, Yeet, and Olympus

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.): This vault could evolve to become a core liquidity pair

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]”

2

Pool has been whitelisted