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 · Blockchain Capital
- Sequence
- #2
- Score
- 68 → 68 (0)
- Cluster
- mainnet-beta
- Slot
- 424160452
- Off-chain at
- 2026-06-04T03:16:41.794Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EXkXKRUWCWcbiS9Prm7bkN96V8NSHe1uuXrQBeMSXiPG
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (932 chars)
{"actor":"reviewer","decided_at":"2026-06-04T03:16:41.642Z","decision":"review","investigation_id":"fd98925b-474f-4834-bc05-5e457faa9029","new_score":68,"page_slug":"blockchain-capital","prev_score":68,"reason":"The investigation page is largely accurate and well-sourced. The most significant factual error is the characterization that Epstein invested 'alongside Blockchain Capital' in the 2014 Coinbase round — the CoinDesk source cited by the page itself clarifies that Blockchain Capital's planned investment was 'never consummated,' making the co-investment framing inaccurate. One cited URL (CoinTelegraph X-hack article) returns a 404 but the underlying event is confirmed by multiple other sources. The fund NAV figure of ~$964M is slightly stale, with current data showing ~$975M.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}