Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions _compress_images_cache.yml
Original file line numberDiff line numberDiff line change
Expand Up@@ -655,3 +655,20 @@ assets/images/guide/getting-started/usage-life-cycle/dropoff@2x.png: dropoff@2x.
assets/images/guide/payments/send/bitcoin-payments@2x.jpg: bitcoin-payments@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-mobile@2x.jpg: bitcoin-payments-mobile@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-social.jpg: bitcoin-payments-social.jpg
assets/images/guide/private-key-management/backups/backups-mobile.jpg: backups-mobile.jpg
assets/images/guide/private-key-management/backups/backup-table.png: backup-table.png
assets/images/guide/private-key-management/backups/backups.jpg: backups.jpg
assets/images/guide/private-key-management/backups/page-backups.jpg: page-backups.jpg
assets/images/guide/private-key-management/backups/backups@2x.jpg: backups@2x.jpg
assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg: backups-mobile@2x.jpg
assets/images/guide/private-key-management/backups/backup-table@2x.png: backup-table@2x.png
assets/images/guide/private-key-management/backups/paperbackup@2x.jpg: paperbackup@2x.jpg
assets/images/guide/private-key-management/backups/metalbackup.jpg: metalbackup.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg: offline-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/metalbackup@2x.jpg: metalbackup@2x.jpg
assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg: cloud-backup@2x.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg: offline-discoveryprotection@2x.jpg
assets/images/guide/private-key-management/backups/paperbackup.jpg: paperbackup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg: multiple-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/cloud-backup.jpg: cloud-backup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg: multiple-discoveryprotection@2x.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
267 changes: 267 additions & 0 deletions guide/private-key-management/backups.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,267 @@
---
layout: guide
title: Bitcoin backups
description: A beginner's guide to Bitcoin backups.
nav_order: 4
parent: Private key management
permalink: /guide/private-key-management/backups/
main_classes: -no-top-padding
image: https://bitcoin.design/assets/images/guide/private-key-management/backups/page-backups.jpg
Comment thread
danielnordh marked this conversation as resolved.
---

<!--

Editor's notes

A guide meant to lower the barrier for first time users of self-custody wallets.

Illustration sources

//

-->

{% include picture.html
image = "/assets/images/guide/private-key-management/backups/backups.jpg"
retina = "/assets/images/guide/private-key-management/backups/backups@2x.jpg"
mobile = "/assets/images/guide/private-key-management/backups/backups-mobile.jpg"
mobileRetina = "/assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg"
alt-text = "Several devices exchanging data"
width = 1600
height = 700
layout = "full-width"
%}

# Bitcoin backups

The self-custody of Bitcoin is an important right, but also a financial responsibility that can scale from pocket money to life savings, and take practice getting used to.

This guide is a straightforward starting point for simple Bitcoin backups, aimed at users of Bitcoin products.

If you are a designer or developer, make sure you offer guidance to your users so they can secure their bitcoin with an appropriate backup.


## What are backups?

When we talk about backups, we mean saving the information needed to restore access to a wallet outside of the application that created the private keys. Often, this will just be the [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }}) of 12 or 24 words, but can also include other information like a *pass-phrase* and [derivation path]({{ '/guide/glossary/#derivation-path' | relative_url }}).
Comment thread
danielnordh marked this conversation as resolved.

The main risks that backups need to protect against are:

- Loss of wallet - you lost the device and application holding the private key
- Remote theft - your backup got discovered online by a bad actor
- Physical damage - your backup got destroyed
- Theft on discovery - your backup got discovered in person by a bad actor
- Catastrophic events - your backup location got destroyed
- Inheritance loss - next-of-kin were unable to access your wallet


## Backup levels, basic to advanced

A basic backup can be done in a few minutes, while more advanced setups can require more time and effort, like the purchase of dedicated material.

Let’s look at some real life examples of backup methods for single-key wallets and what they protect against.

<br>

{% include image.html
image = "/assets/images/guide/private-key-management/backups/backup-table.png"
retina = "/assets/images/guide/private-key-management/backups/backup-table@2x.png"
alt-text = "Table of backup levels"
width = 904
height = 625
layout = "full-width"
%}

{% include tip/recommendation.html %}

Level 0 and 1 are good when getting started, and require very little effort.

Level 2, 3 or 4 are recommended for storing larger amounts.

{% include tip/close.html %}

<br>

#### Level 0
## Encrypted cloud backup

By storing the recovery-phrase in an online location that is encrypted (not in plain text) and hard to access by anyone other than yourself, you are protected against *loss of wallet*. This is the absolute minimum you should do and only takes a few minutes.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/cloud-backup.jpg"
retina = "/assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg"
alt-text = "Encrypted cloud backup"
Comment thread
danielnordh marked this conversation as resolved.
width = 800
height = 420
%}

**Do**
- Use an encrypted password manager like 1Password, LastPass, iCloud Keychain
- Alternatively, use a wallet application with automatic cloud backup

**Don’t**
- Screenshot the recovery-phrase and save it in Google Photos, iCloud photos
- Write down the recovery-phrase in plain text on your device, Google Docs etc.

**Suitable for**
- For small amounts (less than a months salary)
- When you can't wait to set up a new wallet until you are at home

<br>

#### Level 1
## Single paper backup

By storing the recovery-phrase written down on paper in your own home you have protected against *loss of wallet* and *remote theft*.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/paperbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/paperbackup@2x.jpg"
alt-text = "24 word paper backup"
width = 800
height = 508
%}


**Do**
- Write the recovery-phrase with the words numbered, using permanent ink on card
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Scribble the recovery-phrase on a scrap of paper using a pencil
- Stick it on the fridge, or other visible locations

**Suitable**
- For small amounts (less than a months salary)
- When you are setting up a new wallet at home

<br>

#### Level 2
## Single metal backup

By storing the recovery-phrase on metal in your own home you have protected against *loss of wallet*, *remote theft* and *physical damage*.

The best metal backup solutions are resistant to most physical damage, including fire, acid and high pressure.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/metalbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/metalbackup@2x.jpg"
alt-text = "Metal backup"
width = 800
height = 440
%}


**Do**
- Order a dedicated metal backup product, recommendations can be found [here](https://jlopp.github.io/metal-bitcoin-storage-reviews/)
- Follow the instructions and make sure the phrase is indented, etched, engraved or set properly
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Skip ordering a dedicated product, invent your own metal backup solution

**Suitable for**
- Amounts above your monthly salary, but less than half your annual salary

<br>

#### Level 3
## Single backup with discovery protection
The previous offline backups have one flaw in common - if discovered by a bad actor, your funds can be stolen.

To protect against this *theft on discovery* risk, a *pass-phrase* can be added to the recovery-phrase. This pass-phrase is sometimes called an extra word, or the 13th/25th word.

While this level provides more protection, it also adds complexity to your backup setup. For most beginners storing small amounts it might not be worth the effort from the start and can be a later consideration should the funds grow.

Technically, all recovery-phrases have a pass-phrase. If it's not set by the user, an empty string (“”) will be used by default. This means that using the recovery-phrase with or without the user-defined pass-phrase will recover two DIFFERENT wallets.

If a bad actor discovers only the recovery-phrase, they will find an empty wallet. Alternatively, one can deliberately leave a small amount of bitcoin in this wallet as a honey-pot, and monitor it for any withdrawals to know if it has been discovered.

To provide protection against *theft on discovery*, the pass-phrase should be stored separate from the recovery-phrase.

Since adding a pass-phrase will generate a different wallet, it is best to add it when first creating the wallet, and before storing any bitcoin in its addresses.

It's worth noting that most hardware wallets support pass-phrases, while most software wallet applications do not.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg"
alt-text = "Offline backup with discovery protection"
width = 800
height = 420
%}


**Do**
- Use a secure pass-phrase, it is case sensitive and can include numbers and special characters
- Have redundant and secure backups of both the recovery-phrase and the pass-phrase, they are equally important for successful wallet recovery
- Understand you now have two distinct wallets, (one each from the recovery-phrase with or without the pass-phrase), this can be useful to fool a bad actor, or a risk if next-of-kin is unaware of the pass-phrase

**Don’t**
- Store the recovery-phrase and pass-phrase together
- Forget to document your setup for next-of-kin

**Suitable for**
- Large amounts
- Situations where the backup can be discovered by bad actors

**Alternative**

Set up a hardware wallet from the recovery and pass-phrase that uses a PIN to protect usage. The PIN now becomes the protection against theft on discovery and should be saved somewhere safe just like the pass-phrase.

<br>

#### Level 4
## Multiple backups with discovery protection
One remaining flaw with the single offline backup levels is that severe damage to the one location where they are stored, could lead to the backup not being usable. This could be a fire, flood, earthquake or similar, all more or less likely depending on where you live.

To protect against such a *catastrophic event* we can create multiple backups, and distribute them to other locations. This could be a second home, trusted family and friends or a safe deposit box.

As the risk of discovery increases with the multiplying backups, it's best to maintain the protection against theft on discovery with a pass-phrase, or hardware wallets with a PIN.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg"
alt-text = "Multiple offline backups with discovery protection"
width = 800
height = 420
%}

**Do**
- Make sure you have reduntant copies of all parts of the backup in several locations
- Document your setup well for next-of-kin now that complexity has increased

**Don’t**
- Forget to safely store the pass-phrases or PINs

**Suitable for**
- Large amounts
- In locations where catastrophic events are common, or likely to cause severe damage

<br>

---

## Inheritance instructions
For any backup setup, sufficient information and understandable instructions for recovering the wallet should be available to next-of-kin.

Even though it might feel uncomfortable (or unnecessary if you are young and single), it is never too early to document your wallets. If you don’t, there is a very high chance that next-of-kin will not be able to inherit your funds.

At a minimum, document each wallet with a given name (Bob’s Bitcoin wallet 1), how to recover it, when it was created and what application was used to create the wallet. Ideally this document has all the instructions required to recover the wallet, but not the information itself (*recovery-phrase*, *pass-phrase* etc.), as that might expose you to theft on discovery risks.

**Do**
- Make next-of-kin aware of the existence of any wallets
- Explain clearly how to recover the setup, and how to access the required information


**Don’t**
- Store any required information ONLY in locations that will not be accessible to next-of-kin (password managers, single user accounts etc.)


**Suitable for**
- Any amount
6 changes: 6 additions & 0 deletions guide/private-key-management/introduction.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -55,4 +55,10 @@ An introduction to some of the common private key management schemes for shared

---

### [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }})

A straightforward guide to safe manual backups.

---

Start at the top with [private key schemes]({{ '/guide/private-key-management/schemes/' | relative_url }}).
2 changes: 1 addition & 1 deletion guide/private-key-management/multi-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -87,4 +87,4 @@ Few tailor-made products exist for shared wallets, but any wallet application th

---

OK, let's have a look at some [case studies]({{ '/guide/case-studies/' | relative_url }}).
OK, to end this chapter let's have a look at how to do safe [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }}).
4 changes: 2 additions & 2 deletions guide/private-key-management/single-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -132,9 +132,9 @@ This scheme is suitable for users who are already familiar with bitcoin and proc
### How it works
The wallet application will generate a 12 or 24 word phrase (seed / [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }})) from which all the wallet’s [keys]({{ '/guide/glossary/#keys' | relative_url }}) can be derived. This means the user can have access to the wallet from any compatible wallet application with the phrase, even if they lose the device or software.

This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the op-sec burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase. You need to take resistance to physical theft, fire and other destructive events into account. To get the best security out of recovery phrases they should be kept on several dedicated [metal storage pieces](https://jlopp.github.io/metal-bitcoin-storage-reviews/) in secure places offline. A fair amount of effort and knowledge is required for this.
This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase.

A full guide to manual backup best practices for users is out of scope for this chapter but the [Do's and Dont's](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) of Bitcoin key management is a good starting point.
Safe backups can be made fairly simple, take a look at our [Bitcoin backups](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) guide as good starting point.

{% include fact/pros.html %}

Expand Down
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Bitcoin backups page - replaces #210 by danielnordh · Pull Request #305 · BitcoinDesign/Guide · GitHub
Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions _compress_images_cache.yml
Original file line numberDiff line numberDiff line change
Expand Up@@ -655,3 +655,20 @@ assets/images/guide/getting-started/usage-life-cycle/dropoff@2x.png: dropoff@2x.
assets/images/guide/payments/send/bitcoin-payments@2x.jpg: bitcoin-payments@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-mobile@2x.jpg: bitcoin-payments-mobile@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-social.jpg: bitcoin-payments-social.jpg
assets/images/guide/private-key-management/backups/backups-mobile.jpg: backups-mobile.jpg
assets/images/guide/private-key-management/backups/backup-table.png: backup-table.png
assets/images/guide/private-key-management/backups/backups.jpg: backups.jpg
assets/images/guide/private-key-management/backups/page-backups.jpg: page-backups.jpg
assets/images/guide/private-key-management/backups/backups@2x.jpg: backups@2x.jpg
assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg: backups-mobile@2x.jpg
assets/images/guide/private-key-management/backups/backup-table@2x.png: backup-table@2x.png
assets/images/guide/private-key-management/backups/paperbackup@2x.jpg: paperbackup@2x.jpg
assets/images/guide/private-key-management/backups/metalbackup.jpg: metalbackup.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg: offline-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/metalbackup@2x.jpg: metalbackup@2x.jpg
assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg: cloud-backup@2x.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg: offline-discoveryprotection@2x.jpg
assets/images/guide/private-key-management/backups/paperbackup.jpg: paperbackup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg: multiple-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/cloud-backup.jpg: cloud-backup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg: multiple-discoveryprotection@2x.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
267 changes: 267 additions & 0 deletions guide/private-key-management/backups.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,267 @@
---
layout: guide
title: Bitcoin backups
description: A beginner's guide to Bitcoin backups.
nav_order: 4
parent: Private key management
permalink: /guide/private-key-management/backups/
main_classes: -no-top-padding
image: https://bitcoin.design/assets/images/guide/private-key-management/backups/page-backups.jpg
Comment thread
danielnordh marked this conversation as resolved.
---

<!--

Editor's notes

A guide meant to lower the barrier for first time users of self-custody wallets.

Illustration sources

//

-->

{% include picture.html
image = "/assets/images/guide/private-key-management/backups/backups.jpg"
retina = "/assets/images/guide/private-key-management/backups/backups@2x.jpg"
mobile = "/assets/images/guide/private-key-management/backups/backups-mobile.jpg"
mobileRetina = "/assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg"
alt-text = "Several devices exchanging data"
width = 1600
height = 700
layout = "full-width"
%}

# Bitcoin backups

The self-custody of Bitcoin is an important right, but also a financial responsibility that can scale from pocket money to life savings, and take practice getting used to.

This guide is a straightforward starting point for simple Bitcoin backups, aimed at users of Bitcoin products.

If you are a designer or developer, make sure you offer guidance to your users so they can secure their bitcoin with an appropriate backup.


## What are backups?

When we talk about backups, we mean saving the information needed to restore access to a wallet outside of the application that created the private keys. Often, this will just be the [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }}) of 12 or 24 words, but can also include other information like a *pass-phrase* and [derivation path]({{ '/guide/glossary/#derivation-path' | relative_url }}).
Comment thread
danielnordh marked this conversation as resolved.

The main risks that backups need to protect against are:

- Loss of wallet - you lost the device and application holding the private key
- Remote theft - your backup got discovered online by a bad actor
- Physical damage - your backup got destroyed
- Theft on discovery - your backup got discovered in person by a bad actor
- Catastrophic events - your backup location got destroyed
- Inheritance loss - next-of-kin were unable to access your wallet


## Backup levels, basic to advanced

A basic backup can be done in a few minutes, while more advanced setups can require more time and effort, like the purchase of dedicated material.

Let’s look at some real life examples of backup methods for single-key wallets and what they protect against.

<br>

{% include image.html
image = "/assets/images/guide/private-key-management/backups/backup-table.png"
retina = "/assets/images/guide/private-key-management/backups/backup-table@2x.png"
alt-text = "Table of backup levels"
width = 904
height = 625
layout = "full-width"
%}

{% include tip/recommendation.html %}

Level 0 and 1 are good when getting started, and require very little effort.

Level 2, 3 or 4 are recommended for storing larger amounts.

{% include tip/close.html %}

<br>

#### Level 0
## Encrypted cloud backup

By storing the recovery-phrase in an online location that is encrypted (not in plain text) and hard to access by anyone other than yourself, you are protected against *loss of wallet*. This is the absolute minimum you should do and only takes a few minutes.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/cloud-backup.jpg"
retina = "/assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg"
alt-text = "Encrypted cloud backup"
Comment thread
danielnordh marked this conversation as resolved.
width = 800
height = 420
%}

**Do**
- Use an encrypted password manager like 1Password, LastPass, iCloud Keychain
- Alternatively, use a wallet application with automatic cloud backup

**Don’t**
- Screenshot the recovery-phrase and save it in Google Photos, iCloud photos
- Write down the recovery-phrase in plain text on your device, Google Docs etc.

**Suitable for**
- For small amounts (less than a months salary)
- When you can't wait to set up a new wallet until you are at home

<br>

#### Level 1
## Single paper backup

By storing the recovery-phrase written down on paper in your own home you have protected against *loss of wallet* and *remote theft*.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/paperbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/paperbackup@2x.jpg"
alt-text = "24 word paper backup"
width = 800
height = 508
%}


**Do**
- Write the recovery-phrase with the words numbered, using permanent ink on card
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Scribble the recovery-phrase on a scrap of paper using a pencil
- Stick it on the fridge, or other visible locations

**Suitable**
- For small amounts (less than a months salary)
- When you are setting up a new wallet at home

<br>

#### Level 2
## Single metal backup

By storing the recovery-phrase on metal in your own home you have protected against *loss of wallet*, *remote theft* and *physical damage*.

The best metal backup solutions are resistant to most physical damage, including fire, acid and high pressure.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/metalbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/metalbackup@2x.jpg"
alt-text = "Metal backup"
width = 800
height = 440
%}


**Do**
- Order a dedicated metal backup product, recommendations can be found [here](https://jlopp.github.io/metal-bitcoin-storage-reviews/)
- Follow the instructions and make sure the phrase is indented, etched, engraved or set properly
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Skip ordering a dedicated product, invent your own metal backup solution

**Suitable for**
- Amounts above your monthly salary, but less than half your annual salary

<br>

#### Level 3
## Single backup with discovery protection
The previous offline backups have one flaw in common - if discovered by a bad actor, your funds can be stolen.

To protect against this *theft on discovery* risk, a *pass-phrase* can be added to the recovery-phrase. This pass-phrase is sometimes called an extra word, or the 13th/25th word.

While this level provides more protection, it also adds complexity to your backup setup. For most beginners storing small amounts it might not be worth the effort from the start and can be a later consideration should the funds grow.

Technically, all recovery-phrases have a pass-phrase. If it's not set by the user, an empty string (“”) will be used by default. This means that using the recovery-phrase with or without the user-defined pass-phrase will recover two DIFFERENT wallets.

If a bad actor discovers only the recovery-phrase, they will find an empty wallet. Alternatively, one can deliberately leave a small amount of bitcoin in this wallet as a honey-pot, and monitor it for any withdrawals to know if it has been discovered.

To provide protection against *theft on discovery*, the pass-phrase should be stored separate from the recovery-phrase.

Since adding a pass-phrase will generate a different wallet, it is best to add it when first creating the wallet, and before storing any bitcoin in its addresses.

It's worth noting that most hardware wallets support pass-phrases, while most software wallet applications do not.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg"
alt-text = "Offline backup with discovery protection"
width = 800
height = 420
%}


**Do**
- Use a secure pass-phrase, it is case sensitive and can include numbers and special characters
- Have redundant and secure backups of both the recovery-phrase and the pass-phrase, they are equally important for successful wallet recovery
- Understand you now have two distinct wallets, (one each from the recovery-phrase with or without the pass-phrase), this can be useful to fool a bad actor, or a risk if next-of-kin is unaware of the pass-phrase

**Don’t**
- Store the recovery-phrase and pass-phrase together
- Forget to document your setup for next-of-kin

**Suitable for**
- Large amounts
- Situations where the backup can be discovered by bad actors

**Alternative**

Set up a hardware wallet from the recovery and pass-phrase that uses a PIN to protect usage. The PIN now becomes the protection against theft on discovery and should be saved somewhere safe just like the pass-phrase.

<br>

#### Level 4
## Multiple backups with discovery protection
One remaining flaw with the single offline backup levels is that severe damage to the one location where they are stored, could lead to the backup not being usable. This could be a fire, flood, earthquake or similar, all more or less likely depending on where you live.

To protect against such a *catastrophic event* we can create multiple backups, and distribute them to other locations. This could be a second home, trusted family and friends or a safe deposit box.

As the risk of discovery increases with the multiplying backups, it's best to maintain the protection against theft on discovery with a pass-phrase, or hardware wallets with a PIN.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg"
alt-text = "Multiple offline backups with discovery protection"
width = 800
height = 420
%}

**Do**
- Make sure you have reduntant copies of all parts of the backup in several locations
- Document your setup well for next-of-kin now that complexity has increased

**Don’t**
- Forget to safely store the pass-phrases or PINs

**Suitable for**
- Large amounts
- In locations where catastrophic events are common, or likely to cause severe damage

<br>

---

## Inheritance instructions
For any backup setup, sufficient information and understandable instructions for recovering the wallet should be available to next-of-kin.

Even though it might feel uncomfortable (or unnecessary if you are young and single), it is never too early to document your wallets. If you don’t, there is a very high chance that next-of-kin will not be able to inherit your funds.

At a minimum, document each wallet with a given name (Bob’s Bitcoin wallet 1), how to recover it, when it was created and what application was used to create the wallet. Ideally this document has all the instructions required to recover the wallet, but not the information itself (*recovery-phrase*, *pass-phrase* etc.), as that might expose you to theft on discovery risks.

**Do**
- Make next-of-kin aware of the existence of any wallets
- Explain clearly how to recover the setup, and how to access the required information


**Don’t**
- Store any required information ONLY in locations that will not be accessible to next-of-kin (password managers, single user accounts etc.)


**Suitable for**
- Any amount
6 changes: 6 additions & 0 deletions guide/private-key-management/introduction.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -55,4 +55,10 @@ An introduction to some of the common private key management schemes for shared

---

### [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }})

A straightforward guide to safe manual backups.

---

Start at the top with [private key schemes]({{ '/guide/private-key-management/schemes/' | relative_url }}).
2 changes: 1 addition & 1 deletion guide/private-key-management/multi-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -87,4 +87,4 @@ Few tailor-made products exist for shared wallets, but any wallet application th

---

OK, let's have a look at some [case studies]({{ '/guide/case-studies/' | relative_url }}).
OK, to end this chapter let's have a look at how to do safe [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }}).
4 changes: 2 additions & 2 deletions guide/private-key-management/single-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -132,9 +132,9 @@ This scheme is suitable for users who are already familiar with bitcoin and proc
### How it works
The wallet application will generate a 12 or 24 word phrase (seed / [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }})) from which all the wallet’s [keys]({{ '/guide/glossary/#keys' | relative_url }}) can be derived. This means the user can have access to the wallet from any compatible wallet application with the phrase, even if they lose the device or software.

This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the op-sec burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase. You need to take resistance to physical theft, fire and other destructive events into account. To get the best security out of recovery phrases they should be kept on several dedicated [metal storage pieces](https://jlopp.github.io/metal-bitcoin-storage-reviews/) in secure places offline. A fair amount of effort and knowledge is required for this.
This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase.

A full guide to manual backup best practices for users is out of scope for this chapter but the [Do's and Dont's](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) of Bitcoin key management is a good starting point.
Safe backups can be made fairly simple, take a look at our [Bitcoin backups](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) guide as good starting point.

{% include fact/pros.html %}

Expand Down
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Bitcoin backups page - replaces #210 by danielnordh · Pull Request #305 · BitcoinDesign/Guide · GitHub
Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions _compress_images_cache.yml
Original file line numberDiff line numberDiff line change
Expand Up@@ -655,3 +655,20 @@ assets/images/guide/getting-started/usage-life-cycle/dropoff@2x.png: dropoff@2x.
assets/images/guide/payments/send/bitcoin-payments@2x.jpg: bitcoin-payments@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-mobile@2x.jpg: bitcoin-payments-mobile@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-social.jpg: bitcoin-payments-social.jpg
assets/images/guide/private-key-management/backups/backups-mobile.jpg: backups-mobile.jpg
assets/images/guide/private-key-management/backups/backup-table.png: backup-table.png
assets/images/guide/private-key-management/backups/backups.jpg: backups.jpg
assets/images/guide/private-key-management/backups/page-backups.jpg: page-backups.jpg
assets/images/guide/private-key-management/backups/backups@2x.jpg: backups@2x.jpg
assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg: backups-mobile@2x.jpg
assets/images/guide/private-key-management/backups/backup-table@2x.png: backup-table@2x.png
assets/images/guide/private-key-management/backups/paperbackup@2x.jpg: paperbackup@2x.jpg
assets/images/guide/private-key-management/backups/metalbackup.jpg: metalbackup.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg: offline-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/metalbackup@2x.jpg: metalbackup@2x.jpg
assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg: cloud-backup@2x.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg: offline-discoveryprotection@2x.jpg
assets/images/guide/private-key-management/backups/paperbackup.jpg: paperbackup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg: multiple-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/cloud-backup.jpg: cloud-backup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg: multiple-discoveryprotection@2x.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
267 changes: 267 additions & 0 deletions guide/private-key-management/backups.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,267 @@
---
layout: guide
title: Bitcoin backups
description: A beginner's guide to Bitcoin backups.
nav_order: 4
parent: Private key management
permalink: /guide/private-key-management/backups/
main_classes: -no-top-padding
image: https://bitcoin.design/assets/images/guide/private-key-management/backups/page-backups.jpg
Comment thread
danielnordh marked this conversation as resolved.
---

<!--

Editor's notes

A guide meant to lower the barrier for first time users of self-custody wallets.

Illustration sources

//

-->

{% include picture.html
image = "/assets/images/guide/private-key-management/backups/backups.jpg"
retina = "/assets/images/guide/private-key-management/backups/backups@2x.jpg"
mobile = "/assets/images/guide/private-key-management/backups/backups-mobile.jpg"
mobileRetina = "/assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg"
alt-text = "Several devices exchanging data"
width = 1600
height = 700
layout = "full-width"
%}

# Bitcoin backups

The self-custody of Bitcoin is an important right, but also a financial responsibility that can scale from pocket money to life savings, and take practice getting used to.

This guide is a straightforward starting point for simple Bitcoin backups, aimed at users of Bitcoin products.

If you are a designer or developer, make sure you offer guidance to your users so they can secure their bitcoin with an appropriate backup.


## What are backups?

When we talk about backups, we mean saving the information needed to restore access to a wallet outside of the application that created the private keys. Often, this will just be the [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }}) of 12 or 24 words, but can also include other information like a *pass-phrase* and [derivation path]({{ '/guide/glossary/#derivation-path' | relative_url }}).
Comment thread
danielnordh marked this conversation as resolved.

The main risks that backups need to protect against are:

- Loss of wallet - you lost the device and application holding the private key
- Remote theft - your backup got discovered online by a bad actor
- Physical damage - your backup got destroyed
- Theft on discovery - your backup got discovered in person by a bad actor
- Catastrophic events - your backup location got destroyed
- Inheritance loss - next-of-kin were unable to access your wallet


## Backup levels, basic to advanced

A basic backup can be done in a few minutes, while more advanced setups can require more time and effort, like the purchase of dedicated material.

Let’s look at some real life examples of backup methods for single-key wallets and what they protect against.

<br>

{% include image.html
image = "/assets/images/guide/private-key-management/backups/backup-table.png"
retina = "/assets/images/guide/private-key-management/backups/backup-table@2x.png"
alt-text = "Table of backup levels"
width = 904
height = 625
layout = "full-width"
%}

{% include tip/recommendation.html %}

Level 0 and 1 are good when getting started, and require very little effort.

Level 2, 3 or 4 are recommended for storing larger amounts.

{% include tip/close.html %}

<br>

#### Level 0
## Encrypted cloud backup

By storing the recovery-phrase in an online location that is encrypted (not in plain text) and hard to access by anyone other than yourself, you are protected against *loss of wallet*. This is the absolute minimum you should do and only takes a few minutes.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/cloud-backup.jpg"
retina = "/assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg"
alt-text = "Encrypted cloud backup"
Comment thread
danielnordh marked this conversation as resolved.
width = 800
height = 420
%}

**Do**
- Use an encrypted password manager like 1Password, LastPass, iCloud Keychain
- Alternatively, use a wallet application with automatic cloud backup

**Don’t**
- Screenshot the recovery-phrase and save it in Google Photos, iCloud photos
- Write down the recovery-phrase in plain text on your device, Google Docs etc.

**Suitable for**
- For small amounts (less than a months salary)
- When you can't wait to set up a new wallet until you are at home

<br>

#### Level 1
## Single paper backup

By storing the recovery-phrase written down on paper in your own home you have protected against *loss of wallet* and *remote theft*.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/paperbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/paperbackup@2x.jpg"
alt-text = "24 word paper backup"
width = 800
height = 508
%}


**Do**
- Write the recovery-phrase with the words numbered, using permanent ink on card
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Scribble the recovery-phrase on a scrap of paper using a pencil
- Stick it on the fridge, or other visible locations

**Suitable**
- For small amounts (less than a months salary)
- When you are setting up a new wallet at home

<br>

#### Level 2
## Single metal backup

By storing the recovery-phrase on metal in your own home you have protected against *loss of wallet*, *remote theft* and *physical damage*.

The best metal backup solutions are resistant to most physical damage, including fire, acid and high pressure.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/metalbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/metalbackup@2x.jpg"
alt-text = "Metal backup"
width = 800
height = 440
%}


**Do**
- Order a dedicated metal backup product, recommendations can be found [here](https://jlopp.github.io/metal-bitcoin-storage-reviews/)
- Follow the instructions and make sure the phrase is indented, etched, engraved or set properly
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Skip ordering a dedicated product, invent your own metal backup solution

**Suitable for**
- Amounts above your monthly salary, but less than half your annual salary

<br>

#### Level 3
## Single backup with discovery protection
The previous offline backups have one flaw in common - if discovered by a bad actor, your funds can be stolen.

To protect against this *theft on discovery* risk, a *pass-phrase* can be added to the recovery-phrase. This pass-phrase is sometimes called an extra word, or the 13th/25th word.

While this level provides more protection, it also adds complexity to your backup setup. For most beginners storing small amounts it might not be worth the effort from the start and can be a later consideration should the funds grow.

Technically, all recovery-phrases have a pass-phrase. If it's not set by the user, an empty string (“”) will be used by default. This means that using the recovery-phrase with or without the user-defined pass-phrase will recover two DIFFERENT wallets.

If a bad actor discovers only the recovery-phrase, they will find an empty wallet. Alternatively, one can deliberately leave a small amount of bitcoin in this wallet as a honey-pot, and monitor it for any withdrawals to know if it has been discovered.

To provide protection against *theft on discovery*, the pass-phrase should be stored separate from the recovery-phrase.

Since adding a pass-phrase will generate a different wallet, it is best to add it when first creating the wallet, and before storing any bitcoin in its addresses.

It's worth noting that most hardware wallets support pass-phrases, while most software wallet applications do not.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg"
alt-text = "Offline backup with discovery protection"
width = 800
height = 420
%}


**Do**
- Use a secure pass-phrase, it is case sensitive and can include numbers and special characters
- Have redundant and secure backups of both the recovery-phrase and the pass-phrase, they are equally important for successful wallet recovery
- Understand you now have two distinct wallets, (one each from the recovery-phrase with or without the pass-phrase), this can be useful to fool a bad actor, or a risk if next-of-kin is unaware of the pass-phrase

**Don’t**
- Store the recovery-phrase and pass-phrase together
- Forget to document your setup for next-of-kin

**Suitable for**
- Large amounts
- Situations where the backup can be discovered by bad actors

**Alternative**

Set up a hardware wallet from the recovery and pass-phrase that uses a PIN to protect usage. The PIN now becomes the protection against theft on discovery and should be saved somewhere safe just like the pass-phrase.

<br>

#### Level 4
## Multiple backups with discovery protection
One remaining flaw with the single offline backup levels is that severe damage to the one location where they are stored, could lead to the backup not being usable. This could be a fire, flood, earthquake or similar, all more or less likely depending on where you live.

To protect against such a *catastrophic event* we can create multiple backups, and distribute them to other locations. This could be a second home, trusted family and friends or a safe deposit box.

As the risk of discovery increases with the multiplying backups, it's best to maintain the protection against theft on discovery with a pass-phrase, or hardware wallets with a PIN.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg"
alt-text = "Multiple offline backups with discovery protection"
width = 800
height = 420
%}

**Do**
- Make sure you have reduntant copies of all parts of the backup in several locations
- Document your setup well for next-of-kin now that complexity has increased

**Don’t**
- Forget to safely store the pass-phrases or PINs

**Suitable for**
- Large amounts
- In locations where catastrophic events are common, or likely to cause severe damage

<br>

---

## Inheritance instructions
For any backup setup, sufficient information and understandable instructions for recovering the wallet should be available to next-of-kin.

Even though it might feel uncomfortable (or unnecessary if you are young and single), it is never too early to document your wallets. If you don’t, there is a very high chance that next-of-kin will not be able to inherit your funds.

At a minimum, document each wallet with a given name (Bob’s Bitcoin wallet 1), how to recover it, when it was created and what application was used to create the wallet. Ideally this document has all the instructions required to recover the wallet, but not the information itself (*recovery-phrase*, *pass-phrase* etc.), as that might expose you to theft on discovery risks.

**Do**
- Make next-of-kin aware of the existence of any wallets
- Explain clearly how to recover the setup, and how to access the required information


**Don’t**
- Store any required information ONLY in locations that will not be accessible to next-of-kin (password managers, single user accounts etc.)


**Suitable for**
- Any amount
6 changes: 6 additions & 0 deletions guide/private-key-management/introduction.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -55,4 +55,10 @@ An introduction to some of the common private key management schemes for shared

---

### [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }})

A straightforward guide to safe manual backups.

---

Start at the top with [private key schemes]({{ '/guide/private-key-management/schemes/' | relative_url }}).
2 changes: 1 addition & 1 deletion guide/private-key-management/multi-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -87,4 +87,4 @@ Few tailor-made products exist for shared wallets, but any wallet application th

---

OK, let's have a look at some [case studies]({{ '/guide/case-studies/' | relative_url }}).
OK, to end this chapter let's have a look at how to do safe [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }}).
4 changes: 2 additions & 2 deletions guide/private-key-management/single-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -132,9 +132,9 @@ This scheme is suitable for users who are already familiar with bitcoin and proc
### How it works
The wallet application will generate a 12 or 24 word phrase (seed / [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }})) from which all the wallet’s [keys]({{ '/guide/glossary/#keys' | relative_url }}) can be derived. This means the user can have access to the wallet from any compatible wallet application with the phrase, even if they lose the device or software.

This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the op-sec burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase. You need to take resistance to physical theft, fire and other destructive events into account. To get the best security out of recovery phrases they should be kept on several dedicated [metal storage pieces](https://jlopp.github.io/metal-bitcoin-storage-reviews/) in secure places offline. A fair amount of effort and knowledge is required for this.
This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase.

A full guide to manual backup best practices for users is out of scope for this chapter but the [Do's and Dont's](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) of Bitcoin key management is a good starting point.
Safe backups can be made fairly simple, take a look at our [Bitcoin backups](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) guide as good starting point.

{% include fact/pros.html %}

Expand Down
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Bitcoin backups page - replaces #210 by danielnordh · Pull Request #305 · BitcoinDesign/Guide · GitHub
Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions _compress_images_cache.yml
Original file line numberDiff line numberDiff line change
Expand Up@@ -655,3 +655,20 @@ assets/images/guide/getting-started/usage-life-cycle/dropoff@2x.png: dropoff@2x.
assets/images/guide/payments/send/bitcoin-payments@2x.jpg: bitcoin-payments@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-mobile@2x.jpg: bitcoin-payments-mobile@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-social.jpg: bitcoin-payments-social.jpg
assets/images/guide/private-key-management/backups/backups-mobile.jpg: backups-mobile.jpg
assets/images/guide/private-key-management/backups/backup-table.png: backup-table.png
assets/images/guide/private-key-management/backups/backups.jpg: backups.jpg
assets/images/guide/private-key-management/backups/page-backups.jpg: page-backups.jpg
assets/images/guide/private-key-management/backups/backups@2x.jpg: backups@2x.jpg
assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg: backups-mobile@2x.jpg
assets/images/guide/private-key-management/backups/backup-table@2x.png: backup-table@2x.png
assets/images/guide/private-key-management/backups/paperbackup@2x.jpg: paperbackup@2x.jpg
assets/images/guide/private-key-management/backups/metalbackup.jpg: metalbackup.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg: offline-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/metalbackup@2x.jpg: metalbackup@2x.jpg
assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg: cloud-backup@2x.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg: offline-discoveryprotection@2x.jpg
assets/images/guide/private-key-management/backups/paperbackup.jpg: paperbackup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg: multiple-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/cloud-backup.jpg: cloud-backup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg: multiple-discoveryprotection@2x.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
267 changes: 267 additions & 0 deletions guide/private-key-management/backups.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,267 @@
---
layout: guide
title: Bitcoin backups
description: A beginner's guide to Bitcoin backups.
nav_order: 4
parent: Private key management
permalink: /guide/private-key-management/backups/
main_classes: -no-top-padding
image: https://bitcoin.design/assets/images/guide/private-key-management/backups/page-backups.jpg
Comment thread
danielnordh marked this conversation as resolved.
---

<!--

Editor's notes

A guide meant to lower the barrier for first time users of self-custody wallets.

Illustration sources

//

-->

{% include picture.html
image = "/assets/images/guide/private-key-management/backups/backups.jpg"
retina = "/assets/images/guide/private-key-management/backups/backups@2x.jpg"
mobile = "/assets/images/guide/private-key-management/backups/backups-mobile.jpg"
mobileRetina = "/assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg"
alt-text = "Several devices exchanging data"
width = 1600
height = 700
layout = "full-width"
%}

# Bitcoin backups

The self-custody of Bitcoin is an important right, but also a financial responsibility that can scale from pocket money to life savings, and take practice getting used to.

This guide is a straightforward starting point for simple Bitcoin backups, aimed at users of Bitcoin products.

If you are a designer or developer, make sure you offer guidance to your users so they can secure their bitcoin with an appropriate backup.


## What are backups?

When we talk about backups, we mean saving the information needed to restore access to a wallet outside of the application that created the private keys. Often, this will just be the [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }}) of 12 or 24 words, but can also include other information like a *pass-phrase* and [derivation path]({{ '/guide/glossary/#derivation-path' | relative_url }}).
Comment thread
danielnordh marked this conversation as resolved.

The main risks that backups need to protect against are:

- Loss of wallet - you lost the device and application holding the private key
- Remote theft - your backup got discovered online by a bad actor
- Physical damage - your backup got destroyed
- Theft on discovery - your backup got discovered in person by a bad actor
- Catastrophic events - your backup location got destroyed
- Inheritance loss - next-of-kin were unable to access your wallet


## Backup levels, basic to advanced

A basic backup can be done in a few minutes, while more advanced setups can require more time and effort, like the purchase of dedicated material.

Let’s look at some real life examples of backup methods for single-key wallets and what they protect against.

<br>

{% include image.html
image = "/assets/images/guide/private-key-management/backups/backup-table.png"
retina = "/assets/images/guide/private-key-management/backups/backup-table@2x.png"
alt-text = "Table of backup levels"
width = 904
height = 625
layout = "full-width"
%}

{% include tip/recommendation.html %}

Level 0 and 1 are good when getting started, and require very little effort.

Level 2, 3 or 4 are recommended for storing larger amounts.

{% include tip/close.html %}

<br>

#### Level 0
## Encrypted cloud backup

By storing the recovery-phrase in an online location that is encrypted (not in plain text) and hard to access by anyone other than yourself, you are protected against *loss of wallet*. This is the absolute minimum you should do and only takes a few minutes.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/cloud-backup.jpg"
retina = "/assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg"
alt-text = "Encrypted cloud backup"
Comment thread
danielnordh marked this conversation as resolved.
width = 800
height = 420
%}

**Do**
- Use an encrypted password manager like 1Password, LastPass, iCloud Keychain
- Alternatively, use a wallet application with automatic cloud backup

**Don’t**
- Screenshot the recovery-phrase and save it in Google Photos, iCloud photos
- Write down the recovery-phrase in plain text on your device, Google Docs etc.

**Suitable for**
- For small amounts (less than a months salary)
- When you can't wait to set up a new wallet until you are at home

<br>

#### Level 1
## Single paper backup

By storing the recovery-phrase written down on paper in your own home you have protected against *loss of wallet* and *remote theft*.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/paperbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/paperbackup@2x.jpg"
alt-text = "24 word paper backup"
width = 800
height = 508
%}


**Do**
- Write the recovery-phrase with the words numbered, using permanent ink on card
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Scribble the recovery-phrase on a scrap of paper using a pencil
- Stick it on the fridge, or other visible locations

**Suitable**
- For small amounts (less than a months salary)
- When you are setting up a new wallet at home

<br>

#### Level 2
## Single metal backup

By storing the recovery-phrase on metal in your own home you have protected against *loss of wallet*, *remote theft* and *physical damage*.

The best metal backup solutions are resistant to most physical damage, including fire, acid and high pressure.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/metalbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/metalbackup@2x.jpg"
alt-text = "Metal backup"
width = 800
height = 440
%}


**Do**
- Order a dedicated metal backup product, recommendations can be found [here](https://jlopp.github.io/metal-bitcoin-storage-reviews/)
- Follow the instructions and make sure the phrase is indented, etched, engraved or set properly
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Skip ordering a dedicated product, invent your own metal backup solution

**Suitable for**
- Amounts above your monthly salary, but less than half your annual salary

<br>

#### Level 3
## Single backup with discovery protection
The previous offline backups have one flaw in common - if discovered by a bad actor, your funds can be stolen.

To protect against this *theft on discovery* risk, a *pass-phrase* can be added to the recovery-phrase. This pass-phrase is sometimes called an extra word, or the 13th/25th word.

While this level provides more protection, it also adds complexity to your backup setup. For most beginners storing small amounts it might not be worth the effort from the start and can be a later consideration should the funds grow.

Technically, all recovery-phrases have a pass-phrase. If it's not set by the user, an empty string (“”) will be used by default. This means that using the recovery-phrase with or without the user-defined pass-phrase will recover two DIFFERENT wallets.

If a bad actor discovers only the recovery-phrase, they will find an empty wallet. Alternatively, one can deliberately leave a small amount of bitcoin in this wallet as a honey-pot, and monitor it for any withdrawals to know if it has been discovered.

To provide protection against *theft on discovery*, the pass-phrase should be stored separate from the recovery-phrase.

Since adding a pass-phrase will generate a different wallet, it is best to add it when first creating the wallet, and before storing any bitcoin in its addresses.

It's worth noting that most hardware wallets support pass-phrases, while most software wallet applications do not.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg"
alt-text = "Offline backup with discovery protection"
width = 800
height = 420
%}


**Do**
- Use a secure pass-phrase, it is case sensitive and can include numbers and special characters
- Have redundant and secure backups of both the recovery-phrase and the pass-phrase, they are equally important for successful wallet recovery
- Understand you now have two distinct wallets, (one each from the recovery-phrase with or without the pass-phrase), this can be useful to fool a bad actor, or a risk if next-of-kin is unaware of the pass-phrase

**Don’t**
- Store the recovery-phrase and pass-phrase together
- Forget to document your setup for next-of-kin

**Suitable for**
- Large amounts
- Situations where the backup can be discovered by bad actors

**Alternative**

Set up a hardware wallet from the recovery and pass-phrase that uses a PIN to protect usage. The PIN now becomes the protection against theft on discovery and should be saved somewhere safe just like the pass-phrase.

<br>

#### Level 4
## Multiple backups with discovery protection
One remaining flaw with the single offline backup levels is that severe damage to the one location where they are stored, could lead to the backup not being usable. This could be a fire, flood, earthquake or similar, all more or less likely depending on where you live.

To protect against such a *catastrophic event* we can create multiple backups, and distribute them to other locations. This could be a second home, trusted family and friends or a safe deposit box.

As the risk of discovery increases with the multiplying backups, it's best to maintain the protection against theft on discovery with a pass-phrase, or hardware wallets with a PIN.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg"
alt-text = "Multiple offline backups with discovery protection"
width = 800
height = 420
%}

**Do**
- Make sure you have reduntant copies of all parts of the backup in several locations
- Document your setup well for next-of-kin now that complexity has increased

**Don’t**
- Forget to safely store the pass-phrases or PINs

**Suitable for**
- Large amounts
- In locations where catastrophic events are common, or likely to cause severe damage

<br>

---

## Inheritance instructions
For any backup setup, sufficient information and understandable instructions for recovering the wallet should be available to next-of-kin.

Even though it might feel uncomfortable (or unnecessary if you are young and single), it is never too early to document your wallets. If you don’t, there is a very high chance that next-of-kin will not be able to inherit your funds.

At a minimum, document each wallet with a given name (Bob’s Bitcoin wallet 1), how to recover it, when it was created and what application was used to create the wallet. Ideally this document has all the instructions required to recover the wallet, but not the information itself (*recovery-phrase*, *pass-phrase* etc.), as that might expose you to theft on discovery risks.

**Do**
- Make next-of-kin aware of the existence of any wallets
- Explain clearly how to recover the setup, and how to access the required information


**Don’t**
- Store any required information ONLY in locations that will not be accessible to next-of-kin (password managers, single user accounts etc.)


**Suitable for**
- Any amount
6 changes: 6 additions & 0 deletions guide/private-key-management/introduction.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -55,4 +55,10 @@ An introduction to some of the common private key management schemes for shared

---

### [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }})

A straightforward guide to safe manual backups.

---

Start at the top with [private key schemes]({{ '/guide/private-key-management/schemes/' | relative_url }}).
2 changes: 1 addition & 1 deletion guide/private-key-management/multi-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -87,4 +87,4 @@ Few tailor-made products exist for shared wallets, but any wallet application th

---

OK, let's have a look at some [case studies]({{ '/guide/case-studies/' | relative_url }}).
OK, to end this chapter let's have a look at how to do safe [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }}).
4 changes: 2 additions & 2 deletions guide/private-key-management/single-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -132,9 +132,9 @@ This scheme is suitable for users who are already familiar with bitcoin and proc
### How it works
The wallet application will generate a 12 or 24 word phrase (seed / [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }})) from which all the wallet’s [keys]({{ '/guide/glossary/#keys' | relative_url }}) can be derived. This means the user can have access to the wallet from any compatible wallet application with the phrase, even if they lose the device or software.

This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the op-sec burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase. You need to take resistance to physical theft, fire and other destructive events into account. To get the best security out of recovery phrases they should be kept on several dedicated [metal storage pieces](https://jlopp.github.io/metal-bitcoin-storage-reviews/) in secure places offline. A fair amount of effort and knowledge is required for this.
This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase.

A full guide to manual backup best practices for users is out of scope for this chapter but the [Do's and Dont's](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) of Bitcoin key management is a good starting point.
Safe backups can be made fairly simple, take a look at our [Bitcoin backups](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) guide as good starting point.

{% include fact/pros.html %}

Expand Down
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' Bitcoin backups page - replaces #210 by danielnordh · Pull Request #305 · BitcoinDesign/Guide · GitHub
Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions _compress_images_cache.yml
Original file line numberDiff line numberDiff line change
Expand Up@@ -655,3 +655,20 @@ assets/images/guide/getting-started/usage-life-cycle/dropoff@2x.png: dropoff@2x.
assets/images/guide/payments/send/bitcoin-payments@2x.jpg: bitcoin-payments@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-mobile@2x.jpg: bitcoin-payments-mobile@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-social.jpg: bitcoin-payments-social.jpg
assets/images/guide/private-key-management/backups/backups-mobile.jpg: backups-mobile.jpg
assets/images/guide/private-key-management/backups/backup-table.png: backup-table.png
assets/images/guide/private-key-management/backups/backups.jpg: backups.jpg
assets/images/guide/private-key-management/backups/page-backups.jpg: page-backups.jpg
assets/images/guide/private-key-management/backups/backups@2x.jpg: backups@2x.jpg
assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg: backups-mobile@2x.jpg
assets/images/guide/private-key-management/backups/backup-table@2x.png: backup-table@2x.png
assets/images/guide/private-key-management/backups/paperbackup@2x.jpg: paperbackup@2x.jpg
assets/images/guide/private-key-management/backups/metalbackup.jpg: metalbackup.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg: offline-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/metalbackup@2x.jpg: metalbackup@2x.jpg
assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg: cloud-backup@2x.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg: offline-discoveryprotection@2x.jpg
assets/images/guide/private-key-management/backups/paperbackup.jpg: paperbackup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg: multiple-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/cloud-backup.jpg: cloud-backup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg: multiple-discoveryprotection@2x.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
267 changes: 267 additions & 0 deletions guide/private-key-management/backups.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,267 @@
---
layout: guide
title: Bitcoin backups
description: A beginner's guide to Bitcoin backups.
nav_order: 4
parent: Private key management
permalink: /guide/private-key-management/backups/
main_classes: -no-top-padding
image: https://bitcoin.design/assets/images/guide/private-key-management/backups/page-backups.jpg
Comment thread
danielnordh marked this conversation as resolved.
---

<!--

Editor's notes

A guide meant to lower the barrier for first time users of self-custody wallets.

Illustration sources

//

-->

{% include picture.html
image = "/assets/images/guide/private-key-management/backups/backups.jpg"
retina = "/assets/images/guide/private-key-management/backups/backups@2x.jpg"
mobile = "/assets/images/guide/private-key-management/backups/backups-mobile.jpg"
mobileRetina = "/assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg"
alt-text = "Several devices exchanging data"
width = 1600
height = 700
layout = "full-width"
%}

# Bitcoin backups

The self-custody of Bitcoin is an important right, but also a financial responsibility that can scale from pocket money to life savings, and take practice getting used to.

This guide is a straightforward starting point for simple Bitcoin backups, aimed at users of Bitcoin products.

If you are a designer or developer, make sure you offer guidance to your users so they can secure their bitcoin with an appropriate backup.


## What are backups?

When we talk about backups, we mean saving the information needed to restore access to a wallet outside of the application that created the private keys. Often, this will just be the [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }}) of 12 or 24 words, but can also include other information like a *pass-phrase* and [derivation path]({{ '/guide/glossary/#derivation-path' | relative_url }}).
Comment thread
danielnordh marked this conversation as resolved.

The main risks that backups need to protect against are:

- Loss of wallet - you lost the device and application holding the private key
- Remote theft - your backup got discovered online by a bad actor
- Physical damage - your backup got destroyed
- Theft on discovery - your backup got discovered in person by a bad actor
- Catastrophic events - your backup location got destroyed
- Inheritance loss - next-of-kin were unable to access your wallet


## Backup levels, basic to advanced

A basic backup can be done in a few minutes, while more advanced setups can require more time and effort, like the purchase of dedicated material.

Let’s look at some real life examples of backup methods for single-key wallets and what they protect against.

<br>

{% include image.html
image = "/assets/images/guide/private-key-management/backups/backup-table.png"
retina = "/assets/images/guide/private-key-management/backups/backup-table@2x.png"
alt-text = "Table of backup levels"
width = 904
height = 625
layout = "full-width"
%}

{% include tip/recommendation.html %}

Level 0 and 1 are good when getting started, and require very little effort.

Level 2, 3 or 4 are recommended for storing larger amounts.

{% include tip/close.html %}

<br>

#### Level 0
## Encrypted cloud backup

By storing the recovery-phrase in an online location that is encrypted (not in plain text) and hard to access by anyone other than yourself, you are protected against *loss of wallet*. This is the absolute minimum you should do and only takes a few minutes.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/cloud-backup.jpg"
retina = "/assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg"
alt-text = "Encrypted cloud backup"
Comment thread
danielnordh marked this conversation as resolved.
width = 800
height = 420
%}

**Do**
- Use an encrypted password manager like 1Password, LastPass, iCloud Keychain
- Alternatively, use a wallet application with automatic cloud backup

**Don’t**
- Screenshot the recovery-phrase and save it in Google Photos, iCloud photos
- Write down the recovery-phrase in plain text on your device, Google Docs etc.

**Suitable for**
- For small amounts (less than a months salary)
- When you can't wait to set up a new wallet until you are at home

<br>

#### Level 1
## Single paper backup

By storing the recovery-phrase written down on paper in your own home you have protected against *loss of wallet* and *remote theft*.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/paperbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/paperbackup@2x.jpg"
alt-text = "24 word paper backup"
width = 800
height = 508
%}


**Do**
- Write the recovery-phrase with the words numbered, using permanent ink on card
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Scribble the recovery-phrase on a scrap of paper using a pencil
- Stick it on the fridge, or other visible locations

**Suitable**
- For small amounts (less than a months salary)
- When you are setting up a new wallet at home

<br>

#### Level 2
## Single metal backup

By storing the recovery-phrase on metal in your own home you have protected against *loss of wallet*, *remote theft* and *physical damage*.

The best metal backup solutions are resistant to most physical damage, including fire, acid and high pressure.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/metalbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/metalbackup@2x.jpg"
alt-text = "Metal backup"
width = 800
height = 440
%}


**Do**
- Order a dedicated metal backup product, recommendations can be found [here](https://jlopp.github.io/metal-bitcoin-storage-reviews/)
- Follow the instructions and make sure the phrase is indented, etched, engraved or set properly
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Skip ordering a dedicated product, invent your own metal backup solution

**Suitable for**
- Amounts above your monthly salary, but less than half your annual salary

<br>

#### Level 3
## Single backup with discovery protection
The previous offline backups have one flaw in common - if discovered by a bad actor, your funds can be stolen.

To protect against this *theft on discovery* risk, a *pass-phrase* can be added to the recovery-phrase. This pass-phrase is sometimes called an extra word, or the 13th/25th word.

While this level provides more protection, it also adds complexity to your backup setup. For most beginners storing small amounts it might not be worth the effort from the start and can be a later consideration should the funds grow.

Technically, all recovery-phrases have a pass-phrase. If it's not set by the user, an empty string (“”) will be used by default. This means that using the recovery-phrase with or without the user-defined pass-phrase will recover two DIFFERENT wallets.

If a bad actor discovers only the recovery-phrase, they will find an empty wallet. Alternatively, one can deliberately leave a small amount of bitcoin in this wallet as a honey-pot, and monitor it for any withdrawals to know if it has been discovered.

To provide protection against *theft on discovery*, the pass-phrase should be stored separate from the recovery-phrase.

Since adding a pass-phrase will generate a different wallet, it is best to add it when first creating the wallet, and before storing any bitcoin in its addresses.

It's worth noting that most hardware wallets support pass-phrases, while most software wallet applications do not.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg"
alt-text = "Offline backup with discovery protection"
width = 800
height = 420
%}


**Do**
- Use a secure pass-phrase, it is case sensitive and can include numbers and special characters
- Have redundant and secure backups of both the recovery-phrase and the pass-phrase, they are equally important for successful wallet recovery
- Understand you now have two distinct wallets, (one each from the recovery-phrase with or without the pass-phrase), this can be useful to fool a bad actor, or a risk if next-of-kin is unaware of the pass-phrase

**Don’t**
- Store the recovery-phrase and pass-phrase together
- Forget to document your setup for next-of-kin

**Suitable for**
- Large amounts
- Situations where the backup can be discovered by bad actors

**Alternative**

Set up a hardware wallet from the recovery and pass-phrase that uses a PIN to protect usage. The PIN now becomes the protection against theft on discovery and should be saved somewhere safe just like the pass-phrase.

<br>

#### Level 4
## Multiple backups with discovery protection
One remaining flaw with the single offline backup levels is that severe damage to the one location where they are stored, could lead to the backup not being usable. This could be a fire, flood, earthquake or similar, all more or less likely depending on where you live.

To protect against such a *catastrophic event* we can create multiple backups, and distribute them to other locations. This could be a second home, trusted family and friends or a safe deposit box.

As the risk of discovery increases with the multiplying backups, it's best to maintain the protection against theft on discovery with a pass-phrase, or hardware wallets with a PIN.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg"
alt-text = "Multiple offline backups with discovery protection"
width = 800
height = 420
%}

**Do**
- Make sure you have reduntant copies of all parts of the backup in several locations
- Document your setup well for next-of-kin now that complexity has increased

**Don’t**
- Forget to safely store the pass-phrases or PINs

**Suitable for**
- Large amounts
- In locations where catastrophic events are common, or likely to cause severe damage

<br>

---

## Inheritance instructions
For any backup setup, sufficient information and understandable instructions for recovering the wallet should be available to next-of-kin.

Even though it might feel uncomfortable (or unnecessary if you are young and single), it is never too early to document your wallets. If you don’t, there is a very high chance that next-of-kin will not be able to inherit your funds.

At a minimum, document each wallet with a given name (Bob’s Bitcoin wallet 1), how to recover it, when it was created and what application was used to create the wallet. Ideally this document has all the instructions required to recover the wallet, but not the information itself (*recovery-phrase*, *pass-phrase* etc.), as that might expose you to theft on discovery risks.

**Do**
- Make next-of-kin aware of the existence of any wallets
- Explain clearly how to recover the setup, and how to access the required information


**Don’t**
- Store any required information ONLY in locations that will not be accessible to next-of-kin (password managers, single user accounts etc.)


**Suitable for**
- Any amount
6 changes: 6 additions & 0 deletions guide/private-key-management/introduction.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -55,4 +55,10 @@ An introduction to some of the common private key management schemes for shared

---

### [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }})

A straightforward guide to safe manual backups.

---

Start at the top with [private key schemes]({{ '/guide/private-key-management/schemes/' | relative_url }}).
2 changes: 1 addition & 1 deletion guide/private-key-management/multi-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -87,4 +87,4 @@ Few tailor-made products exist for shared wallets, but any wallet application th

---

OK, let's have a look at some [case studies]({{ '/guide/case-studies/' | relative_url }}).
OK, to end this chapter let's have a look at how to do safe [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }}).
4 changes: 2 additions & 2 deletions guide/private-key-management/single-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -132,9 +132,9 @@ This scheme is suitable for users who are already familiar with bitcoin and proc
### How it works
The wallet application will generate a 12 or 24 word phrase (seed / [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }})) from which all the wallet’s [keys]({{ '/guide/glossary/#keys' | relative_url }}) can be derived. This means the user can have access to the wallet from any compatible wallet application with the phrase, even if they lose the device or software.

This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the op-sec burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase. You need to take resistance to physical theft, fire and other destructive events into account. To get the best security out of recovery phrases they should be kept on several dedicated [metal storage pieces](https://jlopp.github.io/metal-bitcoin-storage-reviews/) in secure places offline. A fair amount of effort and knowledge is required for this.
This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase.

A full guide to manual backup best practices for users is out of scope for this chapter but the [Do's and Dont's](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) of Bitcoin key management is a good starting point.
Safe backups can be made fairly simple, take a look at our [Bitcoin backups](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) guide as good starting point.

{% include fact/pros.html %}

Expand Down
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Bitcoin backups page - replaces #210 by danielnordh · Pull Request #305 · BitcoinDesign/Guide · GitHub
Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions _compress_images_cache.yml
Original file line numberDiff line numberDiff line change
Expand Up@@ -655,3 +655,20 @@ assets/images/guide/getting-started/usage-life-cycle/dropoff@2x.png: dropoff@2x.
assets/images/guide/payments/send/bitcoin-payments@2x.jpg: bitcoin-payments@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-mobile@2x.jpg: bitcoin-payments-mobile@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-social.jpg: bitcoin-payments-social.jpg
assets/images/guide/private-key-management/backups/backups-mobile.jpg: backups-mobile.jpg
assets/images/guide/private-key-management/backups/backup-table.png: backup-table.png
assets/images/guide/private-key-management/backups/backups.jpg: backups.jpg
assets/images/guide/private-key-management/backups/page-backups.jpg: page-backups.jpg
assets/images/guide/private-key-management/backups/backups@2x.jpg: backups@2x.jpg
assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg: backups-mobile@2x.jpg
assets/images/guide/private-key-management/backups/backup-table@2x.png: backup-table@2x.png
assets/images/guide/private-key-management/backups/paperbackup@2x.jpg: paperbackup@2x.jpg
assets/images/guide/private-key-management/backups/metalbackup.jpg: metalbackup.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg: offline-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/metalbackup@2x.jpg: metalbackup@2x.jpg
assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg: cloud-backup@2x.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg: offline-discoveryprotection@2x.jpg
assets/images/guide/private-key-management/backups/paperbackup.jpg: paperbackup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg: multiple-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/cloud-backup.jpg: cloud-backup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg: multiple-discoveryprotection@2x.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
267 changes: 267 additions & 0 deletions guide/private-key-management/backups.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,267 @@
---
layout: guide
title: Bitcoin backups
description: A beginner's guide to Bitcoin backups.
nav_order: 4
parent: Private key management
permalink: /guide/private-key-management/backups/
main_classes: -no-top-padding
image: https://bitcoin.design/assets/images/guide/private-key-management/backups/page-backups.jpg
Comment thread
danielnordh marked this conversation as resolved.
---

<!--

Editor's notes

A guide meant to lower the barrier for first time users of self-custody wallets.

Illustration sources

//

-->

{% include picture.html
image = "/assets/images/guide/private-key-management/backups/backups.jpg"
retina = "/assets/images/guide/private-key-management/backups/backups@2x.jpg"
mobile = "/assets/images/guide/private-key-management/backups/backups-mobile.jpg"
mobileRetina = "/assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg"
alt-text = "Several devices exchanging data"
width = 1600
height = 700
layout = "full-width"
%}

# Bitcoin backups

The self-custody of Bitcoin is an important right, but also a financial responsibility that can scale from pocket money to life savings, and take practice getting used to.

This guide is a straightforward starting point for simple Bitcoin backups, aimed at users of Bitcoin products.

If you are a designer or developer, make sure you offer guidance to your users so they can secure their bitcoin with an appropriate backup.


## What are backups?

When we talk about backups, we mean saving the information needed to restore access to a wallet outside of the application that created the private keys. Often, this will just be the [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }}) of 12 or 24 words, but can also include other information like a *pass-phrase* and [derivation path]({{ '/guide/glossary/#derivation-path' | relative_url }}).
Comment thread
danielnordh marked this conversation as resolved.

The main risks that backups need to protect against are:

- Loss of wallet - you lost the device and application holding the private key
- Remote theft - your backup got discovered online by a bad actor
- Physical damage - your backup got destroyed
- Theft on discovery - your backup got discovered in person by a bad actor
- Catastrophic events - your backup location got destroyed
- Inheritance loss - next-of-kin were unable to access your wallet


## Backup levels, basic to advanced

A basic backup can be done in a few minutes, while more advanced setups can require more time and effort, like the purchase of dedicated material.

Let’s look at some real life examples of backup methods for single-key wallets and what they protect against.

<br>

{% include image.html
image = "/assets/images/guide/private-key-management/backups/backup-table.png"
retina = "/assets/images/guide/private-key-management/backups/backup-table@2x.png"
alt-text = "Table of backup levels"
width = 904
height = 625
layout = "full-width"
%}

{% include tip/recommendation.html %}

Level 0 and 1 are good when getting started, and require very little effort.

Level 2, 3 or 4 are recommended for storing larger amounts.

{% include tip/close.html %}

<br>

#### Level 0
## Encrypted cloud backup

By storing the recovery-phrase in an online location that is encrypted (not in plain text) and hard to access by anyone other than yourself, you are protected against *loss of wallet*. This is the absolute minimum you should do and only takes a few minutes.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/cloud-backup.jpg"
retina = "/assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg"
alt-text = "Encrypted cloud backup"
Comment thread
danielnordh marked this conversation as resolved.
width = 800
height = 420
%}

**Do**
- Use an encrypted password manager like 1Password, LastPass, iCloud Keychain
- Alternatively, use a wallet application with automatic cloud backup

**Don’t**
- Screenshot the recovery-phrase and save it in Google Photos, iCloud photos
- Write down the recovery-phrase in plain text on your device, Google Docs etc.

**Suitable for**
- For small amounts (less than a months salary)
- When you can't wait to set up a new wallet until you are at home

<br>

#### Level 1
## Single paper backup

By storing the recovery-phrase written down on paper in your own home you have protected against *loss of wallet* and *remote theft*.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/paperbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/paperbackup@2x.jpg"
alt-text = "24 word paper backup"
width = 800
height = 508
%}


**Do**
- Write the recovery-phrase with the words numbered, using permanent ink on card
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Scribble the recovery-phrase on a scrap of paper using a pencil
- Stick it on the fridge, or other visible locations

**Suitable**
- For small amounts (less than a months salary)
- When you are setting up a new wallet at home

<br>

#### Level 2
## Single metal backup

By storing the recovery-phrase on metal in your own home you have protected against *loss of wallet*, *remote theft* and *physical damage*.

The best metal backup solutions are resistant to most physical damage, including fire, acid and high pressure.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/metalbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/metalbackup@2x.jpg"
alt-text = "Metal backup"
width = 800
height = 440
%}


**Do**
- Order a dedicated metal backup product, recommendations can be found [here](https://jlopp.github.io/metal-bitcoin-storage-reviews/)
- Follow the instructions and make sure the phrase is indented, etched, engraved or set properly
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Skip ordering a dedicated product, invent your own metal backup solution

**Suitable for**
- Amounts above your monthly salary, but less than half your annual salary

<br>

#### Level 3
## Single backup with discovery protection
The previous offline backups have one flaw in common - if discovered by a bad actor, your funds can be stolen.

To protect against this *theft on discovery* risk, a *pass-phrase* can be added to the recovery-phrase. This pass-phrase is sometimes called an extra word, or the 13th/25th word.

While this level provides more protection, it also adds complexity to your backup setup. For most beginners storing small amounts it might not be worth the effort from the start and can be a later consideration should the funds grow.

Technically, all recovery-phrases have a pass-phrase. If it's not set by the user, an empty string (“”) will be used by default. This means that using the recovery-phrase with or without the user-defined pass-phrase will recover two DIFFERENT wallets.

If a bad actor discovers only the recovery-phrase, they will find an empty wallet. Alternatively, one can deliberately leave a small amount of bitcoin in this wallet as a honey-pot, and monitor it for any withdrawals to know if it has been discovered.

To provide protection against *theft on discovery*, the pass-phrase should be stored separate from the recovery-phrase.

Since adding a pass-phrase will generate a different wallet, it is best to add it when first creating the wallet, and before storing any bitcoin in its addresses.

It's worth noting that most hardware wallets support pass-phrases, while most software wallet applications do not.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg"
alt-text = "Offline backup with discovery protection"
width = 800
height = 420
%}


**Do**
- Use a secure pass-phrase, it is case sensitive and can include numbers and special characters
- Have redundant and secure backups of both the recovery-phrase and the pass-phrase, they are equally important for successful wallet recovery
- Understand you now have two distinct wallets, (one each from the recovery-phrase with or without the pass-phrase), this can be useful to fool a bad actor, or a risk if next-of-kin is unaware of the pass-phrase

**Don’t**
- Store the recovery-phrase and pass-phrase together
- Forget to document your setup for next-of-kin

**Suitable for**
- Large amounts
- Situations where the backup can be discovered by bad actors

**Alternative**

Set up a hardware wallet from the recovery and pass-phrase that uses a PIN to protect usage. The PIN now becomes the protection against theft on discovery and should be saved somewhere safe just like the pass-phrase.

<br>

#### Level 4
## Multiple backups with discovery protection
One remaining flaw with the single offline backup levels is that severe damage to the one location where they are stored, could lead to the backup not being usable. This could be a fire, flood, earthquake or similar, all more or less likely depending on where you live.

To protect against such a *catastrophic event* we can create multiple backups, and distribute them to other locations. This could be a second home, trusted family and friends or a safe deposit box.

As the risk of discovery increases with the multiplying backups, it's best to maintain the protection against theft on discovery with a pass-phrase, or hardware wallets with a PIN.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg"
alt-text = "Multiple offline backups with discovery protection"
width = 800
height = 420
%}

**Do**
- Make sure you have reduntant copies of all parts of the backup in several locations
- Document your setup well for next-of-kin now that complexity has increased

**Don’t**
- Forget to safely store the pass-phrases or PINs

**Suitable for**
- Large amounts
- In locations where catastrophic events are common, or likely to cause severe damage

<br>

---

## Inheritance instructions
For any backup setup, sufficient information and understandable instructions for recovering the wallet should be available to next-of-kin.

Even though it might feel uncomfortable (or unnecessary if you are young and single), it is never too early to document your wallets. If you don’t, there is a very high chance that next-of-kin will not be able to inherit your funds.

At a minimum, document each wallet with a given name (Bob’s Bitcoin wallet 1), how to recover it, when it was created and what application was used to create the wallet. Ideally this document has all the instructions required to recover the wallet, but not the information itself (*recovery-phrase*, *pass-phrase* etc.), as that might expose you to theft on discovery risks.

**Do**
- Make next-of-kin aware of the existence of any wallets
- Explain clearly how to recover the setup, and how to access the required information


**Don’t**
- Store any required information ONLY in locations that will not be accessible to next-of-kin (password managers, single user accounts etc.)


**Suitable for**
- Any amount
6 changes: 6 additions & 0 deletions guide/private-key-management/introduction.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -55,4 +55,10 @@ An introduction to some of the common private key management schemes for shared

---

### [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }})

A straightforward guide to safe manual backups.

---

Start at the top with [private key schemes]({{ '/guide/private-key-management/schemes/' | relative_url }}).
2 changes: 1 addition & 1 deletion guide/private-key-management/multi-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -87,4 +87,4 @@ Few tailor-made products exist for shared wallets, but any wallet application th

---

OK, let's have a look at some [case studies]({{ '/guide/case-studies/' | relative_url }}).
OK, to end this chapter let's have a look at how to do safe [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }}).
4 changes: 2 additions & 2 deletions guide/private-key-management/single-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -132,9 +132,9 @@ This scheme is suitable for users who are already familiar with bitcoin and proc
### How it works
The wallet application will generate a 12 or 24 word phrase (seed / [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }})) from which all the wallet’s [keys]({{ '/guide/glossary/#keys' | relative_url }}) can be derived. This means the user can have access to the wallet from any compatible wallet application with the phrase, even if they lose the device or software.

This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the op-sec burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase. You need to take resistance to physical theft, fire and other destructive events into account. To get the best security out of recovery phrases they should be kept on several dedicated [metal storage pieces](https://jlopp.github.io/metal-bitcoin-storage-reviews/) in secure places offline. A fair amount of effort and knowledge is required for this.
This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase.

A full guide to manual backup best practices for users is out of scope for this chapter but the [Do's and Dont's](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) of Bitcoin key management is a good starting point.
Safe backups can be made fairly simple, take a look at our [Bitcoin backups](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) guide as good starting point.

{% include fact/pros.html %}

Expand Down
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Bitcoin backups page - replaces #210 by danielnordh · Pull Request #305 · BitcoinDesign/Guide · GitHub
Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions _compress_images_cache.yml
Original file line numberDiff line numberDiff line change
Expand Up@@ -655,3 +655,20 @@ assets/images/guide/getting-started/usage-life-cycle/dropoff@2x.png: dropoff@2x.
assets/images/guide/payments/send/bitcoin-payments@2x.jpg: bitcoin-payments@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-mobile@2x.jpg: bitcoin-payments-mobile@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-social.jpg: bitcoin-payments-social.jpg
assets/images/guide/private-key-management/backups/backups-mobile.jpg: backups-mobile.jpg
assets/images/guide/private-key-management/backups/backup-table.png: backup-table.png
assets/images/guide/private-key-management/backups/backups.jpg: backups.jpg
assets/images/guide/private-key-management/backups/page-backups.jpg: page-backups.jpg
assets/images/guide/private-key-management/backups/backups@2x.jpg: backups@2x.jpg
assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg: backups-mobile@2x.jpg
assets/images/guide/private-key-management/backups/backup-table@2x.png: backup-table@2x.png
assets/images/guide/private-key-management/backups/paperbackup@2x.jpg: paperbackup@2x.jpg
assets/images/guide/private-key-management/backups/metalbackup.jpg: metalbackup.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg: offline-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/metalbackup@2x.jpg: metalbackup@2x.jpg
assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg: cloud-backup@2x.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg: offline-discoveryprotection@2x.jpg
assets/images/guide/private-key-management/backups/paperbackup.jpg: paperbackup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg: multiple-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/cloud-backup.jpg: cloud-backup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg: multiple-discoveryprotection@2x.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
267 changes: 267 additions & 0 deletions guide/private-key-management/backups.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,267 @@
---
layout: guide
title: Bitcoin backups
description: A beginner's guide to Bitcoin backups.
nav_order: 4
parent: Private key management
permalink: /guide/private-key-management/backups/
main_classes: -no-top-padding
image: https://bitcoin.design/assets/images/guide/private-key-management/backups/page-backups.jpg
Comment thread
danielnordh marked this conversation as resolved.
---

<!--

Editor's notes

A guide meant to lower the barrier for first time users of self-custody wallets.

Illustration sources

//

-->

{% include picture.html
image = "/assets/images/guide/private-key-management/backups/backups.jpg"
retina = "/assets/images/guide/private-key-management/backups/backups@2x.jpg"
mobile = "/assets/images/guide/private-key-management/backups/backups-mobile.jpg"
mobileRetina = "/assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg"
alt-text = "Several devices exchanging data"
width = 1600
height = 700
layout = "full-width"
%}

# Bitcoin backups

The self-custody of Bitcoin is an important right, but also a financial responsibility that can scale from pocket money to life savings, and take practice getting used to.

This guide is a straightforward starting point for simple Bitcoin backups, aimed at users of Bitcoin products.

If you are a designer or developer, make sure you offer guidance to your users so they can secure their bitcoin with an appropriate backup.


## What are backups?

When we talk about backups, we mean saving the information needed to restore access to a wallet outside of the application that created the private keys. Often, this will just be the [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }}) of 12 or 24 words, but can also include other information like a *pass-phrase* and [derivation path]({{ '/guide/glossary/#derivation-path' | relative_url }}).
Comment thread
danielnordh marked this conversation as resolved.

The main risks that backups need to protect against are:

- Loss of wallet - you lost the device and application holding the private key
- Remote theft - your backup got discovered online by a bad actor
- Physical damage - your backup got destroyed
- Theft on discovery - your backup got discovered in person by a bad actor
- Catastrophic events - your backup location got destroyed
- Inheritance loss - next-of-kin were unable to access your wallet


## Backup levels, basic to advanced

A basic backup can be done in a few minutes, while more advanced setups can require more time and effort, like the purchase of dedicated material.

Let’s look at some real life examples of backup methods for single-key wallets and what they protect against.

<br>

{% include image.html
image = "/assets/images/guide/private-key-management/backups/backup-table.png"
retina = "/assets/images/guide/private-key-management/backups/backup-table@2x.png"
alt-text = "Table of backup levels"
width = 904
height = 625
layout = "full-width"
%}

{% include tip/recommendation.html %}

Level 0 and 1 are good when getting started, and require very little effort.

Level 2, 3 or 4 are recommended for storing larger amounts.

{% include tip/close.html %}

<br>

#### Level 0
## Encrypted cloud backup

By storing the recovery-phrase in an online location that is encrypted (not in plain text) and hard to access by anyone other than yourself, you are protected against *loss of wallet*. This is the absolute minimum you should do and only takes a few minutes.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/cloud-backup.jpg"
retina = "/assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg"
alt-text = "Encrypted cloud backup"
Comment thread
danielnordh marked this conversation as resolved.
width = 800
height = 420
%}

**Do**
- Use an encrypted password manager like 1Password, LastPass, iCloud Keychain
- Alternatively, use a wallet application with automatic cloud backup

**Don’t**
- Screenshot the recovery-phrase and save it in Google Photos, iCloud photos
- Write down the recovery-phrase in plain text on your device, Google Docs etc.

**Suitable for**
- For small amounts (less than a months salary)
- When you can't wait to set up a new wallet until you are at home

<br>

#### Level 1
## Single paper backup

By storing the recovery-phrase written down on paper in your own home you have protected against *loss of wallet* and *remote theft*.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/paperbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/paperbackup@2x.jpg"
alt-text = "24 word paper backup"
width = 800
height = 508
%}


**Do**
- Write the recovery-phrase with the words numbered, using permanent ink on card
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Scribble the recovery-phrase on a scrap of paper using a pencil
- Stick it on the fridge, or other visible locations

**Suitable**
- For small amounts (less than a months salary)
- When you are setting up a new wallet at home

<br>

#### Level 2
## Single metal backup

By storing the recovery-phrase on metal in your own home you have protected against *loss of wallet*, *remote theft* and *physical damage*.

The best metal backup solutions are resistant to most physical damage, including fire, acid and high pressure.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/metalbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/metalbackup@2x.jpg"
alt-text = "Metal backup"
width = 800
height = 440
%}


**Do**
- Order a dedicated metal backup product, recommendations can be found [here](https://jlopp.github.io/metal-bitcoin-storage-reviews/)
- Follow the instructions and make sure the phrase is indented, etched, engraved or set properly
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Skip ordering a dedicated product, invent your own metal backup solution

**Suitable for**
- Amounts above your monthly salary, but less than half your annual salary

<br>

#### Level 3
## Single backup with discovery protection
The previous offline backups have one flaw in common - if discovered by a bad actor, your funds can be stolen.

To protect against this *theft on discovery* risk, a *pass-phrase* can be added to the recovery-phrase. This pass-phrase is sometimes called an extra word, or the 13th/25th word.

While this level provides more protection, it also adds complexity to your backup setup. For most beginners storing small amounts it might not be worth the effort from the start and can be a later consideration should the funds grow.

Technically, all recovery-phrases have a pass-phrase. If it's not set by the user, an empty string (“”) will be used by default. This means that using the recovery-phrase with or without the user-defined pass-phrase will recover two DIFFERENT wallets.

If a bad actor discovers only the recovery-phrase, they will find an empty wallet. Alternatively, one can deliberately leave a small amount of bitcoin in this wallet as a honey-pot, and monitor it for any withdrawals to know if it has been discovered.

To provide protection against *theft on discovery*, the pass-phrase should be stored separate from the recovery-phrase.

Since adding a pass-phrase will generate a different wallet, it is best to add it when first creating the wallet, and before storing any bitcoin in its addresses.

It's worth noting that most hardware wallets support pass-phrases, while most software wallet applications do not.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg"
alt-text = "Offline backup with discovery protection"
width = 800
height = 420
%}


**Do**
- Use a secure pass-phrase, it is case sensitive and can include numbers and special characters
- Have redundant and secure backups of both the recovery-phrase and the pass-phrase, they are equally important for successful wallet recovery
- Understand you now have two distinct wallets, (one each from the recovery-phrase with or without the pass-phrase), this can be useful to fool a bad actor, or a risk if next-of-kin is unaware of the pass-phrase

**Don’t**
- Store the recovery-phrase and pass-phrase together
- Forget to document your setup for next-of-kin

**Suitable for**
- Large amounts
- Situations where the backup can be discovered by bad actors

**Alternative**

Set up a hardware wallet from the recovery and pass-phrase that uses a PIN to protect usage. The PIN now becomes the protection against theft on discovery and should be saved somewhere safe just like the pass-phrase.

<br>

#### Level 4
## Multiple backups with discovery protection
One remaining flaw with the single offline backup levels is that severe damage to the one location where they are stored, could lead to the backup not being usable. This could be a fire, flood, earthquake or similar, all more or less likely depending on where you live.

To protect against such a *catastrophic event* we can create multiple backups, and distribute them to other locations. This could be a second home, trusted family and friends or a safe deposit box.

As the risk of discovery increases with the multiplying backups, it's best to maintain the protection against theft on discovery with a pass-phrase, or hardware wallets with a PIN.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg"
alt-text = "Multiple offline backups with discovery protection"
width = 800
height = 420
%}

**Do**
- Make sure you have reduntant copies of all parts of the backup in several locations
- Document your setup well for next-of-kin now that complexity has increased

**Don’t**
- Forget to safely store the pass-phrases or PINs

**Suitable for**
- Large amounts
- In locations where catastrophic events are common, or likely to cause severe damage

<br>

---

## Inheritance instructions
For any backup setup, sufficient information and understandable instructions for recovering the wallet should be available to next-of-kin.

Even though it might feel uncomfortable (or unnecessary if you are young and single), it is never too early to document your wallets. If you don’t, there is a very high chance that next-of-kin will not be able to inherit your funds.

At a minimum, document each wallet with a given name (Bob’s Bitcoin wallet 1), how to recover it, when it was created and what application was used to create the wallet. Ideally this document has all the instructions required to recover the wallet, but not the information itself (*recovery-phrase*, *pass-phrase* etc.), as that might expose you to theft on discovery risks.

**Do**
- Make next-of-kin aware of the existence of any wallets
- Explain clearly how to recover the setup, and how to access the required information


**Don’t**
- Store any required information ONLY in locations that will not be accessible to next-of-kin (password managers, single user accounts etc.)


**Suitable for**
- Any amount
6 changes: 6 additions & 0 deletions guide/private-key-management/introduction.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -55,4 +55,10 @@ An introduction to some of the common private key management schemes for shared

---

### [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }})

A straightforward guide to safe manual backups.

---

Start at the top with [private key schemes]({{ '/guide/private-key-management/schemes/' | relative_url }}).
2 changes: 1 addition & 1 deletion guide/private-key-management/multi-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -87,4 +87,4 @@ Few tailor-made products exist for shared wallets, but any wallet application th

---

OK, let's have a look at some [case studies]({{ '/guide/case-studies/' | relative_url }}).
OK, to end this chapter let's have a look at how to do safe [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }}).
4 changes: 2 additions & 2 deletions guide/private-key-management/single-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -132,9 +132,9 @@ This scheme is suitable for users who are already familiar with bitcoin and proc
### How it works
The wallet application will generate a 12 or 24 word phrase (seed / [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }})) from which all the wallet’s [keys]({{ '/guide/glossary/#keys' | relative_url }}) can be derived. This means the user can have access to the wallet from any compatible wallet application with the phrase, even if they lose the device or software.

This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the op-sec burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase. You need to take resistance to physical theft, fire and other destructive events into account. To get the best security out of recovery phrases they should be kept on several dedicated [metal storage pieces](https://jlopp.github.io/metal-bitcoin-storage-reviews/) in secure places offline. A fair amount of effort and knowledge is required for this.
This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase.

A full guide to manual backup best practices for users is out of scope for this chapter but the [Do's and Dont's](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) of Bitcoin key management is a good starting point.
Safe backups can be made fairly simple, take a look at our [Bitcoin backups](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) guide as good starting point.

{% include fact/pros.html %}

Expand Down
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); Bitcoin backups page - replaces #210 by danielnordh · Pull Request #305 · BitcoinDesign/Guide · GitHub
Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions _compress_images_cache.yml
Original file line numberDiff line numberDiff line change
Expand Up@@ -655,3 +655,20 @@ assets/images/guide/getting-started/usage-life-cycle/dropoff@2x.png: dropoff@2x.
assets/images/guide/payments/send/bitcoin-payments@2x.jpg: bitcoin-payments@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-mobile@2x.jpg: bitcoin-payments-mobile@2x.jpg
assets/images/guide/payments/send/bitcoin-payments-social.jpg: bitcoin-payments-social.jpg
assets/images/guide/private-key-management/backups/backups-mobile.jpg: backups-mobile.jpg
assets/images/guide/private-key-management/backups/backup-table.png: backup-table.png
assets/images/guide/private-key-management/backups/backups.jpg: backups.jpg
assets/images/guide/private-key-management/backups/page-backups.jpg: page-backups.jpg
assets/images/guide/private-key-management/backups/backups@2x.jpg: backups@2x.jpg
assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg: backups-mobile@2x.jpg
assets/images/guide/private-key-management/backups/backup-table@2x.png: backup-table@2x.png
assets/images/guide/private-key-management/backups/paperbackup@2x.jpg: paperbackup@2x.jpg
assets/images/guide/private-key-management/backups/metalbackup.jpg: metalbackup.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg: offline-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/metalbackup@2x.jpg: metalbackup@2x.jpg
assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg: cloud-backup@2x.jpg
assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg: offline-discoveryprotection@2x.jpg
assets/images/guide/private-key-management/backups/paperbackup.jpg: paperbackup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg: multiple-discoveryprotection.jpg
assets/images/guide/private-key-management/backups/cloud-backup.jpg: cloud-backup.jpg
assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg: multiple-discoveryprotection@2x.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
267 changes: 267 additions & 0 deletions guide/private-key-management/backups.md
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,267 @@
---
layout: guide
title: Bitcoin backups
description: A beginner's guide to Bitcoin backups.
nav_order: 4
parent: Private key management
permalink: /guide/private-key-management/backups/
main_classes: -no-top-padding
image: https://bitcoin.design/assets/images/guide/private-key-management/backups/page-backups.jpg
Comment thread
danielnordh marked this conversation as resolved.
---

<!--

Editor's notes

A guide meant to lower the barrier for first time users of self-custody wallets.

Illustration sources

//

-->

{% include picture.html
image = "/assets/images/guide/private-key-management/backups/backups.jpg"
retina = "/assets/images/guide/private-key-management/backups/backups@2x.jpg"
mobile = "/assets/images/guide/private-key-management/backups/backups-mobile.jpg"
mobileRetina = "/assets/images/guide/private-key-management/backups/backups-mobile@2x.jpg"
alt-text = "Several devices exchanging data"
width = 1600
height = 700
layout = "full-width"
%}

# Bitcoin backups

The self-custody of Bitcoin is an important right, but also a financial responsibility that can scale from pocket money to life savings, and take practice getting used to.

This guide is a straightforward starting point for simple Bitcoin backups, aimed at users of Bitcoin products.

If you are a designer or developer, make sure you offer guidance to your users so they can secure their bitcoin with an appropriate backup.


## What are backups?

When we talk about backups, we mean saving the information needed to restore access to a wallet outside of the application that created the private keys. Often, this will just be the [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }}) of 12 or 24 words, but can also include other information like a *pass-phrase* and [derivation path]({{ '/guide/glossary/#derivation-path' | relative_url }}).
Comment thread
danielnordh marked this conversation as resolved.

The main risks that backups need to protect against are:

- Loss of wallet - you lost the device and application holding the private key
- Remote theft - your backup got discovered online by a bad actor
- Physical damage - your backup got destroyed
- Theft on discovery - your backup got discovered in person by a bad actor
- Catastrophic events - your backup location got destroyed
- Inheritance loss - next-of-kin were unable to access your wallet


## Backup levels, basic to advanced

A basic backup can be done in a few minutes, while more advanced setups can require more time and effort, like the purchase of dedicated material.

Let’s look at some real life examples of backup methods for single-key wallets and what they protect against.

<br>

{% include image.html
image = "/assets/images/guide/private-key-management/backups/backup-table.png"
retina = "/assets/images/guide/private-key-management/backups/backup-table@2x.png"
alt-text = "Table of backup levels"
width = 904
height = 625
layout = "full-width"
%}

{% include tip/recommendation.html %}

Level 0 and 1 are good when getting started, and require very little effort.

Level 2, 3 or 4 are recommended for storing larger amounts.

{% include tip/close.html %}

<br>

#### Level 0
## Encrypted cloud backup

By storing the recovery-phrase in an online location that is encrypted (not in plain text) and hard to access by anyone other than yourself, you are protected against *loss of wallet*. This is the absolute minimum you should do and only takes a few minutes.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/cloud-backup.jpg"
retina = "/assets/images/guide/private-key-management/backups/cloud-backup@2x.jpg"
alt-text = "Encrypted cloud backup"
Comment thread
danielnordh marked this conversation as resolved.
width = 800
height = 420
%}

**Do**
- Use an encrypted password manager like 1Password, LastPass, iCloud Keychain
- Alternatively, use a wallet application with automatic cloud backup

**Don’t**
- Screenshot the recovery-phrase and save it in Google Photos, iCloud photos
- Write down the recovery-phrase in plain text on your device, Google Docs etc.

**Suitable for**
- For small amounts (less than a months salary)
- When you can't wait to set up a new wallet until you are at home

<br>

#### Level 1
## Single paper backup

By storing the recovery-phrase written down on paper in your own home you have protected against *loss of wallet* and *remote theft*.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/paperbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/paperbackup@2x.jpg"
alt-text = "24 word paper backup"
width = 800
height = 508
%}


**Do**
- Write the recovery-phrase with the words numbered, using permanent ink on card
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Scribble the recovery-phrase on a scrap of paper using a pencil
- Stick it on the fridge, or other visible locations

**Suitable**
- For small amounts (less than a months salary)
- When you are setting up a new wallet at home

<br>

#### Level 2
## Single metal backup

By storing the recovery-phrase on metal in your own home you have protected against *loss of wallet*, *remote theft* and *physical damage*.

The best metal backup solutions are resistant to most physical damage, including fire, acid and high pressure.


{% include image.html
image = "/assets/images/guide/private-key-management/backups/metalbackup.jpg"
retina = "/assets/images/guide/private-key-management/backups/metalbackup@2x.jpg"
alt-text = "Metal backup"
width = 800
height = 440
%}


**Do**
- Order a dedicated metal backup product, recommendations can be found [here](https://jlopp.github.io/metal-bitcoin-storage-reviews/)
- Follow the instructions and make sure the phrase is indented, etched, engraved or set properly
- Store it in a location where it is unlikely to be found by a bad actor
- Document or tell next-of-kin where the backup can be found

**Don’t**
- Skip ordering a dedicated product, invent your own metal backup solution

**Suitable for**
- Amounts above your monthly salary, but less than half your annual salary

<br>

#### Level 3
## Single backup with discovery protection
The previous offline backups have one flaw in common - if discovered by a bad actor, your funds can be stolen.

To protect against this *theft on discovery* risk, a *pass-phrase* can be added to the recovery-phrase. This pass-phrase is sometimes called an extra word, or the 13th/25th word.

While this level provides more protection, it also adds complexity to your backup setup. For most beginners storing small amounts it might not be worth the effort from the start and can be a later consideration should the funds grow.

Technically, all recovery-phrases have a pass-phrase. If it's not set by the user, an empty string (“”) will be used by default. This means that using the recovery-phrase with or without the user-defined pass-phrase will recover two DIFFERENT wallets.

If a bad actor discovers only the recovery-phrase, they will find an empty wallet. Alternatively, one can deliberately leave a small amount of bitcoin in this wallet as a honey-pot, and monitor it for any withdrawals to know if it has been discovered.

To provide protection against *theft on discovery*, the pass-phrase should be stored separate from the recovery-phrase.

Since adding a pass-phrase will generate a different wallet, it is best to add it when first creating the wallet, and before storing any bitcoin in its addresses.

It's worth noting that most hardware wallets support pass-phrases, while most software wallet applications do not.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/offline-discoveryprotection@2x.jpg"
alt-text = "Offline backup with discovery protection"
width = 800
height = 420
%}


**Do**
- Use a secure pass-phrase, it is case sensitive and can include numbers and special characters
- Have redundant and secure backups of both the recovery-phrase and the pass-phrase, they are equally important for successful wallet recovery
- Understand you now have two distinct wallets, (one each from the recovery-phrase with or without the pass-phrase), this can be useful to fool a bad actor, or a risk if next-of-kin is unaware of the pass-phrase

**Don’t**
- Store the recovery-phrase and pass-phrase together
- Forget to document your setup for next-of-kin

**Suitable for**
- Large amounts
- Situations where the backup can be discovered by bad actors

**Alternative**

Set up a hardware wallet from the recovery and pass-phrase that uses a PIN to protect usage. The PIN now becomes the protection against theft on discovery and should be saved somewhere safe just like the pass-phrase.

<br>

#### Level 4
## Multiple backups with discovery protection
One remaining flaw with the single offline backup levels is that severe damage to the one location where they are stored, could lead to the backup not being usable. This could be a fire, flood, earthquake or similar, all more or less likely depending on where you live.

To protect against such a *catastrophic event* we can create multiple backups, and distribute them to other locations. This could be a second home, trusted family and friends or a safe deposit box.

As the risk of discovery increases with the multiplying backups, it's best to maintain the protection against theft on discovery with a pass-phrase, or hardware wallets with a PIN.

{% include image.html
image = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection.jpg"
retina = "/assets/images/guide/private-key-management/backups/multiple-discoveryprotection@2x.jpg"
alt-text = "Multiple offline backups with discovery protection"
width = 800
height = 420
%}

**Do**
- Make sure you have reduntant copies of all parts of the backup in several locations
- Document your setup well for next-of-kin now that complexity has increased

**Don’t**
- Forget to safely store the pass-phrases or PINs

**Suitable for**
- Large amounts
- In locations where catastrophic events are common, or likely to cause severe damage

<br>

---

## Inheritance instructions
For any backup setup, sufficient information and understandable instructions for recovering the wallet should be available to next-of-kin.

Even though it might feel uncomfortable (or unnecessary if you are young and single), it is never too early to document your wallets. If you don’t, there is a very high chance that next-of-kin will not be able to inherit your funds.

At a minimum, document each wallet with a given name (Bob’s Bitcoin wallet 1), how to recover it, when it was created and what application was used to create the wallet. Ideally this document has all the instructions required to recover the wallet, but not the information itself (*recovery-phrase*, *pass-phrase* etc.), as that might expose you to theft on discovery risks.

**Do**
- Make next-of-kin aware of the existence of any wallets
- Explain clearly how to recover the setup, and how to access the required information


**Don’t**
- Store any required information ONLY in locations that will not be accessible to next-of-kin (password managers, single user accounts etc.)


**Suitable for**
- Any amount
6 changes: 6 additions & 0 deletions guide/private-key-management/introduction.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -55,4 +55,10 @@ An introduction to some of the common private key management schemes for shared

---

### [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }})

A straightforward guide to safe manual backups.

---

Start at the top with [private key schemes]({{ '/guide/private-key-management/schemes/' | relative_url }}).
2 changes: 1 addition & 1 deletion guide/private-key-management/multi-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -87,4 +87,4 @@ Few tailor-made products exist for shared wallets, but any wallet application th

---

OK, let's have a look at some [case studies]({{ '/guide/case-studies/' | relative_url }}).
OK, to end this chapter let's have a look at how to do safe [Bitcoin backups]({{ '/guide/private-key-management/backups/' | relative_url }}).
4 changes: 2 additions & 2 deletions guide/private-key-management/single-user-schemes.md
Original file line numberDiff line numberDiff line change
Expand Up@@ -132,9 +132,9 @@ This scheme is suitable for users who are already familiar with bitcoin and proc
### How it works
The wallet application will generate a 12 or 24 word phrase (seed / [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }})) from which all the wallet’s [keys]({{ '/guide/glossary/#keys' | relative_url }}) can be derived. This means the user can have access to the wallet from any compatible wallet application with the phrase, even if they lose the device or software.

This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the op-sec burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase. You need to take resistance to physical theft, fire and other destructive events into account. To get the best security out of recovery phrases they should be kept on several dedicated [metal storage pieces](https://jlopp.github.io/metal-bitcoin-storage-reviews/) in secure places offline. A fair amount of effort and knowledge is required for this.
This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase.

A full guide to manual backup best practices for users is out of scope for this chapter but the [Do's and Dont's](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) of Bitcoin key management is a good starting point.
Safe backups can be made fairly simple, take a look at our [Bitcoin backups](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/) guide as good starting point.

{% include fact/pros.html %}

Expand Down