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 Exactly 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 consideration by the project. This only applies to Critical and High impacts.

Periphery Contracts have a reward cap equal to “High” (USD 25 000). This means that regardless of the complexity, impact, or exploitability of a potential vulnerability discovered within these contracts, the bounty paid out will not exceed that limit.

Exactly is a decentralized, non-custodial, and open-source protocol that provides an autonomous fixed and variable interest rate market enabling users to frictionlessly exchange the time value of their assets and complete the DeFi credit market.

Theft of unclaimed yield

Theft of unclaimed royalties

Permanent freezing of unclaimed yield

Permanent freezing of unclaimed royalties

Temporary freezing of funds for at least 4 hours

Substantial generation of bad debt on the protocol

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

Miner-extractable value (MEV)

Predictable or manipulable RNG that results in abuse of the principal

Protocol insolvency

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered in-scope, even if they affect something in the assets in the scope table.

Exactly Smart Contracts

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.

Audit Discoveries and Known Issues

Bug reports covering previously-discovered bugs are not eligible for any reward through the bug bounty program. If a bug report covers a known issue (e.g., the use of deprecated Chainlink API was reported in [EXA-36](https://github.com/exactly/audits/blob/main/Coinspect%204th%20audit%20(Oct-22).pdf)), it may be rejected together with proof of the issue being known before escalation of the bug report via Immunefi.

Previous audits and known issues can be found at: [https://docs.exact.ly/security/audits](https://docs.exact.ly/security/audits).

All High and Critical 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.

Critical smart contract vulnerabilities are capped at 10% 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 20 000__. 

KYC is required for this bug bounty program. Government identification, legal name, and country of residence will need to be supplied.

Payouts are handled by the __Exactly__ team directly and are denominated in USD. However, payouts are done in __USDC and DAI__, with the choice of the ratio at the team's discretion.

Exactly

Codebase