1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
Return-Path: <dscotese@gmail.com>
Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137])
by lists.linuxfoundation.org (Postfix) with ESMTP id E3CABC07FF
for <bitcoin-dev@lists.linuxfoundation.org>;
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 <bitcoin-dev@lists.linuxfoundation.org>;
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 <bitcoin-dev@lists.linuxfoundation.org>;
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 <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 21 Mar 2020 18:40:36 +0000 (UTC)
Received: by mail-ed1-f48.google.com with SMTP id v6so11236338edw.8
for <bitcoin-dev@lists.linuxfoundation.org>;
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 <dscotese@litmocracy.com>
Date: Sat, 21 Mar 2020 11:40:24 -0700
Message-ID: <CAGLBAhcS5oxGvrcG7QdO7Ya6X2n1=H_nzx5Eh=69rcje6SQpgA@mail.gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=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
<div dir=3D"ltr">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.</div>
--000000000000cc6fae05a161bc91--
|
