From: Scott Roberts <wordsgalore@gmail•com>
To: Gregory Maxwell <greg@xiph•org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Cash's new difficulty algorithm
Date: Thu, 2 Nov 2017 19:53:25 -0400 [thread overview]
Message-ID: <CADtTMvnOtaq-AsvBOMxPWAHJcSFU+qNXye5+Nu1hB4YP06r3ng@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgT9aM=koBv4PxJFSrHfTRU4TrGCPOE8Ej7T8oTLhGmubA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
Whatever their failings from their previous code or their adversarial
nature, they got this code right and I'm only presenting it as a real and
excellent solution for the impending threat to bitcoin. As a big core fan,
I really wanted to delete the word Cash from my post because I was afraid
someone would turn this technical discussion into a political football.
On Nov 2, 2017 7:37 PM, "Gregory Maxwell" <greg@xiph•org> wrote:
On Thu, Nov 2, 2017 at 11:31 PM, Scott Roberts via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> Bitcoin cash will hard fork on Nov 13 to implement a new difficulty
> algorithm. Bitcoin itself might need to hard fork to employ a similar
> algorithm. It's about as good as they come because it followed the
This is the bitcoin development mailing list, not the "give free
review to the obviously defective proposals of adversarial competing
systems" mailing list. Your posting is off-topic.
[-- Attachment #2: Type: text/html, Size: 1447 bytes --]
next prev parent reply other threads:[~2017-11-02 23:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 23:31 Scott Roberts
2017-11-02 23:37 ` Gregory Maxwell
2017-11-02 23:53 ` Scott Roberts [this message]
2017-11-03 0:00 ` Gregory Maxwell
2017-11-03 0:47 ` gb
2017-11-02 23:39 ` CryptAxe
2017-11-03 1:59 ` Scott Roberts
2017-11-04 3:37 ` Jacob Eliosoff
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=CADtTMvnOtaq-AsvBOMxPWAHJcSFU+qNXye5+Nu1hB4YP06r3ng@mail.gmail.com \
--to=wordsgalore@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=greg@xiph$(echo .)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