From: Gregory Maxwell <greg@xiph•org>
To: James Hilliard <james.hilliard1@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Blockchain verification flag (BIP draft)
Date: Sun, 6 Dec 2015 06:26:15 +0000 [thread overview]
Message-ID: <CAAS2fgQQ+ZTUXXXRJWP-RjP+ehsUTrxa7Vy-QrZ-3Q6Offz=5A@mail.gmail.com> (raw)
In-Reply-To: <CADvTj4q_Ubrk6a15Q4uB3MT0PHGnvZt3yPMOWCdPhWf_WGH-tA@mail.gmail.com>
On Sun, Dec 6, 2015 at 2:47 AM, James Hilliard via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> I think something that anyone who isn't validating should be aware of is
> that cgminer(which powers the vast majority of the current mining network)
> doesn't allow for a pool to revert to mining on the previous block due to
> the way chain tracking is implemented.
An interesting potential use for the flag suggested in this draft
would be allowing non-monotone mining for non-verified blocks.
I could add a recommendation for that as well.
next prev parent reply other threads:[~2015-12-06 6:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 8:26 Gregory Maxwell
2015-12-04 12:44 ` Jannes Faber
2015-12-04 16:46 ` Thomas Kerin
2015-12-04 17:34 ` Gavin Andresen
2015-12-04 22:43 ` Rusty Russell
2015-12-06 2:47 ` James Hilliard
2015-12-06 6:26 ` Gregory Maxwell [this message]
2015-12-06 5:13 ` Gregory Maxwell
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='CAAS2fgQQ+ZTUXXXRJWP-RjP+ehsUTrxa7Vy-QrZ-3Q6Offz=5A@mail.gmail.com' \
--to=greg@xiph$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=james.hilliard1@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