cdk-op-reth runbook.
The sequence
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.
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.
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 runbook.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 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
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 for the component versions and bring-up steps.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.| Step | Integration Partner responsibility | Polygon responsibility | Tooling |
|---|---|---|---|
| 1. Submit a Jira request | Fill the intake form with finalized network parameters. | None at this step. | Polygon Help Center |
| 2. Polygon reviews and approves | Respond to follow-up questions on the ticket. | Review the request, approve or decline, assign a technical contact. | Jira |
| 3. Chain attachment via Safe Wallet | Propose the attachAggchainToAL transaction on the Safe (proposer-only role). | Review the proposal, sign, and execute as a full signer. | Safe Wallet, AgglayerManager on L1 |
| 4. Rollup initialization | Call initialize() on the new Rollup contract using the AggchainManager. | Available to support if the call reverts. | Foundry cast or equivalent EVM tooling |
| 5. Genesis generation | Merge the OP Stack genesis with the Polygon pre-deployed contracts and validate the output. | Maintain the canonical procedure and component versions. | cdk-op-reth |
| 6. Network bring-up | Operate the trusted sequencer, AggKit, bridge service, and mode-specific components (DAC for Validium). | None at this step. | Your chain’s node stack, AggKit, bridge service indexer |
| 7. Chain goes live | Confirm the chain is producing certificates as expected. | None at this step. | Your chain’s monitoring |
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.