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.

Decision
review · BingX
View on Solana ↗
Sequence
#3
Score
58 → 58 (0)
Cluster
mainnet-beta
Slot
462179242
Off-chain at
2026-10-27T18:53:17.071Z
Anchored at
2026-10-27T18:53:43.000Z
Block time
2026-10-27T18:53:43.000Z

Independent verification

1. Database (off-chain)
9nefrJFnxJj4QqJUSm46vrWskJC6neU34KfBZft9Dwb3
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1531 chars)
{"actor":"reviewer","artifact_identity":"622e39c59e7d37022216bc39f2d3df52","blocked_count":1,"decided_at":"2026-10-27T18:53:16.968Z","decision":"review","disputed_pct":0.4,"findings_hash":"4HgdU7wssvnMaDj16XwdVqRyD1TxJq1jM8R7w4VNVJ2p","investigation_id":"1e8bb53f-36c7-49e5-82a4-1f6f83a90360","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":58,"page_content_hash":"04155a51ee343e7d19b5f842b5167c4c85a798a4e6ef7330b21cdf2ad19d6ae7","page_slug":"bingx","prev_score":58,"reason":"The core narrative holds: a September 2024 hot wallet breach across seven chains, the 'wallet maintenance' framing, the cover-up denial, the $10M freeze and staged restoration are supported by DL News, CryptoSlate and CoinDesk. One timeline date is wrong: the FinCEN and FINTRAC announcement is dated January 2022 rather than June 2023. The $52M figure is a Cyvers estimate that the page presents as BingX's confirmed final figure. The Poloniex link, the ten-address detail and completed reimbursement were not verified. The Lazarus link is corroborated only by secondary reporting of ZachXBT's analysis, and the page's own hedging is reasonable. No subject-status contradiction was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}