FAQ
What is the RDK?
The Rollup Development Kit is a client and operator toolkit for designing, launching, configuring, and operating application-specific rollups on QoreChain. It talks to nodes over their public RPC / REST / gRPC / JSON-RPC surfaces and drives rollup creation, settlement-batch submission, lifecycle management, and data-availability queries. It contains no node internals.
How is the RDK related to the QoreChain SDK?
The TypeScript RDK depends on @qorechain/sdk
for accounts, transport, and quantum-safe signing. The SDK is the general dApp
developer kit; the RDK is the rollup-specific toolkit built on top of it.
Which languages are supported?
The TypeScript package (@qorechain/rdk) is the reference and at the highest
polish, alongside the qorollup operator CLI and the create-qorechain-rollup
scaffolder (all on npm). The Python, Go, Rust, and Java (JVM) clients mirror the
full surface — config, presets, utilities, read clients, accounts, and
transaction signing + broadcast — and are verified against shared cross-language
golden vectors. All are published: Python on PyPI (pip install qorechain-rdk,
imported as qorrdk), Rust on crates.io, Go via go get, and Java on Maven
Central (io.github.qorechain:qorechain-rdk).
Which network does the RDK target by default?
Testnet (qorechain-diana). Select mainnet (qorechain-vladi) explicitly to
target the live network. Both presets ship localhost endpoint defaults, so pass
endpoints to reach a real node — see the
network reference for the public endpoints and the
explorer.
What's new in v0.4.0?
Four features. The QCAI Rollup Copilot (getRollupAdvice) aggregates a live
fee estimate, network recommendations, fraud investigations, RL-agent status,
and plain-language suggestions for a rollup. Quantum-safe settlement receipts
(buildSettlementReceipt / verifySettlementReceipt) are portable records that a batch was anchored under an ML-DSA-87
(Dilithium-5) signature. Multi-VM tooling (encodeCrossVmCalldata, isCrossVmPrecompileActive
and the CROSS_VM_PRECOMPILE address) drives EVM → QoreChain Native cross-VM
calls, with a multivm-rollup template — the precompile itself is not yet
active on mainnet or testnet, so check it before relying on it. The Watchtower (watchBatches) is an
auto-challenger framework for optimistic rollups. The Copilot and receipts ship
in all five languages; the multi-VM tooling and Watchtower are TypeScript. See
the Copilot, receipts,
multi-VM, and Watchtower guides.
What can I name my rollup?
From chain v3.2.2 a new rollup id must match ^[a-z0-9][a-z0-9._-]{2,63}$:
3 to 64 characters of lowercase letters, digits, ., _ and -, starting
with a letter or digit. The chain checks this only at creation, after the fee is
paid, so the RDK checks it first — in validateRollupConfig, in createRollup,
and in qorollup create — and refuses an id the chain would refuse. Use
isValidRollupId / rollupIdError to check one yourself. Rollups created
before v3.2.2 keep their ids.
How do I choose a settlement paradigm?
See Settlement paradigms. In short:
optimistic for general-purpose app-chains that tolerate delayed finality, zk
for fast trust-minimized finality, based for host-coupled finality with a
based sequencer, and sovereign for maximum autonomy over consensus. Note that
zk cannot settle on either network yet: the chain has no way to register a
verification key until chain v3.2.7.
What does it cost to create a rollup?
Creating a rollup commits a stake (documented default 10,000 QOR) and burns a
small percentage on creation (documented default 1%). Read the live values from
rdk.params() and preview the total with estimateCreationCost. See
Stake & burn.
Can I use Celestia for data availability?
Celestia DA is planned but not yet active. Configurations may select it and
will validate with a non-fatal warning, but the network does not serve it yet
and the kit fails gracefully with a clear error if you try to use it for live
submission. Use native today. See Data availability.
Do I have to use a preset?
No. Presets are convenient, validated starting points. You can build a fully
custom configuration with RollupConfigBuilder and .set({ ... }); validation
enforces the same compatibility matrix either way.
What does the QCAI-assisted profile suggestion do?
suggestProfile(useCase) takes a plain-language description of your app and
recommends one of the five preset profiles as a starting point. If the advisory
service is unavailable, it falls back to defi and reports
source: "fallback". It is a starting point — always review and validate the
resulting configuration. See Preset profiles.
Which signer should I use?
The RDK accepts any @cosmjs OfflineSigner. For local development, a
DirectSecp256k1Wallet from a raw key works. On a network that requires the
post-quantum signature (mainnet qorechain-vladi, testnet qorechain-diana) you
need a direct signer plus a pqcKeypair on connect, so the TypeScript client
signs hybrid — see
Signing on a PQC-required network.
Where is the full API reference?
Generate it with npm run docs:api from the docs directory. See the
API reference.