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
#6
Score
0 → 0 (-8)
Cluster
mainnet-beta
Slot
462053362
Off-chain at
2026-10-27T11:27:17.090Z
Anchored at
2026-10-27T11:27:33.000Z
Block time
2026-10-27T11:27:33.000Z

Independent verification

1. Database (off-chain)
aXPEEHjUawtMU9TeE3ZmBUvNf8cBM7FJJ8D5R6ZbQkv
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1364 chars)
{"actor":"judge","artifact_identity":"d723249b3d2fb009db900a9371d78cfb","band_override":null,"decided_at":"2026-10-27T11:27:16.529Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2143,"investigation_id":"99a1000c-e088-476f-863e-a288c480bf03","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"nathan-fuller-privvy-investments","prev_score":0,"reason":"The core allegations, figures, charges and bankruptcy outcome match the SEC and DOJ releases (claim_findings[0], [1], [10]). No claim was contradicted, but 3 of 14 claims (21%) could not be verified: the phantom mobile app (claim_findings[9]), the July 2024 timeline date (claim_findings[12]) and the statement that Fuller had not responded to the complaint (claim_findings[13]). Two further details, the 3% loss cap and the original $2 million policy amount (claim_findings[3], [4]), were only partly supported and should be corrected or sourced. The reviewer reported no material omissions and no conflict with the subject's current status, and the page already frames the SEC case as allegations.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}