Reading the figures

Every figure on Turntable comes from the chain. This article covers where each one is read, how fresh it is, and what to make of a figure that could not be read.

Where figures come from

Pages read a database that is built from contract events on Base. An indexer job adds new events as they appear. The Indexed to block line on the overview shows how far it has reached.

Live chain state, such as the vault float, the terms and the KYA setting, comes from a snapshot job that reads the chain every minute. Pages show that snapshot and never call the chain themselves.

How fresh a figure is

A figure from the snapshot says when it was read. When the last read is more than five minutes old, the page marks it as old: the snapshot job has stopped or is failing.

Unreadable is not zero

When a read fails, the page says unreadable or Could not read. It never shows a zero in its place. An empty table means there are no rows. A failed read always says so.

Recorded, netted and paid

A payment moves through three steps before it counts as principal on a line.

1. Paid. The vault pays the merchant at once.
2. Recorded. Anyone can record the spend on chain with recordSpend, which proves it from USDC's own record.
3. Netted. A netting job writes recorded payments onto the ledger in batches. A batch goes when the first of two limits is hit: one hour, or a $0.25 balance.

So Principal outstanding counts netted debt only. Newer payments show as Paid, not yet recorded and Recorded, not yet netted until they are netted.