The Nodle Network is a decentralized wireless network, composed of Nodle Edge Nodes, powered by the Nodle Chain, and the NODL token.
Nodle connects the physical world to Web3 by using smartphones as edge nodes. The edge nodes read devices and sensors in the physical world using Bluetooth Low Energy (BLE) and connect that information to the blockchain. Creating a geolocation-based layer one that can be used by many unique applications built for the hyper-connected, mobile-oriented world we live in. Nodle creates an economic model that is secure, private, and scalable.
For more information about Nodle, please visit https://www.nodle.com/
For Whitehats: It is highly recommended that you review the details of this program in full. Although many Bug Bounty programs have standard terms and conditions, each also has their own unique details that are critical to your success.
Prior to submitting a report please review the Immunefi Bug Report Template and Best Practices.
Nodle adheres to category Publication Category 3: Approval Required. This Policy determines what information whitehats are allowed to make public from their submitted vulnerabilities. For more information about the category selected, please refer to our Responsible Publication page.
Rewards by Threat Level
Please review how rewards are distributed based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale system with separate scales for Smart Contracts and Websites/Apps.
Rewards for critical Blockchain/DLT vulnerabilities are further capped at 10% of the funds at risk. In cases of repeatable attacks, only the first attack is considered unless the smart contract cannot be upgraded or paused. However, there is a minimum reward of USD 10 000 for Critical Blockchain/DLT bug reports.
Rewards for high Blockchain/DLT vulnerabilities are further capped at 100% of the funds at risk. In cases of repeatable attacks, only the first attack is considered unless the smart contract cannot be upgraded or paused. However, there is a minimum reward of USD 2 000 for High Blockchain/DLT bug reports.
Rewards for critical web/app vulnerabilities will be further capped at 10% of direct funds at risk if the bug discovered is exploited. However, there is a minimum reward of USD 4 000.
High web/app vulnerabilities will be further capped at up to 100% of the funds affected. However, there is a minimum reward of USD 1 000.
Payouts and Payout Requirements
Payouts are handled by the Nodle team directly and are denominated in USD. However, payouts are done in NODL, and will be converted to a USD value at the time of bounty acceptance. Nodle commits to honoring payouts according to the terms set out in this program at the time of report submission, and to treat this program as the agreement and source of truth concerning bug reports and responsible disclosures.
For the purposes of determining report validity, this is a Primacy of Impact program.
Learn more about report validity best practices here: Best Practice - Primacy of Impact vs Primacy of Rules.
Nodle does have a Know Your Customer (KYC) requirement for bounty payouts.
KYC Info Required:
- ID Scan
- Self Portrait
KYC information is only required on confirmation of the validity of a vulnerability report.
Audit Discoveries and Known Issues
Vulnerability reports covering previously-discovered are not eligible for any reward through this bounty program. If a report covers a known issue, it may be rejected together with proof of the issue being known before escalation of the vulnerability report via Immunefi.
Previous audits and known issues can be found at:
- Upstream reports to Parity Technologies, for Polkadot or related projects (Blockchain/DLT/Web/API)
- Upstream reports made to OnFinality, concerning improper operation of the Nodle hosted Mainnet RPC endpoint (Blockchain/DLT/Web/API)
- Substrate Pallet Audit, Halborn, Feb. 2022 (Blockchain/DLT)
- Secfault Security, Substrate Chain Audit, July 2020 (Blockchain/DLT)
- Quantstamp Security Assessment Certificate, Sept. 2020 (Blockchain/DLT)
- USD $10,000 to USD $20,000
- USD $2,000 to USD $10,000
Websites and Applications
- USD $4,000 to USD $10,000
- USD $1,000 to USD $4,000
Assets in scope
- Blockchain/DLT - Nodle Chain NodeType
- TargetBlockchain/DLT - Primacy of ImpactType
- Websites and Applications - Eden Parachain Network RPC EndpointType
- Websites and Applications - Paradis Parachain Test Network RPC EndpointType
- TargetWebsites and Applications - Nodle Web ClientType
- TargetWebsites and Applications - Primacy of ImpactType
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 - 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 - 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:
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:
Impacts in scope
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.
- Network not being able to confirm new transactions (Total network shutdown)CriticalImpact
- Unintended permanent chain split requiring hard fork (Network partition requiring hard fork)CriticalImpact
- Direct loss of fundsCriticalImpact
- Permanent freezing of funds (fix requires hardfork)CriticalImpact
- RPC API crash due to a malformatted packet that should return an error to the client. Exceptions include if the attack was triggered due to DNS tampering, denial of service, or exceeding rate limits set by the gatewayCriticalImpact
- Unintended chain split (Network partition)HighImpact
Websites and Applications
- Execute arbitrary system commandsCriticalImpact
- Retrieve sensitive data/files from a running server such as: database passwords, blockchain keys, etc (this does not include non-sensitive environment variables, open source code, or usernames)CriticalImpact
- Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as: Changing registration information, Commenting, Voting, Making trades, Withdrawals, etc.CriticalImpact
- Changing the NFT metadataCriticalImpact
- Subdomain takeover with already-connected wallet interactionCriticalImpact
- Direct theft of user fundsCriticalImpact
- Malicious interactions with an already-connected wallet such as: Modifying transaction arguments or parameters, Substituting contract addresses, Submitting malicious transactionsCriticalImpact
- Direct theft of user NFTsCriticalImpact
- Injection of malicious HTML or XSS through NFT metadataCriticalImpact
- Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as: Email or password of the victim, etc.HighImpact
- Improperly disclosing confidential user information such as: Email address, Phone number, Physical address, etc.HighImpact
- Subdomain takeover without already-connected wallet interactionHighImpact
Out of Scope & Rules
The following impacts and attack vectors are excluded from rewards by default for all Immunefi bounty programs:
- Attacks that the reporter has already exploited themselves, leading to damage
- Attacks requiring access to leaked keys/credentials
- Attacks requiring access to privileged addresses (governance, strategist), except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
- Broken link hijacking is out of scope
Smart Contracts and Blockchain/DLT
- Basic economic governance attacks (e.g. 51% attack)
- Lack of liquidity
- Best practice critiques
- Sybil attacks
- Centralization risks
Websites and Apps
- Theoretical impacts without any proof or demonstration
- Content spoofing / Text injection issues
- Captcha bypass using OCR
- CSRF with no security impact (logout CSRF, change language, etc.)
- Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
- Server-side information disclosure such as IPs, server names, and most stack traces
- Vulnerabilities used to enumerate or confirm the existence of users or tenants
- Vulnerabilities requiring unlikely user actions
- URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
- Lack of SSL/TLS best practices
- Attacks involving DDoS
- Attacks requiring privileged access from within the organization
- SPF records for email domains
- Feature requests
- Best practices
|Category||Additional specific vulnerabilities and/or attacks to exclude|
|Website & Application||Attacks with the potential to disrupt other customers of a shared web hosting environment, such as Vercel.|
|Website & Application||Attacks that purposefully access account-related data that belongs to another user, and was not created for explicit purposes of security investigation.|
|Blockchain/DLT||Attacks with the potential to disrupt other customers of a shared hosting environment OnFinality.|
|Blockchain/DLT||Attacks that purposefully access account-related data that belongs to another user, and was not created for explicit purposes of security investigation.|
|Blockchain/DLT||Vulnerabilities affecting third-party services used by Nodle such as OnFinality|
The following activities are prohibited by this bounty program. Violation of these rules can result in a temporary suspension or permanent ban from the Immunefi platform at the sole discretion of the Immunefi team, which may also result in: 1) the forfeiture and loss of access to all submissions, and 2) zero payout.
Please note that Immunefi has no tolerance for spam/low-quality/incomplete reports, “beg bounty” behavior, and misrepresentation of assets and severity. Immunefi exists to protect the global crypto community, not facilitate grift.
- Any testing with mainnet or public testnet deployed code; all testing should be done on private testnets
- 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
- 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. These rules are subject to change at any time.