Skip to navigation

MPC Wallet

View as Markdown

bitMPC Wallet is a digital asset wallet for individuals, teams and businesses. Individuals can manage their assets and use devices to sign transactions. Families and teams can share responsibility for a wallet. Businesses can manage deposits, fund movements and withdrawals with permissions, approval rules and transaction records.

MPC Wallet is in development ahead of its public launch. The product capabilities described here reflect the current implementation. Available plans, networks and operating rules will be confirmed when access opens.

Who it is for

WalletWhat you can use it for
Personal walletView assets and receiving details in one workspace, manage participating devices and check transfer progress.
Family or team walletManage shared assets in a common workspace, assign responsibilities and have the designated participants sign transactions.
Enterprise wallet with customer-operated nodesOperate signing nodes, manage receiving addresses, organize funds across wallet roles and review outgoing transfers with your team.
Fully managed enterprise walletLet the platform operate signing infrastructure while your team handles balances, payment requests, approval tasks and reconciliation.

The available screens and actions depend on the wallet product and member permissions. Personal and team wallets show device signing progress. Enterprise workspaces also provide a task list for members whose roles permit them to review withdrawals.

What MPC changes

Multi-party computation (MPC) allows participating devices or nodes to sign a transaction together. Each participant uses its own portion of the signing key. During normal signing the participants can produce a valid signature without bringing the whole private key together. The signing threshold determines how many participants from the wallet’s configuration are needed.

In an enterprise payment, a finance operator can submit the request and authorized reviewers can approve it under the workspace policy. The signing participants then produce the blockchain signature. Business approval and signing have separate responsibilities, and chain confirmation establishes the transaction outcome.

Choose how to hold signing keys

  • Fully managed. The platform operates the signing infrastructure. The business manages its people and payment workflow through the workspace.
  • Joint custody. The customer and platform each hold part of the signing material. Review who must participate and who handles backups for the chosen wallet.
  • Self-custody. The customer holds the wallet’s portions of the signing key and prepares the devices, backups and recovery process needed for continued access.

Custody choices vary by wallet product. Check the participant configuration and recovery responsibilities for your wallet before completing setup. See custody models.

What you can do with the wallet

  • Receive assets and track deposits. Obtain receiving details for the selected network. For enterprise address allocation, associate the address with a business user identifier. Keep any required memo with the address and track the deposit after sending those details to the payer.
  • Organize enterprise funds. Use wallets with different roles for receiving deposits, day-to-day payouts, internal movements and reserves. Collection brings funds from receiving addresses into the designated wallet under the applicable policy.
  • Review and follow outgoing transfers. Check the network, asset, amount, destination and fees before submission. With the relevant permission, reviewers can use the enterprise task list to handle approval. The transfer record shows subsequent progress through signing, broadcast and chain confirmation.
  • Manage risk and reconcile records. Enterprise workspaces provide address lists, approval rules and audit logs according to role. Balance, deposit, withdrawal and chain records help finance teams match wallet activity to their own records.
  • Manage signing devices and prepare recovery. Where you operate participants, use the device or node views to manage them. Record who can participate and confirm that the onboarding plan covers backup and recovery for the selected custody arrangement.

Example: an enterprise payment

A finance team wants to collect balances received from customers and pay a supplier. It checks the deposit records against its business records and uses its wallet arrangement to make funds available for payment. An operator submits a transfer to the supplier’s address. Where approval is required, the reviewer checks the destination, asset and amount before approving the request. After the signing participants produce a signature, the team follows the transfer to chain confirmation and uses the transaction record to close its reconciliation.

If the broadcast result is still being verified, the team checks the original record until the outcome is known. This keeps the supplier payment tied to one business request.

Explore the guides