Overview
The QoreChain Rollup Development Kit (RDK) is a set of client libraries (TypeScript, Python, Go, Rust and Java), an operator command-line tool and starter templates for building application-specific rollups that settle on QoreChain through the on-chain x/rdk module. With it you configure a rollup, build and sign its transactions, read its state, follow its challenge windows, issue and verify settlement receipts, and assemble cross-VM calls and withdrawal proofs. 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. This page is for developers who want to launch or operate a rollup, and for anyone deciding whether the RDK fits their application.
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 set up an application-specific rollup three ways changes and limits). This page covers all three, plus the operator lifecycle and batch commands.
Settlement Receipts
A settlement receipt is a portable record that a rollup's settlement batch was anchored to the Main Chain under a post-quantum signature. It names the rollup, the batch and the anchor, and carries the anchor's ML-DSA-87 (Dilithium-5, FIPS-204) signature, the same scheme the Main Chain uses.
QCAI Copilot
The QCAI Rollup Copilot in the RDK is a read-only helper that tries to gather the network's advisory data for one rollup — a fee estimate, network recommendations, fraud investigations that reference the rollup, the reinforcement-learning agent's status — and fold it into one plain-language read with a short list of suggestions.
Multi-VM
The RDK includes TypeScript helpers that encode a call from an EVM contract into the cross-VM precompile at 0x0000000000000000000000000000000000000901, which is designed to route it to a QoreChain Native contract on the QoreChain Native (Wasm) runtime, and a multivm-rollup scaffold template that wires them up. The tooling covers EVM → QoreChain Native only; SVM is a separate runtime and is not part of the precompile.
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 defines three DA backends; today only native is implemented.
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.
RDK on v3.2.8
QoreChain release v3.2.8 changes how rollups settle. Rollups can now put their data on the chain, let the chain order their transactions (based sequencing), settle optimistically with a fraud proof that re-runs the batch, keep their posts private to a set of members, and bind Groth16 withdrawal roots in a way that accepts any 32-byte root. STARK settlement is paused until a later release. This page describes what each change does and how to use it. It is for rollup operators and developers who build on the x/rdk module.