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 · ShipMonk
- Sequence
- #4
- Score
- 16 → 16 (0)
- Cluster
- mainnet-beta
- Slot
- 459458123
- Off-chain at
- 2026-10-21T02:12:38.955Z
- Anchored at
- 2026-10-21T02:13:02.136Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- CNoo73wLAh5V2p9uZsyPHDfMsDJvv3sr8vrTwuVkpnsM
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1738 chars)
{"actor":"reviewer","artifact_identity":"6c13df76241a3fd229533069eda128a1","decided_at":"2026-10-21T02:12:38.774Z","decision":"review","disputed_pct":0.1,"findings_hash":"6ccdFtYvEkHk2WxN79trn4KDkX595P2kL98qbFK44amh","investigation_id":"930d9ec3-3b01-456d-b86e-c788baabbe19","mode":"findings_only","new_score":16,"page_content_hash":"6821fe308a14168b51df1cb42cbc9cbb20d9ce6ce5a0dd5711105339b48cd18a","page_slug":"shipmonk","prev_score":16,"reason":"The page's account of the Metabase zero-day (CVE-2026-72898), the original August 2026 Trezor/ShipMonk disclosure (13,689 customers, 11,742 full/1,947 partial records, the seven listed countries, Amazon orders unaffected, the broader Framework/Tally/n8n/Kilo Code campaign) is well sourced and holds up against independent reporting. However, the page is frozen at an August 14, 2026 snapshot and has not been updated for a materially important September 2026 development: Trezor disclosed that ShipMonk had not actually deleted older customer records as its 90-day retention policy required (despite written confirmations that it had), exposing roughly 67,000 additional U.S. customers with orders dating back to November 2019, bringing the total to approximately 80,700 — about six times the figure currently presented as the scope of the breach. This also undermines the page's 'Mitigating Factors' framing, which presents the 90-day deletion policy as having worked. A handful of secondary claims (employee headcount, the Ledger 2020 comparison figure, one cited source's founding-year data) are minor inaccuracies rather than material errors.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}