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 · Bit.com
- Sequence
- #8
- Score
- 62 → 52 (-10)
- Cluster
- mainnet-beta
- Slot
- 461980852
- Off-chain at
- 2026-10-27T07:10:22.262Z
- Anchored at
- 2026-10-27T07:10:32.000Z
- Block time
- 2026-10-27T07:10:32.000Z
Independent verification
- 1. Database (off-chain)
- Umnc3iipDy1nn3MhygB3DbGFHNCXukdLxatPpM4oiYx
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1344 chars)
{"actor":"judge","artifact_identity":"89ce8e3678d075f0cc634f003a327ea4","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T07:10:21.764Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"cc3fbcec-6e6a-4760-96d9-3cb179d61864","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":52,"page_slug":"bit-com","prev_score":62,"reason":"Of 9 claims checked, 1 could not be scored because the source blocked the reviewer (claim_findings[5]); of the remaining 8, 2 could not be verified (claim_findings[4], claim_findings[8]), giving about 25% disputed or unverifiable. The page states that the shutdown was completed on March 31, 2026, but the cited sources only describe that date as a plan (claim_findings[2]), and the 'orderly' description has no independent source. The core shutdown timeline, the Series C details and the absence of hacks or enforcement are supported, and the page correctly reports the closure. Reviewer confidence is moderate-low, so the penalty stays at the lower end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-10,"scored_claims":8,"sequence_num":8,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}