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 · Cointelegraph
View on Solana ↗
Sequence
#2
Score
44 → 44 (0)
Cluster
mainnet-beta
Slot
426514550
Off-chain at
2026-06-14T23:16:02.178Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
GPh8NVDhVLQub71s25EfDZUiv3qPC9FjmKh1o5iJn7X4
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1814 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:16:02.133Z","decision":"review","investigation_id":"674e90a3-87f1-45b8-a266-ff1084c6dd58","new_score":44,"page_slug":"cointelegraph","prev_score":44,"reason":"Blue-chip calibration review (Prompt A). Verdict: over-penalized. Page content is treated as accurate; the trust_score band is miscalibrated. Cointelegraph is a legitimate, established cryptocurrency news outlet founded in 2013, and the investigation page itself frames both incidents as external attacks on infrastructure controlled by third parties (MailerLite in January 2024; a fraudulent ad network domain in June 2025). Under AVOID.NET's post-policy band semantics, WARNING (20-49) requires elevated fraud/loss risk or an unresolved severe incident. Neither applies: the MailerLite breach was a vendor-side social engineering attack affecting a shared email service used by multiple crypto companies, and Cointelegraph responded promptly; the June 2025 ad system compromise was an ad supply-chain attack also affecting CoinMarketCap simultaneously. The iGaming/SEO controversy (suspected Google manual penalty, Oct 2025) is a real editorial concern — Cointelegraph appears to have allowed a third party to operate casino/gambling content under its domain, which is an integrity lapse — but it does not represent fraud risk to financial users. A score of 62 in CAUTIONARY band correctly captures: legitimate operator with material caveats (two third-party security incidents demonstrating non-trivial attack-surface exposure, plus the iGaming editorial integrity issue), while not misclassifying a globally recognized news organization alongside fraud schemes.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}