paper wallet post more fixes

diff --git a/content/blog/2021/descriptor_based_paper_wallet.md b/content/blog/2021/descriptor_based_paper_wallet.md
index 54f77e4de9c8973610c14d5d22da974b20e72af9..bf93b790a55fa27f7f0c17bbdb0badeacf50f342 100644 (file)
--- a/content/blog/2021/descriptor_based_paper_wallet.md
+++ b/content/blog/2021/descriptor_based_paper_wallet.md
@@ -17,13 +17,13 @@ only be using testnet coins.
 
 ## Descriptors
 
-[Previous version](https://github.com/RCasatta/rusty-paper-wallet/tree/339fa4418d94f6fdd96f3d0301cab8a0bc09e8bd) of the [Rusty Paper Wallet] was following the original paper wallet design: WIF[^WIF] as secret part with the option to generate a different kind of addresses (legacy, nested segwit, and segwit).
+The [previous version] of the [Rusty Paper Wallet] followed the original paper wallet design: WIF[^WIF] as secret part with the option to generate a different kind of addresses (legacy, nested segwit, and segwit).
 
-There were intentions to [support mnemonic](https://github.com/RCasatta/rusty-paper-wallet/issues/5) instead of WIF because it may[^WIF core] save the sweep transaction[^sweep] and there are more wallets capable of importing a mnemonic instead of a WIF.
+There were plans to [support mnemonic](https://github.com/RCasatta/rusty-paper-wallet/issues/5) instead of WIF keys because it may[^WIF core] save the sweep transaction[^sweep] and there are more wallets capable of importing a mnemonic instead of a WIF.
 
-However, choosing a single address type or having wallet support for a specific format is the kind of problem descriptors solve perfectly, so the latest [Rusty Paper Wallet] version now accepts a descriptor and the network as parameters.
+However, choosing a single address type or having wallet support for a specific format is the kind of problem [descriptors] solve perfectly, so the latest [Rusty Paper Wallet] version now accepts a descriptor and the network as parameters.
 
-## Use case
+## Example use case
 
 So let's say your grandma wants to buy bitcoin and asked for your help.
 
@@ -33,11 +33,11 @@ Even though we trust everyone in the family it is better to play it safe and div
 
 This is a perfect case for a 2 of 3 multi-signature paper wallet. This way also protects the participants from having their copy of the wallet stolen. To compromise Grandma's wallet a thief would need to find and steal at least two of them.
 
-Note you as the wallet creator are still the single point of trust because you are going to generate the keys for everyone. Setups combining keys from the participants are possible future work.
+Note that you as the wallet creator are still the single point of trust because you are going to generate the keys for everyone. Setups combining self generated keys from the participants is possible future work.
 
 ## Creating the paper wallet
 
-The spending descriptor would be:
+For this example the spending descriptor would be:
 
 `wsh(multi(2,Grandma,Alice,Barbara))`
 
@@ -45,7 +45,7 @@ You need [rust] installed to use [Rusty Paper Wallet]. The -n option below expli
 generating `testnet` keys. Use `rusty-paper-wallet --help` to see usage instructions and other
 options.
 
-```
+```shell
 $ cargo install rusty-paper-wallet
 $ rusty-paper-wallet "wsh(multi(2,Grandma,Alice,Barbara))" -n testnet
 data:text/html;base64,PCFET0N...
@@ -58,115 +58,120 @@ The following is the result:
 
 <iframe src="/images/descriptor-based-paper-wallets/Bitcoin_Paper_Wallet.html" height="800" width="800" ></iframe>
 
-Under the hood, the command created a key pair randomly for every alias present in the descriptor, then replaced the aliases with the created keys and generated the relative address. This address is the same for every paper wallet and it is shown in the upper part of the paper wallet (the public part) along with the alias, linking the paper wallet to the owner.
+Under the hood, the command created a key pair randomly for every alias present in the descriptor, then replaced the aliases with the created keys and generated the corresponding address. This address is the same for every paper wallet and it is shown in the upper part of the paper wallet (the public part) along with the alias, linking the paper wallet to the owner.
 
 The lower part is the secret part, the written part is the descriptor with the aliases, followed by a legend linking the aliases with the keys. In the legend, all the keys are public but the one of the owner which is a private WIF. The secret QR code instead contains the descriptor already with the keys.
 
-The paper wallet must then be printed, better to use a printer without wifi and also be aware that some sensitive data may remain in the printer cache.
+The paper wallet must then be printed, and it is better to use a printer without wifi and also to be aware that some sensitive data may remain in the printer's cache.
 
-Then the paper wallet must be cut along the dotted lines, the secret part should be folded twice over the black zone[^black zone]. The black zone helps to avoid showing the secret parts in presence of back-light. Once the folding is done the paper wallet should be plasticized to prevent being damaged by water.
+Then the paper wallet must be cut along the dotted lines, the secret part should be folded twice over the black zone[^black zone]. The black zone helps to avoid showing the secret parts in the presence of back-light. Once the folding is done the paper wallet should be plasticized to prevent being damaged by water.
 
 ## BDK
 
-Any descriptor based wallet could be used to check the balance of and sweep the funds from
-Grandma's paper wallet. For this post we'll demonstrate use the [bdk-cli] tool to do these steps.
-Another area where [bdk-cli] could be used with [Rusty Paper Wallet] is to compile a more
-complicated miniscript spending policy into a descriptor, like we have done in the [spending policy demo post].
+Any descriptor based wallet can be used to check the balance of and sweep the funds from
+Grandma's paper wallet. For this post we'll demonstrate using the [bdk-cli] tool to do these steps.
+Another area where [bdk] could be used with [Rusty Paper Wallet] is to compile a more
+complicated miniscript spending policy into a descriptor, as we have done in the [spending policy demo] post.
 
 ## Funding tx
 
 Since Grandma's wallet was created as a `wsh` descriptor, bitcoin can be sent to it from any
 segwit capable wallet, we'll use a public [bitcoin testnet faucet]. Once the funds are sent the
-deposit address `tb1qu6lcua9w2zkarjj5xwxh3l3qtcxh84hsra3jrvpszh69j2e54x7q3thycw` can also use this
+deposit address `tb1qu6lcua9w2zkarjj5xwxh3l3qtcxh84hsra3jrvpszh69j2e54x7q3thycw` we can also use this
 address and a testnet explorer to [confirm the funds were received].
 
 ## Sweep tx
 
-Now that Grandma's paper wallet is funded we can demonstrate how to use [bdk-cli] to sweep these
+Now that Grandma's paper wallet is funded it's time to demonstrate how to use [bdk-cli] to sweep these
 funds to a new address. Let's assume Grandma lost her original paper wallet and has asked
-her daughters to sweep them a new single signature wallet so she can spend them.
+her daughters to sweep them to a new single signature wallet so she can spend them.
 
 ### Step 1: Alice creates and signs a PSBT  
 
-Alice uses the private text or QR code from her paper wallet Alice to find her private key and the
-public keys for Grandma and Barbara. With this info she can create a PSBT to sweep Grandma's funds
-to a new address (in this case we'll send them back to our testnet bitcoin faucet). Notice how she
-includes her wallet checksum '#em3q73l5', this guarantees she has entered her descriptor correctly.
+Alice uses the private text or QR code from her paper wallet to find her private key and the
+public keys for Grandma and Barbara. With this info she creates a PSBT to sweep Grandma's funds
+to a new address (in this example we'll send them back to our [bitcoin testnet faucet]). Notice how Alice
+includes her wallet's descriptor checksum '#em3q73l5', this guarantees she has entered her descriptor correctly.
 
-```  
-export SWEEP_TO_ADDR=tb1qm5tfegjevj27yvvna9elym9lnzcf0zraxgl8z2
+```shell  
+$ export SWEEP_TO_ADDR=tb1qm5tfegjevj27yvvna9elym9lnzcf0zraxgl8z2
 
-export ALICE_WIF=cSSKRHDmQEEutp5LD14tAcixu2ehSNPDTqNek1zMa9Pet98qxHq3
-export BARBARA_PUBKEY=02a3f3f2658b9812ddeabfbde2fde03f8a65369e4ed621f29fa8ba0cc519b789fb
-export GRANDMA_PUBKEY=03f1bd2bff8e9c61f58a8d46d18fd8f3149b1f2d76b3c423a7874a5d5811d67cee
-export ALICE_DESCRIPTOR="wsh(multi(2,$GRANDMA_PUBKEY,$ALICE_WIF,$BARBARA_PUBKEY))#em3q73l5"
+$ export ALICE_WIF=cSSKRHDmQEEutp5LD14tAcixu2ehSNPDTqNek1zMa9Pet98qxHq3
+$ export BARBARA_PUBKEY=02a3f3f2658b9812ddeabfbde2fde03f8a65369e4ed621f29fa8ba0cc519b789fb
+$ export GRANDMA_PUBKEY=03f1bd2bff8e9c61f58a8d46d18fd8f3149b1f2d76b3c423a7874a5d5811d67cee
+$ export ALICE_DESCRIPTOR="wsh(multi(2,$GRANDMA_PUBKEY,$ALICE_WIF,$BARBARA_PUBKEY))#em3q73l5"
 
 # confirm descriptor creates the expected deposit address
-bdk-cli wallet -w alice -d $ALICE_DESCRIPTOR get_new_address
+$ bdk-cli wallet -w alice -d $ALICE_DESCRIPTOR get_new_address
 {
   "address": "tb1qu6lcua9w2zkarjj5xwxh3l3qtcxh84hsra3jrvpszh69j2e54x7q3thycw"
 }
 
 # sync the wallet and show the balance
-bdk-cli wallet -w alice -d $ALICE_DESCRIPTOR sync
+$ bdk-cli wallet -w alice -d $ALICE_DESCRIPTOR sync
 {}
 
-bdk-cli wallet -w alice -d $ALICE_DESCRIPTOR get_balance
+$ bdk-cli wallet -w alice -d $ALICE_DESCRIPTOR get_balance
 {
   "satoshi": 10000
 }
 
 # create and sign PSBT
-export UNSIGNED_PSBT=$(bdk-cli wallet -w alice -d $ALICE_DESCRIPTOR create_tx --send_all --to $SWEEP_TO_ADDR:0 | jq -r ".psbt")
+$ export UNSIGNED_PSBT=$(bdk-cli wallet -w alice -d $ALICE_DESCRIPTOR create_tx --send_all --to $SWEEP_TO_ADDR:0 | jq -r ".psbt")
 
-export ALICE_SIGNED_PSBT=$(bdk-cli wallet -w alice -d $ALICE_DESCRIPTOR sign --psbt $UNSIGNED_PSBT | jq -r ".psbt")
+$ export ALICE_SIGNED_PSBT=$(bdk-cli wallet -w alice -d $ALICE_DESCRIPTOR sign --psbt $UNSIGNED_PSBT | jq -r ".psbt")
 ```
 
 ### Step 2: Barbara signs Alice's signed PSBT and broadcasts the tx
 
 Now it's Barbara's turn to use the private text or QR code from her paper wallet to get her private
 key and the public keys for Grandma and Alice. With this info plus Alice's signed PSBT she can
-create a fully signed PSBT to broadcast and complete the sweep Grandma's funds.
+create a fully signed PSBT to broadcast and complete the sweep of Grandma's funds.
 
-```
-export ALICE_PUBKEY=02e486e32f0f87136fa042cb53219ace8537ea1d036deb2f4293570b94325d11cb
-export BARBARA_WIF=cSfMLzSZ9NjWUTqL3sFpgWJssnu2qgmE2cm5N1jPDRRJuDcrsPEB
-export GRANDMA_PUBKEY=03f1bd2bff8e9c61f58a8d46d18fd8f3149b1f2d76b3c423a7874a5d5811d67cee
-export BARBARA_DESCRIPTOR="wsh(multi(2,$GRANDMA_PUBKEY,$ALICE_PUBKEY,$BARBARA_WIF))#nxfa5n0z"
+```shell
+$ export ALICE_PUBKEY=02e486e32f0f87136fa042cb53219ace8537ea1d036deb2f4293570b94325d11cb
+$ export BARBARA_WIF=cSfMLzSZ9NjWUTqL3sFpgWJssnu2qgmE2cm5N1jPDRRJuDcrsPEB
+$ export GRANDMA_PUBKEY=03f1bd2bff8e9c61f58a8d46d18fd8f3149b1f2d76b3c423a7874a5d5811d67cee
+$ export BARBARA_DESCRIPTOR="wsh(multi(2,$GRANDMA_PUBKEY,$ALICE_PUBKEY,$BARBARA_WIF))#nxfa5n0z"
 
 # confirm descriptor creates the expected deposit address
-bdk-cli wallet -w barbara -d $BARBARA_DESCRIPTOR get_new_address
+$ bdk-cli wallet -w barbara -d $BARBARA_DESCRIPTOR get_new_address
 {
   "address": "tb1qu6lcua9w2zkarjj5xwxh3l3qtcxh84hsra3jrvpszh69j2e54x7q3thycw"
 }
 
 # sync the wallet and show the balance
-bdk-cli wallet -w barbara -d $BARBARA_DESCRIPTOR sync
+$ bdk-cli wallet -w barbara -d $BARBARA_DESCRIPTOR sync
 {}
 
-bdk-cli wallet -w barbara -d $BARBARA_DESCRIPTOR get_balance
+$ bdk-cli wallet -w barbara -d $BARBARA_DESCRIPTOR get_balance
 {
   "satoshi": 10000
 }
 
-export FINAL_PSBT=$(bdk-cli wallet -w barbara -d $BARBARA_DESCRIPTOR sign --psbt $ALICE_SIGNED_PSBT | jq -r ".psbt")
+$ export FINAL_PSBT=$(bdk-cli wallet -w barbara -d $BARBARA_DESCRIPTOR sign --psbt $ALICE_SIGNED_PSBT | jq -r ".psbt")
 
-bdk-cli wallet -w barbara -d $BARBARA_DESCRIPTOR broadcast --psbt $FINAL_PSBT
+$ bdk-cli wallet -w barbara -d $BARBARA_DESCRIPTOR broadcast --psbt $FINAL_PSBT
 {
   "txid": "9ecd8e6be92b7edd8bf1799f8f7090e58f813825f826bdb771b4cdb444cdeb59"
 }
 ```
 
-We can now confirm that Alice and Barbara successfully created a [tx to sweep] Grandma's funds.
+And finally we verify that Alice and Barbara successfully created and broadcast Grandma's [sweep tx].
 
 ## Conclusion
 
-In this post we showed how to create a multi-sig descriptor based paper wallet using [Rusty Paper Wallet], and then sweep funds from the paper wallet to a new address. If you found this interesting
-please comment below. Or if you give it a try yourself and run into any problems or would like
-to suggest improvements please comment on the [Rusty Paper Wallet] or [bdk-cli] github repos. Thanks!  
+In this post we showed how to create a multi-sig descriptor based paper wallet using 
+[Rusty Paper Wallet] and then sweep the funds from our example paper wallet to a new address. If you 
+found this post interesting please comment below. Or give it a try yourself and if you run into any 
+problems or would like to suggest improvements leave an issue in the [Rusty Paper Wallet] or 
+[bdk-cli] github repos. Thanks!  
 
 [paper wallet wikipedia article]: https://en.bitcoin.it/wiki/Paper_wallet
+[previous version]: https://github.com/RCasatta/rusty-paper-wallet/tree/339fa4418d94f6fdd96f3d0301cab8a0bc09e8bd
 [Rusty Paper Wallet]: https://github.com/RCasatta/rusty-paper-wallet
+[support mnemonic]: https://github.com/RCasatta/rusty-paper-wallet/issues/5
+[descriptors]: /descriptors
 [bdk]: https://github.com/bitcoindevkit/bdk
 [rust]: https://www.rust-lang.org/tools/install
 [output]: /images/descriptor-based-paper-wallets/data-url.txt
@@ -174,8 +179,8 @@ to suggest improvements please comment on the [Rusty Paper Wallet] or [bdk-cli]
 [bdk-cli]: https://github.com/bitcoindevkit/bdk-cli
 [bitcoin testnet faucet]: https://bitcoinfaucet.uo1.net/
 [confirm the funds were received]: https://mempool.space/testnet/address/tb1qu6lcua9w2zkarjj5xwxh3l3qtcxh84hsra3jrvpszh69j2e54x7q3thycw
-[tx to sweep]: https://mempool.space/testnet/tx/9ecd8e6be92b7edd8bf1799f8f7090e58f813825f826bdb771b4cdb444cdeb59
-[spending policy demo post]: /blog/2021/01/spending_policy_demo/
+[sweep tx]: https://mempool.space/testnet/tx/9ecd8e6be92b7edd8bf1799f8f7090e58f813825f826bdb771b4cdb444cdeb59
+[spending policy demo]: /blog/2021/02/spending-policy-demo/#step-4-create-wallet-descriptors-for-each-participant
 
 [^WIF]: Wallet Input Format, a string encoding a ECDSA private key  https://en.bitcoin.it/wiki/Wallet_import_format
 [^WIF core]: Unless the user import the WIF directly into bitcoin core