Skip to main content

FAQ & troubleshooting

Is mainnet live?​

Yes. Mainnet is live (chain id qorechain-vladi). The testnet preset (qorechain-diana) also remains available. Both presets ship localhost endpoint defaults; select the network with createClient({ network: "mainnet" }) and override endpoints with your node URLs. See Network & endpoints.

Why do my calls hit localhost?​

createClient() defaults to localhost endpoints. To talk to a real node, pass an endpoints object:

const client = createClient({
  endpoints: {
    rest: "https://rest.testnet.example",
    rpc: "https://rpc.testnet.example",
    evmRpc: "https://evm.testnet.example",
  },
});

The signing path (connectTx) needs the consensus rpc endpoint; CosmWasm reads also use it. REST reads use rest; EVM and qor_ calls use evmRpc.

"Cannot find module 'viem'" / "'@solana/web3.js'"​

These are peer dependencies of @qorechain/evm and @qorechain/svm respectively. Install them in your project:

npm i @qorechain/evm viem
npm i @qorechain/svm @solana/web3.js

A precompile call throws "feature not present"​

The EVM precompiles exist only on nodes running the QoreChain EVM Engine. On a plain EVM node those calls fail. If you target heterogeneous nodes, wrap each precompile call and handle the error per-call.

My amounts are off by a factor of a million​

QOR has 10^6 base uqor units. Use toBase / fromBase and do all math in base units:

toBase("1.5");       // "1500000"
fromBase("1500000"); // "1.5"

Note the EVM runtime represents QOR with 18 decimals (EVM convention), which is distinct from the Cosmos uqor base of 10^6.

Which packages are published, and where?​

All of them. The TypeScript core (@qorechain/sdk) and the EVM/SVM adapters (@qorechain/evm, @qorechain/svm) are on npm at 0.3.0; the Python client is on PyPI (pip install qorechain-sdk at 0.3.1, import qorsdk); the Rust client is on crates.io (cargo add qorechain-sdk at 0.3.0); and the Go client is on the module proxy (go get github.com/qorechain/qorechain-sdk/packages/go/...). See Install for the full per-language commands.

My mnemonic is rejected​

The SDK validates both the BIP-39 wordlist and the checksum before deriving any key, so a typo'd phrase raises instead of silently producing the wrong account. Re-check the words; use validateMnemonic to test a phrase.

Hybrid (PQC) transactions​

Local ML-DSA-87 sign/verify and the hybrid tx-building helpers are available today. Before a hybrid tx PQC-verifies on-chain, the signer's PQC public key must be registered (MsgRegisterPQCKey), or you must set includePqcPublicKey: true to embed it for auto-registration. Full hybrid submission is being finalized for the live network. See Accounts & PQC signing.