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
- 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. - 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.
- 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
- Sequence
- #4
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 423214563
- Off-chain at
- 2026-05-30T18:52:57.639Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- ACc4Ki3T9jUrXFDyBJwVzG94o9UkgVyiefMoBHs4Hbjm
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1057 chars)
{"actor":"reviewer","decided_at":"2026-05-30T18:52:57.517Z","decision":"review","investigation_id":"58625252-4783-49c8-bbb5-d44243a2b444","new_score":0,"page_slug":"uniswap-google-ad-phishing-campaign-may-2026","prev_score":0,"reason":"The investigation page is substantially accurate and well-sourced, with the large majority of specific financial figures, technical details, wallet addresses, and institutional findings confirmed against the primary SEAL Radar report and multiple independent news outlets. The single material factual error is the misclassification of @ika_xbt as a May 2026 victim when all evidence places that incident in February 2026. Secondary issues include the Hayden Adams timeline date being imprecise by approximately 20 days, the omission of 1inch as a named targeted protocol, and a minor conflation of the general 356 blocked URL figure with the specific March 13-30 tracking window.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}