Alongside has created the first on-chain broad-based index for the crypto ecosystem- a single asset that tracks and benchmarks the cryptoasset market. It is a fully redeemable ERC-20 token (index token) that is backed one-to-one with in-kind assets included in the index.
For more information about Alongside, please visit Alongside
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, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
All web bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All High and Critical Smart Contract bug reports require a PoC to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.
Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 20 000.
Critical Websites and Applications are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 10 000, provided that there is a reasonable path to significant economic damage, determined at the discretion of the team.
Alongside requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is: Legal Name. The collection of this information will be done by the project team.
Payouts are handled by the Alongside team directly and are denominated in USD. However, payouts are done in USDC.
- USD $20,000 to USD $50,000
- USD $20,000
- USD $5,000
- USD $1,000
Websites and Applications
- USD $10,000 to USD $50,000
Assets in scope
- Smart Contract - ProxyAdminType
- Smart Contract - MembersType
- Smart Contract - IndexTokenProxyType
- Smart Contract - ControllerProxyType
- Smart Contract - FactoryProxyType
- Websites and Applications - API route only (amkt.batterylabs.io/api)Type
All smart contracts of Alongside can be found https://github.com/Alongside-Finance/amkt-contracts. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
Though only the proxy contracts are listed as in-scope, current implementation and any further updates to the implementation contracts are considered in scope. When reporting a bug, please make sure to select the relevant proxy smart contract as the target.
If an impact can be caused to any other asset managed by Alongside 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. This only applies to Critical and High impacts.
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.
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Protocol insolvencyCriticalImpact
- Unauthorized minting of AMKT tokensCriticalImpact
- Theft of unclaimed inflationHighImpact
- Permanent freezing of unclaimed inflationHighImpact
- Temporary freezing of funds for any amount of timeHighImpact
- Smart contract unable to operate due to lack of token fundsMediumImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Theft of gasMediumImpact
- Unbounded gas consumptionMediumImpact
- Contract fails to deliver promised returns, but doesn't lose valueLowImpact
Websites and Applications
- Stealing any API tokens that have write abilities to Coinbase Prime that results in loss of user fundsCriticalImpact
- Direct theft or loss of user fundsCriticalImpact
- Execute arbitrary system commandsCriticalImpact
- Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactionsCriticalImpact
- Subdomain takeover with already-connected wallet interactionCriticalImpact
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 (merchant, methodologist, custodian, etc)
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
- Centralization risks
Websites and Apps
- Theoretical vulnerabilities without any proof or demonstration
- Attacks requiring physical access to the victim device
- Attacks requiring access to the local network of the victim
- Reflected plain text injection ex: url parameters, path, etc.
- This does not exclude persistent plain text injection
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (ex: logout CSRF)
- Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
- Server-side non-confidential information disclosure such as IPs, server names, and most stack traces
- Vulnerabilities used only to enumerate or confirm the existence of users or tenants
- Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- DDoS vulnerabilities
- Feature requests
- Issues related to the frontend without concrete impact and PoC
- Best practices issues without concrete impact and PoC
- Vulnerabilities primarily caused by browser/plugin defects
- Vulnerabilities requiring non-latest version of Chrome or Firefox
- Vulnerabilities requiring non-Chrome or non-Firefox browsers
- Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
- Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass
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 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