Zenlink
Zenlink DEX Protocol is the underlying unified and universal cross-chain DEX Protocol, which enables parachains to quickly have DEX functionality and share liquidity with other parachains. In addition, Zenlink DEX Aggregator can connect to all DEX DApps on Polkadot, which together form the Zenlink DEX Network with full liquidity.
PoC required
KYC 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 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. In addition, all bug reports must come with a suggestion for a fix in order to be considered for a reward.
All issues previously highlighted in the following audit reports are also considered as out of scope:
Zenlink requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is the name, country of residence and a passport photo.
Payouts are handled by the Zenlink team directly and are denominated in USD. However, payouts are done in ZLK.
Program Overview
Zenlink DEX Protocol is the underlying unified and universal cross-chain DEX Protocol, which enables parachains to quickly have DEX functionality and share liquidity with other parachains. In addition, Zenlink DEX Aggregator can connect to all DEX DApps on Polkadot, which together form the Zenlink DEX Network with full liquidity.
For more information about Zenlink, please visit https://zenlink.pro/en/.
This bug bounty program is focused on their smart contracts and app and is focused on preventing:
- Any governance voting result manipulation
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
- Permanent freezing of funds
- Taking Down the application/website
- Redirection of user deposits and withdrawals
- Wallet interaction modification resulting in financial loss
KYC required
The submission of KYC information is a requirement 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.