diff --git a/_includes/image.html b/_includes/image.html
index a211d2e0f..40569a1d8 100644
--- a/_includes/image.html
+++ b/_includes/image.html
@@ -1,10 +1,12 @@
+
+ >
+
{% if include.caption %}{{ include.caption | markdownify }}{% endif %}
\ No newline at end of file
diff --git a/assets/images/guide/glossary/coin-selection.jpg b/assets/images/guide/glossary/coin-selection.jpg
new file mode 100644
index 000000000..7eee04173
Binary files /dev/null and b/assets/images/guide/glossary/coin-selection.jpg differ
diff --git a/assets/images/guide/glossary/coin-selection@2x.jpg b/assets/images/guide/glossary/coin-selection@2x.jpg
new file mode 100644
index 000000000..69017daab
Binary files /dev/null and b/assets/images/guide/glossary/coin-selection@2x.jpg differ
diff --git a/assets/images/guide/glossary/coinjoin.jpg b/assets/images/guide/glossary/coinjoin.jpg
new file mode 100644
index 000000000..640eff3c9
Binary files /dev/null and b/assets/images/guide/glossary/coinjoin.jpg differ
diff --git a/assets/images/guide/glossary/coinjoin@2x.jpg b/assets/images/guide/glossary/coinjoin@2x.jpg
new file mode 100644
index 000000000..1bc7a502b
Binary files /dev/null and b/assets/images/guide/glossary/coinjoin@2x.jpg differ
diff --git a/assets/images/guide/glossary/descriptors-mobile.jpg b/assets/images/guide/glossary/descriptors-mobile.jpg
new file mode 100644
index 000000000..ce2777fbb
Binary files /dev/null and b/assets/images/guide/glossary/descriptors-mobile.jpg differ
diff --git a/assets/images/guide/glossary/descriptors-mobile@2x.jpg b/assets/images/guide/glossary/descriptors-mobile@2x.jpg
new file mode 100644
index 000000000..0a5ca34d4
Binary files /dev/null and b/assets/images/guide/glossary/descriptors-mobile@2x.jpg differ
diff --git a/assets/images/guide/glossary/descriptors.jpg b/assets/images/guide/glossary/descriptors.jpg
new file mode 100644
index 000000000..b9c3e5ac2
Binary files /dev/null and b/assets/images/guide/glossary/descriptors.jpg differ
diff --git a/assets/images/guide/glossary/descriptors@2x.jpg b/assets/images/guide/glossary/descriptors@2x.jpg
new file mode 100644
index 000000000..0ab58630f
Binary files /dev/null and b/assets/images/guide/glossary/descriptors@2x.jpg differ
diff --git a/assets/images/guide/glossary/wallet.jpg b/assets/images/guide/glossary/wallet.jpg
new file mode 100644
index 000000000..4e1bcd790
Binary files /dev/null and b/assets/images/guide/glossary/wallet.jpg differ
diff --git a/assets/images/guide/glossary/wallet@2x.jpg b/assets/images/guide/glossary/wallet@2x.jpg
new file mode 100644
index 000000000..6a111c78f
Binary files /dev/null and b/assets/images/guide/glossary/wallet@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/case-studies-mobile.jpg b/assets/images/guide/private-key-management/case-studies-mobile.jpg
new file mode 100644
index 000000000..7ce7579c3
Binary files /dev/null and b/assets/images/guide/private-key-management/case-studies-mobile.jpg differ
diff --git a/assets/images/guide/private-key-management/case-studies-mobile@2x.jpg b/assets/images/guide/private-key-management/case-studies-mobile@2x.jpg
new file mode 100644
index 000000000..36da7437e
Binary files /dev/null and b/assets/images/guide/private-key-management/case-studies-mobile@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/case-studies.jpg b/assets/images/guide/private-key-management/case-studies.jpg
new file mode 100644
index 000000000..e568e2f74
Binary files /dev/null and b/assets/images/guide/private-key-management/case-studies.jpg differ
diff --git a/assets/images/guide/private-key-management/case-studies/page-case-studies.jpg b/assets/images/guide/private-key-management/case-studies/page-case-studies.jpg
new file mode 100644
index 000000000..63c715685
Binary files /dev/null and b/assets/images/guide/private-key-management/case-studies/page-case-studies.jpg differ
diff --git a/assets/images/guide/private-key-management/case-studies@2x.jpg b/assets/images/guide/private-key-management/case-studies@2x.jpg
new file mode 100644
index 000000000..1948785ec
Binary files /dev/null and b/assets/images/guide/private-key-management/case-studies@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/header-placeholder.jpg b/assets/images/guide/private-key-management/header-placeholder.jpg
new file mode 100644
index 000000000..22fb995c6
Binary files /dev/null and b/assets/images/guide/private-key-management/header-placeholder.jpg differ
diff --git a/assets/images/guide/private-key-management/header-placeholder@2x.jpg b/assets/images/guide/private-key-management/header-placeholder@2x.jpg
new file mode 100644
index 000000000..bd81dac3b
Binary files /dev/null and b/assets/images/guide/private-key-management/header-placeholder@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/illustration-placeholder.jpg b/assets/images/guide/private-key-management/illustration-placeholder.jpg
new file mode 100644
index 000000000..4d64ee426
Binary files /dev/null and b/assets/images/guide/private-key-management/illustration-placeholder.jpg differ
diff --git a/assets/images/guide/private-key-management/illustration-placeholder@2x.jpg b/assets/images/guide/private-key-management/illustration-placeholder@2x.jpg
new file mode 100644
index 000000000..168eab015
Binary files /dev/null and b/assets/images/guide/private-key-management/illustration-placeholder@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/page-private-key-management.jpg b/assets/images/guide/private-key-management/page-private-key-management.jpg
new file mode 100644
index 000000000..c86b6f8b0
Binary files /dev/null and b/assets/images/guide/private-key-management/page-private-key-management.jpg differ
diff --git a/assets/images/guide/private-key-management/personal-mobile.jpg b/assets/images/guide/private-key-management/personal-mobile.jpg
new file mode 100644
index 000000000..54e663986
Binary files /dev/null and b/assets/images/guide/private-key-management/personal-mobile.jpg differ
diff --git a/assets/images/guide/private-key-management/personal-mobile@2x.jpg b/assets/images/guide/private-key-management/personal-mobile@2x.jpg
new file mode 100644
index 000000000..aba743d38
Binary files /dev/null and b/assets/images/guide/private-key-management/personal-mobile@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/personal.jpg b/assets/images/guide/private-key-management/personal.jpg
new file mode 100644
index 000000000..70f86e840
Binary files /dev/null and b/assets/images/guide/private-key-management/personal.jpg differ
diff --git a/assets/images/guide/private-key-management/personal@2x.jpg b/assets/images/guide/private-key-management/personal@2x.jpg
new file mode 100644
index 000000000..86c651c51
Binary files /dev/null and b/assets/images/guide/private-key-management/personal@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/principles-mobile.jpg b/assets/images/guide/private-key-management/principles-mobile.jpg
new file mode 100644
index 000000000..1cb86618d
Binary files /dev/null and b/assets/images/guide/private-key-management/principles-mobile.jpg differ
diff --git a/assets/images/guide/private-key-management/principles-mobile@2x.jpg b/assets/images/guide/private-key-management/principles-mobile@2x.jpg
new file mode 100644
index 000000000..dd4801038
Binary files /dev/null and b/assets/images/guide/private-key-management/principles-mobile@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/principles.jpg b/assets/images/guide/private-key-management/principles.jpg
new file mode 100644
index 000000000..1bc1478f9
Binary files /dev/null and b/assets/images/guide/private-key-management/principles.jpg differ
diff --git a/assets/images/guide/private-key-management/principles/page-principles.jpg b/assets/images/guide/private-key-management/principles/page-principles.jpg
new file mode 100644
index 000000000..19d231a91
Binary files /dev/null and b/assets/images/guide/private-key-management/principles/page-principles.jpg differ
diff --git a/assets/images/guide/private-key-management/principles@2x.jpg b/assets/images/guide/private-key-management/principles@2x.jpg
new file mode 100644
index 000000000..3cccb8b78
Binary files /dev/null and b/assets/images/guide/private-key-management/principles@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/private-key-management-mobile.jpg b/assets/images/guide/private-key-management/private-key-management-mobile.jpg
new file mode 100644
index 000000000..4a60d8a0f
Binary files /dev/null and b/assets/images/guide/private-key-management/private-key-management-mobile.jpg differ
diff --git a/assets/images/guide/private-key-management/private-key-management-mobile@2x.jpg b/assets/images/guide/private-key-management/private-key-management-mobile@2x.jpg
new file mode 100644
index 000000000..8d8974aee
Binary files /dev/null and b/assets/images/guide/private-key-management/private-key-management-mobile@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/private-key-management.jpg b/assets/images/guide/private-key-management/private-key-management.jpg
new file mode 100644
index 000000000..d78ebb20d
Binary files /dev/null and b/assets/images/guide/private-key-management/private-key-management.jpg differ
diff --git a/assets/images/guide/private-key-management/private-key-management@2x.jpg b/assets/images/guide/private-key-management/private-key-management@2x.jpg
new file mode 100644
index 000000000..035d7561e
Binary files /dev/null and b/assets/images/guide/private-key-management/private-key-management@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes-mobile.jpg b/assets/images/guide/private-key-management/schemes-mobile.jpg
new file mode 100644
index 000000000..b403e3e84
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes-mobile.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes-mobile@2x.jpg b/assets/images/guide/private-key-management/schemes-mobile@2x.jpg
new file mode 100644
index 000000000..826d6c6cb
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes-mobile@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes.jpg b/assets/images/guide/private-key-management/schemes.jpg
new file mode 100644
index 000000000..7ebe7a088
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/cloud-backup.jpg b/assets/images/guide/private-key-management/schemes/cloud-backup.jpg
new file mode 100644
index 000000000..08f3f06f8
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/cloud-backup.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/cloud-backup@2x.jpg b/assets/images/guide/private-key-management/schemes/cloud-backup@2x.jpg
new file mode 100644
index 000000000..2c93dffcd
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/cloud-backup@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/flow-chart.jpg b/assets/images/guide/private-key-management/schemes/flow-chart.jpg
new file mode 100644
index 000000000..241680f10
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/flow-chart.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/flow-chart@2x.jpg b/assets/images/guide/private-key-management/schemes/flow-chart@2x.jpg
new file mode 100644
index 000000000..1524e2b6a
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/flow-chart@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/multi-key.jpg b/assets/images/guide/private-key-management/schemes/multi-key.jpg
new file mode 100644
index 000000000..cf11998b0
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/multi-key.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/multi-key@2x.jpg b/assets/images/guide/private-key-management/schemes/multi-key@2x.jpg
new file mode 100644
index 000000000..efeef2ee7
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/multi-key@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/page-personal-schemes.jpg b/assets/images/guide/private-key-management/schemes/page-personal-schemes.jpg
new file mode 100644
index 000000000..025327268
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/page-personal-schemes.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/page-private-key-schemes.jpg b/assets/images/guide/private-key-management/schemes/page-private-key-schemes.jpg
new file mode 100644
index 000000000..46c851307
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/page-private-key-schemes.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/page-shared-schemes.png b/assets/images/guide/private-key-management/schemes/page-shared-schemes.png
new file mode 100644
index 000000000..62c2f1a68
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/page-shared-schemes.png differ
diff --git a/assets/images/guide/private-key-management/schemes/personal-schemes.jpg b/assets/images/guide/private-key-management/schemes/personal-schemes.jpg
new file mode 100644
index 000000000..e0eb6be5d
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/personal-schemes.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/personal-schemes@2x.jpg b/assets/images/guide/private-key-management/schemes/personal-schemes@2x.jpg
new file mode 100644
index 000000000..25b2fc548
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/personal-schemes@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/recovery-phrase.jpg b/assets/images/guide/private-key-management/schemes/recovery-phrase.jpg
new file mode 100644
index 000000000..23f10d284
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/recovery-phrase.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/recovery-phrase@2x.jpg b/assets/images/guide/private-key-management/schemes/recovery-phrase@2x.jpg
new file mode 100644
index 000000000..7feddaea5
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/recovery-phrase@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/shared-multi-key.jpg b/assets/images/guide/private-key-management/schemes/shared-multi-key.jpg
new file mode 100644
index 000000000..f658eb142
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/shared-multi-key.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/shared-multi-key@2x.jpg b/assets/images/guide/private-key-management/schemes/shared-multi-key@2x.jpg
new file mode 100644
index 000000000..08d3d36d7
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/shared-multi-key@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/signing-devices.jpg b/assets/images/guide/private-key-management/schemes/signing-devices.jpg
new file mode 100644
index 000000000..a500e765d
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/signing-devices.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/signing-devices@2x.jpg b/assets/images/guide/private-key-management/schemes/signing-devices@2x.jpg
new file mode 100644
index 000000000..e7005e23b
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/signing-devices@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/spectrum.jpg b/assets/images/guide/private-key-management/schemes/spectrum.jpg
new file mode 100644
index 000000000..1a1e8c43b
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/spectrum.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/spectrum@2x.jpg b/assets/images/guide/private-key-management/schemes/spectrum@2x.jpg
new file mode 100644
index 000000000..c1aab4bdf
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/spectrum@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/threshold-signatures.jpg b/assets/images/guide/private-key-management/schemes/threshold-signatures.jpg
new file mode 100644
index 000000000..d4c76ba7a
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/threshold-signatures.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes/threshold-signatures@2x.jpg b/assets/images/guide/private-key-management/schemes/threshold-signatures@2x.jpg
new file mode 100644
index 000000000..5cc9d89c7
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes/threshold-signatures@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/schemes@2x.jpg b/assets/images/guide/private-key-management/schemes@2x.jpg
new file mode 100644
index 000000000..5ab91d74a
Binary files /dev/null and b/assets/images/guide/private-key-management/schemes@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/shared-mobile.jpg b/assets/images/guide/private-key-management/shared-mobile.jpg
new file mode 100644
index 000000000..5f345785f
Binary files /dev/null and b/assets/images/guide/private-key-management/shared-mobile.jpg differ
diff --git a/assets/images/guide/private-key-management/shared-mobile@2x.jpg b/assets/images/guide/private-key-management/shared-mobile@2x.jpg
new file mode 100644
index 000000000..e86fd1c56
Binary files /dev/null and b/assets/images/guide/private-key-management/shared-mobile@2x.jpg differ
diff --git a/assets/images/guide/private-key-management/shared.jpg b/assets/images/guide/private-key-management/shared.jpg
new file mode 100644
index 000000000..f9f906242
Binary files /dev/null and b/assets/images/guide/private-key-management/shared.jpg differ
diff --git a/assets/images/guide/private-key-management/shared@2x.jpg b/assets/images/guide/private-key-management/shared@2x.jpg
new file mode 100644
index 000000000..310593e98
Binary files /dev/null and b/assets/images/guide/private-key-management/shared@2x.jpg differ
diff --git a/guide.md b/guide.md
index ec6b6e7cb..e8bb4807d 100644
--- a/guide.md
+++ b/guide.md
@@ -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
diff --git a/guide/glossary.md b/guide/glossary.md
new file mode 100644
index 000000000..b70cf3ddb
--- /dev/null
+++ b/guide/glossary.md
@@ -0,0 +1,334 @@
+---
+layout: guide
+title: Glossary
+nav_order: 4
+---
+
+# Glossary
+{: .no_toc }
+
+## Address
+
+An identifier of 26-35 alphanumeric characters that is used to receive bitcoin. There are [several address formats](https://en.bitcoin.it/wiki/List_of_address_prefixes){:target="_blank"} based on different specifications. Users need to know this information during backup for future recovery so applications should inform users which format it uses as support varies across applications.
+
+When users enter an address, these formats have specific prefixes so it is possible to instantly determine which format is being used.
+
+These are the three most common ones:
+
+
+**Legacy address - [P2PKH](https://en.bitcoin.it/wiki/Transaction#Pay-to-PubkeyHash){:target="_blank"}**
+Stands for pay-to-pubkey-hash, i.e pay to a hash of the recipient’s public key. This was the original address format for bitcoin and is often called *legacy address*.
+
+*Legacy addresses* begin with the number 1, can contain upper and lowercase characters, and are case sensitive.
+For example: `1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2`
+
+**Script address - [P2SH](https://en.bitcoin.it/wiki/Pay_to_script_hash){:target="_blank"}**
+A script address can have code attached to enable additional rules and functionality. P2SH stands for pay-to-script-hash, and was defined in [BIP13](https://github.com/bitcoin/bips/blob/master/bip-0013.mediawiki). Script addresses are most commonly used for multi-sig addresses which can specify, for example, that signatures from several keys are required to authorize the transaction.
+
+*Script addresses* start with the number 3, can contain upper and lowercase characters, and are case sensitive.
+For example: `3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy`
+
+**SegWit address - [Bech32](https://en.bitcoin.it/wiki/Bech32){:target="_blank"}**
+The *SegWit* address format (for segregated witness) was introduced in an update to the Bitcoin protocol that made changes to the transaction format. The technical name of this address format is Bech32, and is specified in [BIP173](https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki){:target="_blank"}. SegWit addresses are supported by the majority of software and hardware wallets, but a minority of exchanges. SegWit address adoption by applications and exchanges is tracked on [this page](https://en.bitcoin.it/wiki/Bech32_adoption). Any new bitcoin-application should support the use of SegWit addresses.
+
+The benefits of SegWit addresses include more resistance to input errors (as they are case insensitive and use error-correcting codes), and lower transaction fees. The fee saving will depend on the type of transaction but for a common transfer of funds it can be in the 30-40% range.
+
+*SegWit addresses* start with `bc1` and are case insensitive.
+For example: `bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq`
+
+**Change address**
+When the output of a transaction is used as the input of another transaction, it must be spent in its entirety. Sometimes the value of the output is higher than what the user wishes to pay. In this case, the bitcoin client generates a new Bitcoin address, and sends the difference back to this address. This is known as *change address*.
+
+## Account
+
+Just like wallet, the term account can also be used for very different things. In bitcoin wallets that follow the hierarchy described in [BIP44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki){:target="_blank"}, a bitcoin wallet can have multiple accounts, with each one having its own addresses. However, account is also oftentimes used for accounts with third-party service providers.
+
+Differentiate between
+
+- Bitcoin wallet account
+- Service account
+
+## Bitcoin / bitcoin
+
+Bitcoin with a capital *B* is typically associated with Bitcoin the protocol and payment network. It is also often used to refer to as the ecosystem as a whole when writing about it in general terms. Bitcoin with a lowercase “b” written as “bitcoin” is usually associated specifically with bitcoin as the currency.
+
+## Bitcoin Core
+
+A Bitcoin wallet often considered as the *reference implementation* and serves as the specification of the Bitcoin protocol. It is the continuation of Satoshi Nakamoto's original code. More on the [Bitcoin Wiki](https://en.bitcoin.it/wiki/Bitcoin_Core).
+
+## BIP - Bitcoin improvement proposal
+
+A standardized technical document format for suggesting improvements to Bitcoin. They are hosted on Github [here](https://github.com/bitcoin/bips){:target="_blank"}. Some important proposals to be aware of:
+
+- [BIP39](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki){:target="_blank"}: Mnemonic code for generating deterministic keys
+- [BIP44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki){:target="_blank"}: Multi-account hierarchy for HD wallets
+- [BIP49](https://github.com/bitcoin/bips/blob/master/bip-0049.mediawiki){:target="_blank"}: Derivation scheme for HD wallets using nested SegWit
+- [BIP84](https://github.com/bitcoin/bips/blob/master/bip-0084.mediawiki){:target="_blank"}: Derivation scheme for HD wallets using SegWit
+- [BIP141](https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki){:target="_blank"}: SegWit, changes to transaction structure
+- [BIP173](https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki){:target="_blank"}: *Bech32* standard for native SegWit addresses
+- [BIP174](https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki){:target="_blank"}: Partially Signed Bitcoin Transaction Format
+
+## Coin control
+
+
+
+{% include image.html
+ image = "/assets/images/guide/glossary/coin-selection.jpg"
+ retina = "/assets/images/guide/glossary/coin-selection@2x.jpg"
+ alt-text = "Illustration of specific coins a user has received getting chosen for a new transacton."
+ layout = "float-right-desktop"
+ width = 400
+ height = 400
+%}
+
+The act of choosing which [unspent transaction output](#unspent-transaction-output-utxo) to forward to another address in a transaction. Wallet-applications can automatically choose the coins to use, but there are scenarios when users may want to manually choose what coins to send.
+
+Fees are based on transaction size, which is based on the number of outputs included. So choosing fewer outputs can reduce fees.
+
+As it is possible to trace the history of coins and see how they were previously spent, it may sometimes be warranted to not send certain coins because the recipient may be able to deduct personal information.
+
+
+
+## CoinJoin
+
+
+
+{% include image.html
+ image = "/assets/images/guide/glossary/coinjoin.jpg"
+ retina = "/assets/images/guide/glossary/coinjoin@2x.jpg"
+ alt-text = "Illustration of multiple senders and receives joining a single transaction."
+ layout = "float-right-desktop"
+ width = 400
+ height = 400
+%}
+
+ Allow for combining multiple payments from multiple spenders into a single transaction to make it harder to determine which spender paid which recipient(s). More information can be found on [the Bitcoin Wiki](https://en.bitcoin.it/wiki/CoinJoin){:target="_blank"}. See also [PayJoin]( {{ '/guide/glossary/#payjoin-p2ep' | relative_url }} ).
+
+
+
+
+## Derivation path
+
+There are several standards for how to notate the path to a key and corresponding address in [HD wallets](#hd-wallet). It is important to know which ones are used and supported by a wallet-application when importing and exporting a wallet. The most common are:
+
+- [BIP32](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki){:target="_blank"}: original, deprecated
+- [BIP44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki){:target="_blank"}: multi-account for HD wallets
+- [BIP49](https://github.com/bitcoin/bips/blob/master/bip-0049.mediawiki){:target="_blank"}: multi-account, for script addresses with nested-SegWit
+- [BIP84](https://github.com/bitcoin/bips/blob/master/bip-0084.mediawiki){:target="_blank"}: multi-account, for SegWit addresses
+
+BIP44 instroduced the following structure, which BIP49 and BIP84 follow:
+`m / purpose / coin_type / account / change / index`
+
+The path to the first address in a bitcoin-wallet using BIP84 will look like this:
+`m/84h/0h/0h/0/0`
+
+For full interoperability a wallet should support all of these standards. More information can be found [here](https://learnmeabitcoin.com/technical/derivation-paths).
+
+## Extended private key (XPRIV)
+
+In a hierarchical deterministic wallet, all addresses and their matching private keys are derived from this extended private key.
+
+## Extended public key (XPUB, YPUB, ZPUB)
+
+The master public key of a bitcoin account. All public addresses are generated from it.
+
+_ToDo: Explain how this is used for multisig and view-only wallets._
+
+### YPUB
+
+Same as XPUB however the Y denotes that this xpub belongs to a wallet that is following the [BIP49](https://github.com/bitcoin/bips/blob/master/bip-0049.mediawiki){:target="_blank"} standard that details the derivation scheme for wrapped-segwit addresses (P2WPKH-nested-in-P2SH).
+
+### ZPUB
+
+Same as YPUB though the Z denotes it is an extended public key from a segregated witness enabled wallet following [BIP49](https://github.com/bitcoin/bips/blob/master/bip-0049.mediawiki){:target="_blank"}.
+
+## Initial block download (IBD)
+
+To fully verify that all transactions on the bitcoin network are valid, a full node needs to download and examine all previous block-data. This is called the initial block download, after which the node has caught up with the latest transaction activity. This can take several hours, and only after it is complete can wallets linked to the node be used.
+
+## Input
+
+When an address receives bitcoin from another address, this is called an input. Transactions can include multiple inputs.
+
+## Keys
+Bitcoin wallets and addresses are have both [public](#public-key) and [private keys](#private-key) associated to them. The private key controls access to funds and the ability to sign (approve) transactions.
+
+## Miniscript
+
+A language for writing certain types of Bitcoin Scripts in a structured way. Miniscript is easier to read by developers, and also allows for various build-tools to help ensure that scripts are safe, valid, and efficient.
+
+**References:**
+
+- [Bitcoin Optech](https://bitcoinops.org/en/topics/miniscript/){:target="_blank"}
+- [Introduction](https://medium.com/blockstream/miniscript-bitcoin-scripting-3aeff3853620){:target="_blank"} by Blockstream
+
+## Multi-signature wallet (Multisig)
+Multi-signature wallets are bitcoin wallets that are controlled by more than one keypair. They can be defined by bitcoin scripts and use P2SH addresses. Common usecases and setups include *2-of-3*, or *3-of-5* multi-signature wallets that require a subset of the controlling keypairs to sign a transaction.
+
+## MuSig
+A standard for multi-signature that uses Schnorr signatures. Previously, the more signers participated in a transaction, the size of the transaction got larger and took more time to verify. It was also possible to see the number of signers in the final transaction. MuSig addresses both issues. It hides the number of signers for better privacy. MuSig also improves scalability by reducing the size of transactions and being more efficient to verify. The [original paper that describes MuSig](https://eprint.iacr.org/2018/068){:target="_blank"}.
+
+**References:**
+
+- [Proposal](https://eprint.iacr.org/2018/068){:target="_blank"} in the Cryptology ePrint archive
+
+## Node
+
+Node refers to [software]({{ '/guide/getting-started/software/#nodes' | relative_url }}) that participates in the bitcoin network. It exchanges transaction data with other nodes, stores some or all of it, and verifies that transactions are valid. There is also dedicated [node hardware]({{ '/guide/getting-started/hardware/#hardware-wallets' | relative_url }}).
+
+### Full node
+
+A node that fully verifies all transactions and rules of the Bitcoin network.
+
+### Pruned full node
+
+A node that fully verifies all of the rules of the Bitcoin network with a much smaller storage capacity because it only stores transactions relevant to the users wallet.
+
+### Archival node
+
+A full node that has not only verified all data, but also stores and provides it to other nodes on the network.
+
+## Output
+The opposite of an input, an output is when an address sends bitcoin to another address. Transactions can include multiple outputs.
+
+## Output script descriptor
+
+A small piece of data that has all the information needed to generate a specific set of addresses or keys. Bundling this data in a standardized format has several benefits. It is harder to forget important configuration details, and it is more efficient than transmitting a long list of addresses or keys.
+
+{% include picture.html
+ image = "/assets/images/guide/glossary/descriptors.jpg"
+ retina = "/assets/images/guide/glossary/descriptors@2x.jpg"
+ mobile = "/assets/images/guide/glossary/descriptors-mobile.jpg"
+ mobileRetina = "/assets/images/glossary/descriptors-mobile@2x.jpg"
+ alt-text = ""
+ width = 1600
+ height = 400
+%}
+
+## Private key
+Every bitcoin address has a public key and a corresponding private key, together they are called a keypair. If you have access to both the public and private key, you effectively control the funds in the address. As with HD Wallets there are also keypairs that control *branches* in the hierarchical tree of the wallet, and at the very top is the extended keypair (x-pub and x-prv for short) that control all the addresses in the wallet.
+
+The private key is a 64 hexadecimal (or 256 if described in binary 1’s and 0’s) character string generated by the encryption algorithm. They look something like this in hexadecimal form:
+
+`5KYZdUEo39z3FPrtuX2QbbwGnNP5zTd7yyr2SC1j299sBCnWjss`
+
+Or for the extended private key:
+
+`xprv9zrji5mK3nb4RbuR2ZYFtyzK3gn78KnEzkNP4ZxwwPPwcgQQVZqnjTMAGxmmM3jpmfsthQUtfD9iYPvnaqwejCjcyEswLqEhX4LPKNFUXT5`
+
+## Public key
+A bitcoin address' public key can be derived from the private key. The address itself is a hash of the public key.
+
+## Replace-by-fee (RBF)
+A node policy that allows an unconfirmed transaction to be replaced with a different transaction that spends at least one of the same inputs and which pays a higher transaction fee. This can sometimes be useful if a transaction has got *stuck* during times of higher-than-normal network-fees.
+
+## Recovery phrase
+
+_Also referred to as Seed, Mnemonic, and Backup phrase._
+
+The controlling keypair of a bitcoin wallet can be derived from a *recovery phrase* of 12 words (or 18 or 24, which is less common) from a standardized list, defined in [BIP39](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki){:target="_blank"}. The recovery phrase provides full access to a bitcoin wallet as it contains the private key and is therefore very valuable. It’s extremely important to keep it safe, both from other people getting access to it and for yourself not to lose it by creating one or several backups of the phrase. In many applications most of this work falls on the user and it’s important to acknowledge the responsibility here of the makers of the application to ensure that the user is able and aware of how to securely store a recovery phrase backup.
+
+Many wallet-applications work with HD Wallets and recovery phrases, and are interoperable, meaning you can change the application that can control your wallet should you wish (although there are some caveats depending on if they support just BIP32 or also BIP44).
+
+**Technicalities** - Recovery of multisig-wallets needs both the extended public key and the recovery phrase of all paticipating keys as well as the master key fingerprint as defined by BIP32 concatenated with the derivation path of the public key. The derivation path is represented as 32-bit little endian unsigned integer indexes concatenated with each other. The number of 32 bit unsigned integer indexes must match the depth provided in the extended public key.
+
+## Simplified payment verification (SPV)
+ It is possible to verify bitcoin payments without running a full network node. This is called simplified payment verification, or SPV. A user’s bitcoin spv wallet only needs a copy of the block headers of the longest chain, which are available by querying network nodes until it is apparent that the longest chain has been obtained. SPV lets you validate your transactions without having to worry about anybody else’s transactions. It ensures your transactions are in a block, and it provides confirmations that additional blocks are being added to the chain. An SPV wallet is a type of bitcoin wallet that works this way.
+
+**References:**
+
+- [WabiSabi](https://github.com/zkSNACKs/WabiSabi/blob/master/explainer.md){:target="_blank"}
+- [Bitcoin wiki](https://en.bitcoin.it/wiki/CoinJoin){:target="_blank"}
+
+## PayJoin (P2EP)
+
+A type of [CoinJoin](#coinjoin) for direct transactions between two parties that makes it harder to understand the ownership of the inputs included in the transaction. The sender creates a partial transaction that the recipient adds another input to. Then the sender broadcasts the transaction. The same amount of bitcoin is transferred as in a simple bitcoin transaction. However, the additional input from the recipient makes it harder to analyze from the outside what happened in the transaction.
+
+## Schnorr signature
+
+An algorithm to generate cryptographic signatures. One of the benefits is that the size of multi signature transactions can be reduced, resulting in lower fees, and that multisignature transactions will appear equal to single signature, increasing privacy (see [MuSig](#musig)). The code for this improvement was merged in Bitcoin Core in September 2020.
+
+**References:**
+
+- [Wikipedia](https://en.wikipedia.org/wiki/Schnorr_signature){:target="_blank"}
+- [Bitcoin wiki](){:target="_blank"}
+- [BIP340](){:target="_blank"}
+
+## Segregated witness (SegWit)
+Segregated Witness, or SegWit, is the name for a soft fork change in the transaction format of Bitcoin. It was described in [BIP141](https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki){:target="_blank"}. It was intended to mitigate a blockchain size limitation problem that reduces bitcoin transaction speed. It does this by splitting the transaction into two segments, removing the unlocking signature (*witness* data) from the original portion and appending it as a separate structure at the end. The original section hold the sender and receiver data, and the new *witness* structure contain scripts and signatures.
+
+## Taproot
+
+A technique that makes complex multisig transactions look the same as standard transactions on the blockchain. This improves both efficiency and privacy, as multiple signatures are combined into a single one.
+
+## Transaction
+*ToDo*
+
+## Unspent transaction output (UTXO)
+An output that has not been sent to another address. The bitcoin wallet balance is calculated from adding up unspent outputs.
+
+## Partially signed bitcoin transaction (PSBT)
+A file format for bitcoin transactions that are not fully signed yet. Allows for passing around a transaction to other applications or devices for signing, for example in a multi signature wallet setup.
+
+**References:**
+
+- [BIP174](https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki){:target="_blank"}: Partially Signed Bitcoin Transaction Format
+
+## Vault
+
+A term sometimes used for multi-signature wallets.
+
+## Wallet
+
+
+
+{% include image.html
+ image = "/assets/images/guide/glossary/wallet.jpg"
+ retina = "/assets/images/guide/glossary/wallet@2x.jpg"
+ alt-text = "Illustrations of different types of wallets."
+ layout = "float-right-desktop"
+ width = 400
+ height = 300
+%}
+
+This term is often used interchangeably for very different things. A user can *download a bitcoin wallet* in the app store, and then the app may offer the option to “create a new wallet” on the home screen. A software wallet may allow for browsing and sending transactions, while a hardware wallet may be limited to key storage and signing functionality.
+
+
+
+### Bitcoin wallet
+
+All bitcoin-related data derived from and associated with a single recovery phrase. Most modern bitcoin wallets are HD wallets.
+
+### HD wallet
+
+Hierarchical Deterministic wallets, or HD wallets, can create infinite keypairs organized in a tree-structure (hierarchical) from a single (deterministic) controlling keypair. They were introduced and defined in [BIP32](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki){:target="_blank"} and then expanded with [BIP44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki){:target="_blank"} which added the ability to handle multiple *accounts* in one wallet.
+
+**Technicalities** - There are different bitcoin address formats (see [address](#address)). They have to be held in different branches of the HD wallet but can be controlled by the same recovery phrase.
+
+### Hardware wallet
+
+A hardware device used to manage a bitcoin wallet. More on the [Hardware overview]({{ '/guide/getting-started/hardware/#hardware-wallets' | relative_url }}) page.
+
+### Wallet application
+
+A software application used to manage a bitcoin wallet. More on the [Hardware overview]({{ '/guide/getting-started/software/#wallets' | relative_url }}) page.
+
+### Non-custodial / Custodial wallet
+
+_Also known as unhosted / self-hosted / hosted wallet._
+
+A non-custodial wallet-application implies that the private key and/or recovery phrase is in full control of the end-user. This means that transactions can never be made without the user's direct action. It also means that should the user forget or misplace their recovery phrase, wallet-application makers cannot help restore access to the funds in the bitcoin wallet. _This guide is focused on non-custodial wallets._
+
+With a custodial wallet-application, the users are not exposed to and in charge of securing the recovery phrase. Often custodial wallet-applications require users to sign in with their email and password. Users have to trust the wallet-application makers to secure their recovery phrase and bitcoin. With a custodial wallet-application, the makers of it are technically in control of their users' funds. Most exchanges give users custodial wallets.
+
+### Hot / Cold wallet
+
+*Hot* and *cold* describe a wallet in terms of being connected to the internet. Where a hot wallet is connected to the internet, a cold wallet is not. The idea is that a cold wallet is less susceptible to third-party theft over the internet. Most software wallet-application would be seen as hot (although some can be used just for signing on a device not connected to the internet) and most hardware wallet-application would be seen as cold (although they are sometimes connected for signing purposes).
+
+## Additional resources
+
+- [Bitcoin.org](https://bitcoin.org/en/vocabulary){:target="_blank"}
+- [Bitcoin Q + A glossary](https://www.bitcoinqna.com/glossary){:target="_blank"}
+- [Bitcoin Wiki](https://en.bitcoin.it/wiki/Main_Page){:target="_blank"}
+- [Bitcoin Optech style guide](https://github.com/bitcoinops/bitcoinops.github.io/blob/master/STYLE.md){:target="_blank"}
+- [Bitcoin Optech topics](https://bitcoinops.org/en/topics/){:target="_blank"}
diff --git a/guide/private-key-management/case-studies.md b/guide/private-key-management/case-studies.md
new file mode 100644
index 000000000..a374f4292
--- /dev/null
+++ b/guide/private-key-management/case-studies.md
@@ -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
+---
+
+
+
+{% 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
+
+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.
+
+
+
+#### 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.
+
+
+
+#### 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
+
+
+
+#### 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.
+
+
+
+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"}.
diff --git a/guide/private-key-management/introduction.md b/guide/private-key-management/introduction.md
index 54e9dee54..95fa093fa 100644
--- a/guide/private-key-management/introduction.md
+++ b/guide/private-key-management/introduction.md
@@ -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
---
+
+
+{% 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.
+
+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 }}).
diff --git a/guide/private-key-management/multi-user-schemes.md b/guide/private-key-management/multi-user-schemes.md
new file mode 100644
index 000000000..6a6f5842f
--- /dev/null
+++ b/guide/private-key-management/multi-user-schemes.md
@@ -0,0 +1,90 @@
+---
+layout: guide
+title: Shared schemes
+description: An overview of shared private key management schemes.
+nav_order: 3
+parent: Private key management
+permalink: /guide/private-key-management/multi-user-schemes/
+main_classes: -no-top-padding
+image: /assets/images/guide/private-key-management/schemes/page-shared-schemes.jpg
+---
+
+
+
+{% include picture.html
+ image = "/assets/images/guide/private-key-management/shared.jpg"
+ retina = "/assets/images/guide/private-key-management/shared@2x.jpg"
+ mobile = "/assets/images/guide/private-key-management/shared-mobile.jpg"
+ mobileRetina = "/assets/images/guide/private-key-management/shared-mobile@2x.jpg"
+ alt-text = "Shared schemes header illustration"
+ width = 1600
+ height = 600
+ layout = "full-width"
+%}
+
+# Shared schemes
+
+While multi-key setups can be used for personal use, if several people need to share funds multiple keys become a necessity. You will often see this referred to as *multi-sig* setups, stemming from the fact that multiple keys are needed to sign a transaction in order for it to go through and be valid.
+
+The use cases for shared schemes include spouses managing a joint account, groups, organizations or companies managing their funds, as well as inheritance planning. It can also be used for governance of an organization, with transactions used not to transfer funds but to record, or vote, for decisions.
+
+## Shared multi-key
+
+As we saw with multi-key setups for personal use, a multi-key wallet has several controlling keypairs attached, or what is often called co-signers. The number of keys and required co-signers will depend on the use case. With spouses sharing a *joint account*, a simple 1-of-2 multi-key setup might suffice, meaning there are two keys but only one is required to sign for a transaction to be valid. At the other end of a spectrum a company might require a more complex 3-of-5 setup, requiring three of the five co-signers to approve any transaction.
+
+Just like with personal schemes, external signing devices can be used to hold one or several of the keys used for a shared multi-key setup. While this can increase security if managed correctly, the same caveat applies in terms of adding significant complexity.
+
+{% include image.html
+ image = "/assets/images/guide/private-key-management/schemes/shared-multi-key.jpg"
+ retina = "/assets/images/guide/private-key-management/schemes/shared-multi-key@2x.jpg"
+ alt-text = "Shared multi-key illustration"
+ caption = "Several users can control the wallet with a combination of the keys."
+ width = 800
+ height = 400
+%}
+
+### How it works
+A wallet or coordination application initiates a multi-sig wallet, choosing the number of total keys, and the number required to sign transactions. It then needs to add private keys from the other user's wallet. It can then complete the creation process. For any future transaction from the multi-sig wallet the required amount of co-signers need to sign (using Partially Signed Bitcoin Transactions - PSBT from [BIP174]({{ 'https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki'}}){:target="_blank"}) before any transaction is valid.
+
+#### Pros
+- Allows several people to access and control a bitcoin wallet
+- Can tailor requirements for multiple co-signers and access
+- High security, if setup well
+
+#### Cons
+- Has significant complexity and op-sec burden for multiple private keys, each of which might need a good manual backup scheme
+
+### Best practice
+
+**When to use**
+- When funds need to be accessed by several people or an organization
+- When users are likely to be very knowledgeable or be guided through setup and use
+
+**When not to use**
+- (No other option currently for shared access scenarios)
+
+**Variations**
+- The number of required co-signers and attached keypairs
+- Key storage devices
+
+**Do's**
+- Make sure the multi-key setup itself is backed up properly, including x-pubs for all the participating keys, fingerprint and derivation.
+
+**Products that use this scheme**
+Few tailor-made products exist for shared wallets, but any wallet application that supports multi-key setups can be used to initiate a shared wallet.
+- [Electrum](https://electrum.org){:target="_blank"}
+- [Bluewallet](https://bluewallet.io){:target="_blank"}
+- [Specter](https://specter.solutions){:target="_blank"}
+- [Armory](https://btcarmory.com){:target="_blank"}
+- [Guarda](https://guarda.com){:target="_blank"}
+- [Revault](https://revault.dev){:target="_blank"} - in development
+
+---
+
+Next up, common [principles]({{ '/guide/private-key-management/principles/' | relative_url }}) we should strive to follow.
\ No newline at end of file
diff --git a/guide/private-key-management/principles.md b/guide/private-key-management/principles.md
new file mode 100644
index 000000000..8d98d314a
--- /dev/null
+++ b/guide/private-key-management/principles.md
@@ -0,0 +1,61 @@
+---
+layout: guide
+title: Principles
+description: Principles to strive for while building bitcoin applications for end-users.
+nav_order: 4
+parent: Private key management
+permalink: /guide/private-key-management/principles/
+main_classes: -no-top-padding
+image: /assets/images/guide/private-key-management/principles/page-principles.jpg
+---
+
+
+
+{% include picture.html
+ image = "/assets/images/guide/private-key-management/principles.jpg"
+ retina = "/assets/images/guide/private-key-management/principles@2x.jpg"
+ mobile = "/assets/images/guide/private-key-management/principles-mobile.jpg"
+ mobileRetina = "/assets/images/guide/private-key-management/principles-mobile@2x.jpg"
+ alt-text = "Principles header illustration"
+ width = 1600
+ height = 600
+ layout = "full-width"
+%}
+
+# Principles
+
+Although every use case and product is different, there are a number of things that all wallet applications should strive for. Diverging from them should only be done with good reason.
+
+## No loss of funds
+
+Even though non-custodial wallet-makers don’t technically hold their users’ funds, and are less exposed to regulation, you are still providing a financial service product. It is essential to take the safekeeping of users’ funds seriously. Regardless of how loss could occur, whether it is self-inflicted or through theft, you should have thought this through and implemented adequate measures for the risk-profile of the use-case. This includes not simply blaming a first-time bitcoin user for not manually backing up their recovery phase when you told them to.
+
+Any loss is ultimately bad for both the user, the wallet application maker and the whole bitcoin community. Strive for *No loss of funds*.
+
+## Interoperability
+
+The bitcoin community is firmly built on open-source, decentralization, and the idea that the individual should be in full control of their funds. This has led to a number of standards that should make it fairly easy to switch and move your bitcoin wallet to a different wallet application. Making sure that your product supports these standards when relevant is best practice and builds trust.
+
+At a minimum, strive for supporting interoperability by enabling import and export, and using standard [address]({{ '/guide/glossary/#address' | relative_url }}){:target="_blank"} derivation schemes.
+
+## Privacy
+
+A common misconception of bitcoin is that it provides anonymity and privacy of transactions. Since the blockchain is literally an unchangeable ledger of all bitcoin transactions ever made, it is in fact very hard to not have your complete transaction history visible to knowledgable parties once even a single one of your addresses is connected to you. If bitcoin is to become viable for a wider audience and daily use we ought to take privacy seriously. This is certainly not to enable or encourage illicit activity, but to protect individual financial privacy. We would not accept our bank to publish our financial transactions publicly. So when building wallet-applications we should strive to implement best practice for maintaining and improving the financial privacy of bitcoin.
+
+At a minimum, make it easy for your customers to avoid address re-use.
+
+## Progressive security
+
+While it is possible to own and store immense wealth in a non-custodial bitcoin wallet, most new users of bitcoin are likely to start with much smaller sums before they get comfortable with depositing material parts of their savings in a wallet where they are responsible for security. There are many guides out there for how to best keep your recovery phrase backup safe, and conduct advanced op-sec to minimise every conceivable threat-vector. This might be appropriate for someone already intimately familiar with bitcoin technology, but is very likely both overkill and scary to the point of turning away new users. Think carefully about who your target customer is and choose a private key management scheme that is well suited to them.
+
+Strive for your product to grow with the user and provide progressively stronger security. For example, offering the ability to *sweep* a wallet into a new one, with a higher level security scheme once certain thresholds are reached. This way, a beginner could start out with an automatic cloud backup scheme but know that as they grow their funds could upgrade to a multikey setup down the line.
+
+***
+
+OK, let's have a look at some [case studies]({{ '/guide/private-key-management/case-studies/' | relative_url }}).
diff --git a/guide/private-key-management/schemes.md b/guide/private-key-management/schemes.md
new file mode 100644
index 000000000..ef1de1a0a
--- /dev/null
+++ b/guide/private-key-management/schemes.md
@@ -0,0 +1,97 @@
+---
+layout: guide
+title: Private key schemes
+description: An overview of personal and shared schemes, and how to pick one for your product depending on your use case.
+nav_order: 1
+parent: Private key management
+permalink: /guide/private-key-management/schemes/
+main_classes: -no-top-padding
+image: /assets/images/guide/private-key-management/schemes/page-private-key-schemes.jpg
+---
+
+
+
+{% include picture.html
+ image = "/assets/images/guide/private-key-management/schemes.jpg"
+ retina = "/assets/images/guide/private-key-management/schemes@2x.jpg"
+ mobile = "/assets/images/guide/private-key-management/schemes-mobile.jpg"
+ mobileRetina = "/assets/images/guide/private-key-management/schemes-mobile@2x.jpg"
+ alt-text = "Schemes header illustration"
+ width = 1600
+ height = 600
+ layout = "full-width"
+%}
+
+# Private key schemes
+The private key controls the bitcoin [wallet]({{ '/guide/glossary/#wallet' | relative_url }}){:target="_blank"}, and the *scheme* is simply a way to describe how the key is stored and kept secure.
+
+Important aspects to consider when choosing a private key management scheme is what you expect your users to use the wallet application for, who they are and how much bitcoin they might store in your product. For example:
+
+
+* **Target audience** - Are your users completely new to bitcoin and its concepts, or well versed in all the technological underpinnings?
+* **Use case** - Are you building a product for daily payments, or a long-term life-saving storage solution?
+* **Value stored** - While we always strive for no loss of funds, how critical to their financial situation would it be if your user lost access to their funds?
+
+
+The narrower you can define your answer to these questions, the easier it will be to pick the right private key management scheme, and provide a great user experience. If you find yourself wanting to target a wide range, it might be a good idea to use a progressive scheme that changes as the user’s funds and familiarity with bitcoin grows.
+
+## Balancing security, risk and convenience
+
+The trick to picking a private key management scheme is finding the appropriate balance between convenience on the one hand, and risk of loss and redundant security on the other. While learnings over the last decade mean we can now enable higher security and good user experience at the same time, there is always a balance. Higher security generally means more friction and work for the user, both during setup and usage of a wallet application.
+
+There are many potential threat-vectors for users of non-custodial wallet applications. People will be exposed differently to these vectors, and be more or less comfortable with their risk in each.
+
+As a simplification we can characterize the main potentials for loss of funds as;
+
+* **Self inflicted** - you lose access to your own private key
+* **Theft** - a third party gains access to your private key
+
+So your goal is to make it hard for users to lose their keys, and at the same time, make it hard for a third party to get to them.
+
+Casa's [wealth security protocol]({{ 'https://github.com/Casa/wealth-security-protocol/blob/master/casa-wealth-security-protocol.pdf'}}){:target="_blank"} is good reading material for more complete views on threat vectors and risk.
+
+## Picking a scheme for your product
+
+Now that you have a clear picture of your use case, target audience and risk vectors we can consider which schemes might be suitable for your product.
+
+{% include image.html
+ image = "/assets/images/guide/private-key-management/schemes/spectrum.jpg"
+ retina = "/assets/images/guide/private-key-management/schemes/spectrum@2x.jpg"
+ alt-text = "Private key management schemes, spectrum"
+ caption = "The range of private key management schemes."
+ width = 2084
+ height = 982
+ layout = "full-width"
+%}
+
+{% include image.html
+ image = "/assets/images/guide/private-key-management/schemes/flow-chart.jpg"
+ retina = "/assets/images/guide/private-key-management/schemes/flow-chart@2x.jpg"
+ alt-text = "Private key management schemes, flowchart"
+ caption = "A flow-chart for picking a scheme based on use case."
+ width = 2226
+ height = 1416
+ layout = "full-width"
+%}
+
+We can divide the options up into personal and shared wallet schemes. The following pages explain each one in more detail:
+
+### [Personal schemes]({{ '/guide/private-key-management/single-user-schemes/' | relative_url }})
+- **Automatic cloud backup** - no user action required for backup
+- **Manual backup / Recovery phrase** - manual backup of a phrase of words
+- **External signing device** - keys are held on a separate device
+- **Threshold signatures / Key-sharing** - one key is split and distributed
+- **Multi-key** - several keys jointly control the wallet
+
+### [Shared schemes]({{ '/guide/private-key-management/multi-user-schemes/' | relative_url }})
+- **Multi-key** - several keys and several people control the wallet
+
+---
+
+Let's continue by looking at [personal schemes]({{ '/guide/private-key-management/single-user-schemes/' | relative_url }}).
diff --git a/guide/private-key-management/single-user-schemes.md b/guide/private-key-management/single-user-schemes.md
new file mode 100644
index 000000000..7a35c271c
--- /dev/null
+++ b/guide/private-key-management/single-user-schemes.md
@@ -0,0 +1,334 @@
+---
+layout: guide
+title: Personal schemes
+description: An overview of personal private key management schemes.
+nav_order: 2
+parent: Private key management
+permalink: /guide/private-key-management/single-user-schemes/
+main_classes: -no-top-padding
+image: /assets/images/guide/private-key-management/schemes/page-personal-schemes.jpg
+---
+
+
+
+{% include picture.html
+ image = "/assets/images/guide/private-key-management/personal.jpg"
+ retina = "/assets/images/guide/private-key-management/personal@2x.jpg"
+ mobile = "/assets/images/guide/private-key-management/personal-mobile.jpg"
+ mobileRetina = "/assets/images/guide/private-key-management/personal-mobile@2x.jpg"
+ alt-text = "Personal schemes header illustration"
+ width = 1600
+ height = 600
+ layout = "full-width"
+%}
+
+# Personal schemes
+
+Now let's dive in and look at the various schemes that might be suitable for a personal wallet application with a single user to understand the differences at a high level.
+
+{% include image.html
+ image = "/assets/images/guide/private-key-management/schemes/personal-schemes.jpg"
+ retina = "/assets/images/guide/private-key-management/schemes/personal-schemes@2x.jpg"
+ alt-text = ""
+ caption = "Cloud backup, manual backup , signing-device, threshold-signatures and multi-key."
+ width = 2012
+ height = 400
+%}
+
+- [Automatic cloud backup]({{ '/guide/private-key-management/single-user-schemes/#automatic-cloud-backup' | relative_url }})
+- [Manual backup / Recovery phrase]({{ '/guide/private-key-management/single-user-schemes/#recovery-phrase' | relative_url }})
+- [External signing device]({{ '/guide/private-key-management/single-user-schemes/#external-signing-device' | relative_url }})
+- [Threshold signatures / Key-sharing]({{ '/guide/private-key-management/single-user-schemes/#threshold-signatures--key-sharing' | relative_url }})
+- [Multi-key]({{ '/guide/private-key-management/single-user-schemes/#multi-key' | relative_url }})
+
+***
+
+## Automatic cloud backup
+
+By using an automatic cloud backup for the private key the user is NOT required to manually backup anything when setting up a new [bitcoin wallet]({{ '/guide/glossary/#bitcoin-wallet' | relative_url }}){:target="_blank"}. This is sometimes also called *seedless*, as the user is never exposed to the traditional *seed*, or [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }}){:target="_blank"} that is used to initiate a wallet.
+
+This scheme can be used for those new to bitcoin, or novices who would find manually backing up a recovery phrase during onboarding confusing, possibly leading to unsafe backups. It could also be a starting point for a progressive security model that lets customers upgrade when they start accumulating more funds.
+
+The automatic cloud backup scheme gives users reasonable security against theft, while providing low risk for self-inflicted losses.
+
+{% include image.html
+ image = "/assets/images/guide/private-key-management/schemes/cloud-backup.jpg"
+ retina = "/assets/images/guide/private-key-management/schemes/cloud-backup@2x.jpg"
+ alt-text = "Automatic cloud backup illustration"
+ caption = "Private keys are encrypted and stored in the cloud."
+ width = 800
+ height = 400
+%}
+
+### How it works
+First the application generates a wallet with a keypair. Then, the key is encrypted and backed up to a location convenient and safe for the user, yet hard for a malicious third-party to gain access to.
+
+
+With most implementations so far, the location will be the keychain or a user-specific key-value-store on a mobile device that is also backed up by the OS provider. The most common would be iOS (iCloud) and Android (Google Drive) which both have secure data storage that is backed up and synced between a user's devices.
+
+This makes the backup accessible by the user on a new device, should they lose the original, but only accessible by someone that can log into the user’s Apple or Google account.
+
+#### Pros
+- Low onboarding friction
+- Low risk of self-inflicted loss due to the automatic nature
+
+#### Cons
+- Private key in cloud storage increases risk of malicious third party access
+- User needs to trust their OS and cloud storage provider
+- Unless the backup includes the recovery phrase users will not be able to export their wallet to another product
+
+### Best practice
+
+**When to use**
+- When risk of self-inflicted loss is higher than loss from theft
+- For beginners, or products with progressive security
+- For lower values
+
+**When not to use**
+- When storing high values
+- When risk of loss from theft is higher than self-inflicted loss
+- When complete self-sovereignty is important to the target audience
+
+**Variations**
+- Storage location (keychain, iCloud, Google Drive, One Password etc.)
+- Additional user authentication (biometrics, pin)
+
+**Products that use this scheme**
+- [Photon SDK](https://photonsdk.org){:target="_blank"} - for use by other wallets, in development
+- [Casa](https://keys.casa){:target="_blank"}
+- [Pine](https://pine.pm ){:target="_blank"} - Lightning, beta
+
+***
+
+## Manual backup / Recovery phrase
+
+Manual backup of the [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }}){:target="_blank"} has been the most common private key management scheme by far since its proposal with [BIP39](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki){:target="_blank"} in 2013. If you have used any [non-custodial]({{ '/guide/glossary/#non-custodial--custodial-wallet' | relative_url }}){:target="_blank"} bitcoin application you are likely to have experienced the onboarding requirements of manual backups.
+
+When creating a new wallet, you will be asked to manually backup a 12 or 24 word recovery phrase to a *safe place*. Often, as the next step it will ask you to verify that you did save it by having you input the phrase in the correct order.
+
+This scheme is suitable for users who are already familiar with bitcoin and procedures for secure offline backups of their recovery phrase. It is not suited for complete beginners. When told to store the backup in a safe way offline, bitcoin-beginners in reality often take a screenshot, write it down in plain text somewhere on their mobile device, computer or a piece of paper on the fridge, or simply don’t back it up at all. This has the risk of achieving the opposite of what we want - high risk of self-inflicted loss and low to medium security in terms of third party theft.
+
+{% include image.html
+ image = "/assets/images/guide/private-key-management/schemes/recovery-phrase.jpg"
+ retina = "/assets/images/guide/private-key-management/schemes/recovery-phrase@2x.jpg"
+ alt-text = "Recovery phrase illustration"
+ caption = "Recovery phrases should be stored offline on metal or paper backups."
+ width = 800
+ height = 400
+%}
+
+### How it works
+The wallet application will generate a 12 or 24 word phrase (seed / [recovery phrase]({{ '/guide/glossary/#recovery-phrase' | relative_url }}){:target="_blank"}) from which all the wallet’s [keys]({{ '/guide/glossary/#keys' | relative_url }}){:target="_blank"} can be derived. This means the user can have access to the wallet from any compatible wallet application with the phrase, even if they lose the device or software.
+
+This can be an effective way to reduce the risk of loss from theft if the backup is offline in a safe place, but puts more of the op-sec burden on the individual user. The security and risk will only be as good as how they backup the recovery phrase. You need to take resistance to physical theft, fire and other destructive events into account. To get the best security out of recovery phrases they should be kept on several dedicated [metal storage pieces](https://jlopp.github.io/metal-bitcoin-storage-reviews/){:target="_blank"} in secure places offline. A fair amount of effort and knowledge is required for this.
+
+A full guide to manual backup best practices for users is out of scope for this chapter but the [Do's and Dont's](https://blog.keys.casa/the-dos-and-donts-of-bitcoin-key-management/){:target="_blank"} of Bitcoin key management is a good starting point.
+
+#### Pros
+- Manual backups done well can provide very high security
+- Good interoperability
+
+#### Cons
+- Requires significant effort from users to achieve safe backups
+- High onboarding friction
+
+### Best practice
+
+**When to use**
+- When target audience is likely to be knowledgeable and implement good manual backup schemes
+- When storing medium amounts
+- When risk of loss from theft is higher than self-inflicted loss
+
+**When not to use**
+- When users are new to bitcoin and unlikely to implement good manual backups
+- For use-cases with small amounts
+- When onboarding is likely to happen outside of users' homes
+
+**Variations**
+- 12 or 24 word phrase
+- Additional user authentication (biometrics use, pin or password)
+- Cloud backup options
+
+**Do's**
+- Explain what a recovery phrase is, and provide a guide how to do *safe offline backups* BEFORE the user is exposed to the phrase or can start using the wallet
+
+**Products that use this scheme**
+Most bitcoin wallets, including;
+- [Bluewallet](https://bluewallet.io){:target="_blank"}
+- [Electrum](https://electrum.org){:target="_blank"}
+- [Wasabi](https://wasabiwallet.io){:target="_blank"}
+- [Blockstream Green](https://blockstream.com/green/){:target="_blank"}
+- [Coinbase Wallet](https://wallet.coinbase.com){:target="_blank"}
+- [Rise](https://www.risewallet.com){:target="_blank"}
+
+***
+
+## External signing device
+
+The most common external signing devices are hardware wallets who’s makers often provide their own software to pair with. But, there are also third party wallet applications that support external signing, or software, that can be run on offline on airgapped computers to perform the same function.
+
+A wallet application that supports external signing can remove the need for the private key to be readable by the wallet software, thereby decreasing the risk of keeping keys on a device that is likely always connected to the internet.
+
+{% include image.html
+ image = "/assets/images/guide/private-key-management/schemes/signing-devices.jpg"
+ retina = "/assets/images/guide/private-key-management/schemes/signing-devices@2x.jpg"
+ alt-text = "External signing device illustration"
+ caption = "Hardware wallets are the most common external signing devices."
+ width = 800
+ height = 400
+%}
+
+### How it works
+The external device can generate and store a keypair offline. Therefore, the private key has never been known outside the device. A software wallet can connect to the signing device and act as an interface, or handle transactions air gapped from the device.
+
+When a transaction needs to be signed, the software submits a partially signed bitcoin transaction (PSBT, defined in [BIP174]('https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki'){:target="_blank"}) to the device. The user confirms on the device and the PSBT state of the transaction returned to the software wallet application is now fully signed and can be transmitted to the blockchain. This process can also happen fully air gapped by using memory cards instead of cables or wireless connections, to keep the device offline at all times.
+
+#### Pros
+- Removes private key from online devices
+- Can provide very high security if used correctly
+
+#### Cons
+- Purchase of specialized hardware required
+- Requires further effort and knowledge to setup correctly
+- Still requires a good manual backup for redundancy
+
+### Best practice
+
+**When to use**
+- When storing medium to large amounts
+- When risk of loss from theft is higher than loss from negligence
+- When target audience is likely to be very knowledgeable or motivated to learn good manual backup schemes
+
+**When not to use**
+- When most users are new to bitcoin and unlikely to implement good backup schemes
+- When transactions are likely to be frequent and low value
+
+**Variations**
+- Interfaces (bluetooth, USB, microSD card, camera, NFC)
+- Platform compatibility
+- Additional user authentication (pin or password)
+
+**Products that use this scheme**
+- [Electrum]({{ 'https://electrum.org'}}){:target="_blank"}
+- [Wasabi]({{ 'https://wasabiwallet.io'}}){:target="_blank"}
+- [Bluewallet]({{ 'https://bluewallet.io'}}){:target="_blank"}
+
+**Hardware wallets**
+- [Trezor]({{ 'https://trezor.io'}}){:target="_blank"}
+- [Ledger]({{ 'https://www.ledger.com'}}){:target="_blank"}
+- [Keepkey]({{ 'https://shapeshift.com/keepkey'}}){:target="_blank"}
+- [Coldcard]({{ 'https://coldcardwallet.com'}}){:target="_blank"}
+
+***
+
+## Threshold signatures / Key-sharing
+
+A threshold signature scheme can require n-of-n signatures from parts of a single private key to make a valid transaction. By sharing parts of the private key among several parties or locations, greater resistance to theft can be achieved since access to more than one share is required. Depending on the setup, resistance to self-inflicted loss can be similar or worse than with a single key (2-of-2) or better (2-of-3 or more).
+
+Some benefits over a multikey setup include greater privacy, as a transaction using threshold signatures will appear equal to a single key transaction and not expose details about the different key shares. Transactions will also incur lower fees than a multikey setup as only one signature will be recorded on-chain. The big caveat here however is that these advantages are true only with the current ECDSA signatures of bitcoin, while with the forthcoming Schnorr signature scheme multikey signatures will be indistinguishable from single key.
+
+{% include image.html
+ image = "/assets/images/guide/private-key-management/schemes/threshold-signatures.jpg"
+ retina = "/assets/images/guide/private-key-management/schemes/threshold-signatures@2x.jpg"
+ alt-text = "Threshold signatures illustration"
+ caption = "One key is split into several pieces, more than one are required for controlling the wallet."
+ width = 800
+ height = 400
+%}
+
+### How it works
+A single private key is split into n key-shares that are distributed to several parties, devices or locations. When signing a transaction the required number of shares need to be coordinated into one valid signature. This relies on a cryptographic algorithm called [Shamir's Secret Sharing](https://en.wikipedia.org/wiki/Shamir's_Secret_Sharing){:target="_blank"} after its creator.
+
+#### Pros
+- Can provide higher resistance to loss from theft
+- Transactions look identical and have same cost as single key wallets on chain
+
+#### Cons
+- Requires precise coordination of key-shares when signing
+- Few advantages over multi-key setups with Schnorr signatures
+- Individual product implementations not interoperable
+
+### Best practice
+
+**When to use**
+- When target audience is well-versed with bitcoin
+- When risk of theft is higher than self-inflicted loss
+
+**When not to use**
+- When Schnorr signatures are available, enabling multi-key setups with similar benefits
+
+**Variations**
+- Number of signatures required
+- Location and distribution of pieces
+- Signing procedure
+
+**Products that use this scheme**
+- [ZenGo](https://zengo.com){:target="_blank"}
+- [Hexa](https://hexawallet.io){:target="_blank"}
+- [Spatium](https://spatium.net){:target="_blank"}
+- [Bitfreeze](https://medium.com/@bitfreeze/threshold-signatures-multisig-is-not-enough-e1ba468f6102){:target="_blank"} - No longer in active development
+
+***
+
+## Multi-key
+All of the above schemes have relied on a single private key to control the wallet. This presents an all-or-nothing risk for loss of funds from both theft and negligence. To counter this a wallet can have several private keys attached of which all or a subset need to sign any transactions. In the personal use case, one person will control all the keys but hold them on different devices, or in different places.
+
+This is often called multi-signature, or multisig for short, but is also sometimes referred to as a *vault*. A multi-key setup is described as *n-of-n* to indicate how many keys are needed to sign a transaction out of the issued number. For example a *2-of-3* setup requires two of the three private keys to sign a transaction for it to be valid.
+
+Multi-key schemes can raise the security, since anyone needs access to more than one key to move any funds. But clearly it also increases complexity and the requirements on the user to keep even more keys securely stored and/or backed up.
+
+{% include image.html
+ image = "/assets/images/guide/private-key-management/schemes/multi-key.jpg"
+ retina = "/assets/images/guide/private-key-management/schemes/multi-key@2x.jpg"
+ alt-text = "Multi-key illustration"
+ caption = "Several keys are required to control the wallet."
+ width = 800
+ height = 400
+%}
+
+### How it works
+A software wallet application or coordination software initiates a multi-sig wallet, choosing the number of total keys, and the number required to sign transactions. The user then adds private keys from other wallets generated elsewhere to the multisig after which the software wallet can complete the creation process. For any future transaction from the multi-sig wallet the required amount of co-signers need to sign (using Partially Signed Bitcoin Transactions - PSBT from [BIP174](https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki){:target="_blank"}) before any transaction is valid.
+
+#### Pros
+- Significantly increases security against theft
+
+#### Cons
+- Adds complexity and op-sec burden for multiple private keys
+
+### Best practice
+
+**When to use**
+- When storing large amounts
+- When target audience is likely to own hardware wallets
+- When most users are likely to implement good backup schemes for multiple keys
+
+**When not to use**
+- For small amounts
+- When users are likely to be new to bitcoin
+
+**Variations**
+- Number of total and co-signing keys
+- Key locations and distribution
+- Managed or completely sovereign
+
+**Do's**
+- Make sure the multi-key setup itself is backed up properly, including [extended public keys]({{ '/guide/glossary/#extended-public-key-xpub-ypub-zpub' | relative_url }}){:target="_blank"} for all the participating keys, fingerprint and derivation.
+
+**Products that use this scheme**
+- [Casa](https://keys.casa'){:target="_blank"} co-managed 2-of-3, or 3-of-5
+- [Electrum](https://electrum.org){:target="_blank"}
+- [Bluewallet](https://bluewallet.io){:target="_blank"}
+- [Unchained Capital/Caravan](https://unchained-capital.com){:target="_blank"} co-managed
+- [Specter](https://specter.solutions){:target="_blank"}
+- [Armory](https://btcarmory.com){:target="_blank"}
+- [Guarda](https://guarda.com){:target="_blank"}
+
+---
+
+Next, let's look at [shared schemes]({{ '/guide/private-key-management/multi-user-schemes/' | relative_url }}).
diff --git a/guide/private-key-management/wallet-recovery.md b/guide/private-key-management/wallet-recovery.md
new file mode 100644
index 000000000..97e583c71
--- /dev/null
+++ b/guide/private-key-management/wallet-recovery.md
@@ -0,0 +1,36 @@
+
+
+# Wallet recovery
+
+Stub for page about wallet recovery (for different schemes).
+
+## Single-key
+
+...
+
+## Multi-key
+
+bip174
+Value: The master key fingerprint as defined by BIP 32 concatenated with the derivation path of the public key. The derivation path is represented as 32-bit little endian unsigned integer indexes concatenated with each other. The number of 32 bit unsigned integer indexes must match the depth provided in the extended public key.
+https://btcguide.github.io/backup-wallet/public-keys-advanced#extended-public-key-info
+https://coldcardwallet.com/docs/multisig
\ No newline at end of file
diff --git a/guide/resources/content-guidelines.md b/guide/resources/content-guidelines.md
index 2b903becf..51d3b0bf1 100644
--- a/guide/resources/content-guidelines.md
+++ b/guide/resources/content-guidelines.md
@@ -3,7 +3,7 @@ layout: guide
title: Content guidelines
nav_order: 10
parent: Resources
-permalink: /guide/resources/content-guidelines
+permalink: /guide/resources/content-guidelines/
---
# Content guidelines
@@ -51,4 +51,3 @@ The guide is a work in progress and needs to evolve to stay relevant. What we wr
It's a good idea to ask for directions by seeking feedback early. This may stop you from wandering too far in the wrong direction. There is a whole community around you that's ready to jump in and help.
-
diff --git a/guide/resources/formatting.md b/guide/resources/formatting.md
index 3f8357f84..79e02c657 100644
--- a/guide/resources/formatting.md
+++ b/guide/resources/formatting.md
@@ -3,7 +3,7 @@ layout: guide
title: Formatting
nav_order: 11
parent: Resources
-permalink: /guide/resources/formatting
+permalink: /guide/resources/formatting/
---
# Formatting