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_revise · Litecoin
- Sequence
- #3
- Score
- 72 → 64 (-8)
- Cluster
- mainnet-beta
- Slot
- 424121791
- Off-chain at
- 2026-06-03T22:59:33.273Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- D9qZwsCGTbc6CLsbFRDquXh8CLMhEBwRw1hnazi19vzV
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1310 chars)
{"actor":"judge","decided_at":"2026-06-03T22:59:33.043Z","decision":"review_revise","investigation_id":"dcbeeb07-7d8c-416f-9f45-84ce4f83d7bb","new_score":64,"page_slug":"litecoin","prev_score":72,"reason":"The page is broadly accurate across its major claims, with 12 of 17 findings confirmed and no link rot or stale critical citations. The primary factual error is in claim_findings[7]: the timeline places Litecoin's $1 billion market cap milestone in January 2013, but Wikipedia and historical price data consistently place it in late November 2013 — approximately 10 months later. Three additional claims are partially supported (claim_findings[0], claim_findings[9], claim_findings[10]): the 'former Google engineer' framing omits the more commonly cited Coinbase credential, the word 'entire' overstates Lee's 2017 divestment slightly, and the January 10 disclosure date in the timeline conflates the theft date with ZachXBT's actual public disclosure (January 16-17). One high-priority coverage gap also requires attention: the ETF section cites the February 2025 CoinShares filing but omits any outcome from the extended SEC review period or 2026 resolution.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}