On October 6, 2026, Category Labs — the team behind Monad — used its OPEN summit in Singapore to unveil a design called Private Settlement. The pitch: confidential execution on a public chain, without giving up access to that chain’s shared settlement environment. The idea is also early — a published design, not a shipped product — so it’s worth separating what’s actually known from what’s still speculation.

What Was Announced

Private Settlement describes encrypted execution domains that run on top of the public Monad L1. Coverage of the announcement describes the proposed model roughly like this. These details come from secondary reporting and have not been checked against a published specification:

  • A domain is created through a standard EVM hub contract on Monad.
  • Transactions and state inside that domain would be encrypted, rather than visible the way a normal Monad transaction is.
  • Monad’s public validators would still handle ordering and atomic settlement, so a domain isn’t a separate chain; it settles into the same shared environment everyone else uses.
  • Execution inside a domain would depend on an attestation method (TEE, zkVM, or MPC) chosen by whoever creates the domain, rather than one fixed approach for the whole network.

That combination is the pitch: privacy for the parts of a trade that an institution may not want public, while still settling in Monad’s shared environment instead of a walled-off private ledger.

What’s Still Unknown

The public material reviewed for this article is thin, so the gaps are worth stating directly:

  • Threat model. The materials reviewed do not detail what each attestation option (TEE, zkVM, MPC) protects against, or what the trust assumptions are for domain operators.
  • Design partners. The materials reviewed do not name participating institutions.
  • Timeline. The summit presentation introduced a design; the materials reviewed do not give a launch date.
  • Liquidity depth. Access to shared settlement does not by itself establish executable depth for a particular market or asset. That depends on the assets, markets, and integrations actually available.

None of that means the idea is wrong. It means the gap between “design unveiled” and “institutions actually routing flow through this” is still large, and this post does not try to fill in the blanks.

Why This Matters Beyond the Headline

The reason Private Settlement is interesting isn’t privacy for its own sake — it’s what privacy plus shared settlement could unlock for on-chain finance generally. Position sizes, counterparties, and rebalancing schedules are sensitive information for many institutions, and a fully public chain exposes them. A design that keeps that information encrypted while still settling in a shared environment is aimed at that tension.

If something like this matures, venues such as lending markets, spot DEXs, and perpetual futures markets could be affected, since execution quality, liquidity access, and risk controls matter for all of them. A perp market doesn’t need every participant’s position to be public to function. Confidential execution could address some institutions’ concerns about exposing sensitive activity, if it works as described.

Where LeverUp Fits In

LeverUp uses a protocol-managed virtual liquidity architecture powered by the VMMV, with oracle-referenced pricing, execution and settlement responsibility at the protocol layer, and protocol-level risk management (docs). That is a different problem from confidential execution. This article does not establish any LeverUp integration with Private Settlement, and none has been publicly announced as of October 14, 2026.

What’s worth watching is the direction. If confidential domains attract institutional activity to Monad, they could broaden the ecosystem’s users and assets. Any benefit to LeverUp would depend on adoption and specific integrations; LeverUp’s open interest capacity remains governed by protocol risk parameters.

Related reading

Trade perpetuals on Monad: app.leverup.xyz