Econia Labs’ codebase can be found at [https://github.com/econia-labs.](https://github.com/econia-labs) Documentation and further resources can be found on [https://econia.dev/. ](https://econia.dev/)

__Vulnerability notes__

In general, vulnerability bounties are centered around the major topics of insolvency, memory corruption, and accounting errors. Econia order books are designed around a custom data structure, the AVL queue, as described here: [https://econia.dev/overview/orders.](https://econia.dev/overview/orders) Global orders are also duplicated for each user at the market account level, as described here: [https://econia.dev/overview/market-accounts.](https://econia.dev/overview/market-accounts) The matching engine manipulates state at both levels, as described here: [https://econia.dev/overview/matching.](https://econia.dev/overview/matching) Errors at any one of these levels could result in a critical impact, whether in the form of accounting errors, a locked order book, a user being unable to withdraw funds, etc., and such issues are of primary impact.

Econia is a back-end settlement layer built on Aptos's Block-STM execution engine. Econia's Move-native codebase leverages Aptos for composability and parallelism, providing integrating protocols and market makers with a suite of extensible features. Built by developers, for developers, and with developer feedback, Econia unlocks the base layer of Aptos DeFi.

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

Permanent freezing of funds

Protocol insolvency

AVL queue memory leak or pointer arithmetic error resulting in corrupted state that adversely affects smart contract functionality, where user is unable to cancel affected order

Market account access key memory leak or pointer arithmetic error resulting in corrupted state that adversely affects smart contract functionality, where user is unable to cancel affected order

Matching or order placement operation that results in an accounting error

Operation resulting in a locked order book that will not process trades, where user can’t get funds out

Temporary freezing of funds

AVL queue memory leak or pointer arithmetic error resulting in corrupted state that adversely affects smart contract functionality, where user is able to cancel affected order

Market account access key memory leak or pointer arithmetic error resulting in corrupted state that adversely affects smart contract functionality, where user is able to cancel affected order

Operation resulting in a locked order book that will not process trades, where user can get funds out

Smart contract unable to operate due to lack of token funds

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

Theft of gas

Incorrect emission of events as defined at: https://econia.dev/off-chain/events

Contract fails to deliver promised returns, but doesn't lose value

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.3. ](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-3/)

__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 100 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 25 000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.

__Repeatable Attack Limitations__

If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attacks within the first hour will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk. 

For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This is because the project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward. 

__Reward Calculation for High Level Reports__

High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are considered at the full amount of funds at risk, capped at the maximum high reward. This is to incentivize security researchers to uncover and responsibly disclose vulnerabilities that may have not have significant monetary value today, but could still be damaging to the project if it goes unaddressed.   

In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lenghents, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature.

__Reward Payment Terms__

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

The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.

Econia

Resources & Documentation