cdk-op-reth runbook for OP Stack chains and the cdk-besu runbook for CDK Besu chains.
The sequence
1
Submit a Jira request
Open a new-chain request on the Polygon Help Center service desk at polygon.atlassian.net/servicedesk/customer/portal/22. The intake form fields and an example payload are listed on the overview page; have your network parameters finalized before submitting so Polygon engineering can scope the work from a single ticket.
2
Polygon engineering reviews and approves
Polygon reviews the ticket and either approves the integration or asks follow-up questions through Jira. On approval, Polygon assigns a technical contact who carries the integration through chain attachment and bring-up.
3
Chain attachment via Safe Wallet proposer flow
The Integration Partner proposes the
attachAggchainToAL transaction on the appropriate Safe; Polygon executes it as a full signer on AgglayerManager. The hands-on procedure is documented in the public cdk-op-reth and cdk-besu runbooks.4
Rollup initialization
After Polygon executes the attachment, you call
initialize() on the new Rollup contract using the AggchainManager. The call sets the admin, trusted sequencer, gas token, network name, and the initial signer configuration; the exact arguments depend on whether the chain uses AggchainECDSAMultisig or AggchainFEP. The hands-on procedure is documented in the public cdk-op-reth and cdk-besu runbooks. CDK Besu chains use AggchainECDSAMultisig.5
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. For a CDK Besu chain, the Polygon pre-deployed contracts go into the
alloc of a QBFT genesis instead; see the cdk-besu Genesis Generation and Besu Network Deployment chapters.6
Network bring-up
Stand up the trusted sequencer, AggKit, bridge service, and any mode-specific components (DAC committee for Validium). See Architecture and deployment modes for the operator-lens component map and the mode-specific extras, and the
cdk-op-reth runbook or the cdk-besu runbook for the component versions and bring-up steps.7
Chain goes live
Once your chain is producing certificates, your chain is live on Agglayer. For CDK Besu chains, the Verification and Operations chapter lists the checks that confirm the chain settles on Agglayer.
Who does what
The table below restates the seven steps with the responsibility split between the Integration Partner and Polygon, plus the tooling involved at each step.What’s next
- Architecture and deployment modes anchors the components and mode choices that the bring-up step depends on.
- Environments and contract addresses is the reference for the endpoints and L1 addresses you will point tooling at during attachment, initialization, and bring-up.
- Support and resources: Jira service desk and tool repositories.