Networks
What is available, per network.
66 networks are registered in this build. Registration is not a product: most of them serve nothing, and there is no page for a network this deployment cannot do anything on. These 10 are the ones it can.
| Network | Family | Balances | Network state | Payments | Payable asset | Final condition |
|---|---|---|---|---|---|---|
| Arbitrum One | EVM | yes | yes | yes | USDT | L1_CONFIRMED |
| Avalanche C-Chain | EVM | yes | yes | yes | USDT | ACCEPTED |
| Base | EVM | yes | yes | yes | USDC | L1_FINALIZED |
| BNB Smart Chain | EVM | yes | yes | yes | USDT | FINALIZED |
| Celo | EVM | no | no | yes | USDT | L1_FINALIZED |
| Ethereum | EVM | yes | yes | no | USDT | FINALIZED |
| Polygon PoS | EVM | yes | yes | yes | USDT | FINALIZED |
| Stellar | NATIVE | no | no | yes | USDC | CLOSED |
| TON | NATIVE | no | no | yes | TON | MASTERCHAIN_COMMITTED |
| XRP Ledger | NATIVE | no | no | yes | RLUSD | VALIDATED |
Generated from the deployment. Live component state is on the status page.
Why some networks are missing
Registered is not served. A network in the registry is one this build knows how to name. Serving it needs an engine, a source, and a capability that has been qualified against the live chain.
Four are held by a Data plane that is not running here. Ethereum, Tron, Solana and Bitcoin are followed for payments by a process that ingests and records those chains. It is not attached to this deployment, and a payment watch on one of them is refused rather than accepted.
Thin pages would be worse than no pages. A page per registered network would be mostly pages saying nothing, which helps nobody looking for an answer and is not something a search engine should reward.
The list moves when the deployment does. This page is generated, so a network that starts or stops being served appears or disappears rather than being remembered incorrectly.