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:
pepar@ramen.finance
- Proposer’s project name:
Panda Bot
- Proposer’s X account (you will be required to make a post from the X account provided for verification purposes):
@peparbera
- Best Telegram Handle for questions/fixes:
@peparbera
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: Panda Bot
- Protocol Details
- Protocol Name (Example: XYZ DEX):
Panda Bot
- Protocol Type (DEX/Lending/Staking/Derivatives/Other):
Other: Telegram trading bot
- Protocol X profile link:
x. com/pandabotfi
- Protocol docs link:
- Protocol audits links (multiple links):
We use a managed wallet service (Turnkey) which is also used by Moonshot, Infinex, MagicEden, Alchemy. At no point does PandaBot developers have custody of the users’ funds.
- Does the protocol have any relationship with current Berachain validators?
Yes
- Contract/Pool Details
- Contract Name (Example: $EXAMPLE / $BERA):
Panda Bot Router
- Contract Address: Insert the contract address.
0x7Ba0eA6C875f41139654522798A76BBc057CC484
- Contract Type / Configuration: Is it a standard AMM pool, a lending pool, a derivatives pool, a custom contract:
Router
- Describe how the contract works (e.g., how to mint and redeem shares of the contract, if tokens can be exchanged within the contract…)
This contract routes all trades through Panda Bot to the correct sources of liquidity
- Contract Fees: Outline the fee structure (e.g., 10% of staking rewards)
Up to 1% fee of the transactions
- Existing Liquidity / TVL: current liquidity and volume stats (if applicable).
100,000+ BERA in volume
- Identify any address(es) controlling more than 10% of the contract shares
(address / type: team, protocol-owned liquidity, etc.)
No
- Is the contract upgradable?
No
- Contract Control: (Multisig/Single Owner/RBAC/Permissionless/Governance)
Multisig
- Additional details on Contract Control
- Is the contract verified?
Yes
- Can the contract be paused?
No
- 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:
Panda Point
- Symbol:
PP
- Contract Addresses (on Berachain and bridging addresses if cross-chain):
chain / address
Berachain: 0x288E8544364c6e2aE553465127bB6d622Bce2E12
- Tokenomics, Distribution, and Vesting (links to official docs, website, etc.)
N/A
- Identify any address(es) controlling more than 10%
(address / type: team, foundation, investor, etc.)
No
- Does the project issuing the token have any relationship with current Berachain validators?
Yes
- If yes, which one?
Kodiak
- Total Supply Cap (if any)
No supply cap
- Circulating Supply
Zero
- Token Type:
(Governance, Utility, Memecoin, Stablecoin, LST, RWA, Other)
Reward Vault Receipt Tokens
- Provide extra details (e.g. Use case, Redemption mechanics, Peg stability)
PandaPoint is a receipt token used to reward user activity on PandaBot based on trading volume and referred volume. Every swap done through the PandaBot router will earn PandaPoints entirely on-chain, in real time, which are automatically staked into BGT earning reward vault on behalf of the user. PandaPoints are awarded directly proportional to volume and referred volume.
- 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…)
It’s an ERC-20 contract with whitelist-only minting to facilitate delegateStaking for PandaBot users
(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:
Wrapped Bera / $WBERA
Additional Requirements:
- Specify how many tokens you plan to allocate for incentives
50% of trading fees collected by Panda Bot (subject to changes in the future)
- 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)
0x7645df7Fccef4491e1CE53400E041B5643e08421
6. Growth, Community & Ecosystem Impact
Why This Contract Matters:
- How will this contract benefit Berachain?
This contract aims to reward and incentivise on-chain trading activity via Panda Bot. With this reward vault, a positive flywheel effect is made possible where trading fees get reinvested into the ecosystem, and liquidity and genuine, productive trading activity becomes more attractive to native Berachain users as well as traders from other venues.
- Will it deepen liquidity for a major ecosystem token (e.g. BERA, core stable asset)?
Yes, every swap on Panda Bot must be made with BERA
- Does it enable important trading pairs that drive adoption or integrate with other Berachain projects?
Built by native teams (Ramen and Kodiak) and facilitating over $1 million in trading volume with 3.4k user signups so far, Panda Bot is positioned to be a crucial native trading infrastructure for new tokens and memecoins on Berachain. Through Panda Bot, users can trade much quicker and more frequently for any token that is and will be on Berachain.
Synergies with Other Protocols:
- Will this contract feed into any yield aggregators, lending markets, or liquid staking derivatives on Berachain?
Panda Bot routes trades via Kodiak and Panda Factory and will soon integrate with other liquidity venues on Berachain.
Marketing / Promotion:
- Are there plans to co-market with another project to bootstrap liquidity?
Kodiak and Ramen will co-incentivize and co-market for 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.)
The receipt token used for this reward vault can be scaled and integrated to reward users for trading volume on Panda Factory. Since trading APIs are integrated with Kodiak v2, v3, Panda Factory, as well as Ooga Booga, Panda Bot will expand and provide an excellent trading experience for users and boost on-chain trading activity on Berachain.
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]”