Eject a wallet

The eject feature allows a user to construct a private key that can be imported into another wallet manager, such as MetaMask.

Warning: Providing the custodian backup share to the client device puts both MPC shares on a single device, removing the multi-party security benefits of MPC. This operation should only be done for users who want to move off of MPC and into a single private key. Use portal.eject() at your own risk!

Ejecting Your User's Wallets

With Portal-managed backups

To eject the private keys for your users' wallets, their two matching backup shares need to be combined. Since both of these shares are stored on the Portal backend encrypted at rest, we first need to verify that the upcoming request to eject the wallet is not an attack. In order to do this, we make this a two-step process:

1. Make a Custodian-authed POST request using your Custodian API Key (the same API key you use to create new users) to the /api/v3/custodians/me/clients/${clientId}/prepare-eject endpoint to allow for this client to perform an eject operation

2. Call the portal.ejectWallet() function from your application

Making the `prepare-eject` request

This endpoint requires a walletId in the POST body. This can be found in the wallets property of the /api/custodians/me/clients/${clientId} GET request.

If you are planning on ejecting multiple wallets for a user, you'll need to make multiple separate requests to "unlock" all requires wallets.

const response = await axios
      .post<string>(
        `https://api.portalhq.io/api/v3/custodians/me/clients/${clientId}/prepare-eject`,
        { walletId: 'YOUR_CLIENTS_WALLET_ID' },
        {
          headers: headers,
        },
      )

Ejecting the wallets

// Provide the appropriate backup method for your client's wallet
let privateKey = try await portal.eject(.Password)

This function will perform the combining of shares from our server and the cryptographic operation required to build a private key for the wallet. The return value is the string literal of the private key.

With Backups from your server

To eject the private keys for your users' wallets, their two matching backup shares need to be combined. This requires providing the following two shares to portal.eject():

• User Backup Share - Encrypted backup share received from portal.backup().

• Custodian Backup Share - Raw backup share received from the POST /backup webhook.

Here's an example implementation:

Ejecting with customer managed backups

// Fetch the encrypted user backup share from your API.
let encryptedUserBackupShare = try await yourAPI.fetchEncryptedUserBackupShare(
    userId,
    withBackupMethodWithCurve: .Password
)

// Fetch the user's custodian backup share from your API.
let custodianBackupShare = try await yourAPI.fetchCustodianBackupShare(
    userId,
    withBackupMethodWithCurve: .PasswordSECP256k1
)

// Fetch the user's custodian backup share from your API.
let custodianBackupSolanaShare = try await yourAPI.fetchCustodianSolanaBackupShare(
    userId,
    withBackupMethod: .PasswordED25519
)

   let privateKeys = try await portal.ejectPrivateKeys(
      .Password,,
      withCipherText: cipherText,
      andOrganizationBackupShare: custodianBackupShare,
      andOrganizationSolanaBackupShare: custodianBackupSolanaShare
    )
return privateKeys

SECP256K1 is the curve used by Ethereum and ED25519 is the curve used by solana.

You can learn more about signing algorithms and curves here.

And that's it!