Skip to main content
AVOID.NET
← 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 · Unicoin
View on Solana ↗
Sequence
#5
Score
26 → 26 (0)
Cluster
mainnet-beta
Slot
456641465
Off-chain at
2026-10-14T00:34:45.124Z
Anchored at
2026-10-14T00:35:05.156Z
Block time
—

Independent verification

1. Database (off-chain)
3kBD4nwxfv6iNB81Upg2fMM2Gf3VgczLxdQCiPjJJ4mv
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1010 chars)
{"actor":"reviewer","artifact_identity":"3e1dc73e6bea1f0e9d52810337fde461","decided_at":"2026-10-14T00:34:44.829Z","decision":"review","disputed_pct":0.5,"findings_hash":"7iEyCvvTFzNNe4K1Qp9GiG29Pvs2NcTjzJPi2njYpLJR","investigation_id":"d7e8a952-0d3a-4635-b2fb-1f25cda1eac5","mode":"findings_only","new_score":26,"page_content_hash":"75db60e7553ffe01107fe8bd7d98923b716ebfc4eefc2441d329f8aff7d5ee07","page_slug":"unicoin","prev_score":26,"reason":"The core SEC allegations, figures, charges and Devlin settlement match the SEC press release, litigation release and complaint. One factual error was found: the planned token launch date is shown as September 28, 2026, but the official site says November 24, 2026. The 'as of June 2026' litigation status is stale or unverifiable, and Moschini's role description is slightly off. The CEO background section is unchecked.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}