Cowrie Research

liminal

5 min read

Liminal

  • Name: Liminal
  • URL: https://www.liminalcustody.com/
  • Category: institutional wallet infrastructure / custody-and-compliance control plane / wallet-as-a-service and transaction-policy platform
  • Tags: ethereum-ecosystem
  • Summary: Liminal is best kept as a product-layer note for the wallet-and-operations stack itself: 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 Travel Rule and transaction-risk screening. That product surface is still worth preserving, but the sharper operator boundary now lives in liminal, which is the better place to reason about who runs Vaults, authors whitelist and policy workflow, intermediates signer experience, and can become part of custody truth in practice.
  • 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
    • Documents an EVM multisig path where a Gnosis Safe-style contract is created in the background and Liminal Gas Station provides the concluding signature and gas fees for Vaults-mediated execution
    • Publishes a public status page and a large first-party docs corpus with operational, compliance, and API guidance
  • Key claims:
    • The live docs overview still describes Liminal as a software solution for web3 institutions, exchanges, and other VASPs and still groups the stack into Wallet-as-a-Service, Managed Custody, and a Whitelabel Solution
    • The key-features docs still say Vaults exposes hot API wallets, warm MPC wallets, and cold multisig wallets alongside organisation, role, team, and quorum workflow in the same first-party surface
    • Those same docs still frame Vaults as the web interface where organisations manage wallets, compliance, security, transactions, teams, and policies, which is why the product note should preserve the workflow stack rather than only custody branding
    • The wallets docs add watch-only wallets for balance and transaction monitoring without storing private keys, which helps keep the note focused on operational wallet topology rather than only key storage
    • The Gas Station guide says Liminal automatically refills wallets with native gas assets and supports Sprayer-style operational flows, which makes the product note useful for routine treasury and exchange-ops questions rather than only incident retrospectives
    • The Firewall docs say transactions are evaluated across Travel Rule, transaction-risk, and transfer policies, with outcomes of accept, reject, or additional approval; the docs also name Notabene and TRM Labs as integrated providers
    • The operate EVM multisig wallets outside Liminal Vaults docs still say an EVM multisig set up through Liminal creates a Gnosis multisig contract in the background, with Liminal as the concluding signer and Gas Station bearing gas fees, while also explaining how operators can later restore the same wallet directly in Safe outside Vaults
    • That operate outside Vaults path is analytically important because it keeps the substrate / middleware split visible: the onchain wallet can persist outside Liminal even when day-to-day transaction intent, policy, and execution flow were previously routed through Liminal’s product surfaces
  • Whitepaper: No canonical standalone Liminal whitepaper or litepaper surfaced in this pass. The clearest current source of truth remains the official docs corpus, the main site, and the public status surface; see ../whitepapers/liminal-primary-sources-2026-04-30.md.
  • Sources:

Internal linkages

Protocol / company boundary

  • Keep this project note on the product and workflow layer: wallet types, Vaults workflow, Gas Station automation, Firewall policy behavior, Travel Rule and risk-screening integrations, and the documented Safe-style multisig operating path.
  • Use liminal when the sharper question is who runs Vaults, controls the web/mobile approval surface, authors whitelist and policy workflow, intermediates signer review, or becomes part of the effective threshold for real custody operations.
  • That split matters because how does Liminal's wallet stack work? and which named operator can become part of custody authenticity in practice? are related but not identical questions.

Control surface

  • At the product layer, the leverage sits in wallet-type choice, organisation and team setup, quorum and approval design, whitelist and policy behavior, gas-refill and consolidation automation, Travel Rule and risk-screening integration, and how tightly an institution binds daily operations to Vaults-managed workflow.

  • The operate outside Vaults docs matter because they show that the onchain wallet and the Liminal workflow are separable objects: a Safe-style multisig can survive outside Liminal even when the day-to-day signing, display, whitelist, and execution path had been routed through Liminal first.

  • That is why the product note still belongs in projects/: the stack is broader than one incident. But the durable caution is that workflow middleware can quietly become part of custody truth, which is exactly why the separate liminal note exists.

  • Last reviewed: 2026-08-13 UTC

Graph View

Backlinks