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 · Blockchain Bandit
- Sequence
- #3
- Score
- 0 → 0 (-24)
- Cluster
- mainnet-beta
- Slot
- 464361220
- Off-chain at
- 2026-11-02T04:29:34.078Z
- Anchored at
- 2026-11-02T04:29:41.000Z
- Block time
- 2026-11-02T04:29:41.000Z
Independent verification
- 1. Database (off-chain)
- 8mmogZmMKqw1KCsrYJQ5s5DVa3AJXkBaPPJqrqA1Yfqv
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1443 chars)
{"actor":"judge","artifact_identity":"bfe191d89e62948e29fd935806dbaaec","band_override":null,"decided_at":"2026-11-02T04:29:33.852Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5455,"investigation_id":"3dcb72f4-0292-4e27-a1c6-a3df3e0c314f","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"blockchain-bandit","prev_score":0,"reason":"Of 11 reviewed claims, 6 (about 55%) were disputed or could not be verified, which falls in the significant-issues band. claim_findings[0] attributes the 5,000 ETH batch timing to January 2023 when sources place it in December 2024. claim_findings[1], [2], [3], [6] and [7] cite sources that do not contain the stated figures, the ZachXBT attribution for 2023, a 2016 peak, or the 2018-12-31 end date. claim_findings[5] shows the primary ISE source, cited across many sections, now returns 404. The core narrative (732 keys, the January 2023 move, the December 2024 consolidation) is corroborated, and the reviewer's confidence is moderate, so the penalty sits in the middle of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-24,"score_limit":{"applied":-24,"limited":false,"proposed":-24,"rule":"second_opinion_agreed","second":-25},"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}