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 · Convex Finance
- Sequence
- #3
- Score
- 62 → 62 (0)
- Cluster
- mainnet-beta
- Slot
- 425177120
- Off-chain at
- 2026-06-08T19:48:36.795Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- CQfdynsWwkKDUV9cQuGmoMJ1RDRL7vzciAXxScChkKmu
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1465 chars)
{"actor":"judge","decided_at":"2026-06-08T19:48:36.563Z","decision":"review_approve","investigation_id":"34a60e5e-0a2a-43d3-bbb1-d6b00c4cb1d1","new_score":62,"page_slug":"convex-finance","prev_score":62,"reason":"The reviewer examined 43 claims and found 34 confirmed, 6 partially supported, 1 disputed, and 1 unverifiable, yielding a disputed_pct of 4.7% — well within the 0–10% approval band. The single disputed claim (claim_findings[32]) concerns the page's current market cap ($164M) and TVL ($1.28B), which CoinGecko data from June 2026 places at approximately $113M and $516M respectively; this is a stale metric rather than a fabricated or materially misleading risk claim. The six partially-supported claims involve peripheral figures (the $12B CVX locked value, the 73% CRV emissions statistic, the $54M Mochi aggregate loss, and a February vs. March 2023 date for Polygon expansion) that do not affect the core risk narrative. All major incidents — the December 2021 OpenZeppelin rug-pull vulnerability, the March 2022 vote-locking bug, the June 2022 DNS hijack, and the Mochi Finance governance attack — are confirmed by Tier 1 sources. The high-priority coverage gap (stale live metrics and missing post-2022 protocol trajectory) flags a need for expansion rather than correction. Reviewer confidence was 0.82.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}