Agglayer CDK
For detailed protocol documentation, refer to the official Agglayer docs.
Conduit allows you to launch a ZK-powered OP Stack rollup in a fraction of the time using Agglayer CDK.
Agglayer CDK is a Polygon-powered L2 framework that combines OP Stack architecture with ZK validity proofs, enabling faster finality and native cross-chain interoperability via Agglayer.
You get full EVM compatibility, familiar tooling, and access to Agglayer’s shared liquidity ecosystem.
Supported JSON RPC Methods
Agglayer CDK uses op-geth, which maintains compatibility with standard go-ethereum (geth) JSON-RPC methods.
The supported JSON RPC methods can be found here
Key Advantages
Faster Finality
ZK validity proofs enable significantly faster withdrawals than traditional optimistic challenge periods.
- Deposits: ~2 minutes (configurable)
- Withdrawals: ~1 hour minimum (configurable based on cost vs security)
Native Agglayer Interoperability
Chains connect to the Agglayer Unified Bridge, enabling:
- Shared liquidity across connected chains
- Cross-chain messaging
- Programmable bridging via Polygon SDKs
Conduit also provides a hosted bridge UI out of the box.
Familiar OP Stack Architecture
- EVM equivalent
- Standard Ethereum tooling (Hardhat, Foundry, ethers, etc.)
- Compatible with existing OP Stack infra patterns
No new execution environment to learn.
Battle-Tested ZK Infrastructure
The ZK proving system is already running in production.
Conduit currently operates this stack for:
- Katana
- Phala
FAQ
Is this a new stack?
Not entirely.
Agglayer CDK builds on OP Stack architecture, adding ZK validity proofs and interoperability via Agglayer.
If you’re familiar with OP Stack, the development experience remains the same.
Does it support alt-DA?
Yes. Agglayer-connected chains can be deployed using the OP Succinct stack, which supports:
- Ethereum blobs
- Conduit DA
- Private DA
- EigenDA
Celestia and EigenDA support within OP Succinct are currently marked as experimental
Can I use a Custom Gas Token (CGT)?
Yes, but not self-serve. A Custom Gas Token (CGT) is possible on the Agglayer CDK stack, but you can’t select one from the deploy dashboard. To use one on an Agglayer CDK chain, contact our Support Team before deploying. A CGT replaces ETH as your chain’s native asset for paying gas. It’s treated as the chain’s native token and it must use 18 decimals.
A Custom Gas Token (CGT) can only be set when your chain is deployed. It cannot be added, removed, or changed after your chain is live, so decide before deploying.
How does bridging work?
Conduit provides:
- Hosted bridge UI
- Unified Bridge integration
- SDK-based programmable bridging via Polygon tooling
Users can bridge across the Agglayer ecosystem once connected.
What are the average deposit and withdrawal times?
Times depend on configuration and security parameters:
- Deposits: typically ~2 minutes
- Withdrawals: ~1 hour minimum
These can be tuned depending on cost vs finality requirements.
Is the ZK system audited?
Yes. The underlying components have undergone public security reviews.
- Optimism (OP Stack) : audit report
- Succinct (OP Succinct) : audit report
- Agglayer contracts : audit report
