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 · CarbonVote Token
- Sequence
- #2
- Score
- 0 → 0 (-5)
- Cluster
- mainnet-beta
- Slot
- 419382393
- Off-chain at
- 2026-05-13T02:43:20.300Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Cbam6bTXLwrEZ3siMx38YzCZKqH5RzWeab228WGBBfdH
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1387 chars)
{"actor":"judge","decided_at":"2026-05-13T02:43:20.043Z","decision":"review_revise","investigation_id":"cf85373b-cb36-442c-afb1-d11ef6759762","new_score":0,"page_slug":"carbonvote-token","prev_score":0,"reason":"The page's core narrative is well-sourced and largely accurate: CVT deployment, 750M supply, Raydium wash trading, durable nonce governance compromise, DPRK attribution, and recovery framework are all confirmed across multiple Tier-1 sources. The disputed_pct is 5.9%, below the approval threshold, but two issues warrant revision before the page is cleared. First, claim_findings[18] identifies a material factual error in a critical section: the page states '26 asset types' drained in the exploit, while the cited Drift official recovery update (Tier 1) shows 19 asset types, and Chainalysis independently reports 'at least 18.' Second, claim_findings[22] understates attribution confidence — the page cites 'medium confidence' attributing it to The Hacker News, but Drift's own post-mortem and SEAL 911 use 'medium-high confidence.' An additional high-priority coverage gap exists: the Circle USDC freeze controversy surrounding the $232M CCTP transfer is absent from the page and is directly relevant to the laundering section.","score_delta":-5,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}