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

The issue of propagation delays with bigger blocks was fixed with xthin blocks (aka: compact blocks) months ago. That is no longer a valid reason for limiting the block size.


There is very limited technical documentation on xthin so it is hard for the community to accept and test it. If Bitcoin were to implement xthin (or an alternative proposal such as compact blocks) it would be much better to release outside of the block increase. again the main contention is the mechanism for change that the Bitcoin unlimited enthusiasts want to impose, a contentious hard fork

And to clarify, the software may have been released (in Bitcoin unlimited's release), but is not used by the Bitcoin network as a whole. Very few nodes are running this implementation. And to many is untested/unproven


You are just spouting false propaganda now. The Core equivalent to Xthin, "Compact Blocks", has been released in Bitcoin Core since version 13.0.0


Please point out where I am spouting false propaganda.... You previously conflated xthin and compact blocks as if they were the same thing. Xthin is not being used by the network. And there are developers who have reasons to believe that increasing the block size will have a centralizing effect on mining. This is not "fixed" as you stated before.


You said: "If Bitcoin were to implement xthin (or an alternative proposal such as compact blocks) it would be much better to release outside of the block increase."

Fact: Both xthin and compact blocks are different implementations of the same idea. Both have already been implemented and released and are in active production.




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

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

Search: