Ampleforth

AMPL is the first rebasing currency and a key DeFi building block for denominating stable contracts. The AMPL protocol adjusts total supply daily based on market conditions, transferring volatility from price to supply. Like Bitcoin, AMPL’s elastic supply policy does not rely on traditional banks or lenders of last resort. Because of this unique approach, AMPL can be used as a true unit of account to denominate smart contracts.

The aAMPL token, a custom aToken on Aave, is planned to be entered into polling with the goal of being integrated into the Aave ecosystem, and was formally submitted as AIP37.

Further resources regarding Ampleforth can be found on their website, https://www.ampleforth.org/.

The bug bounty program is focused around its smart contracts and is mostly concerned with:

• The loss of user AMPL deposits
• Theft of unclaimed yield
• Freezing of AMPL on Aave for 1 hour or longer

This bug bounty program is is further secured by the Armor Alliance Bug Bounty Challenge.

Rewards 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.

Only vulnerabilities that are directly affecting aAMPL and the yield generated from aAMPL are considered under this bug bounty program. For example, if yield can be stolen from staking of other aTokens, they will not be considered for a reward.

Payouts up to USD 50 000 are handled by the Ampleforth team directly and are denominated in USD. However, payouts are done in ETH, USDT, USDC, or AMPL, at the discretion of the team. Payouts above that amount are covered by the Armor Alliance Bug Bounty Challenge and are paid in ARMOR with vesting of up to 24 months.

Vulnerabilities on Aave itself as well as natively on Ampleforth are not covered and are not accepted under this bug bounty program.

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.

Smart Contracts

• Theft of user AMPL deposits
• Theft of unclaimed yield
• Freezing of AMPL on Aave for 1 hour or longer

We are especially interested in receiving and rewarding vulnerabilities of the following types:

• Re-entrancy
• Logic errors
  • including user authentication errors
• Solidity/EVM details not considered
  • including integer over-/under-flow
  • including unhandled exceptions
• Trusting trust/dependency vulnerabilities
  • including composability vulnerabilities
• Oracle failure/manipulation
• Novel governance attacks
• Economic/financial attacks
  • including flash loan attacks
• Congestion and scalability
  • including running out of gas
  • including block stuffing
  • including susceptibility to frontrunning
• Consensus failures
• Cryptography problems
  • Signature malleability
  • Susceptibility to replay attacks
  • Weak randomness
  • Weak encryption
• Susceptibility to block timestamp manipulation
• Missing access controls / unprotected internal or debugging interfaces

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)
• 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