HydraDX

HydraDX is a next-gen DeFi protocol which is designed to bring an ocean of liquidity to Polkadot. The tool for the job the HydraDX Omnipool - an innovative Automated Market Maker (AMM) which unlocks unparalleled efficiencies by combining all assets in a single trading pool.

For more information about HydraDX, please visit https://hydradx.io/.

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 250,000 (whichever is higher). Economic damage is limited to the situation where there is a reasonable risk for existing funds on the HydraDX 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 HydraDX 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.

Payouts under the HydraDX bug bounty program are only made for reports of vulnerabilities which fall under the scope of the program. You can find a full overview of all assets which are in scope hereunder.

If an impact can be caused to any other asset managed by HydraDX 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. This applies only to Critical impacts.

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

Websites and Apps

• Theoretical vulnerabilities without any proof or demonstration
• Attacks requiring physical access to the victim device
• Attacks requiring access to the local network of the victim
• Reflected plain text injection ex: url parameters, path, etc.
  • This does not exclude reflected HTML injection with or without javascript
  • This does not exclude persistent plain text injection
• Self-XSS
• Captcha bypass using OCR without impact demonstration
• CSRF with no state modifying security impact (ex: logout CSRF)
• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
• Server-side non-confidential information disclosure such as IPs, server names, and most stack traces
• Vulnerabilities used only to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Feature requests
• Issues related to the frontend without concrete impact and PoC
• Best practices issues without concrete impact and PoC
• Vulnerabilities primarily caused by browser/plugin defects
• Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
• Any vulnerability exploit which requires browser bugs for exploitation. ex: CSP bypass

The following activities are prohibited by this bug bounty program:

• Any testing with mainnet or public testnet; 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