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 · Helius
View on Solana ↗
Sequence
#4
Score
70 → 70 (0)
Cluster
mainnet-beta
Slot
424142212
Off-chain at
2026-06-04T01:15:16.953Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
7P2zMk9dkRa9jXmtuU8FHscauEXZcb4NPMXdPJyUPN1Y
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (935 chars)
{"actor":"reviewer","decided_at":"2026-06-04T01:15:16.820Z","decision":"review","investigation_id":"f145b6a3-7c14-47bc-a047-8fb0ab67e449","new_score":70,"page_slug":"helius","prev_score":70,"reason":"The Helius investigation page is largely accurate and well-sourced across its core claims about funding, products, and the CEO conduct allegations. The primary factual errors are: (1) total funding stated as $34.85M when arithmetic and multiple sources support $34.35M (a $0.5M overstatement); (2) an incorrect claim that Helius Medical Technologies 'changed its ticker to HSDT' when HSDT was always its ticker — only the company name changed. No link rot was detected. The unverifiable claim (90-day incident breakdown) is a specificity issue with the StatusGator source, not a contradiction.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}