General (non-BEX) RFRV Reward Vault Request for Kuma Reward Token / $KRT

Reward Vaults
1

Reward Vault Request for Kuma Reward Token / $KRT

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: alex@kuma.bid
  • Proposer’s project name: Kuma
  • Proposer’s X account: AlexWearn
  • Best Telegram Handle for questions/fixes: @alexwearn
  • Affiliation: Kuma CEO

2. Protocol Details

3. Contract/Pool Details

  • Contract Name (Example: $EXAMPLE / $BERA)
    Kuma Reward Token / $KRT

  • Contract Address: Insert the contract address.
    RewardVault: 0x5540e29749f6c8f5dcf49fcc17c67e97a8e7335b
    Kuma Reward Token: 0x273c832797bfda1c0826a786670d041282bd6afc

  • Contract Type / Configuration: Custom 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 Kuma Reward Token (KRT) incentivizes traders with BGT rewards for activity that promotes and sustains exchange growth. KRT has no value and does not require any user interaction. KRT is a dummy ERC20 token that implements a permissioned control function to update the token distribution within its associated RewardVault according to signals from the protocol.
    As a perpetuals DEX, the protocol tracks several key performance indicators, such as trading volume and referrals. These indicators are aggregated and screened for undesirable behavior, such as wash trading, to periodically rank overall wallet performance. The protocol then updates KRT distribution according to the trailing period’s performance, incentivizing protocol growth with BGT rewards.

  • Contract Fees: Outline the fee structure: No fees

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

  • Identify any address(es) controlling more than 10% of the contract shares: None

  • Is the contract upgradable? Yes

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

  • Additional details on Contract Control

  • Is the contract verified? Yes

  • Can the contract be paused? No

  • Does the contract rely on oracles? No

4. Token Details

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

For Major Tokens:
  • Name
  • Symbol
For Non-Major Tokens:
  • Name
  • Symbol
  • 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%
    (address / type: team, foundation, investor, etc.)
  • Does the project issuing the token have any relationship with current Berachain validators?
  • If yes, which one?
  • Total Supply Cap (if any)
  • Circulating Supply
  • Token Type:
    (Governance, Utility, Memecoin, Stablecoin, LST, RWA, Other)
  • Provide extra details (e.g. 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?

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 - Bridged USDC (Stargate)

  • Symbol - USDC.e

  • (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%
    (address / type: team, foundation, investor, etc.)

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

  • Total Supply Cap (if any) and 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
    $10,000 USDC per week.

  • Specify for how many weeks you plan to allocate incentives
    Incentives will run for a minimum of 6 months.

  • Outline how decisions about token incentives are made (DAO, multi-sig, etc.).
    Incentive decisions are made by the Kuma team.

  • Incentive Manager address
    0xf640d2502FBd9Ca9F8a884b26a1e738E62d254Cc

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?

The Kuma Rewards Vault strengthens Berachain by driving trading activity, L1 deposits, and ecosystem expansion.

  1. Increased Trading Volume: Incentivizes activity on Kuma, a Berachain perps DEX, boosting both trading volume and liquidity.
  2. Liquidity Growth: Attracts liquidity from traders seeking to earn BGT through perpetual futures trading, increasing Berachain’s TVL.
  3. Ecosystem Expansion: Supports perpetual swap pair listings of Berachain-native tokens, increasing their utility and benefiting their respective communities.
  4. Network Visibility: Increases exposure for Berachain by promoting a high-quality exchange product tied to the ecosystem.

Potential Volume / TVL:

  • Provide metrics or estimates on liquidity you expect to attract.
  • Highlight any known liquidity commitments

We will fund the contract initially with 10,000 USDC weekly. Trading fees will be used to boost these rewards further, creating a positive feedback loop that grows alongside user activity.

We are also in active discussions with multiple liquidity providers and validators within the Berachain ecosystem who have expressed strong interest in supporting the program.

With Kuma’s high-quality UI/UX and a well-structured PoL incentives program, we anticipate positioning the platform among the top 10 perpetual DEXs across all chains. Based on comparable market performance, this would translate to $150M–$200M in daily trading volume.

With an estimated Volume/TVL ratio of 2-5x, this would generate $30-100M in TVL.

Synergies with Other Protocols:

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

Future upgrades to the Kuma platform will allow for multi-collateral support. This introduces the potential to incentivize deposits of other assets in the ecosystem including LSTs and debt receipt tokens.

Marketing / Promotion:

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

Yes, we plan to collaborate with Berachain-native projects to list perpetuals for their tokens and co-market these listings, driving visibility and engagement across the ecosystem.

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

Over the long term, the Kuma Rewards Vault could evolve into a central liquidity engine for Berachain by directly enhancing the utility of the Kuma token itself. As liquidity and trading volume grow, accumulated vault revenues and protocol-owned liquidity could be strategically deployed to offer sustainable yields to Kuma token stakers. This creates direct incentives for token holders to stake long-term, aligning their interests with protocol.

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

Insert post link - https://x.com/kumadotbid/status/1898912636479164516

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

KRT has been whitelisted Kuma - Trade Rewards | Reward Vault | BeraHub