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

Independent verification

1. Database (off-chain)
C3SJqcTiNqHqpp48WpecjA4VAcoqSXRMPUsjMzsM5BpV
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1283 chars)
{"actor":"reviewer","decided_at":"2026-06-01T17:45:17.661Z","decision":"review","investigation_id":"8b1b9eab-eed2-4072-94e6-38436e552dab","new_score":58,"page_slug":"helium-mobile","prev_score":58,"reason":"The investigation page is factually well-grounded on its most important claims: the SEC enforcement action, settlement terms, HIP 138 MOBILE token deprecation, Coinbase delisting, AT&T partnership, and Zero Plan/pricing changes are all confirmed. Two material factual errors were identified: (1) the hotspot count of '98,000 as of Q4 2025' is incorrect — this was the Q2 2025 figure; year-end 2025 hotspot count was 120,000+; and (2) the hotspot expansion characterization '28,100 at the start of [Q1 2025]' is slightly off — that was the Q1 end count, not the start. The page also omits the May 2026 CEO 'parasites' controversy, which is the most recent significant reputational event. The trust_score direction (high concern) is calibrated appropriately given confirmed SEC fraud settlement, confirmed pattern of broken pricing promises, and confirmed token deprecation that materially changed the product's core reward proposition.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}