Who this is for
This section is written for experienced L2 infrastructure engineers at a RaaS provider who already operate OP-Stack or other EVM L2 networks in production. It assumes familiarity with multisig wallets, EVM contract calls, genesis configuration, and running a trusted sequencer. It is not aimed at end-user developers building dapps on top of a CDK chain. Application teams should start with the public Agglayer SDK and ARC API references linked from the Support and resources page.The journey at a glance
A new chain moves through seven steps from intake to a live listing on Agglayer.Intake via the Jira service desk
You submit a chain request through the Polygon Help Center service desk, providing the network parameters listed in the intake form.
Polygon engineering approval and assignment
Polygon reviews the ticket, approves the request, and assigns an technical contact for the integration.
Chain attachment via Safe Wallet proposer flow
You propose the
attachAggchainToAL transaction on the appropriate Safe; Polygon executes it as a full signer. The hands-on procedure is documented in the public cdk-op-reth runbook.Rollup initialization
You call
initialize() on the new Rollup contract using the AggchainManager, setting the trusted sequencer, admin, and signer configuration. The hands-on procedure is documented in the public cdk-op-reth runbook.Genesis generation
Generate the L2 genesis file by merging the OP Stack genesis with the Polygon pre-deployed contracts. The exact procedure is documented in the Genesis Generation runbook.
Network bring-up
You stand up the trusted sequencer, AggKit, bridge service, and any mode-specific components such as a DAC committee for Validium.
What Polygon does vs. what you do
The integration is a shared workflow. Polygon owns the Agglayer protocol and signs the chain-attachment transaction. You own your chain’s components and the operational responsibility for keeping it healthy.| Polygon | You (the Integration Partner) |
|---|---|
| Approves the Jira intake request and assigns an technical contact. | Submits the Jira intake request with your chain’s parameters. |
Holds the full-signer role on the chain-attachment Safe and executes attachAggchainToAL on AgglayerManager. | Holds the proposer-only role on the Safe and submits the attachAggchainToAL proposal. |
| Operates the Agglayer node and the Agglayer contracts on L1. | Calls initialize() on the new Rollup contract using the AggchainManager. |
Maintains the canonical deployment guide and component versions in cdk-op-reth. | Generates the genesis file and brings up the trusted sequencer, AggKit (aggsender and aggoracle), bridge service indexer, and DAC committee (Validium). |
| No further action once the chain is producing certificates. | Monitors chain health and operates all Integration Partner-owned components. |
Engaging Polygon
The primary intake channel for new chains and ongoing support requests is the public Polygon Help Center service desk at Polygon Help Center. When you submit a new-chain request, you provide the following fields. Use the example values as a guide for the format Polygon expects.| Field | Example |
|---|---|
| Rollup Type | Validium |
| Network Name | pay-chain |
| Chain ID (L2) | 31415 |
| Admin Address | 0xecEA75e2854FD52b0aE5C51C88f5eA8e2eC4bf9A |
| Sequencer Address | 0x49a191471F248f7c86cA29477e6E969970BaEAdA |
| Agg Layer Type | mainnet |
| Sequencer URL | https://pay-chain-sequencer.eu-central-6.gateway.fm/ |
| Gas Token Address | ETH |
Have your network parameters finalized before submitting. Changes after Polygon assigns an technical contact cause rework for both sides.
What’s in this section
This section covers the conceptual framing and the environments. The hands-on procedures for chain attachment, rollup initialization, and genesis generation are documented in the publiccdk-op-reth runbook.
Architecture and modes
The components you run, the components Polygon runs, and the four deployment modes from an operator lens.
Environments
Public Agglayer endpoints and L1 contract addresses for the devnet, testnet, and mainnet environments.
Integration flow
The full sequence with per-step role assignments.
Support and resources
Jira service desk and the tool repositories used during integration.