From: Erik Aronesty <erik@q32.com>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] hashcash-newhash
Date: Wed, 27 May 2020 10:12:26 -0400 [thread overview]
Message-ID: <CAJowKgJf2vBQc6Xh8sZeuxpvh5OK8FnSbVXr3K4do8VE_XXYiA@mail.gmail.com> (raw)
In-Reply-To: <-auynbGgS6bfeQq-_RU-Hfxe-uu2dR50iJXHUUvXM0mu0IKvUmQILrX4SzJ9QEK4KyHS2OGscd00f61hdWCQM3CHdrxMBMhfA9okmIlgqC8=@protonmail.com>
> What you are focusing on is only this:
>
> * Proof-of-work.
Bitcoin's primary value proposition is that it's the most resistant to
change: All other coins are these malleable things centrally
controlled and easily moved about by politics and nonsense. So
discussions of POW changes... open up this can of worms (myself being
one of them).
- should also discuss "proof-of-burn", where a burn is performed as a
similar investment-over-time with true loss/risk.
- should discuss moving to sha3 (or something like it) for
everything, not just POW
> However, do note that I doubt that changing the proof-of-work function (and *only* the proof-of-work function) is in any way a high priority.
Yeah, a hard fork like this would be a massive undertaking, with a
zillion "improvements" argued about for years and the final version
some minimal thing that just changes the hash algo and invalidates
legacy stuff (since back compat is not a concern).
next prev parent reply other threads:[~2020-05-27 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2587.1590231461.32591.bitcoin-dev@lists.linuxfoundation.org>
2020-05-23 11:00 ` [bitcoin-dev] hashcash-newhash Karl
2020-05-24 1:12 ` ZmnSCPxj
2020-05-24 9:02 ` Karl
2020-05-24 16:51 ` ZmnSCPxj
2020-05-24 19:50 ` Karl
2020-05-25 7:58 ` ZmnSCPxj
2020-05-25 11:54 ` Karl
2020-05-27 4:47 ` ZmnSCPxj
2020-05-27 14:12 ` Erik Aronesty [this message]
2020-05-24 23:51 ` Ariel Lorenzo-Luaces
2020-05-25 7:03 ` Karl
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=CAJowKgJf2vBQc6Xh8sZeuxpvh5OK8FnSbVXr3K4do8VE_XXYiA@mail.gmail.com \
--to=erik@q32.com \
--cc=ZmnSCPxj@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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