Hydration
Hydration is the leading liquidity protocol on Polkadot. Its mission is to make DeFi efficient, simple, and unstoppable. To achieve this, Hydration unites swaps, lending and a stablecoin currency under the roof of a single, scalable appchain.
PoC required
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 web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All High and Critical Blockchain bug reports require a PoC to be eligible for a reward. Explanations and statements are not accepted as PoC and code are required.
The rewards for reporting Critical Blockchain vulnerabilities are capped at 10% of the potential economic damage, or USD 1,000,000 (whichever is higher). Economic damage is limited to the situation where there is a reasonable risk for existing funds on the Hydration platform. Indirect damages such as reputational damage are out of scope. The assessment of the extent of any potential economic damage is at the full discretion of the Galactic Council. However, there is a minimum reward of USD 15,000 for reporting any vulnerability which can be classified under the category Critical Blockchain.
All potential vulnerabilities are assessed by the Galactic Council based on internally established criteria, taking into account the exploitability of the bug, the impact it causes, and the likelihood of the vulnerability presenting itself, which is especially factored in with bug reports requiring multiple conditions to be met that are currently not in place.
High blockchain/DLT vulnerabilities are scaled based on internally established team criteria, taking into account the exploitability of the bug, the impact it causes, and the likelihood of the vulnerability presenting itself, which is especially factored in with bug reports requiring multiple conditions to be met that are currently not in place. However, there is a minimum reward of USD 5,000, rewards will be provided at the determined fair value by the team depending on these conditions, assuming that the bug report is in-scope of the bug bounty program.
With regard to Blockchain vulnerabilities, only code involving runtime pallets of Hydration and pallets developed by Galactic Council are considered as in-scope of the bug bounty program. Pallets that are not in the mainnet runtime, are not live or are under development are considered as out-of-scope of the bug bounty program.
Payouts are handled by the Galactic Council directly and are denominated in USD. However, the payouts are done in HDX.
Program Overview
Hydration is the leading liquidity protocol on Polkadot. Its mission is to make DeFi efficient, simple, and unstoppable. To achieve this, Hydration unites swaps, lending and a stablecoin currency under the roof of a single, scalable appchain.
For more information about Hydration, please visit https://hydration.net/.
KYC not required
No KYC information is required for payout processing.
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.