From: Melvin Carvalho <melvincarvalho@gmail•com>
To: Jefferson Carpenter <jeffersoncarpenter2@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Upgrading PoW algorithm
Date: Sat, 20 Jan 2018 19:36:09 +0100 [thread overview]
Message-ID: <CAKaEYhJHZ_CFeqRN_QXP-SLX+AHmbRPTx+w=D3920Fc-WPq_1A@mail.gmail.com> (raw)
In-Reply-To: <58fa85b8-cba3-ee34-8c96-41c6c7bfbf9c@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1885 bytes --]
On 17 January 2018 at 23:31, Jefferson Carpenter via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> Bitcoin's difficulty will be maxed out within about 400 years, by Moore's
> law. (After that - supposing the software does not crash when difficulty
> overflows - block time will start decreasing, and it will not take long
> before blocks are mined faster than photons can be sent across the planet).
>
> Bitcoin is the dominant cryptocurrency today, as the first mover: the
> perfectly fair worldwide game of inventing the cryptocurrency has been
> played and won. However, unfortunately, it has a built-in end date: about
> 400 years from now. After that, it won't necessarily be clear what the
> dominant cryptocurrency is. It might be a lot like VHS vs Betamax, and a
> lot of people could lose a lot of money. It seems to me, this could be
> mitigated by planning today for what we are going to do when Bitcoin
> finally breaks 400 years from now.
>
> Are there any distinct plans today for migrating to a PoW supporting an
> even higher difficulty?
>
Crypto algorithms have a lifetime, and consensus is no different.
Is it likely to be more than a few years? Yes.
Is likely to be less than a few hundred years. Yes.
Every algorithm involves trade offs and it's the job of a thoughtful dev
team to examine those trade offs and come to a consensus optimal solution.
This field is only 9 years old, and there is a large amount of R & D in
this area. So we can evaluate what seems to working better and what seems
to be working worse, transfer that to BIPs, create code, test it, try to
achieve consensus. The normal path that has served free software projects
well.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 2710 bytes --]
next prev parent reply other threads:[~2018-01-20 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 22:31 Jefferson Carpenter
2018-01-18 16:36 ` Peter Todd
2018-01-19 20:54 ` Jefferson Carpenter
2018-01-20 6:30 ` nullius
2018-01-20 18:36 ` Melvin Carvalho [this message]
2018-01-21 15:29 ` Glen Peterson
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='CAKaEYhJHZ_CFeqRN_QXP-SLX+AHmbRPTx+w=D3920Fc-WPq_1A@mail.gmail.com' \
--to=melvincarvalho@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jeffersoncarpenter2@gmail$(echo .)com \
/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