Skip to main content
Everything runs through one class — WalletSuiteSDK — so wallet creation, key derivation, transaction lifecycle, and on-chain reads share the same auth, types, and error surface. Signing stays local to your infrastructure.

​
Built for

Engineering teams who need typed, multi-chain wallet primitives in production — trading systems, treasury ops, fintech and payment backends, or Web3 features embedded into an existing stack. If you already own a signing layer (KMS, HSM, custodian), the SDK composes with it through Bring your own signer.

​
What you can build

  • Multi-chain wallet creation with BIP-39 mnemonics and BIP-44 derivation
  • Full transaction lifecycle — prepare, sign, broadcast — step-by-step or bundled in sdk.transfer()
  • Native and token balance queries with fiat valuation
  • Price, fee-quote, transaction status, and history queries across supported chains
  • Asset metadata, name-service resolution (ENS, UNS), NFT ownership, and token allowance checks
  • Staking and swap metadata queries on supported chains
  • Bring-your-own-signer integration — keep keys in your existing KMS, HSM, or custodian

​
Non-Custodial

WalletSuite never stores user funds or private keys. All signing happens locally. Key management remains under the integrator’s full control.
Integrators are responsible for ensuring secure key handling and compliant usage within their own systems.

​
Multi-Chain Wallet Operations

  • Consistent API across supported chain families
  • WASM-based cryptographic implementation compatible with modern runtimes
  • Wallet-agnostic — works with any key management or wallet architecture

​
What’s Included

Environment mapping
pass prod and the SDK resolves the correct endpoints
Typed API client
Typed responses for balances, assets, prices, blocks, fees, transaction status and history
TypeScript & JavaScript
full typings, ESM + CJS dual export, Node 18+