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 · JUDAO
- Sequence
- #3
- Score
- 18 → 6 (-12)
- Cluster
- mainnet-beta
- Slot
- 461973601
- Off-chain at
- 2026-10-27T06:44:37.131Z
- Anchored at
- 2026-10-27T06:44:52.000Z
- Block time
- 2026-10-27T06:44:52.000Z
Independent verification
- 1. Database (off-chain)
- 374GjWB3r5DcTEAP4aEqppxrZb9VKT3qqiDz81LtP5yg
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1868 chars)
{"actor":"judge","artifact_identity":"74b9ff04f35d31a157dca0025192ea7b","band_override":null,"blocked_count":5,"decided_at":"2026-10-27T06:44:36.801Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1818,"investigation_id":"30044096-fa32-4ad7-ba26-1412435a79a3","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":6,"page_slug":"judao","prev_score":18,"reason":"Of 16 claim findings, 5 were unreadable because the source blocked the reviewer (BscScan, X, Coinranking, AiInvest) and were left out, leaving 11. Two of those (claim_findings[8], [13]) could not be found, so about 18% are disputed or unverifiable. The core exploit facts (date, ~$228K loss, root cause, addresses, transaction hash) are confirmed by the Verichains post-mortem (claim_findings[0], [1]). The page needs revision for three reasons. The MEXC link is dead (claim_findings[4], [5]) and the 'independent' TVL claim is doubtful. The Lista DAO and BUSD-JUDAO details are not in the fetched sources (claim_findings[2], [9]). The page also omits the June 2026 JuCoin withdrawal and reserve dispute (omission_findings[0]).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-12,"scored_claims":11,"sequence_num":3,"severity_override":{"applied":false,"band":null,"from_band":"minor","reason":"The material omission (June 2026 withdrawal delays and disputed reserves at parent exchange JuCoin) concerns the parent exchange, not the JUDAO exploit itself. The reviewer found the subject operating, with no shutdown or sanction, and the source itself says the alert did not prove insolvency. The page stays in the minor band, and the omission is passed on as a required addition."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}