Agglayer Expands to OP Stack, Giving Builders the Flexibility to Launch Chains Using Any Tech Stack

Today, Polygon Labs takes the next step to aggregate everything on Agglayer by giving

The goal of Agglayer is to unify Web3, providing builders with the flexibility to launch a network using any stack and connect to any chain.

This multistack vision is coming to fruition with the addition of OP Stack support to Agglayer CDK.

Announcing the CDK OP Stack Config

Polygon Labs is integrating the OP Stack into its chain development kit (CDK), enabling seamless interoperability with Agglayer.

This new CDK config, cdk-opgeth, is a continuation of the multistack vision for Agglayer, offering builders even more flexibility in how they can architect and launch a chain to connect to Agglayer.

Chains built with this config will have no tax to connect to Agglayer. Agglayer is not economically parasitic, rather it is seeking to create a cooperative ecosystem.

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

Introducing the CDK OP STack Config

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 can tap into unified liquidity and seamless cross-chain transactions.

This addition of 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.

For chains built with this new CDK config, there's no tax to connect to Agglayer. Agglayer is not economically parasitic, rather it is seeking to create a cooperative ecosystem.

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 can tap into unified liquidity and seamless cross-chain transactions.

This multistack vision is coming to fruition with the addition of OP Stack support to Agglayer CDK.

Announcing the CDK OP STack Config

Polygon Labs is integrating the OP Stack into its chain development kit (CDK), enabling seamless interoperability with Agglayer.

This new CDK config, cdk-opgeth, is a continuation of the multistack vision for Agglayer, offering builders even more flexibility in how they can architect and launch a chain to connect to Agglayer.

Chains built with this config will have no tax to connect to Agglayer. Agglayer is not economically parasitic, rather it is seeking to create a cooperative ecosystem.

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

This new CDK config 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:

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.

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:

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.

forget the stack wars pic.twitter.com/g3UH13VqlW

Have an idea for a chain you want to build?