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
- 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. - 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.
- 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 · burgel.eth
- Sequence
- #3
- Score
- 50 → 30 (-20)
- Cluster
- mainnet-beta
- Slot
- 425574255
- Off-chain at
- 2026-06-10T15:37:39.702Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DXMyArreKacvLFLoPhuhemWhs54iHVs6iUH3QsvW8wzm
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1204 chars)
{"actor":"judge","decided_at":"2026-06-10T15:37:39.508Z","decision":"review_revise","investigation_id":"fbbc210c-589b-423d-acbd-c997165eb157","new_score":30,"page_slug":"burgeleth","prev_score":50,"reason":"The reviewer found 2 of 7 claims disputed (43% disputed_pct), placing this page in the 30–60% band requiring significant revision. Most critically, claim_findings[4] identifies a direct internal contradiction: the page summary and Entity Identification section assert 'no verifiable information exists,' while sections[0] on the same page documents a confirmed $3M private-key-compromise drain with a named theft address and a ZachXBT citation the reviewer verified resolves correctly. Claim_findings[6] further disputes the trust score justification of 50 (neutral) as inconsistent with the critical-severity incident already documented on the page. Two high-priority coverage gaps — the unverified $3M aggregate and the misleading summary — indicate the page requires editorial correction before it accurately represents the evidence it already holds.","score_delta":-20,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}