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_approve · Bitget Exchange — September 2026 Backend Hack ($387.5M)
- Sequence
- #5
- Score
- 30 → 30 (0)
- Cluster
- mainnet-beta
- Slot
- 462278588
- Off-chain at
- 2026-10-28T00:46:28.637Z
- Anchored at
- 2026-10-28T00:46:38.000Z
- Block time
- 2026-10-28T00:46:38.000Z
Independent verification
- 1. Database (off-chain)
- 8zL8ZmM21JnD5Cz5FUCeZc9rVrqL7WZbaVzvaHoxM4fU
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1418 chars)
{"actor":"judge","artifact_identity":"bdd2e78c57b9baf1a11f48d8730a3f9a","band_override":null,"blocked_count":1,"decided_at":"2026-10-28T00:46:28.374Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"f148389b-fbdf-4f1b-9c26-b291f88ef903","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":30,"page_slug":"bitget-exchange-september-2026-backend-hack-387-5m","prev_score":30,"reason":"Of 14 claim findings, none were disputed and none were unverifiable apart from one (claim_findings[4]) that could not be read because the source blocked the reviewer; that finding is excluded from the calculation, giving 0% disputed. Core claims hold: loss figures and revision (claim_findings[5]), the Protection Fund (claim_findings[6]), the SlowMist and Mandiant root cause, and the hedged North Korea attribution (claim_findings[7], [9]). Three findings were partially supported, mainly a UTC versus UTC+8 date ambiguity (claim_findings[1], [13]). The only omission is minor and Bitget is still operating, so no escalation applies. The blocked source is a coverage limit, not a defect of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":13,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}