Recover a wallet
This guide will walk you through the recovery process in the event that the user needs to recover their wallet.
This product is currently in Beta and is under active development.
MPC recovery allows your users to recover their MPC wallets in the event that their device is lost, stolen, or bricked.
MPC recovery uses the MPC backup that a user has already configured to create a new set of signing shares.
Recovery is handled in two pieces: user recovery and custodian recovery.
Recovery creates two new pairs, one for signing and one for backup, and deprecates the two old pairs.
User Recovery
Recovering a user's MPC share is done by retrieving the encryption key from the user's cloud storage provider and decrypting the encrypted share within your infrastructure.
In order to support user MPC recovery, four dependencies must be met:
Your server must send the encrypted share to the user's device
Your app must initiate the recovery process
Your app must send the new encrypted backup share to your server
Sharing encrypted shares with the client
During the recovery process, the encrypted client backup share needs to be retrieved from the custodian backend.
Create an endpoint to get the encrypted share, so the client can decrypt the value using the encryption key stored in the user's cloud storage provider.
Updating Your App
In order to initiate the recovery process from your app, you must perform three steps:
Retrieve the encrypted client backup share from your API.
Get a new encrypted client backup share from running
portal.mpc.recover
.Send the new backup share to your API and store it.
WARNING: To recover a wallet with the Portal SDK, your device must be configured to use passcode authentication. Please note that if you disable your passcode authentication after executing the recover
function, you will need to run the recover
function again to continue using your Portal wallet.
Custodian Recover
In order to support custodian MPC recovery, one dependencies must be met:
Your server must support the /{webhook_root}/backup/fetch webhook to provide Portal your existing custodian backup share
Implementing the webhook
Portal will request the existing custodian backup share with a POST
request to /{webhook_root}/backup/fetch
.
The request body of this POST
request will contain one field:
clientId
- The PortalclientId
of the user
Last updated
Was this helpful?