Nodle

Impacts only apply to assets in active use by the project like contracts on mainnet or web/app assets used in production. Any impact that applies to assets not in active use, like test or mock files, are out-of-scope of the bounty program unless explicitly mentioned as in-scope.

Blockchain/DLT

• Blockchain/DLT - PoC, Blockchain/DLT vulnerability reports are to include a runnable Proof of Concept (PoC) in order to prove impact.
• For more information on PoCs please visit: Proof of Concept (PoC) Guidelines and Rules
• The list of all deployed code can be found at: https://github.com/nodlecode/chain

Web/App

• Web/App - Vulnerability reports are to include a runnable Proof of Concept (PoC) in order to prove impact.

All web/app vulnerability reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All PoC content must adhere to the PoC guidelines and rules of Immunefi. In the event that a PoC requires an attack on a web/app asset provided, they must still adhere to the rules provided, otherwise eligibility for a reward may be revoked.

• For more information on PoCs please visit: Proof of Concept (PoC) Guidelines and Rules

Whitehats are highly encouraged to review any potential subdomains and what specific port(s) are in scope. Even though the domain may be the same, different ports may point to different assets.

Dev Environment and Documentation:

Nodle has included dev documentation and/or instructions to help in reviewing code and exploring for vulnerabilities:

Dev or Staging Environment Links:

• https://docs.nodle.com/docs/nodle-chain/introduction

Impacts to other assets:

Hackers are encouraged to submit issues outside of the outlined Impacts and Assets in Scope.

If whitehats can demonstrate a critical impact on code in production for an asset not in scope, Noodle encourages you to submit your report using the “primacy of impact exception” asset.

Impacts in Scope

(For Blockchain/DLTR and Smart Contracts Only) This program is considered to be governed by Primacy of Impact. For more information on what this means visit: Best Practice - Primacy of Impact vs Primacy of Rules.

Impacts are based on the Immunefi Vulnerability Severity Classification System V2.2.

At Immunefi, we classify vulnerabilities on a simplified 5-level scale:

• Critical
• High
• Medium
• Low
• None