📅 Original date posted:2017-07-12
📝 Original message:Hi!
Up to now, I have purposefully been running bitcoin releases prior to
0.13.1 as a way to avoid the (possible) segwit activation, at least
until such time as I personally am comfortable with it.
At this time, I would like to have some of the more recent features, but
without the possibility that my node will activate segwit, until I
choose to.
As I understand it, there is not any user setting that can disable
segwit from activating on my node. If there was, I would use it.
Please correct me if wrong.
I am here to ask what is the simplest code change (fewest LOC changed) I
can make to 0.14.2+ code that would disable segwit from activating and
keep my node acting just like a legacy node with regards to consensus
rules, even if/when the rest of the network activates segwit.
I think, more generally, the same question applies to most any Bip9
versionbits feature.
I'm not looking for reasons NOT to do it, only HOW to do it without
unwanted side-effects. My first untested idea is just to change the
segwit nTimeout in chainparams.cpp to a date in the past. But I figured
I should ask the experts first. :-)
thanks.
ps: full disclosure: I may be the only one who wants this, but if
successful, I do plan to release my changes in case someone else wishes
to run with status-quo consensus rules.
Dan Libby [ARCHIVE] /
npub1hm…jk43d
2023-06-07 18:04:25
in reply to nevent1q…92z3
Author Public Key
npub1hm38d5dwxdq5zxlnv2qdfk3flecptqwl7g7u62ja0tr92d0hmrusejk43dPublished at
2023-06-07 18:04:25Event JSON
{
"id": "292160cb9740967a5dfdd715d23b36eeee5b3d437a674ae7457bbd014f1398d2",
"pubkey": "bee276d1ae3341411bf36280d4da29fe701581dff23dcd2a5d7ac65535f7d8f9",
"created_at": 1686161065,
"kind": 1,
"tags": [
[
"e",
"c3417a9d5ad76947acf26c6783addd471ca3bcc5d3ed57deae65203b0eaf5238",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2017-07-12\n📝 Original message:Hi!\n\nUp to now, I have purposefully been running bitcoin releases prior to\n0.13.1 as a way to avoid the (possible) segwit activation, at least\nuntil such time as I personally am comfortable with it.\n\nAt this time, I would like to have some of the more recent features, but\nwithout the possibility that my node will activate segwit, until I\nchoose to.\n\nAs I understand it, there is not any user setting that can disable\nsegwit from activating on my node. If there was, I would use it.\nPlease correct me if wrong.\n\nI am here to ask what is the simplest code change (fewest LOC changed) I\ncan make to 0.14.2+ code that would disable segwit from activating and\nkeep my node acting just like a legacy node with regards to consensus\nrules, even if/when the rest of the network activates segwit.\n\nI think, more generally, the same question applies to most any Bip9\nversionbits feature.\n\nI'm not looking for reasons NOT to do it, only HOW to do it without\nunwanted side-effects. My first untested idea is just to change the\nsegwit nTimeout in chainparams.cpp to a date in the past. But I figured\nI should ask the experts first. :-)\n\nthanks.\n\n\nps: full disclosure: I may be the only one who wants this, but if\nsuccessful, I do plan to release my changes in case someone else wishes\nto run with status-quo consensus rules.",
"sig": "920dad9acc2ea8fffa45fdbcc32759500dc4b521346df552ec9f417598415f32f6dfb94bb59251d64e568e3f862bc6980d53e5bf53545ad215c6b6b4f21defda"
}