Light Protocol
Bounty Range
$1,000 - $50,000
external program
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.
Light is a protocol built on Solana introducing ZK compression, a new primitive that enables the secure scaling of state directly on the L1.
Solana users and program developers can opt-in to compress their on-chain state via the Light Protocol smart contracts. This reduces state cost by orders of magnitude while preserving the security, performance, and composability of the Solana L1.
Light Protocol compressed state natively supports custom ZK compute. This creates a new space for previously impossible computation designs on Solana.
Off-Chain State Storage: State is stored off-chain, i.e., as calldata on the Solana ledger.
Transactions specify state: Transactions define the off-chain state they access (read/write) and include it in the transaction payload.
State Validation: Solana Programs invoke the light_system_program to create and update compressed state. The light_system_program validates the state (validity of read state via compressed-account schema, sum checks, ownership checks, verification of input state inclusion ZKP). Compressed accounts have a layout similar to classic accounts.
State Updates: The light_system_program invokes the account_compression_program which checks against double-spends and updates merkle trees. The new state is recorded as a log on the Solana ledger via the noop-program.
Photon RPC Nodes: index and persist the logs, making the compressed account state available to clients via the ZK Compression RPC API.
Forester nodes (cranks): Interact with the account compression program to empty nullifier_queues, empty address_queues, and roll-over trees.
Light Protocol provides rewards in USDC on Solana, denominated in USD.
Smart Contract - Critical
Smart Contract - High
Smart Contract - Medium
Smart Contract - Low
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $50,000. Minimum reward to discourage security researchers from withholding a bug report: $10,000.
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
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 $50,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 critical bug report.
Repeatable Attack Limitations
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk.
For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This is because the project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward.
Reward Calculation for High Level Reports
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties, as well as arbitrary creation/deletion/permanent freezing of state, are rewarded within a range of USD $5,000 to USD $10,000 depending on the funds at risk, capped at the maximum high reward.
In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lengthens, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature.
Reward Payment Terms
Payouts are handled by the service providers of Light Protocol directly and are denominated in USD. However, payments are done in USDC.
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.
Light Protocol will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
The submission of KYC information is a requirement for payout processing.
Light Protocol adheres to the Primacy of Impact for the following impacts:
Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope.
When submitting a report on Immunefi's dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi.
If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact.
All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms and conditions set within this program.
Proof of concept is always required for all severities.
Category 1: Transparent
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
Any other actions prohibited by the Immunefi Rules
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.
Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report: