@hot-labs/kit connects wallets on many chains behind one API, shows the
balances of everything the user connected, and moves value between chains: deposits into and withdrawals from the HOT
(NEAR Intents) balance account, swaps and bridges, payments signed as intents. It ships a ready-made React UI (connect,
profile, bridge, deposit) and a headless core that also runs on Node.js.
Chains: EVM, NEAR, Solana, TON, Stellar, TRON, Cosmos, Sui, Aptos, Starknet, XRP Ledger and UTXO chains (BTC, LTC, DOGE,
BCH, DASH, ZEC), plus Google login with embedded wallets (Privy).
Guides
Getting started
Install, bundler setup, first
HotKit, SSR, server useConfiguration
Every option, custom RPCs, storage, endpoints
Connectors
Default and lazy connectors, per-chain entry points, Privy, WalletConnect
Wallets and balances
kit.wallets, balances, transfers, auth, eventsIntents
The
Intents builder: transfers, swaps, payments, withdrawalsUI
Popups, sheet or modal, theme, branding, profile tabs
Errors and waits
Error classes and what “unknown outcome” means
Backends
The kit needs no API key and sends no telemetry. Besides the chains’ own nodes it talks to one backend, hex-api (hex-api.app): EVM and Solana RPC, prices and token lists, the 1Click swap proxy and the NEAR Intents relay. Every
chain’s RPC can be replaced with your own (new HotKit({ rpc: { 8453: "https://..." } })). Wallet sessions are kept in
localStorage unless you pass another storage. Details in Endpoints.
Entry points
Every entry point loads in Node.js (ESM). “browser” means the module needs
window once you call it, not to import it.