Skip to main content
The Polygon Chain Development Kit (CDK) is an enterprise-grade toolkit for building custom Ethereum Layer 2 (L2) chains. Every CDK chain connects to Agglayer by default, cross-chain interoperability, shared liquidity, and unified state are native features of the infrastructure, not optional add-ons.

​
Execution clients

CDK supports two OP Stack 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.
Both clients are supported by Conduit and Gateway, who are building open source tooling for production CDK deployments. CDK also supports Besu: a Hyperledger Besu chain with QBFT proof-of-authority consensus, run by a known set of validators and connected to Agglayer in sovereign mode. See CDK Besu and the cdk-besu runbook.

​
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: CDK Besu chains run in sovereign mode only.

​
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
…and more

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.