Dfns supports importing existing private keys into its MPC infrastructure. This allows you to migrate wallets from other providers while gaining Dfns security features.
Imported keys are inherently less secure than keys generated by Dfns MPC. The private key existed in its complete form before import, which means someone else may have had access to it. This feature is restricted to Enterprise customers. Contact your sales representative for more information.
How import works
Dfns uses MPC (Multi-Party Computation) to secure keys. When you import a key, it gets split into encrypted shares distributed across Dfns signer nodes. The original private key is never stored as a whole.
The import process requires:
- The Dfns import SDK to encrypt and split your key
- Calling the Import Key API with the encrypted key shares
See the SDK examples for implementation details.
After importing a key
Once you’ve imported a key, you can:
- Create wallets from it: Use Create Wallet with
signingKey.id to create wallets on specific networks
- Sign directly: Use the Signing API for raw signatures
- Multi-chain usage: The same key can be used across compatible networks (e.g., all EVM chains share the same address)
When to import vs create new
Import makes sense when:
- Migrating from another custody provider
- The wallet address is tied to a smart contract you can’t redeploy
- You have regulatory requirements to maintain specific addresses
Create new keys instead when:
- Starting fresh with no legacy requirements
- High-value production wallets
- You can move assets from old wallets
