Charm
Charm’s Alpha Vaults creates permissionless vaults to manage Uniswap liquidity. It uses Charm’s expertise in Decentralized Market Making Strategies to help anyone increase the liquidity of any Uniswap V3 pool. Using the vault, anyone can launch liquidity mining campaigns just like Uniswap V2, have full control over the vault’s strategy, increase token liquidity using concentrated liquidity, guarantee tokens will always be tradable, and achieve full decentralization.
PoC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$20,000Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.
Payouts are handled by the Charm team directly and are denominated in USD. However, payouts are done in ETH or USDC.
Program Overview
Charm’s Alpha Vaults creates permissionless vaults to manage Uniswap liquidity. It uses Charm’s expertise in Decentralized Market Making Strategies to help anyone increase the liquidity of any Uniswap V3 pool. Using the vault, anyone can launch liquidity mining campaigns just like Uniswap V2, have full control over the vault’s strategy, increase token liquidity using concentrated liquidity, guarantee tokens will always be tradable, and achieve full decentralization. In addition, the vault’s shares are tokenized and ERC-20 compliant, which means LPs can deposit, withdraw, earn yield, and stake just like regular tokens.
The core contracts of Alpha Vaults version 2 are included within the scope of this bug bounty program.
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
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.