USD Network
Overview
USD Network is a ledger built for one job, moving USD₮, operated by a regulated company and open to inspection by anyone.
Most blockchains are general-purpose computers that happen to carry dollars. USD Network does one thing: it records who holds USD₮ and moves it between them. Narrowing the job lets the network make promises a payments system needs and a general-purpose chain cannot.
Design goals
- Dollars in, dollars out. USD₮ is the only asset and the only fee currency. Nobody has to buy a second token to send money.
- Final means final. A transfer is either sealed into a block or it is not. There are no probabilistic confirmations and no reorganisations.
- Accountable operation. USD.NET runs the network as a regulated business, works with banking partners and authorities, and can be held to account.
- Verifiable by anyone, private by default. Every block and compliance action is public, and every transfer is sealed into it; accounts and amounts are confidential. The ledger is a transparency log with signed checkpoints and Merkle proofs, and an hourly signed proof of balances.
- Compatible by default. Accounts are Ethereum-style addresses and transfers are signed with standard
personal_sign, so existing EVM wallets and keys work.
What USD Network is not
It is not a decentralised network, and it does not claim to be. There is no token, no staking, no validator election and no smart-contract platform. Where decentralisation matters most to users, the design keeps it: users hold their own keys, and the record is open for anyone to check and keep a copy of.
Components
| Component | Role |
|---|---|
| Sequencer | Orders transfers, validates them and seals signed blocks |
| Ledger | Accounts, balances, nonces and the full transfer history |
| Transparency log | RFC 9162 Merkle tree of block hashes, with signed checkpoints |
| USD Bridge | Vaults on Ethereum, Tron, Solana and BNB Chain that back bridged USD₮ |
| Fiat gateway | Licensed banking partners for bank transfers in and out |
| Explorer and API | Public read access to all of the above |
Read Architecture for how they connect.