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 · Gondi V3
- Sequence
- #2
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 425562420
- Off-chain at
- 2026-06-10T14:19:19.871Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 5PKpJ1SFsSf1KJtN2KwbuftpuzasNCi541tD3583rqS9
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1059 chars)
{"actor":"reviewer","decided_at":"2026-06-10T14:19:19.631Z","decision":"review","investigation_id":"d3bfd6f1-187e-4fa1-9d62-4dd56f370ab5","new_score":52,"page_slug":"gondi-v3","prev_score":52,"reason":"The page is broadly accurate and well-sourced. The three partially-supported findings concern: (1) the summary omitting Foundation Capital as co-lead of the seed round (correctly named in the timeline, creating an internal inconsistency); (2) the '78 NFTs stolen' figure, which is the commonly reported number but likely reflects double-counting of transfer events — technical on-chain analysis suggests 39 unique NFTs; and (3) the '~40 transactions' claim, which secondary sources repeat but primary on-chain data (DarkNavy) indicates was a single transaction with 81 executeSell calls. No claims were found to be outright disputed or unverifiable, and no link rot was detected among sources that could be fetched.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}