Official Libraries and Developer Kits
Everything you need to build on QoreChain: a multi-language SDK, a Rollup Development Kit, a drop-in wallet adapter, and the post-quantum cryptography library the chain itself relies on. All open source on GitHub and published on npm, PyPI, crates.io, the Go module proxy, and Maven Central.
QoreChain SDK
The official multi-language SDK for building decentralized applications on QoreChain. Available for TypeScript, Python, Go, Rust, and Java, it covers accounts, queries, and transactions across the EVM, CosmWasm, and SVM runtimes, with hybrid post-quantum signing built into the TypeScript client. React hooks, EVM (viem) and SVM adapters, and a create-qorechain-dapp scaffolder round out the TypeScript toolchain.
Use it for
Install
npm i @qorechain/sdkUnique capabilities
AI pre-flight risk scoring
Scan a transaction with on-chain AI before you broadcast it. The scoring runs inside the chain as a deterministic precompile, so a wallet or dApp gets gas plus a risk and anomaly verdict in one call and can warn or block before signing.
Read the docsCross-VM calls: one signature, three VMs, atomic
Call a contract on any VM from one interface, and batch calls across EVM, SVM, and CosmWasm into a single atomic transaction signed once. Single-VM chains have nothing their SDKs could wrap to express this.
Read the docsQuantum-safe in one call
ensurePqcRegistered() registers a signer's ML-DSA-87 key on-chain, migrateToHybrid() switches it to hybrid signing, and the React kit ships a drop-in QuantumSafeBadge that shows users their address is protected.
Read the docsUnified accounts: one key, three addresses, one balance
One key renders as qor1…, 0x…, and a base58 address, all backed by a single balance. A deposit on any lane lands in the same account, so funds are never stranded per-runtime, and connectPhantomUnified bootstraps the identity from a Phantom signature.
Read the docsAuthenticator lanes: delegated spending, PQC intact
A linked Phantom or MetaMask key spends from the canonical post-quantum account through a relayer, bounded by on-chain permissions, spending limits, and expiry. Least-privilege and revocable, while the account itself stays quantum-safe.
Read the docsRollup Development Kit (RDK)
A client and operator toolkit for designing, launching, configuring, and operating application-specific rollups (app-chains) on QoreChain. The RDK talks to public RPC, REST, gRPC, and JSON-RPC surfaces and drives the on-chain rollup module: rollup creation, settlement-batch submission, lifecycle management, and data-availability queries. Ships as libraries for TypeScript, Python, Go, Rust, and Java plus the qorollup operator CLI and a project scaffolder.
Use it for
Install
npm i @qorechain/rdkUnique capabilities
Quantum-safe settlement receipts
When a rollup anchors a batch, the chain commits its state root under an ML-DSA-87 signature. The RDK turns that anchor into a portable receipt anyone can verify fully offline, on an air-gapped machine, and the same receipt verifies byte-for-byte in all five languages. A rollup kit on a non-PQC base layer cannot offer this.
Read the docsQCAI Rollup Copilot
The chain runs network-level AI advisory services on-chain: fee estimates, congestion signals, fraud investigations, circuit breakers. getRollupAdvice() (or qorollup advise) aggregates them into one plain-language, read-only view for your rollup. Other kits have nothing to wrap.
Read the docsMulti-VM rollup contracts
An EVM (Solidity) rollup contract can call an existing CosmWasm contract through a fixed precompile, and the RDK builds the calldata for you. Reuse a CosmWasm oracle, token, or registry from Solidity instead of re-implementing it, and scaffold a starter with the multivm-rollup template.
Read the docsWatchtower auto-challenger
For optimistic rollups, the RDK ships a watchtower that monitors anchored batches and automatically raises challenges, alongside preset profiles, a compatibility matrix, and native data availability.
Read the docsWallet Adapter
A drop-in adapter that adds QoreChain to stock Cosmos wallets (Keplr, Leap, Cosmostation) and produces the chain's required hybrid post-quantum transactions with no wallet-side changes. The adapter bakes the ML-DSA-87 signature extension into the transaction body before the wallet signs it, so the wallet performs a standard SIGN_MODE_DIRECT signature and never needs to know PQC is involved.
Use it for
Install
npm i @qorechain/wallet-adapterDocumentation
Unique capabilities
Post-quantum signing from stock wallets
The chain rejects any Cosmos transaction without an ML-DSA-87 hybrid signature, which stock wallets cannot produce. The adapter bakes the post-quantum signature into the transaction body before the wallet performs its standard SIGN_MODE_DIRECT signature, so Keplr, Leap, and Cosmostation work with no wallet-side changes.
Read the docsQoreChain PQC
The post-quantum cryptography library behind QoreChain: ML-DSA (FIPS 204) signatures, ML-KEM (FIPS 203) key encapsulation, and SHAKE-256 (FIPS 202) hashing with one consistent API in JavaScript/TypeScript, Go, Rust, Python, Java, and C. Standards only, wrapping audited implementations, and every binding is validated against a shared test-vector suite so a signature produced in one language verifies in every other. ML-DSA signs deterministically by default, per FIPS 204.
Use it for
Install
npm i @qorechain/pqcDocumentation
Unique capabilities
Byte-compatible across six languages
Every binding is validated against the same shared test-vector suite, so a signature produced in Python verifies in Go, Rust, Java, C, or the browser, and matches what the chain itself verifies. Standards only, wrapping audited implementations of the final NIST specs.
Read the docsDeterministic ML-DSA by default
All bindings sign ML-DSA deterministically per FIPS 204, with hedged signing as an explicit opt-in, so the same message and key produce the same signature in every language. That property is what makes cross-language and on-chain verification reproducible.
Read the docsFull Documentation
Guides, API references, and network parameters for every library live in the QoreChain documentation.