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:
polar@ramen.finance
- Proposer’s project name:
Ramen
- Proposer’s X account (you will be required to make a post from the X account provided for verification purposes):
@ramen_finance
- Best Telegram Handle for questions/fixes:
@polarbera
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)
Affiliation: $RAMEN token issued by Ramen Finance
- Protocol Details
- Protocol Name (Example: XYZ DEX):
Ramen Finance
- Protocol Type (DEX/Lending/Staking/Derivatives/Other):
Other: Launchpad
- Protocol X profile link:
x. com/ramen_finance
- Protocol docs link:
docs.ramen.finance
- Protocol audits links (multiple links):
- Fixed-price Mode and Token Contracts: Simplified Report Ramen Finance - HackMD
- Price Discovery Mode: About b0g0 - HackMD
- Does the protocol have any relationship with current Berachain validators?
Yes
- Contract/Pool Details
- Contract Name (Example: $EXAMPLE / $BERA):
rvRAMEN Receipt Token Staking
- Contract Address: Insert the contract address.
0xE5C16626b3818468C787affB0d5278d5559b9dAf
- Contract Type / Configuration: Is it a standard AMM pool, a lending pool, a derivatives pool, a custom contract:
Berachain Proof-of-Liquidity Standard Reward Vault, deployed through the factory 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…)
When users lock RAMEN for the non-transferrable gRAMEN for the purpose of participating in fixed-price token launches on Ramen, the corresponding number of rvRAMEN receipt tokens will be issued and staked automatically into this reward vault on behalf of users.
- Contract Fees: Outline the fee structure (e.g., 10% of staking rewards)
0% fee
- Existing Liquidity / TVL: current liquidity and volume stats (if applicable).
16.6M RAMEN tokens locked (estimated US$3M in value)
- Identify any address(es) controlling more than 10% of the contract shares
(address / type: team, protocol-owned liquidity, etc.)
No
- Is the contract upgradable?
Yes
- Contract Control: (Multisig/Single Owner/RBAC/Permissionless/Governance)
Multisig
- Additional details on Contract Control
- Is the contract verified?
Yes
- Can the contract be paused?
Yes
- Does the contract rely on oracles?
No
- (If yes, explain oracle dependency)
4. Token Details
Provide the following details for each token in the contract (up to 5):
For Non-Major Tokens:
- Name:
Ramen Receipt Token
- Symbol:
RV-RAMEN
- Contract Addresses (on Berachain and bridging addresses if cross-chain):
chain / address
Berachain: 0x1a6113B582B21c8aB3c8FBAE5Cc04bCcA5Dc1503
- Tokenomics, Distribution, and Vesting (links to official docs, website, etc.)
Receipt tokens are minted and issued on the fly when users lock RAMEN for gRAMEN
- Identify any address(es) controlling more than 10%
(address / type: team, foundation, investor, etc.)
None
- Does the project issuing the token have any relationship with current Berachain validators?
Yes
- If yes, which one?
The Honey Jar
- Total Supply Cap (if any)
100,000,000 (100M)
- Circulating Supply
Zero
- Token Type:
(Governance, Utility, Memecoin, Stablecoin, LST, RWA, Other)
Utility
- Provide extra details (e.g. Use case, Redemption mechanics, Peg stability)
rvRAMEN token is a receipt token used to track users’ RAMEN locking activities. It’s minted/burned 1-for-1 when RAMEN is locked/unlocked in our gRAMEN contract
- Are token contracts upgradable?
No
- Token Control: (Multisig/Single Owner/RBAC/Permissionless/Governance)
Multisig
- Additional details on Token Control
- Is the token contract verified?
Yes
- Is the token a standard ERC20 or any functions have been customized? (e.g. transfer, balance, mint, burn…)
Standard ERC20
(If custom, provide a link to an audit.)
- 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 / Symbol for Incentive Token 1:
Bera / $BERA
- Name / Symbol for Incentive Token 2:
RAMEN Token / $RAMEN
Additional Requirements:
- Specify how many tokens you plan to allocate for incentives
At least 70,000 $BERA from Ramen’s RFA allocation and 2,000,000 $RAMEN will be allocated for incentives over a minimum of 24 weeks. $BERA incentives will be used first. More incentives may be allocated based on protocol revenue performance.
- Outline how decisions about token incentives are made (DAO, multi-sig, etc.).
Multi-sig
- 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)
0x0068E67048998c3D4DC38fD1A4A478803e76fbEA
6. Growth, Community & Ecosystem Impact
Why This Contract Matters:
- How will this contract benefit Berachain?
By rewarding $RAMEN staking, we aim to attract more prospective launchpad participants for the Ramen token launchpad, which ensures that projects bootstrapping liquidity for their TGEs can reach a greater audience and achieve a wider, healthier, more equitable token distribution from day one.
- Does it enable important trading pairs that drive adoption or integrate with other Berachain projects?
Currently, 16.6M $RAMEN is locked by a total of 3,329 users, of which 3,025 users registered for the recent $henlo allocation lottery, signalling a highly active community of launchpad users excited about new projects and protocols on Berachain.
With additional rewards from this reward vault, this drastically reduces the opportunity cost to participate in launchpad events. Conservatively, we expect to double the participant pool to at least 7,000 eligible users in the next 6 months with another 5 to 6 million RAMEN locked.
Synergies with Other Protocols:
- Will this contract feed into any yield aggregators, lending markets, or liquid staking derivatives on Berachain?
While this contract does not directly feed into DeFi primitives, we believe it does drive participation and adoption for new protocols launching on Ramen, many of which are innovative Berachain-native products. In addition, the high activity and engagement rate demonstrated by the Ramen community will also translate to greater activity and delegation of $BGT to validators.
Marketing / Promotion:
- Are there plans to co-market with another project to bootstrap liquidity?
As a launchpad protocol, Ramen regularly co-markets with featured ecosystem projects as they launch their tokens on our platform, as well as key partners like The Honey Jar, Beraland, and Kodiak.
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.)
By incentivizing $RAMEN staking and deepening the participation pool, we see Ramen as the ecosystem-aligned token launchpad platform of choice for protocols to effectively bootstrap liquidity and distribute tokens to genuine community users, which in turns, drive adoption in ecosystem dApps (active users), deepens liquidity in major and non-major assets (TVL), and promote healthier trading activity post-launch (trading volume).
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]”