Deployment Process
Detailed overview of the deployment steps
The deployment of Polkadot Native Rollups involves a combination of on-chain and off-chain processes. Each step must be executed in a precise sequence to ensure the success of the deployment.
Step 1: Rollup Configuration
Off-chain and on-chain process (via proxy)
This step is the starting point of the deployment journey and is explained in detail on the corresponding documentation page. At this stage, you define the configuration of your Polkadot Native Rollup through the Rollup Form. This includes critical details such as the runtime, SUDO account, and template selection.
Once the Deployment Proxy is signed, the process automatically moves to the next step.
Step 2: Reserving a paraID
On-chain process
The paraID serves as the unique identifier for your Polkadot Native Rollup. It is essential for creating Genesis files and enabling cross-chain communication. The paraID reservation is completed on-chain using the Deployment Proxy.
Step 3: Building Genesis Files (Wasm and Head) & Provisioning Resources
Off-chain process
With the paraID reserved, the PDP service generates the Genesis files for your Polkadot Native Rollup. This process also uses details provided in the Rollup Form, such as the SUDO account and the selected template. The Genesis files include:
- Wasm: Contains the genesis code for your Polkadot Native Rollup.
- Head: Contains the genesis state for your Polkadot Native Rollup.
Simultaneously, the PDP service provisions the necessary infrastructure, such as machines for collators and auxiliary services, to support your Polkadot Native Rollup.
Step 4: Registering Genesis Files (Wasm and Head)
On-chain process
After generating the Genesis files, the PDP registers them on the Polkadot Cloud. Once the registration is successful, the proxy provided in Step 1 is revoked, ensuring the PDP no longer has access to your account.
Step 5: Polkadot Native Rollup Onboarding
On-chain process
Following the successful registration of the Genesis files, the onboarding process begins. This automated process is handled by the Polkadot Cloud and takes one full epoch to complete. If an epoch is ongoing when the process starts, the total onboarding time includes the remainder of the current epoch plus one full epoch.
| Chain | Epoch Duration | Max Registration Duration |
|---|---|---|
| Polkadot | 4 hrs | 8 hrs |
| Kusama | 1 hr | 2 hrs |
| Westend | 1 hr | 2 hrs |
| Paseo | 1 hr | 2 hrs |
Step 6: Core Assignment
On-chain process
In the final step, the PDP service assigns a core to your Polkadot Native Rollup. The core allocation depends on the options you selected in the Rollup Form, such as shared or dedicated cores. Once assigned, your Polkadot Native Rollup is fully operational and ready for use.