From: Dave Collins <davec@conformal.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Regtest Consensus Forking Behavior Introduced in Bitcoin Core in May 2014
Date: Tue, 19 May 2015 11:05:18 -0500 [thread overview]
Message-ID: <555B5F3E.1070605@conformal.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
Hello All,
Josh Rickmar and I discovered a subtle consensus change in Bitcoin Core
which causes forking behavior on regtest. Luckily it does not affect
mainnet or testnet, however it does mean that regtest difficulty
retargetting is broken.
I've made a post to the bitcointalk forums at
https://bitcointalk.org/index.php?topic=1065504 for the nicer formatting
which explains in detail.
Regards,
Dave Collins
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 834 bytes --]
reply other threads:[~2015-05-19 16:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=555B5F3E.1070605@conformal.com \
--to=davec@conformal.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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