Skip to main content
The architecture described in this section is not a specification waiting to be built. It is running now, on a private testnet carrying the full stack: consensus, the execution kernel, the order book, the clearinghouse, the oracle, vaults, the bridge, and the data surfaces. This page is what that network looks like from the outside.
Private means pre-announcement, not inaccessible. The endpoints below are reachable, but the network is not open for general use and carries no support commitment. Public testnet access opens 20 September 2026, followed by mainnet beta on 1 November 2026 — see Milestones.

​
Chain identity

The chain ID is part of what a transaction signs over, which is what stops a transaction signed for one network from being replayed on another. Any client that constructs and signs transactions must include it — a signature that omits it, or carries the wrong one, fails verification rather than executing somewhere unintended.
Treat the chain ID as network-scoped rather than globally unique. It distinguishes this network from others in the same family, and it will change when mainnet launches. Read it from the node at startup rather than hard-coding it.

​
Endpoints

​
Checking what you are connected to

The RPC root returns the chain’s current state, which is the fastest way to confirm a connection is pointed where you think it is:
Two fields are worth reading on every startup. chain_id confirms the network. oldest_ledger_version tells you how far back this node retains history — a node pruned aggressively cannot answer historical queries even though it serves current state correctly. See State sync.

​
What to expect from a private testnet

State may be reset. Balances, positions, and history can be wiped without notice before public testnet. Nothing here carries value. Parameters move. Risk parameters, listed markets, and fee configuration are being tuned. Read them from the chain rather than assuming they are stable — see Markets. Breaking changes arrive without a notice period. The notice commitments described under Rule changes begin at public testnet. Integrate against it anyway. The execution semantics — ordering, matching, clearing, attribution — are the ones that ship. What changes before mainnet is configuration and surface polish, not how a block executes.

​
Where to go next

Architecture overview

What this network is running.

Milestones

Delivered capabilities, and the two dates ahead.

Developers

APIs, SDKs, and testnet tooling.

Testnet

Getting access when the public testnet opens.