Nado Smart Contracts
By Nado Bug bounty on HackenProof
- Top reward
- $500,000
- Top severity paid
- Critical
- Assets in scope
- 1
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to $500,000
- for critical bugs.
- Report on HackenProof
- Submit through the program page.
- Replies within 3 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What HackenProof lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$500,000 |
- Response
-
Within 3 days
First Response 3d
Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test.
Source code 1
- https://github.com/nadohq/nado-contracts
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Nado Smart Contracts (via HackenProof)'s policy.
While testing
-
Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
-
Make every effort not to damage or restrict the availability of products, services, or infrastructure
-
Don’t access or modify other user data, localize all tests to your accounts
-
Perform testing only within the scope
-
Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
-
Don’t break any law and stay in the defined scope
-
Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
-
AI-generated reports without runable PoC are not accepted under this program.
Not accepted
-
Theoretical vulnerabilities without any proof or demonstration
-
Old compiler version
-
The compiler version is not locked
-
Vulnerabilities in imported contracts
-
Code style guide violations
-
Redundant code
-
Gas optimizations
-
Best practice issues
-
Vulnerabilities that can be exploited through front-run attacks only
Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Status
Program status changed
-
Status
Program status changed
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
Original policy
Copied from hackenproof.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Bug bounty Triaged by HackenProof Nado Smart Contracts : Program info Nado Smart Contracts Company: Nado Scope Review: 360516 Submissions: 1431 Total rewards: $18,750 Reputation 100 points required PoC Required Program is: active now Live Submit report Program info Hackers 444 Reports 0 The orderbook DEX harnessing the perfect storm with precision, performance, and control – built on the Ink L2. All Scope Focus Area Program Rules Eligibility and Coordinated Disclosure Disclosure Guidelines Scope Search targets In scope Target │ Type │ Severity https://github.com/nadohq/nado-contracts Copy Smart Contract │ Critical Focus Area IN SCOPE VULNERABILITIES: Smart Contracts We are looking for evidence and reasons for incorrect behavior of the smart contract, which could cause unintended functionality: Stealing or loss of funds Unauthorized transaction Transaction manipulation Attacks on logic (behavior of the code is different from the business description) Reentrancy Reordering Over and underflows OUT OF SCOPE VULNERABILITIES: Smart Contracts Theoretical vulnerabilities without any proof or demonstration Old compiler version The compiler version is not locked Vulnerabilities in imported contracts Code style guide violations Redundant code Gas optimizations Best practice issues Vulnerabilities that can be exploited through front-run attacks only Program Rules Avoid using web application scanners for automatic vulnerability searching which generates massive traffic Make every effort not to damage or restrict the availability of products, services, or infrastructure Avoid compromising any personal data, interruption, or degradation of any service Don’t access or modify other user data, localize all tests to your accounts Perform testing only within the scope Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam Don’t spam forms or account creation flows using automated scanners In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity. Don’t break any law and stay in the defined scope Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission Eligibility and Coordinated Disclosure We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward: You must be the first reporter of a vulnerability. The vulnerability must be a qualifying vulnerability Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary. You must not be a former or current employee of us or one of its contractor. ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded) Provide detailed but to-the point reproduction steps AI-generated reports without runable PoC are not accepted under this program. Disclosure Guidelines Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization No vulnerability disclosure, including partial is allowed for the moment. Please do NOT publish/discuss bugs Live since 17 Nov 2025 Published date 17 Nov 2025 Last updated 24 Sep 2026 Range of bounty $50 - $500,000 Severity Critical $50,000 - $500,000 High $5,000 - $50,000 Medium $2,000 - $5,000 Low $50 - $1,000 Lending smart contract Solidity @Vagner KYC Verified 1 @CL-Nightmare KYC Verified 2 @SuperSabeel1 KYC Verified 3 @rathvahet KYC Verified 4 @lyubomir-slavchev1 KYC Verified 5 Response type Business days First Response 3d Triage Time 7d Reward Time 3d Resolution Time 14d