|
|
|
|
@ -379,7 +379,7 @@ include more types of transactions.
|
|
|
|
|
|
|
|
|
|
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 _transaction pool_, _memory pool_, or
|
|
|
|
|
transactions known as the _memory pool_ or
|
|
|
|
|
_mempool_.
|
|
|
|
|
|
|
|
|
|
=== Mining Nodes
|
|
|
|
|
@ -414,8 +414,8 @@ id="MACaggreg10")))((("transactions", "aggregating into blocks",
|
|
|
|
|
id="Taggreg10")))((("blocks", "aggregating transactions into",
|
|
|
|
|
id="Baggreg10")))((("blocks", "candidate blocks")))((("candidate
|
|
|
|
|
blocks")))((("transaction pools")))((("memory pools (mempools)")))After
|
|
|
|
|
validating transactions, a Bitcoin node will add them to the _memory
|
|
|
|
|
pool_, or _transaction pool_, where transactions await until they can be
|
|
|
|
|
validating transactions, a Bitcoin node will add them to the mempool
|
|
|
|
|
where transactions wait until they can be
|
|
|
|
|
included (mined) into a block. Jing's node collects, validates, and
|
|
|
|
|
relays new transactions just like any other node. Unlike other nodes,
|
|
|
|
|
however, Jing's node will then aggregate these transactions into a
|
|
|
|
|
|
David A. Harding
12 months ago