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 · Gemini Exchange
View on Solana ↗
Sequence
#5
Score
44 → 58 (+14)
Cluster
mainnet-beta
Slot
426514806
Off-chain at
2026-06-14T23:16:15.224Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
Cx1NAJ5E9CCJnFtRuiw4c8agU34tZdm2LpVq1d4bE4iw
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1591 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:15.117Z","decision":"review_approve","investigation_id":"c7183845-f827-4fbf-bee3-76a2ad31fbbf","new_score":58,"page_slug":"gemini","prev_score":44,"reason":"This is a severity-calibration review, not a fact-dispute review — all claim_findings[0–5] were returned as 'supported' with 0% disputed. The calibration review found the current score of 44/WARNING over-penalizes a legitimately regulated, NYDFS-chartered, Nasdaq-listed entity. The three principal risk factors driving the WARNING band have materially changed: claim_findings[0] confirms Earn customers received 232% in-kind recovery and the SEC dismissed its case with prejudice in January 2026; claim_findings[2] confirms the CFTC itself filed a motion to vacate its own $5M penalty in May 2026 citing changed enforcement standards; and claim_findings[3] confirms the 2022 data breach originated in third-party infrastructure (Twilio/Authy), not Gemini's own systems. Real ongoing concerns — an active securities class action (claim_findings[5]), $582M net loss, 80%+ post-IPO stock decline, and simultaneous CFO/COO/CLO departures — support a CAUTIONARY rather than WARNING or VERIFIED band. A score of 58/CAUTIONARY accurately reflects a licensed, publicly accountable entity with significant but non-fraudulent business and legal headwinds. Score is adjusted +14 to move from 44 to 58. Page content stands accurate and remains published.","score_delta":14,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}