mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-11-22 08:08:11 +00:00
Edited ch05_wallets.adoc with Atlas code editor
This commit is contained in:
parent
6d66497026
commit
d9bea0844e
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user