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 · Raft Protocol
- Sequence
- #6
- Score
- 47 → 47 (0)
- Cluster
- mainnet-beta
- Slot
- 462052570
- Off-chain at
- 2026-10-27T11:24:36.727Z
- Anchored at
- 2026-10-27T11:24:43.000Z
- Block time
- 2026-10-27T11:24:43.000Z
Independent verification
- 1. Database (off-chain)
- H1nhHWFDaPsAoVwAno5GMVVXQn7RBtHr237LagtPcXnZ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1402 chars)
{"actor":"reviewer","artifact_identity":"c480dcb1ca26b0318c7eafe352e6bc90","blocked_count":2,"decided_at":"2026-10-27T11:24:36.243Z","decision":"review","disputed_pct":0,"findings_hash":"BigNwPo4CEe6qAMaCqEQei5qBCRyak3L1BB8iwPeoxrk","investigation_id":"4ca64fe1-1c2b-442d-84e9-ddd98e3729f2","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":47,"page_content_hash":"79a88582afd3d33e5f70bceb4b1543e08c55e69ae9e3af3d291256dd4081c5f7","page_slug":"raft-protocol","prev_score":47,"reason":"The core narrative holds: the 10 Nov 2023 exploit, about 1,577 ETH drained, 1,570 ETH burned, the roughly 50% depeg, and the sunset of the current version all match CoinDesk and REKT. The attacker's ETH accounting is internally inconsistent: 18 ETH in and 7 ETH out does not equal a 4 ETH loss, and CoinDesk says 14 ETH remained. Several claims (the time, hash, 42% recovery and 2026 TVL) could not be checked because of blocked or unreachable sources. The page contains reviewer-facing language ('survivor page', 'merged page') that should be cleaned up.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":5,"sequence_num":6,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}