RootstockLabs

RootstockLabs, previously IOVLabs, have been longstanding contributors to Rootstock, Bitcoin's DeFi layer. Launched in 2018, Rootstock allows anyone to develop apps and services on top of the planet's most secure and decentralized financial infrastructure; Bitcoin.

Today we continue to contribute to Rootstock's evolution by building tools and technology focused on scaling Bitcoin and making it work for everyone.

RootstockLabs is making Bitcoin work for everyone. We believe Bitcoin will play a crucial role in breaking down barriers to economic participation, providing the world's most secure and decentralized financial infrastructure to empower people everywhere to exercise their economic rights more fully.

Seamless payments without punitive charges for small businesses; savings that protect people from inflation; remittances that allow the ninety-nine percent to move capital as easily as the one; and loans that fuel grassroots economic growth—all denominated in stablecoins and available through the intuitive smartphone interfaces of today's Web2—this is what we call Everyday DeFi.

Rewards

RootstockLabs provides rewards in USDC on Ethereum, denominated in USD.

Rewards by Threat Level

Blockchain/DLT

• Critical: Max $200,000 / Min $10,000
• High: Max $10,000 / Min $5,000
• Medium: Max $5,000 / Min $2,500
• Low: Max $2,500 / Min $1,000

Smart Contract

• Critical: Max $100,000 / Min $10,000
• High: Max $10,000 / Min $5,000
• Medium: Flat $2,500
• Low: Flat $1,000

Websites and Applications

• Critical: Max $10,000 / Min $5,000
• High: Flat $2,500
• Medium: Flat $1,500
• Low: Flat $1,000

Critical Reward Calculation

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.

Final severity is determined by combining the potential impact of the vulnerability with the likelihood of successful exploitation. In assessing likelihood, we consider factors such as attacker motivation, the capital required (and whether it exceeds potential gains), and whether the exploit provides a direct benefit to the attacker.

For critical Blockchain/DLT bugs on HSM Firmware: The reward amount is 10% of the funds directly affected, capped at the maximum critical reward of USD 200,000. However, a minimum reward of USD 20,000 is to be rewarded in order to incentivize security researchers against withholding a bug report.

For critical Blockchain/DLT bugs on powpeg-node and rskj: The reward amount is 10% of the funds directly affected, capped at the maximum critical reward of USD 50,000. However, a minimum reward of USD 10,000 is to be rewarded in order to incentivize security researchers against withholding a bug report.

For critical Blockchain/DLT bugs with non-funds-at-risk impact:

• Total network shutdown (network not being able to confirm new transactions) via propagated/chained effect: USD $10,000

For critical smart contract bugs: The reward amount is 10% of the funds directly affected up to a maximum of USD 100,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.

For critical web/apps bugs: Reports will be rewarded with USD 10,000 only if the impact leads to:

• A loss of funds involving an attack that does not require any user action
• Private key or private key generation leakage leading to unauthorized access to user funds

All other impacts that would be classified as Critical would be rewarded a flat amount of USD 5,000.

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.
• The amount of funds at risk will be calculated with the impact of the first attack being at 100% and then a reduction of 25% from the amount of the first attack for every 150 blocks the attack needs for subsequent attacks from the first attack, rounded down.

High Level Reward Calculation

• For all High level bugs found on HSM Firmware: USD 10,000
• For High level bugs found on powpeg-node and rskj: USD 5,000

Medium Level Reward Calculation

• For all Medium level bugs found on HSM Firmware: USD 5,000
• For Medium level bugs found on powpeg-node and rskj: USD 2,500

Low Level Reward Calculation

• For all Low level bugs found on HSM Firmware: USD 2,500
• For Low level bugs found on powpeg-node and rskj: USD 1,000

Reward Payment Terms

Payouts are handled by the RootstockLabs team directly and are denominated in USD. However, payments are done in USDC on ETH.

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.

Program Details

Responsible Publication

RootstockLabs adheres to Category 2: Notice Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports.

Primacy of Impact vs Primacy of Rules

RootstockLabs adheres to the Primacy of Impact for the following impacts:

• Blockchain/DLT — Critical
• Blockchain/DLT — High
• Smart Contract — Critical
• Smart Contract — High
• Website & Application — Critical

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 (PoC) Requirements

A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules. Proof of concept is required for all severities.

Previous Audits

RootstockLabs's completed audit reports can be found at:

• http://rootstock.io/blog/rsk-security-audit-results/
• https://rootstock.io/blog/rsk-powhsm-is-now-open-source/

Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.

Known Issues

Smart Contract: False Positive Reports (Last Updated: 11 February 2026)

KYC Requirement

The submission of KYC information is a requirement for payout processing.

Participants must adhere to the Eligibility Criteria.

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
• Any other actions prohibited by the Immunefi Rules

Feasibility Limitations

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.

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.