Accuracy
Measured, not asserted
Most trust products tell you how many dimensions their score has. We think the only number that matters is what happened after the verdict. Every score Vouch issues becomes a watched event: an on-chain detector and partner reports label what the wallet actually did next, and the aggregate is published here — including the number that flatters us least.
ALLOW verdicts that later showed adverse activity
insufficient data
BLOCK verdicts later confirmed legitimate (our false positives)
insufficient data
| Verdict | Resolved outcomes | Went bad | Stayed good | Adverse rate |
|---|---|---|---|---|
| ALLOW | 0 | 0 | 0 | insufficient data |
| WARN | 0 | 0 | 0 | insufficient data |
| BLOCK | 0 | 0 | 0 | insufficient data |
No resolved outcomes in the current window yet. The collection pipeline is live — this page fills in as verdicts age and outcomes land. We publish the methodology first and the numbers when the sample is real, because an accuracy page that appears only once the numbers look good would defeat its own point. Raw JSON: GET /api/v1/accuracy.
Methodology (v1)
- Outcome sources. Auto-detected on-chain activity (drain patterns, sustained healthy activity, dormancy, ownership changes, negative on-chain feedback) and partner reports (
POST /api/v1/events/:trustEventId/outcome: confirmed fraud, confirmed legitimate, chargeback/dispute). - Classification. Rug-pull outflow, negative feedback, confirmed fraud and chargebacks count as bad. Sustained healthy activity and confirmed-legitimate count as good. Dormancy and ownership changes are neutral — silence is not vindication, so neutral outcomes never move a rate in either direction.
- Conflicts. When one verdict accumulates conflicting outcomes, a partner confirmation beats auto detection; within the same tier, bad beats good — ties count against us, not for us.
- Minimum sample. A rate is published only at 10+ resolved verdicts for that bucket; below that the page says “insufficient data” rather than printing noise.
- Window. Rolling 90 days, aggregate counts only — no wallet addresses, no agent ids, no per-customer data on this page or in the API response.
Run a payment provider and want your outcomes counted? Get an API key and report them — partner-confirmed outcomes take precedence over our auto-detection.