mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-12-23 07:08:13 +00:00
Edited ch07.asciidoc with Atlas code editor
This commit is contained in:
parent
d16a5c06db
commit
66b51689a4
@ -5,7 +5,7 @@
|
||||
[[ch07_intro]]
|
||||
=== Introduction
|
||||
|
||||
In the previous chapter, we introduced the basic elements of bitcoin transactions and looked at the most common type of transaction script, the Pay-to-Public-Key-Hash script. In this chapter we will look at more advanced scripting and how we can use it to build transactions with complex conditions.
|
||||
((("bitcoin", "scripting", id="Bscript07")))In the previous chapter, we introduced the basic elements of bitcoin transactions and looked at the most common type of transaction script, the Pay-to-Public-Key-Hash script. In this chapter we will look at more advanced scripting and how we can use it to build transactions with complex conditions.
|
||||
|
||||
First, we will look at _multisignature_ scripts. Next we will examine the second most common transaction script, _Pay-to-Script-Hash_, which opens up a whole world of complex scripts. Then, we will examine new script operators that add a time-dimension to bitcoin, through _timelocks_.
|
||||
|
||||
@ -597,4 +597,4 @@ A few more things to consider when reading this example. See if you can find the
|
||||
|
||||
* How do the partners "reset" the clock every 29 or 89 days to prevent the lawyer from accessing the funds?
|
||||
|
||||
* Why do some +CHECKSIG+ opcodes in this script have the +VERIFY+ suffix while others don't?
|
||||
* Why do some +CHECKSIG+ opcodes in this script have the +VERIFY+ suffix while others don't?((("", startref="Bscript07")))
|
||||
|
Loading…
Reference in New Issue
Block a user