Execution clients
CDK supports two execution clients, both maintained as open source by implementation providers:- op-geth: Geth-based client with OP Stack architecture. Familiar developer environment and broad tooling support.
- op-reth: Reth-based client optimized for high throughput and lower resource consumption.
Performance
- 60 to 100+ million gas per second (Mgas/s)
- Over 4,700 peak TPS in standard configuration
- 20,000+ TPS when optimized for payment workloads
- Finality in under 60 minutes in zkRollup and validium modes
Rollup modes
Every CDK chain supports three operating modes:| Mode | Status | Description |
|---|---|---|
| Sovereign | Live | Agglayer connectivity secured by pessimistic proofs. No prover required. Default configuration. |
| Validium | In development | ZK-secured execution with offchain data storage via a DAC. |
| zkRollup | In development | Fully onchain ZK rollup for maximum security and Ethereum-aligned trust. |
Agglayer integration
All CDK chains connect to Agglayer by default. This provides unified liquidity, shared state, and cross-chain messaging as a native feature of every enterprise chain, without additional bridging infrastructure.Projects using CDK
- Ternoa
- Merlin Chain
- Magic Labs (Newton)
- Silicon Network
- Witness Chain
- WireX
- Lumia (formerly Orion)
- Okto Wallet
- Palm Network
- Prom
- OKX
- Moonveil
Continue through CDK docs
Compare execution clients, operating modes, and implementation options.
Request managed CDK deployment
Contact Polygon about a dedicated enterprise chain and managed deployment support.