Skip to main content
Sign in
← 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 · Gnosis Pay
View on Solana ↗
Sequence
#3
Score
4228 (-14)
Cluster
mainnet-beta
Slot
443525944
Off-chain at
2026-08-27T12:06:30.726Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
Gkr9pwTLWo2iYuagCRkZNN8B2LGs6bvYXPJujWrQYUJX
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2458 chars)
{"actor":"judge","decided_at":"2026-08-27T12:06:30.484Z","decision":"review_revise","investigation_id":"8ed8454e-4391-4266-b163-451864833160","new_score":28,"page_slug":"gnosis-pay","prev_score":42,"reason":"Independent recomputation confirms disputed_pct = (3 disputed + 3 unverifiable) / 23 = 26.1%, which falls in the 10-30% band and maps to review_revise with no status change. The page contains two disputed factual claims of real substance: claim_findings[7] asserts the card is unavailable in Latin America while citing sources that place a Gnosis Pay Brazil launch (via Picnic) in April 2025, months before the page's own December 2025 reference point in the same sentence; and claim_findings[5] undercounts total transactions (1.6M vs. Gnosis's own reported 2 millionth payment). claim_findings[20] shows a citation pointing to an article about an unrelated exploit (TesseraDAO) rather than the SquidRouterModule incident it is meant to support, though the underlying wallet/loss figures for that incident were separately corroborated elsewhere (claim_findings[19]). Two stale findings (claim_findings[15], [18]) are excluded from the disputed_pct numerator by definition, but are weighted heavily here: the page repeats 'losses undisclosed' language despite Gnosis's own official post-mortem (final ~$1.8M loss, 5,281 wallets, restoration complete by June 6) having been published before several of the page's own cited sources were archived. Combined with two high-priority coverage gaps -- the missing post-mortem update and the omission of card issuer Monavate's 2026 receivership and subsequent acquisition by Exodus Movement -- these push the score delta toward the top of the applicable band. The three unverifiable items (claim_findings[3], [6], [21]) stem from source access failures (503 errors, inaccessible X posts) rather than established errors and are treated as open questions, not violations. Reviewer confidence of 0.72 and the fact that 11 of 23 claims -- including all core exploit mechanics, corporate registration, and executive quotes -- were fully confirmed keep this within the revise band rather than escalating to under_investigation. The page sits close to the 30% band boundary, but the measured 26.1% does not support crossing it, so no status change or delisting is applied.","score_delta":-14,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}