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_approve · Spicenet
- Sequence
- #3
- Score
- 58 → 58 (0)
- Cluster
- mainnet-beta
- Slot
- 425213126
- Off-chain at
- 2026-06-08T23:47:59.858Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- J6bEpYm1M5QLm3jgX7v3iRA3ZXwzVNrm5REAJBrG6RcY
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1181 chars)
{"actor":"judge","decided_at":"2026-06-08T23:47:59.616Z","decision":"review_approve","investigation_id":"dd61201d-64a3-48d7-bca3-d3dd0bf2558c","new_score":58,"page_slug":"spicenet","prev_score":58,"reason":"The reviewer checked 21 claims and found zero disputed. Seventeen claims are fully confirmed by independent sources, one claim is partially supported due to a naming ambiguity with a legacy Indian ISP that does not contradict the page (claim_findings[0]), and three claims are unverifiable for low-stakes reasons — an unscrapable tweet, a regulatory absence-of-evidence finding, and a future milestone date (claim_findings[17], claim_findings[18], claim_findings[19]). No link rot or stale citations were identified on any critical source. The one high-priority coverage gap — the absence of a post-Q1 2026 revised mainnet timeline — is an expansion recommendation, not a disputed fact, and the page itself already discloses the missed deadline. With zero disputed claims and 0.82 reviewer confidence, the page holds up to scrutiny.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}