From: Thomas Guyot-Sionnest <dermoth@aei•ca>
To: Cserveny Tamas <cserveny.tamas+bc@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Lucas Clemente Vella <lvella@gmail•com>,
Tom Zander <tomz@freedommail•ch>
Subject: Re: [bitcoin-dev] Horizontal scaling of blockchain
Date: Fri, 1 Sep 2017 15:40:44 -0400 [thread overview]
Message-ID: <e9531342-db9b-ffdf-5ada-0c143eb89d9e@aei.ca> (raw)
In-Reply-To: <CACY+MSOPWhTnR-ZR67T1a5ZU2w4pWa6FkXsGF3_C+n3gKFCPSA@mail.gmail.com>
On 01/09/17 02:15 PM, Cserveny Tamas via bitcoin-dev wrote:
> Yes. I meant the single thread as an analogy, if a block is found,
> other blocks are worthless. (more or less) Longest chain wins.
>
> My line of though was, that currently the only way to scale with the
> traffic (and lowering the fees) is increasing the block size (which is
> hard as I learned from recent events), or reducing the complexity
> which is less secure (most likely more controversial)
>
It wouldn't be less secure as long as you adjust the confirmation
accordingly. If we decided to mine one block every minute, then your
usual 6 confirmation should become 60 confirmation. In the end, the same
amount of work will have been done to prove the transaction is legit and
so it's just as secure... Actually, one could argue since the average
hash rate over 60 block is more accurate than over 6, it's actually more
secure if you also pay attention to hash rate variation as part of the
confirmation... That help in the scenario a very large pool goes dark to
mine a sidechain.
--
Thomas
next prev parent reply other threads:[~2017-09-01 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 12:47 Cserveny Tamas
2017-09-01 13:12 ` Tom Zander
2017-09-01 17:15 ` Lucas Clemente Vella
2017-09-01 17:24 ` Thomas Guyot-Sionnest
2017-09-01 18:15 ` Cserveny Tamas
2017-09-01 19:40 ` Thomas Guyot-Sionnest [this message]
2017-09-02 21:13 ` Tom Zander
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=e9531342-db9b-ffdf-5ada-0c143eb89d9e@aei.ca \
--to=dermoth@aei$(echo .)ca \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=cserveny.tamas+bc@gmail$(echo .)com \
--cc=lvella@gmail$(echo .)com \
--cc=tomz@freedommail$(echo .)ch \
/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