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 · Coincheck
- Sequence
- #3
- Score
- 74 → 74 (0)
- Cluster
- mainnet-beta
- Slot
- 464344674
- Off-chain at
- 2026-11-02T03:30:16.106Z
- Anchored at
- 2026-11-02T03:30:32.000Z
- Block time
- 2026-11-02T03:30:32.000Z
Independent verification
- 1. Database (off-chain)
- 6g3LhwmWsAQnPqqPNxDeJff1yFPbNba5oGBaLQ6tZ81P
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1365 chars)
{"actor":"reviewer","artifact_identity":"6a8895656edf2181da889f1931b394ba","decided_at":"2026-11-02T03:30:16.015Z","decision":"review","disputed_pct":0.6364,"findings_hash":"4MkhpwjP95WCNroovEjSmatLSr7pSEQp74a3qJBuebfF","investigation_id":"7e0ca938-db80-4669-85f3-f45a238c59f4","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":74,"omissions":{"material":0,"total":2},"page_content_hash":"01fa002ac7edce423a0e5f7994ee2e01a0d7c30ab9ba2cc86752febb315f386d","page_slug":"coincheck","prev_score":74,"reason":"The core narrative holds: the January 2018 NEM hack, the FSA orders, Monex's acquisition, the 2019 license and the 2024 Nasdaq listing all occurred. The sampled details contain several errors: the SPAC closing date (Dec 10, not Dec 5), the compensation start date (Mar 12, not Mar 9), the FSA March order date and count (Mar 8; four other exchanges, not five), a low USD compensation figure, and a mislabeled net-loss period. The entity is still operating. Many hack-mechanics claims were not independently verified.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}