Developer packages
QoreChain publishes its developer tooling as small packages on the public registries (npm, PyPI, crates.io, the Go module proxy, Maven Central and Swift Package Manager). This page is the index: what each package is for, its exact registry name, language, current version, install command and status, and where to read how to use it. It is for developers who build dApps, wallets, backends and rollups on QoreChain and want to pick the right package before they read a guide.
Versions in the tables were read from the registries on 27 October 2026. Mainnet qorechain-vladi runs v3.2.5 (applied on 29 October 2026) and testnet qorechain-diana runs v3.2.6. Every package listed as published is licensed Apache-2.0.
Innovations
- One hybrid signature format in every language. The chain requires a secp256k1 signature plus an ML-DSA-87 (FIPS 204) signature on native-lane transactions. QoreSign reproduces its published test vectors byte for byte in TypeScript, Rust, Go, Swift, Kotlin and Python, and
qorechain-pqcruns one shared set of vectors in its six bindings, so a key or signature made in one language verifies in the others. - Sign-bytes form chosen from chain state, not guessed. The SDK, the wallet adapter,
chain-bridgeand the QoreSign network helpers ask the nodeGET /cosmos/upgrade/v1beta1/applied_plan/{name}for both upgrade names (v3.2.0andv3.1.98) and sign the v2 form when either height is above zero. Without a REST endpoint on these two chains they throw instead of guessing. Both networks verify v2 today (checked 27 October 2026:v3.2.0applied on mainnet at height 2,981,742 andv3.1.98on testnet at height 5,746,000). - Quickstarts that were run, not only written. For the packages that have one, the example was run on 27 October 2026 after installing from the public registry. 31 of 34 quickstart entries ran and passed; the manifest records which three did not (see Limits).
- One manifest behind the tables. The package names, versions and install commands on this page come from a single machine-readable manifest with a live version endpoint per package, the same data the SDK hub on the dashboard Developers page is built from.
How to use
Pick by what you are building.
| You want to | Use | Read |
|---|---|---|
| Read chain state, derive accounts, send hybrid-signed transactions from a script or dApp | QoreChain SDK | SDK overview, Install, Quickstart |
| Sign in your own wallet or backend, verify signatures, Sign In With QoreChain | QoreSign | QoreSign overview, Quickstart |
| Add QoreChain to Keplr, Leap or Cosmostation, generate unified wallets, build EVM window and linked-key messages | Wallet adapter | Wallet adapter |
| Run a server job that sends QOR, registers keys or deploys contracts | Chain bridge (or the SDK) | Chain bridge and handles |
Resolve an @handle to a verified address | Handles | Chain bridge and handles |
| Let your dApp use the QoreX wallet, or test it without an extension | QoreX integrations | QoreX integrations, QoreX, for developers |
| Create and operate an application rollup | RDK | Rollups overview, Deploying a rollup |
| Use the post-quantum primitives alone (ML-DSA, ML-KEM, SHAKE-256) | qorechain-pqc | Post-Quantum Signing |
| Let an AI agent or developer tool read the chain (blocks, transactions, accounts, hybrid signature status, simulation, unsigned transfers) | QoreChain MCP server | QoreChain MCP server |
| Read the chain from a terminal or a shell script, with JSON output | qore CLI | QoreChain CLI |
| Read back how a committed transaction was protected (messages, signer, fee, ML-DSA-87 layer, tier) | QoreSign transaction inspector (inspectTransaction) | QoreSign overview |
| Encrypt data to QoreChain accounts, private groups or sidechains with ML-KEM-1024 | QoreSeal | QoreSeal |
| Review or test a post-quantum light client design (checkpoint verification) | PQ light client | PQ light client |
| Integrate QoreChain as a custodian or exchange (address checks, withdrawal verification, deposit crediting) | Custody kit | Custody kit |
| Inventory the cryptography of a node, a network or Solidity sources as a CycloneDX CBOM | QoreScan | QoreScan |
| Prototype a permissioned real-world-asset token on testnet (ERC-3643, CMTAT, restricted-share vaults, post-quantum holder check) | Asset Kit | Asset Kit |
| Build and test Solidity or CosmWasm projects on QoreChain with Foundry, Hardhat or viem | Chain developer kit (SDK 0.11.0, coming) | Chain developer kit |
Install one package and run its quickstart against the public testnet first. Reads need no account, no key and no fee.
How to access
| Testnet | Mainnet | |
|---|---|---|
| Chain ID | qorechain-diana | qorechain-vladi |
| EVM chain ID | 9800 | 9801 |
| REST | https://api-testnet.qore.host | https://api.qore.host |
| Consensus RPC | https://rpc-testnet.qore.host | https://rpc.qore.host |
| EVM JSON-RPC | https://evm-testnet.qore.host | https://evm.qore.host |
| SVM JSON-RPC | https://svm-testnet.qore.host | https://svm.qore.host |
- Account and keys: none for reads. To send, you need an account with QOR (testnet QOR comes from the Faucet) and, on the native lane, an ML-DSA-87 key registered for it.
- Cost: the packages are free. Transactions pay the network fee; the fee floor is 0.1 uqor per gas.
- Signature rules: a native-lane transaction must carry a hybrid (secp256k1 plus ML-DSA-87) signature. An EVM transaction is accepted only from an account with a registered ML-DSA-87 key and an open EVM authorization window. SVM reads work and SVM transactions are not open yet. See Accounts and PQC signing.
- Quickstart conventions: the examples read the public testnet faucet account and sign with the public test phrase (
abandoneleven times, thenabout). Never fund an account derived from that phrase. No quickstart sends a transaction.
The dashboard developer page
The dashboard has a public page at dashboard.qorechain.io/developers. Checked on 27 October 2026 it has seven tabs (full walkthrough: Developers):
- SDKs: the SDK hub. Every package in the manifest, grouped by product, with a language selector, the latest version read live from each registry, install and import lines with copy buttons, the quickstart with the output the SDK team observed, known issues, and the chain ids and public endpoints. Packages that are not published show no install command.
- Transaction inspector: paste a 64-hex transaction hash on testnet or mainnet and see the status, signer, fee, whether the post-quantum layer verifies, and the security tier (PQC, Enrollment, SHAKE or Classical). It uses the QoreSign 0.1.1 function
inspectTransaction: see Transaction inspector. - PQ key status: reads the ML-DSA-87 key an address has registered on chain and its EVM authorization window, on testnet or mainnet.
- Simulator: dry-runs a signed transaction (base64 or hex
TxRaw) and shows gas use and balance changes. Nothing is broadcast. - Signing playground: testnet only. Generates a throwaway hybrid key in the browser, kept in memory, to sign and verify messages and Sign In With QoreChain requests.
- QoreX test wallet: testnet only. Injects a test wallet (
window.qorex, announced over EIP-6963 as "QoreX (mock)") into the tab so you can try dApp flows. - AI agents (MCP): the status of the QoreChain MCP server (published) and the setup for an MCP client: local
npxfirst, plus a hosted testnet endpoint that needs an API key. See QoreChain MCP server.
The same inspector check is available in code as the library function inspectTransaction in QoreSign 0.1.1 (TypeScript). The tables below and the SDK hub show the same package data; the tables were checked against the registries on 27 October 2026.
Where it is published
Each name is the exact registry name. The link on the package opens its registry page. "Published" means the version shown is installable today.
QoreChain SDK
Guides: SDK overview, Install, React guide, CLI reference. Source: qorechain/qorechain-sdk.
| Package | Language | Version | Install | Status |
|---|---|---|---|---|
@qorechain/sdk | TypeScript | 0.10.0 | npm install @qorechain/sdk | Published |
@qorechain/react | TypeScript (React) | 0.10.0 | npm install @qorechain/react @qorechain/sdk react react-dom | Published. Provider, hooks, ConnectButton and the PQC status badge (exported as QuantumSafeBadge in 0.10.0) |
@qorechain/evm | TypeScript | 0.8.0 | npm install @qorechain/evm viem | Published |
@qorechain/svm | TypeScript | 0.8.0 | npm install @qorechain/svm @solana/web3.js | Published. Reads only on the live networks |
create-qorechain-dapp | TypeScript (CLI) | 0.10.0 | npx create-qorechain-dapp my-dapp | Published |
qorechain-sdk | Python | 0.10.0 | pip install qorechain-sdk | Published |
qorechain-sdk | Rust | 0.10.0 | cargo add qorechain-sdk tokio --features tokio/macros,tokio/rt-multi-thread | Published |
github.com/qorechain/qorechain-sdk/packages/go | Go | v0.10.0 | go get github.com/qorechain/qorechain-sdk/packages/go@latest | Published |
io.github.qorechain:qorechain-sdk | Java | 0.10.0 | implementation("io.github.qorechain:qorechain-sdk:0.10.0") | Published |
QoreSign
Guides: QoreSign overview, Quickstart, Test vectors. Source: qorechain/qoresign. Version 0.1.1 was published on 27 October 2026. QoreSign signs locally; it holds no keys for you and does no threshold, MPC or hardware-wallet signing.
| Package | Language | Version | Install | Status |
|---|---|---|---|---|
@qorechain/qoresign | TypeScript | 0.1.1 | npm install @qorechain/qoresign | Published. Includes inspectTransaction and fetchEvmWindow (new in 0.1.1) |
qorechain-qoresign | Rust (imports as qoresign) | 0.1.1 | cargo add qorechain-qoresign | Published |
github.com/qorechain/qoresign/go | Go | v0.1.1 | go get github.com/qorechain/qoresign/go@v0.1.1 | Published |
qorechain-qoresign | Python 3.9+ (imports as qoresign) | 0.1.1 | pip install qorechain-qoresign | Published, new in 0.1.1. Wheels for macOS (arm64, x86_64) and Linux (x86_64, aarch64); no Windows wheel yet. Offline functions only |
QoreSign (Swift package) | Swift (iOS 16+, macOS 13+) | 0.1.1 | .package(url: "https://github.com/qorechain/qoresign", from: "0.1.1"), product QoreSign | Published as a GitHub release; the binary framework downloads from it |
io.github.qorechain:qoresign | Kotlin / JVM (JVM 17+, Kotlin 2.3+) | 0.1.1 | implementation("io.github.qorechain:qoresign:0.1.1") | Published |
io.github.qorechain:qoresign-android | Kotlin (Android API 24+, Kotlin 2.3+) | 0.1.1 | implementation("io.github.qorechain:qoresign-android:0.1.1") | Published. Same API as the JVM artifact; its example was run on the JVM artifact only, not on an Android device |
The Kotlin and Android artifacts need the Kotlin 2.3 or later compiler in your project; a project on Kotlin 2.1 fails to compile against them.
The TypeScript package has a @qorechain/qoresign/network subpath, and the Go module has the same helpers except inspectTransaction and fetchEvmWindow: fetchPqKeyStatus, resolveSignBytesVersion, simulateTx (with balance changes), suggestGasLimit, broadcastTx, submitWithSignBytesFallback (one fallback, then it stops), verifySiwqWithChain and verifyMessageWithChain. The Rust, Swift, Kotlin and Python packages have no network code.
QoreSeal
Page: QoreSeal. Source: qorechain/qoreseal. QoreSeal 0.1.0 encrypts data to QoreChain accounts, private groups and sidechains with ML-KEM-1024 (FIPS 203). The encryption works offline; reading a recipient's key from the chain needs the KEM key registry, which is live on the testnet and whose read route answers on mainnet since v3.2.5 (applied 29 October 2026; no key published there yet when checked). The construction is pending an external review before 1.0.
| Package | Language | Version | Install | Status |
|---|---|---|---|---|
qorechain-qoreseal | Rust (imports as qoreseal) | 0.1.0 | cargo add qorechain-qoreseal | Published |
github.com/qorechain/qoreseal/go | Go | v0.1.0 | go get github.com/qorechain/qoreseal/go@v0.1.0 | Published |
qorechain-qoreseal | Python 3.9+ (imports as qoreseal) | 0.1.0 | pip install qorechain-qoreseal | Published. Wheels for macOS (arm64, x86_64) and Linux (x86_64, aarch64); no Windows wheel yet |
QoreSeal (Swift package) | Swift (iOS 16+, macOS 13+) | 0.1.0 | .package(url: "https://github.com/qorechain/qoreseal", from: "0.1.0"), product QoreSeal | Published as a GitHub release; the binary framework downloads from it |
io.github.qorechain:qoreseal | Kotlin / JVM (JVM 17+, Kotlin 2.3+) | 0.1.0 | implementation("io.github.qorechain:qoreseal:0.1.0") | Published on Maven Central |
io.github.qorechain:qoreseal-android | Kotlin (Android API 24+, Kotlin 2.3+) | 0.1.0 | implementation("io.github.qorechain:qoreseal-android:0.1.0") | Published on Maven Central |
@qorechain/qoreseal | TypeScript | none yet | none | Not published to npm (404 on 27 October 2026). The source is in the repository |
PQ light client
Page: PQ light client. Source: qorechain/qorechain-pq-light-client. A draft specification and reference verifiers for ML-DSA-87 signed checkpoints. It does not connect to mainnet or testnet: QoreChain does not produce the checkpoints it verifies and no chain support is scheduled. It runs against simulated validator sets and shared test vectors.
| Package | Language | Version | Install | Status |
|---|---|---|---|---|
@qorechain/pq-light-client | TypeScript | 0.1.0 | npm install @qorechain/pq-light-client | Published. Depends on @qorechain/pqc 0.2.3 |
qorechain-pq-light-client | Rust (library qorechain_pq_light_client) | 0.1.0 | cargo add qorechain-pq-light-client | Published |
github.com/qorechain/qorechain-pq-light-client/go | Go (package pqlightclient) | v0.1.0 | go get github.com/qorechain/qorechain-pq-light-client/go@v0.1.0 | Published |
Custody kit
Page: Custody kit. Source: qorechain/qorechain-custody-kit. An integration guide, reference code and test vectors for custodians and exchanges, in TypeScript, Python, Go, Rust and Java. It is reference code to read, copy or vendor, not a package set: the only registry entry is the Go module.
| Package | Language | Version | Install | Status |
|---|---|---|---|---|
GitHub release v0.1.0 | TypeScript, Python, Go, Rust, Java | 0.1.0 | git clone https://github.com/qorechain/qorechain-custody-kit, then build the folder for your language | Published, 27 October 2026. No npm, PyPI, crates.io or Maven package, by design |
github.com/qorechain/qorechain-custody-kit/code/go | Go (package custodykit) | v0.1.0 | go get github.com/qorechain/qorechain-custody-kit/code/go@v0.1.0 | Published |
QoreScan
Page: QoreScan. Source: qorechain/qorescan. QoreScan Community 0.1.0 inventories the cryptography of a QoreChain deployment (a node home directory, live network state, TLS endpoints and Solidity sources) and writes a CycloneDX 1.6 CBOM and Markdown reports. It is an inventory aid, not a certification or an audit.
| Package | Language | Version | Install | Status |
|---|---|---|---|---|
GitHub release v0.1.0 | Binaries for macOS, Linux and Windows (amd64, arm64) | 0.1.0 | download and check against qorescan_0.1.0_checksums.txt | Published, 27 October 2026 |
@qorechain/qorescan | npm wrapper (Node.js 18+) | 0.1.0 | npx @qorechain/qorescan scan ... | Published. Downloads and checks the release binary on first run |
qorescan | PyPI wrapper (Python 3.9+) | 0.1.0 | pipx run qorescan scan ... or pip install qorescan | Published. Same behaviour as the npm wrapper |
github.com/qorechain/qorescan | Go | v0.1.0 | go install github.com/qorechain/qorescan/cmd/qorescan@v0.1.0 | Published. Go 1.26 |
Asset Kit
Page: Asset Kit. Source: qorechain/qorechain-asset-kit. QoreChain Asset Kit 0.1.0 is open-source tooling for permissioned real-world-asset tokens: EVM contracts (an ERC-3643 module, a CMTAT rule and restricted-share vaults over a guard that requires a registered ML-DSA-87 key), Foundry deployment scripts and an issuer console, plus clients for a proposal of native modules (x/asset, x/identity, x/compliance, x/settlement, x/attest) that is not scheduled and exists on no network. The contracts work on testnet only: the 0x0A02 precompile is not active on mainnet, where the guard fails closed. Pre-1.0, not audited; the legal templates in the repository are unreviewed drafts, not legal advice.
| Package | Language | Version | Install | Status |
|---|---|---|---|---|
GitHub release v0.1.0 | Solidity contracts, issuer console, protos, docs | 0.1.0 | git clone --recurse-submodules https://github.com/qorechain/qorechain-asset-kit, or forge install qorechain/qorechain-asset-kit@v0.1.0 | Published. The contracts and the console are used from the repository |
io.github.qorechain:asset-kit | Java 17 (client for the proposal) | 0.1.0 | implementation("io.github.qorechain:asset-kit:0.1.0") | Published |
github.com/qorechain/qorechain-asset-kit/clients/go | Go (package assetkit, client for the proposal) | v0.1.0 | go get github.com/qorechain/qorechain-asset-kit/clients/go@v0.1.0 | Published |
qorechain-asset-kit on PyPI | Python | none yet | none | Coming. Not on PyPI (404 on 28 October 2026) |
@qorechain/asset-kit on npm | TypeScript | none yet | none | Coming. Not published (404 on 28 October 2026) |
Chain developer kit (SDK 0.11.0)
Page: Chain developer kit. Source: qorechain/qorechain-sdk. The part of QoreChain SDK 0.11.0 for Solidity and smart-contract teams: viem chain definitions and EVM authorization window helpers in @qorechain/evm, four new create-qorechain-dapp templates (Foundry, Hardhat 3, viem with wagmi, and a QoreChain Native token), EVM quickstarts and a page on how the QoreChain EVM differs from Ethereum.
Coming. SDK 0.11.0 is tagged on GitHub (v0.11.0) and its npm release is pending: on 27 October 2026 npm served @qorechain/sdk 0.10.0, @qorechain/evm 0.8.0 and create-qorechain-dapp 0.10.0, and @qorechain/sdk@0.11.0 returned 404. Until npm shows 0.11.0, the new chain definitions, window helpers and templates cannot be installed; the 0.10.0 packages in the SDK table are what you get today. 0.11.0 changes the npm packages only: the Python, Rust, Go and Java SDKs stay at 0.10.0.
Rollup Development Kit (RDK)
Guides: Rollups overview, Deploying a rollup, Rollup Development Kit architecture. Source: qorechain/qorechain-rdk.
| Package | Language | Version | Install | Status |
|---|---|---|---|---|
@qorechain/rdk | TypeScript | 0.8.0 | npm install @qorechain/rdk | Published. Signs hybrid when you pass a pqcKeypair; reads need no key |
@qorechain/rdk-cli | TypeScript (CLI qorollup) | 0.8.0 | npm install -g @qorechain/rdk-cli | Published. Since 0.6.2 it launches through the npm bin link (0.6.1 and earlier printed nothing). Since 0.7.1 its transaction commands sign hybrid when they resolve your post-quantum key (0.7.0 and earlier signed classical only, which the networks refused) |
create-qorechain-rollup | TypeScript (CLI) | 0.8.0 | npx create-qorechain-rollup my-rollup | Published |
qorechain-rdk | Python (3.10+, imports qorrdk) | 0.8.0 | pip install qorechain-rdk | Published. Reads work; from 0.8.0 transactions sign hybrid when you pass a post-quantum keypair (earlier versions signed classical only) |
qorechain-rdk | Rust | 0.8.0 | cargo add qorechain-rdk | Published. Reads work; from 0.8.0 transactions sign hybrid when you pass a post-quantum keypair (earlier versions signed classical only) |
github.com/qorechain/qorechain-rdk/packages/go | Go | v0.8.0 | go get github.com/qorechain/qorechain-rdk/packages/go@v0.8.0 | Published. Reads work; from 0.8.0 transactions sign hybrid when you pass a post-quantum keypair (earlier versions signed classical only) |
io.github.qorechain:qorechain-rdk | Java (Java 21+) | 0.8.0 | implementation("io.github.qorechain:qorechain-rdk:0.8.0") | Published. Reads work; from 0.8.0 transactions sign hybrid when you pass a post-quantum keypair (earlier versions signed classical only, and needed Java 17) |
Post-quantum primitives (qorechain-pqc)
Guide: Post-Quantum Signing. Source: qorechain/qorechain-pqc. ML-DSA signing is deterministic by default in all bindings; hedged signing is an explicit opt-in.
| Package | Language | Version | Install | Status |
|---|---|---|---|---|
@qorechain/pqc | TypeScript | 0.2.3 | npm install @qorechain/pqc | Published |
qorechain-pqc | Python (3.9+) | 0.2.3 | pip install qorechain-pqc | Published. Needs liboqs; the first import builds it if missing (git, CMake and a C compiler) |
qorechain-pqc | Rust | 0.2.3 | cargo add qorechain-pqc | Published |
github.com/qorechain/qorechain-pqc/go | Go | v0.2.3 | go get github.com/qorechain/qorechain-pqc/go | Published |
io.github.qorechain:qorechain-pqc | Java | 0.2.3 | implementation("io.github.qorechain:qorechain-pqc:0.2.3") | Published |
| C library | C | 0.2.3 | build c/ from the repository (needs liboqs and OpenSSL) | Source only, no package registry |
Wallet adapter
Page: Wallet adapter. Source: qorechain/qorechain-wallet-adapter.
| Package | Language | Version | Install | Status |
|---|---|---|---|---|
@qorechain/wallet-adapter | TypeScript (ES module, plain JavaScript with typings) | 0.4.0 | npm install @qorechain/wallet-adapter @cosmjs/stargate @cosmjs/proto-signing | Published. No tested quickstart |
Chain bridge
Page: Chain bridge and handles.
| Package | Language | Version | Install | Status |
|---|---|---|---|---|
@qorechain/chain-bridge | TypeScript (Node.js server) | 0.2.3 | npm install @qorechain/chain-bridge | Published. No tested quickstart. The registry lists no source repository |
Handles
Page: Chain bridge and handles.
| Package | Language | Version | Install | Status |
|---|---|---|---|---|
@qorechain/handles | TypeScript | 0.1.0 | npm install @qorechain/handles | Published. Verifies a handle resolution against a pinned registry key. It does not pin addresses itself: the caller supplies the pin store and decides when to pin. No tested quickstart. The registry lists no source repository |
QoreX integrations
Guide: QoreX, for developers. Source: qorechain/qorex-integrations. All six were published on 27 October 2026.
| Package | Language | Version | Install | Status |
|---|---|---|---|---|
@qorechain/qorex-types | TypeScript | 0.1.0 | npm install @qorechain/qorex-types | Published. Finds QoreX (EIP-6963 and the native provider) |
@qorechain/qorex-rainbowkit | TypeScript | 0.1.0 | npm install @qorechain/qorex-rainbowkit @rainbow-me/rainbowkit wagmi viem @tanstack/react-query | Published |
@qorechain/qorex-interchain-kit | TypeScript (React) | 0.1.0 | npm install @qorechain/qorex-interchain-kit @interchain-kit/core @interchain-kit/react | Published |
@qorechain/qorex-cosmos-kit | TypeScript (React) | 0.1.0 | npm install @qorechain/qorex-cosmos-kit @cosmos-kit/core @cosmos-kit/react | Published. With @cosmos-kit/react 2.24 pass throwErrors={false}; the README snippet omits it |
@qorechain/qorex-wallet-mock | TypeScript | 0.1.0 | npm install -D @qorechain/qorex-wallet-mock | Published. A test wallet that signs for real on testnet |
@qorechain/qorex-synpress | TypeScript | 0.1.0 | npm install -D @qorechain/qorex-synpress @playwright/test | Published. Playwright fixtures; extension mode throws today |
Connect (deprecated)
| Package | Language | Version | Install | Status |
|---|---|---|---|---|
@qorechain/connect | TypeScript | 0.2.1 | none | Deprecated and no longer maintained. Do not use it for new work. Replace it as in the table below |
@qorechain/connect is marked deprecated on npm. Its peer range is @qorechain/wallet-adapter ^0.2.1, which does not include 0.4.0, and it does not open an EVM authorization window, so an EVM send through it is refused until the account has a registered key and an open window. The repository listed in its registry metadata is not publicly reachable.
| Need | Use instead |
|---|---|
| Detect QoreX (EVM, native, Solana) | @qorechain/qorex-types |
| EVM dApps with RainbowKit and wagmi | @qorechain/qorex-rainbowkit |
| Cosmos dApps | @qorechain/qorex-interchain-kit (or @qorechain/qorex-cosmos-kit) |
| Hybrid signing in your own wallet or backend | @qorechain/qoresign |
QORel, the IBC relayer
| Package | Where | Version | Install | Status |
|---|---|---|---|---|
QORel (qorel) | GitHub release qorel-v0.1.0, Homebrew, container ghcr.io/qorechain/qorel | 0.1.0 | brew install qorechain/tap/qorel | Published as a pre-release. IBC v1 only; testnet only. See QORel |
MCP server and CLI
Pages: QoreChain MCP server, QoreChain CLI. Source: qorechain/qorechain-mcp (public). Both read the chain and neither signs, holds keys or broadcasts. Published on 27 October 2026.
| Package | Language | Version | Install | Status |
|---|---|---|---|---|
@qorechain/mcp | TypeScript (Node.js server, bin qorechain-mcp) | 0.1.0 | npx -y @qorechain/mcp | Published. stdio and Streamable HTTP. A hosted endpoint, https://mcp.qorechain.io/mcp, needs an API key, requested from your dashboard |
qorechain-mcp | Python (3.10+) | 0.1.0 | pip install qorechain-mcp (or uvx qorechain-mcp) | Published. Same tools as the npm package; stdio only |
@qorechain/qore-cli | TypeScript (CLI qore) | 0.1.0 | npm install -g @qorechain/qore-cli | Published. --json output identical to the MCP tool output |
Planned (not published)
These are not on their registry yet, so there is nothing to install and the behaviour described for them cannot be used yet. Each returned 404 (or was not listed) on 27 October 2026.
| Package | Intended use | Status |
|---|---|---|
@qorechain/qoreseal on npm | QoreSeal for TypeScript | Not published; the source is in the repository |
qorechain-asset-kit on PyPI, @qorechain/asset-kit on npm | The Asset Kit clients for Python and TypeScript | Not published; use a clone of the repository |
@qorechain/sdk, @qorechain/evm, @qorechain/react, @qorechain/svm, create-qorechain-dapp 0.11.0 on npm | The chain developer kit | Tagged on GitHub, npm release pending |
How to get live versions
The tables are a snapshot. To read the current version of a package yourself:
| Registry | Request | Field |
|---|---|---|
| npm | https://registry.npmjs.org/<name>/latest | version |
| PyPI | https://pypi.org/pypi/<name>/json | info.version |
| crates.io | https://crates.io/api/v1/crates/<name> (send a User-Agent header or the request is refused) | crate.max_stable_version |
| Go | https://proxy.golang.org/<module>/@latest | Version (remove the leading v) |
| Maven Central | https://repo1.maven.org/maven2/<group path>/<artifact>/maven-metadata.xml | <release> |
| Swift | https://api.github.com/repos/qorechain/qoresign/releases/latest | tag_name (remove the leading v); unauthenticated GitHub calls are limited to 60 per hour per address |
For a scoped npm name keep the @, for example https://registry.npmjs.org/@qorechain/sdk/latest. A 404 means the package is not published. The Go proxy can answer @latest from a cache for a short while after a release, so pin the version in the command when you need a specific one (the RDK Go install above does). Each package page on its registry also shows the version and the release history.
Limits and known issues
- Two live networks, different versions. Mainnet runs v3.2.5 (since 29 October 2026) and testnet runs v3.2.6. A feature that exists only on testnet (v3.2.6 items, the EVM PQC precompiles) is marked on its own page.
- Not live yet:
@qorechain/qoresealon npm, the Asset Kit on PyPI and npm (and its native modules, a proposal that is not scheduled), SDK 0.11.0 (the chain developer kit) on npm, SVM transactions, and the EVM precompiles on mainnet (they are active on testnet only; see the SDK overview for the lane-by-lane list). - QoreSeal registry and the PQ light client. Encrypting to an address read from the chain needs the KEM key registry, live on testnet, and its read route answers on mainnet since v3.2.5. The PQ light client does not connect to either network; no chain support for its checkpoints is scheduled.
- Kotlin 2.3 or later. The QoreSign and QoreSeal Kotlin and Android artifacts need the Kotlin 2.3 or later compiler; Kotlin 2.1 fails to compile against them.
- No Windows wheels. The QoreSign and QoreSeal Python packages have wheels for macOS and Linux only; other platforms build from the source distribution, which needs Rust.
- Examples not run: of the 34 quickstart entries, 31 ran and passed on 27 October 2026. The QoreSign Python example was run after the package was published (macOS arm64 and Linux aarch64), and the QoreSign Android example was not run on a device. The wallet adapter, chain bridge and handles have no quickstart, so their examples in this manual come from the package typings and source and were not run end to end.
@qorechain/rdk-clibefore 0.6.2 printed nothing when started through the npm bin link, and its--versionprinted 0.4.1.@qorechain/rdkbefore 0.7.0 built withdrawal proofs that never verified on chain. Use 0.8.0.- cosmjs version conflict.
@qorechain/wallet-adapterand@qorechain/chain-bridgeuse cosmjs 0.32; the SDK uses cosmjs 0.39. Installing the adapter next to the SDK in one project makes npm reportERESOLVE. Keep them in separate projects or pass--legacy-peer-deps. - Nested SDK copy in older RDK releases.
@qorechain/rdk0.6.2 and earlier depend on@qorechain/sdk^0.9.0, so an app on SDK 0.10.0 got a second, nested SDK 0.9.x copy. From 0.7.0 the kit depends on@qorechain/sdk^0.10.0and shares one copy. - Classical-only RDK clients before 0.8.0. The Python, Rust, Go and Java RDK clients before 0.8.0 sign classical only, which the native lane refuses on both networks (and
qorollupdid so before 0.7.1); upgrade to 0.8.0, which signs hybrid in all five languages when given a post-quantum keypair. - Packages without a public source repository.
@qorechain/chain-bridgeand@qorechain/handleslist no source repository in their registry metadata. You can read the published package contents on npm. - Python
qorechain-pqchas no seeded key generation in 0.2.3, and it needs liboqs.