5 ms·
Because right now you can't distribute the UXTO set in a trustless way. Core developers blocked it two years ago for nonsensical reasons [1], one of the many re
by SnowProblem 9y ago
Because right now you can't distribute the UXTO set in a trustless way. Core developers blocked it two years ago for nonsensical reasons [1], one of the many reasons the community doesn't trust them. Work has picked up on this in BCH [2].
[1] https://bitcoincore.org/en/meetings/2016/03/10/#initial-block-download-ibd-with-pre-generated-signed-utxos https://bitcoincore.org/en/meetings/2016/03/10/#initial-bloc...
[2] https://github.com/bitcoincashorg/workgroups/blob/master/wg-utxocommit-sync/workgroup.md https://github.com/bitcoincashorg/workgroups/blob/master/wg-...
- Ajedi32 9y agoWait, so that solution is essentially just trusting a few members of the community to decide what everyone's Bitcoin balance is? (Pick a few people to sign the UXTO and just trust their signatures?) I'm kinda surprised you consider the dev's rejection of that idea to be "nonsensical". Seems perfectly sensible to me that they wouldn't want to grant that kind of authority to any particular set of individuals. In particular, that method is most certainly _not_ "a trustless way" of distributing the UXTO. Hopefully whatever solution the BCH devs are working on isn't anything like that...
- SnowProblem 9y agoIt's nonsensical to shutdown the discussion so quickly. This wasn't a BIP. You can hash the UXTO set and put the hash in the blockchain, or put the UXTO set in special blocks, or cross-validate the UXTO set across nodes. There are solutions.