Message-ID: <559012A9.3050606@sky-ip.org>
Date: Sun, 28 Jun 2015 18:28:41 +0300
From: s7r <s7r@sky-ip.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
	rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>, NxtChg <nxtchg@hush.com>
References: <CAPg+sBjOj9eXiDG0F6G54SVKkStF_1HRu2wzGqtFF5X_NAWy4w@mail.gmail.com>	<20150627074259.GA25420@amethyst.visucore.com>	<20150627095501.C59B541A40@smtp.hushmail.com>	<20150627100400.GC25420@amethyst.visucore.com>	<20150627102912.06E2641A3E@smtp.hushmail.com>	<CABm2gDpnzjph5SKTf+8GWgwe+njS=k2GNm9uL73RC-EV=Y5wug@mail.gmail.com>	<20150627121016.2360041A3E@smtp.hushmail.com>
	<CABm2gDovynxmZmf_voz-19mmb5k0R4Snxcucx-WObt_stkAL9A@mail.gmail.com>
In-Reply-To: <CABm2gDovynxmZmf_voz-19mmb5k0R4Snxcucx-WObt_stkAL9A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] The need for larger blocks
Precedence: list
Reply-To: s7r@sky-ip.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

+1 for this  Jorge.
Agreed the majority should not be able to enforce rules over the
minority. But if the majority will just leave and create an altcoin or
whatever, this will leave the remaining minority with a less value (or
even 0 value) product or service. By enforcing some rules agreed by
the majority or supermajority, the minority will be dragged along and
even so with rules they haven't signed up for, they will still have a
product or service which is worth something.

That is why we have to be very careful into deciding this.

This debate is good, there are lots of valid points from smart people
and I am happy to see there is so much interest in this project, and
regardless if the blocksize hard cap will be changed or not I do hope,
if a hardfork will happen, it will also include a smart change that
will allow future changes (requiring hardforks) simpler, with less
headache and risks involved.

On 6/28/2015 3:13 PM, Jorge Timón wrote:
> On Sat, Jun 27, 2015 at 2:10 PM, NxtChg <nxtchg@hush.com> wrote:
>> 
>> On 6/27/2015 at 2:04 PM, "Jorge Timón" <jtimon@jtimon.cc> wrote:
>> 
>>> But that option is not unknown...
>> 
>> It is, until it actually happens. Before that, anything is a
>> speculation. That's why risk is attached to both "doing nothing"
>> and "raising the limit".
> 
> Fortunately we have a lower limit in the standard mining policy to
> see if the skies turn purple when we hit that limit like some
> people predict.
> 
>> Various people perceive these risks differently and there is no
>> clear mechanism currently to somehow gauge what the majority
>> wants. So it's tempting to just give up and say: let's do
>> nothing.
>> 
>> In this situation, doing a "software fork" seems like the only
>> way to actually see how many people/interests are in favor of
>> bigger blocks.
> 
> But this is NOT a way to see the majority of anything. I can run
> 1000 nodes, have you heard of sybil attacks? There's simply no
> decentralized way of voting that works. Otherwise we could vote on
> each block instead of using proof of work. Miners voting on size is
> also ridiculous since big miners have an incentive to completely
> remove the limit and make smaller miners unprofitable.
> 
>> (Whether the majority has a moral right to dictate the minority
>> is a tough philosophical question, which should probably be left
>> out of this discussion :)
> 
> No, this is very important. The majority has no right to dictate
> on the minority. If the majority of bitcoiners wanted demurrage
> (and we actually had a working method for "measuring majorities"),
> the minority would still say "these are not the rules we signed up
> for, go make freicoin as a separate chain". And that is very
> reasonable. If some people want a more centralized version of
> Bitcoin they can create an altcoin too. Doesn't dogecoin already
> have big blocks? _______________________________________________ 
> bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org 
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBCAAGBQJVkBKpAAoJEIN/pSyBJlsR4FMIAITS10rtx4Uw20WjFPkWZRB3
ucRRPncXkKehQlFd9cY6sgPAUk50rM0FSpm69Ra1KnawNLLxkgpzTGZk1iTHbGe8
JlWoTduLOyvInVXCdM8l71TVWoyt8rDZpg1KAsaMmMi9UvstHZPGZp85XScxhYyC
uBHv1Hm7oeszPBkjGsB9B9mF/gH8naCjcNva+XbcgsKNM681xbOeJQ9qW0GOwq+Z
j4ocY77G8AENZkhCy2KKiJrz0ZBVDbnJAos06uKrdxhUPBwliVpyJW96aFsRp/sL
SNqTkpSmvxgSUBHCrRoWiBf/xo06W9QeoEfoROfgFkSTcUlPWqCJHxqwOLk2VrY=
=eUgF
-----END PGP SIGNATURE-----