$16.65B
Already gone after people trusted a report
DefiLlama
Web3 security contests. Proof that stays live.
Contest.Then proof.
We find bugs in a contest, then keep a live page that still matches the code.
Loading
Trust Passport
MatchedLive evidence
Protocol Trust Record
Score
Native /1400
Code
Exact match
Controls
Keys mapped
Gaps
Still open
1Contest2Fixes3Match4Passport
$36.7M
Stolen from live contracts with hidden source
Chainalysis
$340.7M
14 bridge incidents. One missing check. Country-scale loss
PeckShield
You paid copies
Same bug, many payouts
Forty people can file the same High. You funded forty write-ups of one bug. Unique work got dust. The drain later was not a copy.
- Copies eat the prize pool
- Judges spend days on repeats
- New work gets split to nothing
A leaderboard is not coverage
Nobody owns the hard parts
A busy contest board can still miss the function that later drains. Nobody was assigned to it. No findings is not the same as reviewed.
- No owner per function
- Admin and upgrade paths sit untouched
- A quiet board can still hide a hole
The rest gets skipped
Easy bugs first
People hunt the bugs that pay. Upgrade paths and boring wiring get skipped. Zero paid Highs can still mean a drain. Then someone signs.
- Easy surfaces first
- The work that later drains gets skipped
- People still signed off a PDF
T4
Assigned owner
Function
Someone owns each user action. Deposit, withdraw, the basics.
T3
Assigned owner
Contract
Someone owns the whole contract, not just one function.
T2
Assigned owner
Integration
Someone owns how contracts talk to each other.
T1
Assigned owner
System
Someone owns the money rules and admin powers. The work people skip.
Firm PDF
- One team. One pass.
- A PDF for one week of code.
- Badge stays after the code moves.
- User sees: audited by Firm X. Then signs.
Open contest
- Same easy bugs. Many copies.
- Busy board. No owner. Drain still possible.
- Report ages on the next change.
- User sees: we ran a contest. Then signs.
Our solution
- 4x coverage. Each layer has an owner.
- Copies are not paid as unique work.
- Live page after launch. Gaps stay visible.
- User sees: what was checked, if the code still matches.
03Pipeline
How we run it.Contest first. Live page after.
A firm PDF cannot close this. An open contest cannot. We find bugs in a contest with 4x coverage. Then we keep a live page after the code goes live.
01 · Prepare
Pre-audit
Freeze the code, map the risks, and write a brief so contest reviewers do not start cold.
Protocol team + up to 3 pre-audit reviewers (function, contract, system)
Open pre-auditYou get
- Frozen code for the contest
- A risk map
- A brief for reviewers
- Stop if the basics are not ready
1 / 5
Core cascade · T4 → T0
Lower tiers hunt. Higher tiers validate. T0 locks the report.
Protocols / founders
- Pre-audit readiness instead of cold auditor spend
- Tier-routed core coverage with locked findings
- Post-audit fix proof on the real diff
- Native score + Trust Passport investors can open
Auditors
- Exact-tier work matched to skills (not politics)
- Validation cascade builds portable reputation
- Verified findings raise score and routing power
- Settlement tied to accepted, validated work
Investors & users
- Passport: scope, fix state, live match, gaps
- Native /1400 and External /900 kept separate
- Authority and upgrade risk visible
- Wallet-time signal before the signature
Start a contest. Keep the proof.
Loading