1
0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2025-02-04 11:53:09 +00:00

Edited ch06_transactions.adoc with Atlas code editor

This commit is contained in:
clenser 2023-10-19 01:20:31 +00:00
parent d13ba4bfcb
commit 4527d730eb

View File

@ -599,7 +599,7 @@ The example transaction has two outputs.
==== Amount ==== Amount
The first field of a specific output is its _amount_, also called The first((("transactions", "outputs", "amount field", id="transaction-output-amount")))((("outputs", "amount field", id="output-transaction-amount")))((("amount field (transaction outputs)", id="amount-field"))) field of a specific output is its _amount_, also called
"value" in Bitcoin Core. This is an 8-byte signed integer indicating "value" in Bitcoin Core. This is an 8-byte signed integer indicating
the number of _satoshis_ to transfer. A satoshi is the smallest unit of the number of _satoshis_ to transfer. A satoshi is the smallest unit of
bitcoin that can be represented in an onchain Bitcoin transaction. bitcoin that can be represented in an onchain Bitcoin transaction.
@ -679,7 +679,7 @@ amounts of arbitrary data in the blockchain without increasing the size
of its UTXO database. Since the outputs are unspendable, they aren't of its UTXO database. Since the outputs are unspendable, they aren't
uneconomical--any satoshis assigned to them become uneconomical--any satoshis assigned to them become
permanently unspendable--so allowing the amount to be zero ensures permanently unspendable--so allowing the amount to be zero ensures
satoshis aren't being destroyed. satoshis aren't being ((("transactions", "outputs", "amount field", startref="transaction-output-amount")))((("outputs", "amount field", startref="output-transaction-amount")))((("amount field (transaction outputs)", startref="amount-field")))destroyed.
==== Output Scripts ==== Output Scripts