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 · Haruko
- Sequence
- #3
- Score
- 62 → 62 (0)
- Cluster
- mainnet-beta
- Slot
- 464299918
- Off-chain at
- 2026-11-02T00:50:22.932Z
- Anchored at
- 2026-11-02T00:50:43.000Z
- Block time
- 2026-11-02T00:50:43.000Z
Independent verification
- 1. Database (off-chain)
- 3F1ZgdhL5dnD2mjC1ofMZhKt3cAzxMwbNiyUKvP7U6xY
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1408 chars)
{"actor":"reviewer","artifact_identity":"d540fb417f41da35d77a28058caa49e7","decided_at":"2026-11-02T00:50:22.866Z","decision":"review","disputed_pct":0.5,"findings_hash":"6DEiU8x3fpxnBcrku1qXidqsxRxp7zScxDX3zUPHfSSM","investigation_id":"e3c2ffbe-d630-4133-ba9e-c7a1013ddc3a","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":62,"omissions":{"material":1,"total":1},"page_content_hash":"263bfcae6ae4711a2c25eb79a811f489a104e8a809ddc121c03e6c23ad751c26","page_slug":"haruko","prev_score":62,"reason":"The core incident facts (15 clients, targeted attack, token extraction, patch, secret rotation, promised post-mortem), the funding details and the client list match CoinDesk and Tech.eu. The page overstates the funds loss as 'confirmed' when sources attribute it to unnamed sources, and it presents the bare-metal point as multiple reports when CoinDesk cites one source. The March 2021 incorporation date was not verified. The page is stale on the post-mortem, which was still unpublished on October 2. The TRM figures and the regulatory negative were not checked.","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}