6
2
As more and more Bitcoin transactions are produced, the growth of the Blockchain may well, one day, become a problem for systems which want (need?) to store the whole blockchain.
- Storage usage
- Client startup time
- First-time synchronisation
This answer to "Are there any studies into the size of the blockchain scaling over time?" suggests that Simplified Payment Verification is a good solution, but SPV, as far as I understand it, requires a degree of trust in individual peers that may not be to everyone's taste.
Although I don't really understand the blockchain well enough even to know if this is sensible, the sort of thing that occurs to me might be a mixture of SPV with partial blockchain caching (least frequently used?), where the client keeps a small piece of the blockchain.
Is this really a problem, and is there any work in progress to solve it?
Alternatively, if this isn't a problem, please help me to understand why.
Hi Brent, Actually, just this issue is currently a hotly debated topic. A little while back, Bitcoin Core added support for blockchain pruning, which enables node operators to limit the memory available for blockchain storage. However, then the node will not "store the whole blockchain". Longterm solutions are still in development.
– Murch – 2015-07-24T12:16:35.650@Murch : Thank you - if you'd care to make this an answer, I'd certainly upvote it, and, after a few days, even accept it! – Brent.Longborough – 2015-07-24T12:53:48.533
Sorry, currently at work. I'll have a look later, to write something more encompassing though. – Murch – 2015-07-24T13:18:53.433
@Murch : No problem :) It occurs to me that one might run one's own pruned blockchain node (without a wallet, of course), and assign that as a trusted node for an SPV client. – Brent.Longborough – 2015-07-24T17:00:47.653