|
December 20, 2015, 03:30:42 PM |
|
If you do not store unconfirmed transactions in the mempool then when your node receives a transaction that relies on an unconfirmed transaction it will reject such transaction even though it is valid.
I believe the person answering the stackexchange answer was referring specifically to storing the mempool in memory as opposed to disk. Someone could send a large number of transactions that would cause bitcoind to be consistently writing data on your hard drive (when it receives a new transaction) and reading data on your hard drive (when it needs to make sure a transaction that relies on an unconfirmed transaction is valid) which contributes to wear and tear to your hard drive.
|