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 · Curve Finance
View on Solana ↗
Sequence
#7
Score
60 → 60 (0)
Cluster
mainnet-beta
Slot
457866756
Off-chain at
2026-10-17T02:14:49.956Z
Anchored at
2026-10-17T02:15:06.748Z
Block time
—

Independent verification

1. Database (off-chain)
7UcTNKtUSMPi2UdGcf4ktCoGpjwqskBKegR1rJywMFZ5
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1969 chars)
{"actor":"reviewer","artifact_identity":"2e25914ab3c2121dc5e1ddec64dde82f","decided_at":"2026-10-17T02:14:49.717Z","decision":"review","disputed_pct":0.0526,"findings_hash":"FF5Yg5jZgZQKGq6YRJhvKrgtZaKKuLCReLjxuVTRrreD","investigation_id":"3e4567af-0a09-4107-b598-0cddbf8e26fa","mode":"findings_only","new_score":60,"page_content_hash":"289c303766186276bcd9a979313f46a463049b1bba4c6a72a7980ee501ed25d3","page_slug":"curve-dex","prev_score":60,"reason":"The page is substantially well-sourced and most load-bearing figures -- the July 2023 Vyper exploit mechanics and per-pool losses, the recovery and bounty timeline, the December 2023 DAO compensation vote, Egorov's 2023 CRV-backed loan exposure, and the June 2024 liquidation cascade -- check out closely against primary and credible secondary sources (Chainalysis, Vyper's own post-mortem, CoinDesk, The Block, Curve's own announcements). The clearest concrete defect found is a named-entity error: 'DW Labs' should be 'DWF Labs,' a real and well-documented OTC buyer. A precise '53 investors' figure for the CRV OTC sales could not be corroborated anywhere and should be treated as unverifiable. Two citations are dead: a Cointelegraph article on the $49M compensation vote (404, with a live CoinGape replacement already cited elsewhere in the page) and a duplicate blockworks.com URL that 403s and is redundant with a working blockworks.co citation used alongside it in three places. Two softer issues are a bad-debt figure ($11.5M) for the June 2024 Curve Lend cascade that is real but competes with an equally-cited $10M figure without acknowledgment, and a December 2024 'further liquidation' reference that is technically accurate but, next to the much larger June 2024 episode, risks implying comparable severity for an event roughly two orders of magnitude smaller.","score_delta":0,"sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}