You also know that a block size increase is _only the first_ of a string of increase demands that will end up centralizing Bitcoin.
-
-
Replying to @Beautyon_ @DollarJones
It's amazing to me that those who worry about centralization seem to have zero concern with one reference client. >50% of commits are 2 cos.
13 replies 16 retweets 74 likes -
Replying to @ErikVoorhees @seweso and
The worst that development centralization can do is protocol stagnation. Devs can't force users to run changes they don't want.
1 reply 1 retweet 2 likes -
Replying to @hugohanoi @ErikVoorhees and
Which means keeping existing consensus rules if devs' interests start to deviate from users's. That is a good thing.
1 reply 0 retweets 0 likes -
Replying to @hugohanoi @ErikVoorhees and
Transparent OSS process mitigates the problem of development centralization. It's hard to hide intent in code.
1 reply 0 retweets 0 likes -
Replying to @hugohanoi @ErikVoorhees and
So dev centralization worst case is protocol stagnation: network intact. Miner centralization worst case, otoh, reduces network security.
2 replies 0 retweets 0 likes -
Replying to @hugohanoi @ErikVoorhees and
You call protocol stagnation and killing off Bitcoin as a payment system before secure alternatives are ready as network being intact? ....
2 replies 0 retweets 2 likes -
Replying to @seweso @ErikVoorhees and
Protocol stagnation won't kill Bitcoin. Stability promotes a healthy ecosystem. No clear consensus in changes == keeping current consensus.
2 replies 1 retweet 3 likes -
Replying to @hugohanoi
Stability? Full blocks results in instability. Keeping protocol rules, while completely altering how Bitcoin works isn't conservative.

1 reply 0 retweets 0 likes -
Replying to @seweso
A blockchain is a public, limited resource with infinite demand. Full blocks & fee market are unavoidable. There are elegant L2 solutions.
1 reply 0 retweets 0 likes
To be clear there is room for onchain scaling and I support that. Onchain scaling requires HFs though so we should approach that with care.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
