Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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
#4
Score
39 → 39 (0)
Cluster
mainnet-beta
Slot
462056134
Off-chain at
2026-10-27T11:36:51.741Z
Anchored at
2026-10-27T11:37:24.000Z
Block time
2026-10-27T11:37:24.000Z

Independent verification

1. Database (off-chain)
CsCLWXj2zys1iM1qGJvXoACKSTk8vZRbW6WAFB4keVvR
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2047 chars)
{"actor":"judge","artifact_identity":"2fdca8e043ccee6ee094ceca38a8f771","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T11:36:51.158Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"1dfb8799-9cd7-4d79-8502-751f5b77eb62","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":39,"page_slug":"coldcard-hardware-wallet","prev_score":39,"reason":"Most core facts check out against the Coinkite advisory and TRM Labs: the affected firmware ranges, the 72-bit entropy figure, the July 30 advisory date and the first-wave losses. However, the patched firmware versions 5.6.1 and 1.5.1Q are contradicted by the official advisory, which lists 5.6.0+ and 1.5.0Q+ (claim_findings[3], [4]). The page also states no class action has been filed, but a proposed class action was filed in Ontario on September 11, 2026 (claim_findings[5], [6]), and it omits Coinkite's reported denial of the 2025 warning. Because the page contradicts the current status of the subject, the penalty is set above what the claim percentage alone implies, while the well-sourced exploit facts keep it a revision rather than a denial.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":12,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"minor","reason":"The raw claim rate (2 disputed of 12 counted, about 17%) implies the minor band. The review reports a material omission and subject_status.contradicts_page is true: a proposed class action was filed in Ontario on 2026-09-11, while the summary, section 4 and the timeline say none exists (claim_findings[5], [6], [7]). Two further findings are marked stale, which the percentage does not count, and a second material omission concerns Coinkite's denial of the May 2025 warning. Judged by the significant band."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}