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
- #5
- Score
- 14 → 4 (-10)
- Cluster
- mainnet-beta
- Slot
- 423844516
- Off-chain at
- 2026-06-02T16:20:07.005Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9rkTMqm9zieC8JWeQupVzvuuF2LVDHqkhF7jiHVKjFt8
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1548 chars)
{"actor":"judge","decided_at":"2026-06-02T16:20:06.774Z","decision":"review_revise","investigation_id":"cfa54088-9549-4a76-a3e8-6567fa5722af","new_score":4,"page_slug":"sigma-bot","prev_score":14,"reason":"The investigation's core incident claims — the May 11, 2026 drain amount, chains, timing, victim identity, analyst attribution, and SIGMA's silence — are confirmed by multiple independent Tier 2 news sources across claim_findings[1] through claim_findings[8]. The reviewer's disputed_pct of 13.3% falls in the minor-issues band. Three items require remediation: (1) claim_findings[15] identifies a sourcing misattribution where the 'bulk private key export' quote attributed to Hacken in sections[6] does not appear in the cited Hacken article — similar language originates from KuCoin's Polycule coverage and the quote should be verified or removed; (2) two dead citations need replacement, as the CoinTelegraph Banana Gun URL (claim_findings[27]) returns 404 across three page locations and The Defiant Unibot URL (claim_findings[28]) returns 403; and (3) three high-priority coverage gaps remain open — independent block explorer verification of attacker wallet 0xF7cFFC27732a5C9c4E2D592F3E33435F8dDb019A, a search for additional SIGMA victims beyond Unihax0r, and direct review of SIGMA's Telegram and X channels post-May 11 — any of which could materially change the incident scope assessment.","score_delta":-10,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}