All smart contracts of Eco can be found at [https://github.com/helix-foundation/currency](https://github.com/helix-foundation/currency) and [https://github.com/eco/ecox-lockup](https://github.com/eco/ecox-lockup). All the web/app of Eco can be found at [https://github.com/helix-foundation/eco-id-app](https://github.com/helix-foundation/eco-id-app) and [https://github.com/helix-foundation/eco-claim-dapp](https://github.com/helix-foundation/eco-claim-dapp). All of the bridge can be found at [https://github.com/eco-association/op-eco](https://github.com/eco-association/op-eco). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Though only the proxy contracts are listed as in-scope, current implementation and any further updates to the implementation contracts are considered in scope. When reporting a bug, please make sure to select the relevant proxy smart contract as the target. 

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

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.  

Any governance voting result manipulation

Permanent freezing of funds

Direct theft of any user NFTs, whether at-rest or in-motion, other than unclaimed royalties

Permanent freezing of unclaimed yield

Unauthorized minting of NFTs or tokens

Protocol insolvency

Execute arbitrary system commands

Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys(this does not include non-sensitive environment variables, open source code, or usernames)

Taking down the application/website

Taking down the NFT URI

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as, changing registration information, commenting, voting, making trades, withdrawals, etc.

Changing the NFT metadata

Subdomain takeover with already-connected wallet interaction

Direct theft of user funds

Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions

Direct theft of user NFTs

Injection of malicious HTML or XSS through NFT metadata

Theft of unclaimed yield

Theft of unclaimed fees / refunds

Temporary freezing of funds for at least 1 day

Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc.

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.

Improperly disclosing confidential user information such as email address, phone number, physical address, etc.

Subdomain takeover without already-connected wallet interaction

Smart contract unable to operate due to lack of token funds

Block stuffing for profit

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Theft of gas

Unbounded gas consumption

Changing non-sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as changing the first/last name of user, or en/disabling notification

Injecting/modifying the static content on the target application without Javascript (Reflected) such as reflected HTML injection or loading external site data

Redirecting users to malicious websites (Open Redirect)

Unintended alteration of what the NFT represents (e.g. token URI, payload, artistic content)

Smart contract fails to deliver promised returns, but doesn’t lose value

Changing details of other users (including modifying browser local storage) without already-connected wallet interaction and with significant user interaction such as iframing leading to modifying the backend/browser state (demonstrate impact with PoC)

Any impact involving a publicly released CVE without a working PoC

Taking over broken or expired outgoing links such as social media handles, etc.

Temporarily disabling user to access target site, such as locking up the victim from login, cookie bombing, etc.

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/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. 
    - [https://github.com/helix-foundation/currency](https://github.com/helix-foundation/currency)
    - [https://github.com/helix-foundation/eco-claim](https://github.com/helix-foundation/eco-claim)
    - [https://github.com/helix-foundation/eco-id](https://github.com/helix-foundation/eco-id)
    - [https://github.com/eco/ecox-lockup](https://github.com/eco/ecox-lockup)
    - [https://github.com/eco-association/op-eco](https://github.com/eco-association/op-eco)
   - 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](https://github.com/eco-association/op-eco) repository. 

The Eco Association requires an affidavit that the bug bounty hunter is not from a [sanctioned](https://home.treasury.gov/policy-issues/financial-sanctions/sanctions-programs-and-country-information) 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__.

Eco

Resources & Documentation