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 · The Sandbox (SAND)
- Sequence
- #2
- Score
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 443510441
- Off-chain at
- 2026-08-25T02:53:06.255Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AjidbyibWeW4RS6i1T6seqxNCp8ghTisdjsmi2p2RUm6
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1664 chars)
{"actor":"reviewer","decided_at":"2026-08-25T02:53:06.149Z","decision":"review","investigation_id":"c755b6a4-dcf8-43cf-9777-53595004dc81","new_score":38,"page_slug":"the-sandbox-sand","prev_score":38,"reason":"The page's core narrative about the August 2026 SAND OFT bridge exploit -- mechanism (approveAndCall/LayerZero delegate hijack), scale (329.24T minted, 703 events, 173 addresses), real economic loss (~$675K / ~79.74 ETH), containment, and background on The Sandbox/Animoca and the 2025 restructuring and 2023 phishing breach -- is well supported by multiple independent, topically relevant sources and was independently corroborated in this review. No claims were found to be disputed or contradicted by more credible sources, and no dead links were encountered among the URLs actually fetched. Several claims are only partially supported due to minor cross-source numeric discrepancies (transaction counts/timing of the ETH drain, differing 24-hour price-change figures), an editorializing timeline entry that implies the Coinbase futures delisting was 'in connection with' the exploit when reporting suggests a routine, separately-scheduled review, and a framing of the 2026 LayerZero incident pattern that understates the infrastructure-level nature of the KelpDAO root cause. A handful of granular figures (exact adapter balances, one wallet's SAND holding, DAU/treasury figures) could not be independently verified within this review's search budget, in part due to CoinDesk rate-limiting automated fetches.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}