eckoDEX
eckoDEX is a DEX built on Kadena, the only sharded and scalable layer-1 PoW public network. Kadena solves the scaling challenges of Bitcoin and the security issues of Ethereum. eckoDEX Allows for fantastic passive rewards, security, and so much more.
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. Explanations and statements are not accepted as PoC and code is required.
All vulnerabilities marked in the NCC Group security review are not eligible for a reward.
Payouts are handled by the eckoDAO team directly and are denominated in USDT. Payouts are done in USDT, first payout at 25% of bounty value, with the remainder USDC vested over 1 year. 25% - Day 0 | 50% Month 4 | 75% Month 8 | 100% Month 12
Program Overview
eckoDEX is a DEX built on Kadena, the only sharded and scalable layer-1 PoW public network. Kadena solves the scaling challenges of Bitcoin and the security issues of Ethereum. eckoDEX Allows for fantastic passive rewards, security, and so much more.
For more information about eckoDEX, please visit https://dex.ecko.finance/.
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.