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 OFT Exploit)
- Sequence
- #4
- Score
- 36 → 36 (0)
- Cluster
- mainnet-beta
- Slot
- 457472447
- Off-chain at
- 2026-10-16T02:34:43.058Z
- Anchored at
- 2026-10-16T02:35:11.844Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- E6S41kvG8Kok8kPGzRag7jJbmPzGSdS59BJyZ7KyxJYK
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2057 chars)
{"actor":"reviewer","artifact_identity":"61d0fb1e55a5aea074cecf31860bb359","decided_at":"2026-10-16T02:34:42.849Z","decision":"review","disputed_pct":0.1579,"findings_hash":"5fJBqRpsZzxksanf7U4Ew8AXtWtuUdtG9Y8i6gaT2fwe","investigation_id":"af1341f6-f129-46eb-9226-bfa047c8932a","mode":"findings_only","new_score":36,"page_content_hash":"12923f23ec1f55ee4280a1d7a187bdcabe119fe99f7685f90206a12fdc84272c","page_slug":"the-sandbox-sand-oft-exploit","prev_score":36,"reason":"The page's central narrative -- an application-level approveAndCall/LayerZero-delegate configuration flaw on The Sandbox's Base and BNB Smart Chain OFT bridge, a headline $49B face-value mint against a real loss of roughly $675-700K, containment, and a 1:1 treasury-funded compensation plan with specific snapshot blocks -- is well corroborated by multiple independent outlets and holds up under independent verification, including a direct fetch of the compensation announcement that confirmed exact block numbers. The broader LayerZero context (KelpDAO, Stake DAO) is also substantially accurate. The clearest defects are: a likely two-day date error for LayerZero's KelpDAO incident report (May 18 vs. the better-attested May 20); a stale '0.01% of supply' impact figure that The Sandbox itself revised to about 0.5% within days, repeated in two places without the revision; an overstated characterization of Brinztech's report as using 'critical' and 'permission flaw' language it does not actually use; and a significant staleness gap in the 'Open items' section, which still presents the Upbit/Bithumb review as unresolved even though it concluded (with warnings lifted and a sharp price rally) well before this review date. One granular on-chain detail (313-day dormant address / Relay Solver funding) could not be independently confirmed and is marked unverifiable rather than disputed, since the page itself hedges it as 'reportedly.'","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}