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_approve · Synthetix
View on Solana ↗
Sequence
#5
Score
47 → 58 (+11)
Cluster
mainnet-beta
Slot
426514922
Off-chain at
2026-06-14T23:16:20.941Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
fxuFwS13AX1zXrx5QZhPX2fD1jH6iqndkhjWU97nMFa
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1499 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:20.825Z","decision":"review_approve","investigation_id":"3504bf43-3ada-4577-beea-0500b7216b9c","new_score":58,"page_slug":"synthetix","prev_score":47,"reason":"This is a severity-calibration adjudication. All six claim_findings (indices 0–5) were returned as 'supported' with 0% disputed content — the page's factual record stands in full. The reviewer (confidence 0.82) correctly identifies that the current WARNING score of 47 over-penalizes Synthetix by treating a recovered oracle exploit (claim_findings[0], full fund reversal via bug bounty), a governance-driven stablecoin depeg (claim_findings[1], SIP-420 design failure, not fraud), and a third-party market-maker controversy (claim_findings[2], Synthetix was itself the aggrieved party) as equivalent in severity to fraudulent intent. Claim_findings[3] confirms no SEC, CFTC, or DOJ action exists, and claim_findings[4] confirms active operations with a published 2026 roadmap — both inconsistent with a WARNING band. A CAUTIONARY score of 58 correctly acknowledges material ongoing risk (unresolved sUSD peg, DWF Labs governance episode, historical front-running) while properly distinguishing a legitimate-but-troubled protocol from one with elevated fraud risk. A positive delta of +11 is applied to move the score from 47 to the recommended 58.","score_delta":11,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}