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 · Multichain
- Sequence
- #3
- Score
- 32 → 32 (0)
- Cluster
- mainnet-beta
- Slot
- 465090111
- Off-chain at
- 2026-11-03T23:51:43.265Z
- Anchored at
- 2026-11-03T23:52:02.000Z
- Block time
- 2026-11-03T23:52:02.000Z
Independent verification
- 1. Database (off-chain)
- FqLZdNTa4STi6DYhGZTfNSBujugxV3iFNkUtSREad6Z9
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1244 chars)
{"actor":"reviewer","artifact_identity":"38a4484fb743985686c07704320ef6de","decided_at":"2026-11-03T23:51:43.193Z","decision":"review","disputed_pct":0.1667,"findings_hash":"HFhxgLXZnMdTN19nRCFEcJcudTpFperTcngTyhbrHRPx","investigation_id":"a7494e2f-bbed-4892-a2cc-55eee9a00bae","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":32,"omissions":{"material":1,"total":1},"page_content_hash":"aabdd20ec72a568a1ff9a0915a3226c8adfbfc63a43f48001e59ce43136502c7","page_slug":"multichain","prev_score":32,"reason":"The core narrative (CEO detention, about $126M drain, shutdown on 2023-07-14, Singapore damages award) matches the sources checked. Issues: the Singapore court 'finding' on CEO control appears to be the claimant's position in a default judgment, the $265M total is not in the cited Chainalysis post, and the page misses the May 2025 liquidation order. Only a small sample of claims was checked.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","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}