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 · DYORSwap
- Sequence
- #3
- Score
- 38 → 33 (-5)
- Cluster
- mainnet-beta
- Slot
- 462042985
- Off-chain at
- 2026-10-27T10:50:40.345Z
- Anchored at
- 2026-10-27T10:50:46.000Z
- Block time
- 2026-10-27T10:50:46.000Z
Independent verification
- 1. Database (off-chain)
- 9QqHpNuajhUX6FBHPkSAdNV1yE9sffFPc3Umj9zpJLz3
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2865 chars)
{"actor":"judge","artifact_identity":"91cf880561a2ca813b14a76f2ad2e959","band_override":{"actual_delta":-5,"actual_verdict":"review_revise","disputed_pct":0,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"The core incident facts (fake GIWA chain, chain ID 9134, 767.65 ETH received, 766.25 ETH drained) were confirmed (claim_findings[0]), and no claim was disputed, so the computed disputed share is 0% (4 countable findings; 2 of 6 were excluded because the sources blocked the reviewer). The page is revised rather than approved because the audit and team claims rest on a single source that could not be read, which the reviewer rated a high-priority coverage gap, and because three claims need correction: the 'inadvertent victim' wording is attributed to Crypto Briefing but is DYORSwap's own framing (claim_findings[1]), the 40% compensation ratio and address are cited to the wrong article (claim_findings[2]), and 'no perpetrators named' leaves out the project's suspect addresses and the Tornado Cash laundering (claim_findings[3], omission_findings[0]). No shutdown, sanction or exploit contradicts the page, and the omissions are minor. The blocked share is a limit on what could be checked, not a defect of the page."},"blocked_count":2,"decided_at":"2026-10-27T10:50:40.026Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"9d3b1634-433e-4739-8a58-1d3f391d4a73","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":33,"page_slug":"dyorswap","prev_score":38,"reason":"The core incident facts (fake GIWA chain, chain ID 9134, 767.65 ETH received, 766.25 ETH drained) were confirmed (claim_findings[0]), and no claim was disputed, so the computed disputed share is 0% (4 countable findings; 2 of 6 were excluded because the sources blocked the reviewer). The page is revised rather than approved because the audit and team claims rest on a single source that could not be read, which the reviewer rated a high-priority coverage gap, and because three claims need correction: the 'inadvertent victim' wording is attributed to Crypto Briefing but is DYORSwap's own framing (claim_findings[1]), the 40% compensation ratio and address are cited to the wrong article (claim_findings[2]), and 'no perpetrators named' leaves out the project's suspect addresses and the Tornado Cash laundering (claim_findings[3], omission_findings[0]). No shutdown, sanction or exploit contradicts the page, and the omissions are minor. The blocked share is a limit on what could be checked, not a defect of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-5,"scored_claims":4,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}