Tom Zander
Active Member
- Jun 2, 2016
- 208
- 455
Because I don't trust the developers in general to manage the max blocksize limit, and that they can find consensus about what the max blocksize should be in the future. We could get stuck at 32 MB. The threat is real.
And it's just a default setting. Miners may very well adjust it down. Or up. The subtle psychology around the default values should not be underestimated.
I read this 3 times because at first read you are making two incompatible statements. Devs manage max blocksize and miners can just change the setting. They can't both be true...
But on re-read it looks like you think that the developers deciding on a default setting is enough to control the network, in a subtle psychological manner.
In reality the software can't currently handle blocks over 32MiB. And the developers need to do many fixes in order to get there. And, yes, the miners can then change the block size to have a new max, the miners just need to set a value in their client.
What you think about developers having the power over the protocol or not is really not relevant.