You’re viewing Porto documentation — a distinct product from Anchorage Digital’s core custody platform. Go to Anchorage Digital docs →
For the full recovery model — wallet recovery shares, the organization recovery document, and decrypting wallet keys — see Key management & recovery. This page focuses specifically on how encrypted wallet backups work.
How encrypted backups work
- Automatic — An encrypted backup is generated the moment you create a wallet. You don’t need to trigger anything manually.
- Not sensitive on their own — The encrypted backup file itself is not sensitive material. It’s useless without the credentials needed to decrypt it.
- Accessible any time — You can access your encrypted wallet backups at any time from the web dashboard.
What’s required to decrypt a backup
To decrypt an encrypted wallet backup and access the underlying private key, you need:- 2 out of 3 wallet recovery shares, and
- A device enrolled in Porto, or the organization recovery document
Why this design
This is what lets you achieve true self-custody: Anchorage Digital never holds the credentials needed to decrypt your backups on its own. Decryption always requires wallet recovery shares that are distributed to your own team members, combined with either an enrolled device or your organization’s recovery document — both of which are also unique to your organization.Related pages
- Key management & recovery — wallet recovery shares, decrypting wallet keys, and the full recovery flow
- Organization recovery document — using the organization recovery document
- Wallet recovery — account and device recovery