Skip to content
Closed
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
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.
54 changes: 30 additions & 24 deletions guide/daily-spending-wallet/backup-and-recovery/cloud-backup.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,35 +37,37 @@ layout = "full-width"

# Automatic cloud backup

### How it works
> Crypto rookies perceive themselves as “incapable of self-managing keys”.
>
> <cite>As researched by <a href="https://informationsecurity.uibk.ac.at/pdfs/ECIS21_Non-Adoption_of_Crypto-Assets.pdf">Abramova et al</a></cite>

The user's wallet recovery data and channel states are backed up on their respective cloud storage provider. The [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }}) only needs to be backed up once. However, channel states may need to be backed up frequently because they change every time the user's wallet sends, receives, or routes a payment; therefore, the channel state should be backed up automatically.
## How it works

If the user's device is lost, stolen, or broken, they can use the backup from their cloud storage account (such as Apple iCloud or Google Drive) to regain access to their funds. To learn more about the technical details, hop over to the [private key management]({{ '/guide/private-key-management/introduction' | relative_url }}) section on this topic.
The user's wallet recovery data and channel states are backed up on their respective cloud storage provider. The [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }}) only needs to be backed up once. However, channel states may need to be backed up frequently because they change every time the user’s wallet sends, receives, or routes a payment; therefore, the channel state should be backed up automatically.

> Crypto rookies perceive themselves as “incapable of self-managing keys”.
>
> <cite>As researched by <a href="https://voskart.de/pdf/u_in_crypto.pdf">Abramova et al</a></cite>
If the user's device is lost, stolen, or broken, they can use the backup from their cloud storage account (such as Apple iCloud or Google Drive) to regain access to their funds. To learn more about the technical details, hop over to the [private key management]({{ '/guide/private-key-management/introduction' | relative_url }}) section on this topic.

This method provides users with the feeling that they can rely on their cloud provider to regain access to their funds rather than putting the responsibility on themselves.
This method provides users with the feeling that they can rely on their cloud provider to regain access to their funds rather than putting the responsibility entirely on themselves. It also significantly reduces friction during onboarding.

Below is an example of what the user interface might look like for an automatic cloud backup that significantly reduces friction during onboarding. An optimal phase to show this may be after the wallet has received funds for the first time, so that the user has an incentive to back up their wallet.
Below is what this wallet's automatic cloud backup user interface looks like.

<div class="image-slide-gallery">

{% include picture.html
image = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-prompt.png"
retina = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-prompt@2x.png"
layout = "shadow"
caption = "Prompt the user to back up when they have funds in the wallet"
alt-text = "Screen prompting the user to back up after they have received a payment"
width = 250
height = 541
image = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-prompt.png"
retina = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-prompt@2x.png"
modalImage = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-prompt@2x.png"
layout = "shadow"
caption = "Prompt the user to back up when they have funds in the wallet"
alt-text = "Screen prompting the user to back up after they have received a payment"
width = 250
height = 541
%}

{% include picture.html
image = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-intro.png"
retina = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-intro@2x.png"
modalImage="/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-intro@2x.png"
layout = "shadow"
caption = "Describe to the user know what is about to happen and how it works."
alt-text = "Screen explaining automatic cloud backups"
Expand All @@ -74,8 +76,9 @@ height = 541
%}

{% include picture.html
image = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-PIN.png"
image = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-PIN.png"
retina = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-PIN@2x.png"
modalImage="/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-PIN@2x.png"
layout = "shadow"
caption = "Allows the user to set a PIN used for authentication."
alt-text = "The user can set a PIN which will be used to authenticate and access the wallet"
Expand All @@ -84,8 +87,9 @@ height = 541
%}

{% include picture.html
image = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-service.png"
image = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-service.png"
retina = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-service@2x.png"
modalImage="/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-service@2x.png"
layout = "shadow"
caption = "Give the user different cloud provider options, others such as Dropbox might also be included."
alt-text = "Screen showing saving a password to encrypt the recovery phrase"
Expand All @@ -96,6 +100,7 @@ height = 541
{% include picture.html
image = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-provider.png"
retina = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-provider@2x.png"
modalImage="/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-provider@2x.png"
layout = "shadow"
caption = "This UI will be very different depending on the cloud provider and what permissions are required."
alt-text = "Screen of placeholder where cloud provider UI would be"
Expand All @@ -106,6 +111,7 @@ height = 541
{% include picture.html
image = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-confirmation.png"
retina = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-confirmation@2x.png"
modalImage="/assets/images/guide/daily-spending-wallet/backup-and-recovery/automatic-cloud-backup/cloud-backup-confirmation@2x.png"
layout = "shadow"
caption = "Once the upload is complete it's a good idea to show a success screen and give some reassurances."
alt-text = "Screen showing completing a cloud backup"
Expand All @@ -115,15 +121,15 @@ height = 541

</div>

### How to discuss/explain it
### How to explain it

One approach is to explicitly explain within onboarding carousels that a user’s wallet backup is stored on the cloud; this means that if they lose or break their device, they can regain access to their funds on another device using their respective cloud account and bitcoin wallet app.
This wallet prompts the user to backup as soon as they have received funds in their wallet for the first time. This is a great time to remind the user because they now have a financial incentive to backup this wallet. Many users may skip the backup during their [first use]({{'/guide/daily-spending-wallet/first-use/' | relative_url}}). This is fine, as they may simply want to try out the wallet and see if it has the features they want before fully committing to using it. But in the event they do skip the backup, it's important to remind them about the backup later, especially once it contains funds.

On a similar note, it’s crucial that you also explain that if someone else knows their cloud account information, they can gain access to their funds, too.
The wallet explains to the user that their backup is stored on the cloud, and that they can regain access to their funds on another device using their respective cloud account and bitcoin wallet app. The app also explains that if somebody else gains access to your cloud account information, they can also gain access to your funds.

{% include tip/open.html color="green" icon="check" label="Do: Inform your Users" %}

Before creating a wallet backup via cloud backup, make sure the user knows what they are about to do. Once the backup is complete, provide a summary and some reassurances before moving on. This is a good place for loading interactions and animation because there will likely be a few seconds between when a user clicks to upload to the cloud provider and when it completes.
Before creating a wallet backup via cloud backup, make sure the user knows what they are about to do. Once the backup is complete, provide a summary and some reassurances before moving on. Let them know where in their cloud storage they can find their backup. This is a good place for loading interactions and animation because there will likely be a few seconds between when a user clicks to upload to the cloud provider and when it completes.

{% include tip/close.html %}

Expand All @@ -133,15 +139,15 @@ By not making users manually backup, you decrease the risk of self-inflicted los

While this is an easier way for users to set up a wallet, it brings in the potential threat of malicious third-party access. If a user's cloud account is hacked, their funds could be compromised. This can be mitigated by encrypting the wallet recovery data before sending it to the cloud provider. However, the user could still lose access to funds if they forget their cloud login information or the cloud provider blocks their access.

By bringing cloud storage providers into the equation, we assume that users trust their providers. This also raises the question of [decentralization]({{ 'guide/getting-started/principles/#decentralization' | relative_url }}): a guiding principle of the bitcoin space and could be considered in conflict with the popular saying, “not your keys, not your coins”.
By bringing cloud storage providers into the equation, we assume that users trust their providers. This also raises the question of [decentralization]({{ 'guide/getting-started/principles/#decentralization' | relative_url }}), a guiding principle of the bitcoin space, and could be considered in conflict with the popular saying, “not your keys, not your coins.”

{% include tip/open.html color="red" icon="forbid" label="Don’t: Use for High Value Amounts" %}

Automatic cloud backups should not be considered for products with users that are storing high-value amounts. This is because there are potentially more security threat vectors.
Automatic cloud backups should not be considered for products with users that are storing high-value amounts. This is because there are potentially more security threat vectors. Instead, consider a [manual backup]({{'/guide/daily-spending-wallet/backup-and-recovery/manual-backup/' | relative_url}}) or using a multi-sig solution like the [Savings wallet]({{'/guide/savings-wallet/' | relative_url}}).

{% include tip/close.html %}

To grant users some ownership of their wallet data, you can create an optional manual backup within the settings menu. A great way to do this is by framing it as an extra layer of security or a good alternative in case the user loses access to their cloud account, or feels uncomfortable trusting their cloud provider.
To grant users some ownership of their wallet data, you can create an optional manual backup within the settings menu. A great way to do this is by framing it as an extra layer of security or a good alternative in case the user loses access to their cloud account or feels uncomfortable trusting their cloud provider.

---

Expand Down
11 changes: 5 additions & 6 deletions guide/daily-spending-wallet/backup-and-recovery/landing-page.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ Illustration sources

When a user generates and [funds]({{ '/guide/daily-spending-wallet/funding/' | relative_url }}) a new daily spending wallet, they will then need to create a backup of their wallet in order to ensure their bitcoin are not lost.

Two main types of information need to be backed up: the user's wallet recovery data and their Lightning channel state. While the wallet recovery data may be used to restore the wallet using another wallet application, the channel state is typically only restorable within the same application.
Three main types of information need to be backed up: the user's wallet recovery data, their Lightning channel state, and any other user metadata. While the wallet recovery data may be used to restore the wallet using another wallet application, the channel state is typically only restorable within the same application. Similarly, most user metadata can only be restored within the wallet in which it was created since there is not an industry-standard format for such data.

{% include picture.html
image = "/assets/images/guide/daily-spending-wallet/backup-and-recovery/wallet-backup.png"
Expand All @@ -58,16 +58,15 @@ Two main types of information need to be backed up: the user's wallet recovery d
- A _Fingerprint_ allows for verification that the wallet was reconstructed correctly after import
- _Static channel backups_ contain all basic information about active Lightning channels
- A _Channels database_ contains data on payments made in active Lightning channels
- _[Activity]({{'/guide/daily-spending-wallet/activity/' | relative_url }})_ includes transaction memos, categories, tags, or any other metadata that helps the user keep track of their transaction history
- _[Contacts]({{'/guide/daily-spending-wallet/activity/' | relative_url }})_ includes any metadata that helps to abstract transaction endpoints into a contacts list for the user.

Users who lose both their wallet access and their backup permanently lose their bitcoin. Arguably, this creates one of the most challenging design problems within the space.

Backups could be handled automatically by the software, manually by the user, or a mix of these two methods. Regardless of the type of scheme you decide to go with, it’s crucial to be explicit about how your product handles backups and private key management.

{% include tip/recommendation.html %}

We recommend that the optimal phase to hint the user to perform the backup should be after the wallet has received funds for the first time. This way, we avoid overwhelming the user with an unnecessary task, as it makes more sense to backup a wallet with funds on it.

{% include tip/close.html %}
This daily spending wallet reference design encourages the user to configure an automatic cloud backup for their recovery phrase and lightning channel state. It also provides manual backup as a fallback.
This wallet signals to the user to perform the backup immediately after they receive funds for the first time. This way, we avoid overwhelming the user with an unnecessary task, as it makes more sense to backup a wallet with funds on it.

Recent [studies](https://dl.acm.org/doi/fullHtml/10.1145/3411764.3445679) show users are often confused or unaware of where their private keys are being stored, ultimately causing inadequate risk assessment and poor storage behavior. This risk of user negligence may be avoided with transparent messaging around the scheme your wallet is using.

Expand Down