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
- Sequence
- #5
- Score
- 56 → 56 (0)
- Cluster
- mainnet-beta
- Slot
- 457760091
- Off-chain at
- 2026-10-16T19:50:25.396Z
- Anchored at
- 2026-10-16T19:50:38.532Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- CwFK7oPUoq5oTyPFadeLdr1ZhMq58mebFxSv88QDuEQN
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2102 chars)
{"actor":"reviewer","artifact_identity":"a17768b854ee21bfdd0517da9ea71b3a","decided_at":"2026-10-16T19:50:25.014Z","decision":"review","disputed_pct":0.2273,"findings_hash":"AyTp1CXNTXwTRccrQDc9K2PmHPX7E1knNgBhV9tX24sF","investigation_id":"e198003e-9540-4950-a4cc-3868bcd92ce3","mode":"findings_only","new_score":56,"page_content_hash":"ef9676f4cee40840dde2e9a1e5c4465a33a892ac2b000ff97a265a2729382c4d","page_slug":"gnosis-pay-zodiac-delay-module-exploit","prev_score":56,"reason":"This page holds up well under independent verification. Every major claim checked — the exploit date and mechanism, the $265,000/41-Safe CertiK estimate, the Hyperliquid bridging and Monero conversion, Köppelmann's reimbursement pledge, the 99% card-service restoration by June 7, the 95%+ pre-disclosure remediation figure, and the Safe-core-unaffected finding — is directly supported by the cited sources, and several are independently corroborated by outlets and an official Gnosis Q2 2026 report not cited on the page. Three issues were found: (1) the Technical Vulnerability section's root-cause description, while accurate, omits a materially important detail surfaced in the accepted Verichains submission — that the same bug had already been found and silently fixed in a separate, actively maintained Zodiac repository months earlier, and the production module was simply left on a stale, vulnerable dependency; (2) the Cryptopolitan source cited in the Financial Impact section does not actually address Gnosis Pay's loss figures and should be removed or replaced; (3) five timeline entries covering the June 1 events have had their date field truncated to month-only precision ('2026-06') even though the exact date is both recorded in each entry's own date_original field and confirmed by every source as June 1, 2026 — these should be corrected to the precise date. No link rot was found across the ten sources_used entries or the accepted submission's wayback URL.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}