path: root/f8/c841f120f0ca49cbc5527ee3ce9821e617d550

Return-Path: <newsletters@briancloutier.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 34210C0012
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 18 Dec 2021 08:36:22 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp3.osuosl.org (Postfix) with ESMTP id 2F1A160EDE
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 18 Dec 2021 08:36:22 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp3.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key)
 header.d=briancloutier-com.20210112.gappssmtp.com
Received: from smtp3.osuosl.org ([127.0.0.1])
 by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id JtLyfJZribZH
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 18 Dec 2021 08:36:20 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-il1-x135.google.com (mail-il1-x135.google.com
 [IPv6:2607:f8b0:4864:20::135])
 by smtp3.osuosl.org (Postfix) with ESMTPS id EC96B60EDD
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 18 Dec 2021 08:36:19 +0000 (UTC)
Received: by mail-il1-x135.google.com with SMTP id m12so3530014ild.0
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 18 Dec 2021 00:36:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=briancloutier-com.20210112.gappssmtp.com; s=20210112;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
 bh=5v/cO+jZhVIgUlHQs8O3E1NxmVy6zkOHPoIeYfsHmlM=;
 b=vU1QAdgvDjRY+COEwjsobrXs41vQXwTv5VxIfLXuuoDfWLDgFb8SbOTHonG5cW4dqs
 W7g+HePV9WaPw6zTeBt7+wiTyyMDoz/+4R7m008sr5BD43l2fzxn8q8kXMRBvtaNUn1W
 fsnOMbrs5Je7uwySpEX7eC+GmNxJevdseKvemNtqoKdGZM0MJohBXGqQXkW9Jzrsid2d
 oIoa7KCw4C+x9hbHo2lth9v3gKnJS93g99c6xsm8IXU0B3+aNIslXCZn6gJloKOdXVCZ
 wg8CQ1p7o1CDhccVJGS+Yo5mW1xAAyVPE+T9UXZG0IvVCZShCievE7ZIQwJxPqYQe8wp
 g6sg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to;
 bh=5v/cO+jZhVIgUlHQs8O3E1NxmVy6zkOHPoIeYfsHmlM=;
 b=xMxbPWd4dlEH+tV0Anf4zDvxII7H3N1QmlFpl9CH2Ix549epNOkvc7/J8MgoyyLmKm
 duYiHZbJn4pEzX6ZAwRJletg57NKg5Bw9n1UNlSB0RrvTs1jml/i0SOkqks9jMl73GR/
 tbJGH5nrsNXMqXITpVKGiI864lpjAwdrKmV1JbKi4fNdvrHDtYzcyS0k/t9Xu8do9OmH
 ioSHHSlQpt8WjzWaovXsGfWOlG0iyILrLkFHb4eNgmyyv9qshlEoiRs1wLdCRN7lc2K4
 o3u0eKEzAYLFA/yY7HAwqJ/asETtJYxnmhI9RECwAQZQDo9ZBcL/GDfRIXVHBg+bwWFT
 n/Hw==
X-Gm-Message-State: AOAM533bPxduSfyOdYl8nmc0al7/hd62iZeQF2EFYfn/DOjRZbvsGZtO
 joZPaHh4iPD61nTZcgk8DEXmPuD51Y7efo7q7hK9ssGv82h/AQ==
X-Google-Smtp-Source: ABdhPJw/Psv7nOmbm9FLQ+ytp/8tdFyh1dJkwY7biNMvX0RtBwBkIgY6hjsCacMbcoSSG3Q6LuWX3dKGRrMQZ8+wOkA=
X-Received: by 2002:a05:6e02:1b8a:: with SMTP id
 h10mr3488548ili.14.1639816578928; 
 Sat, 18 Dec 2021 00:36:18 -0800 (PST)
MIME-Version: 1.0
References: <CAD5xwhjqKC3qUFyOA6Jf=tgQz5KFr97CVVVzemDsX=jLoq2GSg@mail.gmail.com>
In-Reply-To: <CAD5xwhjqKC3qUFyOA6Jf=tgQz5KFr97CVVVzemDsX=jLoq2GSg@mail.gmail.com>
From: Newsletter Catcher <newsletters@briancloutier.com>
Date: Sat, 18 Dec 2021 00:36:07 -0800
Message-ID: <CAGBDHp0WkX4S6Ctgq=7YD75s_PSy==wchEtKPR3YYw0ZVxOtiA@mail.gmail.com>
To: Jeremy <jlrubin@mit.edu>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000af236105d3678c24"
X-Mailman-Approved-At: Sat, 18 Dec 2021 09:56:47 +0000
Subject: Re: [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: Sat, 18 Dec 2021 08:36:22 -0000

--000000000000af236105d3678c24
Content-Type: text/plain; charset="UTF-8"

It's not exactly what you're looking for but this is very similar to the
premise of Bobtail, which was presented at Scaling Bitcoin a few years ago:
https://arxiv.org/abs/1709.08750

On Fri, Dec 17, 2021, 10:54 Jeremy via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> 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>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--000000000000af236105d3678c24
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>It&#39;s not exactly what you&#39;re looking for but=
 this is very similar to the premise of Bobtail, which was presented at Sca=
ling Bitcoin a few years ago:=C2=A0<a href=3D"https://arxiv.org/abs/1709.08=
750">https://arxiv.org/abs/1709.08750</a><br><br><div class=3D"gmail_quote"=
><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Dec 17, 2021, 10:54 Jeremy v=
ia bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org"=
>bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"f=
ont-family:arial,helvetica,sans-serif;font-size:small;color:#000000">An int=
eresting concept occurred to me today while chatting with Nic Carter.</div>=
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small;color:#000000"><br></div><div class=3D"gmail_default" sty=
le=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#000000"=
>If we set Bitcoin Core up to gossip headers for work shares (e.g., expecte=
d 500 headers per block would have 20kb overhead, assuming we don&#39;t nee=
d to send the prev hash) we&#39;d be able to have more accurate finality es=
timates and warnings if we see hashrate abandoning our chain tip. This is o=
bservable regardless of if dishonest miners choose not to publish their wor=
k 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-siz=
e:small;color:#000000"><br></div><div class=3D"gmail_default" style=3D"font=
-family:arial,helvetica,sans-serif;font-size:small;color:#000000">In the GU=
I, we could give users an additional warning if they are accepting=C2=A0a p=
ayment during a sudden hashrate decrease that they might wait longer.</div>=
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small;color:#000000"><br></div><div class=3D"gmail_default" sty=
le=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#000000"=
>Has this been discussed 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,san=
s-serif;font-size:small;color:#000000">Cheers,</div><div class=3D"gmail_def=
ault" 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:small;color:#000000">Jeremy</div><br clear=
=3D"all"><div><div dir=3D"ltr" data-smartmail=3D"gmail_signature"><div dir=
=3D"ltr">--<br><a href=3D"https://twitter.com/JeremyRubin" target=3D"_blank=
" rel=3D"noreferrer">@JeremyRubin</a><a href=3D"https://twitter.com/JeremyR=
ubin" target=3D"_blank" rel=3D"noreferrer"></a></div></div></div></div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank" =
rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer noreferrer" target=3D"_blank">https://lists.linuxfoundati=
on.org/mailman/listinfo/bitcoin-dev</a><br>
</blockquote></div></div></div>

--000000000000af236105d3678c24--