Deploying Rollups

This guide covers how to deploy application-specific rollups on QoreChain using the Rollup Development Kit (RDK). The RDK provides preset profiles for common use cases and full customization for advanced deployments.

caution

The RDK and the rollup settlement layer are an actively evolving capability. Treat the parameters, presets, and maturity of individual features below as subject to change, and validate deployments on qorechain-diana before targeting mainnet.

note

The commands below use the qorechain-diana testnet (EVM chain ID 9800). Mainnet (qorechain-vladi, EVM chain ID 9801) has been live since 7 June 2026 running chain version v3.1.77 — substitute the mainnet chain ID and endpoints from the Connecting to Mainnet page when deploying on mainnet.

Overview

The QoreChain RDK allows developers to launch sovereign rollups that settle on QoreChain. Each rollup is an independent execution environment with its own block time, virtual machine, and fee model, while inheriting QoreChain's security and data availability guarantees.

Preset Profiles

The RDK ships with five preset profiles, each tuned for a common application category:

Profile	Settlement (proof)	Sequencer	DA	Gas model	VM	Intended use case
defi	zk (SNARK)	dedicated	native	EIP-1559	EVM	DeFi/AMM applications (lending, DEXs, derivatives)
gaming	based	based	native	flat	custom	High-throughput game state and real-time experiences
nft	optimistic (fraud)	dedicated	native (Celestia DA planned)	standard	CosmWasm	NFT minting and marketplace workloads
enterprise	based	based	native	subsidized	EVM	Permissioned and consortium deployments with sponsored fees
custom	fully parameterized	fully parameterized	fully parameterized	fully parameterized	fully parameterized	Set every field yourself

note

The per-preset values above match the shipped @qorechain/rdk profile defaults. The exact configuration may evolve as the RDK matures — query the authoritative values with qorechaind query rdk config (or RdkClient.params()), and note that based settlement always pairs with the based sequencer mode.

Requirements

Before deploying a rollup, ensure you meet the following requirements:

Requirement	Details
Minimum Stake	10,000 QOR (10,000,000,000 uqor)
Creation Burn	1% of the staked amount is permanently burned on rollup creation
Account	A funded QoreChain account with sufficient balance for the stake plus transaction fees

Creating a Rollup from a Preset

Deploy a rollup using one of the preset profiles:

qorechaind tx rdk create-rollup \
  --rollup-id "my-defi-rollup" \
  --profile defi \
  --from mykey \
  --chain-id qorechain-diana \
  --fees 500uqor

Example: Deploy a gaming rollup:

qorechaind tx rdk create-rollup \
  --rollup-id "battle-arena" \
  --profile gaming \
  --from mykey \
  --chain-id qorechain-diana \
  --fees 500uqor

Creating a Custom Rollup

For full control over rollup parameters, use the custom profile and specify each option:

qorechaind tx rdk create-rollup \
  --rollup-id "my-rollup" \
  --profile custom \
  --settlement optimistic \
  --sequencer dedicated \
  --da-backend native \
  --vm-type evm \
  --block-time 1000 \
  --from mykey \
  --chain-id qorechain-diana \
  --fees 500uqor

Custom parameters:

Parameter	Options	Description
`--settlement`	`optimistic`, `zk`, `based`, `sovereign`	How state transitions are verified
`--sequencer`	`dedicated`, `shared`, `based`	Transaction ordering strategy
`--da-backend`	`native`, `external`	Data availability layer
`--vm-type`	`evm`, `cosmwasm`, `custom`	Execution environment
`--block-time`	Integer (milliseconds)	Target block production interval

Submitting Batches

Rollup operators submit transaction batches to QoreChain for settlement:

qorechaind tx rdk submit-batch \
  --rollup-id "my-rollup" \
  --state-root <hex_encoded_state_root> \
  --tx-count 500 \
  --from mykey \
  --chain-id qorechain-diana \
  --fees 500uqor

Example:

qorechaind tx rdk submit-batch \
  --rollup-id "my-rollup" \
  --state-root a1b2c3d4e5f6... \
  --tx-count 500 \
  --from mykey \
  --chain-id qorechain-diana \
  --fees 500uqor

Rollup Lifecycle Management

Rollup operators can manage the lifecycle of their deployments:

Pause a Rollup — Temporarily halt block production. The rollup state is preserved and can be resumed.

qorechaind tx rdk pause-rollup \
  --rollup-id "my-rollup" \
  --from mykey \
  --chain-id qorechain-diana \
  --fees 500uqor

Resume a Rollup — Resume block production on a paused rollup:

qorechaind tx rdk resume-rollup \
  --rollup-id "my-rollup" \
  --from mykey \
  --chain-id qorechain-diana \
  --fees 500uqor

Stop a Rollup (Permanent) — Permanently stop a rollup. This action is irreversible.

qorechaind tx rdk stop-rollup \
  --rollup-id "my-rollup" \
  --from mykey \
  --chain-id qorechain-diana \
  --fees 500uqor

danger

Stopping a rollup is permanent. All associated state is archived but the rollup cannot be restarted. The staked QOR (minus the creation burn) is returned to the operator.

Querying Rollups

Get details about a specific rollup:

qorechaind query rdk rollup <rollup_id>

List all rollups on QoreChain:

qorechaind query rdk rollups

Sample output:

rollup:
  id: "my-defi-rollup"
  owner: qor1abc...xyz
  profile: defi
  settlement: zk
  vm_type: evm
  block_time: 500ms
  status: active
  total_batches: 1247
  last_state_root: "a1b2c3d4..."

QCAI-Assisted Profile Suggestion

Not sure which profile fits your use case? Use the QCAI-assisted suggestion tool:

qorechaind query rdk suggest-profile --use-case "defi lending protocol"

Sample output:

suggested_profile: defi
confidence: 0.94
reasoning: "DeFi lending protocols benefit from ZK settlement for fast finality, EVM compatibility for Solidity smart contracts, and EIP-1559 fee model for predictable gas costs."
alternative_profile: enterprise

This command analyzes your description and recommends the most suitable preset profile along with an explanation.

Tips

Start with a preset profile and customize later. Presets are optimized for their target use cases.
The 1% creation burn is a one-time cost applied to the minimum stake at deployment time.
Use based settlement if you want the simplest setup with QoreChain validators handling sequencing.
Monitor batch submissions closely. Gaps in batch submission can trigger alerts from the network.
The suggest-profile command is a helpful starting point, but review the recommendation against your specific requirements.

Overview​

Preset Profiles​

Requirements​

Creating a Rollup from a Preset​

Creating a Custom Rollup​

Submitting Batches​

Rollup Lifecycle Management​

Querying Rollups​

QCAI-Assisted Profile Suggestion​

Tips​