Skip to main content
AVOID.NET
← 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 · Binance
View on Solana ↗
Sequence
#9
Score
26 → 26 (0)
Cluster
mainnet-beta
Slot
466739464
Off-chain at
2026-11-08T02:00:21.055Z
Anchored at
2026-11-08T02:00:38.000Z
Block time
2026-11-08T02:00:38.000Z

Independent verification

1. Database (off-chain)
AGbT6mvNs42GNZmVGxoubJ1ErqYsH1ZEByWgGqkcdZ8L
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1284 chars)
{"actor":"reviewer","artifact_identity":"cf1f39bc1018d323e0de77d5dee4baf4","decided_at":"2026-11-08T02:00:20.921Z","decision":"review","disputed_pct":0.1429,"findings_hash":"D2qYQii5BqiFJcKzWEtaUHw4t5wL5AfJiWSoB2pEH7Du","investigation_id":"ee0b172d-1fd3-47c7-812a-115748f8108a","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":26,"omissions":{"material":1,"total":1},"page_content_hash":"d5e059068befacb38475c8cb8db44ce1c64f537c644c0d0e087bef21544bfc4a","page_slug":"binance","prev_score":26,"reason":"The October 2026 hot-wallet theft section matches the Chainalysis post and wire coverage, and the page labels self-reported Binance figures as unaudited. The monitorship claims check out. One defect found: the 60,000-user KYC leak figure, which the cited Hacker News article gives as 10,000. The page omits Binance's June-July 2026 EU withdrawal after the failed MiCA application. This was a time-boxed spot check, not an exhaustive one.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":9,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}