---
# System prepended metadata

title: Untitled

---

You can think of an address just as you would an invoice. A new address should be generated for every payment, as they should only be used once. This prevents the sender from learning about previously received funds.
- can be linked to a page in the future. the privacy part.


like the names of the transacting parties or the purpose of the transaction
- not sure about the "names of the transacting parties"


As the blockchain only stores the amount and addresses involved in a transaction, any additional information has to be stored in your application, or encoded in payment links when they need to be shared.
- why do i want to save additional information
    - e.g. for book keeping purposes
    - instead of what this additional information could be, why?


Let’s look at our options when receivers want to share other details with the sender, or store them with the payment request for their own record keeping.

- make it more general

creating an invoice

While the application will generate a new address in the background, other information ~~like; how much is being requested, the name of the sender, and what is being paid for has to be manually entered by the receiver~~


The more time passes, the more difficult it will be to recall the details of transactions. When transacting in Bitcoin, there is no requirement for senders and receivers even to identify themselves, so both sides may end up having a transaction history with only amounts, random-looking text (addresses), and the date it was included in a block to reference when trying to understand where some funds came from.
- telling the reader why they should be doing the extra informaiton gathering. dos and don'ts?

title of the flow for the gallery
- ?

Requesting bitcoin
1. quickly generating a address
2. adding additional information
3. comparing the affects of not storing additional information


#### IDEA
transaction list with the additional information and without


##### moving address compatiblity to the bottom.


Whether it’s just an address or a payment link, the two methods of sharing the payment details are text or scannable QR Codes.

- is not consistent with first paragrpah


Here are some constraints to consider when displaying QR Codes:
- simplify the sentences into one line

Waiting and ~~transaction processing~~ #


Awaiting payment – the sender has not broadcast~~ed~~ a transaction with the payment, or one has not been detected as yet by the receiver’s application.

