Category: Blockchain API / RPC infrastructure / wallet operations / key-management and notifications platform
Summary: Tatum is a multi-product blockchain infrastructure vendor that packages RPC access, indexed blockchain data, notifications, fee tooling, wallet/account primitives, and local-signing key management behind one developer platform. Its first-party materials position it less as a simple node provider and more as a broad abstraction layer for teams that want to ship wallet, transaction, and monitoring features across many chains without running their own blockchain-specific stack.
What it does:
Offers unified APIs and RPC access across 130+ supported blockchain networks so developers can build against one platform instead of many chain-specific integrations
Provides indexed block data, address/activity notifications, fee-estimation tooling, and other operational surfaces that sit above raw JSON-RPC
Ships a large JavaScript/TypeScript SDK that simplifies RPC calls, wallet balances, NFT queries, and blockchain monitoring workflows
Maintains a local-signing Tatum Key Management System (KMS) that stores keys and mnemonics inside the user’s own perimeter, signs pending transactions locally, and then broadcasts through Tatum-connected workflows
Extends beyond pure infra endpoints into virtual accounts and managed wallet/account flows, which suggests a control-plane posture rather than a narrow node-access product
Key claims:
The official site markets Tatum as “Enterprise-Grade Blockchain Infrastructure” and says developers get a unified abstraction layer, APIs, RPCs, and access to all blockchains from one platform
The docs say Tatum provides access to 130+ blockchain networks and 100+ blockchain nodes, alongside indexed block data, real-time notifications, fee estimation, virtual accounts, and KMS
The SDK README frames Tatum as a developer-first gateway to blockchain for monitoring addresses, making RPC calls, querying balances and transactions, and working with NFTs
The public GitHub organization highlights both the SDK and the KMS as pinned repos, showing that the developer SDK and local-signing key-management layer are core parts of the product surface
The KMS README says private keys and mnemonics are encrypted locally and never leave the user’s perimeter, which is a key trust-model distinction compared with fully hosted custodial signing services
Whitepaper: No classic standalone whitepaper or litepaper was found during this pass. The strongest primary materials were Tatum’s official site, docs, SDK repo, KMS repo, and GitHub organization; see ../whitepapers/tatum-primary-sources-2026-04-26.md.