Bitcoin Forum
April 25, 2018, 05:35:50 AM *
News: Latest stable version of Bitcoin Core: 0.16.0  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Storing unconfirmed tx on disk  (Read 422 times)
btc_enigma
Hero Member
*****
Offline Offline

Activity: 581
Merit: 500


View Profile
December 20, 2015, 05:49:12 AM
 #1

I was thinking about why a non miner node would  keep unconfirmed tx in mempool.

Had a look at this https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009482.html  and http://bitcoin.stackexchange.com/questions/41536/why-does-bitcoin-keep-transactions-in-a-memory-pool.

While I understand the need to relay tx as fast as possible. How is having a mempool mitigating DOS attack. Can someone give me example on this?




Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Quickseller
Copper Member
Legendary
*
Offline Offline

Activity: 1386
Merit: 1061


Hire BOUNTYPORTALS>Bounty management goo.gl/pSzJuA


View Profile WWW
December 20, 2015, 03:30:42 PM
 #2

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.

Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!