Author

Topic: [2016-01-25]Blocktrail CTO and BitcoinJS Co-Maintainer Ruben De Vries (Read 189 times)

full member
Activity: 172
Merit: 100
If voting made any difference they wouldn't let us
The long-lasting block-size dispute has catapulted into the center of attention again. One of the most talked about developments right now is Segregated Witness, of which a public testnet iteration waslaunched last week. The innovation as recently proposed by Blockstream co-founder and Bitcoin Core developer Dr. Pieter Wuille is a centerpiece of a scalability “roadmap” set out by Bitcoin Core.

But relying on Segregated Witness as the next step of Bitcoin’s scalability process is contended by recently launched Bitcoin Core fork Bitcoin Classic. Rather than a Segregated Witness soft fork, Bitcoin Classic prefers to deploy a “cleaner” hard fork in order to increase the block-size limit to 2 megabytes.
To find out where the development community stands on this issue, Bitcoin Magazine reached out to library and wallet developers, those who will need to do the heavy lifting needed to utilize Segregated Witness once rolled out.

In part 1: Blocktrail CTO and BitcoinJS co-maintainer Ruben de Vries.

Segregated Witness

Wuille’s Segregated Witness proposal offers several improvements to the Bitcoin network. The benefit that probably received most attention is its potential to effectively increase the block size to some 1.75 megabytes to 2 megabytes. Interestingly, however, many developers are more excited about the other improvements Segregated Witness has to offer, which they believe makes it well worth the effort.

https://bitcoinmagazine.com/articles/blocktrail-cto-and-bitcoinjs-co-maintainer-ruben-de-vries-segregated-witness-not-very-complicated-1453757293
Jump to: