
zkVerify
Bounty Range
$5,000 - $50,000
external program
zkVerify allows modular blockchain networks to offload the computationally heavy and expensive process of proof verification, enabling them to focus on their primary functions and stay ahead of their competition.
This modular approach not only streamlines operations but also significantly boosts overall network efficiency.
zkVerify provides rewards in USDC on Ethereum, denominated in USD.
Blockchain/DLT
Websites and Applications
For critical Blockchain/DLT bugs, the reward amount is 5% of the funds directly affected, capped at the maximum critical reward of $50,000. A minimum reward of USD $15,000 is to be rewarded in order to incentivize security researchers against withholding on a bug report.
For critical Blockchain/DLT bugs with a non-funds-at-risk impact, the reward will be paid out as follows:
For critical Blockchain/DLT bugs, the reward is dependent on the ratio between the funds at risk, which includes all affected projects on top of the respective blockchain/DLT, and the market cap according to the average between CoinMarketCap.com and CoinGecko.com, calculated at the time the bug report is submitted.
For critical web/apps bugs, reports will be rewarded with $10,000, only if the impact leads to:
All other impacts that would be classified as Critical would be rewarded a flat amount of $5,000. The rest of the severity levels are paid out according to the Impact in Scope table.
For high Blockchain/DLT non-funds-at-risk impacts, the reward will be paid out as follows:
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.
Participants must adhere to the Eligibility Criteria.
Category 3: Approval Required
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:
| Auditor | Link | Completed |
|---|---|---|
| Trail of Bits | https://github.com/trailofbits/publications/blob/master/reviews/2025-02-zkverify-foundation-blockchain-securityreview.pdf | 6 February 2025 |
| SRLabs | https://github.com/srlabs/audit-reports/blob/main/Polkadot/SRL-zkVerify_baseline_assurance-report-2025.pdf | 3 September 2025 |