From: Gregory Maxwell <gmaxwell@gmail•com>
To: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Testnet3 difficulty transition problem?
Date: Sat, 22 Dec 2012 13:45:52 -0500 [thread overview]
Message-ID: <CAAS2fgTM6n17x+3Oen78LHeAVuyOaXLCy285NKqqCLN74VB_=Q@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgQKidxKmJ47oDi80YZrTW_MrVYf_u_tcZtO+xv2o+8S+w@mail.gmail.com>
On Sat, Dec 22, 2012 at 1:39 PM, Andreas Schildbach
<andreas@schildbach•de> wrote:
> Both blocks
>
> 38304 00000000015bb4069249fa1f41ae61d8a7447aaacc33c50dacd3c3654377fa43
>
> and
>
> 40320 000000008011f56b8c92ff27fb502df5723171c5374673670ef0eee3696aee6d
>
> are difficulty transition blocks. However, block 40320 has a difficulty
> of 1. I know there is this special testnet rule that allows mining a
> block at difficulty 1,
Yes.
> but I always thought you can't use this exception
> on difficulty transition blocks.
Not so— but what you're actually seeing is that difficult change is
relative to the prior block's difficulty. E.g. if the penultimate
block in the difficulty cycle is under the special rule the difficulty
change will be relative to 1.
(I had intentionally avoided triggering that test case when adding the
timewarp attack to the testnet chain in case we had wanted to fix it
prior to testnet3's release— I guess I should have added it sooner in
order to catch the bitcoinj misbehavior!)
next prev parent reply other threads:[~2012-12-22 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 18:39 Andreas Schildbach
[not found] ` <CAAS2fgQKidxKmJ47oDi80YZrTW_MrVYf_u_tcZtO+xv2o+8S+w@mail.gmail.com>
2012-12-22 18:45 ` Gregory Maxwell [this message]
2012-12-24 16:21 ` Mike Hearn
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='CAAS2fgTM6n17x+3Oen78LHeAVuyOaXLCy285NKqqCLN74VB_=Q@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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