From 09b6d6a3b2e4274ce677aab268a93ec7e0f06e9a Mon Sep 17 00:00:00 2001 From: nadams Date: Tue, 30 May 2017 12:15:35 -0700 Subject: [PATCH] Edited ch06.asciidoc with Atlas code editor --- ch06.asciidoc | 1 + 1 file changed, 1 insertion(+) diff --git a/ch06.asciidoc b/ch06.asciidoc index bd37f9e1..e75f00da 100644 --- a/ch06.asciidoc +++ b/ch06.asciidoc @@ -356,6 +356,7 @@ As Eugenia's wallet application tries to construct a single larger payment trans Eugenia's wallet application will calculate the appropriate fee by measuring the size of the transaction and multiplying that by the per-kilobyte fee. Many wallets will overpay fees for larger transactions to ensure the transaction is processed promptly. The higher fee is not because Eugenia is spending more money, but because her transaction is more complex and larger in size--the fee is independent of the transaction's bitcoin value.((("", startref="Tout06"))) [[tx_script]] +[role="pagebreak-before"] === Transaction Scripts and Script Language ((("transactions", "scripts and Script language", id="Tsript06")))((("scripting", "transactions and", id="Stransact06")))The bitcoin transaction script language, called _Script_, is a Forth-like reverse-polish notation stack-based execution language. If that sounds like gibberish, you probably haven't studied 1960s programming languages, but that's ok—we will explain it all in this chapter. Both the locking script placed on a UTXO and the unlocking script are written in this scripting language. When a transaction is validated, the unlocking script in each input is executed alongside the corresponding locking script to see if it satisfies the spending condition.