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 · Amazon Web Services
View on Solana ↗
Sequence
#2
Score
75 → 75 (0)
Cluster
mainnet-beta
Slot
423951601
Off-chain at
2026-06-03T04:10:32.506Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
CmmwukktQJBUqggD6hkVm2uvgTr5p5Hnjs6ZKiFuwDKg
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1216 chars)
{"actor":"reviewer","decided_at":"2026-06-03T04:10:32.383Z","decision":"review","investigation_id":"8b30f4bf-6cf5-4ebe-9a2d-168e5d641f39","new_score":75,"page_slug":"amazon-web-services","prev_score":75,"reason":"The page is broadly factual and most individual claims are confirmed by credible sources. The primary accuracy problem is the summary's 38% cloud market share figure, which overstates AWS's position relative to current analyst consensus of 28-31% for the broader infrastructure market. Several other claims are partially supported: the October 2025 outage cause description follows a secondary source's simplification rather than AWS's own postmortem, the Capital One breach characterization overstates SSN/bank account exposure breadth, the Alteryx household count is slightly understated (120M vs 123M), and the BIPA litigation section does not reflect the May 2026 Third Circuit dismissal of the federal case. One claim about internal GenAI memos could not be verified against the cited secondary sources. No link rot was detected across the sources checked.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}