AMKT is a fully backed market index, providing exposure to a market-cap weighted basket of assets, to be reconstituted quarterly.

Permanent freezing of funds

Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results

Temporary freezing of funds

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

Protocol insolvency

Alongside Codebase

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below. 

__Reward Calculation for Critical Level Reports__

For critical Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 150,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 10,000 is to be rewarded in order to incentivize security researchers against withholding a bug report.   
__Reward Calculation for High Level Reports__

High smart contract vulnerabilities will be capped at up to 100% of the funds affected. In the event of temporary freezing and permanent freezing of funds, the reward doubles for every additional 300  blocks that the funds or NFTs could be temporarily frozen, rounded down to the nearest multiple of 300, up to the hard cap of USD 10,000. However, a minimum reward of USD 2,500 is to be rewarded in order to incentivize security researchers against withholding a bug report. For “Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results” impact, a fixed reward of USD 10,000 will apply.  

__Public Disclosure of Known Issues__

Bug reports covering previously-discovered bugs acknowledged below are not eligible for any reward through the bug bounty program. 
- Cannot Support atypical ERC20s
- Trusted Authority Role (Timelock)
- Trusted Authority Role (Multisig)
- Trusted Authority Role (Emergency Responder)
- Trusted Bounty Poster / Oracle
- Assumes Bounty has been checked for correctness: duplicates/includes all underlying
- Rebalance will have some slippage because of the delay in computing the nominals and it being fulfilled. This means if the price of the tokens going out are less than the price of the tokens going in, it's on the person fulfilling the bounty to cover this. In other words this trade may not easily be profitable. 
- Governance has not executed any proposals yet, including the one to accept ownership of vault. This can be ignored. 
- Rounding in tryInflation will cause drift between vault balance and nominal calculation
- tryInflation can be sandwiched to skirt fees (or profit, if there are AMKT lending markets)
- AMKT is limited as a governance token, creating centralization risks for users
- Ownership transfer risks in migration process
- Delay in rebalancing process could lead to exploitation
- Protocol governance initially has low token delegation
- Bounty fulfillments may arbitrarily update the precision of the total basket of tokens
- setInflationRate will apply the rate retroactively

__Previous Audits__

Alongside has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
- [https://github.com/Alongside-Finance/Audits/blob/main/Solidified_April_22.pdf ](https://github.com/Alongside-Finance/Audits/blob/main/Solidified_April_22.pdf)
- [https://github.com/Alongside-Finance/Audits/blob/main/SigmaPrime_Sept_28.pdf ](https://github.com/Alongside-Finance/Audits/blob/main/SigmaPrime_Sept_28.pdf)
- [https://github.com/zobront/audits/blob/main/reports/alongside.md ](https://github.com/zobront/audits/blob/main/reports/alongside.md)
- [https://github.com/Alongside-Finance/Audits/blob/main/Cantina.pdf ](https://github.com/Alongside-Finance/Audits/blob/main/Cantina.pdf)
- [https://github.com/Alongside-Finance/Audits/blob/main/Cantina-2.pdf](https://github.com/Alongside-Finance/Audits/blob/main/Cantina-2.pdf)


__Proof of Concept (PoC) Requirements__

A PoC is required for the following severity levels:
- Smart Contract, Critical
- Smart Contract, High

All PoCs submitted must comply with the Immunefi-wide [PoC Guidelines and Rules.](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules) Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

__Reward Payment Terms__

Payouts are handled by the Alongside team directly and are denominated in USD. However, payments are done in USDC  and AMKT. The payout ratio will be 50% in USDC and 50% in AMKT.

The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability. For avoidance of doubt, if the reward amount is USD 5 000 and the average price is USD 1.75 per token, then the reward will be 2857.142857 units of that token.