CDK Goes Multistack: Aggregate Everything, Starting with OP Stack

tl;dr

• Agglayer CDK (formerly Polygon CDK) goes multistack to unify Web3: Introducing the CDK OP Stack configuration, with native Agglayer connection 
• This new config lets builders launch performant, low-cost OP Stack chains connected to Agglayer, with the efficiency of ZK
• No tax on CDK OP Stack-configured chains to connect to Agglayer—Agglayer is not rent-seeking
• The OP Stack config joins the legacy CDK version using Erigon, known for custom token support, ZK-security, and high throughput
• Other stacks, such as Arbitrum Orbit, ABC Stack, and more, are under consideration to be added to Agglayer CDK and made native to Agglayer

Agglayer has a simple goal: unify Web3. 

Builders should have the option to launch a network using any stack and connect to any chain. L1, L2, OP Stack, ZK stacks—it shouldn’t matter. 

Today, Polygon Labs takes the next step to aggregate everything on Agglayer by giving builders a flexible option for interop: introducing the CDK OP Stack configuration, natively connected to Agglayer and using Ethereum’s top execution client (Geth). 

With forthcoming execution proofs, this new CDK (chain development kit) config gives builders more flexibility in how they architect and launch a chain to connect to Agglayer.

For chains built with the CDK OP Stack config, there’s no tax to connect to Agglayer. Agglayer is not rent-seeking.

Instead, a multistack CDK, with native Agglayer integration, gives builders maximum sovereignty to run with whatever stack works best. 

Formerly “Polygon CDK,” Agglayer CDK is a multistack toolkit for launching custom chains with default Agglayer integration. The goal is simple: expand support to as many tech stacks and chains as possible, so builders tap into unified liquidity and seamless cross-chain transactions. 

Adding the OP Stack as a config for CDK is only the beginning of the multistack story. More stacks will be added as configurations in the future, all natively integrated with Agglayer. 

Ready to build your own CDK chain? Implementation providers are here to help:

• Conduit, core builders of the OP Stack CDK configuration, and the creators of the highly performant G2 sequencer for enhanced performance in data-intensive projects. Reach out HERE
• Gateway.fm, who brought the legacy CDK Erigon from proof-of-concept to production, supports teams building with this config. Reach out HERE

More stacks mean more options. 

Right now, Agglayer CDK has two configurations, the OP Stack configuration, (cdk-opgeth) and the original CDK config (CDK Erigon) that enables custom tokens, ZK-security, and performant throughput. 

Builders choose whichever works best for them.

Unpacking the CDK OP Stack config (cdk-opgeth), using the most widely adopted Ethereum client 

The new CDK OP Stack configuration builds on Ethereum’s most used client, Geth, which has more than 50% market share. 

A quick rundown of performance for this config, cdk-opgeth. Conduit will provide G2 sequencer support to cdk-opgeth rollups, which means: 

• 60-100+ Mgas/s, or ~4,700+ peak TPS
• Security through the pessimistic proof
• Familiar developer tooling from the widely-adopted Geth client

In this first release, the OP Stack configuration offers a low-cost and high-performance “sovereign” mode, with native Agglayer connectivity. Chains connect to Agglayer with security provided by the pessimistic proof. 

This novel ZK proof ensures safety across chains: no one chain can rug any other.

Once full execution proofs are supported, there will no longer be a seven-day fraud-proof withdrawal delay. Chains built in this mode will be able to tap fast finality using Succinct’s SP1, powered by Polygon Plonky3, which leverages the security and efficiency of Polygon Plonky3 as the most performant prover in the market. Through Succinct’s OP Succinct, CDK OP Stack chains will experience fast finality and affordable proving (less than $0.005 per transaction).

Stay tuned for upcoming modes, including zkRollup and Validium, each offering different structures for data storage.

With the legacy CDK Erigon config (cdk-erigon), build a secure, tailored L2 with Agglayer connectivity

The legacy CDK config gives developers extensive customizations: native gas tokens, three core modes, and flexible pricing options, all with native Agglayer connection. 

Chains built with this client are demonstrably production ready, with over 500M transactions and 99.95% uptime in live environments.

Perfect for enterprises and security-first devs who need ZK resilience for custom chains.

An overview of performance data provided by Gateway FM from existing chains: 

• 60 Mgas/s burst or ~1000+ peak TPS
• 90% reduced storage requirements
• Custom gas token support

Builders who choose the cdk-erigon config can deploy across a number of different modes, including zkRollup for full onchain security and scalability; validium for lower-costs; and sovereign mode, for Agglayer-optimized fees. 

Have an idea for a chain you want to build? 

Check out the new Agglayer CDK developer docs here to learn more or spin up a local testnet. 

For projects who are production ready, reach out to Conduit here, and Gateway FM here.

Website | Agglayer |  X (Twitter) | Forum | Telegram | Discord | Instagram | LinkedIn | Farcaster | Polygon Knowledge Layer