Skip to content

Commit ca406ce

Browse files
authored
Fix summary title
1 parent 58a40b8 commit ca406ce

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

10_6_Spending_a_P2SH_Transaction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ $ bitcoin-cli -named signrawtransactionwithkey hexstring=$rawtxhex prevtxs='''[
3333
```
3434
With any other sort of P2SH you're going to be including a different `redeemscript`, but otherwise the practice is exactly the same. The only difference is that after two chapters of work on Scripts you now understand what the `scriptPubKey` is and what the `redeemScript` is, so hopefully what were mysterious elements four chapters ago are now old hat.
3535

36-
## Summary: Spending a Transaction with a Bitcoin Script
36+
## Summary: Spending a P2SH Transaction
3737

3838
You already spent a P2SH back in Chapter 6, when you resent a multsig transaction the hard way, which required lining up the `scriptPubKey` and `redeemScript` information. Now you know that the `scriptPubKey` is a standardized P2SH locking script, while the `redeemScript` matches a hash in that locking script and that you need to be able to run it with the proper variables to receive a `True` result. But other than knowing more, there's nothing new in spending a P2SH transaction, because you already did it!
3939

0 commit comments

Comments
 (0)