CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
Mintlayer logo
Mintlayer
DeFi
Infrastructure
L2 Scaling
Max Payout
$20,000
Project Overview

We’re launching a bug bounty program with Certik for zkThunder, our new zero-knowledge rollup testnet on the Mintlayer network.

This program invites security researchers to identify vulnerabilities in the zkThunder architecture, including its infrastructure, consensus layer, zero-knowledge components, and the smart contracts essential to the network’s operation (excluding user-deployed contracts).

Rewards in ML tokens will be granted based on severity and impact. Help us secure zkThunder before mainnet launch — your expertise is essential to strengthening Bitcoin-native scalability.

Rewards by Severity

Program Overview Mintlayer, in partnership with CertiK, has launched a bug bounty program for zkThunder—its zero-knowledge rollup testnet designed to enhance Bitcoin-native scalability. This initiative aims to identify and mitigate security vulnerabilities within the zkThunder architecture before mainnet deployment. Security researchers are invited to investigate core components, including the consensus layer, infrastructure, zero-knowledge logic, and protocol-level smart contracts. Please note that user-deployed contracts are out of scope.

Reward Structure All submissions are assessed using a 4-tier severity model, with rewards based on the severity and potential impact of each finding. Higher-tier rewards are reserved for vulnerabilities affecting network stability, fund security, or the integrity of core zk components. Rewards are granted at the discretion of the Mintlayer team based on internal evaluation and severity classification.

Submission Requirements Bug reports must include a complete proof of concept (PoC) along with step-by-step instructions demonstrating the vulnerability's real-world impact on in-scope components. Reports that do not include executable code or fail to show end-effect on the network will not qualify for rewards.

Payouts Rewards are denominated in USD-equivalent value and paid in ML, Mintlayer’s native token. All payouts are handled directly by the Mintlayer team after successful validation and KYC compliance.

Smart Contract
The bounty will be paid out in ML
Assets In-Scope
Target
Severity
Name
https://github.com/mintlayer/zk-thunder
Smart Contract
ZkThunder network
In-Scope Vulnerabilities
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered in-scope, even if they affect something in the assets in scope table.
Smart Contract
Critical
Network not being able to confirm new transactions (Total network shutdown)
Unintended permanent chain split requiring hard fork
Permanent freezing of funds(fix requires hard fork)
Transaction/consensus manipulation
Unauthorized token minting
Major
Unintended chain split (fix not requiring hard fork)
Transient consensus failures
Bad/incorrect usage of cryptography primitives
Medium
High compute consumption by validator/mining nodes
Vulnerability in RPC API (except via DDoS attack)
Unhandled on-chain errors affecting a user corner case
Low
Underpricing transaction fees relative to computation time
Griefing (e.g. triggering abnormally high gas fees for everyone or abnormal cpu consumption for validator/mining nodes)
Out-Of-Scope Vulnerabilities
The following vulnerabilities are excluded from the rewards for this bug bounty program:
  • Vulnerabilities that have already been exploited
  • Centralization-related vulnerabilities related to: private keys, privileged addresses, governance, credentials, etc.
Smart Contract
Centralization risks
Best practice critiques
Program Rules
  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue - the issue will not be eligible for a reward.
  • Submit one vulnerability per report - unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur we only award the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • Make a good faith effort to avoid privacy violations - destruction of data - and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
  • Do not attempt to conduct post-exploitation including modification or destruction of data - and interruption or degradation of services.
  • Do not attempt to perform brute-force attacks or denial-of-service attacks., Do not attempt to target employees or customers including social engineering attacks - phishing attacks or physical attacks.
The following activities are prohibited by this bug bounty program:
  • Any testing with mainnet or public testnet contracts, all testing should be done on private testnets.
  • Automated testing of services that generate significant amounts of traffic.
  • Public disclosure of an unpatched vulnerability in an embargoed bounty.
  • Social engineering (e.g. phishing, vishing, smishing) of any kind.
FAQs
How do I search for active bounties?
A: Active bounties can be viewed here [CertiK URL], and by filtering for bounties on the Security Leaderboard. Projects will post bounties along with the assets in the scope of the bounties with a corresponding bounty reward.
How do I submit a bounty?
To submit a bug report, first register an account with us https://www.certik.com/auth/signup. Once your account is created, you can log in and select “Submit Bug” for the specific bounties you're interested in. You will be prompted to fill out a webform; follow the instructions and upon successful submission, you will receive an email confirmation with a reference ID.
Who do I contact if I'm having trouble with my bug report submission?
You can reach out to bugbounty@certik.com for updates and assistance with your bug bounty submission.
I submitted my bug report. What now?
Once your bug report is submitted, CertiK will evaluate the report and contact the respective project. Depending on the criteria stated within a bug bounty, a KYC may be required. With valid bug reports, you will be contacted to begin the process of evaluating the bug with the project.
How is KYC handled?
CertiK has a team of investigative professionals that will handle any needed KYC services for bug bounty submissions requiring KYC.
Why was my bug report submission rejected?
A description of dismissal will be available for any bug bounty that is rejected.
The project is being slow responding to my bug report. What are their required response times / SLAs?
There can be multiple bug bounty submissions therefore there might be some delay in process times.
How do payouts work?
Payments for successful bug bounties will be communicated directly via the project wherein wallet information can be exchanged.
Bounty Highlights
Assets in Scope1
Live SinceApr 1, 2025
Last Updated3mo 11d ago
Funds Reserved$20,000
Max Payout$20,000
Skynet Score
86.25
A
KYC
Required
PoC
Required
View on Skynet