From: Braydon Fuller <braydon@purse•io>
To: "Joachim Strömbergson" <joachimstr@protonmail•com>,
"Bitcoin Protocol Discussion"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Chain width expansion
Date: Tue, 15 Oct 2019 01:12:09 -0700 [thread overview]
Message-ID: <7b0d0bff-d898-10ff-5fdb-c982b82054a1@purse.io> (raw)
In-Reply-To: <yKuDn4LKCA9-olIsgnJO7VqN3RE9BgZWEzLu6-k4wG30iHYDIJa6wjTBoYXU0zWCRyNCEvBb4xQw7qp0BDGBCR4zccI6kJ_4AnlsB9vc9L4=@protonmail.com>
On 10/15/19 12:20 AM, Joachim Strömbergson wrote:
>>> [...] to generate much longer chain with superslow timestamp increase (~5 blocks in 1 second) without increasing difficulty (i.e. staying at min. diff.). [...]
>> In that case, it would take about 7 minutes of block time seconds for
>> the next retarget period, every 2016 blocks, and the difficulty would
>> adjust. The difficulty would adjust in that case as if 2 weeks of blocks
>> had been mined in 7 minutes. For the difficulty to remain the same the
>> time between blocks needs to be 10 minutes.
> This calculation does not apply under time warp attack. You can fake timestamps of all blocks except for those relevant to the retarget calculation. Those are only the first and the last block in the 2016 block window.
This must be in reference to the non-overlapping difficulty calculation
and off-by-one bug?
next prev parent reply other threads:[~2019-10-15 8:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 0:38 Braydon Fuller
2019-10-04 8:20 ` David A. Harding
2019-10-04 19:51 ` Braydon Fuller
2019-10-11 21:24 ` Braydon Fuller
2019-10-04 23:31 ` Tier Nolan
2019-10-10 16:16 ` Braydon Fuller
2019-10-12 16:27 ` Tier Nolan
2019-10-12 17:56 ` Joachim Strömbergson
2019-10-12 20:46 ` Tier Nolan
2019-10-16 19:07 ` Braydon Fuller
2019-10-15 0:42 ` Braydon Fuller
2019-10-15 7:20 ` Joachim Strömbergson
2019-10-15 8:12 ` Braydon Fuller [this message]
2019-10-15 15:50 ` Joachim Strömbergson
2019-10-16 19:25 ` Braydon Fuller
2019-10-15 18:30 ` Tier Nolan
2019-10-15 0:38 ` Braydon Fuller
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=7b0d0bff-d898-10ff-5fdb-c982b82054a1@purse.io \
--to=braydon@purse$(echo .)io \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=joachimstr@protonmail$(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