1
0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-12-04 22:08:23 +00:00
Commit Graph

5022 Commits

Author SHA1 Message Date
David A. Harding
58643749fb CH02::getting inputs: warn about privacy for address lookup calls 2023-02-05 13:33:02 -10:00
David A. Harding
fbdb840923 CH02::getting inputs: introduce UTXO term
Introduce the UTXO term as it is one of the most essential concepts to
understanding how Bitcoin works and is widely used in other Bitcoin
technical documentation.
2023-02-05 13:33:02 -10:00
David A. Harding
2753d8cd8d CH02::constructing: clarify offline requirements
Previous text said that wallets can construct tranactions offline.  Add
clarification that this requires the wallet to already know what inputs
it controls.
2023-02-05 13:33:02 -10:00
David A. Harding
fa7a385c83 CH02::common tx forms: introduce technical terms
- *consolidation transaction_ for what was previously called an
  aggregating transaction

- *payment batching* for paying multiple outputs
2023-02-05 13:33:02 -10:00
David A. Harding
e458e803cd CH02::tx chain: remove repetitive summary paragraph 2023-02-04 21:17:35 -10:00
David A. Harding
a20a159cb5 CH02::coin selection: make its own subsection 2023-02-04 21:17:35 -10:00
David A. Harding
a4327fa4fe CH02::Change update for illustration, add detail
- Update text to refer to new illustration

- Introduce the term "change output" in addition to existing term
  "change address"

- Add information about the privacy advantages of unique change
  addresses
2023-02-04 21:17:35 -10:00
David A. Harding
b05a5ee6f8 CH02::chain of txes: update illustration, add detail
- Previous illustration was cut-off, both in the source and the print
  edition.  We update the illustration to not only correct that but also
  provide more accuracy:

    - Instead of showing input values, the illustration now shows input
      references to prevouts.

    - Instead of using BTC denomination, it use satoshis

    - Instead of putting tx fees in the output category, it shows them
      outside the transaction since they're an implicit value

    - The source for the new illustration is provided as a comment to
      make future editing easier

- The text is updated to refer to the new illustration appropriately.

- Text now mentions the implicit input value

- We describe that we use satoshi values because that's what's in the
  protocol
2023-02-04 21:17:35 -10:00
David A. Harding
4725f0f51d CH02::Alice pays Bob: change example from laptop to podcast episode
Before earlier edits, the second edition text for this chapter was about
buying a cup of coffee.  The edits changed it to a laptop.  The risk
profile of a cup of coffee and a laptop are different, making some parts
of the text problematic, e.g. Bob accepting payment without waiting for
confirmation.

This update replaces the example with Alice buying a premium podcast
episode, which has a very low risk profile.
2023-02-04 21:17:35 -10:00
David A. Harding
3d9794f65a CH02::Alice pays Bob: remove text about payment completion
Existing text claimed that Alice's unconfirmed transaction completed the
payment to Bob, but Bob would be wise to wait for a $750 transaction to
confirm.

I think this is a problem resulting from a previous edit to the
second-edition text where the example was changed from a cup of coffee
at a cafe to a laptop.  A cup of coffee is cheap and has no resale
value, so the chance of fraud is small; a laptop is expensive and has
significant resale value, making fraud a greater risk.
2023-02-04 21:17:35 -10:00
David A. Harding
fef1182828 CH02: remove some specific amounts
Remove some specific amounts and numbers to make updating the text in
the future easier.  The removed values don't add anything to the text.
2023-02-04 21:17:33 -10:00
David A. Harding
7a5351efa8 CH02::invoice: replace "payment request" with "invoice"
The payment request language is confusing because BIP70 payment requests
look a lot like the URI used here but this is not a BIP70 payment
request (and BIP70 is dead, so we need not describe it).

Instead, update the text to use the more generic word "invoice", which
has the advantage of also being simpler English.
2023-02-04 21:15:32 -10:00
David A. Harding
562304b4cf CH02::pluralization: update to follow standard conventions
Existing text used "bitcoin" as both the singular and plural unit, which
was not an uncommon practice when the first edition was written.
However, my edits to the first chapter and this update adopt the
practice of using the same pluralization rules used for other
currencies, like the dollar, plus most numbered things in general.
This produces more natural text.

Reference: https://www.chicagomanualofstyle.org/qanda/data/faq/topics/Numbers/faq0058.html
2023-02-04 21:15:32 -10:00
David A. Harding
9435ad7d66 CH02::block explorers: modernize list and add warning
Replace older block explorers with modern alternatives and warn readers
that looking up info on explorers may disclose their interest to third
parties.
2023-02-04 06:11:19 -10:00
David A. Harding
be0ab0c6c5 CH02::intro: remove statements that Bitcoin requires trust
Users operating a full node don't need to trust anyone else for certain
guarantees about the system, although they do need at least one honest
peer to obtain some other guarantees.  Clarify this in the text by
revising text about text and emergent properties.
2023-02-03 20:58:39 -10:00
David A. Harding
ef06e4294b CH02: reflow text so that future diffs will be more readable 2023-02-03 20:49:51 -10:00
David A. Harding
bada9cbe41 CH01: minor edits for consistency, voice, and correctness 2023-02-03 20:26:17 -10:00
David A. Harding
7a0f5f49e4 CH01::Receving: remove misleading claim about address identity association
Original text claimed that there is no association between a user's
identity and their addresses prior to using that address in most
wallets, but many lightweight wallets send even their not-yet-used
addresses to remote servers to scan for incoming payments.  This is
often done over IPv4 or IPv6, which creates a link between the user's
connection and their addresses.  Update text by simply dropping this
claim.
2023-02-03 20:26:17 -10:00
David A. Harding
e9392b7ac4 CH01::Lightweight clients: direct connection to P2P network not required
SPV verification doesn't require connecting to a full node over the P2P
network.  Many clients connect to specially designed tranasctions
servers (e.g. an Electrum server) which provides them with transactions,
SPV proofs, and headers--and provide relay for outgoing transactions.
Update text to remove claims about direct P2P connection.
2023-02-03 20:26:17 -10:00
David A. Harding
b839919066 CH01::First Time: make more futureproof by removing specific prices
Also other changes to more generically describe wallet interfaces so
that screenshots can be updated in the future without changing text.
2023-02-03 20:26:16 -10:00
David A. Harding
849d49035f CH01::Addresses: mention invoices also; mention privacy concerns about address sharing
- The previous text only refers to onchain addresses, but BIP22 URIs,
  QR-encoded BIP22 URIs, and offchain invoices (like BOLT11) are the way
  many users will now exchange payment information, so the tipbox is
  generalized to refer to both addresses and invoices.

- A few words are added to clarify why sharing an address or invoice
  doesn't create security risks: Bitcoin is push-only.

- We mention the privacy downsides of sharing addresses or invoices and
  encourage generating new addresses for each payment.
2023-02-03 20:26:16 -10:00
David A. Harding
84fd8b5953 CH01::Backups: s/mnemonic/recovery code/, add detail and warnings
- Use "recovery code" instead of "mnemonic phrase" or "seed phrase".  A
  new tipbox describes that mnemonic implies memorization but that's bad
  practice.  The phrase recovery code is generic enough to apply to a
  variety of schemes, including Electrum seed words, BIP38 seed words,
  aezeed, and non-phrase schemes like that used in Muun.

- Be clearer about the difference between "wallet" and "wallet
  software".

- Mention that restoring from a code doesn't restore labels or
  offchain transaction info.

- Warn about re-entering your code into malware / phishing attacks.
2023-02-03 20:26:16 -10:00
David A. Harding
89c40241e2 CH01::Full node: clarify requirements; update "client" language to include "peer"
- Full nodes don't need to store transactions long-term or serve data to
  other software, so mention those as option

- Stop calling full nodes "clients".  Add a tipbox describing that full
  nodes are the peers on Bitcoin's P2P network.
2023-02-03 20:26:16 -10:00
David A. Harding
1db8772e86 CH01::Wallet Types: mention privacy; s/HWW/hardware signing device/
- Mention that mobile wallets and web wallets almost universally use
  remote servers for scanning, reducing privacy.

- Rename "hardware wallets" to "hardware signing devices".  In general,
  all these devices do is display info about an unsigned transaction to
  a user and then sign it if the user approves.  They need to be paired
  with other software that implements all of the other wallet behavior.
  We rename them accordingly and mention that the security and privacy
  of the wallet they pair with plays a role in the user's security and
  privacy.
2023-02-03 20:26:16 -10:00
David A. Harding
9ea0eee92a CH01::BGP: clarify problem; drop "widde applicability"
- A key element of the problem is *leaderless* selection; mention this.

- Drop the list of other things PoW helps with.  Some of them are very
  wrong, e.g. "proving the fairness of elections".
2023-02-03 20:26:16 -10:00
David A. Harding
934f08678e CH01::History: clarify Nakamoto & PoW facts
- Bitcoin was invented in 2007 (not 2008) per Nakamoto saying he'd
  worked on it for about a year and a half prior to publication.  Update
  text to just say "first described in 2008"

- Of the inventions Bitcoin combined, b-money wasn't one of them.  We
  know that Nakamoto sent his original paper to Adam Back, Back told
  Nakamoto about Wei Dai's b-mony, and Nakamoto contacted Dai in order
  to add the b-money reference to his paper as an example of a previous
  related idea.  Nakamoto was aparently unaware of b-money before then
  and so couldn't have combined it with other ideas in the creation of
  bitcoin.  Updated text from "b-money" to say "digital signatures",
  which is a critical technology that was obviously part of Bitcoin's
  original combination.

- The text describes "the" critical invention of Bitcoin as using PoW to
  conduct an global election.  Although that was critical, other factors
  may also have been critical (e.g. difficulty adjustments to keep the
  rate of issuance relatively constant).  Updated text to say "a"
  critical invention.

- Changed Bitcoin from exceeding the combined processing power of top
  super computers to exceeding the number of computing operations.
  It's not really fair to compare ASICs to general purpose CPU chips;
  it's like comparing a wrench to your hand.

- Updated the dollar value of the largest transaction to "over a billion
  dollars"; dropped the amount of the transaction fee.  I think this
  will better future-proof the text.
2023-02-03 20:26:16 -10:00
David A. Harding
f8a2340cb2 CH01::Mining: clarify that 99% of all bitcoins will be mined within a decade
Previous text mentioned all bitcoins would be mined by 2140, which is
correct but easily confuses people who don't understand exponential
decay into thinking a substantial number of bitcoins will continue to be
mined for a century.
2023-02-03 20:26:16 -10:00
David A. Harding
b2626aeb39 CH01::Mining: Clarify that miners add security to transactions
Previous text said they "verify" transactions, but that's not always the
case (e.g. validationless mining) and it may give readers the impression
that the entities primarily responsible for verifying transactions are
miners---when it's actually users who are ultimately responsible for
verifying the transactions they care about.
2023-02-03 20:26:16 -10:00
David A. Harding
bc703ce9ce CH01: minor edits 2023-02-03 20:26:16 -10:00
David A. Harding
4b08bdf3d6 CH01::Bitcoin vs Bitcoin: be less prescriptive 2023-02-03 20:25:12 -10:00
David A. Harding
21550eecd4 CH01: Reflow text to make later diffs more readable 2023-02-03 20:24:50 -10:00
David A. Harding
2f0d7d8c3a Revert CC-BY-SA material added since the second edition
The commit ab5ae32bae is the last commit
for the second edition, so all changes since then are dropped except for
several commits for the third edition authored by Andreas Antonopoulos.

No attempt is made to remove CC-BY-SA or other licensed content present
in the already-published first or second editions.

This revert may itself be reverted for versions of the book published
under CC-BY-SA.
2023-02-01 06:31:10 -10:00
Andreas M. Antonopoulos
eeca5dee4a Merge branch 'mb3dev' into main 2022-06-26 15:33:05 +02:00
Andreas M. Antonopoulos
79e870d372 New illustrations for ECDSA and Schnorr signatures 2022-06-26 15:22:09 +02:00
Andreas M. Antonopoulos
7820286ca3 schnorr signature equation explained 2022-06-26 15:22:09 +02:00
Andreas M. Antonopoulos
2791c5a700 schnorr intro 2022-06-26 15:22:09 +02:00
Pamela Morgan
bdc40d6d6b initial changes on copyright page
needs more updates later
2022-06-26 15:22:09 +02:00
Pamela Morgan
7a7365fe6f changed Second to Third Edition 2022-06-26 15:22:09 +02:00
Andreas M. Antonopoulos
b99c906fb8 bips links 2022-06-26 15:22:09 +02:00
Pamela Morgan
bec8eec981 added links to bips 2022-06-26 15:22:09 +02:00
Andreas M. Antonopoulos
37f7452a79 bech32m skeleton 2022-06-26 15:22:09 +02:00
Andreas M. Antonopoulos
195d42f548 MAST Merkle Branches skeleton 2022-06-26 15:22:09 +02:00
Andreas M. Antonopoulos
25c06254c3 Tapscript skeleton 2022-06-26 15:22:09 +02:00
Andreas M. Antonopoulos
1ccdc396c3 SegWit v1 skeleton 2022-06-26 15:22:09 +02:00
Andreas M. Antonopoulos
6d473c715a Schnorr Signatures skeleton 2022-06-26 15:22:09 +02:00
Andreas M. Antonopoulos
c0177295e7 Third edition changelog 2022-06-26 15:22:09 +02:00
aantonop
c4640b6775 Updated atlas.json 2022-06-26 15:22:09 +02:00
aantonop
ce2d6580df Updated atlas.json 2022-06-26 15:22:09 +02:00
aantonop
8db329c1e8 Updated atlas.json 2022-06-26 15:22:09 +02:00
Andreas M. Antonopoulos
827d188829 ch2 edits part 1 2022-06-26 15:22:09 +02:00