From 66b51689a4446b68ba2ad4fe33553c5d4f6eea76 Mon Sep 17 00:00:00 2001 From: "judymcconville@roadrunner.com" Date: Mon, 1 May 2017 10:14:21 -0700 Subject: [PATCH] Edited ch07.asciidoc with Atlas code editor --- ch07.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch07.asciidoc b/ch07.asciidoc index 354d0b0e..e85aff79 100644 --- a/ch07.asciidoc +++ b/ch07.asciidoc @@ -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")))