|
|
|
@ -872,7 +872,7 @@ for which she needs to pay transaction fees every time she wants to spend money
|
|
|
|
|
small commitments to large amounts of data also applies here.
|
|
|
|
|
|
|
|
|
|
The BIP16 upgrade to the Bitcoin protocol in 2012 allows an
|
|
|
|
|
output script to commit to a _redemption script_ (_redeem script_). When
|
|
|
|
|
output script to ((("redemption scripts", id="redeem-script")))commit to a _redemption script_ (_redeem script_). When
|
|
|
|
|
Bob spends his bitcoins, his input script needs to provide a redeem script
|
|
|
|
|
that matches the commitment and also any data necessary to satisfy the
|
|
|
|
|
redeem script (such as signatures). Let's start by imagining Bob wants
|
|
|
|
@ -939,7 +939,7 @@ transactions.
|
|
|
|
|
P2PKH and P2SH are the only two script templates used with base58check
|
|
|
|
|
encoding. They are now known as legacy addresses and have become less
|
|
|
|
|
common over time.
|
|
|
|
|
Legacy addresses were supplanted by the bech32 family of addresses.
|
|
|
|
|
Legacy addresses were supplanted by the bech32 family of ((("redemption scripts", startref="redeem-script")))addresses.
|
|
|
|
|
|
|
|
|
|
[[p2sh_collision_attacks]]
|
|
|
|
|
.P2SH Collision Attacks
|
|
|
|
|