Reading the snapshot…
Projects each settlement belongs to one project
One card per project for the window selected; the project, chain, rail and parties filters do not apply here, so the five cards stay comparable and add up to the headline figures. A settlement belongs to the project whose contract its transaction called (read from that project’s deployment trackers), else to the project whose contract emitted an event in it; a GL1 PC transaction signed by a wallet of the repo cases 2C and 2D belongs to Les Gardiennes. Shared registers keeps the direct operations on the central bank money, deposit token and stablecoin registers that no project contract called. “Exchanges in one tx” counts settlements that moved two assets or more in one transaction, split into delivery versus payment (a security against money), payment versus payment (two currencies) and other (two forms of one currency), wraps and bridge steps left out. The line is settlements per week over 26 weeks on one scale for the five cards, the current week dashed.
Tokenised central bank money legs
The six figures overlap and are not meant to add up: Minted and Burnt are the zero-address nodes of the diagram, whatever the operation; All legs counts every leg, so a wrap shows both forms of the money and a bridge crossing a leg on each chain.
Every leg of a central bank money token (CBDC registers of the Shared Ledger and their wrapped forms on Hoodi, the Appia tCeBM token, the GL1 PC euro token), for the window, project, chain, rail and parties selected. Bands run from the sector that sent the money, through the operation the leg served, to the sector that received it, each band in the colour of the sector at its outer end; Minted and Burnt stand for the zero address. Widths count legs across currencies, or add amounts at the decimals read on each token when one currency is chosen (amounts in two currencies never add). Hover or focus a node to follow its bands; click a band or a node, or press Enter on a node, to list its transactions. The table under the chart lists every band.
Outstanding on the Shared Ledger register by holder
Central bank money held by each sector at the end of every day with a movement, rebuilt from every leg on the Shared Ledger since block 0: an issuance adds, a redemption removes, a transfer moves the amount between holders. Bridge vaults hold what backs the wrapped tokens on Hoodi, so Hoodi is not added again. All projects together, whatever the project, chain, rail and parties filters: a register is shared. The chart covers all history; the window applies to the table below it; the currency choice applies to both. A policy wrapper is left out, since the money it wraps is counted where the wrapper holds it.
Money stack who uses which instrument, for what
Each band is a set of value legs, as wide as their number, for the window, chain, rail and parties selected. It runs from the party that used the money (the payer, or the receiver when the payer is a contract, the zero address of an issuance or an operator key), each FI by name and any other party by its kind, through the instrument that moved, to the use case of its rail and step. Securities appear as an instrument because they settle on the same chains, as collateral and in delivery versus payment. Under each instrument: its settlements, legs, the daily average over the window and its main tokens. Hover or focus a box or a band for the detail; "Contracts and operators" lists its families, as the N/A station does.
Airspace corridors between countries
Each line is a corridor on one rail of one chain, thicker with more settlements, arrow on the receiving side; dashed lines carry securities. Positions are schematic, Europe is enlarged. Hover or focus a station for its institutions and for the contracts placed there. A contract, the zero address or an operator key has no country of its own: it is placed where its money belongs (see How this is read). N/A keeps the few ends no rule could place.
Flight strips latest value legs
No flow on this rail and parties inside the window.
Traffic per week settlements, by rail
All recorded weeks (Monday to Sunday, UTC) for the chain, rail and parties selected; the shaded band is the selected window.
Corridor matrix settlements
Rows send, columns receive; click a cell, or press Enter on it, to list its transactions. The matrix counts every placed end, so a corridor can show more settlements here than in the headline sentence, which counts two parties with a country of their own. N/A is an end no rule could place: a US dollar leg (no station), a token with no currency on record, an unlabelled wallet. Detail N/A splits it into families.
Corridor board: amounts per rail and step; click a row for its transactions
| Chain | Corridor | Rail | Step | Settlements | Sent | Received | Last (UTC) |
|---|
Transactions
Calls per function
Successful calls, counted from the event each one emits; a reverted call emits none. Hover or focus for the sender that sent the most.
Who sends the transactions
Successful calls per kind of sender: FI wallets and node keys from IBM's referential, central banks, FIs and custodians from the Appia and platform referentials, operator and submitter keys from the keys tables.
Lifecycle and exceptions
Liquidations, repo close-outs, cancelled legs, forced transfers, clawbacks, bridge refunds, pauses and access changes, in settlements or calls, for the window, chain and project selected. A reverted call emits no event, so it is not counted: the chains are read from their events. Hover or focus for the last one and where they happened most.
Ends no rule could place
The N/A station of the radar, by family: what is left once contracts, the zero address and operator keys are placed where their money belongs, mostly US dollar legs, tokens with no currency on record and unlabelled wallets. Hover or focus a family for its members and tokens.
Assets moved
Money and securities tokens that moved, with the total at the decimals read on each token.
| Chain | Token | Kind | Legs | Total moved | Decimals |
|---|
How this is read
- Projects. Mandala: the Hoodi rails IBM’s nodes use (UC2a, UC2b, UC2c, UC3) and its Shared Ledger estate (deposit-token clearing, netting, the bridge to Hoodi). GL1 PC: the GL1 Programmable Compliance toolkit, policy wrappers on money and securities, its transfer and stablecoin cases. Les Gardiennes: a tokenised repo session, a money-market fund token (uMINT) against euro on two ledgers (case 2C) and through a gated Morpho Blue market (case 2D), both liquidated. Appia: the Eurosystem programme on tokenised central bank money, with the tCeBM token and its bridge, the collateral protocol, eligible securities and the credit and repo facilities. A contract belongs to the project whose deployment tracker deploys it; a tracker that only uses another project’s contract (the money a wrapper wraps, the market of another programme, a signing key) does not make it its own. A Mandala rail transaction stays Mandala even when it touches another project’s contract (UC3 openings on Appia’s option B frames).
- Every token on this page is a demonstration token on a test network or the Shared Ledger; none is issued by the institution whose instrument it stands for. Party names come from the referentials of each project (the source of every label is in parties.json); a name says which role an address plays in a demonstration.
- Hoodi (chain 560048), read only through a public node: the events of the three UC2 settlement orchestrators, the UC3 repo settler, the compliance verifier and the two key registries, from block – to block –. Only successful calls emit an event, so reverted calls are not counted.
- Hoodi, the three other projects: every transaction of the GL1 PC, Les Gardiennes and Appia contracts from the same block to block –, read whole (every log of its receipt), its token transfers netted per address as on the Shared Ledger. A transaction already counted on a Mandala rail is not counted twice.
- Shared Ledger (chain 6565), read only through rpc.shared-ledger.eu: every event from block – to block –. The token transfers of each transaction are netted per address, so a contract a value only passes through drops out and each leg runs from the party that paid to the party that received; the zero address marks an issuance or a redemption.
- Parties: IBM institutions come from IBM's referential; node keys, submitters and operators from the published keys tables; central banks, FIs and custodians of the Shared Ledger from the Appia and platform referentials. An address no referential names is shown by its first and last characters.
- A country belongs to a party. A contract, the zero address or an operator key has none, but the money it moves does, so each such end is placed by one rule, recorded on the leg (fromPlacedBy, toPlacedBy): an issuance or a redemption at the country of the key that signed it, when that key has one (the central bank for its central bank money, the FI for its deposit token); a bridge vault at the country of the party at the other end of the crossing, named by the bridge event (the beneficiary or the depositor on Hoodi, the same UETR on both chains): most crossings are an FI moving its own float between the two chains, so they show as a loop on its country; the ramp desk at the country of the FI it serves on that leg; any other contract, operator key, custodian or FX provider at the jurisdiction of the currency the leg moved (the euro at the euro area, the rupee at India). A collateral counterparty takes the country of its LEI's legal address in the GLEIF registry. What no rule places stays at N/A.
- The money stack and the N/A families group by fixed rules, written in the calculations stack, offmap and arcsNa: the user of the money is the payer, or the receiver when the payer is a contract, the zero address or an operator key; an FI is named on its own bar, the twelve busiest of the selection, the others sharing Other FIs; the instrument is the class of the token that left; the use case comes from the rail and the step; an end with no country belongs to a family by its kind and label (bridge vault, issuance, burn, FX provider, clearing contract, escrow, custody, ramp desk, operator key, FI with no country, unlabelled).
- Amounts use the decimals read on the token that moved. UC2a counts the deposit token that left the originating FI and the one that reached the beneficiary FI; UC3 counts the cash and the t-EUTBL collateral at opening and closing, and the collateral seized at liquidation.
- – UC2a legs over all history carry amounts under one millionth of a unit: they were sent at a 6-decimal scale on an 18-decimal deposit token. The flight strips mark them "scale?".
- Windows count back from the later of the two snapshot heads. Every figure on this page is computed in the browser from the published data files (flows, calls, assets, parties, status); each leg and call carries its block and transaction.
- Tokenised central bank money. A leg counts when its token is central bank money: the CBDC registers of the Shared Ledger, their wrapped forms on Hoodi, the Appia tCeBM token (euro: a joint Eurosystem issuance with a liability per national central bank) and the GL1 PC euro token and its policy wrapper. Its sector comes from the kind and label of each end, by one rule written the same in the calculations tcebm, tcebmLegs and tcebmSupply (a contract by what its label says it is: a bridge or vault, a policy wrapper, a repo, escrow or collateral contract, a clearing or settlement contract); its operation comes from the step. Legs that do not settle (a cash leg escrowed before a repo opens) are left out.
- Stock and flows. The outstanding amount is rebuilt from every settled leg of the Shared Ledger since block 0; a policy wrapper is left out, since the money it wraps is counted where the wrapper holds it; tokens with no currency on record are listed, never added to a currency. The table under the chart goes from the opening stock of the window to its closing stock through every mint and burn, by operation; transfers leave the stock unchanged. The closing stock is checked against totalSupply() read on chain, and the bridge backing compares what each MandalaBridge vault holds on the Shared Ledger with the wrapped supply on Hoodi, both read at their latest block (supply.json).
- Drill-down. A matrix cell, a corridor board row, or a band or node of the central bank money diagram lists the legs behind it for the filters selected, newest first, each with its block and a link to its transaction; the CSV holds every one (up to 5,000).
- The chain heads in the header and the strips marked LIVE are read by this browser from the two public endpoints every 15 seconds while the tab is visible; everything else is the snapshot, read at –.