From: Matt Corallo <lf-lists@mattcorallo.com>
To: "Casciano, Anthony" <ac89@buffalo.edu>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>,
"Casciano,
Anthony via bitcoin-dev" <bitcoin-dev@lists.linuxfoundation.org>,
"bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BetterHash status
Date: Tue, 26 Jun 2018 14:44:02 +0000 [thread overview]
Message-ID: <8D5A789A-5807-4C5A-BD95-6BBB9169601C@mattcorallo.com> (raw)
In-Reply-To: <1530023526835.10657@buffalo.edu>
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
Things go into production when people decide to adopt them, not before. You're welcome to contribute to the implementation at https://github.com/TheBlueMatt/mining-proxy
On June 26, 2018 2:32:06 PM UTC, "Casciano, Anthony via bitcoin-dev" <bitcoin-dev@lists.linuxfoundation.org> wrote:
>What is the status of Matt Corallo's "BetterHash" BIP?? I recommend
>it
>
>goes into production sooner than later. Any 2nd's ?
>
>
>Thanks in advance!
>
>Tony Cash
[-- Attachment #2: Type: text/html, Size: 1933 bytes --]
prev parent reply other threads:[~2018-06-26 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 14:32 [bitcoin-dev] BetterHash status Casciano, Anthony
2018-06-26 14:44 ` Matt Corallo [this message]
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=8D5A789A-5807-4C5A-BD95-6BBB9169601C@mattcorallo.com \
--to=lf-lists@mattcorallo.com \
--cc=ac89@buffalo.edu \
--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