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_revise · Helium Mobile
View on Solana ↗
Sequence
#3
Score
58 → 48 (-10)
Cluster
mainnet-beta
Slot
423639867
Off-chain at
2026-06-01T17:45:17.834Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
GLkzVzK1JQy2R3UeisAxdyebvE38Djg9pw8ShKELvn9v
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1195 chars)
{"actor":"judge","decided_at":"2026-06-01T17:45:17.661Z","decision":"review_revise","investigation_id":"8b1b9eab-eed2-4072-94e6-38436e552dab","new_score":48,"page_slug":"helium-mobile","prev_score":58,"reason":"The review confirmed all high-severity claims — SEC fraud settlement, MOBILE token deprecation via HIP 138, broken pricing promises, and Zero Plan discontinuation — against Tier 1 and Tier 2 sources. Two factual errors were identified in the network infrastructure sections: claim_findings[17] places the 98,000 hotspot figure at Q4 2025 when Messari data shows it was the Q2 2025 figure (year-end 2025 was 120,000+), and claim_findings[28] conflates Q1 2025 new-hotspot start/end counts with a different total that includes converted legacy hotspots. These are supporting metrics, not core allegations, which limits their severity. The disputed_pct of 14.7% and two high-priority coverage gaps — particularly the May 2026 CEO public controversy that postdates the page — support a revise verdict with a moderate penalty rather than denial.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}