On Monday, 17 April 2017 08:54:49 CEST David Vorick via bitcoin-dev wrote: > The best alternative today to storing the full blockchain is to run a > pruned node
The idea looks a little overly complex to me. I suggested something similar which is a much simpler version; https://zander.github.io/scaling/Pruning/ > # Random pruning mode > > There is a large gap between the two current modes of everything > (currently 75GB) and only what we need (2GB or so). > > This mode would have two areas, it would keep a days worth of blocks to > make sure that any reorgs etc would not cause a re-download, but it would > have additionally have an area that can be used to store historical data > to be shared on the network. Maybe 20 or 50GB. > > One main feature of Bitcoin is that we have massive replication. Each node > currently holds all the same data that every other node holds. But this > doesn't have to be the case with pruned nodes. A node itself has no need > for historic data at all. > > The suggestion is that a node stores a random set of blocks. Dropping > random blocks as the node runs out of disk-space. Additionally, we would > introduce a new way to download blocks from other nodes which allows the > node to say it doesn't actually have the block requested. > > The effect of this setup is that many different nodes together end up > having the total amount of blocks, even though each node only has a > fraction of the total amount. -- Tom Zander Blog: https://zander.github.io Vlog: https://vimeo.com/channels/tomscryptochannel _______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
