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.
Last updated
Was this helpful?
The eject feature allows a user to construct a private key that can be imported into another wallet manager, such as MetaMask.
Last updated
Was this helpful?
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.
To eject the private keys for your wallets, the two matching backup shares need to be combined. This is done by fetching the backup shares and then inputing them into the eject function in the NPM package.
To eject the private keys for your wallet, the two matching backup shares need to be combined.
Client Backup Shares - The client backup shares that are encrypted and stored with Portal.
Custodian Backup Shares - The custodian backup shares that are encrypted and stored with Portal.
The general steps here are to:
Get the Portal client's details and derive their SECP256K1 and ED25519 wallets.
Retrieve the Portal client's client backup shares and custodian backup shares.
Eject the Portal client's wallets and get their private keys.
Below is an example of how you might do this using TypeScript.
To eject the private keys for your wallet, the two matching backup shares need to be combined.
Client Backup Shares - The client backup shares that you stored on your backend.
Custodian Backup Shares - The custodian backup shares that you stored on your backend.
And that's it!
You can learn more about signing algorithms and curves .
You can learn more about signing algorithms and curves .