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
- Sequence
- #3
- Score
- 30 → 26 (-4)
- Cluster
- mainnet-beta
- Slot
- 462186216
- Off-chain at
- 2026-10-27T19:17:59.730Z
- Anchored at
- 2026-10-27T19:18:27.000Z
- Block time
- 2026-10-27T19:18:27.000Z
Independent verification
- 1. Database (off-chain)
- ArtfaHHi24w4xKvdD9y47fDH7kK38vEumNVGV8oMai9b
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2074 chars)
{"actor":"judge","artifact_identity":"e7d67876811513d998fc24d719b8ab67","band_override":null,"decided_at":"2026-10-27T19:17:59.379Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2727,"investigation_id":"015d6932-0e47-455d-8215-8980f8872a47","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"mid-tier-exchange-closure-wave-2026-ascendex-bitmex-bitmart-coinex","prev_score":30,"reason":"The core dates and terms for all four closures check out (claim_findings[0], [1], [6], [7], [10]), and the subject status is consistent with the page. About 27% of claims were disputed or unverifiable: the CoinEx fee is described as compounding although it is a flat percentage (claim_findings[2]), and the 'largest cluster in history' and BitMart 'unsecured creditors' statements have no support (claim_findings[8], [9]). Two further claims are overstated: the BitMart withdrawal freeze and the Binance EU stop (claim_findings[4], [5]). The page also omits BitMart's restructuring pivot and AscendEX's insolvency warning, both material, so the page is rated as having significant issues and needs correction.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-4,"score_limit":{"applied":-4,"limited":true,"proposed":-18,"rule":"limited_no_second_opinion","second":null},"sequence_num":3,"severity_override":{"applied":true,"band":"significant","from_band":"minor","reason":"Computed disputed_pct is 27% (1 disputed + 2 unverifiable of 11 findings, none source_blocked), which is the minor band. Two material omissions (BitMart restructuring pivot, AscendEX insolvency warning) concern the two exchanges the page flags as highest risk, and there is a high-priority coverage gap on post-September BitMart developments. Together with partially supported claims on the BitMart freeze and Binance EU stop, the minor band understates the problem."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}