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
review · SIGMA Bot
- Sequence
- #4
- Score
- 14 → 14 (0)
- Cluster
- mainnet-beta
- Slot
- 423844500
- Off-chain at
- 2026-06-02T16:20:06.900Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 5K2WrNSfubmDYqyJeiHh4bTvRFZRMQMYonGPDgvnnjaY
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1200 chars)
{"actor":"reviewer","decided_at":"2026-06-02T16:20:06.774Z","decision":"review","investigation_id":"cfa54088-9549-4a76-a3e8-6567fa5722af","new_score":14,"page_slug":"sigma-bot","prev_score":14,"reason":"The investigation is substantively accurate across its core claims. The May 11, 2026 incident facts — amount, chains, timing, victim identity, analyst attribution, wallet origin pattern, and SIGMA silence — are confirmed by multiple independent news sources. Two dead links (CoinTelegraph 404, The Defiant 403) are flagged but their underlying claims are corroborated by other sources. One notable sourcing error: the Hacken article cited for 'bulk private key export' language does not contain that phrase — similar language appears in KuCoin's Polycule coverage instead, suggesting a misattribution. The terms-and-conditions inaccessibility claim is weakly disputed given search engine indexing. The framing of SIGMA as the root cause is appropriately hedged throughout as an inference from wallet origin correlation, not a confirmed server-side breach.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}