Stargate is a composable crosschain liquidity protocol, and the first application built on LayerZero.
ETH
Arbitrum
Solana
Aptos
Avalanche
Base
Blast
BSC
Fantom
Fraxtal
Fuse
Horizen EON
Injective
Kava
Linea
Manta
Mantle
Moonbeam
Metis
Optimism
Maximum Bounty
$3,500,000Live Since
24 September 2024Last Updated
29 October 2026Triaged by Immunefi
PoC Required
KYC required
Arbitration enabled
Select the category you'd like to explore
Assets in Scope
Target
Primacy Of Impact
Name
Added on
10 November 2025
Impacts in Scope
Severity
Critical
Title
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Severity
Critical
Title
Permanent freezing of funds
Severity
Critical
Title
Protocol insolvency
Severity
Medium
Title
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Out of scope
Program's Out of Scope information
- LayerZero Offchain Infrastructure
- Sybil Attacks
- Impacts to assets as a result of their own misconfiguration
- Impacts as a result of a chain-level issue
- Reports regarding bugs that LayerZero was previously aware of are not eligible for a reward
- Dependencies & Third Party Code
- Temporary impacts resulting from configuration adjustment race-conditions
Previous Audits
Stargate’s completed audit reports can be found at https://stargateprotocol.gitbook.io/stargate/v2-developer-docs/security/audit. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
Default Out of Scope and rules
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers