Skip to main content
Sign in
← avoid.net

Verify a decision

Every moderation decision on AVOID.NET is anchored to the Solana blockchain. You don't have to trust us — you can verify cryptographically that we committed to a verdict at a specific moment and have not rewritten it.

How verification works

  1. We commit. When a moderator accepts/rejects a submission, we serialize the decision into deterministic UTF-8 bytes (payload_canonical_string), hash it with SHA-256, encode the digest as base58, and write it to Solana inside an SPL Memo v2 transaction.
  2. We store the bytes. The exact bytes we hashed are stored alongside the decision in our database. Anyone can read them and recompute the hash in any language.
  3. You compare three values. Database hash, your independently-recomputed hash, and the hash inside the on-chain memo. If all three match, the decision is authentic and timestamped.
The on-chain memo format is AVOID.NET|v1|h:<b58-sha256>|d:<id>|t:<iso>

Find a signature on any investigation page's decision log, or run python -m src.verify_decision --signature <sig> for a CLI check.

Decision
review_approve · Drift Protocol
View on Solana ↗
Sequence
#2
Score
2222 (0)
Cluster
mainnet-beta
Slot
418765555
Off-chain at
2026-05-10T05:40:03.492Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
9uddDSjMgG7KDgYRmvUxJrDvoQDHG53oh3od6eK1mG7i
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1471 chars)
{"actor":"judge","decided_at":"2026-05-10T05:40:03.309Z","decision":"review_approve","investigation_id":"50227794-5b4a-4d07-97d3-2fae3507b3e0","new_score":22,"page_slug":"drift-protocol","prev_score":22,"reason":"The reviewer evaluated 35 claims and found a disputed rate of 5.7% (1 of 35), which falls within the 0-10% approval band. The single disputed claim — Solana DeFi TVL dropping 12% after the exploit (claim_findings[33]) vs. a consensus range of 14-17% — is a peripheral contagion-impact metric that does not affect any core allegation about the exploit mechanism, attacker identity, or financial losses. The CCTP bridging window stated as 8 hours (claim_findings[17] and claim_findings[27]) is classified as partially supported rather than disputed because the dollar amount ($232M) and transaction count (100+) are confirmed by multiple Tier 1 sources; only the window duration varies between sources. The OFAC/CAATSA legal authority conflation (claim_findings[26]) is a technical imprecision that does not constitute fabrication. No link rot or stale citations were identified. Two high-priority coverage gaps — on-chain transaction hash verification and Circle's legal response to the class action — are expansion opportunities, not accuracy failures, and do not affect approval under the applicable decision rules.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}