Blog / Introducing Confidential Transactions to OP Succinct

Introducing Confidential Transactions to OP Succinct

by Succinct 2 min read
Introducing Confidential Transactions to OP Succinct

OP Succinct now supports data confidentiality, letting chains keep transaction data private while still settling to Ethereum. Polygon CDK is the first production-ready implementation to use this feature, letting institutions keep customer data private without fragmenting liquidity.

OP Succinct: Now Supporting Data Confidentiality

The pace of institutional adoption of blockchain infrastructure has accelerated sharply this year. However, these institutions operate under regulatory and fiduciary obligations that make data exposure a non-starter. They need infrastructure that keeps data confidential without cutting them off from the rest of the onchain economy.

Our latest OP Succinct upgrade lets institutions run chains while keeping customer data confidential. Instead of publishing batch data to Ethereum like a standard public chain, institutions store transaction data on a self-hosted server they operate and post only a cryptographic commitment to that data on Ethereum. This means institutions retain full visibility into their own transaction data, while the public can verify that the chain is operating correctly without ever seeing the data itself.

Confidentiality over transaction data can be paired with access control configurations over the chain itself: custom RPC endpoints gated through enterprise identity systems, private or permissioned block explorers, custom sequencer policies, and contract-level access controls enforced within each application.

Together, this unlocks functionality like:

  • Customer data confidentiality — sensitive transaction data stays inside owned and operated infrastructure, with regulators, auditors, and counterparties receiving scoped access on the institution's terms.
  • Self-hosted infrastructure — data availability runs behind the institution's existing security perimeter, in jurisdictions it has already cleared with compliance, with no third-party dependency.
  • Global liquidity — the chain stays connected to the Ethereum ecosystem, retaining access to billions in stablecoins, tokenized assets, and counterparty capital.
  • Ethereum-anchored security — every chain transition is verified by a ZK proof settled to Ethereum, inheriting Ethereum's economic security for settlement.

A Practical Solution for Institutions

The financial system is moving onchain. Instant settlement, programmable assets, and global liquidity are reshaping how the world handles tokenized deposits, payments, and the rails underneath them.

However, public chains make every transaction globally visible by default, which is a non-starter for institutions. Regulators don't allow data exposure, and competitors would use it against them.

Today's alternatives all fall short. Permissioned chains keep data private but cut institutions off from outside liquidity. Institutional L1s solve confidentiality but introduce new trust assumptions outside Ethereum's security model. 

Only OP Succinct delivers all four properties institutions need.

Powering Privacy on Polygon CDK

Polygon CDK’s privacy configuration is the first major deployment of OP Succinct for confidentiality, allowing institutions to keep transaction data confidential within their own environment, along with other privacy features supported by Polygon’s Open Money Stack.

Read more on Polygon's blog.

Add Confidentiality With OP Succinct

Any team running an OP Stack chain can configure confidentiality with OP Succinct. Get started today:

If you’re evaluating confidential chain architectures for tokenized assets, settlement rails, stablecoin payments, or any use case where confidentiality matters, get in touch.