From: John Tromp <john.tromp@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Scaling and anonymizing Bitcoin at layer 1 with client-side validation
Date: Sat, 3 Jun 2023 15:30:53 +0200 [thread overview]
Message-ID: <CAOU__fykfQiymVJ4oRwOZQPZu8CsYJhSHPJZZxoLDwRa25zu0Q@mail.gmail.com> (raw)
In-Reply-To: <mailman.110973.1685749706.956.bitcoin-dev@lists.linuxfoundation.org>
> The white paper describing the proposal can be found here:
> https://github.com/LNP-BP/layer1/
Some questions about the Bitcoin PoW anchoring:
What if a miner spends the current miner single-use-seal while
creating a commitment, but makes the PMT only partially available, or
entirely unavailable ?
How do other miners reach consensus on whether a protocol reset is
required? It seems impossible to agree on something like PMT
availability (much like mempool contents).
next parent reply other threads:[~2023-06-03 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.110973.1685749706.956.bitcoin-dev@lists.linuxfoundation.org>
2023-06-03 13:30 ` John Tromp [this message]
2023-06-03 17:17 ` Dr Maxim Orlovsky
2023-06-01 17:21 Dr Maxim Orlovsky
2023-06-05 18:09 ` Peter Todd
2023-06-14 20:14 ` Dr Maxim Orlovsky
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=CAOU__fykfQiymVJ4oRwOZQPZu8CsYJhSHPJZZxoLDwRa25zu0Q@mail.gmail.com \
--to=john.tromp@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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