Account Recovery Process
Salt has provided an open-source process, the Salt Recovery Tool, that lets organisation owners recover access to their Salt-managed digital assets if Salt's hosted services become unavailable. It has been designed to be usable by operators without deep technical expertise, while remaining completely independent of Salt's infrastructure.
The recovery process:
- operates entirely self-contained once the required information has been provided
- does not communicate with the Salt backend
- uses only publicly available blockchain data plus cryptographic material you supply
- can be independently verified because it is open source
The recovery process is a disaster-recovery mechanism. Its purpose is to recover assets from Salt-managed accounts so they can be transferred elsewhere. It's not for managing Salt Accounts day-to-day.
Recovery flows
There are two independent recovery methods available.
Flow 1: Owner EOA + Robo Guardian wallet-seed backup
Requires:
- the owner's EOA private key
- the encrypted Robo Guardian wallet-seed backup
The encrypted Robo Guardian wallet-seed backup is available from each organisation's Salt profile. Because the recovery process operates independently of Salt, organisations may also wish to store a copy of the encrypted Robo Guardian wallet-seed backup outside of Salt as part of their disaster-recovery procedures.
The owner imports both pieces into the tool, which then recovers the required cryptographic material.
Flow 2: All user EOAs
This recovery pathway will need to be done for each account in a Salt Organisation. It does not require the Robo Guardian wallet-seed backup.
Instead, gather the private keys for all of the account's proposers except the Robo Guardians.
The tool uses those keys together with the on-chain backup data to recover an account. This is an alternative path if the encrypted Robo Guardian wallet-seed backup is unavailable.
Recovery process
Once the required material is imported, the recovery process:
- reads the encrypted backup stored on-chain
- decrypts the required recovery material
- identifies the recoverable Salt accounts
- displays those accounts to the operator
From there, the operator can export the private keys. The process reconstructs the private key for each recovered account. These can be imported into another compatible wallet (e.g. MetaMask) and managed like any standard blockchain account.
Disaster-recovery considerations
The supplied tooling, the Salt Recovery Tool, comes with warnings and guidance tips where appropriate. Please read them carefully.
Independence from Salt
A core design goal is complete independence from Salt's hosted infrastructure. The recovery process:
- does not require access to the Salt backend
- does not rely on Salt-operated services
- uses only publicly available blockchain data
- uses cryptographic material supplied by the operator
- can be audited and verified because it is open source
This ensures organisations retain the ability to recover and move their assets even if Salt is permanently unavailable.
See also
- Keyshard backup and recovery: how the encrypted, Salt-independent keyshard backups are created.