[Bitcoin-development] Block Size Increase
jtimon at jtimon.cc
Thu May 7 16:47:53 UTC 2015
On Thu, May 7, 2015 at 6:11 PM, Mike Hearn <mike at plan99.net> wrote:
>> It is an argument against my admittedly vague definition of
>> "non-controversial change".
> If it's an argument against something you said, it's not a straw man, right
Yes, but it was an argument against something I didn't said ;)
> Consensus has to be defined as agreement between a group of people. Who are
> those people? If you don't know, it's impossible to decide when there is
> consensus or not.
> Right now there is this nice warm fuzzy notion that decisions in Bitcoin
> Core are made by consensus. "Controversial" changes are avoided. I am trying
> to show you that this is just marketing. Nobody can define what these terms
> even mean. It would be more accurate to say decisions are vetoed by whoever
> shows up and complains enough, regardless of technical merit.
Yes, that's why I drafted a definition for "uncontroversial change"
rather than "change accepted by consensus".
It will still be vague and hard to define, but consensus seems much harder.
And, yes, you're right, it is more like giving power to anyone with
valid arguments to veto hardfork changes.
But as you say, that could lead to make hardforks actually impossible,
so we should limit what constitutes a valid argument.
I later listed some examples of invalid arguments: logical fallacies,
unrelated arguments, outright lies.
Certainly I don't think technical merits should count here or that we
could veto a particular person from vetoing.
We should filter the arguments, not require an identity layer to
We should even accept arguments from anonymous people in the internet
(you know, it wouldn't be the first time).
> Unfortunately it's hard to know what other kinds of meet-in-the-middle
> compromise could be made here. I'm sure Gavin would consider them if he
> knew. But the concerns provided are too vague to address. There are no
> numbers in them, for example:
> We need more research -> how much more?
Some research at all about fee market dynamics with limited size that
hasn't happened at all.
If we're increasing the consensus max size maybe we could at least
maintain the 1MB limit as a standard policy limit, so that we can
study it a little bit (like we could have done instead of removing the
initial policy limit).
> I'm not against changing the size, just not now -> then when?
I don't know yet, but I understand now that having a clearer roadmap
is what's actually urgent, not the change itself.
> I'm not wedded to 1mb, but not sure 20mb is right -> then what?
What about 2 MB consensus limit and 1 MB policy limit for now? I know
that's arbitrary too.
> Full node count is going down -> then what size do you think would fix that?
As others have explained, the number of full nodes is not the
improtant part, but how easy it is to run one.
I think a modest laptop with the average internet connection of say,
India or Brazil, should be able to run a full node.
I haven't made those numbers myself but I'm sure that's possible with
1 MB blocks today, and probably with 2 MB blocks too.
> It will make mining more centralised -> how do you measure that and how much
> centralisation would you accept?
This is an excellent question for both sides.
Unfortunately I don't know the answer to this. Do you?
More information about the bitcoin-dev