Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id EB169486 for ; Thu, 19 Oct 2017 06:52:50 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-pg0-f65.google.com (mail-pg0-f65.google.com [74.125.83.65]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 3F7DE196 for ; Thu, 19 Oct 2017 06:52:50 +0000 (UTC) Received: by mail-pg0-f65.google.com with SMTP id g6so6325036pgn.6 for ; Wed, 18 Oct 2017 23:52:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thancodes.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=EXx1iuNI4nsmWu2JUwXq8REQ0emC3xD0FJR+SmJGChI=; b=u+HH4rhYA+XJVzrUqx0txZkjwuJ1/BTiT671x2u/vPnbqfCHv0xrQUR1KnZVv/AAr6 mioYeIS5VoN5XZ3ds66Q8IulgI+LkwP6Dhwjbw8xz8pj784UCcCs+NCeG7wvLZn+iIKE 2i6oTU4GDFQn/IBSii/GWcCi+Wzu5B2LtvZtWv742Yr2dHa0Tx5xyYbPmQ+dxl0APa1Y Xys6QaG8pSUGNR90DF/HwPy5MbGv/f7eBNkgaoDgpxarREy70nhTteFE4oOzoX1+Vv8g eW01zwMNnCvaj3U1ZQHxoigWJoOzEFGj7wGp2PK/jdxQXrK9d3fyISu/iU1G0jWTZxII wsSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=EXx1iuNI4nsmWu2JUwXq8REQ0emC3xD0FJR+SmJGChI=; b=RZQUVeqcjj0lKCUTFH88xX+13NBHaCFt7PdqtDEyjsFOVveN5tN4dOXhli5bz3cr5s e+YC3TpeMPdmf/IG/njwqF/K7g1Sb9PkSofIssB5YwizNqUV31INrkTDnSSkGSm6xVFV VwC+byb1kMriWcxnV/510/ljNzd4bVDIl+hk9PknB3MNlkw/LCMOjU4k6Y+bEGo/AqPZ HH7q57Ckml2z+p6r/KsJywpCUKI+sJ4zRmMh3nOy2O/dMnhjNfAexzy5wyzJoqukPN8O /sBfXmDPxkxLmU6fQvv0QNfm5qeu2AH6N1szjulkeSKXoBERpAfDHTgLGv9GUwQ0qFU+ xNog== X-Gm-Message-State: AMCzsaWaOm6GB2WHVfVsExUCI1g114Scl/GL5AYVhI9Oj7pT9hA8+HCm ab4jb5OIgXcuE1f2fKcvSYZNXi7AxKcIyEcHBYRYnHwMot0= X-Google-Smtp-Source: ABhQp+RmGokQAQHpIWSlqpMRRUPW8UCYSuR72nHsgUTQi1lwpM+44Hk5ms4nVmdRXmyESyYkAnANFY5FGmO+hncJTHk= X-Received: by 10.84.129.228 with SMTP id b91mr669484plb.56.1508395969431; Wed, 18 Oct 2017 23:52:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.174.204 with HTTP; Wed, 18 Oct 2017 23:52:48 -0700 (PDT) From: Jonathan Sterling Date: Thu, 19 Oct 2017 14:52:48 +0800 Message-ID: To: bitcoin-dev@lists.linuxfoundation.org Content-Type: multipart/alternative; boundary="94eb2c119bb6f05bf0055be0cdac" X-Spam-Status: No, score=0.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM autolearn=disabled version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Thu, 19 Oct 2017 12:50:52 +0000 Subject: [bitcoin-dev] Improving Scalability via Block Time Decrease X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2017 06:52:51 -0000 --94eb2c119bb6f05bf0055be0cdac Content-Type: text/plain; charset="UTF-8" The current ten-minute block time was chosen by Satoshi as a tradeoff between confirmation time and the amount of work wasted due to chain splits. Is there not room for optimization in this number from: A. Advances in technology in the last 8-9 years B. A lack of any rigorous formula being used to determine what's the optimal rate C. The existence of similar chains that work at a much lower block times Whilst I think we can all agree that 10 second block times would result in a lot of chain splits due to Bitcoins 12-13 second propagation time (to 95% of nodes), I think we'll find that we can go lower than 10 minutes without much issue. Is this something that should be looked at or am I an idiot who needs to read more? If I'm an idiot, I apologize; kindly point me in the right direction. Things I've read on the subject: https://medium.facilelogin.com/the-mystery-behind-block-time-63351e35603a (section header "Why Bitcoin Block Time Is 10 Minutes ?") https://bitcointalk.org/index.php?topic=176108.0 https://bitcoin.stackexchange.com/questions/1863/why-was-the-target-block-time-chosen-to-be-10-minutes Kind Regards, Jonathan Sterling --94eb2c119bb6f05bf0055be0cdac Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The current ten-minute block time was chosen by Satos= hi as a tradeoff between confirmation time and the amount of work wasted du= e to chain splits. Is there not room for optimization in this number from:<= br>
A. Advances in technology in the last 8-9 years
B. A lack = of any rigorous formula being used to determine what's the optimal rate=
C. The existence of similar chains that work at a much lower blo= ck times

Whilst I think we can all agree that 10 second= block times would result in a lot of chain splits due to Bitcoins 12-13 se= cond propagation time (to 95% of nodes), I think we'll find that we can= go lower than 10 minutes without much issue. Is this something that should= be looked at or am I an idiot who needs to read more? If I'm an idiot,= I apologize; kindly point me in the right direction.

Th= ings I've read on the subject:
https://medium.faci= lelogin.com/the-mystery-behind-block-time-63351e35603a (section header = "Why Bitcoin Block Time Is 10 Minutes ?")

Kind Regards,

Jonathan Sterling
--94eb2c119bb6f05bf0055be0cdac--