From 6d547e4f005cccb8cf4b407526f074a81954d734 Mon Sep 17 00:00:00 2001 From: Daniel Nordh <3393669+danielnordh@users.noreply.github.com> Date: Thu, 14 Oct 2021 12:09:15 +0100 Subject: [PATCH 01/13] Add 'First use' intro, update 'Create a wallet' --- guide/onboarding/creating-a-new-wallet.md | 29 +++++++++++++++-------- 1 file changed, 19 insertions(+), 10 deletions(-) diff --git a/guide/onboarding/creating-a-new-wallet.md b/guide/onboarding/creating-a-new-wallet.md index 74731dd0e..8d0f81b31 100644 --- a/guide/onboarding/creating-a-new-wallet.md +++ b/guide/onboarding/creating-a-new-wallet.md @@ -20,17 +20,28 @@ image: https://bitcoin.design/assets/images/guide/onboarding/creating-a-new-wall layout = "full-width" %} -# Creating a new wallet +# First use -First, bitcoin [wallets]({{ 'guide/glossary/#wallet' | relative_url }}) are not analogous to their namesakes. Physical wallets are places to store physical currency, credit cards, IDs, and so on. Bitcoin wallets don't store bitcoin. However, the [self custodial]({{ 'guide/glossary/wallet/#non-custodial--custodial-wallet' | relative_url }}) nature of bitcoin wallets gives users full control of what they do with their bitcoin. +There are a number of common tasks a user might want to achieve the first time they open a wallet application: -Instead, a Bitcoin wallet contains the "private keys" to a users bitcoin. The bitcoin is located on the Bitcoin network that contains a public ledger similar in many ways to a spreadsheet with a record of everyone's transactions and balances. Private keys let users access bitcoin associated with those keys. A more suitable analogy for a Bitcoin wallet would be a keychain. +- [Create a new wallet](/guide/onboarding/creating-a-new-wallet/#creating-a-wallet), or +- [Restore an existing wallet](/guide/onboarding/restoring-a-wallet/) +- [Backup a wallet](/guide/onboarding/backing-up-a-recovery-phrase/) +- [Acquire bitcoin](/guide/onboarding/funding-a-wallet/) - Like regular keys on a keychain, Bitcoin private keys can be copied. For example, if you gave someone a copy of your house keys, they can unlock the door to your home. Likewise, if someone has a copy of your private key, they can access your bitcoin. This makes [private key management]({{ '/guide/private-key-management/introduction' | relative_url }}) one of the most important considerations of any bitcoin owner. +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. - Most bitcoin wallets will automatically generate users' private keys during onboarding, and is not usually something a user controls. We will look at practical design solutions for guiding users through this process in this chapter. This page explains how we can help get a user comfortable with the idea of a self-custodial wallet. +It is common to see onboarding flows that implores the user to do a manual backup of their recovery phrase straight away, often before they have even gotten to see the main screen of the application. While this can make sure the user is aware of the need to backup, their motivation and ability to safely do this at that exact moment might be limited. -A few different types of wallets let you send, receive, store, and manage bitcoin. For this page, we focus on regular single-key wallets, which are the ones most commonly used. +Alternative approaches can be to wait and prompt the user only once there are funds in the wallet, at regular intervals, or to use an automatic cloud backup for small amounts. This is all up to you as the application designer to decide what works best in your users’ use case. + +### Creating a wallet + +[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. + +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. + +Most Bitcoin wallet applications will automatically generate users’ private keys during onboarding.
@@ -44,11 +55,9 @@ A few different types of wallets let you send, receive, store, and manage bitcoi layout = "float-left-desktop -background -shadow" %} -Most wallets will begin the onboarding process by creating a new or restoring an existing wallet. New users to Bitcoin will usually be going through the flow of creating a new wallet. - -Once an individual selects “create a new wallet”, you might present informational carousels that provide a high-level overview of the implications, benefits, and responsibility that comes with having a self-custodial wallet. Here you can explain to your user that access to the wallet will not require collecting any sensitive information such as usernames and passwords, which is often the case with traditional financial products. +After the user selects “Create a new wallet”, you might present informational carousels that provide a high-level overview of the implications, benefits, and responsibility that comes with having a self-custodial wallet. Here you can explain to your user that access to the wallet will not require collecting any sensitive information such as usernames and passwords, which is often the case with traditional financial products. -Rather, the user can directly access their funds as long as they have access to the private key or recovery phrase. You should help your users understand that your team do not have the ability to recover their funds in the event they lose their private key. A self custodial wallet often means the user will have to take on greater responsibilty to safely protect their private key so they can always access their funds. +Rather, the user can directly access their funds as long as they have access to the private key or recovery phrase. You should help your users understand that your team does not have the ability to recover their funds in the event they lose their private key. A self custodial wallet often means the user will have to take on greater responsibility to safely protect their private key so they can always access their funds.
From 91fa35333cc513738f68ab12a5cd583c5646b8c4 Mon Sep 17 00:00:00 2001 From: Daniel Nordh <3393669+danielnordh@users.noreply.github.com> Date: Thu, 14 Oct 2021 12:10:08 +0100 Subject: [PATCH 02/13] Add Lightning paragraph --- guide/onboarding/creating-a-new-wallet.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/guide/onboarding/creating-a-new-wallet.md b/guide/onboarding/creating-a-new-wallet.md index 8d0f81b31..e2106a91b 100644 --- a/guide/onboarding/creating-a-new-wallet.md +++ b/guide/onboarding/creating-a-new-wallet.md @@ -70,6 +70,8 @@ Wallet creation during onboarding is an excellent opportunity to educate your us While this may sound daunting to first-time users, these caveats mustn't be hidden. Doing so may severely compromise their funds' safety, as their default assumptions and behaviors could potentially mimic how they typically use centralized applications (for example, feeling like it is OK if they forget their account information because they can contact customer support to help them recover it). +Ideally your application supports both the base layer and the Lightning network. When talking about backups, you should be clear on what is possible and required in terms of restoring the user’s wallet from a backup. + Some studies suggest that users struggled greatly with technical terminology and feeling as though they had a lack of guidance during wallet setup. By walking users through single steps that clearly frame the features of self-custody Bitcoin wallets, users will feel well-equipped to navigate and use the wallet confidently. > Users reported that they often felt like they lacked guidance and understanding during wallet setup From 33847585340d0a92f25ee27aa1e43b19e16e8f2a Mon Sep 17 00:00:00 2001 From: Daniel Nordh <3393669+danielnordh@users.noreply.github.com> Date: Thu, 14 Oct 2021 12:11:35 +0100 Subject: [PATCH 03/13] Minor readability tweaks --- guide/onboarding/creating-a-new-wallet.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guide/onboarding/creating-a-new-wallet.md b/guide/onboarding/creating-a-new-wallet.md index e2106a91b..7f7d905d2 100644 --- a/guide/onboarding/creating-a-new-wallet.md +++ b/guide/onboarding/creating-a-new-wallet.md @@ -78,7 +78,7 @@ Some studies suggest that users struggled greatly with technical terminology and > > As researched by Eskandari et al -Below is an example of some carousel screens that might be useful in helping a user understand what to expect from this wallet. For this example, we have opted to backup up the users' recovery phrase to a cloud provider but other alternatives exist. +Below is an example of some carousel screens that might be useful in helping a user understand what to expect from this wallet. For this example, we have opted to backup the users' recovery phrase to a cloud provider but other alternatives exist.
@@ -111,7 +111,7 @@ Below is an example of some carousel screens that might be useful in helping a u
- These screens explicitly lay out/guide users on the unique features of self-custodial wallets to make sure they understand these caveats. These screens suggest talking about ownership, explicitly stating the recovery mechanism that the respective wallet uses, and security measures that they should take to protect their wallet. + These screens explicitly lay out the unique features of self-custodial wallets to make sure the user understands these caveats. These screens suggest talking about ownership, explicitly stating the recovery mechanism that the respective wallet uses, and security measures that they should take to protect their wallet. --- From c4ec8ff33828b2cadeef3be04c07685bf66ac583 Mon Sep 17 00:00:00 2001 From: Daniel Nordh <3393669+danielnordh@users.noreply.github.com> Date: Thu, 14 Oct 2021 12:18:12 +0100 Subject: [PATCH 04/13] Update name of page, permalink and mentions on other pages --- guide/onboarding/backing-up-a-recovery-phrase.md | 4 ++-- guide/onboarding/creating-a-new-wallet.md | 8 ++++---- guide/onboarding/getting-to-know-your-users.md | 4 ++-- guide/onboarding/introduction.md | 4 ++-- 4 files changed, 10 insertions(+), 10 deletions(-) diff --git a/guide/onboarding/backing-up-a-recovery-phrase.md b/guide/onboarding/backing-up-a-recovery-phrase.md index 180da6710..da994f27e 100644 --- a/guide/onboarding/backing-up-a-recovery-phrase.md +++ b/guide/onboarding/backing-up-a-recovery-phrase.md @@ -75,8 +75,8 @@ However, there may be times when it is necessary to use a manual backup alternat The next sections will look at some UI considerations for [automatic 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 }}). {% include next-previous.html - previousUrl = "/guide/onboarding/creating-a-new-wallet/" - previousName = "Creating a new wallet" + previousUrl = "/guide/onboarding/first-use/" + previousName = "First use" nextUrl = "/guide/onboarding/backing-up-a-recovery-phrase/automatic-cloud-backup/" nextName = "Automatic cloud backups" %} diff --git a/guide/onboarding/creating-a-new-wallet.md b/guide/onboarding/creating-a-new-wallet.md index 7f7d905d2..ae4e2a140 100644 --- a/guide/onboarding/creating-a-new-wallet.md +++ b/guide/onboarding/creating-a-new-wallet.md @@ -1,10 +1,10 @@ --- layout: guide -title: Creating a new wallet -description: Steps to take when creating a new wallet, and tips for a great user experience. +title: First use +description: Common tasks when using a wallet application for the first time. parent: Onboarding nav_order: 2 -permalink: /guide/onboarding/creating-a-new-wallet/ +permalink: /guide/onboarding/first-use/ main_classes: -no-top-padding image: https://bitcoin.design/assets/images/guide/onboarding/creating-a-new-wallet/creating-a-new-wallet-preview.png --- @@ -24,7 +24,7 @@ image: https://bitcoin.design/assets/images/guide/onboarding/creating-a-new-wall There are a number of common tasks a user might want to achieve the first time they open a wallet application: -- [Create a new wallet](/guide/onboarding/creating-a-new-wallet/#creating-a-wallet), or +- [Create a new wallet](/guide/onboarding/first-use/#creating-a-wallet), or - [Restore an existing wallet](/guide/onboarding/restoring-a-wallet/) - [Backup a wallet](/guide/onboarding/backing-up-a-recovery-phrase/) - [Acquire bitcoin](/guide/onboarding/funding-a-wallet/) diff --git a/guide/onboarding/getting-to-know-your-users.md b/guide/onboarding/getting-to-know-your-users.md index 8f923ea58..2d8c2988e 100644 --- a/guide/onboarding/getting-to-know-your-users.md +++ b/guide/onboarding/getting-to-know-your-users.md @@ -182,11 +182,11 @@ Ultimately the goal of onboarding is that users trust the application, feel comf --- -Next, we will cover [creating a new wallet]({{ '/guide/onboarding/creating-a-new-wallet/' | relative_url }}). +Next, we will cover the [first use]({{ '/guide/onboarding/first-use/' | relative_url }}) of a wallet application. {% include next-previous.html previousUrl = "/guide/onboarding/introduction/" previousName = "Onboarding" - nextUrl = "/guide/onboarding/creating-a-new-wallet/" + nextUrl = "/guide/onboarding/first-use/" nextName = "Creating a new wallet" %} diff --git a/guide/onboarding/introduction.md b/guide/onboarding/introduction.md index 9c965e6a4..95bcd114c 100644 --- a/guide/onboarding/introduction.md +++ b/guide/onboarding/introduction.md @@ -49,9 +49,9 @@ This section will give you some tips on how best to understand and develop knowl --- -### [Creating a new wallet]({{ '/guide/onboarding/creating-a-new-wallet/' | relative_url }}) +### [First use]({{ '/guide/onboarding/first-use/' | relative_url }}) -An overview of what information to include when creating a wallet for the first time. +An overview of common tasks when using a wallet application for the first time. --- From 564c40f6895aff2a26f210618a631ac5fb4cea75 Mon Sep 17 00:00:00 2001 From: Daniel Nordh <3393669+danielnordh@users.noreply.github.com> Date: Thu, 14 Oct 2021 12:20:18 +0100 Subject: [PATCH 05/13] Rename file --- guide/onboarding/{creating-a-new-wallet.md => first-use.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename guide/onboarding/{creating-a-new-wallet.md => first-use.md} (100%) diff --git a/guide/onboarding/creating-a-new-wallet.md b/guide/onboarding/first-use.md similarity index 100% rename from guide/onboarding/creating-a-new-wallet.md rename to guide/onboarding/first-use.md From 278a42d63c8e815fd5d160c9667411c33e490e6a Mon Sep 17 00:00:00 2001 From: Daniel Nordh <3393669+danielnordh@users.noreply.github.com> Date: Thu, 14 Oct 2021 12:31:07 +0100 Subject: [PATCH 06/13] Minor readability tweaks. --- guide/onboarding/first-use.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/guide/onboarding/first-use.md b/guide/onboarding/first-use.md index ae4e2a140..26c19bcd9 100644 --- a/guide/onboarding/first-use.md +++ b/guide/onboarding/first-use.md @@ -31,17 +31,15 @@ There are a number of common tasks a user might want to achieve the first time t 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. -It is common to see onboarding flows that implores the user to do a manual backup of their recovery phrase straight away, often before they have even gotten to see the main screen of the application. While this can make sure the user is aware of the need to backup, their motivation and ability to safely do this at that exact moment might be limited. +It is common to see onboarding flows that implore the user to do a manual backup of their recovery phrase straight away, often before they have even gotten to see the main screen of the application. While this can make sure the user is aware of the need to backup, their motivation and ability to safely do this at that exact moment might be limited. -Alternative approaches can be to wait and prompt the user only once there are funds in the wallet, at regular intervals, or to use an automatic cloud backup for small amounts. This is all up to you as the application designer to decide what works best in your users’ use case. +Alternative approaches can be to wait and prompt the user only once there are funds in the wallet, at regular intervals, or to use an automatic cloud backup for small amounts. It is up to you as the application designer to decide what works best in your users’ use case. ### Creating a wallet -[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. +[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. -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. - -Most Bitcoin wallet applications will automatically generate users’ private keys during onboarding. +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. Most Bitcoin wallet applications will automatically generate the user’s private keys during onboarding.
@@ -111,7 +109,7 @@ Below is an example of some carousel screens that might be useful in helping a u
- These screens explicitly lay out the unique features of self-custodial wallets to make sure the user understands these caveats. These screens suggest talking about ownership, explicitly stating the recovery mechanism that the respective wallet uses, and security measures that they should take to protect their wallet. + These screens lay out the unique features of self-custodial wallets to make sure the user understands these caveats. These screens suggest talking about ownership, explicitly stating the recovery mechanism that the respective wallet uses, and security measures that they should take to protect their wallet. --- From 91cc6c8f0212aa40c736bcb5f49849c855da13e6 Mon Sep 17 00:00:00 2001 From: Daniel Nordh <3393669+danielnordh@users.noreply.github.com> Date: Fri, 15 Oct 2021 15:01:25 +0100 Subject: [PATCH 07/13] Update wording Co-authored-by: Christoph Ono --- guide/onboarding/first-use.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/onboarding/first-use.md b/guide/onboarding/first-use.md index 26c19bcd9..b89369cef 100644 --- a/guide/onboarding/first-use.md +++ b/guide/onboarding/first-use.md @@ -27,7 +27,7 @@ There are a number of common tasks a user might want to achieve the first time t - [Create a new wallet](/guide/onboarding/first-use/#creating-a-wallet), or - [Restore an existing wallet](/guide/onboarding/restoring-a-wallet/) - [Backup a wallet](/guide/onboarding/backing-up-a-recovery-phrase/) -- [Acquire bitcoin](/guide/onboarding/funding-a-wallet/) +- [Fund a wallet](/guide/onboarding/funding-a-wallet/) 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. From f3e3696fbf8c797f601532e138d0ada9293cf4c1 Mon Sep 17 00:00:00 2001 From: Daniel Nordh <3393669+danielnordh@users.noreply.github.com> Date: Fri, 15 Oct 2021 15:02:09 +0100 Subject: [PATCH 08/13] Minor tweaks Co-authored-by: Christoph Ono --- guide/onboarding/first-use.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/onboarding/first-use.md b/guide/onboarding/first-use.md index b89369cef..83faf6820 100644 --- a/guide/onboarding/first-use.md +++ b/guide/onboarding/first-use.md @@ -55,7 +55,7 @@ Like regular keys on a keychain, Bitcoin private keys can be copied. This makes After the user selects “Create a new wallet”, you might present informational carousels that provide a high-level overview of the implications, benefits, and responsibility that comes with having a self-custodial wallet. Here you can explain to your user that access to the wallet will not require collecting any sensitive information such as usernames and passwords, which is often the case with traditional financial products. -Rather, the user can directly access their funds as long as they have access to the private key or recovery phrase. You should help your users understand that your team does not have the ability to recover their funds in the event they lose their private key. A self custodial wallet often means the user will have to take on greater responsibility to safely protect their private key so they can always access their funds. +Rather, the user can directly access their funds as long as they have access to the private key or recovery phrase. You should help your users understand that your team does not have the ability to recover their funds in the event they lose their private key. A self-custodial wallet often means the user will have to take on greater responsibility to safely protect their private key so they can always access their funds. From 8d2b0ae83d0633f548744326a42f779cd5c22ce4 Mon Sep 17 00:00:00 2001 From: Daniel Nordh <3393669+danielnordh@users.noreply.github.com> Date: Fri, 15 Oct 2021 15:03:02 +0100 Subject: [PATCH 09/13] Add comma Co-authored-by: Christoph Ono --- guide/onboarding/first-use.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/onboarding/first-use.md b/guide/onboarding/first-use.md index 83faf6820..f270db53f 100644 --- a/guide/onboarding/first-use.md +++ b/guide/onboarding/first-use.md @@ -76,7 +76,7 @@ Some studies suggest that users struggled greatly with technical terminology and > > As researched by Eskandari et al -Below is an example of some carousel screens that might be useful in helping a user understand what to expect from this wallet. For this example, we have opted to backup the users' recovery phrase to a cloud provider but other alternatives exist. +Below is an example of some carousel screens that might be useful in helping a user understand what to expect from this wallet. For this example, we have opted to backup the users' recovery phrase to a cloud provider, but other alternatives exist.
From bb922e484946f39985fd35ff829fea2c8e22de32 Mon Sep 17 00:00:00 2001 From: Daniel Nordh <3393669+danielnordh@users.noreply.github.com> Date: Mon, 18 Oct 2021 14:30:52 +0100 Subject: [PATCH 10/13] custody -> custodial --- guide/onboarding/first-use.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/onboarding/first-use.md b/guide/onboarding/first-use.md index df1cb57e4..d12d96253 100644 --- a/guide/onboarding/first-use.md +++ b/guide/onboarding/first-use.md @@ -70,7 +70,7 @@ While this may sound daunting to first-time users, these caveats mustn't be hidd Ideally your application supports both the base layer and the Lightning network. When talking about backups, you should be clear on what is possible and required in terms of restoring the user’s wallet from a backup. -Some studies suggest that users struggled greatly with technical terminology and feeling as though they had a lack of guidance during wallet setup. By walking users through single steps that clearly frame the features of self-custody Bitcoin wallets, users will feel well-equipped to navigate and use the wallet confidently. +Some studies suggest that users struggled greatly with technical terminology and feeling as though they had a lack of guidance during wallet setup. By walking users through single steps that clearly frame the features of self-custodial Bitcoin wallets, users will feel well-equipped to navigate and use the wallet confidently. > Users reported that they often felt like they lacked guidance and understanding during wallet setup > From cd4ca496e417c4493146069dca2c48e2e518e4c1 Mon Sep 17 00:00:00 2001 From: Daniel Nordh <3393669+danielnordh@users.noreply.github.com> Date: Tue, 19 Oct 2021 08:47:52 +0100 Subject: [PATCH 11/13] Wording Co-authored-by: bosch <55287964+Bosch-0@users.noreply.github.com> --- guide/onboarding/first-use.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/onboarding/first-use.md b/guide/onboarding/first-use.md index d12d96253..7e036d529 100644 --- a/guide/onboarding/first-use.md +++ b/guide/onboarding/first-use.md @@ -55,7 +55,7 @@ Like regular keys on a keychain, Bitcoin private keys can be copied. This makes After the user selects “Create a new wallet”, you might present informational carousels that provide a high-level overview of the implications, benefits, and responsibility that comes with having a self-custodial wallet. Here you can explain to your user that access to the wallet will not require collecting any sensitive information such as usernames and passwords, which is often the case with traditional financial products. -Rather, the user can directly access their funds as long as they have access to the private key or recovery phrase. You should help your users understand that your team does not have the ability to recover their funds in the event they lose their private key. A self-custodial wallet often means the user will have to take on greater responsibility to safely protect their private key so they can always access their funds. +Bitcoin owners can directly access their funds as long as they have access to their private keys or recovery phrase. You should help your users understand that your team does not have the ability to recover their funds in the event they lose their private key. A self-custodial wallet means the user will have to take on greater responsibility to safely protect their private key so they can always access their funds.
From bd3b8214c2eb57d174ca6b7567ed0a1069c37b20 Mon Sep 17 00:00:00 2001 From: Daniel Nordh <3393669+danielnordh@users.noreply.github.com> Date: Tue, 19 Oct 2021 08:48:48 +0100 Subject: [PATCH 12/13] Clarification Co-authored-by: bosch <55287964+Bosch-0@users.noreply.github.com> --- guide/onboarding/first-use.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/onboarding/first-use.md b/guide/onboarding/first-use.md index 7e036d529..b7da715f3 100644 --- a/guide/onboarding/first-use.md +++ b/guide/onboarding/first-use.md @@ -39,7 +39,7 @@ Alternative approaches can be to wait and prompt the user only once there are fu [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. -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. Most Bitcoin wallet applications will automatically generate the user’s private keys during onboarding. +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.
From 20ba574f23b987642bc7d43c6d2235210748f277 Mon Sep 17 00:00:00 2001 From: Daniel Nordh <3393669+danielnordh@users.noreply.github.com> Date: Tue, 19 Oct 2021 08:50:57 +0100 Subject: [PATCH 13/13] Fix link from previous page that got lost in merge cleanup --- guide/onboarding/introduction.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guide/onboarding/introduction.md b/guide/onboarding/introduction.md index feaabd2dc..f7c9f29b8 100644 --- a/guide/onboarding/introduction.md +++ b/guide/onboarding/introduction.md @@ -76,6 +76,6 @@ An overview of how users are likely to fund their wallets {% include next-previous.html previousUrl = "/guide/designing-products/design-resources/" previousName = "Design resources" - nextUrl = "/guide/onboarding/creating-a-new-wallet/" - nextName = "Creating a new wallet" + nextUrl = "/guide/onboarding/first-use/" + nextName = "First use" %}