Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id D5F1E8A7 for ; Wed, 12 Aug 2015 16:41:39 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from pmx.vmail.no (pmx.vmail.no [193.75.16.11]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 5E833218 for ; Wed, 12 Aug 2015 16:41:39 +0000 (UTC) Received: from pmx.vmail.no (localhost [127.0.0.1]) by localhost (pmx.isp.as2116.net) with SMTP id 3EB6944BA9 for ; Wed, 12 Aug 2015 18:41:38 +0200 (CEST) Received: from smtp.bluecom.no (smtp.bluecom.no [193.75.75.28]) by pmx.vmail.no (pmx.isp.as2116.net) with ESMTP id AD3E544A29 for ; Wed, 12 Aug 2015 18:41:37 +0200 (CEST) Received: from pluto.localnet (unknown [81.191.177.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.bluecom.no (Postfix) with ESMTPS id 93FC4AA for ; Wed, 12 Aug 2015 18:41:37 +0200 (CEST) From: Thomas Zander To: Bitcoin Dev Date: Wed, 12 Aug 2015 18:41:36 +0200 Message-ID: <2133828.JttggH90JM@pluto> User-Agent: KMail/4.14.1 (Linux/3.16.0-4-amd64; KDE/4.14.2; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] A summary list of all concerns related to rising the block size 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: Wed, 12 Aug 2015 16:41:39 -0000 On Wednesday 12. August 2015 12.28.39 Jorge Tim=F3n wrote: > But let's just list the concerns first. Concerns? I have never heard of "develop-by-concerns"? Is that similar to=20 fire fighting management? To that I have this reply; http://www.aleanjourney.com/2009/07/stop-fighting-fires.html Your question makes sure that the proper answers don't fit. And that may be why you are getting frustrated because I've given a lot= of=20 reasons why a blocksize increase is needed soon, and none of them show = up=20 in your list... http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/0101= 20.html http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/0101= 29.html And various others; I'm not going to bother pasting URLs, you probably = have=20 them already. Point is, Bitcoin is a growing network, with a growing amount of transa= ctions=20 and we KNOW we will get into problems when the block consistently get f= ull.=20 How do we know? Because of the old guys in this list having the experie= nce=20 that this always happens, because anyone in the IT business can tell yo= u the=20 same. We have started LN to cope with this growth, but this won't be enough s= ince it=20 just won't handle all usecases and thus the on-chain growth will contin= ue. For=20 instance remittances and cross-border purchases. We need both LN as well as bigger blocks. --=20 Thomas Zander