Monad Unveils Private Settlement as On-Chain Rails for Banks

High attention and emotional sentiment detected.

The company shared the design at Monad’s Open conference in Singapore on Monday. The Monad Foundation and both public cofounders amplified it the same morning. No contract address and no launch date came with it.

What Category Labs Actually Announced

Monad Private Settlement is a proposed design, not a live product. Category Labs dated the document September 2026 and called it an “institutional synopsis.”

The disclaimer is explicit. It says some features “are under development or subject to change and are forward-looking.” It adds that “there is no assurance they will be delivered as described.”

Jan Camenisch, a staff researcher at Category Labs, presented the design at Open. He later posted that the “cat is out of the bag.”

Category Labs is the former Monad Labs. The firm rebranded in December 2024 and still writes Monad’s consensus and execution clients. It is not a subsidiary of the Monad Foundation, which split out in the same month.

How Monad Private Settlement Works

A bank does not get a new chain. Instead, it registers a domain through a hub smart contract that already sits on Monad.

The creator sets the validator set, the jurisdiction, the access rules, and the attestation policy. The creator also picks which Monad tokens can move inside the domain. The design needs no protocol fork.

Users encrypt a transaction, address it to a domain, and submit it to the L1. Monad’s validators still order the transaction. Execution of the private state then happens inside the domain.

Transactions, state, and contract code stay encrypted end to end, according to the synopsis. Cross-domain messages also stay encrypted. The document claims the information stays confidential “even from the L1 itself.”

Because domains sit inside the L1, the design claims atomic settlement. In its own words, “all legs settle, or none does.” The logic builds in delivery versus payment.

Why Banks Are the Target

The pitch is simple. Client registers, payroll, treasury flows, orders, and positions cannot sit in a public mempool.

Yet a fully private chain strands liquidity and makes the operator carry governance and liability. The synopsis argues that a domain on Monad avoids both problems.

Keone Hon, cofounder and general manager at Monad, framed it for that audience. He said the design gives banks and enterprises “the best of both worlds.” He pointed to “sovereign execution environments with privacy and compliance by default.”

The Privacy Tech Is a Menu, Not a Commitment

The synopsis does not fix one privacy method. Instead, the domain creator chooses the cryptographic technique, whether that is a TEE, a zkVM, or MPC.

The page names no default scheme, circuit, or hardware attestation. It also stays silent on what the L1 stores and on how keys move between parties. Crucially, it never explains how a public validator checks a private execution without seeing it.

So “confidential even from the L1” remains a design claim for now. It is not yet a demonstrated construction. The announcement linked no whitepaper, PDF spec, or code repository.

What Monad Private Settlement Still Lacks

The gaps are large, and the synopsis does not hide them. There is no mainnet date, no testnet date, and no roadmap section.

Category Labs names no audit firm. No bank or fund has signed on as a customer. No contract address or testnet deployment exists on the public record.

The regulatory language stays cautious. The design is a “building block toward meeting jurisdictional compliance requirements.” No license, regulator, or legal memo backs that claim yet.

The fee model is also open. The document does not explain the gas split between domain validators and Monad validators. It also skips whether domain validators must run Monad too.

How It Compares to Canton and Zama

Community posts, not the official page, are already drawing comparisons. The synopsis itself does not endorse them.

Christo Sal of Kintsu laid out the clearest version. He noted that Canton started with protocol-level privacy, while Monad starts from a permissionless EVM and adds private domains. Zama, by contrast, takes the fully homomorphic encryption route.

He treated the difference as architectural, not as a debunking. The synopsis makes its own comparison to permissioned ledgers and institution-run chains, which it says fragment liquidity.

MON Price and Market Context

MON traded around $0.028 to $0.029 on 6 October, down roughly 12% on the day across sources. DefiLlama put the market cap near $337 million and fully diluted value near $2.87 billion.

Monad’s own site reports about 909 million transactions and roughly $1 billion in DeFi TVL. That footprint is the chain itself, not Private Settlement.

Nothing in the primary posts ties the price move to this design. The announcement is only hours old, so any causal price claim would be unsupported. This article is not financial advice.

What Comes Next for Monad Private Settlement

The early reaction on X skewed bullish and institutional, mostly from Monad-adjacent accounts. No major desk at CoinDesk, The Block, Bloomberg, Reuters, or DL News had covered it in the hours after the posts.

For now, the real test is delivery. The synopsis becomes a product only with a testnet, a committed privacy scheme, an audit, and a named institutional user.

Watch for a technical paper, a contract address, and the first confirmed bank. Those signals, not the slides from Singapore, will show whether Monad Private Settlement ships as described.