Getting Started

Register in the app with a username and email address. The username cannot be changed after registration, so choose carefully.

The app is DeepSafe's security root — key shards are generated and held there. The Web Console requires a QR code scan from the app to sign in; account credentials alone will not work.

2. Bind Google Authenticator

After registration, you are prompted to bind Google Authenticator for two-factor protection at sign-in.

Binding requires an authenticator app on your device. Scan the QR code shown or enter the key manually. Back up that key and store it safely — if your device is lost, it is what lets you restore your verification capability.

You can skip this step and set it up later in Security Center under "Me." Your account protection is weaker until you do, so we recommend completing it early.

See Account & Security Settings.

3. Create a Team

A Team is the basic unit for using DeepSafe. Assets belong to the Team, not to an individual.

If this is your first time, choose to create a Team and enter a name. If a colleague has already created a Team and invited you, choose to join an existing Team instead.

See Teams & Members.

4. Initialize the MPC Team Wallet

After you submit, initialization begins and takes roughly three minutes. It generates the local key shard, configures the MPC Node, verifies the cloud Trusted Execution Environment, generates and verifies key shards for two signature algorithms, and finally initializes the Team Wallet.

Keep the app in the foreground until it finishes.

Once complete, your Team has a default Team Wallet and can begin receiving and sending assets.

5. Back up your key shard

After initialization, you are prompted to back up your recovery phrase.

The recovery 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. DeepSafe cannot retrieve it for you — custody is decentralized, and a lost phrase cannot be recovered.

Complete the backup where there is no surveillance and no one else present. Do not screenshot or photograph it, and do not transmit it over a network.

This step can also be skipped, though we do not recommend it. If you skip it, complete the backup soon under Key Shards in the Workbench, and designate backup holders for the two cloud shards at the same time.

See Key Shards.

6. Get familiar with the wallet home

The home screen shows total Team assets, separating visible and hidden wallets. Below it is the Team Wallet list, with entry points for Receive, Send, and Transaction Records.

Wallet details list assets by token. Testnet assets carry a Testnet label; they have no real value and cannot be exchanged for mainnet assets.

See Wallets & Assets.

7. Receive your first assets

Open Receive, select the token and then the network, and share the generated address with the sender.

Confirm that the sender's network matches the network of that address. Assets sent on the wrong network usually cannot be recovered.

Arrival requires on-chain confirmation and can be tracked in Transaction Records.

See Receiving Assets.

8. Complete your first transfer

Open Send, choose the token, enter the destination address and amount, review the details, and submit. Submitting requires identity verification.

Before submitting, check the token and network, the source and destination addresses, the amount, and the network fee. An on-chain transaction cannot be reversed once broadcast.

If your Team has configured transfer policies, the transaction is validated against them first. If it matches a policy that requires approval, it enters the approval flow and is handled by the designated approvers in the app. Once approved, members with the approve-transactions permission complete signing, and only then is the transaction broadcast.

See Sending Assets.

9. Track the transaction

Open Transaction Records to view status and details. Details show the policy that was matched, approval and signing progress, and the transaction hash once it is on-chain.

See Transaction Records.

Recommended next steps

Once your first transfer goes through, we recommend setting up the following, in this order:

Invite members and assign permissions. Decide who can initiate transactions and who approves them. Note that inviting an Admin moves your Team into multi-admin governance, which cannot be reverted to sole decision-making by the Team Creator.

Configure transfer policies. The Policy Engine denies by default — any transaction not covered by a policy is blocked. Make sure your policies cover your Team's routine transaction scenarios.

Build your whitelist. Add frequently used destination addresses, and decide whether to enable transfer restrictions.

Designate cloud shard backup holders. Assign the two cloud shards separately. Do not give both to the same person, and do not store them alongside your local shard.

Enable App Lock and Biometric Payment in Security Center.

1. Register and sign in#

2. Bind Google Authenticator#

3. Create a Team#

4. Initialize the MPC Team Wallet#

5. Back up your key shard#

6. Get familiar with the wallet home#

7. Receive your first assets#

8. Complete your first transfer#

9. Track the transaction#

Recommended next steps#

1. Register and sign in