- Top reward
- $250,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 $250,000
- for critical bugs, from $100.
- Report by email
- [email protected]
- Partial safe harbor
- Some legal protection; read the terms.
- Paid by USDC, ETH
- No identity requirement stated.
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$250,000 |
| High |
|
$50,000 |
| Medium |
|
$5,000 |
| Low |
|
$1,000 |
- Top reward
-
$250,000
Critical = Up to 250,000 USDC
- Lowest reward
-
$100
Note = Up to 100 USDC
- Safe harbor
-
Partial
Not engage in any unlawful conduct when disclosing the bug, including through threats, demands, or any other coercive tactics.
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, 4 excluded.
Smart contracts 2
- Collection contracts
- SZNS core smart contracts
Out of scope (4)
- Any already-reported bugs or other vulnerabilities
- Bugs in any third party contract or platform that interacts with SZNS
- Vulnerabilities already reported and/or discovered in contracts built by third parties on SZNS
- Vulnerabilities related to domains, DNS or servers of websites
Rules
What the policy asks of you, and the bug types it won't reward, quoted from szns's policy.
While testing
-
Discover a previously unreported, non-public vulnerability within the scope of this Program.
-
Be the first to disclose the unique vulnerability to the Team by the disclosure requirements below.
-
Not exploit the vulnerability in any way, including by making it public or obtaining a profit (other than a reward under this Program).
-
Make a good faith effort to avoid privacy violations, data destruction, interruption or degradation of SZNS.
-
Submit only one vulnerability per submission unless you need to chain vulnerabilities to impact any vulnerabilities.
-
Not submit a separate vulnerability caused by an underlying issue that is the same as an issue on which a reward has been paid under this Program.
-
The disclosure must be made within 24 hours following the discovery of the vulnerability
Not accepted
-
Bugs in any third party contract or platform that interacts with SZNS
-
Vulnerabilities related to domains, DNS or servers of websites
-
Vulnerabilities already reported and/or discovered in contracts built by third parties on SZNS
-
Any already-reported bugs or other vulnerabilities
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.