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 · JaredFromSubway.eth MEV Bot - Counter-Honeypot Exploit
- Sequence
- #3
- Score
- 10 → 0 (-15)
- Cluster
- mainnet-beta
- Slot
- 465102678
- Off-chain at
- 2026-11-04T00:36:35.254Z
- Anchored at
- 2026-11-04T00:37:00.000Z
- Block time
- 2026-11-04T00:37:00.000Z
Independent verification
- 1. Database (off-chain)
- HUpBYDD8daDYULvHDtfwyDtNEWRWj1zvGyyqeUkdAANN
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1461 chars)
{"actor":"judge","artifact_identity":"c1cd6b20f74be1242119e51b5c2d6599","band_override":null,"decided_at":"2026-11-04T00:36:34.955Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"4cab0096-1bed-44a7-a426-9d3d147f7d95","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":0,"page_slug":"jaredfromsubway-eth-mev-bot-counter-honeypot-exploit","prev_score":10,"reason":"The core event (a roughly $7.5M drain on June 20, 2026, followed by a 50% bounty offer and legal threat) is confirmed by CoinDesk and Decrypt (claim_findings[0], [3]). However, 4 of 8 claims (50%) could not be verified: the 66 fake contracts and 97 blocks (claim_findings[1], where CoinDesk says only 'dozens'), the impersonator account (claim_findings[4]), the Tornado Cash figures (claim_findings[5]) and the Vitalik Buterin sandwich (claim_findings[6]). The page also contradicts itself on PEPE-era profits (claim_findings[7]) and does not note conflicting loss figures across outlets. The reviewer's confidence was low and the review was time-boxed, with no claim directly disputed, so the penalty is set at the mild end of the band; the page is revised rather than denied.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":-15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}