- | Authorization |
-Authentication |
-+ | Authorization |
+Authentication |
+
+
---|---|---|---|
Whitepaper |
+Whitepaper |
Public key |
Signature |
Field |
-Factor |
-Weight in Alice’s Tx |
-Field |
+Factor |
+Weight in Alice’s Tx |
+
+
---|---|---|
Version |
4 |
diff --git a/ch07_authorization-authentication.adoc b/ch07_authorization-authentication.adoc
index 074170ed..589b20d9 100644
--- a/ch07_authorization-authentication.adoc
+++ b/ch07_authorization-authentication.adoc
@@ -625,7 +625,7 @@ For example, Mohammed's complex script, hashed and base58check-encoded
as a P2SH address, becomes +39RF6JqABiHdYHkfChV6USGMe6Nsr66Gzw+.
Now, Mohammed can give this "address" to his customers, and they can use
-almost any Bitcoin wallet to make a simple payment like any other
+almost any Bitcoin wallet to make a simple payment, like any other
Bitcoin address. The 3 prefix gives them a hint that this is a special
type of address, one corresponding to a script instead of a public key,
but otherwise it works in exactly the same way as a payment to any other Bitcoin
@@ -910,7 +910,7 @@ the +OP_CHECKSEQUENCEVERIFY+ (+OP_CSV+) opcode.
Relative timelocks are
implemented according to the specifications in
https://oreil.ly/ZuANb[BIP68,
-relative lock-time using consensus-enforced sequence numbers] and
+relative Lock-Time Using Consensus-Enforced Sequence Numbers] and
https://oreil.ly/dLA2r[BIP112,
+OP_CHECKSEQUENCEVERIFY+].
@@ -1257,9 +1257,9 @@ Try running the script on paper to see how it behaves on the stack.
Let’s look at ((("scripts", "segregated witness", id="script-segwit")))((("segregated witness (segwit)", "scripts and", id="segwit-script")))some of our example transactions and see how they would
change with segregated witness. We’ll first look at how a
-pay to public key hash (P2PKH) payment can be accomplished as the
+pay to public key hash P2PKH payment can be accomplished as the
segregated witness program. Then, we’ll look at the segregated witness
-equivalent for pay to script hash (P2SH) scripts. Finally, we’ll look at
+equivalent for P2SH scripts. Finally, we’ll look at
how both of the preceding segregated witness programs can be embedded
inside a P2SH script.
@@ -1352,10 +1352,10 @@ to the receiver in the manner that the receiver indicated.
====
[[p2wsh]]
-===== Pay to witness script hash
+===== Pay to witness script hash (P2WSH)
The ((("scripts", "segregated witness", "P2WSH", id="script-segwit-p2wsh")))((("segregated witness (segwit)", "scripts and", "P2WSH", id="segwit-script-p2wsh")))((("P2WSH (pay to witness script hash)", id="p2wsh-ch7")))((("output scripts", "P2WSH (pay to witness script hash)", id="output-script-p2wsh")))second type of
-segwit v0 witness program corresponds to a pay to script hash (P2SH) script. We
+segwit v0 witness program corresponds to a P2SH script. We
saw this type of script in <