Difference between revisions of "Transaction Pools"
AlexMackay (talk | contribs) |
|||
| Line 1: | Line 1: | ||
| − | A ''transaction pool'' or ''mempool'' is a | + | A ''transaction pool'' or ''mempool'' is a set of transactions that are unconfirmed but validated prior to inclusion in a block. |
==Transaction Pools in Bitcoin SV== | ==Transaction Pools in Bitcoin SV== | ||
| − | A bitcoin [[Node| node]] stores bitcoin transactions that have been validated but not mined. It can be thought of as a staging area for transactions prior to their inclusion in a [[block chain|block]]. When creating a new block to mine miners will gather transactions from their | + | A bitcoin [[Node| node]] stores bitcoin transactions that have been validated but not mined. It can be thought of as a staging area for transactions prior to their inclusion in a [[block chain|block]]. When creating a new block to mine, miners will gather transactions from their transaction pool using the rpc command ''getblocktemplate'' to construct a candidate block. Similarly, when receiving a block, a validator can speed-up the validation process if the [[TXID|transactions IDs]] match the transaction IDs in the validator's transaction pool. The transaction pool data is used extensively by block explorers, wallet servers and other Bitcoin SV related web services [https://jochen-hoenicke.de/queue/#3,24h]. |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==See Also== | ==See Also== | ||
| Line 21: | Line 13: | ||
* [1] https://jochen-hoenicke.de/queue/#3,24h | * [1] https://jochen-hoenicke.de/queue/#3,24h | ||
| − | |||
Revision as of 10:45, 21 January 2020
A transaction pool or mempool is a set of transactions that are unconfirmed but validated prior to inclusion in a block.
Transaction Pools in Bitcoin SV
A bitcoin node stores bitcoin transactions that have been validated but not mined. It can be thought of as a staging area for transactions prior to their inclusion in a block. When creating a new block to mine, miners will gather transactions from their transaction pool using the rpc command getblocktemplate to construct a candidate block. Similarly, when receiving a block, a validator can speed-up the validation process if the transactions IDs match the transaction IDs in the validator's transaction pool. The transaction pool data is used extensively by block explorers, wallet servers and other Bitcoin SV related web services [1].