Eco
The Eco Currency is intended to serve as a decentralized alternative to fiat currencies. Other cryptocurrencies either fix their monetary policies and admit exchange rate volatility, or attempt to limit volatility and achieve dollar parity through various policies.
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 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 Smart Contract bug reports require a PoC to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.
Smart Contracts
Critical smart contract vulnerabilities are capped at 5% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects and market liquidity, at the discretion of the team. However, there is a minimum reward of USD 25 000, unless the bug falls under the “Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield or fees/refunds” category, in which case the 10% cap still applies.
High smart contract vulnerabilities are capped at 100% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 5 000 and a maximum reward of USD 25 000 regardless of the economic damage.
Websites and Applications
Critical website and application bug reports will be rewarded with USD 50 000 only if the impact leads to a direct loss in funds or a manipulation of the votes or the voting result. All other impacts that would be classified as Critical would be rewarded USD 25 000
Bridge Contracts Critical smart contract vulnerabilities are capped at 5% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects and market liquidity, at the discretion of the team. However, there is a minimum reward of USD 10 000.
High smart contract vulnerabilities are capped at 100% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 2 000 and a maximum reward of USD 5 000 regardless of the economic damage.
The reward structure listed below applies only to the following Bridge Contracts:
- L1ECOBridge.sol
- L2ECOBridge.sol
- L2ECO.sol
| Severity | Reward |
|---|---|
| Critical | USD $10,000 to USD $25,000 |
| High | USD $2,000 to USD $5,000 |
| Medium | USD $1,000 |
The following vulnerabilities are not eligible for a reward:
- All vulnerabilities mentioned in the audits in the relevant repos for each contract.
- Any vulnerabilities that are vulnerabilities in the Bridge Contracts that arise from a bug in the core Optimism Contracts or Bridge Application, including to, but not limited to, the Optimism Blockchain, the L1Messenger, etc. are not eligible for a reward. The bug in the bridge contracts MUST arise from a code issue in the https://github.com/eco-association/op-eco repository.
The Eco Association requires an affidavit that the bug bounty hunter is not from a sanctioned county or a sanctioned entity. The collection of this information will be done by the Eco Association.
Payouts are handled by the Eco Association directly and are denominated in USD. However, payouts are done in USDC.
Program Overview
The Eco Currency is intended to serve as a decentralized alternative to fiat currencies. Other cryptocurrencies either fix their monetary policies and admit exchange rate volatility, or attempt to limit volatility and achieve dollar parity through various policies.
Eco does not treat dollar-parity as a proxy for utility. Eco is a free-floating currency designed to achieve its aims through monetary policy transparently established and managed by a representative group of governing “Trustees” who are elected by the community of Eco holders. Trustees have one core mandate: to maximize the wealth held in ECO. As with many other token systems, Eco currency holders are also empowered to vote on community proposals and protocol upgrades.
Eco features two tokens: the variable supply base currency (ECO), and a deflationary supply token (ECOx) intended to incentivize long-term holders and bootstrap an open market signaling expectations for ECO adoption. These tokens, together with the various contracts and components that support them, form the Eco Currency Protocol.
This bug bounty covers the following core components and peripherals:
- The core Eco Protocol contracts
- The ECO NFT and ECO Claim contracts
- All associated dApp
- ECO ID dApp
- ECO claim dApp
For more information about Eco, please visit https://eco.org/.
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.