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
- #8
- Score
- 11 → 11 (0)
- Cluster
- mainnet-beta
- Slot
- 462277230
- Off-chain at
- 2026-10-28T00:41:37.669Z
- Anchored at
- 2026-10-28T00:41:50.000Z
- Block time
- 2026-10-28T00:41:50.000Z
Independent verification
- 1. Database (off-chain)
- 3M5wPCChG8bUQkzEg9zUpHxzxQnDN1zvQ9pUZzkd5VJc
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1731 chars)
{"actor":"reviewer","artifact_identity":"03f137d8d9247b3ac7c687e3eddceeca","blocked_count":2,"decided_at":"2026-10-28T00:41:37.551Z","decision":"review","disputed_pct":0.2,"findings_hash":"YdHeZtDCgi6MqmudbhKmaNNm7iDkjgseWgkL1sapBud","investigation_id":"a9cdc7b5-15a1-4e71-857b-15faed45731b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":11,"omissions":{"material":0,"total":1},"page_content_hash":"887b6fc1d2f6c390ba33123ae87524d2b014dd8dc0321f435f278b1340962783","page_slug":"coldcard-coinkite-firmware-seed-entropy-exploit-multi-actor-august-2026","prev_score":11,"reason":"The technical account (March 2021 libNgU error, entropy estimates, fixed versions, migration advice), the O'Beirne allegation and the Ontario class action all match what I could fetch, and are appropriately hedged. Problems are narrow. The 2026-08-04 timeline entry pairs a $140M headline figure with the 1,596 BTC tally, which the same-day Galaxy report puts near $100M. The 41-minute first-wave detail is not in its cited Cointelegraph article, and the destroyed-stock claim is not in Coinkite's disclosure. The Novak apology quote and the 8,865-address tally could not be checked because sources were empty or blocked. The Coinkite backgrounder's inline update is Aug 1 but its publication date is July 30. The subject appears to be operating, with no contradiction by current status.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":8,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}