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
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 462051986
- Off-chain at
- 2026-10-27T11:22:24.858Z
- Anchored at
- 2026-10-27T11:22:38.000Z
- Block time
- 2026-10-27T11:22:38.000Z
Independent verification
- 1. Database (off-chain)
- 5UrnCn2abRM2VMdQZLqTkhyFbouAr3x2raGiyJoZ35vn
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1481 chars)
{"actor":"reviewer","artifact_identity":"f5aab6c08219f050ae800c4cbe5ecdf8","blocked_count":3,"decided_at":"2026-10-27T11:22:24.508Z","decision":"review","disputed_pct":0.3333,"findings_hash":"9uDQnL835UBDDcrS2TJEwFkYgSq5Ywcp4VQpLfCtzB54","investigation_id":"68c31745-7e93-46e5-90b3-8250d884cf08","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":38,"omissions":{"material":0,"total":1},"page_content_hash":"586343857d2740bbd9b1fe3d91a43a9b4c951c1108a1862a2e9551e2ff7868af","page_slug":"world-mobile-token-wmtx-singularitynet-bridge-key-compromise","prev_score":38,"reason":"The core incident (bridge key compromise, 53.838M WMTx minted, $16.77M attacker cluster, no per-conversion limit and unbound recipient) is corroborated. Overprecise or unsupported details include the exact $627,350 figure and the 'more than 48 hours' unrotated-key claim. The response and migration narrative (Sept 25 plan, exchange reopenings, police notification) could not be verified because the main source is paywalled, and the timeline's CoinMarketCap source predates the event. The page already flags the 500.6M versus 53.8M discrepancy.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"sequence_num":2,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}