Nadav Ivgi
2 min readFeb 13, 2017

--

The goalpost was 20MB, there was an attempt at a compromise to 8MB, then an attempt to compromise even more 2MB, which a core developer poison pilled and some core supporters went high gear on character assassination … AXA Blockstream AXA AXA …

Wow, man, you really got your history and facts all mixed up. Where do I begin?

The goalpost was 20MB, there was an attempt at a compromise to 8MB

This is not what happened. Gavin showed some models that he created that were meant to prove 20MB was safe. However, people quickly noticed that he had an arithmetic error in his calculations and that 20MB isn’t safe even by Gavin’s own model.

When corrected, his model showed that the actual safe block size was 8MB, which is why Bitcoin XT corrected it to 8MB. Nothing to do with compromise.

then an attempt to compromise even more 2MB

Again, no :-( Here’s what actually happened:

Then, Bitcoin Classic lead developer Jonathan Toomim did his own analysis and asked the miners what block size they’re willing to support. He found that the miners deem 8MB as too risky and that none of them are willing to go for it.

The block size the miners were willing to support, according to the analysis done by Bitcoin Classic (below), was 2MB. Again, not a compromise.

Ultimately, there was no compromise, because the bitcoin core development team refused any.

The bitcoin development community did release a protocol upgrade that makes the block-size limit larger compared to what Bitcoin Classic was offering, only as a safe, forward-compatible upgrade instead of as a hardfork that could split the network in two.

I fail to see how this is not a compromise.

--

--

Nadav Ivgi

Bitcoin hodler · Founder of @Bitrated · Ambassador at @BitcoinEmbassy TLV · PGP: FCF1 9B67 8665 62F0 8A43 AAD6 81F6 104C D0F1 50FC · Cypherpunks write code.