All smart contracts of SPOT can be found at [https://github.com/ampleforth/spot/tree/main/spot-contracts](https://github.com/ampleforth/spot/tree/main/spot-contracts). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Known issues highlighted in the following audit reports are considered out of scope: 

- [https://github.com/ampleforth/ampleforth-audits/tree/master/spot/v1.0.0](https://github.com/ampleforth/ampleforth-audits/tree/master/spot/v1.0.0)

The following known issues are also considered out of scope of this program: 

- MEV around rebases
- Insolvency

If an impact can be caused to any other asset managed by SPOT that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. 


SPOT is a perpetual note backed by fully collateralized AMPL derivatives. SPOT can fulfill many properties of modern day stablecoins but is not pegged to any particular value. Its price will likely float within a range similar to AMPL and you can think of SPOT as a derivative that strips away most of AMPL's supply volatility.

Any governance voting result manipulation

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Predictable or manipulable RNG that results in abuse of the principal

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

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as, changing registration information, commenting, voting, making trades, withdrawals, etc.

Subdomain takeover with already-connected wallet interaction

Direct theft of user funds

Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions

Injection of malicious HTML or XSS through NFT metadata

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Temporary freezing of funds

Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc.

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.

Improperly disclosing confidential user information such as email address, phone number, physical address, etc.

Subdomain takeover without already-connected wallet interaction

Smart contract unable to operate due to lack of token funds

Block stuffing for profit

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Theft of gas

Unbounded gas consumption

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/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 web/app 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.

Payouts are handled by the __SPOT__ team directly and are denominated in USD. However, payouts are done in __AMPL, SPOT, ETH, USDC__, or __USDT__ at the choice of the whitehat.


SPOT

Resources & Documentation