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
- Sequence
- #2
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 443519698
- Off-chain at
- 2026-08-26T08:03:52.453Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 2wtc5R7gFdsbR8ZjkBzPUqs5ZByZhaQGk55JoWZMy8j5
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1098 chars)
{"actor":"reviewer","decided_at":"2026-08-26T08:03:52.335Z","decision":"review","investigation_id":"7b8d8b86-b079-4597-9103-2049c740e3e3","new_score":0,"page_slug":"june-2026-cross-chain-bridge-exploit-127m","prev_score":0,"reason":"Independent research found no Tier 1 or Tier 2 corroboration for a $127 million June 2026 cross-chain bridge exploit; the page's sole named source (a Nadcab Labs marketing blog) contains an independently verifiable factual error (a nonexistent 'Wormhole February breach'), reinforcing that the $127M claim is uncorroborated at best and likely fabricated. The page's substantial secondary content on the real Syscoin bridge exploit and the KelpDAO/LayerZero exploit is well corroborated by multiple independent Tier 1/2 sources and matches on-chain details published by Rekt News, though its claim that Syscoin was the 'only' large June 2026 bridge exploit is contradicted by the comparably-sized Humanity Protocol incident.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}