arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2025-02-17 01:52:09 +00:00
Code Issues Releases Wiki Activity

CH07: drop confusing claims about segwit wallet requirements

Browse Source
This commit is contained in:
David A. Harding 2023-03-16 09:32:53 -10:00
parent 90eafb5df8
commit 7b6bc29171
1 changed files with 8 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
chapters/authorization-authentication.adoc
View File

@ -1511,29 +1511,16 @@ As we can see from the previous examples, upgrading to Segregated
Witness is a two-step process. First, wallets must create special segwit Witness is a two-step process. First, wallets must create special segwit
type outputs. Then, these outputs can be spent by wallets that know how type outputs. Then, these outputs can be spent by wallets that know how
to construct Segregated Witness transactions. In the examples, Alice's to construct Segregated Witness transactions. In the examples, Alice's
wallet was segwit-aware and able to create special outputs with wallet is able to create outputs paying
Segregated Witness scripts. Bob's wallet is also segwit-aware and able Segregated Witness scriptPubKeys. Bob's wallet is also segwit-aware and able
to spend those outputs. What may not be obvious from the example is that to spend those outputs.
in practice, Alice's wallet needs to _know_ that Bob uses a segwit-aware
wallet and can spend these outputs. Otherwise, if Bob's wallet is not
upgraded and Alice tries to make segwit payments to Bob, Bob's wallet
will not be able to detect these payments.
[TIP] Segregated Witness was implemented as a
====
For P2WPKH and P2WSH payment types, both the sender and the recipient
wallets need to be upgraded to be able to use segwit. Furthermore, the
sender's wallet needs to know that the recipient's wallet is
segwit-aware.
====
Segregated Witness will not be implemented simultaneously across the
entire network. Rather, Segregated Witness is implemented as a
backward-compatible upgrade, where _old and new clients can coexist_. backward-compatible upgrade, where _old and new clients can coexist_.
Wallet developers will independently upgrade wallet software to add Wallet developers independently upgraded wallet software to add
segwit capabilities. The P2WPKH and P2WSH payment types are used when segwit capabilities.
both sender and recipient are segwit-aware. The traditional P2PKH and Legacy P2PKH and
P2SH will continue to work for nonupgraded wallets. That leaves two P2SH continue to work for nonupgraded wallets. That leaves two
important scenarios, which are addressed in the next section: important scenarios, which are addressed in the next section:
- Ability of a sender's wallet that is not segwit-aware to make a - Ability of a sender's wallet that is not segwit-aware to make a