From: Dr Maxim Orlovsky <orlovsky@lnp-bp•org>
To: john.tromp@gmail•com, bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Scaling and anonymizing Bitcoin at layer 1 with client-side validation
Date: Sat, 03 Jun 2023 17:17:48 +0000 [thread overview]
Message-ID: <BZFrQ76cM2ULPqNTIuhMmyKw8RIGJPRdpkVaC_0VyWrceamVOutVF16m0fFchnl9SmJL_FLuPnYdNlOGh-SOUBoqdsh8MNwAoaVa2W8RGdg=@lnp-bp.org> (raw)
In-Reply-To: <CAOU__fykfQiymVJ4oRwOZQPZu8CsYJhSHPJZZxoLDwRa25zu0Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
Hi John,
Thank you for the question. We have discussed this case in the paper, second paragraph of the “Bitcoin PoW Anchoring” Section:
> If a party spends current miner single-use-seal without creating a commitment - or committing to a header without sufficient PoW, such closing is considered invalid; in this case, any party is allowed to create a special bitcoin transaction providing publically-identifiableOP_RETURNinformation ("announcement") about a new miner single-use-seal (protocol reset); only the firstOP_RETURNannouncement which is closed with a proper procedure is considered valid under the consensus rules.
Kind regards,
Maxim Orlovsky
On Sat, Jun 3, 2023 at 4:30 PM, John Tromp via bitcoin-dev <[bitcoin-dev@lists•linuxfoundation.org](mailto:On Sat, Jun 3, 2023 at 4:30 PM, John Tromp via bitcoin-dev <<a href=)> wrote:
>> 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).
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[-- Attachment #2: Type: text/html, Size: 3108 bytes --]
next prev parent reply other threads:[~2023-06-03 17:18 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
2023-06-03 17:17 ` Dr Maxim Orlovsky [this message]
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='BZFrQ76cM2ULPqNTIuhMmyKw8RIGJPRdpkVaC_0VyWrceamVOutVF16m0fFchnl9SmJL_FLuPnYdNlOGh-SOUBoqdsh8MNwAoaVa2W8RGdg=@lnp-bp.org' \
--to=orlovsky@lnp-bp$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=john.tromp@gmail$(echo .)com \
/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