Convexly / Evidence
Every public claim, with its receipt.
For each public Convexly claim, the table below shows the allowed wording we use externally, the receipt URL you can verify against, and the last-verified date.
The same machine-checkable list backs the pre-publication audit guard inside the codebase. If a Convexly outbound email, paper, or social post references a wording that is not on this page's allowed list, tell us - that is a bug, and we want to fix it.
Is the claim live?
Live means the product surface may use the wording shown here.
Is the proof external?
External verification is separate from Convexly-hosted evidence.
14 public claims, 2 externally verified
A Convexly-hosted receipt means our own records, source code, public data bundles, audit-chain entries, or filings we publish ourselves. It is useful support, but it is not an external certification.
“CFTC ANPRM comment filed 2026-04-29 (mok-lrhf-09it) on the perpetual-derivatives rulemaking”
“audit-chained methodology”
“transparency and independent integrity inherent in the blockchain”
“out-of-fold Spearman +0.514 (p < 0.0001) on the V1 cohort”
“24-of-24 aggregators failed to beat market-implied baseline”
“median and volume-weighted Edge Score V3b of wallets active on this market in the trailing 7 / 30 / 60 days; nulled below n_unique_wallets >= 5”
“frozen-methodology rating of market trustworthiness across seven pillars; rating is a diligence input, not advice or a price prediction”
“heuristic resolution-risk score from subjective wording, liquidity floor, time-to-resolution proximity, and category historical UMA dispute rate; per services/api/scripts/cme_v0_1/resolution_risk.py”
“cross-venue activity flags showing each wallets activity across Polymarket, Kalshi, and Manifold”
“Top-50 by Edge Score (>=20 resolved positions; current cohort 50 wallets out of 69 qualifying)”
“co-filing posture with the Hyperliquid Policy Center for the next regulatory window”
“modeled net EV at prescribed size”
“planned venue-level audit format; pilot scope and timing depend on V0.1.6 validation; nothing shipping yet”
How this page is built
Same source the codebase audits against.
Every row above is a record in the claim_registry Postgres table. The same table powers a pre-publication audit guard inside the codebase: outbound copy is greppable against the union of allowed wordings, and any unsafe wording must come with an external receipt URL or a formal statistical test before it ships. The page reads from the same source so external readers and internal authors see identical state.
For the audit doctrine, see /research/start-here and the credibility-claim audit section of the project CLAUDE.md (mandatory for every external send).