BitcoinCash/specification
1
Fork 0
Code Issues Pull Requests Releases Activity

Fixing links and other merge issues.

Browse Source
This commit is contained in:
Andrew Groot
2020-11-05 10:26:59 -05:00
parent f74cc51632
commit 629c886f87
4 changed files with 31 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files
protocol/blockchain/memory-pool.md
+7 -6
View File
@@ -1,7 +1,7 @@
# Memory Pool
# Memory Pool
The Bitcoin Cash memory pool, or mempool, is a staging area for valid Bitcoin Cash [transactions](protocol\blockchain\transaction) waiting to be added to the [blockchain](protocol\blockchain).
[Valid transactions](protocol\blockchain\transaction-validation) received from the network are usually cached in the mempool and are removed once they are mined into a [block](protocol\blockchain\block).
The Bitcoin Cash memory pool, or mempool, is a staging area for valid Bitcoin Cash [transactions](/protocol/blockchain/transaction) waiting to be added to the [blockchain](/protocol/blockchain).
[Valid transactions](/protocol/blockchain/transaction-validation) received from the network are usually cached in the mempool and are removed once they are mined into a [block](/protocol/blockchain/block).
Bitcoin Cash nodes typically employ mempools to increase their responsiveness, enabling them to accept and validate transactions anytime even though new blocks are only mined once per 10 minutes on average.
Mining nodes are also incentivized to do so in order to collect larger amounts of transaction fees from groups of transactions for every block mined.
@@ -17,14 +17,14 @@ Although this rarely occurs, mempools may reach their maximum capacity set by th
The policies regarding such scenarios are at the discretion of each node.
Apart from the capacity reasons, transactions that once were considered valid may still be rejected from adding to the mempool or removed from the mempool for other reasons.
## Rejection of transactions to the mempool
## Rejection of transactions to the mempool
Valid transactions may be rejected by the node to enter the mempool for several typical reasons.
1. Transactions may be rejected if they fail to meet the minimum transaction fee set by the node.
This usually happens if the mempool is approaching its capacity or if the transactions are considered [dust transactions](transaction-validation\network-level-validation-rules#dust).
This usually happens if the mempool is approaching its capacity or if the transactions are considered [dust transactions](/protocol/blockchain/transaction-validation/network-level-validation-rules#dust).
2. Transactions that double spend inputs of another transaction already in the mempool will be rejected.
3. [Non-standard](transaction-validation\network-level-validation-rules#standard-transactions) transactions are often rejected.
3. [Non-standard](/protocol/blockchain/transaction-validation/network-level-validation-rules#standard-transactions) transactions are often rejected.
## Removal of transactions from the mempool
@@ -34,4 +34,5 @@ The reasons for such removal may include but not limited to:
1. Nodes may remove the transactions that are no longer valid after a blockchain reorg, such as transactions that double spend inputs of existing transactions in the blockchain or transactions that spend outputs that are now time-locked due to reduced block height or earlier median time-past (MTP) after the blockchain reorg.
2. Transactions may be removed when new blocks are received, such as transactions included in the received blocks or transactions that double spend inputs of transactions in the new blocks.
3. Nodes may remove transactions due to performance or capacity constraints.
Typically, transactions that provide low fees may be removed when the mempool is approaching its capacity or after prolonged periods in the mempool without being mined.