Export Key
Last updated
Last updated
POST /keys/{keyId}/export
Dfns secures private keys by generating them as MPC key shares in our decentralized key management network. Our goal is to eliminate all single points of failure (SPOFs) associated with blockchain private keys.
In certain circumstances, however, customers require Dfns to export a private key. In this case, Dfns exposes the following endpoint which can be used in conjunction with our .
Dfns can not guarantee the security of exported keys as we have no way to control blockchain transactions once the single point of failure has been reconstituted. For this reason, this feature is restricted to customers who have signed a contractual addendum limiting our liability for exported keys. Additionally, by default exported keys can no longer be used to sign within the Dfns platform. Please contact your sales representative for more information.
Keys:Export
Always Required
The private key which you need to export, will never be transmitted through Dfns system in one piece, or in clear (un-encrypted). The process follows this flow:
On your side (client-side), with the help of our , you create an "export context" locally. This will generate an encryption/decryption key pair to perform the export in a secure way. This step corresponds to in our SDK key export example.
You then call the Key Export endpoint, providing the API with the previous encryption key for secure export. This step corresponds to in our SDK key export example.
On Dfns side, the export encryption key gets transmitted to each node of your Signing Cluster (Your Signing Cluster is the network of nodes, also referred as "signers", where your private key shares are securely stored). Each signer node will encrypt the corresponding key share to be exported. All encrypted key shares are then transmitted back to you.
On your side (client-side), with the help of our , you will then decrypt each encrypted key share, and re-compose the key shares into a single private key. This step corresponds to in our SDK key export example.
encryptionKey
The public key of an asymmetric key pair used to encrypt the key shares prior to transmission.
String
supportedSchemes
An object with the format shown below.
Array<SupportedScheme>
delete
Whether the key should be deleted after export. Defaults to true
when not specified.
Boolean (optional)
protocol
CGGMP21
, FROST
, FROST_BITCOIN
String
curve
secp256k1
, edd25519
, stark
String
publicKey
Public key of the exported key.
String
protocol
CGGMP21
, FROST
, FROST_BITCOIN
String
curve
secp256k1
, edd25519
, stark
String
minSigners
Always 3
. Mininum number of signers to complete a signature (TSS threshold).
Integer
encryptedKeyShares
An array of objects containing the encrypted keyshares. See format below.
Array<EncryptedKeyShare>
signerId
ID of the signer returned from List Signers.
String
encryptedKeyShare
The key share encrypted with the signer encryption key (public key, asymmetric encryption).
String