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 · WEN
- Sequence
- #2
- Score
- 42 → 42 (0)
- Cluster
- mainnet-beta
- Slot
- 461772417
- Off-chain at
- 2026-10-26T18:51:26.605Z
- Anchored at
- 2026-10-26T18:51:51.000Z
- Block time
- 2026-10-26T18:51:51.000Z
Independent verification
- 1. Database (off-chain)
- 5QbawuUyJsfiwvBJfshqdyU9mivFBpzuSYxzvpSPUur9
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1366 chars)
{"actor":"reviewer","artifact_identity":"b33fd9e37cd9b6f55bac3be16964a4ba","decided_at":"2026-10-26T18:51:26.456Z","decision":"review","disputed_pct":0.4545,"findings_hash":"89Fq4mPgNLmrJ6VYkmgHvMB79PbiA965atBWsqfyMRcv","investigation_id":"d2b7e266-d875-476a-a3ad-5c9578fa2aef","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":42,"page_content_hash":"2694ddf80276c3808fc8a0fd7f97a2f2544b3c6a29f798f79861f23b0d7a6689","page_slug":"wen","prev_score":42,"reason":"The core launch narrative holds: the Jan 26 airdrop, the Jan 29 burn of about 272B tokens, the 23% drop, and the current trading range. Two items are wrong. The 40.7% burn figure conflicts with the 27% burn the page states elsewhere and with the roughly 727.7B supply now reported. The summary's 'over 91%' decline from peak should be over 98%. Several claims (the Ovols handover, the December poem date, the wBTC credit, the 70% allocation and the HTX listing date) could not be found in the cited sources. No shutdown, exploit or regulatory action was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}