From d9bea0844e032908d81b6e8e8cde67dad677e021 Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 19:37:54 +0000 Subject: [PATCH] Edited ch05_wallets.adoc with Atlas code editor --- ch05_wallets.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch05_wallets.adoc b/ch05_wallets.adoc index 842f7753..87952d5c 100644 --- a/ch05_wallets.adoc +++ b/ch05_wallets.adoc @@ -418,7 +418,7 @@ just keys--they also also store user-provided information about every transaction they sent or received. For example, when Bob creates a new address as part of sending an -invoice to Alice, he ((("labels", "backing up", id="label-backup")))adds a _label_ to the address he generates +invoice to Alice, he ((("labels, backing up", id="label-backup")))adds a _label_ to the address he generates so that he can distinguish her payment from other payments he receives. When Alice pays Bob's address, she labels the transaction as paying Bob for the same reason. Some wallets @@ -472,7 +472,7 @@ data. Additionally, it may be useful for wallet applications to provide a standardized format to export labels so that they can be used in other -applications, e.g., accounting software. A standard for that ((("labels", "backing up", startref="label-backup")))format is +applications, e.g., accounting software. A standard for that ((("labels, backing up", startref="label-backup")))format is proposed in BIP329. Wallet applications implementing additional protocols beyond basic