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
- 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. - 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.
- 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 (HNT)
- Sequence
- #2
- Score
- 58 → 58 (0)
- Cluster
- mainnet-beta
- Slot
- 423639869
- Off-chain at
- 2026-06-01T17:45:18.240Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 95q5SLLq4HUUmixA7S4j76MzecdH5P5Yx2aYvkwtWeqx
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1008 chars)
{"actor":"reviewer","decided_at":"2026-06-01T17:45:18.143Z","decision":"review","investigation_id":"2c5e9484-d7b6-4097-872d-dcf549c266de","new_score":58,"page_slug":"helium","prev_score":58,"reason":"The page is broadly accurate and well-sourced. The most material recurring error is characterizing the Series D '$1.2 billion' figure as a pre-money valuation when multiple primary sources indicate it was the post-money figure (pre-money was $1 billion). The SEC settlement date cited as April 10, 2025, is the announcement date; the actual court-entered final judgment was April 23, 2025, and the page cites the complaint release (lr-26229) rather than the settlement release (lr-26291). AT&T is incorrectly grouped as a June 2024 carrier launch partner when it joined in April 2025. No claims were found to be outright disputed or contradicted by credible sources.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}