public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
* [bitcoin-dev] Globally Broadcasting Workshares to Improve Finality Heuristics
@ 2021-12-17 18:53 Jeremy
  2021-12-18  8:36 ` Newsletter Catcher
  0 siblings, 1 reply; 3+ messages in thread
From: Jeremy @ 2021-12-17 18:53 UTC (permalink / raw)
  To: Bitcoin development mailing list

[-- Attachment #1: Type: text/plain, Size: 788 bytes --]

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>

[-- Attachment #2: Type: text/html, Size: 2222 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [bitcoin-dev] Globally Broadcasting Workshares to Improve Finality Heuristics
  2021-12-17 18:53 [bitcoin-dev] Globally Broadcasting Workshares to Improve Finality Heuristics Jeremy
@ 2021-12-18  8:36 ` Newsletter Catcher
  0 siblings, 0 replies; 3+ messages in thread
From: Newsletter Catcher @ 2021-12-18  8:36 UTC (permalink / raw)
  To: Jeremy, Bitcoin Protocol Discussion

[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [bitcoin-dev] Globally Broadcasting Workshares to Improve Finality Heuristics
@ 2021-12-18 13:25 Rune K. Svendsen
  0 siblings, 0 replies; 3+ messages in thread
From: Rune K. Svendsen @ 2021-12-18 13:25 UTC (permalink / raw)
  To: bitcoin-dev

Hi Jeremy,

If I understand you correctly, then I believe I touch upon this concept here: https://bitcointalk.org/index.php?topic=97153.msg1309930#msg1309930


/Rune



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-12-18 13:25 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-12-17 18:53 [bitcoin-dev] Globally Broadcasting Workshares to Improve Finality Heuristics Jeremy
2021-12-18  8:36 ` Newsletter Catcher
2021-12-18 13:25 Rune K. Svendsen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox