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 · AscendEX (BitMax)
- Sequence
- #9
- Score
- 23 → 23 (0)
- Cluster
- mainnet-beta
- Slot
- 462057504
- Off-chain at
- 2026-10-27T11:42:00.017Z
- Anchored at
- 2026-10-27T11:42:17.000Z
- Block time
- 2026-10-27T11:42:17.000Z
Independent verification
- 1. Database (off-chain)
- 6MZzvYyE1T34p9asXbiiw8zvVhwnXyRKCQ2qS2x3vYx2
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1562 chars)
{"actor":"reviewer","artifact_identity":"00483b9d7a9a7c117f486ffce5205a55","blocked_count":1,"decided_at":"2026-10-27T11:41:59.532Z","decision":"review","disputed_pct":0.0909,"findings_hash":"8HQB6ARYEptky9bygzVBhNnXYX2ChEDeCC66TAXAUiEt","investigation_id":"a2376978-bfce-4a51-9673-406ac00d7f5d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":23,"omissions":{"material":0,"total":2},"page_content_hash":"247c02edfc81a278562a8787b96160192bd0bf2782a126f68bbbd6485a315773","page_slug":"ascendex-bitmax","prev_score":23,"reason":"The core narrative (June 2026 withdrawal freeze, ZachXBT hot-wallet analysis, $240M outflow, July 1 shutdown, MiCA and failed liquidity deal, July 6 manual-review notice) is well supported by the sources I could read, and the page appropriately caveats cold storage and insolvency. Weaker points are the unsupported 'verified user loss claims in the millions' on July 8, the editorial 'response was appropriate' line, a CoinDesk citation that does not name AscendEX, and two archive links that point at unrelated pages. I could not fetch several sources (BeInCrypto, and I did not open every citation), so many of the 2021 hack details were not independently re-checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"sequence_num":9,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}