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
- 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. - 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.
- 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 Finance
- Sequence
- #5
- Score
- 44 → 62 (+18)
- Cluster
- mainnet-beta
- Slot
- 426514559
- Off-chain at
- 2026-06-14T23:16:02.728Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6V56N4j3wz3wP9NZCjq9JjWLS5k1XPj16JXLKHCnKX7A
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1361 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:02.628Z","decision":"review_approve","investigation_id":"108d7b65-7cee-4e16-a90a-10e0f4936e64","new_score":62,"page_slug":"curve-finance","prev_score":44,"reason":"All six claim_findings (indices 0–5) are supported with zero disputed claims. The July 2023 exploit originated from a third-party Vyper compiler bug, not Curve's own code or conduct (claim_findings[1]); 73% of stolen funds were recovered within days and the DAO voted 94% in favor to compensate remaining losses by December 2023 (claim_findings[2]); no regulatory enforcement actions exist against the entity (claim_findings[3]); and the protocol continues operating with ~$2.2B TVL as of June 2026 (claim_findings[0]). The current score of 44 (WARNING band) treats Curve as though it bears ongoing elevated fraud risk, but the incident is resolved, funds were compensated, and the root cause was an upstream toolchain vulnerability — a pattern that belongs in the CAUTIONARY band (50–69) under the post-policy band semantics. The reviewer's recommended delta of +18 (44→62) is well-supported and appropriate. No status change or delist is warranted; the page content is accurate and must remain published.","score_delta":18,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}