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
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the 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.
All bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required. All bug reports must also come with a suggestion for a fix in order to be considered for a reward.
Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of USD 30 000 and a maximum reward of USD 500 000.
The Liquidswap team requires KYC to be done for all bug bounty hunters submitting a Critical severity report and wanting a reward. The information needed is a National ID photo along with a utility bill for proof of residency.
Known issues previously highlighted in the following audit reports are considered out of scope:
- OtterSec - Website
- Halborn - General
- Halborn - Flashloan
- Halborn - Dynamic Fees and Config
- Zellic - Liquidswap
The team is aware of an issue causing LP burn to be aborted in wildly lopsided pools. There is also an overflow bug in the v1 router that has already been resolved. Bug reports related to these issues would be considered out of scope.
Payouts are handled by the Liquidswap team directly and are denominated in USD. However, payouts are done in USDC (ERC20) or USDT (ERC20), at the discretion of the team.
Program Overview
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.
For more information about Liquidswap, please visit https://pontem.network/liquidswap.
KYC required
The submission of KYC information is a requirement for payout processing.
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- Any testing with pricing oracles or third-party smart contracts
- Attempting phishing or other social engineering attacks against our employees and/or customers
- Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
- Any denial of service attacks that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
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 to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.