From: Jonathan Sterling <jon@thancodes•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Improving Scalability via Block Time Decrease
Date: Thu, 19 Oct 2017 14:52:48 +0800 [thread overview]
Message-ID: <CAH01uEtLhLEj5XOp_MDRii2dR8-zUu4fUsCd25mzLDtpD_fwYQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1686 bytes --]
next reply other threads:[~2017-10-19 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 6:52 Jonathan Sterling [this message]
2017-10-19 13:41 ` Adán Sánchez de Pedro Crespo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH01uEtLhLEj5XOp_MDRii2dR8-zUu4fUsCd25mzLDtpD_fwYQ@mail.gmail.com \
--to=jon@thancodes$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox