Category: institutional wallet infrastructure / custody-and-compliance control plane / wallet-as-a-service and transaction-policy platform
Summary: Liminal is best cataloged as wallet-and-operations infrastructure for exchanges, VASPs, and other digital-asset institutions rather than as a simple custodian. Its official docs expose a fairly broad operating stack: API-created hot wallets, MPC warm wallets, multisig cold wallets, watch-only wallets, Gas Station and Sprayer fee/refill automation, Smart Refill and Smart Consolidation flows, web-and-mobile approval workflows, and a Firewall policy layer that combines internal transfer rules with Notabene Travel Rule and TRM Labs transaction-risk screening. That product surface makes Liminal look less like a single custody vault and more like an institutional wallet control plane with embedded compliance and transaction automation.
What it does:
Provides hot deposit and withdrawal wallets managed via API for exchanges and other digital-asset businesses
Supports MPC warm wallets, multisig cold wallets using hardware devices, and watch-only wallets for external-address monitoring without key custody
Offers a web platform and mobile app for wallet management, approvals, policy administration, and organisation-level role/quorum controls
Automates operational tasks including gas-fee top-ups, deposit-address spraying, withdrawal-wallet refills, and asset consolidation
Adds a Firewall layer that can accept, reject, or route transactions for extra approvals based on transfer, Travel Rule, and transaction-risk policies
Integrates with Notabene for Travel Rule workflows and TRM Labs for transaction-risk monitoring
Publishes a public status page and a large first-party docs corpus with operational, compliance, and API guidance
Key claims:
The docs overview describes Liminal as a software solution for web3 institutions, exchanges, and other VASPs, and says it offers wallet infrastructure plus web and mobile platforms for managing wallets, transactions, and operations
The overview says Liminal provides three service lines: Wallet-as-a-Service (WaaS), Managed Custody, and a Whitelabel Solution
The key-features page says Liminal supports warm MPC wallets, cold multisig wallets, and hot API-based wallets, alongside role-based access control, admin quorum, team-based approvals, transaction policies, and automation features
The wallets guide adds a fourth operating model—watch-only wallets for balance and transaction monitoring without storing private keys—and says hot wallets are created and managed through APIs
The Gas Station guide says Liminal automatically refills wallets with native gas assets, supports Sprayer flows for deposit-wallet addresses, and is created per protocol for an organisation
The Firewall docs say transactions are evaluated across Travel Rule, Transaction Risk, and Transfers policies, with outcomes of accept, reject, or additional approval; the docs also name Notabene and TRM Labs as integrated providers
The Travel Rule configuration guide shows concrete Notabene credential wiring inside Vaults, which reinforces that compliance is integrated into the operational product rather than bolted on as a marketing claim
The docs llms.txt is unusually revealing: it enumerates a large first-party surface covering exchange operations, staking, Travel Rule, TRM integration, wallets, consolidation, Gas Station, Firewall, and API-backed workflows
Whitepaper: No canonical standalone Liminal whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official docs corpus, the main site, and the public status surface; see ../whitepapers/liminal-primary-sources-2026-04-30.md.