public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Dave Scotese <dscotese@litmocracy.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Block solving slowdown question/poll
Date: Sat, 21 Mar 2020 11:40:24 -0700	[thread overview]
Message-ID: <CAGLBAhcS5oxGvrcG7QdO7Ya6X2n1=H_nzx5Eh=69rcje6SQpgA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 441 bytes --]

It seems that many on this list think deeply enough to imagine the scenario
where we have  few days left before a difficulty adjustment comes up but we
also see mining power dropping off at a rate that suggests the few days
might become a few weeks, and then, possibly, a few months or even the
unthinkable, a few eons.  I'm curious to know if anyone has ideas on how
this might be handled because I'm sure we're not going to let it happen.

[-- Attachment #2: Type: text/html, Size: 477 bytes --]

             reply	other threads:[~2020-03-21 18:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21 18:40 Dave Scotese [this message]
2020-03-22  7:54 ` [bitcoin-dev] Block solving slowdown question/poll David A. Harding
2020-03-22 11:58   ` LORD HIS EXCELLENCY JAMES HRMH
2020-03-22 16:54     ` Eric Voskuil
2020-03-22 18:17       ` Dave Scotese
2020-03-23 12:59         ` Andrew Cann
2020-03-23 18:39           ` Dave Scotese
2020-03-24  7:42             ` ZmnSCPxj
2020-03-25 15:23               ` Andrew Cann
2020-03-26  1:42                 ` ZmnSCPxj
2020-03-27  9:17                   ` Andrew Cann
2020-03-28  2:12                     ` ZmnSCPxj
2020-03-29  8:11                       ` [bitcoin-dev] Block solving slowdown Andrew Cann
2020-03-30  2:59                         ` ZmnSCPxj
2020-03-31  2:06                           ` ZmnSCPxj

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='CAGLBAhcS5oxGvrcG7QdO7Ya6X2n1=H_nzx5Eh=69rcje6SQpgA@mail.gmail.com' \
    --to=dscotese@litmocracy.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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