From f1a1f69b7b03ad559c4b6f5002dbd89440e7531a Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 20:10:55 +0000 Subject: [PATCH] Edited appa_whitepaper.adoc with Atlas code editor --- appa_whitepaper.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appa_whitepaper.adoc b/appa_whitepaper.adoc index d8cb9592..b0ff0ce8 100644 --- a/appa_whitepaper.adoc +++ b/appa_whitepaper.adoc @@ -85,7 +85,7 @@ image::images/mbc3_aain05.png["spv"] As such, the verification is reliable as long as honest nodes control the network, but is more vulnerable if the network is overpowered by an attacker. While network nodes can verify transactions for themselves, the simplified method can be fooled by an attacker's fabricated transactions for as long as the attacker can continue to overpower the network. One strategy to protect against this would be to accept alerts from network nodes when they detect an invalid block, prompting the user's software to download the full block and alerted transactions to confirm the inconsistency. Businesses that receive frequent payments will probably still want to run their own nodes for more independent security and quicker ((("payment verification", "in Bitcoin whitepaper", secondary-sortas="Bitcoin whitepaper", startref="payment-verify")))((("verifying payment", "in Bitcoin whitepaper", secondary-sortas="Bitcoin whitepaper", startref="verify-payment")))verification. ==== Combining and Splitting Value -Although ((("transactions", "inputs/outputs")))((("inputs", "in Bitcoin whitepaper", secondary-sortas="Bitcoin whitepaper")))((("outputs", "in Bitcoin whitepaper", secondary-sortas="Bitcoin whitepaper")))it would be possible to handle coins individually, it would be unwieldy to make a separate transaction for every cent in a transfer. To allow value to be split and combined, transactions contain multiple inputs and outputs. Normally there will be either a single input from a larger previous transaction or multiple inputs combining smaller amounts, and at most two outputs: one for the payment, and one returning the change, if any, back to the sender. +Although ((("transactions", "inputs", "in Bitcoin whitepaper", secondary-sortas="Bitcoin whitepaper")))((("transactions", "outputs", "in Bitcoin whitepaper", secondary-sortas="Bitcoin whitepaper")))((("inputs", "in Bitcoin whitepaper", secondary-sortas="Bitcoin whitepaper")))((("outputs", "in Bitcoin whitepaper", secondary-sortas="Bitcoin whitepaper")))it would be possible to handle coins individually, it would be unwieldy to make a separate transaction for every cent in a transfer. To allow value to be split and combined, transactions contain multiple inputs and outputs. Normally there will be either a single input from a larger previous transaction or multiple inputs combining smaller amounts, and at most two outputs: one for the payment, and one returning the change, if any, back to the sender. image::images/mbc3_aain06.png["combining-splitting"]