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_approve · Helius
View on Solana ↗
Sequence
#5
Score
7067 (-3)
Cluster
mainnet-beta
Slot
424142216
Off-chain at
2026-06-04T01:15:17.063Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
6o7Fb5GF4cLqxfM6bgkkD2NPE5Qf2PURnGUoawJv79Ze
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1513 chars)
{"actor":"judge","decided_at":"2026-06-04T01:15:16.820Z","decision":"review_approve","investigation_id":"f145b6a3-7c14-47bc-a047-8fb0ab67e449","new_score":67,"page_slug":"helius","prev_score":70,"reason":"The reviewer examined 32 claims and found 24 confirmed, 5 partially supported, 1 disputed, and 1 unverifiable, producing a disputed_pct of 6.3% — within the 0-10% approval band. The single disputed claim (claim_findings[23]) is in a peripheral section clarifying that Helius Medical Technologies and helius.dev are unrelated entities; the page incorrectly states the company 'changed its ticker to HSDT' when HSDT was always its original ticker — only the company name changed. This error does not affect the core risk assessment of Helius the infrastructure company. A secondary factual error appears in claim_findings[9] and claim_findings[24]: total funding is stated as $34.85M when the arithmetic sum of the three disclosed rounds is $34.35M, overstated by $0.5M with no source support. All material claims about products, funding rounds, founders, the Bitwise ETF partnership, SOC 2 certification, and the workplace conduct allegations are confirmed or well-supported by Tier 1 sources. No link rot was detected. A minor score adjustment of -3 reflects the two documented factual errors, which editors should correct without requiring a formal revision cycle.","score_delta":-3,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}