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 · Synthetix
View on Solana ↗
Sequence
#4
Score
4747 (0)
Cluster
mainnet-beta
Slot
426514917
Off-chain at
2026-06-14T23:16:20.877Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
6QNT5EV2jY1bjmJ4kMRUzVzbCo5QvGEcqMUXrmAxwvRp
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1705 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:16:20.825Z","decision":"review","investigation_id":"3504bf43-3ada-4577-beea-0500b7216b9c","new_score":47,"page_slug":"synthetix","prev_score":47,"reason":"Blue-chip calibration review (Prompt A). Verdict: over-penalized. Page content is treated as accurate; the trust_score band is miscalibrated. Synthetix is a legitimate, long-running DeFi derivatives protocol (founded 2017, $30M ICO 2018) with no evidence of fraud, exit intent, or Ponzi mechanics. All major incidents are either suffered-by-entity or attributable to governance design decisions: the 2019 oracle exploit was fully reversed via bug bounty; the sUSD depeg (which worsened to $0.2081 in August 2025, a fact the page understates by citing only the $0.68 April 2025 low as the worst point) was caused by the protocol's own SIP-420 collateralization reduction — a negligence/design failure, not fraud. The protocol continues active operations with a published 2026 roadmap, 10 live perp markets, and an ongoing peg-restoration program. No regulatory actions have been taken by any regulator. A CAUTIONARY band (score 58) is appropriate: it acknowledges the serious unresolved sUSD depeg crisis, the DWF Labs governance controversy, and years of front-running vulnerabilities as material caveats, while correctly distinguishing a legitimate-but-troubled protocol from one with elevated fraud risk. The current WARNING score of 47 over-penalizes by conflating loss events suffered by or caused by the protocol's design decisions with fraudulent intent.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}