Overview
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.
Wallet adapter
@qorechain/wallet-adapter adds QoreChain to Cosmos wallets that expose signDirect (Keplr, Leap, Cosmostation) and builds the transactions the chain requires: a native-lane transaction must carry an ML-DSA-87 (FIPS 204) signature next to the account's classical secp256k1 signature, and a stock wallet cannot make the ML-DSA-87 one. The adapter makes it, places it in the transaction body, and then asks the unchanged wallet for an ordinary signature. It is for dApp and wallet developers, and for tool builders who need unified QoreChain wallets, EVM authorization window messages or linked-key (authenticator) messages in JavaScript. The current version is 0.4.0.
Chain bridge and handles
This page covers two small server-side packages.
PQC Library
qorechain-pqc is the standards-only post-quantum cryptography library that QoreChain tooling is built on. It is for developers of wallets, backends, exchanges and tools who need to create or check the exact keys and signatures the chain uses, without depending on the full QoreChain SDK. It wraps independent implementations of three NIST standards (ML-DSA, FIPS 204, for signatures; ML-KEM, FIPS 203, for key encapsulation; SHAKE-256, FIPS 202, as the hash) behind one API in TypeScript/JavaScript, Python, Rust, Go, Java and C, and adds the helpers that build the bytes a hybrid QoreChain transaction signs. Version 0.2.3, Apache-2.0, checked against the registries on 27 October 2026.
Scaffolders and CLI
Three command-line tools get a QoreChain project from nothing to a typed, buildable starting point. They are for application developers (dApps) and rollup operators who work in Node.js:
QoreX Integrations
The QoreX integrations are six small npm packages for dApp developers who want the QoreX wallet to work in an EVM, Cosmos or Solana front end, and for teams who test those front ends. Three are wallet connectors for popular libraries (RainbowKit, Interchain Kit, cosmos-kit), one holds the shared types and detection helpers, and two are test tooling (a mock wallet and Playwright fixtures). All six are version 0.1.0, published on 27 October 2026, Apache-2.0.
MCP Server
The QoreChain MCP server gives AI agents and developer tools read access to QoreChain through the Model Context Protocol: blocks, transactions, accounts, validators, staking tiers, the status of the hybrid secp256k1 plus ML-DSA-87 (FIPS 204) signature, EVM contract reads, simulation and fee estimates, and unsigned transfers that the account owner signs in their own wallet. It is for developers who connect an MCP-capable client or agent to QoreChain, and for teams who want a scriptable, read-only view of the chain with stable output.
QoreChain CLI
qore reads QoreChain from the terminal. It is for developers, operators and scripts that want to look up a transaction, check whether its post-quantum signature verifies, read an account or the validator set, simulate a transaction, or prepare an unsigned transfer, without writing code. Every command runs one tool of the QoreChain MCP server, and --json prints exactly the JSON that the tool returns, so a script and an AI agent see the same data.
QoreSeal
QoreSeal is an open-source library that encrypts data to QoreChain accounts with ML-KEM-1024 (FIPS 203). An account publishes its ML-KEM-1024 public key on chain; anyone can then encrypt a payload that this account, and any other recipient the sender adds, can read. It is for dApp developers who need confidential payloads (memos, invoices, documents, bids), for auditors who need view access, and for operators of private groups and sidechains. It composes standard primitives and implements none of its own. Version 0.1.0, Apache-2.0, maintained by the QoreChain Association.
PQ Light Client
qorechain-pq-light-client is a draft specification and a reference verifier for ML-DSA-87 (FIPS 204) signed checkpoints. In the proposed design, validators sign a short checkpoint at the end of each epoch with a separate ML-DSA-87 checkpoint key, and a light client follows the chain of checkpoints by verifying those signatures and nothing else. It is for protocol researchers, relayer and bridge developers, and teams on other chains who want to review the design and test against it. Version 0.1.0, Apache-2.0, maintained by the QoreChain Association.
Custody Kit
The QoreChain custody kit is a written integration guide, a set of test vectors and small reference code for custodians and exchanges that hold customer funds on QoreChain. It explains what the network requires on each execution lane, and it shows, in readable code, the parts of an integration that are easy to get wrong: checking an address, decoding and verifying a signed transaction before it is broadcast, and deciding which incoming transfers to credit.
QoreScan
QoreScan Community is a command-line tool that inventories the cryptography of a QoreChain deployment and writes the result as a CycloneDX 1.6 CBOM (cryptographic bill of materials). It reads a node home directory, the live state of the network, TLS endpoints and Solidity sources, and records each algorithm, protocol, certificate and key it finds, with the file and line or the endpoint where it was found.
Chain Developer Kit
The chain developer kit is the part of QoreChain SDK 0.11.0 that helps Solidity and smart-contract teams build on QoreChain with the tools they already use. It adds viem chain definitions and EVM authorization window helpers to @qorechain/evm, four new project templates to create-qorechain-dapp (Foundry, Hardhat 3, viem with wagmi, and a QoreChain Native CosmWasm token), EVM quickstarts for five languages, and a reference on how the QoreChain EVM differs from Ethereum. It is for Solidity teams porting contracts from Ethereum, dApp front-end developers on wagmi and RainbowKit, CosmWasm developers, and maintainers of EVM tools who want to add QoreChain.
Asset Kit
The QoreChain Asset Kit is open-source tooling for issuing and managing permissioned tokens that represent real-world assets on QoreChain. It has two parts with different status. One part is a set of EVM contracts that run on the QoreChain EVM Engine today: adapters for two open token standards for regulated assets (ERC-3643 and CMTAT), vaults with restricted shares, and one QoreChain-specific control that requires every holder to have a registered ML-DSA-87 key. The other part is a proposal for native chain modules, published as protobuf interfaces with clients in four languages and an in-memory mock, so that applications can be designed and tested against the proposed rules.