📅 Original date posted:2021-04-04
📝 Original message:So the only thing that seemed clear, using height as per bip8, it's not
clear anymore.
And, as usual, we're not talking about activation in general but about
taproot activation, segwit activation...
I won't make it to the meeting because I don't think I have much more to
contribute that I haven't said already beyond perhaps: sigh.
My arguments will probably ignored again, so it doesn't matter.
On Sun, Apr 4, 2021, 06:39 Jeremy via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> We'll be having another meeting this Tuesday, as per
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-March/018699.html.
> If you can't make it feel free to leave a comment on any agenda item below,
> or if you think there are other things to be discussed.
>
> Agenda:
>
> 1. AJ's update to MTP time.
>
> Please review https://github.com/bitcoin/bitcoin/pull/21377 as AJ updated
> it substantially.
>
> The PR is now purely MTP based, and the state machine has been simplified.
> This approach is intended to be compatible with a mandatory signaling
> period (via a LAST_CHANCE change) and makes it easier to deploy ST on
> signets (irrelevant for Taproot, because it is already active on all
> signets).
>
> 2. Selecting between MTP and Height
>
> In the previous meeting, there was no substantial publicly discussed
> benefit to using MTPs over height. Since agenda item 1, there is now a
> tangible benefit to using MTP.
>
> The changes AJ promulgated for MTP neutralizes the argument, mostly, that
> MTP was easier to review. As such, the main conversation in this agenda
> item is around the pros/cons of height or MTP and determining if we can
> reach consensus on either approach.
>
> 3. Timeline Discussion
> In all hope, we will reach consensus around item 2. Should that occur, we
> can use this time to discuss a final selection on parameters, mindful of
> Core's process.
>
> If the meeting doesn't reach rough consensus around item 2, it seems that
> we may fall short on the proposed schedule from last time. In this section,
> we can discuss realities around scheduling.
>
>
> Best,
>
> Jeremy
>
>
>
> --
> @JeremyRubin <https://twitter.com/JeremyRubin>;
> <https://twitter.com/JeremyRubin>;
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210404/c59b83e4/attachment.html>;
Jorge Timón [ARCHIVE] /
npub1fx…cl2d8
2023-06-07 22:51:08
in reply to nevent1q…pq4a
Author Public Key
npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8Published at
2023-06-07 22:51:08Event JSON
{
"id": "d65519f8ddecfe0615eba142736689b41986657d5c4335025a9b0a4f550bc97c",
"pubkey": "498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84",
"created_at": 1686178268,
"kind": 1,
"tags": [
[
"e",
"4a8fcc2e5a5f072bf4f8d2fa9f35b98817e71c0fecb9f6b8569b3021d902f19c",
"",
"root"
],
[
"e",
"817e2b2c86549c4190a85094c0c03a0dedcc488c0a1b2c1d897dbad0f4184663",
"",
"reply"
],
[
"p",
"01f53a3166b3b23139201763777e070fcfed5555ad7555f7e90114c0c9e0e8b4"
]
],
"content": "📅 Original date posted:2021-04-04\n📝 Original message:So the only thing that seemed clear, using height as per bip8, it's not\nclear anymore.\nAnd, as usual, we're not talking about activation in general but about\ntaproot activation, segwit activation...\n\nI won't make it to the meeting because I don't think I have much more to\ncontribute that I haven't said already beyond perhaps: sigh.\nMy arguments will probably ignored again, so it doesn't matter.\n\n\nOn Sun, Apr 4, 2021, 06:39 Jeremy via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e We'll be having another meeting this Tuesday, as per\n\u003e https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-March/018699.html.\n\u003e If you can't make it feel free to leave a comment on any agenda item below,\n\u003e or if you think there are other things to be discussed.\n\u003e\n\u003e Agenda:\n\u003e\n\u003e 1. AJ's update to MTP time.\n\u003e\n\u003e Please review https://github.com/bitcoin/bitcoin/pull/21377 as AJ updated\n\u003e it substantially.\n\u003e\n\u003e The PR is now purely MTP based, and the state machine has been simplified.\n\u003e This approach is intended to be compatible with a mandatory signaling\n\u003e period (via a LAST_CHANCE change) and makes it easier to deploy ST on\n\u003e signets (irrelevant for Taproot, because it is already active on all\n\u003e signets).\n\u003e\n\u003e 2. Selecting between MTP and Height\n\u003e\n\u003e In the previous meeting, there was no substantial publicly discussed\n\u003e benefit to using MTPs over height. Since agenda item 1, there is now a\n\u003e tangible benefit to using MTP.\n\u003e\n\u003e The changes AJ promulgated for MTP neutralizes the argument, mostly, that\n\u003e MTP was easier to review. As such, the main conversation in this agenda\n\u003e item is around the pros/cons of height or MTP and determining if we can\n\u003e reach consensus on either approach.\n\u003e\n\u003e 3. Timeline Discussion\n\u003e In all hope, we will reach consensus around item 2. Should that occur, we\n\u003e can use this time to discuss a final selection on parameters, mindful of\n\u003e Core's process.\n\u003e\n\u003e If the meeting doesn't reach rough consensus around item 2, it seems that\n\u003e we may fall short on the proposed schedule from last time. In this section,\n\u003e we can discuss realities around scheduling.\n\u003e\n\u003e\n\u003e Best,\n\u003e\n\u003e Jeremy\n\u003e\n\u003e\n\u003e\n\u003e --\n\u003e @JeremyRubin \u003chttps://twitter.com/JeremyRubin\u003e\n\u003e \u003chttps://twitter.com/JeremyRubin\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210404/c59b83e4/attachment.html\u003e",
"sig": "e4562f33d58c52a59da29eacb75a30df467905036fc7d7b3a4d400f94e71a84793bba2591be96f912d5fba6f60f4db35a42b82d48cfd7c896d74012d74ee1ff3"
}