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.
- Sequence
- #4
- Score
- 30 → 30 (0)
- Cluster
- mainnet-beta
- Slot
- 462278580
- Off-chain at
- 2026-10-28T00:46:28.469Z
- Anchored at
- 2026-10-28T00:46:37.000Z
- Block time
- 2026-10-28T00:46:37.000Z
Independent verification
- 1. Database (off-chain)
- HTP9z7zZhRCUyzaa4dLFEtP1YS5k8bkv5fMGDnmgFpyY
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1362 chars)
{"actor":"reviewer","artifact_identity":"bdd2e78c57b9baf1a11f48d8730a3f9a","blocked_count":1,"decided_at":"2026-10-28T00:46:28.374Z","decision":"review","disputed_pct":0,"findings_hash":"GzhGyUSW8FJ1MepuRRgUdT9fnXTRgWTr6tvjyVgQz5iE","investigation_id":"f148389b-fbdf-4f1b-9c26-b291f88ef903","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":30,"omissions":{"material":0,"total":1},"page_content_hash":"74be87faf6e859940c61a0c8208732a22719314ba9249b38d3027976ea5b617d","page_slug":"bitget-exchange-september-2026-backend-hack-387-5m","prev_score":30,"reason":"Sampled core claims hold up: the loss figures and revision, the Protection Fund, the SlowMist/Mandiant root cause, the timestamps and the hedged North Korea attribution all match sources I read. Remaining findings are minor: a UTC versus UTC+8 date ambiguity, a few details I could not confirm because BleepingComputer was blocked, and laundering-route figures that I did not verify. I found no material omissions. Bitget remains operating.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":13,"sequence_num":4,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}