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.
- Sequence
- #2
- Score
- 20 → 20 (0)
- Cluster
- mainnet-beta
- Slot
- 462186550
- Off-chain at
- 2026-10-27T19:19:13.065Z
- Anchored at
- 2026-10-27T19:19:38.000Z
- Block time
- 2026-10-27T19:19:38.000Z
Independent verification
- 1. Database (off-chain)
- vBEZQqgiRiG1Ga2S53iqrNZUrozGLw3aHicq2R9yNtc
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1417 chars)
{"actor":"reviewer","artifact_identity":"c73b5b81eaa9534a22b21749a8a7e06d","blocked_count":1,"decided_at":"2026-10-27T19:19:12.864Z","decision":"review","disputed_pct":0.25,"findings_hash":"4EWJxF4ADgmMgLGxaAsGLz7ATP1cHedNGpHwXgfTafgK","investigation_id":"2e8494c6-57c9-4f11-b28f-f16c12c1151e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":20,"omissions":{"material":0,"total":2},"page_content_hash":"ec9699ea52d066cfe6cc8784736ff7cd095f58e75313f7f94c4cd46f6f6b64e4","page_slug":"coldcard-firmware-vulnerability-standalone-investigation","prev_score":20,"reason":"The core technical and financial narrative is consistent with Coinkite's advisory and secondary reporting. One clear error: the 5.6.1/1.5.1Q timeline entry is dated 2026-08-01 but was published about 2026-08-20, contradicting the page's own 'three weeks later' text. That entry is also out of chronological order. The double SHA-256 detail was not found. The passphrase mitigation is somewhat overstated. Several secondary-source figures could not be fully checked (403 on Crypto Times).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":2,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}