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 · SpaceX Brand Crypto Fraud
View on Solana ↗
Sequence
#6
Score
0 → 0 (0)
Cluster
mainnet-beta
Slot
423942132
Off-chain at
2026-06-03T03:07:36.702Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
TTtec3Hhf5NP72CSRCfZg5fRRqVo4eC81XN5HVxyzYA
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1233 chars)
{"actor":"reviewer","decided_at":"2026-06-03T03:07:36.610Z","decision":"review","investigation_id":"f7a5a76a-4d6d-4111-865d-48e7733d9b52","new_score":0,"page_slug":"spacex-brand-crypto-fraud","prev_score":0,"reason":"The page's core factual record — campaign start dates, specific loss figures for documented incidents, platform details, and technical mechanisms — is well-supported by cited sources. The principal accuracy issues are: (1) the FTC '46,000 people / $1 billion' statistic is attributed to the May 2021 FTC data spotlight, which does not contain those figures; the correct source is the June 2022 FTC report; (2) the Robinhood section heading labels the incident as '(2024)' when multiple high-credibility sources confirm the events occurred in June-July 2025; and (3) the 164,000 concurrent viewer figure for the April 2024 solar eclipse incident is not supported by the OECD.AI source cited. One Trend Micro URL has permanently redirected to trendlife.com. The aggregate 'tens of millions' loss figure in the summary is not independently verifiable from the sources provided.","score_delta":0,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}