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.

Sequence
#3
Score
6257 (-5)
Cluster
mainnet-beta
Slot
425420172
Off-chain at
2026-06-09T22:40:16.424Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
Dr2dHRJTGkwGyTdmrNLxTBmAwgSVNS2b7hzkK3xh1iMY
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1562 chars)
{"actor":"judge","decided_at":"2026-06-09T22:40:16.237Z","decision":"review_revise","investigation_id":"e198003e-9540-4950-a4cc-3868bcd92ce3","new_score":57,"page_slug":"gnosis-pay-zodiac-delay-module-exploit","prev_score":62,"reason":"The page is broadly accurate and well-sourced: 18 of 22 claims were independently confirmed, zero claims were disputed by any source, and all core facts — exploit date, affected module versions, $265,000 loss estimate, 41-Safe count, on-chain fund movement, Köppelmann reimbursement pledge, and 99% service restoration — hold up. Two link-rot findings (claim_findings[21] and claim_findings[22]) reflect HTTP 403 paywall restrictions on The Block and The Defiant, not dead links; the underlying claims are confirmed by independent sources. One partially-supported finding (claim_findings[15]) notes that the page overstates balance restoration as completed when sources describe it as a pledge in progress at time of reporting. A high-priority coverage gap flags that the vulnerability was silently patched in the zodiac-core repository on February 27, 2026, months before the exploit, while production instances remained on the legacy vulnerable package — material context for responsibility assessment that is absent from the page. A light revision incorporating that disclosure timeline context and softening the balance-restoration language would bring the page to full accuracy.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}