Rollups

A rollup executes transactions in its own environment, then commits the resulting state to a settlement layer. Ethereum's scaling overview distinguishes rollups, which derive security from their settlement layer, from systems with independent security assumptions. Running one is an application, infrastructure, security, and operations responsibility, not just a node deployment.

This section focuses on the decisions that matter after the basic definition: execution and proof model, data availability, bridge trust, sequencer design, configuration ownership, and the procedures required after launch.

The Repositories index links to the Proviroll code for OP Stack, Polygon CDK, ZK Stack, Arbitrum, and Rollup Gateway. This section explains the cross-stack operational decisions that still need to be made for each deployment.

Start here

• What are rollups?
• Optimistic rollups
• OP Stack deployment model
• Zero-knowledge rollups
• ZK Stack deployment model
• Arbitrum deployment model
• Polygon CDK deployment model
• Rollup Gateway
• Data availability
• Bridging assets

Delivery and operations

• Prepare a deployment
• Configuration options
• Deployment guide
• Monitoring
• Scaling and optimization
• Upgrading rollups

Scope

The implementation details depend on the chosen stack and deployment model. Treat framework defaults as inputs to validate against the target network, security model, and user expectations. Do not copy a test configuration into a production chain without reviewing governance, keys, bridge contracts, data availability, and incident ownership.