Migrate between RaaSes
Overview of the provider migration process
A migration between RaaS providers is an operational handoff, not a redeployment of the rollup. With planning, downtime can be kept to minutes, while the total transfer spans several days for infrastructure, partners, and communications. The new operator must stand up shadow infrastructure, replicate data, and pass health checks before the DNS and Batch‑poster handover.
This document is provided for informational purposes only and does not constitute an end-to-end guide for executing the migration. An infrastructure migration between RaaS providers will require significant planning between the two providers. Offchain Labs is unable to support a third party in an infrastructure handoff. OCL does not have special knowledge or a private “fast path.” This document provides the extent of our guidance. All questions about handoff planning should be between the two RaaS teams. We can provide introductions to RaaSes.
Who should read this doc?
Chain owners and operators.
What are the must-transfer items?
Sequencer runtime, batch poster, staker/validators, DAC signer set for AnyTrust, RPC/explorer domains, alerting/monitoring credentials. Your RaaS may have other requirements.
Do chain ID or L1 contracts change?
Normally, no, the chain will stay on the same chain ID and L1 rollup contracts.
Who coordinates ecosystem partners?
Chain Owner. Typical partners include oracles, indexers, bridges, wallets, analytics, and custody, among others.
How long is the downtime?
With planning, you can keep downtime to minutes. RPC nodes will stop serving write transactions like eth_sendRawTransaction a few minutes before downtime.
The full transfer (infra spin-up, partner handovers, comms) typically spans several days.
What should we monitor during handover?
Retryables creation, batch posting cadence, Assertion Confirmation, base fee, sequencer health, DAC signer liveness. Please see 'Monitoring Tools and Considerations’ for more information.
What legal/administrative assets need to move?
Domains (RPC/explorer), CDN accounts, SSL certificates, and GitHub/S3 buckets that host snapshots. Your RaaS provider may have different requirements.
What is the process involved in migrating an existing Arbitrum (Orbit) chain from one RaaS operator to another?
Chain migration will require close coordination between the old and new chain operators. With proper planning and coordination, a migration can result in only a few minutes of downtime, with the total transfer process occurring over several days.
An end-to-end migration will require:
- The new operator will spin up appropriate nodes & infrastructure (e.g., validators, sequencers)
- Ownership transfer of any on-chain contracts.
- Ownership transfer of any important community assets / URLs (e.g., RPC or explorer URLs)
- Updating onchain parameters responsible for identifying nodes (e.g., Validator whitelist)