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 · ALEX Lab
- Sequence
- #3
- Score
- 56 → 56 (0)
- Cluster
- mainnet-beta
- Slot
- 462188404
- Off-chain at
- 2026-10-27T19:25:55.091Z
- Anchored at
- 2026-10-27T19:26:15.000Z
- Block time
- 2026-10-27T19:26:15.000Z
Independent verification
- 1. Database (off-chain)
- 8mGgpqFS3R4ND5K58KyJV4GwnQfvupVNmbQy8eWSuCcF
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1337 chars)
{"actor":"reviewer","artifact_identity":"5503684f7d6601eec0acf2619015192b","blocked_count":2,"decided_at":"2026-10-27T19:25:54.930Z","decision":"review","disputed_pct":0.2857,"findings_hash":"8zpYMTiio474oqJa94FX569QvFJ6QfUuD1q5VSoKxB2","investigation_id":"de5ce8c2-e704-4380-9344-7a58d9ebba45","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":56,"page_content_hash":"2bca6b6b7f5716668e4e124f7fb93610fc6eab2f7ec1e78cefe70489c07b641f","page_slug":"alex","prev_score":56,"reason":"The claims I could check hold up: the $4.3M figure and bounty terms from CoinDesk, the $3.9M freeze from Cointelegraph, and the June 2025 root cause, $16.18M estimate and audit-scope gap from Halborn. The page hedges the Lazarus attribution appropriately and flags the source discrepancies it found. I could not verify the exchange list, the Lazarus attribution details or the TVL figures. Two timeline entries have no source. I found no disputed claims and no status change that the page omits.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"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}