GYSR
GYSR is an open platform for on-chain incentives. It makes yield farming and token distribution easier, more accessible, and safer for both the creator and the investor. The platform allows anyone to configure and launch a staking pool with zero code.
ETH
Defi
NFT
Staking
Yield Aggregator
Solidity
Maximum Bounty
$10,000Live Since
07 January 2022Last Updated
12 December 2024PoC Required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Severity
Critical
Title
Direct theft of any user funds other than unclaimed yield
Severity
Critical
Title
Permanent freezing of funds
Severity
High
Title
Theft of unclaimed yield
Severity
High
Title
Permanent freezing of unclaimed yield
Severity
High
Title
Temporary freezing of funds
Severity
Medium
Title
Smart contract unable to operate
Severity
Medium
Title
Unexpected and unfair manipulation of time incentive mechanisms
Severity
Medium
Title
Unexpected and unfair manipulation of GYSR bonus mechanisms
Severity
Low
Title
Miscomputed rewards
Severity
Low
Title
Smart contract temporarily unable to operate
Out of scope
Program's Out of Scope information
- Any issues caused by invalid, non compliant, or unsupported third party tokens (ERC20, ERC721, etc) shall be considered out of scope
- Unsupported token mechanics include (but are not limited to)
- tokens with bot guards or transfer cooldown periods
- non-uniform elastic token supply expansion/shrinking
- airdrops or interest in other ERC20 tokens
- random lottery style airdrops to individual users
- elastic token expansion beyond 1000x of rate at initial deposit
- Best practice critiques
Default Out of Scope and rules
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