Grizzly.fi is a crypto platform that simplifies investing in the best opportunities in the DeFi space. Grizzly.fi will act as a Hub for long term capital growth. Grizzly.fi starts by making Liquidity Mining accessible and will extend the portfolio continuously. The special thing about Grizzly.fi is that it is very easy for beginners and professionals to build a passive income with cryptocurrencies. Through Grizzly.fi users make money no matter if prices go up or down.
For more information about Grizzlyfi, please visit https://grizzly.fi/.
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 20,000
The following vulnerabilities are not eligible for a reward:
- Mining rate depends on the token price that is received from a current Honey-BNB rate. This rate can be manipulated with a flash loan before the deposit/withdraw/changeStrategy transactions, and then more rewards will be minted for all pool participants.
Payouts are handled by the Grizzlyfi team directly and are denominated in USD. However, payouts are done in ETH.
- USD $100,000
- USD $10,000
Assets in scope
- Smart Contract - StakingPoolType
- Smart Contract - SeedVestingType
- Smart Contract - ReferralType
- Smart Contract - HoneyTokenType
- Smart Contract - HoneyBNBFarmType
- Smart Contract - GrizzlyType
- Smart Contract - GrizzlyStrategyType
- Smart Contract - StableCoinStrategyType
- Smart Contract - StandardStrategyType
- Smart Contract - BaseConfigType
All smart contracts of Grizzlyfi can be found at https://github.com/grizzlyfi/smart-contracts. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
Though only the proxy contracts are listed as in-scope, current implementation and any further updates to the implementation contracts are considered in scope. When reporting a bug, please make sure to select the relevant proxy smart contract as the target.
If an impact can be caused to any other asset managed by Grizzlyfi that isn’t on this table but for which the impact is in the Impacts in Scope section, you are encouraged to submit it for the consideration of the project. This applies to only Critical and High impacts.
Impacts in scope
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Miner-extractable value (MEV)CriticalImpact
- Permanent freezing of fundsCriticalImpact
- Protocol InsolvencyCriticalImpact
- Theft of unclaimed yieldHighImpact
- Temporary freezing of funds for a minimum of 7 daysHighImpact
- Permanent freezing of unclaimed yieldHighImpact
Out of Scope & Rules
The following vulnerabilities are excluded from the rewards for this bug bounty program:
- Attacks that the reporter has already exploited themselves, leading to damage
- Attacks requiring access to leaked keys/credentials
- Attacks requiring access to privileged addresses (governance, strategist)
Smart Contracts and Blockchain
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Basic economic governance attacks (e.g. 51% attack)
- Lack of liquidity
- Best practice critiques
- Sybil attacks
- Centralization risks
The following activities are prohibited by this bug bounty program:
- Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
- 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
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty