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 · SKYAI Token
- Sequence
- #7
- Score
- 44 → 44 (0)
- Cluster
- mainnet-beta
- Slot
- 464183554
- Off-chain at
- 2026-11-01T17:55:02.661Z
- Anchored at
- 2026-11-01T17:55:04.000Z
- Block time
- 2026-11-01T17:55:04.000Z
Independent verification
- 1. Database (off-chain)
- 7QbZU7X4MvMDB4RjgA8frWtsFJSzdeHopEXUdeqdvsUa
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1496 chars)
{"actor":"judge","artifact_identity":"7c37ba2c42486731423edf51e2d67ff6","band_override":null,"blocked_count":2,"decided_at":"2026-11-01T17:55:02.244Z","decision":"review_approve","delist_requested":false,"disputed_pct":0.0714,"investigation_id":"b94f8d16-63c7-40b9-a0f6-a262c603b0de","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":44,"page_slug":"skyai-token","prev_score":44,"reason":"Of 15 claim findings, 2 were not scored because the sources were blocked (claim_findings[5], [11]), leaving 13 scored. One was disputed (claim_findings[0], the supply allocation) and none were unverifiable, so the disputed share is about 8%, within the approve band. The disputed statement is a real error, because the cited article says 80% of tokens went to presale participants and 20% to liquidity. It does not touch the page's core allegations (the Bubblemaps analysis, the price decline and the Bitget delisting), which were confirmed against sources. The ZachXBT quote wording (claim_findings[4]) and the unsourced 36-hour duration (claim_findings[1]) are partially supported and have proposed corrections. No shutdown, exploit or sanction was found, and the only omission (bullish counter-views) is minor.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":14,"sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}