Yeet is a gamified DeFi protocol on Berachain that offers an interactive financial experience through strategy and timing. Its core feature, the Yeet Game, allows users to deposit BERA tokens into a pool, with the last depositor winning most of the funds. YeetBonds help protocols manage their liquidity efficiently, while Yeetard NFTs provide additional in-game benefits.
The native $YEET token can be farmed and staked for rewards. By integrating game mechanics into DeFi, Yeet fosters community engagement, liquidity solutions, and a unique way to participate in decentralized finance. Learn more at https://www.yeetit.xyz/
Evaluating
Triaged by Immunefi
Step-by-step PoC Required
Vault program
This Audit Competition Is Under Evaluation
Immunefi vault program
Rewards
Rewards by Threat Level
Reward pool:
If bugs are found → USD $30k (see Immunefi’s Standardized Competition Reward Terms)
If not a single bug is found (Insights do not count as bugs) the reward pool is (15% of the max Reward Pool) → $4.5k.
Duplicate submissions of bugs are valid. Duplicate submissions of Insights are invalid.
Private known issues, meaning known issues that were not publicly disclosed, are valid and unlock the corresponding reward pool.
Yeet rewards are denominated in USD and distributed in USDC on Ethereum
Proof of Concept (PoC) Requirements
For this program, runnable PoC code is not required. Whitehats are instead required to write a step-by-step explanation of the PoC and impact This explanation needs to be entered in the PoC section of the submission wizard to prevent the submission from being excluded by our OOS filter.
Program Overview
Your favorite Bonzi on berachain. Yeet is a gamified DeFi protocol in the Berachain ecosystem with no dominant game theoretic strategy. Players can win or lose money in a variety of different ways, and employ multiple types of tactics whilst playing.
For more information about Yeet, please visit https://www.yeetit.xyz/
Audits
Known Issues
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- Any testing with pricing oracles or third-party smart contracts
- Attempting phishing or other social engineering attacks against our employees and/or customers
- Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
- Any denial of service attacks that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.
Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.