Angle is an over-collateralized, decentralized and capital-efficient stablecoin protocol.
It can be used to issue stablecoins, called agTokens, that are pegged to a specific value. This means that these tokens are designed to mirror the value of the asset they are pegged to.
Angle has started with agEUR, a Euro (EUR - €) stablecoin on Ethereum mainnet.
On top of its stablecoin product, Angle protocol also offers to its users ways to:
- Trade perpetual futures
- Earn yield from strategies
- Get leverage on a wide range of assets
- Precisely speaking, the protocol consists of several different modules, or set of smart contracts, from which agTokens can be issued or minted. While Angle was launched with a single minting module (the Core module), a Borrowing module allowing to borrow Angle stablecoins against deposited collateral has been introduced
For more information about Angle Protocol, please visit https://www.angle.money/.
This bug bounty program is focused on their smart contracts and is focused on preventing:
- Thefts and freezing of principal of any amount
- Thefts and freezing of unclaimed yield of any amount
- Theft of governance funds
- Governance activity disruption
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 and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.
All Critical Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. All High and Medium Smart Contract bug reports require a PoC to be eligible for a reward.
Vulnerabilities marked as “Acknowledged”, “ Accepted Risk” or “Closed” in the ChainSecurity security review from July 2021, the Sigma Prime security review from July 21, the ChainSecurity security review from December 2021, the ChainSecurity security review from April 22 are not eligible for a reward.
Critical-level smart contract vulnerabilities that result in the loss of user funds will have rewards additionally capped at 10% of the funds potentially affected based on the vulnerability that was identified. These rewards are payable in USDC or in ANGLE at the discretion of the team. ANGLE rewards will have a vesting schedule lasting between 6-12 months with a minimum of 6 months for rewards up to USD 200 000, with an additional month added for every USD 50 000 tranche, rounded up. However, there is a minimum of USD 50 000 for Critical bug reports.
Payouts are handled by the Angle Protocol team directly and are denominated in USD. However, payouts are done in ANGLE or USDC, with the choice of the ratio at the discretion of the team.
- Up to USD $500,000
- USD $20,000
- USD $2,500
Assets in scope
- Smart Contract - AgTokenType
- Smart Contract - CoreType
- Smart Contract - ANGLEType
- Smart Contract - Fee ManagerType
- Smart Contract - Generic AaveType
- Smart Contract - Generic CompoundType
- Smart Contract - Oracle DAIType
- Smart Contract - Perpetual Manager FrontType
- Smart Contract - Pool ManagerType
- Smart Contract - San TokenType
- Smart Contract - Optimizer APR StrategyType
- Smart Contract - Stable Master FrontType
- Smart Contract - AngleDistributorType
- Smart Contract - LiquidityGaugeV4Type
- Smart Contract - SurplusConverterSanTokensType
- Smart Contract - SurplusConverterUniV3Type
- Smart Contract - GaugeControllerType
- Smart Contract - veANGLEType
- Smart Contract - FlashAngleType
- Smart Contract - AngleRouterType
- Smart Contract - Aave Folding StrategyType
- Smart Contract - GenericAaveFraxConvexStakerType
- Smart Contract - stETH StrategyType
- Smart Contract - TreasuryType
- Smart Contract - CoreBorrowType
- Smart Contract - VaultManagerType
- Smart Contract - Oracle Borrow ModuleType
All smart contracts of Angle Protocol can be found in the following repositories
- https://github.com/AngleProtocol/angle-core: for the Core module and the governance smart contracts.
- https://github.com/AngleProtocol/angle-borrow: for the Borrowing module smart contracts
- https://github.com/AngleProtocol/angle-strategies: for the smart contracts linked to the yield strategies of the protocol
However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
Some of the contracts in scope are upgradeable and you’ll see proxies at the given addresses, make sure to look at the corresponding implementation.
Impacts in scope
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.
- Any governance voting result manipulationCriticalImpact
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Protocol InsolvencyCriticalImpact
- Miner-extractable value (MEV)CriticalImpact
- Theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Temporary freezing of fundsHighImpact
- Smart contract unable to operate due to lack of token fundsMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Block stuffing for profitMediumImpact
- Unbounded gas consumptionMediumImpact
- Theft of gasMediumImpact
Out of Scope & Rules
The following vulnerabilities are excluded from the rewards for this bug bounty program:
- Attacks that the reporter has already exploited themselves, leading to damage
- Attacks requiring access to leaked keys/credentials
- Attacks requiring access to privileged addresses (governance, strategist)
Smart Contracts and Blockchain
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Basic economic governance attacks (e.g. 51% attack)
- Lack of liquidity
- Best practice critiques
- Sybil attacks
The following activities are prohibited by this bug bounty program:
- Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
- 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
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty