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 · CoW Swap (CoW Protocol)
- Sequence
- #3
- Score
- 58 → 50 (-8)
- Cluster
- mainnet-beta
- Slot
- 423656069
- Off-chain at
- 2026-06-01T19:32:30.343Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 5Jdk56enAer3sgZvMATtkhUVhj9k5Z9NFdspNnG6Y43k
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1306 chars)
{"actor":"judge","decided_at":"2026-06-01T19:32:30.158Z","decision":"review_revise","investigation_id":"99a79ffe-a739-45dd-9f2c-24975a8e2f06","new_score":50,"page_slug":"cow-swap-cow-protocol","prev_score":58,"reason":"The page is substantially accurate across 21 of 25 checked claims, with no claims outright disputed by credible sources. Two claims are partially supported and warrant correction: claim_findings[8] states the phishing interface operated for 'approximately 90 minutes,' but multiple Tier 2 sources indicate the phishing redirect remained live until migration to cow.finance at approximately 18:30 UTC — roughly 3.5 hours after onset, not 90 minutes. This figure appears in the summary, sections[1], and sections[3], making it a recurring material inaccuracy about user exposure duration. Claim_findings[24] presents the Legal Defense Reserve replenishment to 5 million USDC as a completed action, whereas CIP-86 states it as a stated intent. One claim about multi-signature domain management and MFA commitments (claim_findings[27]) could not be independently verified. No link rot, stale sources, or high-priority coverage gaps were identified.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}