Skip to main content
AVOID.NET
Sign in
← 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.

Decision
review_revise · ATM Token BNB Chain Exploit
View on Solana ↗
Sequence
#3
Score
4 → 0 (-10)
Cluster
mainnet-beta
Slot
443505487
Off-chain at
2026-08-08T02:21:05.179Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
C3nuMKBmYDpAe8e9rCYnkknadksV8oPuBJW9YyGshEGm
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1171 chars)
{"actor":"judge","decided_at":"2026-08-08T02:21:04.867Z","decision":"review_revise","investigation_id":"511f52c7-4e0c-4b51-964e-f2259b62b80b","new_score":0,"page_slug":"atm-token-bnb-chain-exploit","prev_score":4,"reason":"The investigation's core narrative — a BNB Smart Chain exploit draining approximately $243,500 via a flawed transferFrom() auto-swap mechanism — is well-supported by on-chain data and consistent secondary sources. However, claim_findings[7] is disputed by two Tier 1 BSCScan sources: the address cited as the ATM token contract (0x4fd0878ee1bbf7b1019138e8eec746e5a5d5a205) is actually the PancakeSwap V2 LP pair for the BSC-USD/ATM pool, not the token contract itself. This is a material factual error that should be corrected before the page is re-approved. Additionally, all claim sourcing flows through two credibility-tier-2 news outlets with no first-party CertiK or TenArmor primary source cited, and the on-chain transaction timestamp (June 3 UTC) does not match the stated exploit date of June 4.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}