Open data

Overview

Everything that happens on USD Network is public, and the ledger is built so you can check it rather than trust it.

USD Network is operated by one company, so the obvious question is: why believe what it says? The answer is that you do not have to. The ledger is published as open data, and its structure makes rewriting history detectable by anyone who is watching.

What is public

Accounts are confidential: who paid whom and how much is visible only to the parties. Everything below is open to everyone.

DataWhere
Every block, with its signatureusd.net/explorer/blocks, GET /blocks
That every transfer happened, when and in which blockusd.net/explorer/txs, GET /txs
Every deposit and release: amount and the other chain's transactionusd.net/explorer/bridge, GET /bridge/events
The sum of every balance, signed hourly, against the supplyusd.net/explorer/balances, GET /balances
Every freeze and unfreeze, with a reasonusd.net/explorer/compliance, GET /compliance
Signed checkpoints of the logusd.net/explorer/checkpoints, GET /checkpoint
Proofs of inclusion and consistencyGET /proof/…
Bridge vaults and bridged supplyusd.net/explorer/bridge
Solana anchors and witness cosignaturesGET /anchors, GET /witnesses

Three layers of assurance

  1. 1

    Signed blocks

    Every block is signed by the sequencer's Ed25519 key and names the hash of the block before it. Anyone holding a copy of the chain can check every link.

  2. 2

    A transparency log

    Block hashes are leaves in an append-only Merkle tree, the structure used by Certificate Transparency to keep certificate authorities honest. A small signed checkpoint commits to the whole history. Consistency proofs show that a newer checkpoint extends an older one without changing anything.

  3. 3

    Witnesses and anchors

    Every hour the latest checkpoint is written into a memo on Solana, a record USD.NET can't edit or delete. Independent organisations can check each new checkpoint for consistency with the last and cosign it; their signatures appear on the checkpoint. To show different histories to different people, USD.NET would have to deceive parties it does not control. See Checkpoints.

What this proves and what it does not

The log proves that history is consistent: once a block has been seen in a checkpoint, it can never be silently changed or removed. It does not, on its own, prove that the operator applied every rule correctly inside a block. For that there are two more checks. The hourly proof of balances shows every balance adds up to the supply and lets each account confirm it is counted. And because accounts are confidential, full replay of every transfer is open to the operator and to auditors given read access, rather than to everyone.