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.

Sequence
#2
Score
3 → 3 (0)
Cluster
mainnet-beta
Slot
461974853
Off-chain at
2026-10-27T06:49:12.628Z
Anchored at
2026-10-27T06:49:18.000Z
Block time
2026-10-27T06:49:18.000Z

Independent verification

1. Database (off-chain)
3e2Y8u1GeTXXpPDXiHXZQHkvtxBPYFUQCRFPLiTmfPnv
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1469 chars)
{"actor":"reviewer","artifact_identity":"b415fab95cde9ffadf524689cd730b40","decided_at":"2026-10-27T06:49:12.425Z","decision":"review","disputed_pct":0.2667,"findings_hash":"7x7zt7pGDP61tCQ4d3DrSBsExm5i33SxX2QL3QWPKnTE","investigation_id":"9dca8a37-94ec-492b-abc7-90a7b38b6393","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":3,"page_content_hash":"c9d433b89fa0fa457df0fcbf73eb03c6ad89149d6d5ad700b71108699979f2e6","page_slug":"clippy-token-clippy-microsoft-x-account-hijack","prev_score":3,"reason":"The core account of the hijack, Microsoft's confirmation, the 13+ million followers, the roughly 30-minute duration, the suspended impersonator and the listed compromise vectors are supported by BleepingComputer and SecurityWeek. Two problems stand out. The page attributes a deleted apology to Microsoft, but sources say Microsoft did not post it. It also names spokesperson Brent Colburn, whom no fetched source mentions. The exact date is unsettled because the sources' 'Thursday' does not match October 2, 2026. Token metrics are broadly consistent with live data, and the page hedges well on which token was promoted.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}