Skip to main content
Sign in
← 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.

Decision
review_approve · Coinbase
View on Solana ↗
Sequence
#5
Score
3662 (+26)
Cluster
mainnet-beta
Slot
426514344
Off-chain at
2026-06-14T23:15:51.492Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
CsvnyHWxQ51nq4op9Dmdn379XpXexDHJFkespQu7pbmi
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1533 chars)
{"actor":"judge","decided_at":"2026-06-14T23:15:51.352Z","decision":"review_approve","investigation_id":"34a1d395-ed34-4277-a8ff-7adb35a32f66","new_score":62,"page_slug":"coinbase","prev_score":36,"reason":"All six claim findings (claim_findings[0]-[5]) are supported with 0% disputed content. The page accurately documents Coinbase's history and is not in question. The sole issue is whether the current WARNING-band score (36) correctly reflects the entity's risk profile. The review establishes with high confidence (0.88) that it does not: the most material regulatory risk (SEC enforcement action) was dismissed 2025-02-27 (claim_findings[1], [5]); the May 2025 data breach was suffered at the hands of bribed contractors, not perpetrated by Coinbase (claim_findings[2]); $300M+ in annual social-engineering losses are attributable to third-party external scammers, not Coinbase's own conduct (claim_findings[4]); and the CFTC and NYDFS penalties are fully resolved settled actions (claim_findings[3]). Legitimate residual concerns — AML/KYC compliance history, ongoing user-safety exposure, and Base blockchain controversies — place the entity in the CAUTIONARY band (50-69). A corrected score of 62 reflects documented negligence-class failures without entity-level fraud or unresolved shutdown risk. The page remains published and accurate; the trust score band is corrected upward.","score_delta":26,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}