<p>Assuming you are talking about a full node,
It does indeed need to download the full blockchain, to verify it and build up a set of Unspent Transaction Outputs (UTXOs). But the thing is, once it's downloaded all those blocks, its not going to go back looking through them, it just uses the UTXO set to verify new transactions. All those old blocks are basically stored solely for sending to other nodes. So if we have a checkpoint at some block hash, we can say that all blocks before that are legitimate and stop storing them, just store the UTXOs, and then just keep the most recent blocks so we can still propagate them around the network. This greatly reduces the amount of disk space used.</p>

<p>Of course, there are also SPV nodes which just store block headers and rely on full nodes for specific transaction data, so they have blockchains in the megabytes rather than gigabytes. </p>

CC BY-SA 3.0
2017-07-14T23:27:52.150Z
2017-07-14T23:27:52.150Z
meshcollider
<p>I have recently been studying more in-depth how bitcoin actually operates, and I have repeatedly heard that the blockchain in its entirety is many Gigabytes in size. As such, how can the storage space taken up by end-user bitcoin clients by anything less than that, because, for example, satoshi him/herself could send you some bitcoins, and the system would need to reference some really early blocks to verify that transaction?  </p>

<p>Essentially, could someone explain to me or point to a resource detailing why wallet clients only download the 'most recent blocks,' and how this cut-off is decided? </p>

<p>Most bitcoin guides assume every user contains a copy of the entire blockchain, but, in practice, that seems to be incorrect.</p>

<blockchain><storage-footprint>
How Can the Bitcoin Wallet Blockchain Size Be So Small?
Coolio2654
# How Can the Bitcoin Wallet Blockchain Size Be So Small?

(Asked by: username_0 on 2017-07-14)

I have recently been studying more in-depth how bitcoin actually operates, and I have repeatedly heard that the blockchain in its entirety is many Gigabytes in size. As such, how can the storage space taken up by end-user bitcoin clients by anything less than that, because, for example, satoshi him/herself could send you some bitcoins, and the system would need to reference some really early blocks to verify that transaction?

Essentially, could someone explain to me or point to a resource detailing why wallet clients only download the 'most recent blocks,' and how this cut-off is decided?

Most bitcoin guides assume every user contains a copy of the entire blockchain, but, in practice, that seems to be incorrect.

**Tags:** blockchain, storage-footprint


---

## 1 answers

### Answer by username_1 on 2017-07-14. Score: 2

Assuming you are talking about a full node,
It does indeed need to download the full blockchain, to verify it and build up a set of Unspent Transaction Outputs (UTXOs). But the thing is, once it's downloaded all those blocks, its not going to go back looking through them, it just uses the UTXO set to verify new transactions. All those old blocks are basically stored solely for sending to other nodes. So if we have a checkpoint at some block hash, we can say that all blocks before that are legitimate and stop storing them, just store the UTXOs, and then just keep the most recent blocks so we can still propagate them around the network. This greatly reduces the amount of disk space used.

Of course, there are also SPV nodes which just store block headers and rely on full nodes for specific transaction data, so they have blockchains in the megabytes rather than gigabytes.


---

