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 · SKYAI Token
- Sequence
- #4
- Score
- 17 → 5 (-12)
- Cluster
- mainnet-beta
- Slot
- 463778584
- Off-chain at
- 2026-10-31T17:49:39.051Z
- Anchored at
- 2026-10-31T17:49:52.000Z
- Block time
- 2026-10-31T17:49:52.000Z
Independent verification
- 1. Database (off-chain)
- DDCnarmqcJrRCkAhWwoqnqMY2itcwnLyxXVgLxTb5ZPt
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1940 chars)
{"actor":"judge","artifact_identity":"3a95144ddf558b62ef23d3f1a97efd93","band_override":null,"blocked_count":1,"decided_at":"2026-10-31T17:49:38.775Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"b94f8d16-63c7-40b9-a0f6-a262c603b0de","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":5,"page_slug":"skyai-token","prev_score":17,"reason":"No claim finding was disputed. The core allegations are supported and framed as allegations: the ZachXBT naming of SKYAI is confirmed (claim_findings[0]) and the Bubblemaps post supports the coordinated-wallet allegation. However, the Merkle article, the main source for the 36-wallet, 25% supply, 3,911 BNB and 6.5% figures, returns 404 and was never archived (claim_findings[1]). The 79% price decline is out of date, since the token is now more than 95% below its peak (claim_findings[3], omission_findings[0]). One Gate.io citation could not be read because the source blocked the reviewer (claim_findings[2]), so it is a coverage limit and not a defect of the page. The reviewer's confidence is moderate (0.5) and it sampled only a few claims, so the penalty is kept at the low end of the minor band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-12,"scored_claims":3,"sequence_num":4,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"The review reports a material omission: the page stops at late May 2026 (down 79%), while the token is now more than 95% below its peak. A high-priority coverage gap covers the same period. The percentage alone (0 disputed or unverifiable findings among the 3 counted, once the source_blocked finding is left out) would approve the page, so it is judged in the minor band."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}