Before you go live

What to set up, back up, and test before a vault holds real assets

Complete this checklist before any vault holds real assets. Some of these steps can't be done later: a Virtual Signer's recovery key is fixed when it first starts, and a backup you didn't take can't be recovered.

❗️

If your organisation loses access to enough signers to meet a vault's threshold, the only way to reach its assets is the disaster recovery process. It works only if your backups are current and you can find their keys.

Must do

  1. Design the vault's signers and threshold.

    • Make sure the signers you can always reach have enough combined signing power to meet the threshold, even with one or two of them unavailable.
    • Give a single signer enough power to sign alone only if you intend it.

    See Vaults, signers, and thresholds.

  2. Generate each Virtual Signer's recovery key pair before it first starts. The Virtual Signer won't start without the public key, and you can't change the key afterwards. Store the private key offline. See Virtual Signer disaster recovery.

  3. Check each Virtual Signer has the right recovery key. Compare the checksum of the deployed public key with your own copy before the signer joins a vault.

  4. Back up every signer after the vault is created. See Back up your signers.

  5. Run a disaster recovery drill. On a test vault, back up the signers, then recover the vault's keys on an air-gapped computer with the disaster recovery tool. Include every type of signer the vault uses.

  6. Keep your own copy of the disaster recovery tool, version 6.5.0 or later, so you can recover without depending on io.finnet.

  7. Record who holds what. For each vault, record who holds each backup file and each key, where they are stored, and how to retrieve them during an incident. Choose the person who will run a recovery: they will see the vault's private keys.

  8. Test with a small amount first. Send a small transaction on each network you will use, and confirm it arrives.

If you run Virtual Signers, also test the deployment. If you run the io.sign backend yourself, also check its authentication, database backups, and licence.

Back up your signers

Each signer has its own backup, and each backup needs a separate key to read it. You need both to recover a vault.

Mobile SignerVirtual Signer
BackupAn encrypted backup file, exported from the app.A recovery bundle, exported with signerctl share backup.
KeyThe 24-word secret phrase the app shows when you export that backup.Your organisation's ML-KEM-768 private key.
Store the backupOff the device, somewhere your organisation permits.Off the signer's host.
Store the keyOffline, separately from the backup and the device.Offline, with more than one copy, never on the signer's host.
Update itAfter the signer joins a vault, and after every reshare.After the signer joins a vault, after every reshare, and on a regular schedule.

A backup taken before the latest reshare may not hold the current shares, and may not recover the vault. Take a new backup after every reshare.

Backing up a Virtual Signer's storage volume keeps that signer running after a host failure. It doesn't replace the recovery bundle, which is what recovers the vault.

Never

  • Never store a secret phrase or private key with its backup, or on the signer's device or host.
  • Never let a vault hold real assets before you have tested recovering it.
  • Never use the Virtual Signer's always-approve mode, or simulated cryptography, for a vault that holds real assets.
  • Never run two copies of the same Virtual Signer, for example by copying its storage volume.
  • Never delete a Virtual Signer's storage to get past a configuration error.

Next steps


Did this page help you?