About Tradfi Chains
What this is
Tradfi Chains is a tokenized real-world-asset knowledge base. It tracks which chains carry real-world-asset tokens (Stellar, Arc, Tempo, Canton, Solana, Prividium, Ethereum as the RWA baseline), what their issuers are, and how the measured state of the tracked contracts changes over time. It is a data and agent-tool layer: every number is a dated, sourced, evidence-kind-tagged row in a read-only SQLite knowledge base, not a scrape of a marketing page.
This page is static — it reads no database. Everything data-driven lives on the other pages, dated at render time.
How to read a number
measured Almost every number on this site is a measurement: we asked a public endpoint or a chain for a fact, recorded the answer with the source and the date we asked, and stored the two together.
reported A vendor, a newsroom or a product page says something about a chain. That is real information about what people claim, and it is kept in its own lane with its own label, because a claim on a marketing page and a reading of the same chain do not deserve the same trust.
inferred Our own reading of what a contract appears to be for, which appears only on a contract page, carries the measured properties behind every sentence, states what we could actually read, and never gets stored next to the facts it was derived from.
reported not yet checked A recorded value we cannot vouch for is shown as reported with this badge, so an unchecked row is never dressed as plain reported — there is no fourth kind.
as of example date stale A figure older than the rest of its section carries its own date and this badge; the section states its as-of once, and the older figure repeats its own.
How the data is gathered
One file, knowledge.db, opened read-only by a python reader. The dashboard never writes to it; a test proves the file's sha256 is unchanged after reads.
Every page is composed per request — one short script call, then a pure TypeScript renderer turns the JSON into HTML. No cache layer, no JS framework, no build step: what you see is what the file says now.
The front page's lead is generated, not written: the biggest measured move, the newest contract and the watch that fired in the last 24 h, each with its date and a link to its chain page. The daily brief (an internal generator) computes the same lead from the same rows, so the morning update and the homepage stay one artifact.
RoutesAll 8 routes
/Front page: lead (the last 24 h, measured), 360 chain cards, the 7-chain table with a per-chain 24h change cell, What's coming (coverage doc + live pending watches), yesterday's daily brief excerpt, the raw diff table (evidence layer), watch state./chain/<id>Per-chain page: 30-second narrative answer, KPI strip, identity, contracts, usage history, What changed, honest gaps./chain/<id>/contract/<address>Contract drill-down: the one contract's full history, usage series chart, evidence rows, related contracts./chain/<id>/timelinePer-chain timeline: diffs + usage merged into one dated stream./issuersCross-chain issuer view: one row per issuer — chains present, contracts, measured usage, first seen, internal note, provenance./changesThe dated diff log: all diffs, filterable by chain / change / table / evidence_kind / limit./rwaConsolidated market + activity + positions (the W12 measured-vs-no-data split verbatim)./api/*JSON API (market, activity, positions, quotes, kb_* read tools).What it refuses to fabricate (the honesty contract)
- Absent ≠ 0. A missing value is rendered as an explicit empty state with the reason — never
0, never blank. Canton / Prividium / Ethereum showing "0 contracts" means the KB records zero, and the page says why (watch-tier access, no proven public RPC path). - Measured ≠ reported. Measured rows (on-chain, primary sources) and reported rows (docs, press) are never mixed in one sentence; each carries its
evidence_kindon the line itself. - Every factual row is dated and sourced. Nothing is a number without an
as_ofand a kind. - Caps are named. Diff lists are capped and the page says the cap and how many more exist.
What this site does not cover
Nothing anywhere here forecasts: no launch dates, no adoption claims, no prices. What a contract does and what it might become are different questions, and only the first one is answerable from data.
Where two readings of a contract tie on the evidence — a pooled-fund unit and a bill-backed unit can be built identically — both readings are shown, because picking one silently would make the page look more certain than the evidence is.
Where we could not get an answer, the page says so in the same place the number would have been — an unverifiable source is written as not verifiable, never as zero, because zero is a fact and "we could not check" is not one.
Where to read more
- the dashboard methodology doc (internal repo file) — page-by-page column mapping and the honesty rules.
- the internal coverage strategy doc (2026-11-12) — the testnet/devnet coverage strategy that
powers the front page's What's coming section (
to probe≠ live coverage). - the internal daily-brief generator (same lead logic as the homepage).