Light Protocol
Light Protocol introduces ZK Compression, a new primitive designed to scale Solana’s L1 while maintaining security and performance. It delivers significant cost savings for developers, addresses the problem of state growth, and provides a foundation for native ZK compute on Solana.
Triaged by Immunefi
PoC required
KYC required
Arbitration enabled
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Arbitrary creation or deletion of state
Unauthorized minting of compressed tokens/sol
Permanent freezing of compressed tokens/sol
Permanent freezing of state
Temporary freezing of state
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Contract fails to deliver promised returns, but doesn't lose value
Out of scope
From the assets listed above, only the latest releases are in scope. The latest main on https://github.com/Lightprotocol/light-protocol is not automatically in scope. Make sure the asset’s commit hash you review matches the commit hash of the Light Programs in the resources section.
These assets are out of scope for this bug bounty program: client side libraries, sdks, cli, server, tests, test-utilities or code only used for testing.
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