From: Zawy <wordsgalore@gmail.com>
To: Dave Scotese <dscotese@litmocracy.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] How much is too much time between difficulty changes?
Date: Wed, 5 Dec 2018 09:08:56 -0500 [thread overview]
Message-ID: <CADtTMv=y66ERvmJzcgu0P1xt_dBkwd_qqEc=g=GfJgwhsdEPZw@mail.gmail.com> (raw)
In-Reply-To: <CAGLBAhdtXEjhZWavgytQAOuXUaJZc=ZQyvjB2KV-YczAh-H4WQ@mail.gmail.com>
It's possible to let the difficulty linearly drop as the solvetime
goes beyond some limit (credit AS). If the limit is greater than any
delay in the past it could be backwards-compatible.
A simple daily-rolling average DA like BCH is probably the best option
if a faster DA is ever needed.
As a point of research interest (not likely to be needed by BTC), I've
taken the first above idea of "intra-block" timestamp-based difficulty
adjustment to the limit and made it symmetrical (higher D for fast
solves) and continuous. The result is a "tightening of the Poisson"
that increases "availability" (predictable solution times) at an
expense in "consistency" (orphans). It requires a very tight future
time limit to reduce timestamp manipulation. My objective was to help
small coins deal with persistent 20x hash rate changes that result in
long delays. About 3 coins have it on testnet.
https://github.com/zawy12/difficulty-algorithms/issues/36
prev parent reply other threads:[~2018-12-05 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 20:37 [bitcoin-dev] How much is too much time between difficulty changes? Dave Scotese
2018-12-05 14:08 ` Zawy [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='CADtTMv=y66ERvmJzcgu0P1xt_dBkwd_qqEc=g=GfJgwhsdEPZw@mail.gmail.com' \
--to=wordsgalore@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=dscotese@litmocracy.com \
/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