All code of Euphrates can be found at [https://github.com/AcalaNetwork/Euphrates.](https://github.com/AcalaNetwork/Euphrates) Documentation for the assets provided in the table can be found at [https://farmdoc.acala.network/euphrates/readme. ](https://farmdoc.acala.network/euphrates/readme) 

Euphrates allows stakers and liquidity providers of LSTs (liquid staking tokens) to earn boosted rewards in ACA as well as participating project tokens with minimum effort.

Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results

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

Permanent freezing of funds

Protocol insolvency

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Permanent freezing of unclaimed royalties

Temporary freezing of funds

Smart contract unable to operate due to lack of token funds

Block stuffing

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

Theft of gas

Unbounded gas consumption

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below. 

__Reward Calculation for Critical Level Reports__

For critical Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 50,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 10,000 is to be rewarded in order to incentivize security researchers against withholding a bug report.   

__Reward Calculation for High Level Reports__

High smart contract vulnerabilities will be capped at up to 10% of the funds affected. up to the hard cap of USD 10,000. However, a minimum reward of USD 2,000 is to be rewarded in order to incentivize security researchers against withholding a bug report.   

__Previous Audits__

Euphrates has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
- [https://github.com/AcalaNetwork/Euphrates/blob/master/audit/PeckShield-Audit-Report-Acala-Euphrates-v1.0.pdf](https://github.com/AcalaNetwork/Euphrates/blob/master/audit/PeckShield-Audit-Report-Acala-Euphrates-v1.0.pdf) 

__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, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bugs severity.
- Therefore, Immunefi has developed a set of [feasibility limitation standards ](https://immunefisupport.zendesk.com/hc/en-us/articles/16913132495377-Feasibility-Limitation-Standards)which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.

__Proof of Concept (PoC) Requirements__

A PoC is required for the following severity levels:
- Smart Contract, Critical
- Smart Contract, High
- Smart Contract, Medium

All PoCs submitted must comply with the Immunefi-wide [PoC Guidelines and Rules.](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules) Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

__Reward Payment Terms__

Payouts are handled by the Euphrates team directly and are denominated in USD. However, payments are done in USDC.


Euphrates

Resources & Documentation