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 · Convergence
View on Solana ↗
Sequence
#4
Score
47 → 47 (0)
Cluster
mainnet-beta
Slot
464350760
Off-chain at
2026-11-02T03:51:52.627Z
Anchored at
2026-11-02T03:52:19.000Z
Block time
2026-11-02T03:52:19.000Z

Independent verification

1. Database (off-chain)
CqoYcRQr3kHbS4i5sP8QHj5QCS8KKAcT7kSNv9y4pKYd
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1543 chars)
{"actor":"judge","artifact_identity":"2fe4c32d25da09b114e06d21563a4f08","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T03:51:52.319Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"19e543d7-8d79-40e0-89fb-47e45ca82f4e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":47,"page_slug":"convergence","prev_score":47,"reason":"Counting claim_findings with one source-blocked finding excluded (claim_findings[7]), 5 of 10 findings are disputed or unverifiable (50%), which falls in the significant-issues band. The core exploit facts (claim_findings[0]: 58M CVG, about $212k, 99% drop, removed validation line) are confirmed by a Tier 2 source. The disputes are an internal ticker error, TGN versus TAN (claim_findings[1]), and a contradictory statement on whether audits covered the modified code (claim_findings[3]). The Tornado Cash routing (claim_findings[4]), the ZachXBT flag (claim_findings[6]) and the unsourced timeline entries (claim_findings[9]) could not be verified. The Tornado Cash sanction wording is also stale (claim_findings[5]). Because the central allegation holds up, the penalty sits at the lighter end of the band. Omissions are minor, so no severity override applies.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}