Liquidswap
Liquidswap is the first AMM exchange for volatile and stable pairs on Aptos. Built by Aptos-backed Pontem, it has feature parity with both Uniswap and Curve using various bonding curves to enable liquidity providers and traders to swap assets. Liquidswap is audited by Ottersec, Halborn and Zellic. Token economic is audit coming soon.
PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct theft of any user funds or liquidity, or company funds (fees)
Permanent freezing of funds in more than one pool
DoS or similar which prevents users from swapping/flashloan
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 (not including DDOS/DOS).
Direct theft of user funds.
XSS with ability to run users' transactions or change pricing, or etc, in nutshell what leads to funds lost.
Permanent freezing of funds of one pool
Subdomain takeover without already-connected wallet interaction
Redirecting users to malicious websites (Open Redirect).
Indirect theft of any user funds via economic attack vectors or periphery issues like routers or scripts (excluding minor rounding errors)
Out of scope
- Issues related to the frontend without concrete impact and PoC
- Best practices issues without concrete impact and PoC
- Best practice critiques
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