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
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
|
Return-Path: <jlrubin@mit.edu>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138])
by lists.linuxfoundation.org (Postfix) with ESMTP id 77361C0012
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 17 Dec 2021 18:54:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id 655B284CB6
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 17 Dec 2021 18:54:10 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3,
RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp1.osuosl.org ([127.0.0.1])
by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id Dgvk38Oei65V
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 17 Dec 2021 18:54:09 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])
by smtp1.osuosl.org (Postfix) with ESMTPS id 6252184CB0
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 17 Dec 2021 18:54:09 +0000 (UTC)
Received: from mail-lf1-f47.google.com (mail-lf1-f47.google.com
[209.85.167.47]) (authenticated bits=0)
(User authenticated as jlrubin@ATHENA.MIT.EDU)
by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 1BHIs6og018222
(version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT)
for <bitcoin-dev@lists.linuxfoundation.org>; Fri, 17 Dec 2021 13:54:07 -0500
Received: by mail-lf1-f47.google.com with SMTP id g11so6584449lfu.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 17 Dec 2021 10:54:07 -0800 (PST)
X-Gm-Message-State: AOAM531O8UZ4vpBVnCfWCno3lZIng90i6Mh9vWctvBqvf27ZSvyK31ax
Y7YGSdkSgRa+tMh++o1j1/istKSJLH7j9okTYxI=
X-Google-Smtp-Source: ABdhPJz27Wn9oQK2aJ8b7Sa0sqOLgrMQjhJTHibAhWJ6PpfUQXp3OS75eq+vkTZ5fS7ky6PkP2rz/+gdDmhIJ2YvIn4=
X-Received: by 2002:ac2:4353:: with SMTP id o19mr3763814lfl.670.1639767246286;
Fri, 17 Dec 2021 10:54:06 -0800 (PST)
MIME-Version: 1.0
From: Jeremy <jlrubin@mit.edu>
Date: Fri, 17 Dec 2021 10:53:55 -0800
X-Gmail-Original-Message-ID: <CAD5xwhjqKC3qUFyOA6Jf=tgQz5KFr97CVVVzemDsX=jLoq2GSg@mail.gmail.com>
Message-ID: <CAD5xwhjqKC3qUFyOA6Jf=tgQz5KFr97CVVVzemDsX=jLoq2GSg@mail.gmail.com>
To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000003ab57305d35c10df"
Subject: [bitcoin-dev] Globally Broadcasting Workshares to Improve Finality
Heuristics
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: Fri, 17 Dec 2021 18:54:10 -0000
--0000000000003ab57305d35c10df
Content-Type: text/plain; charset="UTF-8"
An interesting concept occurred to me today while chatting with Nic Carter.
If we set Bitcoin Core up to gossip headers for work shares (e.g., expected
500 headers per block would have 20kb overhead, assuming we don't need to
send the prev hash) we'd be able to have more accurate finality estimates
and warnings if we see hashrate abandoning our chain tip. This is
observable regardless of if dishonest miners choose not to publish their
work on non tip shares, since you can notice the missing work.
In the GUI, we could give users an additional warning if they are
accepting a payment during a sudden hashrate decrease that they might wait
longer.
Has this been discussed before?
Cheers,
Jeremy
--
@JeremyRubin <https://twitter.com/JeremyRubin>
<https://twitter.com/JeremyRubin>
--0000000000003ab57305d35c10df
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small;color:#000000">An interesting concept oc=
curred to me today while chatting with Nic Carter.</div><div class=3D"gmail=
_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;c=
olor:#000000"><br></div><div class=3D"gmail_default" style=3D"font-family:a=
rial,helvetica,sans-serif;font-size:small;color:#000000">If we set Bitcoin =
Core up to gossip headers for work shares (e.g., expected 500 headers per b=
lock would have 20kb overhead, assuming we don't need to send the prev =
hash) we'd be able to have more accurate finality estimates and warning=
s if we see hashrate abandoning our chain tip. This is observable regardles=
s of if dishonest miners choose not to publish their work on non tip shares=
, since you can notice the missing work.</div><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#0000=
00"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,helve=
tica,sans-serif;font-size:small;color:#000000">In the GUI, we could give us=
ers an additional warning if they are accepting=C2=A0a payment during a sud=
den hashrate decrease that they might wait longer.</div><div class=3D"gmail=
_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;c=
olor:#000000"><br></div><div class=3D"gmail_default" style=3D"font-family:a=
rial,helvetica,sans-serif;font-size:small;color:#000000">Has this been disc=
ussed before?</div><div class=3D"gmail_default" style=3D"font-family:arial,=
helvetica,sans-serif;font-size:small;color:#000000"><br></div><div class=3D=
"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:s=
mall;color:#000000">Cheers,</div><div class=3D"gmail_default" style=3D"font=
-family:arial,helvetica,sans-serif;font-size:small;color:#000000"><br></div=
><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-ser=
if;font-size:small;color:#000000">Jeremy</div><br clear=3D"all"><div><div d=
ir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><di=
v dir=3D"ltr">--<br><a href=3D"https://twitter.com/JeremyRubin" target=3D"_=
blank">@JeremyRubin</a><a href=3D"https://twitter.com/JeremyRubin" target=
=3D"_blank"></a></div></div></div></div>
--0000000000003ab57305d35c10df--
|
