Nomad-logo

Nomad

Nomad is a security-first cross-chain messaging protocol that enables seamless communication between blockchains. By leveraging an optimistic mechanism, Nomad only requires one honest actor to keep the entire system safe. This drastically reduces the trust required relative to other interoperability solutions.

Avalanche
ETH
Gnosis
Moonbeam
Infrastructure
Bridge
DAO
Solidity
Maximum Bounty
$1,000,000
Live Since
09 June 2022
Last Updated
08 April 2024
  • PoC required

  • KYC required

Rewards

Nomad provides rewards in USDC on Ethereum, Avalanche, denominated in USD.

Rewards by Threat Level

Smart Contract
Critical
USD $10,000 - $100,000
High
USD $1,000 - $10,000

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

For critical Blockchain/DLT bugs, the reward will be determined based on the funds at risk, and may also consider subsequent impacts on other projects built on the respective blockchain, as well as PR and brand reputation risk, capped at the maximum critical reward.

To incentivize security researchers and ensure bug reports are not withheld, a minimum reward USD 10 000 will be provided.

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 bug report.

Repeatable Attack Limitations

  • If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attacks within the first hour 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 can not 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

  • In the event of temporary freezing, the reward increases at a multiplier of two 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 lenghents, 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 Nomad team directly and are denominated in USD. However, payouts 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.

Program Overview

Nomad is a security-first cross-chain messaging protocol that enables seamless communication between blockchains. By leveraging an optimistic mechanism, Nomad only requires one honest actor to keep the entire system safe. This drastically reduces the trust required relative to other interoperability solutions.

Nomad enables generalized messaging passing between chains, so developers can build cross-chain applications (or xApps) that compose logic and smart contract calls between chains, natively.

For more information about Nomad, please visit https://www.nomad.xyz/.

KYC Requirement

Nomad will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:

  • Full name
  • Date of birth
  • Proof of address (either a redacted bank statement with address or a recent utility bill)
  • Copy of Passport or other Government issued ID

Security researchers must pass OFAC screening and cannot be on the SDN list.

Responsible Publication

Nomad adheres to category 3 - Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.

Primacy of Impact vs Primacy of Rules

Nomad adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms stated in this page.

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.

Known Issue Assurance

Nomad commits to providing Known Issue Assurance to bug submissions through their program. This means that Nomad will either disclose known issues publicly or at the very least privately via a self-reported bug submission.

In scenarios where there might be a mediation, this allows for a more objective and streamlined process to prove that an issue is known. Otherwise, assuming the bug report is valid, it would result in the report being considered as in-scope, and due a reward.

Previous Audits

All Nomad’s completed audit reports can be found here: https://docs.nomad.xyz/operational-security/audits. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.

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.

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.

Immunefi Standard Badge

By adhering to Immunefi’s best practice recommendations, Nomad has satisfied the requirements for the Immunefi Standard Badge

KYC required

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

Proof of Concept

Proof of concept is always required for all severities.

Responsible Publication

Category 3: Approval Required

Prohibited Activities

Default 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. 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.