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_revise · DYORSwap
View on Solana ↗
Sequence
#7
Score
45 → 45 (0)
Cluster
mainnet-beta
Slot
464856323
Off-chain at
2026-11-03T09:55:57.003Z
Anchored at
2026-11-03T09:56:28.000Z
Block time
2026-11-03T09:56:28.000Z

Independent verification

1. Database (off-chain)
BbrwraW7naTZVCa1F9qJ2QiDNiXe4tkf8U2UshRQ27A9
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1402 chars)
{"actor":"judge","artifact_identity":"f9eb68d7f410e8ff06d4cade21c96cb0","band_override":null,"decided_at":"2026-11-03T09:55:56.722Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2222,"investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":45,"page_slug":"dyorswap","prev_score":45,"reason":"The core incident facts on this page (amounts, address count, deployment date, compensation of more than 200 ETH, Tornado Cash figures) match the cited sources, and no shutdown, sanction or omission was found. Two of eight claims could not be verified (claim_findings[7] on the timing of GIWA's denial, claim_findings[8] on the audit, team and TVL caveats), giving a disputed share of 25%. Two further claims are attributed to the wrong source: the 40% reimbursement policy is credited to KuCoin though Protos reports it (claim_findings[2]), and the 12-13 hour duration is credited to Cointelegraph though it does not state it (claim_findings[3]). These are citation fixes rather than disputed allegations, so the penalty is at the lower end of the minor band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}