|
|
|
@ -254,7 +254,7 @@ trusted, public, global ((("bitcoins", "mining", "decentralized consensus", star
|
|
|
|
|
=== Independent Verification of Transactions
|
|
|
|
|
|
|
|
|
|
In
|
|
|
|
|
<<c_transactions>>, we saw how wallet software creates transactions by
|
|
|
|
|
<<c_transactions>>, we saw ((("bitcoins", "mining", "independent transaction verification", id="bitcoin-mining-verify")))((("mining", "independent transaction verification", id="mining-verify")))((("transactions", "independent verification", id="transaction-verify")))((("independent transaction verification", id="independent-transaction-verify")))((("verifying", "transactions", id="verify-transaction")))((("nodes", "transaction verification", id="node-verify")))how wallet software creates transactions by
|
|
|
|
|
collecting UTXOs, providing the appropriate authentication data, and then
|
|
|
|
|
constructing new outputs assigned to a new owner. The resulting
|
|
|
|
|
transaction is then sent to the neighboring nodes in the Bitcoin network
|
|
|
|
@ -303,7 +303,7 @@ address new types of denial-of-service attacks.
|
|
|
|
|
|
|
|
|
|
By independently verifying each transaction as it is received and before
|
|
|
|
|
propagating it, every node builds a pool of valid (but unconfirmed)
|
|
|
|
|
transactions known as the _memory pool_ or
|
|
|
|
|
transactions known ((("bitcoins", "mining", "independent transaction verification", startref="bitcoin-mining-verify")))((("mining", "independent transaction verification", startref="mining-verify")))((("transactions", "independent verification", startref="transaction-verify")))((("independent transaction verification", startref="independent-transaction-verify")))((("verifying", "transactions", startref="verify-transaction")))((("nodes", "transaction verification", startref="node-verify")))as the _memory pool_ or
|
|
|
|
|
_mempool_.
|
|
|
|
|
|
|
|
|
|
=== Mining Nodes
|
|
|
|
|