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 · Bybit
- Sequence
- #7
- Score
- 82 → 82 (0)
- Cluster
- mainnet-beta
- Slot
- 457819668
- Off-chain at
- 2026-10-16T23:25:22.013Z
- Anchored at
- 2026-10-16T23:25:26.827Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- HjyMwUnPcL9zeuDafzdtubCdmUoNXcP5faSXreGZWEua
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1975 chars)
{"actor":"reviewer","artifact_identity":"095b30c65ab106283bddb041f5e886e8","decided_at":"2026-10-16T23:25:21.461Z","decision":"review","disputed_pct":0.2381,"findings_hash":"8f2ZHNi1zUAQBzeV1hb5KtgujRMc7J9ixaQxeWNMWgpk","investigation_id":"cc5d2629-b918-4554-b41b-cf765ff31285","mode":"findings_only","new_score":82,"page_content_hash":"d411eb4cb50a044e1a590aed95cd94b7238b782e418597a205bd56b26e998558","page_slug":"bybit","prev_score":82,"reason":"The page's core narrative — the February 21, 2025 Bybit hack, its ~$1.46B/401,347 ETH scale, the Safe{Wallet} supply-chain compromise mechanism, FBI/Lazarus Group attribution, Bybit's solvency response, and the November 2025 ICIJ Coin Laundry mention — is well supported by credible primary and technical sources (FBI/IC3, Sygnia, Hacken, ICIJ, CNBC) and is written with appropriate hedging where evidence (e.g., the ICIJ citation) is limited. However, four factual errors were found: the timeline misstates Bybit's founding location as Singapore when the page's own cited Wikipedia source places it in Shanghai; the Attribution section cites a $73 million Phemex hack figure that contradicts both its own cited source and the page's own timeline entry of $29 million; the FBI address count is given as 50 rather than the 51 in the cited PSA; and the claim that Bybit remains 'blocked or restricted' in France is now stale, contradicted by the page's own cited Datawallet source, given Bybit's 2025 AMF-blacklist removal and Austrian MiCAR license. Several granular figures (the 86.29% BTC-conversion disclosure, the QinShihuang memecoin details) are accurate per independent reporting but not actually supported by the specific sources the page cites for them, and two response-timeline figures ($4B/12-hour withdrawal surge, 30-minute CEO response) could not be verified either way.","score_delta":0,"sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}