Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That's why it was such a compromise. In order to get the massive decentralization and privacy boost of the malleability fix that segwit provided, the blocksize increase was included to give the increase that the classic hard-fork suggested. And it was done as a soft-fork too, which means none of the 160,000+ bitcoin nodes needed to upgrade their software.

And what happened? After they got exactly what they wanted with the doubling of capacity, they said "we want more" which demonstrated the entire exercise had nothing to do with blocksize, but about stealing the blockchain away from its users, and centralizing it in their data-centers. Which is why, months after the segwit implementation, the biggest and loudest people clamouring for a capacity increase for years, which includes bitpay, the subject of this thread, and coinbase, which has been an actively undermining the bitcoin developers for years, have not even implemented the blocksize increase. So much for blocksize being important.



Privacy boost for a malleability improvement? Do tell.

All full nodes had to upgrade or risk mining invalid blocks.


Nodes don't mine. There are still many nodes using old client node software. Look.

http://luke.dashjr.org/programs/bitcoin/files/charts/softwar...

I don't think you really understand the relationship between nodes and consensus.


>nodes don't mine

Hmm that's not how it used to be. You must be talking about something other than Bitcoin.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: