Skip to main content
4 of 5
added 160 characters in body
RedGrittyBrick
  • 28.5k
  • 3
  • 25
  • 53

A pruned node discards from persistent storage (disk, SSD) blocks for which it has no further use.

A pruned node therefore cannot help with the initial synchronisation of a new full-node.

A pruned node can pass on unconfirmed transactions in its mempool and, in the case of BIP-159 compliant software such as Bitcoin core, the 288 blocks prior to, and including, to their active chain-tip.

A pruned node downloads exactly the same amount of data per month as a fully-synchronised full-node. It probably uploads less since it retains less. Actual amounts probably depend on connectivity and levels of Bitcoin network activity (i.e I haven't measured this).


RedGrittyBrick
  • 28.5k
  • 3
  • 25
  • 53