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_revise · Helius
- Sequence
- #3
- Score
- 78 → 70 (-8)
- Cluster
- mainnet-beta
- Slot
- 423639847
- Off-chain at
- 2026-06-01T17:45:17.326Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- H2kvmL1UNJESWotSp4TireaA4wTJJFLi62YdxUypyCCW
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1336 chars)
{"actor":"judge","decided_at":"2026-06-01T17:45:17.107Z","decision":"review_revise","investigation_id":"f145b6a3-7c14-47bc-a047-8fb0ab67e449","new_score":70,"page_slug":"helius","prev_score":78,"reason":"The review assessed 42 claims and found a disputed_pct of 11.9%, placing this page in the minor-issues band. Two claims were formally disputed: claim_findings[15] incorrectly states Gatekeeper launched 'in late 2025' when the public beta was announced February 2026 (confirmed by the official Helius blog); and claim_findings[31] inverts the HSDT ticker narrative, stating the company 'changed its ticker to HSDT' when HSDT was the pre-existing ticker that was retained after renaming. Additionally, the total funding figure of $34.85M (stated in claim_findings[12] and timeline[5]) overstates the arithmetic sum by $0.5M — multiple Tier-1 databases confirm $34.35M. All three errors are precision issues in peripheral or contextual claims; no core trust-signal claims (regulatory history, client list, funding rounds individually, team identity) were disputed. Reviewer confidence of 0.82 supports a moderate penalty. Page should be revised to correct the three identified factual errors.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}