I read an article that the core developers are beginning to open up to the idea of 2mb block sizes. If Segwit does not get implemented we may see 2mb blocks happen. But I am not sure if it is a "0.13.1b segwit 2mb base 4mb weight" like you said or just a straight 2mb block size hard fork.
the article is not dynamic. but FIXED 2mb.
you really think core want to let the community have self control and not rely on core to spoonfeed code every few months.
What do you mean by that? Self control on what? To my understanding when you are saying "dynamic" you mean dynamic block sizes? If it is only up to 2mb then I believe there is nothing much to manage.
I do not get what you mean by core to spoon feed code every few months by having a fixed 2mb block size. Please explain and please give a suggestion on what better way to do it so that there will be no more need to spoon feed code.
i mean instead of being dynamic where the network can grow without endless downloads by allowing the node users to manually choose their own preference in a setting and broadcast that preference in a way the network can see and grow when satisfactory consensus is reached.
core instead are 'thinking' of just having a fixed 2mb implementation. and lets say in a few years when we want to go passed 2mb we again need core to release another implementation with a higher number. endlessly needing to plead to core to release code. rather than self management and using consensus without downloads
