From 4115bd0fc64d9129799f17a8b2a47c39f6a7bb5c Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 01:22:27 +0000 Subject: [PATCH] Edited ch06_transactions.adoc with Atlas code editor --- ch06_transactions.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch06_transactions.adoc b/ch06_transactions.adoc index daaaa071..20702027 100644 --- a/ch06_transactions.adoc +++ b/ch06_transactions.adoc @@ -613,7 +613,7 @@ zero and as large as 21 million bitcoins (2.1 quadrillion satoshis). [[uneconomical_outputs]] ===== Uneconomical outputs and disallowed dust -Despite not having any value, a zero-value output can be spent under +Despite not ((("uneconomical outputs", id="uneconomical")))((("dust policies", id="dust")))having any value, a zero-value output can be spent under the same rules as any other output. However, spending an output (using it as the input in a transaction) increases the size of a transaction, which increases the amount of fee that needs to be paid. If the value @@ -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 uneconomical--any satoshis assigned to them become permanently unspendable--so allowing the amount to be zero ensures -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. +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")))((("uneconomical outputs", startref="uneconomical")))((("dust policies", startref="dust")))destroyed. ==== Output Scripts