- Top reward
- $10,000
- Top severity paid
- Critical
- Assets in scope
- 2
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $10,000
- for critical bugs, from $100.
- Report by email
- [email protected]
- Partial safe harbor
- Some legal protection; read the terms.
- Paid by ARK, BTC
- Proof of identity needed to get paid.
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$10,000 from $5,000 |
| Medium |
|
$1,500 from $500 |
- Top reward
-
$10,000
Critical Vulnerabilities: $5,000 — $10,000
- Lowest reward
-
$100
Basic Vulnerabilities: $100 — $300
- Safe harbor
-
Partial
The Researcher must not maliciously initiate an exploit on ARK Public Network. If testing is required for a potential vulnerability or to reproduce it, please use ARK Development Network or set up your own local ARK-based chain .
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
2 assets you may test, 1 excluded.
Domains 1
- ark.io
Source code 1
- https://github.com/ArkEcosystem/core
Out of scope (1)
- ARK Public Network
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Ark's policy. "We" in these lines means the program, not this site.
While testing
-
The Researcher must never have publicly disclosed the exploit or vulnerability.
-
The Researcher must not maliciously initiate an exploit on ARK Public Network.
-
If testing is required for a potential vulnerability or to reproduce it, please use ARK Development Network or set up your own local ARK-based chain .
-
The Researcher must be able to completely reproduce and demonstrate the vulnerability or provide valid instructions so that our development team can do the same.
-
Before reporting a security vulnerability, the Researcher should review public branches and the latest commits to see if the team is currently aware of the vulnerability.
Not accepted
-
Exploits that make indirect use of already known issues may not be eligible for payment.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
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.