Overview
With the emergence of DORA and other industry standards, institutions are placing increased emphasis on business continuity and operational resilience. Utila addresses this need by enabling organizations to rapidly mirror their existing wallet environments, ensuring seamless continuity in the event of provider downtime or disruption. This gives teams the confidence that critical operations can continue without interruption - regardless of vendor availability.
For now, mirroring Fireblocks wallets is supported.
How you can achieve wallet mirroring
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.
Utila supports two methods for importing these keys:
Fireblocks recovery package: The encrypted recovery package is loaded into the Utila backend, and the encrypted client key shares are transferred to the Utila mobile app. There, they are decrypted locally using a passphrase provided by the user, thus ensuring that Utila never has access to the unencrypted key shares.
Direct key import into the mobile app: The full private key is imported directly into the Utila mobile app, which then splits it into two shares—one retained on the device and the other securely uploaded to the Utila backend. This method requires using a secure, air-gapped machine to handle the full key (which should be wiped once the process is complete), making it more operationally complex and inherently less secure.
Both methods result in an identical mirrored wallet environment, allowing for seamless failover in the event of disruption or downtime from the primary wallet provider.