Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
233 commits
Select commit Hold shift + click to select a range
c1f950b
WiP starting point for a glossary
GBKS Oct 1, 2020
ef0051a
Update content-guidelines.md
ImTiaan Oct 20, 2020
8cf2e6e
Update glossary.md
ImTiaan Oct 20, 2020
127ad29
Update glossary.md
ImTiaan Oct 20, 2020
a5cc631
Reordered alphabetically
GBKS Oct 21, 2020
bbd3d53
Merge branch 'feature/glossary' into feature/glossary
GBKS Oct 21, 2020
29b1fe0
Merge pull request #41 from ImTiaan/feature/glossary
GBKS Oct 21, 2020
a8650ff
Merge branch 'master' into feature/glossary
GBKS Oct 21, 2020
8dd7d50
Create intro page for private key management chapter
danielnordh Nov 16, 2020
54267fb
Update intro page
danielnordh Nov 16, 2020
0c4d645
Rename file to fix jekyll routing
danielnordh Nov 16, 2020
a6c30ba
Added schemes page
danielnordh Nov 16, 2020
c386da6
Remove unused image
danielnordh Nov 16, 2020
e1cdd9f
Updated H1 title
danielnordh Nov 16, 2020
742580d
Added pages for single and multi user schemes
danielnordh Nov 16, 2020
832d52e
Added principles page
danielnordh Nov 16, 2020
5ed3312
Added case studies page
danielnordh Nov 17, 2020
a2118f1
Tweaks to titles
danielnordh Nov 17, 2020
8eaee2d
Added stubs to case studies page
danielnordh Nov 17, 2020
490d5e3
Update glossary, mainly around wallets
danielnordh Nov 17, 2020
755cda4
Add temp illustrations to schemes and case studies
danielnordh Nov 17, 2020
3e52728
Fix formatting
danielnordh Nov 17, 2020
28c2da1
Add /guide in permalinks and update nav_order
danielnordh Nov 17, 2020
375c88a
Update guide/private-key-management/single-user-schemes.md
danielnordh Nov 18, 2020
7974c45
Add link to private key chapter from Guide welcome page
danielnordh Nov 24, 2020
ae74176
Fix internal links (missing /guide)
danielnordh Nov 24, 2020
c488255
Tweaks to schemes.md
danielnordh Nov 24, 2020
ca378f5
Added Single/Multi user schemes list
danielnordh Nov 24, 2020
99d61b0
Add temporary chapter intro illustration
danielnordh Nov 24, 2020
40753d7
Renaming and linking to scheme ids
danielnordh Nov 24, 2020
47e7f35
Updates to single scheme, formatting
danielnordh Nov 24, 2020
c9f3ab0
Cut intro text
danielnordh Nov 25, 2020
851a764
Intro text tweaks
danielnordh Nov 25, 2020
a693465
Text updates to schemes overview
danielnordh Nov 25, 2020
3319461
Single-user -> personal
danielnordh Nov 25, 2020
32d04f8
Link to products with cloud backup
danielnordh Nov 25, 2020
51752ad
Tweaks to recovery phrase
danielnordh Nov 25, 2020
2316074
Recovery phrase / Signing device updates
danielnordh Nov 25, 2020
861b6cb
External devices update
danielnordh Nov 26, 2020
7c4598d
Threshold signatures updates
danielnordh Nov 26, 2020
2806d1e
Multi-key updates
danielnordh Nov 26, 2020
fd19bc8
Shared schemes update
danielnordh Nov 26, 2020
040d0a5
Links of schemes at top of Personal schemes
danielnordh Nov 26, 2020
0a8d82b
Case study cleanup
danielnordh Nov 26, 2020
0e4fba0
Add illustration placeholders
danielnordh Nov 27, 2020
ceeda39
Case studies changes
danielnordh Nov 27, 2020
968c56f
Add links to next page at bottom of pages
danielnordh Dec 2, 2020
b1b2a76
Update header illustrations
danielnordh Dec 2, 2020
cf75262
Add mobile assets, fix links
danielnordh Dec 2, 2020
5647869
Remove link to Appendix until it's ready.
danielnordh Dec 2, 2020
7a1b263
Spectrum updates
danielnordh Dec 2, 2020
d417027
Fix png/jpg issue
danielnordh Dec 2, 2020
a7d8721
Update flowchart
danielnordh Dec 2, 2020
f07aedc
Schemes tweaks
danielnordh Dec 2, 2020
568f567
Update headers
danielnordh Dec 2, 2020
3609554
Recovery-phrase illustration
danielnordh Dec 2, 2020
7a1f2cd
Scheme illustrations
danielnordh Dec 2, 2020
8e69d49
Add 5 schemes illustration
danielnordh Dec 2, 2020
93f74f6
Swap order
danielnordh Dec 2, 2020
e9ab130
Add shared multi-key illustration
danielnordh Dec 2, 2020
c3f720c
Image location
danielnordh Dec 2, 2020
f636f33
Fine tune illustrations
danielnordh Dec 2, 2020
9362409
Update device illustration
danielnordh Dec 3, 2020
8007be6
Update chapter header
danielnordh Dec 3, 2020
f9d7776
Updates to principles page
danielnordh Dec 3, 2020
4024fba
Rename to Manual backup / Recovery phrase
danielnordh Dec 3, 2020
5bc9469
Replace sovereign with manual
danielnordh Dec 3, 2020
567efda
More products, tweaks.
danielnordh Dec 3, 2020
502e47b
Wording
danielnordh Dec 3, 2020
6278256
Merge branch 'master' into feature/glossary
GBKS Dec 7, 2020
65de34d
Some added definitions
GBKS Dec 7, 2020
328514f
Added images for CoinJoin, Coin control, and wallet types
GBKS Dec 8, 2020
7c256f6
Full width images
danielnordh Dec 8, 2020
487c014
Wallet graphic update
GBKS Dec 9, 2020
3d3f76d
Merge branch 'master' into feature/glossary
GBKS Dec 9, 2020
6fc2fe8
Merge branch 'master' into private-key-management-v1
danielnordh Dec 9, 2020
944d2ce
Updates to multi-key
danielnordh Dec 10, 2020
d5bb0f7
Add new page for wallet recovery
danielnordh Dec 10, 2020
dd9fed4
Fix link
danielnordh Dec 10, 2020
df3c0d6
Test figma embed
danielnordh Dec 10, 2020
b411fa4
Test prototype image
danielnordh Dec 10, 2020
f03fb35
Add ability for image link-url to include
danielnordh Dec 10, 2020
768862f
Close /a
danielnordh Dec 10, 2020
4e7c607
Image tweaks
danielnordh Dec 10, 2020
220d21d
Figma embed height
danielnordh Dec 10, 2020
89fbe85
Remove border
danielnordh Dec 10, 2020
ccf23e2
Re-order
danielnordh Dec 10, 2020
f2869d1
Update embed source
danielnordh Dec 11, 2020
0d4dc5c
Add link to figma file (needs updating once community)
Dec 11, 2020
0be73df
Add prototype for current account
Dec 11, 2020
560e1e4
Add prototype for generalist
Dec 11, 2020
fd26284
Add shared
Dec 11, 2020
5f2822a
Update manual
Dec 11, 2020
8b5bf6a
use wallet-application instead of wallet-product
Dec 11, 2020
24384e1
Add private/public key info
danielnordh Dec 14, 2020
7a113d4
Merge branch 'master' into feature/glossary
GBKS Dec 14, 2020
5f3f2f2
Updates to address formats
danielnordh Dec 14, 2020
53575df
Merge branch 'feature/glossary' of https://github.com/BitcoinDesign/G…
danielnordh Dec 14, 2020
763da52
Fix typo and move paragraph.
danielnordh Dec 14, 2020
f14c7eb
Address tweaks
danielnordh Dec 14, 2020
163a3c2
Minor tweaks
danielnordh Dec 14, 2020
24618f5
Write all BIPs the same way
danielnordh Dec 14, 2020
3993bd2
Tweaks to xpubs and key
danielnordh Dec 14, 2020
377542b
Tweaks to various empty or rough terms.
danielnordh Dec 14, 2020
948cb86
Further term updates
danielnordh Dec 14, 2020
268e8fd
Transaction ToDo
danielnordh Dec 14, 2020
066c765
Fix heading code for PSBT
danielnordh Dec 14, 2020
24cda11
Tweaks to wallets
danielnordh Dec 14, 2020
a6c018e
Add BIP84, fix errors
danielnordh Dec 14, 2020
57ce77c
Fix link
danielnordh Dec 14, 2020
48aaee0
Add link to CoinJoin info
danielnordh Dec 14, 2020
7e74781
Typo
danielnordh Dec 14, 2020
4a9cc71
Minor tweak to fix link rendering
GBKS Dec 14, 2020
521c320
Fixing formattnig of external links
GBKS Dec 15, 2020
b90200b
Merge branch 'master' into feature/glossary
GBKS Dec 15, 2020
b9e5223
Update guide/private-key-management/introduction.md
danielnordh Dec 16, 2020
4870d1c
Update guide/private-key-management/introduction.md
danielnordh Dec 16, 2020
4acffd5
Remove speculation
danielnordh Dec 16, 2020
14a3c39
Update guide/private-key-management/schemes.md
danielnordh Dec 16, 2020
1d8803e
Update guide/private-key-management/schemes.md
danielnordh Dec 16, 2020
9e6f223
Update guide/private-key-management/schemes.md
danielnordh Dec 16, 2020
5a0506f
Update guide/private-key-management/schemes.md
danielnordh Dec 16, 2020
a4a4481
Update guide/private-key-management/single-user-schemes.md
danielnordh Dec 16, 2020
16cd223
Update guide/private-key-management/single-user-schemes.md
danielnordh Dec 16, 2020
fee43c1
Typo
danielnordh Dec 16, 2020
47f22da
Clarify key-value-store
danielnordh Dec 16, 2020
7f1cb81
Remove Paymobil reference
danielnordh Dec 16, 2020
c2014fa
Remove speculation about 24 words
danielnordh Dec 16, 2020
41c6caf
Open external links in new window
danielnordh Dec 16, 2020
1d675a7
Link typos
danielnordh Dec 16, 2020
80ffe19
External links open in new window
danielnordh Dec 16, 2020
64476a4
Simplify shared multi-key 'how it works'
danielnordh Dec 16, 2020
c6b5a3f
Put in development product at the end
danielnordh Dec 16, 2020
7e2d609
Update guide/private-key-management/principles.md
danielnordh Dec 16, 2020
d13fa58
Typo
danielnordh Dec 16, 2020
216b8bc
Update guide/private-key-management/principles.md
danielnordh Dec 16, 2020
ba7d882
Update guide/private-key-management/principles.md
danielnordh Dec 16, 2020
e5e1e30
Test renamed/styled titles in navigation
danielnordh Dec 16, 2020
2d2d525
Clarify shared multi-key title
danielnordh Dec 16, 2020
7c91343
Fix broken navigation
danielnordh Dec 16, 2020
7d87961
Update title to be consistent with navigation
danielnordh Dec 16, 2020
d3880f0
Tweak link
danielnordh Dec 16, 2020
a14129b
Tweak link
danielnordh Dec 16, 2020
c4f654a
Missing paranthesis
danielnordh Dec 16, 2020
f2ced09
Fix order
danielnordh Dec 16, 2020
b8c283c
Tweaks to multi-key
danielnordh Dec 16, 2020
48ece3b
Fix link
danielnordh Dec 16, 2020
71ff4ad
Missing paranthesis
danielnordh Dec 16, 2020
6373685
Add to interoperability
danielnordh Dec 16, 2020
605394a
Move change address to address section
danielnordh Dec 16, 2020
c3af454
Simplify legacy address
danielnordh Dec 16, 2020
8e0a559
Simplify script addresses
danielnordh Dec 16, 2020
dccc305
Simplify SegWit address
danielnordh Dec 16, 2020
9326f46
Merge branch 'master' into private-key-management-v1
danielnordh Dec 16, 2020
8597bba
Merge branch 'master' into feature/glossary
GBKS Dec 16, 2020
00394d2
Merge branch 'feature/glossary' of https://github.com/BitcoinDesign/G…
GBKS Dec 16, 2020
8bc2859
Minor URL fixes
GBKS Dec 16, 2020
902f1eb
Missing line break
danielnordh Dec 16, 2020
759ca19
Minor link fixes
GBKS Dec 16, 2020
20bd7d9
Markdown rendering fix
GBKS Dec 16, 2020
17c4c3a
Actual line break
danielnordh Dec 16, 2020
7239244
Actual line break
danielnordh Dec 16, 2020
545afae
Merge branch 'feature/glossary' into private-key-management-v1
danielnordh Dec 16, 2020
d148a87
Merge glossary
danielnordh Dec 16, 2020
2bf7018
Update titles to be consistent with nav
danielnordh Dec 16, 2020
d602fc7
Test linking to glossary
danielnordh Dec 16, 2020
1db214f
Test for glossary link to section
danielnordh Dec 16, 2020
c65fc6f
Revert "Test for glossary link to section"
danielnordh Dec 16, 2020
0a622a8
Links to glossary, minor tweaks
danielnordh Dec 16, 2020
e2e56cc
Glossary link
danielnordh Dec 16, 2020
15a5d2a
Update guide/glossary.md
danielnordh Dec 16, 2020
42977e2
Update guide/glossary.md
danielnordh Dec 16, 2020
51eeb6e
Update guide/glossary.md
danielnordh Dec 16, 2020
a680814
Update guide/glossary.md
danielnordh Dec 16, 2020
10bab6d
Change all product to application
danielnordh Dec 16, 2020
1663bdc
Update guide/glossary.md
danielnordh Dec 16, 2020
e11f72b
Segwit addresses
danielnordh Dec 16, 2020
34907aa
Merge branch 'feature/glossary' of https://github.com/BitcoinDesign/G…
danielnordh Dec 16, 2020
3ee3857
Update guide/glossary.md
danielnordh Dec 16, 2020
b9ad8e6
Update guide/glossary.md
danielnordh Dec 16, 2020
12bd761
Typos
danielnordh Dec 16, 2020
dfc071a
Update guide/glossary.md
danielnordh Dec 16, 2020
ab12b26
Update guide/glossary.md
danielnordh Dec 16, 2020
87359ad
Update guide/glossary.md
danielnordh Dec 16, 2020
ab07cd9
Coincontrol, readability
danielnordh Dec 16, 2020
ed1f3e9
Merge branch 'feature/glossary' into private-key-management-v1
danielnordh Dec 16, 2020
bb27468
Remove duplicate or unused images
danielnordh Dec 16, 2020
82b39a8
Optimized images
danielnordh Dec 16, 2020
b88ee74
Add page images, remove duplicate page files
danielnordh Dec 16, 2020
63b0144
Editor's notes
danielnordh Dec 16, 2020
9369e8e
Added links to hardware and software overview pages
GBKS Dec 17, 2020
94ee31b
Update guide/glossary.md
danielnordh Dec 17, 2020
4d384e2
Move to correct alphabetical location
danielnordh Dec 17, 2020
dc1c8cc
Add Derivation path
danielnordh Dec 17, 2020
473fe83
Derivation path tweaks / layout
danielnordh Dec 17, 2020
41ad5d4
Consistent use of SegWit
danielnordh Dec 17, 2020
5d22793
Format, typo
danielnordh Dec 17, 2020
4973f04
Update guide/glossary.md
danielnordh Dec 17, 2020
b5b3f3b
Merge branch 'feature/glossary' into private-key-management-v1
danielnordh Dec 17, 2020
d3b8ba1
Update guide/private-key-management/schemes.md
danielnordh Dec 21, 2020
008e959
Update guide/private-key-management/case-studies.md
danielnordh Dec 21, 2020
bbc3a05
Update guide/private-key-management/case-studies.md
danielnordh Dec 21, 2020
af81e90
Update guide/private-key-management/case-studies.md
danielnordh Dec 21, 2020
da8b677
Update guide/private-key-management/case-studies.md
danielnordh Dec 21, 2020
1127aae
Rephrase
danielnordh Dec 21, 2020
85f7659
Add descriptions to page meta-data
danielnordh Dec 21, 2020
9602469
Mass de-hyphenation
danielnordh Dec 21, 2020
1c2322d
Rephrase.
danielnordh Dec 21, 2020
00f8032
Update guide/private-key-management/single-user-schemes.md
danielnordh Dec 22, 2020
ef7a89e
Typo
danielnordh Dec 22, 2020
69cae90
Update guide/private-key-management/single-user-schemes.md
danielnordh Dec 22, 2020
1dfa55e
Update guide/private-key-management/single-user-schemes.md
danielnordh Dec 22, 2020
ef42453
Update guide/private-key-management/single-user-schemes.md
danielnordh Dec 22, 2020
9f9abf8
Update guide/private-key-management/single-user-schemes.md
danielnordh Dec 22, 2020
4c41fef
Update guide/private-key-management/schemes.md
danielnordh Dec 22, 2020
f003877
Update guide/private-key-management/schemes.md
danielnordh Dec 22, 2020
d952e8b
Update guide/private-key-management/schemes.md
danielnordh Dec 22, 2020
94a2664
Update guide/private-key-management/schemes.md
danielnordh Dec 22, 2020
0872094
Update guide/private-key-management/single-user-schemes.md
danielnordh Dec 22, 2020
e55bddb
Replace backfire with actual result.
danielnordh Dec 22, 2020
eda83c4
Update guide/private-key-management/single-user-schemes.md
danielnordh Dec 22, 2020
362ea5e
Update guide/private-key-management/single-user-schemes.md
danielnordh Dec 22, 2020
3a9aa62
Update guide/private-key-management/single-user-schemes.md
danielnordh Dec 22, 2020
8c950ed
Off-line
danielnordh Dec 22, 2020
0610cff
Merge branch 'private-key-management-v1' of https://github.com/Bitcoi…
danielnordh Dec 22, 2020
88dbcf3
air gapped
danielnordh Dec 22, 2020
ff62b93
Rephrase
danielnordh Dec 23, 2020
82b7c11
Put 'how it works' before pros and cons
danielnordh Dec 23, 2020
a759a86
More off-line
danielnordh Dec 23, 2020
f5b7089
Simplify, don't use redundant
danielnordh Dec 23, 2020
182fda9
Grammar
danielnordh Dec 23, 2020
588d44a
Clarify that multi-key can be used for single user.
danielnordh Dec 23, 2020
ada291c
bitcoin instead of crypto
danielnordh Dec 23, 2020
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
4 changes: 3 additions & 1 deletion _includes/image.html
Original file line number Diff line number Diff line change
@@ -1,10 +1,12 @@
<figure{% if include.layout %} class="-{{ include.layout }}"{% endif %}>
<a href="{{ include.link-url }}">
<img
src="{{ include.image | relative_url }}"
{% if include.retina %} srcset="{{ include.image | relative_url }} 1x, {{ include.retina | relative_url }} 2x"{% endif %}
alt="{{ include.alt-text }}"
width="{{ include.width }}"
height="{{ include.height }}"
>
>
</a>
{% if include.caption %}<figcaption markdown="1">{{ include.caption | markdownify }}</figcaption>{% endif %}
</figure>
Binary file added assets/images/guide/glossary/coin-selection.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.
Binary file added assets/images/guide/glossary/coinjoin.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added assets/images/guide/glossary/coinjoin@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.
Binary file added assets/images/guide/glossary/descriptors.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added assets/images/guide/glossary/descriptors@2x.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added assets/images/guide/glossary/wallet.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added assets/images/guide/glossary/wallet@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.
2 changes: 1 addition & 1 deletion guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ With bitcoin being so new and different, a big focus of the guide lies on provid

- [Getting started]({{ '/guide/getting-started/introduction/' | relative_url }}) is for top-level overviews, whether it's bitcoin technology, visual language, software, or design collaboration in an open-source world
- _Onboarding_ (Coming soon) goes in-depth on the delicate process of introducing new users to bitcoin and how to use specific products and features
- [Private key management]({{ '/private-key-management/introduction/' | relative_url }}) provides extensive details and guidance on the many techniques for storing private keys
- [Private key management]({{ '/guide/private-key-management/introduction/' | relative_url }}) provides extensive details and guidance on the many techniques for storing private keys
- _Transactions_ (Coming soon) deals with the complexities of sending and receiving bitcoin across various use cases
- _Resources_ (Coming soon) are tools and information to practically help you get things done
- _Reference_ (Coming soon) includes a glossary, an overview of important bitcoin improvement proposals and other useful information
Expand Down
334 changes: 334 additions & 0 deletions guide/glossary.md

Large diffs are not rendered by default.

147 changes: 147 additions & 0 deletions guide/private-key-management/case-studies.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,147 @@
---
layout: guide
title: Case studies
description: A range of case study designs for bitcoin applications.
nav_order: 5
parent: Private key management
permalink: /guide/private-key-management/case-studies/
main_classes: -no-top-padding
image: /assets/images/guide/private-key-management/case-studies/page-case-studies.jpg
---

<!--

Editor's notes

A range of case study designs for bitcoin applications.

-->

{% include picture.html
image = "/assets/images/guide/private-key-management/case-studies.jpg"
retina = "/assets/images/guide/private-key-management/case-studies@2x.jpg"
mobile = "/assets/images/guide/private-key-management/case-studies-mobile.jpg"
mobileRetina = "/assets/images/guide/private-key-management/case-studies-mobile@2x.jpg"
alt-text = "Case studies header illustration"
width = 1600
height = 600
layout = "full-width"
%}

# Case studies

Before deciding on a private key management scheme it’s essential to have a good idea of what use case and target audience your product has. Let’s look at some hypothetical use case categories and what might be suitable approaches.

- [Cash / Daily spending]({{ '/guide/private-key-management/case-studies/#cash--daily-spending' | relative_url }})
- [Current / Checking account]({{ '/guide/private-key-management/case-studies/#current--checking-account' | relative_url }})
- [General upgradeable wallet]({{ '/guide/private-key-management/case-studies/#general-upgradeable-wallet' | relative_url }})
- [Shared account]({{ '/guide/private-key-management/case-studies/#shared-account' | relative_url }})

***

## Cash / Daily spending

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great section, sums up everything we talked about with examples. I love it.


Imagine a product which tries to solve the problem of quickly and easily sending smaller amounts of money to friends and family, or for small purchases. Ease and speed of use will be important as usage is likely to be on mobile devices and on the go. Users are not expected to be well versed in bitcoin technology or advanced private key management, which makes it reasonable to worry more about self-inflicted loss than from theft.

A single-key scheme with [automatic cloud backup]({{ '/guide/private-key-management/single-user-schemes/#automatic-cloud-backup' | relative_url }}) might be the best choice for the majority of users in this case. For more advanced users you could offer the option to opt-out of automatic cloud backup and instead use a recovery phrase.

<iframe style="border: 0px solid rgba(0, 0, 0, 0.1);" width="450" height="1000" src="https://www.figma.com/embed?embed_host=share&url=https%3A%2F%2Fwww.figma.com%2Fproto%2FSRWlaxbDulsacpPQn2TTri%2FCase-study-prototypes%3Fnode-id%3D1%253A3%26viewport%3D1204%252C392%252C0.5%26scaling%3Dmin-zoom" allowfullscreen></iframe>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Locally (and I have power-machine and connection) these embeds take quite a while to load (~5 sec), is there something we can do to improve the performance?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point.
Not sure what to here as it's mostly in Figma's hands.
Options:

  1. Accept load times, not helped by having several on one page
  2. Accept load times, but split case studies into separate pages
  3. Don't embed, show static image or gif and then link to prototype externally

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as an image goes, how about we include all screens in the prototype laid out next to each other with arrows indicating the sequence? That allows readers to easily understand the full user flow, and we can still offer a "View prototype" option to feel out the interaction.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also think the prototype needs some explanation. "The following prototype shows how convenient a cloud backup user flow can be. Start by tapping 'Create wallet'." Prototypes are great to make designs feel more real, but they don't explain themselves at all.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Recieve" should be "Receive" in the prototype.


#### Design considerations
- Most users will be bitcoin beginners
- Quick and easy send/receive
- Onboarding with as little friction as possible

#### Technical considerations
- Back up encrypted recovery phrase automatically to retain export option in the future
- Use a platform-appropriate storage location (keychain with iCloud, Google Drive)
- Additional user authentication to consider: biometrics, pin
- Upgrade-path to other schemes if funds stored increase

You can find a prototype for this case study embedded above, and a Figma file with [outline designs here](https://www.figma.com/file/SRWlaxbDulsacpPQn2TTri/Case-study-prototypes?node-id=0%3A1){:target="_blank"}.

***

## Current / Checking account

In this section, we are looking at a product that is meant to be a replacement for what a bank would call a current/checking account where the user might receive their salary and pay their bills from.
Safeguards against loss will be a higher priority than with a cash product, and we might therefore accept more friction both when setting up the wallet and when transacting.
If users have no prior bitcoin knowledge we should expect to spend a significant effort educating them to put them in a position to safely operate the wallet product.

A 2-of-3 [multi-key setup]({{ '/guide/private-key-management/single-user-schemes/#multi-key' | relative_url }}) would seem the most appropriate here, although it will be a significant hurdle in onboarding. Other schemes could be considered but come with distinct downsides for amounts of value we can expect users to store in this use case. A single-key scheme with an automatic cloud backup, recovery phrase or single signing device could work at the lower end of the value scale, but start to look like less responsible recommendations with higher values due to their single points of failure.

An important question is the combination of key-storage devices and their distribution. We have many options here, and it might come down to the experience of the target audience and their expected access to the necessary hardware;

- As low friction as possible (co-managed, no purpose-built signing device)
- Middle ground (co-managed, one purpose-built signing device)
- Full sovereignty (one or more purpose-built signing devices)
- All keys off-line (two or more purpose-built signing devices)

For this case study we will go with the middle ground option which will require one purpose-built signing device such as a hardware wallet. The other two keys will be one created on the user’s main mobile device and automatically backed up to their cloud provider, and another key held by the wallet application provider on a server for recovery. Neither of the two keys in the user’s control (mobile and signing device) will require recovery phrase backups, although this could be offered as an option.

The idea here is that the user will control the wallet through an app on their main mobile device, but when they are sending funds (paying bills etc) they will need to confirm the transaction on the purpose-built signing device.

Should they lose either their main mobile device, or the purpose-built signing device they can replace the lost key (rotate in a new key) with the help of the recovery key. However, if they lose both the mobile and signing device they will not be able to recover their funds, unless they had also backed up either of the respective recovery phrases.

<iframe style="border: 0px solid rgba(0, 0, 0, 0.1);" width="450" height="1000" src="https://www.figma.com/embed?embed_host=share&url=https%3A%2F%2Fwww.figma.com%2Fproto%2FSRWlaxbDulsacpPQn2TTri%2FCase-study-prototypes%3Fnode-id%3D6%253A11%26viewport%3D479%252C82%252C0.5%26scaling%3Dscale-down" allowfullscreen></iframe>

#### Design considerations
- Suitable for monthly transactions
- Lots of edge cases and infrequent but important situations
- Key setup, rotation, recovery and signing flows

#### Technical considerations
- Complexities of multi-key setups
- Implement thorough backup code and instructions for users
- Usage could be simplified by having hardware device designed/customized by the software maker (compare banks and their digital token signers common in Europe)

You can find a prototype for this case study embedded above, and a Figma file with [outline designs here](https://www.figma.com/file/SRWlaxbDulsacpPQn2TTri/Case-study-prototypes?node-id=6%3A9){:target="_blank"}.

***

## Upgradeable wallet

Although it is generally easier to build a great experience with a specific use case in mind, let's look at a case where we would like to make a wallet that is made for a broad range of uses and audiences. It needs to be suitable both for beginners and expanding users, and for holding anything between small and significant amounts. How do we choose a single private key management scheme for this situation?

The solution in this case could be a wallet that enables the user to upgrade the scheme as their experience and funds grow. The idea is to provide progressive security that doesn't introduce unnecessary friction until it is required. Our wallet will be able to switch from;

- Automatic cloud backup - as default for new users, who often start out with small amounts
- External signing device - for more experienced users, and when funds have grown
- 2-of-3 multi-key - for seasoned users, and critical amounts
- 3-of-5 multi-key - for really serious situations and/or very high amounts

<iframe style="border: 0px solid rgba(0, 0, 0, 0.1);" width="450" height="1000" src="https://www.figma.com/embed?embed_host=share&url=https%3A%2F%2Fwww.figma.com%2Fproto%2FSRWlaxbDulsacpPQn2TTri%2FCase-study-prototypes%3Fnode-id%3D15%253A270%26viewport%3D1057%252C573%252C0.23897239565849304%26scaling%3Dscale-down" allowfullscreen></iframe>

#### Design considerations
- Low friction onboarding
- Guide the user through scheme upgrades as funds grow

#### Technical considerations
- Need to handle many schemes; automatic cloud backups, recovery phrases, external signing devices, multi-key

You can find a prototype for this case study embedded above, and a Figma file with [outline designs here](https://www.figma.com/file/SRWlaxbDulsacpPQn2TTri/Case-study-prototypes?node-id=15%3A269){:target="_blank"}.

***

## Shared account

A common real-world use case for shared accounts are couples managing their monthly spending, with both parties being able to spend from the account. For this situation we could consider the following private key management schemes:

- 1-of-2 multi-key - either party can spend without the other's approval
- 2-of-3 multi-key - either party can spend with approval from one additional key

The other person does not need to co-sign every transaction, but we might want a *spending limit*, above which both parties need to approve the transaction. All multi-key setups are represented by bitcoin scripts on the blockchain, and the spending limit can be introduced as a conditional for both the 1-of-2 or 2-of-3 scheme.

Although the 1-of-2 scheme could work here, it offers lower protection against both theft and self-inflicted loss, unless rigorous manual backups are implemented. For this example we will choose the 2-of-3 scheme, but still have to decide on who will hold the third key, and the location of the other two.

Depending on how tailor-made or interoperable we want this setup could be we have many options for the location of the three keys, including:

- Individual mobile keys for the two users, plus one held by the co-manager (the product maker) for recovery and co-signing
- Individual mobile keys for the two users, plus a shared external signing device
- Each user can choose their own key location (mobile, external device, etc.), plus a shared external signing device

We are looking for a low friction, easy-to-manage solution that could work for beginners so in this case we'll go with the two mobile keys and the third key held by the co-manager.

<iframe style="border: 0px solid rgba(0, 0, 0, 0.1);" width="450" height="1000" src="https://www.figma.com/embed?embed_host=share&url=https%3A%2F%2Fwww.figma.com%2Fproto%2FSRWlaxbDulsacpPQn2TTri%2FCase-study-prototypes%3Fnode-id%3D15%253A824%26viewport%3D739%252C217%252C0.5%26scaling%3Dscale-down" allowfullscreen></iframe>

You can find a prototype for this case study embedded above, and a Figma file with [outline designs here](https://www.figma.com/file/SRWlaxbDulsacpPQn2TTri/Case-study-prototypes?node-id=15%3A822){:target="_blank"}.
50 changes: 48 additions & 2 deletions guide/private-key-management/introduction.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,56 @@
---
layout: guide
title: Private key management
description: An overview of private key management schemes, including descriptions of available approaches, some advice and best practices.
nav_order: 2
permalink: /private-key-management/introduction/
has_children: true
permalink: /guide/private-key-management/introduction/
main_classes: -no-top-padding
image: /assets/images/guide/private-key-management/page-private-key-management.jpg
---

<!--

Editor's notes

A brief introduction and summary of all pages in this section. The idea is that readers
scan this page to get an overview of the section and then decide which topics to dive into.

-->

{% include picture.html
image = "/assets/images/guide/private-key-management/private-key-management.jpg"
retina = "/assets/images/guide/private-key-management/private-key-management@2x.jpg"
mobile = "/assets/images/guide/private-key-management/private-key-management-mobile.jpg"
mobileRetina = "/assets/images/guide/private-key-management/private-key-management-mobile@2x.jpg"
alt-text = "Private key management chapter illustration"
width = 1600
height = 600
layout = "full-width"
%}

# Private key management

This chapter is in development at [PR #48](https://github.com/BitcoinDesign/Guide/pull/48){:target="_blank"}. Check the [preview](https://deploy-preview-48--sad-borg-390916.netlify.app/guide/private-key-management/introduction/){:target="_blank"}.
When designing a bitcoin-application, the way you choose to manage the [private key]({{ '/guide/glossary/#private-key' | relative_url }}){:target="_blank"} often dictates the fundamental user experience for your users. Being in control of a private key means you have access to the funds it holds. Keeping that key safe is like being in charge of the security of your own bank. It comes with a lot of freedom, but also a big responsibility that many users are not used to.
Comment thread
danielnordh marked this conversation as resolved.
Resolved

If it’s not secure enough, you risk loss of user's funds. But if it’s not convenient enough, you risk not getting or retaining many users in the first place.

This chapter is meant to give an overview of private key management schemes, including descriptions of available approaches, some advice and best practices. After this chapter, you should be able to choose a solution that is well suited to your product’s use case, and understand best-practices for the implementation of it.

---

**[Private key schemes]({{ '/guide/private-key-management/schemes/' | relative_url }})**

An overview of the most common private key management schemes for bitcoin products, and thoughts on picking a suitable scheme for your target audience and their use case.

**[Principles]({{ '/guide/private-key-management/principles/' | relative_url }})**

Every use case and product is different but there are things that all wallet applications should strive for, and only diverge from with very good reasons.

**[Case studies]({{ '/guide/private-key-management/case-studies/' | relative_url }})**

A look at some hypothetical use case categories and what might be suitable approaches for private key management schemes for each of them.

---

Let's get started with an overview of [private key schemes]({{ '/guide/private-key-management/schemes/' | relative_url }}).
Loading