From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YqSHC-0003nv-9x for bitcoin-development@lists.sourceforge.net; Thu, 07 May 2015 20:20:10 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.218.52 as permitted sender) client-ip=209.85.218.52; envelope-from=jeremie.dl@gmail.com; helo=mail-oi0-f52.google.com; Received: from mail-oi0-f52.google.com ([209.85.218.52]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YqSHB-0002Cm-3i for bitcoin-development@lists.sourceforge.net; Thu, 07 May 2015 20:20:10 +0000 Received: by oign205 with SMTP id n205so42914772oig.2 for ; Thu, 07 May 2015 13:20:03 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.33.74 with SMTP id p10mr349247oei.62.1431030003700; Thu, 07 May 2015 13:20:03 -0700 (PDT) Received: by 10.202.210.88 with HTTP; Thu, 7 May 2015 13:20:03 -0700 (PDT) In-Reply-To: References: <554A91BE.6060105@bluematt.me> Date: Thu, 7 May 2015 22:20:03 +0200 Message-ID: From: =?UTF-8?B?SsOpcsOpbWllIER1Ym9pcy1MYWNvc3Rl?= Cc: Bitcoin Dev Content-Type: text/plain; charset=UTF-8 X-Spam-Score: 1.2 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (jeremie.dl[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.2 MISSING_HEADERS Missing To: header -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 1.6 MALFORMED_FREEMAIL Bad headers on message from free email service X-Headers-End: 1YqSHB-0002Cm-3i Subject: Re: [Bitcoin-development] Block Size Increase X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2015 20:20:10 -0000 > I have written up an explanation of what I think will happen if we run out > of capacity: > > https://medium.com/@octskyward/crash-landing-f5cc19908e32 Looks like a solid description of what would happen. I fail to see how this description wouldn't be applicable also to a 20MB-network in some time in the future, say ~3 years from now, if Bitcoin keeps taking off. If you agree that it will be harder in the future to change the block limit again, and we switch to hardcoded 20MB, then aren't we just going from an immediate relief to a future larger blockage? > > Now I'm going to go eat some dinner :) > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >