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 · ChainSwap
- Sequence
- #4
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 465091272
- Off-chain at
- 2026-11-03T23:55:50.980Z
- Anchored at
- 2026-11-03T23:56:14.000Z
- Block time
- 2026-11-03T23:56:14.000Z
Independent verification
- 1. Database (off-chain)
- FgVGtYHccy1vHok5cR5Td4B4WxkiuBwbbYYQuRSnBdAB
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1469 chars)
{"actor":"judge","artifact_identity":"7aa7910081ebbe78a7809ad82b20562d","band_override":null,"blocked_count":1,"decided_at":"2026-11-03T23:55:50.677Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2,"investigation_id":"7110070c-ef75-4d63-9110-4b2c1b9731b9","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":50,"page_slug":"chainswap","prev_score":50,"reason":"Of 6 claims reviewed, 5 count toward the dispute rate (1 unverifiable claim was excluded because its source blocked the reviewer). One of those 5, the 30-minute fix claim (claim_findings[2]), was not found in the cited Decrypt article, giving a 20% rate. Two further claims were only partially supported: the $4.4M figure is the value held in the attacker's wallet, not confirmed bridge losses (claim_findings[1]), and the summary's 96% token drop conflicts with the 99% in the body (claim_findings[5]). The core narrative of two July 2021 exploits and the attacker's cash-out figures was confirmed. One minor omission (partial recovery with police and OKEx) was noted and no shutdown or sanction contradicts the page. The reviewer checked relatively few sources, so the penalty is kept small.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":5,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}