arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-11-22 08:08:11 +00:00
Code Issues Releases Wiki Activity

Edited ch06_transactions.adoc with Atlas code editor

Browse Source
This commit is contained in:
clenser 2023-10-19 01:01:59 +00:00
parent 138d1e8457
commit 9d7f230bc2
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ch06_transactions.adoc
View File

@ -419,7 +419,7 @@ tracked the version of the transaction.
For example, imagine Alice and Bob want to bet on a game of cards. They
start by each signing a transaction that deposits some money into an
output with a script that requires signatures from both of them to spend, a
output with a script that requires signatures from both of them to ((("multisignature scripts")))((("setup transactions")))spend, a
_multisignature_ script (_multisig_ for short). This is called the
_setup transaction_. They then create a transaction that spends that
output:
@ -466,8 +466,8 @@ alternative scenarios:
got lucky and a block was discovered before Alice's version arrived,
it's Alice's version of the transaction that will get confirmed.
This type of protocol is what we now call a _payment channel_.
Bitcoin's creator, in an email attributed to him, called these
This type of protocol is what we now ((("payment channels")))call a _payment channel_.
Bitcoin's creator, in an email attributed to him, called((("high-frequency transactions"))) these
_high-frequency transactions_ and described a number of features added to
the protocol to support them. We'll learn about several of those other
features later and also discover how modern versions of payment channels