Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 1DC60AC9 for ; Tue, 25 Aug 2015 20:26:27 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [69.252.207.39]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B9F3019C for ; Tue, 25 Aug 2015 20:26:26 +0000 (UTC) Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-07v.sys.comcast.net with comcast id 98Rm1r0092Bo0NV018SR3i; Tue, 25 Aug 2015 20:26:25 +0000 Received: from crushinator.localnet ([IPv6:2601:186:c000:825e:e9f4:8901:87c7:24a0]) by resomta-ch2-05v.sys.comcast.net with comcast id 98SP1r00H4eLRLv018SQvo; Tue, 25 Aug 2015 20:26:24 +0000 From: Matt Whitlock To: bitcoin-dev@lists.linuxfoundation.org, Peter Todd Date: Tue, 25 Aug 2015 16:26:23 -0400 Message-ID: <1489961.GhSFCGzPRJ@crushinator> User-Agent: KMail/4.14.10 (Linux/4.0.5-gentoo; KDE/4.14.11; x86_64; ; ) In-Reply-To: <20150825201643.GC11083@muck> References: <20150825201643.GC11083@muck> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1440534385; bh=/LJ3Sr6e3XdZivDAU5VX1XuUcAFk3TnlzUgX39AI2Co=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=UG7yMsEY2/8wEOAWsYAVcScUTIdiZ2pB9EA8U7AMS3SLvUPjpYXynDgByzsO+4Sfg n1Puanfd/QF7BF4IR8h9E+gq1qDc6ihpuqYHnIvNzgNwnFhHEJHZKQmyL9h+czNSe5 5mmefqjaNpinOHpl1KPWuxfvkWTM2hSBDYuzpLS1kcJJDCYgq6x65Ne48b9Gu/vaaz OmdNIsn7wK94PCpjji/VyNG8tnh7ek1rQjwNy5bI1q62lhsmoj1+R4xidw/driFBsc bgqGxg2vYC7bVw9fnarrDlwnpa9BJSVBlts3euj1Z905jiRBzBfp9NA8KWl0HnKNb+ w3z7DUC3bmjpA== X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: greg@xiph.org Subject: Re: [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap [BIP 1xx - Draft] X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2015 20:26:27 -0000 On Tuesday, 25 August 2015, at 1:16 pm, Peter Todd via bitcoin-dev wrote: > What would you think of an approach like John Dillon's proposal to > explicitly give the economic majority of coin holders a vote for the max > blocksize? Miners could still vote BIP100 style for what max they were > willing to use, limited in turn by the vote of the economic majority. What fraction of coin holders do you suppose will vote? And, of those, what fraction have the technical knowledge to make an informed vote? It would be like polling Toyota truck owners to see whether the 2017 Tacoma should increase its engine's cylinder displacement by 10%. Ordinary users just aren't going to be able to vote meaningfully, and most won't respond to the poll at all.