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_revise · Cod3x
View on Solana ↗
Sequence
#3
Score
48 → 36 (-12)
Cluster
mainnet-beta
Slot
443525548
Off-chain at
2026-08-27T10:55:21.266Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
CFKAuq1GiTNRiQKLuQoLUkXEmzQ7Jeiw1CYLpTKcwG8b
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1677 chars)
{"actor":"judge","decided_at":"2026-08-27T10:55:20.498Z","decision":"review_revise","investigation_id":"e92fd795-e2ee-4446-aae1-5a25cc8aaeca","new_score":36,"page_slug":"cod3x","prev_score":48,"reason":"Independent verification found 23.3% of the page's checkable claims (7 of 30: 4 disputed, 3 unverifiable) to be disputed or unverifiable, which falls in the middle of the range calling for correction rather than removal. The most consequential problems are a security-audit date the page's own cited audit log contradicts — it credits Reaper Farm with a CertiK audit 'prior to' the August 2022 exploit, when that audit is dated three months after it (claim_findings[4]) — and an exploit-loss figure for Ionic Money that reports only the laundered portion ($3.2M) as the total, when the same cited sources report total losses of $6.9-8.6 million (claim_findings[7]). The page also incorrectly states that no major exchange has listed the token, when Coinbase, MEXC, Bybit and LBank all show active listings (claim_findings[14]), and a market-cap ratio claim conflicts with supply figures printed elsewhere on the same page (claim_findings[13]). Three of the seven disputed/unverifiable findings trace to sources that could not be fetched during review rather than to confirmed inaccuracies, and the reviewer's own confidence was moderate (0.72), both of which argue against the harsher end of this band; a high-priority gap in on-chain treasury analysis was also flagged but does not change the outcome at this disputed-claim rate.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}