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.
Solana
Infrastructure
Zero-Knowledge Proofs
Maximum Bounty
$50,000Live Since
12 September 2024Last Updated
16 September 2024Triaged by Immunefi
PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Severity
Critical
Title
Direct theft of any user funds, whether at-rest or in-motion
Severity
Critical
Title
Permanent freezing of state
Severity
Critical
Title
Permanent freezing of compressed tokens/sol
Severity
Critical
Title
Unauthorized minting of compressed tokens/sol
Severity
Critical
Title
Arbitrary creation or deletion of state
Severity
High
Title
Temporary freezing of state
Severity
Medium
Title
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Severity
Low
Title
Contract fails to deliver promised returns, but doesn't lose value
Out of scope
Program's Out of Scope information
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 such as the reference indexed Merkle tree.
These impacts are out of scope for this bug bounty program.
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 (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
- 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
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
Prohibited Activities:
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- Any testing with pricing oracles or third-party smart contracts
- Attempting phishing or other social engineering attacks against our employees and/or 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 that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty