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 · The Sandbox (SAND)
- Sequence
- #3
- Score
- 38 → 30 (-8)
- Cluster
- mainnet-beta
- Slot
- 443510445
- Off-chain at
- 2026-08-25T02:53:06.350Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7qWZJYFzgQqjAbci5fsLm4ATMvnLKDnSRNrk9x7UwEqx
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1574 chars)
{"actor":"judge","decided_at":"2026-08-25T02:53:06.149Z","decision":"review_revise","investigation_id":"c755b6a4-dcf8-43cf-9777-53595004dc81","new_score":30,"page_slug":"the-sandbox-sand","prev_score":38,"reason":"The reviewer's summary block understated the claim count (27 claims, 3 unverifiable, 11.1% disputed_pct) relative to the actual claim_findings array it produced, which contains 29 individually adjudicated claims: 20 confirmed, 7 partially supported, 2 unverifiable, and 0 disputed. Recounting from that authoritative array gives (0 disputed + 2 unverifiable) / 29 = 6.9%, which falls in the 0-10% approve band rather than the 10-30% band the summary implied. No claim was found disputed or contradicted, and the core narrative -- exploit mechanism, scale, real dollar losses, and containment -- is confirmed across multiple independent outlets. However, the review also surfaced a high-priority coverage gap (no on-chain/block-explorer citations for the page's most load-bearing numeric figures) and several substantive partially-supported findings, most notably a timeline entry implying the Coinbase futures delisting was announced 'in connection with' the exploit when the cited reporting instead points to a routine, separately-scheduled review. That framing risks misleading readers about causation and, combined with the sourcing gap, is enough to warrant a light revision rather than an unconditional approval.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}