From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id E3CABC07FF for ; Sat, 21 Mar 2020 18:40:37 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by fraxinus.osuosl.org (Postfix) with ESMTP id D363B8623B for ; Sat, 21 Mar 2020 18:40:37 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from fraxinus.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fx95hqmnrLit for ; Sat, 21 Mar 2020 18:40:37 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ed1-f48.google.com (mail-ed1-f48.google.com [209.85.208.48]) by fraxinus.osuosl.org (Postfix) with ESMTPS id C580385FD0 for ; Sat, 21 Mar 2020 18:40:36 +0000 (UTC) Received: by mail-ed1-f48.google.com with SMTP id v6so11236338edw.8 for ; Sat, 21 Mar 2020 11:40:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=cm2ulmgVVVGD/zSPk1ekOP/p2q9n1jPydwgEutKelsA=; b=JgiWSWxNwE1sCyVhDhghnYFngZPxTis5EtiqLOEyk7RVPvrmnFrn+Xjnuc5vzbHCvu F/2pnqIzPdt4ZjuUqI8yP8jy7nyIx/uT9CzrOsAPHWNKJpBMDWXbv7j8QvXdRQqRGY8S EuzlJOH8+Ml/ZS74kLNdFFJMUil0/+cMK5q3DUmASE1PBPzF//N5pSNINM1VBSwJHova PhUGRIyeIYYwNVySGPFWq0fd+UpKPDJZpMkgxMBYyLSokp8wd3zSnKQWlQ3pKCbvKs8E YHd6vY9yeptIlbUNjiERXx0y8NxWd1nlVX/k3+xaY4q92uTkdtTXUWDsgQmGhN6vxf/2 j3dg== X-Gm-Message-State: ANhLgQ2iZrqBqxymyeingDQSGCJ5pjXrc+5ecF8Z7lkWbGNNJPRsQIDF J/Qg78eKZRd042ODrNR9OoKnOuea9m4UNkckMk5aQvB2 X-Google-Smtp-Source: ADFU+vsuOvWSjD2WMmWatl1tPN4nrA1xk8wBYGO/aGtWMX0sU7RJE4OX1IU+PG2BXtBlvxAt8QIadCavg+L4VpnBZxg= X-Received: by 2002:a50:8d1a:: with SMTP id s26mr14428011eds.152.1584816034965; Sat, 21 Mar 2020 11:40:34 -0700 (PDT) MIME-Version: 1.0 From: Dave Scotese Date: Sat, 21 Mar 2020 11:40:24 -0700 Message-ID: To: Bitcoin Dev Content-Type: multipart/alternative; boundary="000000000000cc6fae05a161bc91" Subject: [bitcoin-dev] Block solving slowdown question/poll X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Mar 2020 18:40:38 -0000 --000000000000cc6fae05a161bc91 Content-Type: text/plain; charset="UTF-8" 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. --000000000000cc6fae05a161bc91 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
It seems that many on this list think deeply enough to ima= gine the scenario where we have=C2=A0 few days left before a difficulty adj= ustment comes up but we also see mining power dropping off at a rate that s= uggests the few days might become a few weeks, and then, possibly, a few mo= nths or even the unthinkable, a few eons.=C2=A0 I'm curious to know if = anyone has ideas on how this might be handled because I'm sure we'r= e not going to let it happen.
--000000000000cc6fae05a161bc91--