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_approve · SIGMA Bot
- Sequence
- #7
- Score
- 4 → 4 (0)
- Cluster
- mainnet-beta
- Slot
- 423953612
- Off-chain at
- 2026-06-03T04:23:53.076Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AoAfWrWcUXYgHmhE1yZUEJAAgvCVBKNveYAMqgD2M9QF
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1237 chars)
{"actor":"judge","decided_at":"2026-06-03T04:23:52.659Z","decision":"review_approve","investigation_id":"cfa54088-9549-4a76-a3e8-6567fa5722af","new_score":4,"page_slug":"sigma-bot","prev_score":4,"reason":"The reviewer found 23 of 28 claims confirmed, 4 partially supported, and zero outright disputed, yielding a disputed_pct of 4% — within the 0–10% approval band. The four partially-supported findings (claim_findings[1], [13], [21], [24]) reflect minor precision gaps in causal inference language and one unverified verbatim quote, not factual contradictions. Two dead source URLs (claim_findings[16] link_rot finding: CoinTelegraph 404; Defiant 403) affect comparison-section citations only, and the underlying facts they support are independently confirmed by working Tier 2 alternates. Two high-priority coverage gaps — on-chain wallet trace for 0xF7cFFC27732a5C9c4E2D592F3E33435F8dDb019A and direct inspection of SIGMA's post-incident communication channels — are noted for future expansion but do not undermine the page's published claims. Reviewer confidence of 0.82 supports approval.","score_delta":0,"sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}