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 · Loopring DEX Shutdown (June 2026)
- Sequence
- #5
- Score
- 17 → 17 (0)
- Cluster
- mainnet-beta
- Slot
- 457878068
- Off-chain at
- 2026-10-17T02:55:42.617Z
- Anchored at
- 2026-10-17T02:55:53.691Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DMKHLSXZ2qWFStkRSCbAHwuciK1VeyeethEVHw5VWUro
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1999 chars)
{"actor":"reviewer","artifact_identity":"7e38309b61b7945cf5b41cea9e21839d","decided_at":"2026-10-17T02:55:42.427Z","decision":"review","disputed_pct":0.2778,"findings_hash":"Eq71Jvoqmnj5yPWPM8ecimA6Jh9S7TXu94o33JaYnmz9","investigation_id":"a9a7a1bb-b9d5-47b9-8247-6afdaee77e40","mode":"findings_only","new_score":17,"page_content_hash":"8439c053b591d27febabee261b3681b491a21f4827e5346ff3c3d029e739fc6f","page_slug":"loopring-dex-shutdown-june-2026","prev_score":17,"reason":"The page is substantially well-sourced and accurate on its central claims: the mechanics of the shutdown, the smart-contract upgrade restricting exits to team-controlled whitelisted addresses, the $10 distribution threshold, the June 2024 Guardian hack figures (1,373 ETH / ~$5M / 58 addresses), the 2022 and 2025 CEO transitions, the LRC delisting timeline, and the L2Beat Stage-0/multisig risk profile all check out against independent, credible sources, including exact quoted language verified against the cited CryptoTimes and L2Beat pages. The page is also commendably transparent about a genuine date conflict (June 28 vs 29) across its own sources rather than silently resolving it. The main defect found is a mismatched archive date for the L2Beat citation (prose and timeline say June 29, 2026, but the recorded archive_url is a July 20, 2026 capture), which recurs in three places and is grouped as one defect. A RootData industry-wide statistic lacks a direct citation and could not be independently confirmed at the stated figure, and a May 2026 BYDFi delisting-warning date is only weakly corroborated. The single accepted community submission is a duplicate of an already-cited neutral source mislabeled as 'incriminating.' The most significant gap is the absence of any post-announcement reporting on whether the fund distribution was actually completed as promised.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}