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
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Build Commands, Test Commands, and How to Run Them
forge build, forge test.
Asset Accuracy Assurance
Bugs found on assets incorrectly listed in-scope are valid.
Code Freeze Assurance
Code of the assets in scope is frozen while the program is live.
-
Duplicate submissions of bugs are valid. Duplicate submissions of Insights are invalid.
-
The project commits to keeping private all info related to bug findings until this program is over. This means the project will not leak info about any bug findings or planned bug fixes, including bug findings found independently by the project or from concurrent private audits.
Permanent freezing of funds
Protocol insolvency
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Theft of unclaimed yield
Theft of unclaimed royalties
Permanent freezing of unclaimed yield
Permanent freezing of unclaimed royalties
Temporary freezing of funds for at least 24 hours
Smart contract unable to operate due to lack of token funds
Block stuffing
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Theft of gas
Out of scope
- The contract
NFTVesting.solis not included in the scope of this Audit Competition. - Griefing via block stuffing on berachain to prevent users from Yeeting, forcing the game to end by blocking new transactions.
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers