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_revise · SIGMA Bot
- Sequence
- #3
- Score
- 22 → 14 (-8)
- Cluster
- mainnet-beta
- Slot
- 423722395
- Off-chain at
- 2026-06-02T02:51:59.144Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DwvzD63fFvEbTy3bNcn9FunuFmLSZDUkU2G3yK4ECouR
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1620 chars)
{"actor":"judge","decided_at":"2026-06-02T02:51:58.824Z","decision":"review_revise","investigation_id":"cfa54088-9549-4a76-a3e8-6567fa5722af","new_score":14,"page_slug":"sigma-bot","prev_score":22,"reason":"The core incident reporting — the May 11, 2026 drain amount, chains, victim identity, timing, wallet origin analysis, and SIGMA's silence — is confirmed across multiple independent Tier 2 sources and is not in dispute. The reviewer's 15.4% disputed_pct reflects three issues warranting revision: (1) claim_findings[15] flags that a direct quote attributed to Hacken about bulk private key export could not be found in the cited source (hacken.io), which is a citation integrity concern regardless of whether the underlying sentiment is accurate; (2) two instances of link rot on a Tier 1 CoinTelegraph URL (Banana Gun, claim_findings[16]) and a Tier 2 Defiant URL (Unibot, claim_findings[20]) — both are dead but their underlying facts are corroborated by alternative sources; and (3) the summary's characterization that both wallets are 'traceable exclusively to SIGMA's wallet generation infrastructure' (claim_findings[2]) overstates forensic certainty relative to what sources confirm. No status change or delisting is warranted given the page's appropriate epistemic hedging throughout and the strong corroboration of its central claims. Revision should focus on verifying or removing the unlocatable Hacken quote and updating or replacing the two broken citations.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}