Overview
The QoreChain Rollup Development Kit (RDK) — the x/rdk module — lets developers launch application-specific rollups that settle on QoreChain. Each rollup is an independent execution environment with its own block time, virtual machine, fee model, and sequencing, while it inherits QoreChain's security, post-quantum cryptography, and data availability guarantees.
Why QoreChain RDK
Most rollup development kits are variations on the same theme: they help you
Preset Profiles
The RDK ships preset profiles that provide turnkey rollup configurations tuned for common application categories. A preset bundles a settlement mode, sequencer mode, data availability backend, and execution parameters, so you can launch a rollup without hand-picking every option.
Deploying a Rollup
You can deploy an application-specific rollup three ways: through the Dashboard (a guided, no-code wizard), through the chain CLI (qorechaind, full control over the on-chain transaction), or programmatically with the TypeScript RDK (@qorechain/rdk plus the create-qorechain-rollup scaffolder). This page covers all three, plus the operator lifecycle and batch commands.
Settlement Receipts
A settlement receipt is a portable, self-contained proof that a rollup's
QCAI Copilot
The QCAI Rollup Copilot gathers everything the network's advisory services know
Multi-VM
A multi-VM rollup runs an EVM execution layer that can call into CosmWasm
Watchtower
The Watchtower is an auto-challenger framework for optimistic rollups. It follows
Data Availability
Data availability (DA) is the guarantee that the transaction data behind a rollup's state is published somewhere anyone can read it — so that anyone can independently reconstruct and verify the rollup's state. The RDK supports three DA backends.
ZK / STARK & Withdrawals
This page covers two related topics: the ZK proof systems (snark and stark) used by ZK-settled rollups, and the L2 → L1 withdrawal flow that moves funds from a rollup back to QoreChain once a batch is finalized.