Skip to main content

Migrate wallets into Utila

How to mirror your wallet environment into Utila

Overview

Operational resilience is no longer optional. Frameworks like the EU's DORA and the UK's operational resilience rules from the PRA and FCA have made provider concentration risk a first-order concern for any institution holding digital assets. Utila's wallet mirroring lets you eliminate single-vendor dependency by recreating your existing wallet environment inside Utila, so operations continue uninterrupted even if your current provider goes down.

Mirroring recreates your wallets inside Utila from the same underlying cryptographic material, so every address is reproduced exactly. This ensures that critical operations continue without interruption, regardless of vendor availability, while offering a clear path to consolidate operations onto Utila over time.

How mirroring works

Wallet mirroring is achieved by securely importing the cryptographic material that underpins each wallet address. This material, in the form of ECDSA or EdDSA keys, is used to reconstruct wallets according to a predefined derivation path.

Regardless of the method you choose, the result is an identical mirrored wallet environment that allows for seamless failover.

When mirroring from a vendor that uses HD (hierarchical deterministic) wallets, the individual wallets are recreated after the key material import is complete, either manually or by uploading the HD addresses in bulk.

Two ways to import wallets into Utila

1. Import Fireblocks recovery package

Mirror your existing Fireblocks workspace into Utila. You can do this in one of two ways:

  • Station70 SWAT integration
    Mirror your Fireblocks workspace using the Station70 integration. See Migrate your Fireblocks workspace into Utila using Station70 integration.

  • [Coming soon]: Upload the Fireblocks recovery package directly:
    Load your encrypted Fireblocks recovery package into Utila, then enter your recovery passphrase in the Utila mobile app to decrypt your key shares locally

2. Import direct key material using the Utila CLI

Import the raw private key material on a secure, air-gapped machine using the Utila CLI tool. The CLI splits the key into shares and encodes them into a QR code, which you scan into the Utila mobile app.

Because this method handles full private keys, it is more operationally complex, and the air-gapped machine must be wiped once the process is complete. Two variants are supported:

Did this answer your question?