Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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.

Sequence
#4
Score
42 → 42 (0)
Cluster
mainnet-beta
Slot
457482821
Off-chain at
2026-10-16T03:12:09.454Z
Anchored at
2026-10-16T03:12:25.027Z
Block time
—

Independent verification

1. Database (off-chain)
DwTd72kK988YKmhnyya6xEEfcU48mEsvMeaZXQg8hypD
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1963 chars)
{"actor":"reviewer","artifact_identity":"602d2a51daaf74e71e3ed4fb9abd9bf9","decided_at":"2026-10-16T03:12:09.270Z","decision":"review","disputed_pct":0.1739,"findings_hash":"3n2ZdsmMw9PkiVQj5sYkj5hh1c3YBCVBnyd4YDPUDWuT","investigation_id":"c755b6a4-dcf8-43cf-9777-53595004dc81","mode":"findings_only","new_score":42,"page_content_hash":"0034881cdd54abac6c99fea52bd264317e15031af7e72f5f82a38450ec02b58e","page_slug":"the-sandbox-sand","prev_score":42,"reason":"The page is largely well-sourced and its central narrative -- the August 21-22, 2026 LayerZero OFT bridge exploit, the resulting compensation plan, the February 2023 phishing breach, the 2023 SEC/Coinbase SAND allegation, and the August 2025 Animoca-led restructuring -- holds up against independent reporting on the specific figures (329.24 trillion SAND minted, ~14.75 million SAND / ~$675,000 drained, 703 transactions, five-hour window, 313-day-dormant attacker, snapshot blocks, claims-portal dates, staff/office cuts). Two substantive problems were found: the compensation section's claim that affected supply was 'less than 0.01%' of max supply is wrong by roughly 49x (actual figure, by the page's own numbers and current reporting, is about 0.5%), and the regulatory section presents the SEC/Coinbase SAND allegation as still-open litigation requiring ongoing user monitoring without disclosing that the underlying case was dismissed with prejudice in February 2025 -- while also citing, via HackerNoon, a source that is actually about a separate and unmentioned 2024 SEC action against Consensys. Several other claims (the Nov 29, 2021 'official launch,' Robby Yung's Animoca Brands title, the 166,464 LAND/3B supply figures) are directionally accurate but either overstate what happened or aren't actually supported by the two sources cited for them.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}