From: Newsletter Catcher <newsletters@briancloutier•com>
To: Jeremy <jlrubin@mit•edu>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Globally Broadcasting Workshares to Improve Finality Heuristics
Date: Sat, 18 Dec 2021 00:36:07 -0800 [thread overview]
Message-ID: <CAGBDHp0WkX4S6Ctgq=7YD75s_PSy==wchEtKPR3YYw0ZVxOtiA@mail.gmail.com> (raw)
In-Reply-To: <CAD5xwhjqKC3qUFyOA6Jf=tgQz5KFr97CVVVzemDsX=jLoq2GSg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 3271 bytes --]
next prev parent reply other threads:[~2021-12-18 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 18:53 Jeremy
2021-12-18 8:36 ` Newsletter Catcher [this message]
2021-12-18 13:25 Rune K. Svendsen
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='CAGBDHp0WkX4S6Ctgq=7YD75s_PSy==wchEtKPR3YYw0ZVxOtiA@mail.gmail.com' \
--to=newsletters@briancloutier$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jlrubin@mit$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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