Deploying a Rollup with RaaS (Browser-Based Workshop)

Planning Your Rollup: VM, DA Layer, Governance, Gas Token

Before initiating deployment on a RaaS platform, teams must define key design parameters. Choosing the execution environment determines the virtual machine, EVM, zkEVM, WASM or hybrid model, which affects tooling compatibility and developer productivity. The choice of data availability layer, such as Ethereum blobs, Celestia, EigenDA or Avail, influences cost and finality assumptions.

Governance considerations include selecting the admin architecture, whether a multisignature wallet or DAO governance is used, and how upgrade paths are controlled. Similarly, gas token decisions, whether to use native rollup tokens or rely on standard ETH, impact user experience and token economics. These planning decisions determine the configurability allowed by providers and are typically set during initial draft stages before deployment begins.

Setting Up via No‑Code Dashboards: Step‑By‑Step Flow

Once planning decisions are finalized, deployment begins by logging into the RaaS provider’s dashboard, selecting the rollup or appchain deployment section, and initiating a new rollup. Providers such as QuickNode make this straightforward: users log in, navigate to the “Deploy a New Rollup” area, choose the framework (e.g. Arbitrum Orbit or OP Stack), designate chain naming and admin keys, and confirm foundational parameters.

The system walks users through settlement layer selection, DA layer configuration, and gas token choice. Testnet deployments go live typically within 15 to 20 minutes. RaaS dashboards show progress and provide immediate access to block explorer, faucet, RPC endpoints and monitoring tools for the newly created testnet chain.

Configuring Chain Parameters: Block Time, Calldata Cost, Fees

After deployment, teams configure chain-specific parameters: block time determines transaction cadence; calldata cost affects fee economics; and base gas price or scaling factors influence operational cost. The dashboard interfaces generally allow adjustments to block intervals, calldata size limits, and gas per operation, enabling customization aligned with usage patterns.

For example, reducing calldata cost leverages Ethereum’s EIP-4844 blobs and Proto-Danksharding to lower DA expenses on optimistic rollups. Configuring these correctly ensures that transactions remain low-cost and performant in production. Providers may also permit configuring sequencer cadence or fee adjustment policies via the dashboard for on-chain governance after genesis.

Testing and Monitoring: Dashboards, Alerts, Upgrades

Once the rollup is deployed, teams must engage in testing and monitoring.

• Testnet faucets and RPC endpoints enable trial smart contract deployment and transactions.
• Providers typically include block explorers configured for the new chain to track real-time activity and verify state transitions.
• Dedicated monitoring tools serve block production rate, latency, failed transaction count and bridging health.
• Alert systems notify teams via dashboards or external integrations when anomalies such as sequencer lag or transaction reversion spikes occur.
• Upgrade workflows are managed by the provider either via UI or guided procedures; these allow governance-controlled updates such as protocol upgrades or sequencer address rotation while preserving continuity and security.
• QuickNode supports continuous updates to core framework and dependency patches as part of their RaaS service.

Security and Cost Considerations: MEV, Decentralisation Roadmap

Security and cost planning involve both immediate and long-run considerations. MEV risk is affected by sequencer architecture: centralized sequencers may capture value through ordering policies, so teams should plan for future decentralisation by enabling sequencer rotation or shared sequencing when supported. Providers may support restaked security via EigenLayer AVS, extending Ethereum validators’ trust to the rollup’s execution and DA layers.

This design shifts security cost from bespoke validator sets to shared staked infrastructure while maintaining high decentralization assumptions. Cost projections include DA posting fees, sequencer operation, and node maintenance; RaaS providers often provide usage dashboards and forecast tools. Decentralization roadmaps should specify sequencer tapers, governance handoffs, and sequencer peer expansion to avoid central points of failure as the rollup scales.