Request for iBGT Reward Vault

Summary of RFRV Criteria

  • Deployed Contract: Must already be live.
  • Deployed Tokens: Must have the incentive tokens live.
  • Economic Value: Show significant TVL, trading volume potential, or strategic benefit.
  • Security: Use standard or audited contracts; tokens must be reputable.
  • Decentralization: Each token in the pair must show sufficient decentralization.
  • Transparency: Team/project info, audits, and open communication.
  • Synergy: Integrate with or benefit the broader Berachain ecosystem.
  • Community Support: Demonstrate genuine interest/demand.
  • Operational Safety: Clear ownership, upgradeability details, and compliance considerations.
  • Pair with a Major (Recommended for DEX pools): Major tokens are BERA, HONEY, BYUSD, USDC, wETH, and wBTC.
  • Verification: The proposer should be affiliated with the protocol or at least one of the tokens in the contract

1. Proposer Details

  • Email: monobera@beratrax.com
  • Proposer’s project name: BeraTrax
  • Proposer’s X account (you will be required to make a post from the X account provided for verification purposes): https://x.com/m0n0bera
  • Best Telegram Handle for questions/fixes: @m0n0bera

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): BeraTrax is the protocol that is requesting this vault, and is the protocol that has deployed this vault.
  1. Protocol Details: Mobile yield aggregator & auto-compounder on Berachain
  • Protocol Name (Example: XYZ DEX): BeraTrax
  • Protocol Type (DEX/Lending/Staking/Derivatives/Other)
    • If other: please specify: Staking
  • Protocol X profile link: https://x.com/beratrax
  • Protocol docs link: https://docs.beratrax.com
  • Protocol audits links (multiple links): BeraTrax Smart Contract Audit | Cyberscope
  • Does the protocol have any relationship with current Berachain validators? Yes, we have a relationship with Infrared, THJ, and Lavender.Five

  1. Contract/Pool Details
  • Contract Name (Example: $EXAMPLE / $BERA)

ERC-20: BeraTrax Vault Infrared BGT (btxiBGT)

  • Contract Address: Insert the contract address.
  • Contract Type / Configuration: Is it a standard AMM pool, a lending pool, a derivatives pool, a custom contract

Standard ERC4626 Tokenized Vault contract

  • Describe how the contract works (e.g., how to mint and redeem shares of the contract, if tokens can be exchanged within the contract…)

The vault contract deploys the funds to the iBGTStrategy contract which deposit the iBGT into infrared’s staking vault, staking rewards are auto compounded through strategy contract

  • Contract Fees: Outline the fee structure (e.g., 10% of staking rewards)

Contract takes 10% of staking rewards

  • Existing Liquidity / TVL: current liquidity and volume stats (if applicable).

$139k in TVL

  • Identify any address(es) controlling more than 10% of the contract shares
    (address / type: team, protocol-owned liquidity, etc.)

The following are users who control more than 10% of the vault shares
0xdc35A1bBB14c944430Ab6Cf21c3075417535fAb8
0x8A474fD1b929306a6827630AEFEaDE443128eC68

  • Is the contract upgradable?

No

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

Multisig

  • Additional details on Contract Control

  • Is the contract verified?

Yes contract is deployed through a factory, so the source code can be found on the factory itself
0xCBd77Fb2EB03Ab41f7FC3f579faC23161F977313

  • Can the contract be paused?

No

  • Does the contract rely on oracles?

    • (If yes, explain oracle dependency)

No


4. Token Details

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

For Major Tokens:
  • Name

Infrared BGT

  • Symbol

iBGT

For Non-Major Tokens:
  • Name

ERC-20: BeraTrax Vault Infrared BGT

  • Symbol

btxiBGT

  • Contract Addresses (on Berachain and bridging addresses if cross-chain):
    chain / address
  • Tokenomics, Distribution, and Vesting (links to official docs, website, etc.)

This is a vault share token, it is minted based on the iBGT deposit proportional to its iBGT balance of the vault.

  • Identify any address(es) controlling more than 10%
    (address / type: team, foundation, investor, etc.)
    The following are users who control more than 10% of the vault shares
    0xdc35A1bBB14c944430Ab6Cf21c3075417535fAb8
    0x8A474fD1b929306a6827630AEFEaDE443128eC68

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

  • If yes, which one?

No

  • Total Supply Cap (if any)

None

  • Circulating Supply

19,061

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

Vault share

  • Provide extra details (e.g. Use case, Redemption mechanics, Peg stability)

ERC4626 vault share

  • Are token contracts upgradable?

No

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

0x1cfe31Bfa1Ac9b28588C91BB4300A1ED032F069F

  • Additional details on Token Control
  • Is the token contract verified?

Yes contract is deployed through a factory, so the source code can be found on the factory itself
0xCBd77Fb2EB03Ab41f7FC3f579faC23161F977313

  • 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.)

ERC4626 standard token BeraTrax Smart Contract Audit | Cyberscope

  • 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.

Our native token will not be included, so for the section below, the information will be for ecosystem HONEY and BERA tokens,

Additional Requirements:

  • Specify how many tokens you plan to allocate for incentives and over what period of time:

$20,000 HONEY for 2 months, at which point we will determine if we want to change the reward token & reallocate.

  • Outline how decisions about token incentives are made (DAO, multi-sig, etc):

Currently decided by the core team, but the plan is to move these decisions to the hands of the project token holders once that token is live.

  • 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):

0x1cfe31Bfa1Ac9b28588C91BB4300A1ED032F069F


6. Growth, Community & Ecosystem Impact

Why This Contract Matters:

  • How will this contract benefit Berachain?

iBGT is an abstraction on BGT that allows PoL participation with the convenience of liquidity. BeraTrax’s vault builds automation on top of IBGT with auto-compounding, and allows easier deposit with native zapping. Incentivizing this vault will lead to more iBGT liquidity.

  • Will it deepen liquidity for a major ecosystem token (e.g., BERA, core stable asset)?

It will do so for iBGT, which currently is the most popular liquid wrapper for BGT.

  • Does it enable important trading pairs that drive adoption or integrate with other Berachain projects? Not directly, but it deepens iBGT liquidity and simplifies its access.

No

Potential Volume / TVL:

  • Provide metrics or estimates on liquidity you expect to attract:

Currently, our iBGT vault has about $140k in liquidity. The underlying vault has $10m. Our expectation is co-market this vault with Infrared to bring awareness to this simplified of staking iBGT, and increase liquidity my multiple folds.

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

None.

Synergies with Other Protocols:

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

Infrared’s iBGT staking.

Marketing / Promotion:

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

Yes, we will coordinate with Infrared on the co-marketing of this reward vault.

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.)

In the future, we can work with Infrared’s iBGT adapter to enable the BGT earned to itself be in iBGT and add directly to the APY of the vault, even further deepening iBGT liquidity.


7. Verification

Please post the following text with the provided X account:

“Submitted Reward Vault Request for btxiBGT on protocol BeraTrax with incentive token HONEY”

Insert post link: https://x.com/m0n0bera/status/1899512773500932116


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!

2 Likes

Hi team, thanks for the proposal.

A couple of concerns to address:

  • Reward Vault Address was not provided
  • Incentive amount is below the minimum threshold (USD 10,000 per month for a minimum duration of 2 months)
  • Is the reward vault redundant, if it is incentivizing the autocompounding of iBGT It wouldn’t make sense to incentivize the same capital twice.

Please note that the following feedback doesn’t represent the opinions of the BGT Foundation.
It is contextual feedback from the Bera ecosystem team with respect to publicly stated guidelines.

With the following changes implemented, this application should be a better candidate for a Reward Vault.

1 Like

Hello BeraLabs team,

Here is the address for the iBGT Reward Vault: RewardVault | Address 0xf27Cd149e5221fb60be011f6009a60BC054eAf66 | BeraScan

For the incentives, I believe we did say that we would do $20k over 2 months, so that means $10k a month for two months, which is the minimum. it wasn’t clear before, we are restating it now more clearly that we will meet the minimum.

Regarding redundancy: The iBGT vault we’ve proposed is not double-counting capital or seeking to re-incentivize existing emissions. This vault simply aggregate and compound iBGT yield for users who already hold iBGT, as well as helping users obtain it with our zapping into the vault. The actual growth coming from the strategy of swapping whatever rewards are emitted to iBGT for in order to increase the sake in iBGT. It’s not generating new emissions or directing BGT to the same source again—it’s taking distributed rewards and putting them to work more efficiently.

The intent is to improve capital efficiency and reduce friction. Many users holding iBGT benefit from this efficiency if their intent was to restake anyways, and our intent is to bring this option a mobile form factor to make it easy to be introduced to PoL benefits in a single click.