DeepSafe
User Manual
Updates & Announcements
User Manual
Updates & Announcements
  1. User Manual
  • About DeepSafe
  • Quick Start
    • Core Concepts
    • Account Security Principles
    • Getting Started
  • Using DeepSafe
    • Accounts & Teams
      • Teams & Members
      • Decision Mode
      • Roles & Permissions
      • Account & Security Settings
    • Wallets & Transactions
      • Wallets & Assets
      • Key Shards
      • Sending Assets
      • Receiving Assets
      • Transaction Records
      • Gas Service
    • Security
      • Approval Workbench
      • Address Whitelist
      • Approval Nodes
      • Policy Engine
      • Audit Log
    • Developer
      • API Key Management
  1. User Manual

About DeepSafe

DeepSafe is a self-custody digital asset management platform built for institutional clients. Your organization holds its own keys, manages wallet assets, configures internal approval and risk-control rules, and integrates wallet capabilities into its own systems as needed.
The platform serves trading platforms, asset managers, payment institutions, token issuers, OTC and proprietary trading desks, and any organization that manages assets on-chain.

What the platform includes#

MPC Wallet — self-custodied multi-chain wallets for receiving, sending, and managing assets.
Policy Engine — the core of transaction risk control. Configure rules based on initiator, address, token, amount, and frequency; matched transactions are routed to approval or blocked.
Treasury Management — asset consolidation and a consolidated view across multiple wallets and chains.
Wallet-as-a-Service (WaaS) — wallet capabilities exposed through APIs for integration into your own systems.

Two lines of defense#

Keys are never reassembled. DeepSafe manages keys using MPC threshold signatures (MPC-TSS). The private key is stored as shards across nodes, and signing never reassembles it — the complete private key is not constructed at any point. Core signing operations run inside a hardware-isolated Trusted Execution Environment (TEE) that the operating system layer cannot access.
Every transaction passes policy first. Before a transaction enters the signing stage, it must pass validation against the policies your Team has configured. Transactions that fail validation do not proceed to signing.
If your organization stops using DeepSafe, you can still regain control of your assets through the platform's offline recovery method, without relying on DeepSafe services.

Clients#

The mobile app is the security root. Key shards are generated and held on the app, and transaction signing and final approval confirmations all happen there.
The Web Console is designed for day-to-day operations and management, with an interface better suited to bulk actions and reviewing information. Signing in requires scanning a QR code with the app.
The API serves business systems that have integrated with DeepSafe.
The two clients do not have identical capabilities, and some operations require both. See Core Concepts for details.

Where to start#

New to DeepSafe — read Core Concepts first to understand MPC Team Wallets, roles and permissions, and how policies work. Then follow Getting Started to go from registration to your first transfer.
Focused on security — Account Security Principles covers account protection, key custody, transfer verification, and how to recognize common risks. We recommend it for everyone on your Team.
Day-to-day operations — the in-depth section is organized into four groups: Accounts & Teams, Wallets, Assets & Transactions, Security, and API Management.
Modified at 2026-08-26 02:51:05
Next
Core Concepts
Built with