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 · Bitrefill
- Sequence
- #7
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 461982814
- Off-chain at
- 2026-10-27T07:17:15.086Z
- Anchored at
- 2026-10-27T07:17:33.000Z
- Block time
- 2026-10-27T07:17:33.000Z
Independent verification
- 1. Database (off-chain)
- FKJWkQSSRDxhEpqmBdBGuZZod8r5GzWofGhJaeTVrnV6
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1289 chars)
{"actor":"reviewer","artifact_identity":"1d1a8b2634a905241219ad50d8faa018","decided_at":"2026-10-27T07:17:14.689Z","decision":"review","disputed_pct":0.1,"findings_hash":"CPF8DX3LXiiJ1DZNUFUNs9tPgCAMxyTnNmHXuC9tcfZX","investigation_id":"8038ecc2-39f1-4530-bfdf-f87bf4b49de2","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":52,"omissions":{"material":0,"total":1},"page_content_hash":"881751ee9aba6cbeb746dd44fb93863ee4e63c92e1c609e721e7137edbeb6a07","page_slug":"bitrefill","prev_score":52,"reason":"The incident narrative (date, vector, 18,500 records, about 1,000 encrypted names, undisclosed loss, disclosure on March 17) is well supported by CoinDesk and The Block. The page states the Lazarus attribution slightly more firmly than Bitrefill's own tentative wording. The company-overview figures (900 carriers, 170 countries) are not supported by the cited Coin Bureau page. The entity appears to be operating. No critical omissions found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":7,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}