Econia
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.
PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
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
Out of scope
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers