The mempool, short for memory pool, refers to a temporary storage of valid Bitcoin transactions that have been broadcast across nodes but not yet confirmed. Each full node manages its own mempool, allowing them to exchange information about unconfirmed transactions. Nodes may have unique configurations, affecting how they manage their transactions. Key stakeholders, including miners and exchanges, utilize the mempool differently, with miners focusing on transaction profitability and exchanges monitoring pending transactions. This cooperation allows for a synchronized understanding of the transaction pool across the network.
Each mempool is its own independent island essentially, with its own set of unconfirmed transactions, and sometimes its own configuration variables and settings.
Different nodes have different reasons for running a mempool, and therefore different needs, but it is ultimately through everyone in synchrony running their own mempools interacting with each other that those individual needs are met.
Collection
[
|
...
]