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 · CBEX (CryptoBridge Exchange)
- Sequence
- #3
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 462052138
- Off-chain at
- 2026-10-27T11:22:35.568Z
- Anchored at
- 2026-10-27T11:23:10.000Z
- Block time
- 2026-10-27T11:23:10.000Z
Independent verification
- 1. Database (off-chain)
- 2NvwrYq4DMsDn1LXT2VdDbuNxcEdaVamo976soJvcVy1
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1339 chars)
{"actor":"reviewer","artifact_identity":"2aeefef4f77230531896e90be5bd8d72","decided_at":"2026-10-27T11:22:35.217Z","decision":"review","disputed_pct":0.125,"findings_hash":"GKoyi9m5hvxbkfkznog9X2VYDzSB1rj7H6E2XVt22L4N","investigation_id":"4da399d3-d15c-481e-a37e-dda4e4d30282","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"omissions":{"material":1,"total":2},"page_content_hash":"289ff36a4a2d7c83120042ff65fdece8967ecda08cf85cd40ee821f25ab6fc58","page_slug":"cbex-cryptobridge-exchange","prev_score":0,"reason":"The core narrative holds: the NFIU loss figure, the SFC alert date, Elliptic's October 2024 laundering finding, the EFCC consultancy-certificate point and the 7 July 2025 arraignment details all match their sources. Problems are small. The 600,000-investor figure is not in the main sources I checked, the SFC wording on Hong Kong is not in the alert, and the page omits the EFCC's retraction of a wrongly named suspect. The page is also more than a year stale on case status.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}