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 · AscendEX (BitMax)
- Sequence
- #13
- Score
- 49 → 49 (0)
- Cluster
- mainnet-beta
- Slot
- 465076216
- Off-chain at
- 2026-11-03T23:02:07.193Z
- Anchored at
- 2026-11-03T23:02:35.000Z
- Block time
- 2026-11-03T23:02:35.000Z
Independent verification
- 1. Database (off-chain)
- F1hZ4WsrEpAid75pihnsoqL5T4m4RkWnmeWqc6R7LGsT
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1342 chars)
{"actor":"judge","artifact_identity":"5cada73e01377ec3c7c55d696d2d18d0","band_override":null,"decided_at":"2026-11-03T23:02:06.888Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"a2376978-bfce-4a51-9673-406ac00d7f5d","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":49,"page_slug":"ascendex-bitmax","prev_score":49,"reason":"Of six checked claims, one (the AMF blacklist date, claim_findings[5]) could not be verified because the source was not fetched, giving about 17% disputed or unverifiable. The core claims (July 1, 2026 shutdown for lack of MiCA authorization, 2021 hack figures, $240M reserve drop) were confirmed by Tier 2 sources. One wording, describing the $12M+ in Arkham-labeled addresses as 'illiquid tokens tied to the exchange's own ecosystem' (claim_findings[3]), goes beyond the source, which names UNITE and ASD tokens. The shutdown is stated correctly on the page and the one omission (unclear legal entity and insolvency jurisdiction) is minor, so the penalty is kept at the low end of the band.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":13,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}