General (non-BEX) RFRV Reward Vault Request for juBera

Reward Vaults
1
  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) $juBERA

2. Protocol Details

  1. PvP games
    QuillAudit_Reports/Junky Ursas PVP Smart Contract Audit Report - QuillAuudits.pdf at master · Quillhash/QuillAudit_Reports · GitHub
  2. PvH games
    https://github.com/Quillhash/QuillAudit_Reports/blob/master/Junky%20Ursas%20Services%20Smart%20Contract%20Audit%20Report%20-%20QuillAudits.pdf
    3. Vaults & Service contracts
    QuillAudit_Reports/Junky Ursas Services Smart Contract Audit Report - QuillAudits.pdf at master · Quillhash/QuillAudit_Reports · GitHub
  • Does the protocol have any relationship with current Berachain validators?
    Yes

3. Contract/Pool Details

  • Contract Name: jubera
  • Contract Address: 0x0c7d3b02bb5742a02e2f05dfb735d2268f835b98.
  • Contract Type / Configuration: Vault based ERC20. Users can deposit BERA into the Junky Ursas BERA vault and receive juBERA. On withdrawal, BERA is returned.
  • Describe how the contract works: jubera/BERA pair has its own custom exchange rate. When the abstract user of the protocol wins the game, the exchange rate goes up, and when he loses, it goes down. Fees also contribute to the exchange rate. To deposit BERA, the user must open the JU app and exchange assets on a specific page at the current exchange rate and vice versa.
  • Contract Fees: 0
  • Existing Liquidity / TVL: $50k
  • Identify any address(es) controlling more than 10% of the contract shares:
    0xbE9073905E2F0dF62950420c930038890D6c3Aa2: protocol-owned liquidity
  • Is the contract upgradable?: No
  • Contract Control: Vault Manager(0x40a2b487d19bd13fe869C30C90150EFc585A5ba5) controlled by Team Multisig has owner rights on jubera token contract. It mints jubera when user deposits BERA and burns jubera when user withdraws. Vault Manager is upgradable.
  • 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 juBERA
  • Symbol $juBERA
  • Contract Addresses (on Berachain and bridging addresses if cross-chain):
    Berachain: 0x0C7d3B02BB5742A02e2f05dfB735D2268F835b98
  • Tokenomics, Distribution, and Vesting (links to official docs, website, etc.): N/A
  • Identify any address(es) controlling more than 10%:
    0xbE9073905E2F0dF62950420c930038890D6c3Aa2: protocol-owned liquidity
  • Does the project issuing the token have any relationship with current Berachain validators?: Yes
  • If yes, which one?: Infrared, THJ, KysenPool, BlackNodes, P-OPS Team, StakeLab, Lavender.Five
  • Total Supply Cap (if any): No
  • Circulating Supply: 6743
  • Token Type: LP
  • Provide extra details (e.g. Use case, Redemption mechanics, Peg stability) N/A
  • Are token contracts upgradable?: No
  • Token Control: Permissionless
  • Additional details on Token Control: N/A
  • Is the token contract verified?: Yes
  • Is the token a standard ERC20 or any functions have been customized? (e.g. transfer, balance, mint, burn…): Yes, each transfer is also logged by JU vault manager. Junky-Ursas-Service Security Audit Report | QuillAudits
  • 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: BERA
  • Symbol: $BERA

Additional Requirements:

  • Specify how many tokens per week you plan to allocate for incentives: We are planning to allocate 350 $Bera per week.
  • Specify for how many weeks you plan to allocate incentives: Around 8 weeks for bribes in $Bera. This duration is caused by our future token launch, we have a separate part of tokenomics for bribes (Around 5%).
  • Outline how decisions about token incentives are made (DAO, multi-sig, etc.): Multisig
  • 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): 0xB41a6F71d231540746293eE2c75cC89F0D4ebdF0

6. Growth, Community & Ecosystem Impact

Why This Contract Matters:

  • How will this contract benefit Berachain? Junky Bets is the premier decentralized gambling protocol on Berachain. We are currently holding the biggest volume across other competitors. Our vault can benefit our native users and general Berachain DeFi farmers because they can use it as a diversification for their farming strategies.
  • Will it deepen liquidity for a major ecosystem token (e.g., BERA, core stable asset)? Yes
  • Does it enable important trading pairs that drive adoption or integrate with other Berachain projects? Yes

Potential Volume / TVL:

  • Provide metrics or estimates on liquidity you expect to attract. We are targeting to attract 400-500k in TVL during first 2 months.
  • Highlight any known liquidity commitments. (If you or partners plan to seed the contract, provide proof of funds or a statement of intent.) There is 50k in TVL at that moment. Moreover, we have a commitment from private LP for another 50k.

Synergies with Other Protocols:

  • Will this contract feed into any yield aggregators, lending markets, or liquid staking derivatives on Berachain? Yes, we are in talks with Infrared and Beratrax.

Marketing / Promotion:

  • Are there plans to co-market with another project to bootstrap liquidity? Yes, we are in talks with biggest communities to do a co-marketing. We are a strategic partner of THJ.

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.) Our target is to have a deep liquidity for our games. It will be used for increasing bet limits and user experience in general. Influx of TVL will help us to reach a sustainability in terms of bet limits.

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/JunkyUrsas/status/1907020839909781505

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!

8 Likes
2

Hi team, thanks for the proposal!

Could you please help address the following concerns?

  • TVL is under 100K
  • LPs are fairly concentrated and POL heavy

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