The Bitnob Enterprise API is a separate product from the Bitnob Business API, with its own keys, base URL, and authentication. Choose a product compares the two.
What non-custodial means here
Three properties define it, and each is enforced in hardware rather than by policy alone.- Keys never leave the enclave. They are generated inside AWS Nitro Enclaves and are never exposed, including to Bitnob engineers.
- Every signature passes your policies first. The enclave releases a signature only when your enforced policy allows it.
- There is no administrative override. Bitnob cannot sign a transaction for you. Root quorum governance applies even to Bitnob-side operations on your organization.
What the platform gives you
Managing private keys, signing transactions, enforcing spending limits, and coordinating approvals across several blockchains is hard engineering. This platform provides:- Hardware-isolated key management that no single person on your team can bypass
- A declarative policy engine that runs before every signing event
- Multi-chain support across EVM chains, Bitcoin, Solana, Tron, and TON
- Gas sponsorship, so your customers never hold a fee token
- Batch transfers and HD wallets that scale from one customer to millions
Supported chains
The live list for your organization is returned by List Chains, with per-asset detail in List Assets.Key features
- Bitnob Secure Enclave. Private keys are generated and stored inside AWS Nitro Enclaves, hardware-isolated memory that never exposes key material, not even to Bitnob engineers. Every signing event is logged as an immutable audit trail.
- Declarative policy engine. Set spending limits, destination allowlists, time locks, and multi-party approval thresholds as ordered rules. Your policy runs before every signing event, and the first matching rule decides whether the Enclave signs, holds, or blocks.
- HD vault hierarchy. A single BIP-39 seed generates unlimited wallets and addresses across all supported chains. Use a dedicated vault for treasury wallets or a pool vault to assign one wallet per customer.
- Gas station abstraction. Pre-fund a gas station once per chain, send with
sponsor: true, and the gas station pays the network fee, so customer wallets never hold the native asset. For users who hold their own keys, sponsored transfers take the fee in the token instead. - 50 to 100 ms signing latency. The Bitnob Secure Enclave is optimized for low-latency signing. Fully governed transactions are signed and broadcast within milliseconds of request.
Common use cases
- A crypto exchange that needs one deposit address per customer per chain, with automated withdrawal governance: see the Exchange integration guide
- A neo-bank that holds customer balances in Bitcoin and stablecoins and needs to enforce daily spend caps
- A treasury management product that rebalances across chains and requires dual-admin approval for large transfers
- A fintech platform that processes cross-border payments and must comply with address-whitelist requirements
- A DeFi aggregator that sponsors gas fees for its users using USDC and ETH across multiple L2s
Designed for institutions
Bitnob Enterprise is built with:- Non-custodial by design: keys never leave the hardware boundary; Bitnob cannot move funds unilaterally
- Root quorum governance: a configurable set of senior approvers must sign off on policy changes themselves
- Immutable audit logs for every signing event, policy change, and approval decision
- Managed blockchain nodes with their own per-second RPC limit, so you don’t need to run your own infrastructure
- Idempotency keys on
POST,PATCH, andDELETErequests, such as Create Transaction, to guarantee safe retries under network failures