Execution economics and asset fundamentals, measured.
Log in →

Execution economics and programmable-asset fundamentals, measured across six chains.

Estimate what execution will cost, evaluate how an asset is actually performing, and build strategies on data that carries its own receipts. Six chains — Bitcoin, Ethereum, Solana, Arbitrum, Base, Optimism — live and fully archived.

Get started with Google → Request a design-partner pilot →

Every number on this page is pulled live from the measured feed — not typed into it.

Scan a venue — live measured read, no login

Live now — the operating state of every venue, from the same feed the API serves

loading the live feed…

Coverage & delivery

ChainsSix. Bitcoin, Ethereum, Solana, Arbitrum, Base, Optimism.
CadenceDaily state, updated live. 24-hour fee forecasts where they clear the bar.
HistoryEthereum to 2016, Bitcoin to 2017, Solana to 2020; the L2s from first collection. The full daily archive, not a trailing window.
FormatsFree artifacts, a metered /v1 API, and a terminal.

What you do with it

Execute — price the transaction before you send it. Fee distributions, the congestion regime, expected wait, and the cost of waiting — for Bitcoin settlement, Ethereum execution, Solana priority, and the L2 engines. Each venue in its own native cost language; no forced cross-chain column.
Output — a next-24h fee forecast with a q10–q90 band on the venues that earned a receipt.
GET /v1/chains/ETH/forecast
Evaluate — underwrite the asset, not the ticker. Network security budgets and who funds them, L2 economics and L1 dependence, protocol gross fees and the share that reaches holders (a = R / G), and token survival over the real population. Every object in the economics native to its type; no universal quality score.
Output — security coverage, fee-switch state, and a censoring-aware survival curve, per object.
GET /v1/chains/BTC · protocols.json · tokens.json
Build — export the data with its definitions attached. A data workbench over every measured object: define a target, horizon, frequency, and universe; inspect coverage and missingness; transform; export. Save data specifications, not black-box strategies. The platform never writes the trading logic.
Output — CSV export, a reproducible spec, and a Python or curl snippet for every pull.
curl -O https://sttl.live/feed/site/settlement_client.py

One number, end to end

Tamper-evident ledger
externally anchored — loading…
ledger.jsonl · anchors · recompute the chain yourself
ETH next-24h fee
loading receipt…

Every forecast is written to an append-only ledger before it resolves and scored after. It ships only if it beats the best naive baseline by at least 5% out of sample, at a Diebold–Mariano t of 2 or more. If it doesn't clear that bar, it doesn't ship — and the record stays in the artifacts for anyone to read.

curl -s https://sttl.live/v1/chains/ETH/forecast python settlement_client.py receipts # every receipt — and every refusal

The command that prints the receipts prints the refusals too. Check the bar was really cleared before you rely on the number.

Why trust the numbers

TimestampedEvery value carries its as-of date, frequency, and coverage.
VersionedSemantic versioning on every artifact; metric ids are permanent, never renamed.
ReproducibleThe ledger head is anchored externally — OpenTimestamps and an on-chain memo — so history cannot be quietly rewritten, including by us. Recompute the hash chain yourself.
Out-of-sample validatedForecasts clear a pre-registered bar before they ship, and the record is public.

No return predictions. The platform prices execution and measures asset state. It does not forecast price.
Non-custodial by construction: the platform proposes, the wallet signs. No keys, order flow, or client data are held.

Access

Public artifacts Free, no login. feed.json, evidence.json, ledger.json, and a one-file Python client — every field documented.
Metered API Keyed /v1 access with per-object routes and usage metering. One uniform response envelope on every call — value, unit, timestamp, frequency, method, evidence class, coverage, version.
Design-partner pilot Six weeks. Full terminal access and a transaction-cost report built for your desk. Pricing is set with the first partners.