Audit infrastructure

Audit chain verifier

Convexly publishes a SHA-256 hash-chained audit log for every Coherent Markets Engine run plus a file-level integrity log for logged research artifacts (papers, data bundles, snapshot CSVs). This page walks both chains in your browser and renders a verdict for each. Mutable daily snapshots (leaderboard JSON, wallet-labels JSON, daily Coherence Signals archive) are LOGGED on each regenerate and the verifier compares the LATEST entry per file to the live file (older entries are publication history, not live-file hash assertions). Row-level Coherent Markets Engine hash recomputation and RFC-3161 timestamp anchoring are roadmap items.

Cross-references: AsPredicted manifest · negative-result registry · full research index.

Market Trust Card

Card input verification

Verifies the v0.1 card row hash and lists each source artifact hash declared in the card's input manifest.

Valid

Will Solstice launch a token by June 30 2026?

cf90f5854414e7c9bda04582e345e287284308e1000c2a4d399e7c22e85bb38c

public/research/cme/snapshots/20260511/gamma_snapshot.json

48h+ stale

market_metadata_liquidity

Source artifacts are stale for a market-quality product surface; the next materialization run should refresh or suppress the card.

expected sha256: b44c652eed29c2dbb8c91d93f16664cf65900e96dcae157e41ab49d2b9b17066

data/cme/private/20260511/orderbook_snapshots_coverage.jsonl

48h+ stale

visible_orderbook_depth_coverage

Source artifacts are stale for a market-quality product surface; the next materialization run should refresh or suppress the card.

expected sha256: ed0fb25aff36fd61253c3e33b74075f04ba9eb450c1bbee79e8fa77062ed7ec7

public/research/cme/snapshots/20260511/cme_signal_report.json

48h+ stale

public_cme_daily_snapshot

Source artifacts are stale for a market-quality product surface; the next materialization run should refresh or suppress the card.

expected sha256: 81c2fa753b2a3bbf78009022f5d1370baff31a7a3a780b175e834917ad933c30

data/cme/private/20260511/cme_signal_report_full.json

48h+ stale

internal_condition_id_join_without_trade_construction

Source artifacts are stale for a market-quality product surface; the next materialization run should refresh or suppress the card.

expected sha256: 81c2fa753b2a3bbf78009022f5d1370baff31a7a3a780b175e834917ad933c30

market_participant_rollups:pending

pending

participant_quality_wallet_flow

Per-market wallet-flow rollups are not materialized in v0.1, so participant quality remains intentionally unscored.

pending input · no artifact hash yet

Coherent Markets Engine audit chain

Every row of the Coherent Markets Engine audit log carries a SHA-256 prev_hash that must match the prior row's row_hash. The genesis row's prev_hash is the all-zero string. Tampering with any row mid-stream breaks the linkage and the verifier below reports the first invalid row.

Rows

First row

2026-04-29T01:19:42

Latest row

2026-05-25T17:44:27

Download audit_log.jsonl

Research-artifact integrity log

Every published research artifact (paper PDF, leaderboard JSON, whale-audit CSV) is logged with its SHA-256 + git parent commit + retroactive timestamp. For mutable artifacts (the daily leaderboard, wallet-labels, etc.) the integrity log accumulates one row per regenerate; the verifier compares the LATEST row per file to the live file. Older rows are publication history, not live-file hash assertions.

Artifacts

First entry

2026-04-12

Latest entry

n/a

Loading integrity manifest...

Download integrity-log.jsonl

What this verifier proves

Chain linkage: no row in the Coherent Markets Engine audit log can be edited without invalidating every subsequent row's prev_hash. The verifier identifies the first invalid row when it walks the chain.
Artifact integrity: every published research artifact (paper PDFs, JSON snapshots, CSV bundles) hashes match the integrity-log claim at publication time. Tampering after publication breaks the SHA-256.
Open verification: the verifier code is inspectable in the page source. Anyone can re-run the same checks offline by downloading the JSONL files and running shasum -a 256.
Pre-registration linkage: each AsPredicted entry on /research/preregistrations has an audit_chain_anchor field referencing the run identifier in the audit log. Combined, this shows that the data behind the verdict is the data Convexly committed to before running the test.