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_revise · OKX NFT Aggregator
- Sequence
- #3
- Score
- 42 → 30 (-12)
- Cluster
- mainnet-beta
- Slot
- 426286841
- Off-chain at
- 2026-06-13T22:10:30.197Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- BammkpmaJQxNpdLDft2SPob7zTzpGEsGogtPdSp6V4pX
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1452 chars)
{"actor":"judge","decided_at":"2026-06-13T22:10:29.929Z","decision":"review_revise","investigation_id":"37d902e3-aec9-4679-8048-058ca5d1ebbb","new_score":30,"page_slug":"okx-nft-aggregator","prev_score":42,"reason":"One claim is materially disputed (claim_findings[4]): the ZachXBT citation inverts the actual relationship — OKX funded ZachXBT's investigation into a third party, not the reverse. This mischaracterizes the source and should be removed or corrected. Five further claims are only partially supported, most notably the implied scale of the OKX NFT Aggregator's direct loss in the June 2024 storage-collision exploit (its individual exposure was approximately $14,000, not a meaningful share of the $6.9M combined total) and the framing of Lazarus Group laundering as completed rather than attempted and partially blocked. Two high-priority structural gaps also require attention: all seven page sections have empty content bodies, making the page unpublishable in its current form, and multiple incidents attributed to the OKX NFT Aggregator actually involve the broader OKX exchange or DEX arm. Core claims — the $504M DOJ settlement, the December 2023 DEX exploit, the CertiK RCE disclosure, and the March 2025 DEX aggregator suspension — are confirmed by Tier 1 sources and are not at issue.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}