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.
PoC required
Rewards
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.
All Medium, High and Critical Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. All Low Smart Contract bug reports require a suggestion for a fix to be eligible for a reward.
Payouts are handled by the GYSR team directly and are denominated in USD. However, payouts are done in USDC and ETH, with the choice of the ratio at the discretion of the team.
Program Overview
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.
For more information about GYSR, along with whitepapers and security audit reports, please visit https://www.gysr.io/.
This bug bounty program is focused on their core smart contracts and on preventing:
- Thefts and freezing of principal of any amount
- Thefts and freezing of unclaimed yield of any amount
- Logical errors or miscalculation that result in incorrect accounting or yield amount
- Unexpected and unfair manipulation of incentive mechanisms
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.