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 · Tia
- Sequence
- #2
- Score
- 42 → 42 (0)
- Cluster
- mainnet-beta
- Slot
- 443508343
- Off-chain at
- 2026-08-18T16:55:20.223Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 5xc3khK1cppmqvyN5xXsAy9JXKWzMFbd8HwwFvXADXQi
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1234 chars)
{"actor":"reviewer","decided_at":"2026-08-18T16:55:20.048Z","decision":"review","investigation_id":"4a9ed1f3-fadc-4508-b6d8-8d34901e8588","new_score":42,"page_slug":"tia","prev_score":42,"reason":"The page's core factual claims -- funding history, the Polychain staking-rewards controversy and subsequent Foundation buyback, the sybil-dominated airdrop, price collapse, and the Lotus upgrade fix -- are well-sourced and independently corroborated. The most severe allegation (personal insider dumping by Al-Bassam) is properly hedged as an unverified single-source claim, which is good practice. One factual error was found (500 hours of community service vs. 320-300 in sources including the page's own citation) and one mischaracterization (calling a DDoS attack on the CIA a 'breach'), both in the founder-biography section, which is otherwise tangential to Celestia's own conduct as an entity. The page also correctly surfaces an entity-favorable development (Foundation proactively bought back Polychain's position and closed the loophole via a protocol upgrade) rather than omitting it.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}