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.
- Sequence
- #2
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 443515352
- Off-chain at
- 2026-08-25T17:04:35.186Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- BVsvqhBntzhAsw2JyZgLhDhtTzTgN47gW5jx9GLrbod4
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1361 chars)
{"actor":"reviewer","decided_at":"2026-08-25T17:04:34.915Z","decision":"review","investigation_id":"6a80ffa9-764c-4d6c-819b-2534f22d1540","new_score":0,"page_slug":"july-2026-bridge-hack-wave-three-protocols-35-6m-one-day","prev_score":0,"reason":"The core per-incident facts for AFX Trade, Verus, and B-Squared (amounts, dates, technical causes, bounty terms, fund flows) are well-corroborated by multiple independent, credible sources and the $35.6M aggregate arithmetically reconciles with the three parts. However, the page contains two clear sourcing defects: it attributes the 'Hackers Day' label specifically to Blockaid when the only located source attributes it to unnamed commentators generally, and it asserts a July 8 Verus fund-redeposit event that its own cited source does not contain and that is otherwise substantiated only by an uncited opinion blog. The page also overstates H1 2026 as record-setting for aggregate losses when its own cited sources (Blockaid, TRM Labs, Immunefi) explicitly say losses were below the prior year and only incident count was a record, and it characterizes B-Squared as part of a 'bridge hack wave' despite a source explicitly distinguishing it as a non-bridge incident.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}