You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: guide/designing-products/principles.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,7 +102,7 @@ layout="float-left"
102
102
103
103
Self-custody often leaves the end-user responsible for the security of their private keys. They can only do a good job of that if we provide them with appropriate tools and awareness of best practices.
104
104
105
-
Security is especially important when onboarding people who are new to Bitcoin. For example, new users are likely to start by only storing small amounts. After a while, they may become more comfortable with the idea of self-custody and begin to store larger amounts. The concept of progressive security is a good idea here, starting with [automatic cloud backups]({{'/guide/onboarding/backing-up-a-recovery-phrase/automatic-cloud-backup/' | relative_url}}). This would let a user upgrade their security and private key management scheme as their savings grow. Although common, recovery phrases that require [manual backup]({{'/guide/onboarding/backing-up-a-recovery-phrase/manual-backup/' | relative_url}}) might backfire for new users not yet familiar with safe backup practices.
105
+
Security is especially important when onboarding people who are new to Bitcoin. For example, new users are likely to start by only storing small amounts. After a while, they may become more comfortable with the idea of self-custody and begin to store larger amounts. The concept of progressive security is a good idea here, starting with [automatic cloud backups]({{'/guide/onboarding/backing-up-a-wallet/cloud-backup/' | relative_url}}). This would let a user upgrade their security and private key management scheme as their savings grow. Although common, recovery phrases that require [manual backup]({{'/guide/onboarding/backing-up-a-wallet/manual-backup/' | relative_url}}) might backfire for new users not yet familiar with safe backup practices.
106
106
107
107
Education and awareness are a big part of security, as they can protect users from bad actors and potentially their own security mistakes. It is unrealistic to expect beginners to take in all the knowledge acquired by advanced users in one go, for example, while [onboarding]({{ '/guide/onboarding/introduction/' | relative_url }}) to a Bitcoin product. We should therefore consider how to continuously educate and level up user awareness of best practices and risks.
@@ -73,11 +73,11 @@ However, there may be times when it is necessary to use a manual backup alternat
73
73
74
74
---
75
75
76
-
The next sections will look at some UI considerations for [cloud backups]({{ '/guide/onboarding/backing-up-a-recovery-phrase/automatic-cloud-backup' | relative_url }}) and [manual backups]({{ 'guide/onboarding/backing-up-a-recovery-phrase/manual-backup/' | relative_url }}).
76
+
The next sections will look at some UI considerations for [cloud backups]({{ '/guide/onboarding/backing-up-a-wallet/cloud-backup' | relative_url }}) and [manual backups]({{ 'guide/onboarding/backing-up-a-wallet/manual-backup/' | relative_url }}).
@@ -142,11 +142,11 @@ To grant users some ownership of their wallet data, you can create an optional m
142
142
143
143
---
144
144
145
-
In the next section we will show different methods for [manual backups]({{ '/guide/onboarding/backing-up-a-recovery-phrase/manual-backup/' | relative_url }}).
145
+
In the next section we will show different methods for [manual backups]({{ '/guide/onboarding/backing-up-a-wallet/manual-backup/' | relative_url }}).
Copy file name to clipboardExpand all lines: guide/onboarding/first-use.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ There are a number of common tasks a user might want to achieve the first time t
28
28
29
29
-[Create a new wallet](/guide/onboarding/first-use/#creating-a-wallet), or
30
30
-[Restore an existing wallet](/guide/onboarding/restoring-a-wallet/)
31
-
-[Backup a wallet](/guide/onboarding/backing-up-a-recovery-phrase/)
31
+
-[Backup a wallet](/guide/onboarding/backing-up-a-wallet/)
32
32
-[Fund a wallet](/guide/onboarding/funding-a-wallet/)
33
33
34
34
While the first two, creating or restoring a wallet, normally need to be tackled straight away, the last two can be designed to fit the flow and capability of your application.
@@ -39,9 +39,9 @@ Alternative approaches can be to wait and prompt the user only once there are fu
39
39
40
40
### Creating a wallet
41
41
42
-
[Bitcoin wallets]({{ 'guide/glossary/#wallet' | relative_url }}) contain the private keys to a user’s bitcoin. Private keys let users access bitcoin associated with those keys. If the user does not have a Bitcoin wallet already that they want to restore, it is necessary to create a new one.
42
+
[Bitcoin wallets]({{ 'guide/glossary/#wallet' | relative_url }}) contain the private keys to a user’s bitcoin. Private keys let users access bitcoin associated with those keys. If the user does not have a Bitcoin wallet already that they want to restore, it is necessary to create a new one.
43
43
44
-
Like regular keys on a keychain, Bitcoin private keys can be copied. This makes [private key management]({{ '/guide/private-key-management/introduction' | relative_url }}) one of the most important considerations of any bitcoin owner. Bitcoin wallet applications should automatically generate the user’s private keys locally, meaning they are only generated and stored on the device and not by the wallet provider, during onboarding.
44
+
Like regular keys on a keychain, Bitcoin private keys can be copied. This makes [private key management]({{ '/guide/private-key-management/introduction' | relative_url }}) one of the most important considerations of any bitcoin owner. Bitcoin wallet applications should automatically generate the user’s private keys locally, meaning they are only generated and stored on the device and not by the wallet provider, during onboarding.
45
45
46
46
<divclass="center"markdown="1">
47
47
@@ -115,11 +115,11 @@ Below is an example of some carousel screens that might be useful in helping a u
115
115
116
116
---
117
117
118
-
Ok, now let's look at [backing up a recovery phrase.]({{ '/guide/onboarding/backing-up-a-recovery-phrase/' | relative_url }})
118
+
Ok, now let's look at [backing up a recovery phrase.]({{ '/guide/onboarding/backing-up-a-wallet/' | relative_url }})
Copy file name to clipboardExpand all lines: guide/onboarding/introduction.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,9 +49,9 @@ An overview of common tasks when using a wallet application for the first time.
49
49
50
50
---
51
51
52
-
### [Backing up a recovery phrase]({{ 'guide/onboarding/backing-up-a-recovery-phrase' | relative_url }})
52
+
### [Backing up a wallet]({{ 'guide/onboarding/backing-up-a-wallet' | relative_url }})
53
53
54
-
An overview of the tradeoffs between using [manual backup]({{ 'guide/onboarding/backing-up-a-recovery-phrase/manual-backup' | relative_url }}) vs [automatic cloud backup]({{ 'guide/onboarding/backing-up-a-recovery-phrase/automatic-cloud-backup' | relative_url }}).
54
+
An overview of the tradeoffs between using [manual backup]({{ 'guide/onboarding/backing-up-a-wallet/manual-backup' | relative_url }}) vs [automatic cloud backup]({{ 'guide/onboarding/backing-up-a-wallet/cloud-backup' | relative_url }}).
There are several reasons why a user might need to restore their Bitcoin wallet. They may have lost their device, be migrating from a different application or have deleted their wallet application. Regardless of why, it’s important that your wallet application has an easy way for users to recover their funds.
27
+
There are several reasons why a user might need to restore their Bitcoin wallet. They may have lost their device, be migrating from a different application or have deleted their wallet application. Regardless of why, it’s important that your wallet application has an easy way for users to recover their funds.
28
28
29
-
However, not all wallets from one application can be recovered in another, depending on what standards they support, as covered in the [wallet interoperability]({{ 'guide/designing-products/wallet-interoperability' | relative_url }}) section. Lack of interoperability and vendor dependance is an issue for wallets holding bitcoin on the Lightning network. Lightning network wallets can currently only be restored in the application originally used. It's also worth noting that restoring from a recovery phrase only restores the private keys, but no user data like transaction notes, contacts etc.
29
+
However, not all wallets from one application can be recovered in another, depending on what standards they support, as covered in the [wallet interoperability]({{ 'guide/designing-products/wallet-interoperability' | relative_url }}) section. Lack of interoperability and vendor dependance is an issue for wallets holding bitcoin on the Lightning network. Lightning network wallets can currently only be restored in the application originally used. It's also worth noting that restoring from a recovery phrase only restores the private keys, but no user data like transaction notes, contacts etc.
@@ -42,23 +42,23 @@ However, not all wallets from one application can be recovered in another, depen
42
42
43
43
### Restore from an automatic cloud backup
44
44
45
-
As outlined earlier in the chapter, we consider an [automatic cloud backup](/guide/onboarding/backing-up-a-recovery-phrase/automatic-cloud-backup/) a good option, especially for beginners. One of the major UX benefits of this is a seamless recovery process. Assuming they are restoring in the same wallet application originally used, all the user needs to do to gain access to their funds again is to log in to their cloud storage account (typically iCloud or Google Drive).
45
+
As outlined earlier in the chapter, we consider an [automatic cloud backup](/guide/onboarding/backing-up-a-wallet/cloud-backup/) a good option, especially for beginners. One of the major UX benefits of this is a seamless recovery process. Assuming they are restoring in the same wallet application originally used, all the user needs to do to gain access to their funds again is to log in to their cloud storage account (typically iCloud or Google Drive).
46
46
47
47
### Restore manually with a recovery phrase
48
48
49
-
Users may have created a wallet with another wallet application. In this case, they should be able to import that wallet into yours by entering their 12 or 24-word recovery phrase. There are several options for the UI when entering a recovery phase, as outlined earlier in the [manual backup]({{ 'guide/onboarding/backing-up-a-recovery-phrase/manual-backup/' | relative_url }}) section of this chapter.
49
+
Users may have created a wallet with another wallet application. In this case, they should be able to import that wallet into yours by entering their 12 or 24-word recovery phrase. There are several options for the UI when entering a recovery phase, as outlined earlier in the [manual backup]({{ 'guide/onboarding/backing-up-a-wallet/manual-backup/' | relative_url }}) section of this chapter.
50
50
51
51
### Restore from an encrypted QR code backup
52
52
53
53
Some applications also provide an option for users to scan an encrypted proprietary QR code version of their recovery phrase. For a more detailed explanation of this recovery technique, check out this [blog post](https://blog.keys.casa/product-update-transaction-memos-encrypted-backups/) by Casa.
54
54
55
55
### Restore a wallet with funds on the Lightning network
56
56
57
-
To fully restore a wallet with funds on the [Lightning network](/guide/glossary/#lightning-network), the state and history of the payment channels are needed in addition to the recovery phrase. As there are no standards for this yet, wallet applications need to have their own format for backing this up, and subsequently restoring. Due to the amount of information, a QR code of the encrypted data, like in the previous example, can be appropriate.
57
+
To fully restore a wallet with funds on the [Lightning network](/guide/glossary/#lightning-network), the state and history of the payment channels are needed in addition to the recovery phrase. As there are no standards for this yet, wallet applications need to have their own format for backing this up, and subsequently restoring. Due to the amount of information, a QR code of the encrypted data, like in the previous example, can be appropriate.
58
58
59
59
{% include tip/recommendation.html %}
60
60
61
-
Be clear to users what you support and what wallet specifications they can expect to restore in your application. Most bitcoin products should support restoring from a recovery phrase at a minimum. Capability to restore an HD wallet implemented according to BIP32, 39, 43, 44, 49, 84 and 380 would be a good starting point.
61
+
Be clear to users what you support and what wallet specifications they can expect to restore in your application. Most bitcoin products should support restoring from a recovery phrase at a minimum. Capability to restore an HD wallet implemented according to BIP32, 39, 43, 44, 49, 84 and 380 would be a good starting point.
62
62
63
63
{% include tip/close.html %}
64
64
@@ -69,7 +69,7 @@ Some less popular methods for restoring a wallet include importing a file with a
69
69
The next section looks at options for adding extra layers of security and [protecting a wallet]({{ '/guide/onboarding/protecting-a-wallet/' | relative_url }}).
0 commit comments