DeepSafe
User Manual
Updates & Announcements
User Manual
Updates & Announcements
  1. Wallets & Transactions
  • 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. Wallets & Transactions

Key Shards

Overview#

DeepSafe uses MPC key technology to generate three key shards for a Team Wallet in distributed form. Signing is performed jointly by the threshold number of shards, and the complete private key is not constructed at any point.

How the three shards are distributed#

The local key shard is generated and stored on your mobile device and held by you alone.
The two cloud key shards are generated and stored encrypted on DeepSafe MPC Nodes, protected by SGX secure chips. Core signing operations run inside a hardware-isolated Trusted Execution Environment that the operating system layer cannot access.
This distribution determines the backup strategy: you back up the local shard yourself, while the two cloud shards are secured by designating backup holders.

Backing up the local shard#

The local shard is backed up through a recovery phrase. That phrase is the only way to recover your wallet — you need it when changing devices, if you forget your Wallet Password, or after reinstalling the app.
Before you begin, make sure your surroundings are secure: no surveillance cameras, no one else present, and no public network. Do not screenshot or photograph the phrase, and do not transmit it by email, messaging apps, or cloud notes.
If the recovery phrase is lost, DeepSafe cannot retrieve it for you. Store it offline, and consider making multiple copies kept separately.

Backing up the cloud shards#

Each of the two cloud shards can have its own backup holder — a business partner, a Team member, a family member, or another of your own devices. Once the backup holder signs in, the system guides them through the backup.
Assigning them separately is the point of this design. Anyone holding both cloud shards can use the DeepSafe offline recovery tool to reconstruct the complete private key. For that reason, the two cloud shards should not go to the same person, and neither should sit alongside your local shard. Once all three shards are in one place, distributing them serves no purpose.
Conversely, if you want more direct control over your assets, you can have two separate trusted parties hold the cloud shards. Guidance on this is sent to your registered email periodically.

Checking backup status#

The Key Shards screen lists the backup holder and backup status for each of the three shards. Any shard that has not been backed up is flagged.
An incomplete backup does not prevent day-to-day sending and receiving, but if your device is lost or damaged you may be unable to recover control of your assets. Complete your backups soon after creating a Team.

Recovery and changing devices#

After changing devices, you generate a new local shard on the new device, and the Team Creator verifies your security certificate. Once that is done, you can participate in signing again.
If a device is lost, contact the Team Creator through another channel as soon as possible, and check your account's sign-in status and security settings.
Even if you stop using DeepSafe, you can regain control of your assets through the platform's offline recovery method, without relying on DeepSafe services.

Things to note#

DeepSafe staff will never ask you for your recovery phrase or key shards under any circumstances. Any request framed as identity verification, recovery assistance, or a system upgrade is fraudulent.
Once you designate a backup holder, confirm that they understand the responsibility. A backup holder who does not complete the backup is the same as no backup at all.
Modified at 2026-08-26 02:51:05
Previous
Wallets & Assets
Next
Sending Assets
Built with