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 · Curve DEX
View on Solana ↗
Sequence
#5
Score
26 → 62 (+36)
Cluster
mainnet-beta
Slot
426514236
Off-chain at
2026-06-14T23:15:45.474Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
8iyKXWPVhazzSQaysxFCg29LivSAY7E26WZtPXN8oCFg
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1854 chars)
{"actor":"judge","decided_at":"2026-06-14T23:15:45.355Z","decision":"review_approve","investigation_id":"3e4567af-0a09-4107-b598-0cddbf8e26fa","new_score":62,"page_slug":"curve-dex","prev_score":26,"reason":"This is a severity-calibration review, not a fact-dispute review: all six claim_findings are supported and disputed_pct is 0%. The page content stands as accurate and must remain published. The review establishes with high confidence (0.88) that the current WARNING-band score over-penalizes Curve Finance on three grounds: (1) the July 2023 $70M exploit originated from a Vyper compiler bug, a third-party failure not attributable to Curve protocol design, and 73% of funds were recovered (claim_findings[0-1]); (2) the $10M bad debt generated by the June 2024 founder liquidation was fully repaid by Egorov personally within days, making any framing of it as an unresolved community loss inaccurate (claim_findings[2]); and (3) the VC fraud lawsuit was dismissed by a California appeals court in February 2025, removing it as an active fraud indicator (claim_findings[3]). Curve continues to operate with approximately $1.43B TVL and $126B annual volume (claim_findings[4]), and the 2025 X-account and DNS incidents were infrastructure-layer attacks that did not breach its smart contracts (claim_findings[5]). Material caveats remain — ongoing Swiss proceedings, founder governance-token concentration, and a pattern of infrastructure security breaches — which correctly place the entity in the CAUTIONARY band rather than SAFE. A score_modifier_delta of +36 moves the score toward the reviewer-recommended 62 (CAUTIONARY), correcting the mis-calibration from the current over-penalized WARNING band.","score_delta":36,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}