Skip to main content
AVOID.NET
Sign in
← 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 · burgel.eth
View on Solana ↗
Sequence
#2
Score
50 → 50 (0)
Cluster
mainnet-beta
Slot
425574252
Off-chain at
2026-06-10T15:37:39.619Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
B1gFNKwUAT6NicNadGQ1e1iJpJXW58ZJiy7BZWard216
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1042 chars)
{"actor":"reviewer","decided_at":"2026-06-10T15:37:39.508Z","decision":"review","investigation_id":"fbbc210c-589b-423d-acbd-c997165eb157","new_score":50,"page_slug":"burgeleth","prev_score":50,"reason":"The page suffers from a critical internal inconsistency: its summary and 'Entity Identification' section assert no verifiable information exists, while sections[0] documents a specific $3M private-key-compromise drain of burgel.eth with a named theft address and a ZachXBT Telegram citation that is independently confirmed to exist. The core incident claim (drain, consolidation, Tornado Cash) is sourced to a single verifiable Telegram post but lacks independent corroboration and on-chain documentation of the full $3M aggregate. The ZachXBT source URL resolves and contains the attributed text, but no archive URL is provided and no secondary press coverage of this specific incident was found.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}