Monad Private Settlement

Confidential end to end

Senders, recipients, amounts and contract data are never published. The public sees encrypted transactions and a sealed fingerprint of the domain’s state.

Public view

tx0x9f3a…c71eencrypted

domainacme-treasury

state root0x41d0…8a2bsealed

fee paid by0x7b2e…19f0

Inside the domain

fromAcme Corp · Ops

toAcme GmbH · Payroll

amount2,400,000.00 USDC

memoOct payroll float

Private, but accountable

Access rules decide who can read each balance and record. Auditors and regulators get exactly the view they are granted.

access-rules.sol · 4 grants

Treasury teamread · write

External auditorbalances

Regulatorall records

Publicnone

Configured by the creator

Operators and their jurisdiction, the sign-off rule, allowed tokens, and deposit checks such as KYC and sanctions screening.

Domain config

Operators4CHSGUKUS

Sign-off3 of 4

TokensUSDC, EURC

Deposit checksKYC ✓Sanctions ✓

Liquidity stays on Monad

Domains trade against Monad’s existing pools and venues, and settle with each other all-or-nothing.

Cross-domain settlement

1,000,000.00 USDC → EURC

Locked in US bank domain09:24:01
Swapped in public Monad pool09:24:01
Credited in EU bank domain09:24:02
Settled, all legs or none09:24:02

	Monad Private Settlement	Shielded pool	Private rollupe.g. Tempo Zones	Independent chaine.g. Avalanche L1s, Canton
What it is	A private environment that runs on the public chain. Transactions go to Monad encrypted, and only the domain’s operators can open them.	A privacy vault inside one contract on the public chain. Funds go in, move privately between holders, and come out.	A separate permissioned chain beside the public chain, run by its own operators and linked back for liquidity.	A chain of its own, with its own validators, consensus and state. Some connect to sister chains through a messaging protocol.
Who orders transactions	Monad. Operators must execute in the order Monad sets, so they cannot reorder transactions inside the domain.	The public chain.	The chain’s own sequencers.	The chain’s own validators.
Who can see transactions	The parties, the operators, and anyone granted access. Operators running on trusted hardware cannot see them either.	Only the parties, plus anyone they share a viewing key with.	The parties and the chain’s sequencers.	Depends on the chain. Avalanche L1s are public unless access is closed off; Canton shows each party only its part of a transaction.
What privacy relies on	Encryption, enforced access rules and the operators chosen, much as with a bank today. Trusted hardware can strengthen it.	Cryptography, and how many others use the same pool.	The sequencers’ honesty, with correctness checked on the public chain.	Restricting who can join and read the chain.
Working with other environments	Contracts in different domains and on Monad can send each other messages, with the sender and its domain verified.	None. Anything beyond a private transfer means leaving the pool.	Funds move in and out through the bridge. Custom contracts cannot be deployed on a zone.	Avalanche L1s can message other L1s in their ecosystem. Permissioned ledgers such as Canton are cut off from public chains.
All-or-nothing settlement	Token moves between domains are all-or-nothing. Multi-step deals, such as a currency exchange, use locking contracts so nothing settles halfway.	Within a single private transfer only.	Within one zone. Moving between zones is a withdrawal followed by a deposit.	Within the chain. Across chains it depends on the bridge or messaging protocol.
Liquidity	Uses pools and venues on Monad. Assets stay locked on Monad, held separately for each domain.	Shared with the public chain, but every move in or out is public.	Shared with the public chain through the bridge.	Its own. Permissioned ledgers such as Canton are cut off from public-chain liquidity.
What outsiders still see	Encrypted transactions, deposits and withdrawals at the domain’s gateway, and amounts that pass through public pools. The roadmap closes the last gap.	Every deposit and withdrawal, and when it happened.	Deposits and withdrawals and their amounts. Recipients inside stay private.	Nothing, if access is closed off. Avalanche L1s are public by default.
Contracts and fees	Existing EVM contracts work unchanged. Fees are paid on Monad, and a bank can pay them for its customers.	Built to the pool’s fixed features; nothing to port.	A fixed set of token contracts. Fees can be paid in stablecoins.	Each chain runs its own validators and infrastructure.

Private settlement on a public chain.

Private inside, final outside

Confidential end to end

Private, but accountable

Configured by the creator

Liquidity stays on Monad

How it compares

Frequently asked questions

What the public sees