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 · Blockchain Bandit
- Sequence
- #2
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 464361216
- Off-chain at
- 2026-11-02T04:29:33.904Z
- Anchored at
- 2026-11-02T04:29:40.000Z
- Block time
- 2026-11-02T04:29:40.000Z
Independent verification
- 1. Database (off-chain)
- ZF32U19LejaXJ7Xus1WFHDt5CkEZ26r9MfFku6YzZqQ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1474 chars)
{"actor":"reviewer","artifact_identity":"bfe191d89e62948e29fd935806dbaaec","decided_at":"2026-11-02T04:29:33.852Z","decision":"review","disputed_pct":0.5455,"findings_hash":"9h1cCSSt8c7jgiSjcN522F9H5FyEseCKLuQtMyKJUkup","investigation_id":"3dcb72f4-0292-4e27-a1c6-a3df3e0c314f","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_content_hash":"c7242a11f6e32333ae6c613b072dddc2d68aa6058eb4f36d3a09d185eb2ba8ad","page_slug":"blockchain-bandit","prev_score":0,"reason":"The core narrative holds: the ISE disclosure, 732 keys and 49,060 transactions (corroborated by secondary coverage), the January 2023 move per Chainalysis, and the December 2024 consolidation per CoinTelegraph. Problems: the primary ISE URL is dead and cited across many places, so the ISE-specific figures were not verified directly. The 8:54-9:18 PM UTC batch detail is misattributed to 2023 and belongs to December 2024. The ZachXBT and 33%/39% claims about 2023 are not in the cited Chainalysis post. Some timeline dates (2016 peak, 2018-12-31 cessation) are unsupported. I checked a limited sample of claims, and I could not confirm current fund status.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}