3 ms·
To me the most interesting thing here is "Rolling UTXO set hashes". Bitcoin has a (theoretical future) scaling problem because the blockchain keeps growing fore
by modeless 9y ago
To me the most interesting thing here is "Rolling UTXO set hashes". Bitcoin has a (theoretical future) scaling problem because the blockchain keeps growing forever without bound. No matter what you think about Moore's law, everyone knows it can't go on forever, so an infinitely large blockchain is not sustainable. With UTXO set hashes included in blocks, ancient blockchain history can be discarded on a rolling basis, turning the infinitely large blockchain into a fixed size rolling chain.
This doesn't solve the whole problem as the UTXO set itself also grows, but I suspect appropriate incentives could manage this problem (fees for increasing UTXO set size and/or bounties for reducing it).
With these problems solved, Bitcoin would theoretically be able to operate indefinitely without issue. Of course many practical scaling problems remain, the most important being the transaction rate cap.
- kanzure 9y agorolling UTXO set hashes: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014337.html https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017... high-performance merkle set implementation http://diyhpl.us/wiki/transcripts/sf-bitcoin-meetup/2017-07-08-bram-cohen-merkle-sets/ http://diyhpl.us/wiki/transcripts/sf-bitcoin-meetup/2017-07-... and https://github.com/bramcohen/MerkleSet https://github.com/bramcohen/MerkleSet "Making UTXO set growth irrelevant with low-latency delayed TXO commitments" https://petertodd.org/2016/delayed-txo-commitments https://petertodd.org/2016/delayed-txo-commitments "TXO commitments do not need a soft-fork to be useful" https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-February/013591.html https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017...
- kushti 9y agoThe problem would be still to maintain the UTXO set. Fortunately, by using a two-party dynamic authenticated data structure, it is possible to have only miners(and also powerful full nodes willing to hold full-state, like block explorers etc) to store the whole set, while others can check proofs of set transformations included into blocks, storing just 32 bytes. For details, see introduction to the paper https://eprint.iacr.org/2016/994 https://eprint.iacr.org/2016/994 (and blockchain processing benchmark graph, 2nd half of pg. 14)
- MichaelGG 9y ago> so an infinitely large blockchain is not sustainable. This is a bit misleading. With 1MB blocks a 2TB drive holds around 40 years. So put that out a century and we're still talking nearly nothing. Even with 32MB blocks it's not exactly a gigantic commitment, needing a drive every few years. Having a nice way to checkpoint utxo is good to get people bootstrapped but it's not like block chain size is a serious issue.
- kobeya 9y agoThe problems with large blocks are not disk space.
- olala69 9y agoPeople who think the problem with large blocks is disk space or internet speed are the worst tbh
- igreulich 9y agoWithout getting into the 'vim vs emacs' type debate rolling through the bitcoin community, why? Why is storage not 'the problem'? I am not trying to kick a hornets nest here, I am genuinly trying to understand.
- MichaelGG 9y agoCause a 2TB drive is so cheap? People wanting to run a full node can easily afford it. But if BTC stays with small blocks and becomes a settlement layer, nobody will even care about running a node in the first place. Why would I want to run a node to validate payments between corporations? Increasing blocks increases the load on nodes somewhat, but it keeps the system much more peer to peer, as transaction fees won't end up as high. There's no obvious easy solution, but making the network expensive and congested is certainly not a real solution.
- deleted 9y ago[deleted]