📅 Original date posted:2015-05-27
📝 Original message:On Wednesday, May 27, 2015 1:48:05 AM Pieter Wuille wrote:
> Feel free to comment. As the gist does not support notifying participants
> of new comments, I would suggest using the mailing list instead.
I suggest adding a section describing how this interacts with and changes GBT.
Currently, the client tells the server what the highest block version it
supports is, and the server indicates a block version to use in its template,
as well as optional instructions for the client to forcefully use this version
despite its own maximum version number. Making the version a bitfield
contradicts the increment-only assumption of this design, and since GBT
clients are not aware of overall network consensus state, reused bits can
easily become confused. I suggest, therefore, that GBT clients should indicate
(instead of a maximum supported version number) a list of softforks by
identifier keyword, and the GBT server respond with a template indicating:
- An object of softfork keywords to bit values, that the server will accept.
- The version number, as presently conveyed, indicating the preferred softfork
flags.
Does this sound reasonable, and/or am I missing anything else?
Luke
Luke Dashjr [ARCHIVE] /
npub1tf…rfq0n
2023-06-07 15:35:44
in reply to nevent1q…j46d
Author Public Key
npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nPublished at
2023-06-07 15:35:44Event JSON
{
"id": "ab1a54e9831da7b6528c4782e8563ed4155e023d8e376a1ccc89cd6fc3ae140c",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686152144,
"kind": 1,
"tags": [
[
"e",
"adec857a98b4d2ee3d4c91141aca2e0f0c8988c01182c3217cb69443b39af30e",
"",
"root"
],
[
"e",
"e827caad94843a8abcde8ce6db810e60170e52784a93f819880e7289d47add65",
"",
"reply"
],
[
"p",
"533e45ffeb94bc88c14af70b25994838170e7910c1273994b63bce468eac2230"
]
],
"content": "📅 Original date posted:2015-05-27\n📝 Original message:On Wednesday, May 27, 2015 1:48:05 AM Pieter Wuille wrote:\n\u003e Feel free to comment. As the gist does not support notifying participants\n\u003e of new comments, I would suggest using the mailing list instead.\n\nI suggest adding a section describing how this interacts with and changes GBT.\n\nCurrently, the client tells the server what the highest block version it \nsupports is, and the server indicates a block version to use in its template, \nas well as optional instructions for the client to forcefully use this version \ndespite its own maximum version number. Making the version a bitfield \ncontradicts the increment-only assumption of this design, and since GBT \nclients are not aware of overall network consensus state, reused bits can \neasily become confused. I suggest, therefore, that GBT clients should indicate \n(instead of a maximum supported version number) a list of softforks by \nidentifier keyword, and the GBT server respond with a template indicating:\n- An object of softfork keywords to bit values, that the server will accept.\n- The version number, as presently conveyed, indicating the preferred softfork \nflags.\n\nDoes this sound reasonable, and/or am I missing anything else?\n\nLuke",
"sig": "4d35f5624b35c12ab5246c2be3366983cc24ac43dfade48813224fade6a025a3ff9732bbfc7866ea87971c2c9e48aa55581addaa59adbfea05c305b1dc653e81"
}