Stader for Polygon is a non-custodial smart contract based staking platform that helps you conveniently discover and access staking solutions.
In the short term, Stader for Polygon is building native staking smart contracts across multiple chains including Terra, Fantom, Polygon, Solana, among others, and building an economic ecosystem to grow and develop solutions like YFI-style farming with rewards, launchpads, gaming with rewards, liquid staking solutions, and more.
In the long term, Stader for Polygon is focused on unlocking the platform approach and nurturing third parties to develop several staking-related applications on top of Stader for Polygon infrastructure.
For more information about Stader for Polygon, please visit https://staderlabs.com/.
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.
All bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.
Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of USD 100 000 for Critical smart contract bug reports.
Previous issues highlighted in the following audit reports are considered out of scope of this program:
Payouts are handled by the Stader for Polygon team directly and are denominated in USD. However, payouts are done in USDC or ETH, at the discretion of the team.
- Up to USD $1,000,000
- USD $100,000
- USD $20,000
Assets in scope
- Smart Contract - MaticX token ERC20 - Stader for PolygonType
- Smart Contract - ValidatorRegistry - Stader for PolygonType
For proxy contracts, only the current implementation and any further updates to the implementation contracts are considered in scope.
All smart contracts of Stader for Polygon can be found at https://github.com/stader-labs/stader-liquid-token/tree/main/contracts. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
If any Critical or High severity impact can be caused to any other asset managed by Stader for Polygon that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.
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.
- Any governance voting result manipulationCriticalImpact
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Protocol InsolvencyCriticalImpact
- Miner-extractable value (MEV)CriticalImpact
- Theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Temporary freezing of funds for at least 24 hoursHighImpact
- Smart contract unable to operate due to lack of token fundsMediumImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Unbounded gas consumptionMediumImpact
- Theft of gasMediumImpact
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