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 · Chillguy
- Sequence
- #4
- Score
- 53 → 53 (0)
- Cluster
- mainnet-beta
- Slot
- 461978101
- Off-chain at
- 2026-10-27T07:00:21.411Z
- Anchored at
- 2026-10-27T07:00:47.000Z
- Block time
- 2026-10-27T07:00:47.000Z
Independent verification
- 1. Database (off-chain)
- 9AXFcvTFwHsEvD69wQRg6hynsPn28YGAV3gmozM8xa3v
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1492 chars)
{"actor":"judge","artifact_identity":"a3d3733c3f2da4ff156fd6a2f04c8b2c","band_override":null,"decided_at":"2026-10-27T07:00:21.025Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"4f7309a0-87c3-451a-94db-e94baa36e395","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"page_slug":"chillguy","prev_score":53,"reason":"Of 10 claims checked, 3 were disputed (claim_findings[0], [1], [2]) and 2 could not be verified (claim_findings[8], [9]), giving 50%, which falls in the significant-issues band. The disputed items are date errors of one to two days (Binance listing dated 11-25 versus 11-27 in the cited article; Banks' post dated 11-21 versus 11-20, appearing in both the text and the timeline), not challenges to the core story, and the two Banks-date findings are one underlying error. The core narrative (Pump.fun launch, 11-27 all-time high, roughly 98% decline, no regulatory action found) held up, the review found no shutdown, exploit or omission, and the reviewer's confidence was low (0.5) with many sources not fetched, so the penalty is set at the mild end of the band. A high-priority coverage gap on holder concentration and deployer activity remains open.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}