Visible to you,invisible toeveryone else

Run a validator-only L1 and the chain's data stops at the network's edge. Only nodes you admit can sync, query, or even see it.

Network access
Validator-only
Data residency
Operator-controlled
Outside visibility
None
OUTSIDENO VISIBILITYVALIDATOR-ONLY
03 / 04Privacy

How it works.The primitives underneath.

01

Validator-only networks

One configuration flag closes the chain. Only validators and the nodes they admit can connect, sync, or serve its data.

02

Data residency

Validators are machines you place: keep every copy of the ledger in a jurisdiction, a data center, or your own racks.

03

Encrypted transport

Traffic between nodes runs over TLS. Even on the network path between your data centers, the chain's data is never readable in transit.

Choose the shape.Architectures the primitives compose into.

REQUESTSPRIVATE L1
Model 01Walled Garden

Model 01

Walled Garden.

Full control over who enters the perimeter.

You decide who participates. The network sits behind a permissioned perimeter: no outsider can query it, read its transactions, or join without approval. Inside, everything is visible to participants; outside, the network is invisible.

Best for

Closed consortia, single-institution tokenization, regulated market infrastructure.

ABANK ABBANK B[ PRIVATE ]CNON-PARTY
Model 02Partitioned Ledger

Model 02

Partitioned Ledger.

Each party holds only their own ledger.

Every counterparty pair runs its own isolated ledger, exchanging settlement proofs directly rather than on a shared global one. Non-parties see nothing: no amounts, no identities, no timing.

Best for

DVP settlement, inter-bank clearing, FX netting, bilateral repo.

SHARED LEDGER$840MPUBLICsees: validAUDITORkey reveals value
Model 03Encrypted Settlement

Model 03

Encrypted Settlement.

Amounts encrypted on shared infrastructure.

Transactions run on shared infrastructure, so everyone keeps shared liquidity and interoperability, but amounts, counterparties, and logic stay encrypted. Settlement is verified without anyone reading the underlying values.

Best for

Tokenized assets, cross-institution liquidity pools, digital bonds.

Where it is used.Institutional patterns built on it.

Tokenized deposits

Commercial bank money, on-chain.

Institutions want to move commercial bank money on-chain, but a deposit at one bank is not the same instrument as a deposit at another, and a shared public ledger would expose balances and flows to competitors. Moving value between issuers has to reconcile two different liabilities without either side broadcasting its book.

Every issuer's deposit is a distinct asset, settled between counterparties without a shared global ledger.

Partitioned ledger · ICM burn-and-mint · Permissioned validators

Asset model
Per-issuer
Cross-issuer
Burn-and-mint
Visibility
Counterparty-only
ISSUER AISSUER B$ABURNICM$BMINTBANK A LEDGERBANK B LEDGER

Repo & securities lending

Positions priced, never broadcast.

Intraday repo and lending positions signal trading strategy, and broadcasting them to a shared ledger hands that signal to competitors. Desks need on-chain settlement without an on-chain book.

Each counterparty pair settles on its own ledger, invisible to the rest of the street.

Partitioned ledger · Bilateral channels · Validator-only access

Ledger
Per-pair
Visibility
Parties-only
Street view
None
AB[ PRIVATE ]CD[ PRIVATE ]EACH PAIR, ITS OWN LEDGER
NextPolicy enforced by the protocol
Build yours in the Console