📅 Original date posted:2017-06-20
📝 Original message:On Tue, Jun 20, 2017 at 3:44 PM, Erik Aronesty via bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org> wrote:
> Because a large percentage of miners are indifferent, right now miners have
> to choose between BIP148 and Segwit2x if they want to activate Segwit.
Miners can simply continuing signaling segwit, which will leave them
at least soft-fork compatible with BIP148 and BIP91 (and god knows
what "segwit2x" is since they keep changing the actual definition and
do not have a specification; but last I saw the near-term behavior the
same as BIP91 but with a radically reduced activation window, so the
story would be the same there in the near term).
Ironically, it looks like most of the segwit2x signaling miners are
faking it (because they're not signaling segwit which it requires).
It'll be unfortunate if some aren't faking it and start orphaning
their own blocks because they are failing to signal segwit.
I don't think the rejection of segwit2x from Bitcoin's developers
could be any more resolute than what we've already seen:
https://en.bitcoin.it/wiki/Segwit_support
On Tue, Jun 20, 2017 at 5:22 PM, Mark Friedenbach via bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org> wrote:
> I think it is very naïve to assume that any shift would be temporary.
> We have a hard enough time getting miners to proactively upgrade to
> recent versions of the reference bitcoin daemon. If miners interpret
> the situation as being forced to run non-reference software in order
> to prevent a chain split because a lack of support from Bitcoin Core,
> that could be a one-way street.
I think this is somewhat naive and sounds a lot like the repeat of the
previously debunked "XT" and "Classic" hysteria.
There is a reason that segwit2x is pretty much unanimously rejected by
the technical community. And just like with XT/Classic/Unlimited
you'll continue to see a strong correlation with people who are
unwilling and unable to keep updating the software at an acceptable
level of quality-- esp. because the very founding on their fork is
predicated on discarding those properties.
If miners want to go off and create an altcoin-- welp, thats something
they can always do, and nothing about that will force anyone to go
along with it.
As far as prevent a chain split goes, all those things
(148/91/segwit2x(per today)) effectively guarantee a chainsplit-- so I
don't think that holds.
Gregory Maxwell [ARCHIVE] /
npub1f2…crwet
2023-06-07 18:03:26
in reply to nevent1q…wnqc
Author Public Key
npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwetSeen on
wss://relay.noswhere.comPublished at
2023-06-07 18:03:26Event JSON
{
"id": "fb63e6b148e828b0cb3dc283ecceab0a83274c5449f645735e416306194fb0f7",
"pubkey": "4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73",
"created_at": 1686161006,
"kind": 1,
"tags": [
[
"e",
"f10d3c1837e5518719736f82b51f13e32ba605e8e3996b8db87dad10332b09a3",
"",
"root"
],
[
"e",
"21a2b9a909314d4598999c4b2176ef15c3308b8ded3b28b15d8692903c624f3b",
"",
"reply"
],
[
"p",
"1c61d995949cbfaf14f767784e166bde865c7b8783d7aa3bf0a1d014b70c0069"
]
],
"content": "📅 Original date posted:2017-06-20\n📝 Original message:On Tue, Jun 20, 2017 at 3:44 PM, Erik Aronesty via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e Because a large percentage of miners are indifferent, right now miners have\n\u003e to choose between BIP148 and Segwit2x if they want to activate Segwit.\n\nMiners can simply continuing signaling segwit, which will leave them\nat least soft-fork compatible with BIP148 and BIP91 (and god knows\nwhat \"segwit2x\" is since they keep changing the actual definition and\ndo not have a specification; but last I saw the near-term behavior the\nsame as BIP91 but with a radically reduced activation window, so the\nstory would be the same there in the near term).\n\nIronically, it looks like most of the segwit2x signaling miners are\nfaking it (because they're not signaling segwit which it requires).\nIt'll be unfortunate if some aren't faking it and start orphaning\ntheir own blocks because they are failing to signal segwit.\n\nI don't think the rejection of segwit2x from Bitcoin's developers\ncould be any more resolute than what we've already seen:\nhttps://en.bitcoin.it/wiki/Segwit_support\n\nOn Tue, Jun 20, 2017 at 5:22 PM, Mark Friedenbach via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e I think it is very naïve to assume that any shift would be temporary.\n\u003e We have a hard enough time getting miners to proactively upgrade to\n\u003e recent versions of the reference bitcoin daemon. If miners interpret\n\u003e the situation as being forced to run non-reference software in order\n\u003e to prevent a chain split because a lack of support from Bitcoin Core,\n\u003e that could be a one-way street.\n\nI think this is somewhat naive and sounds a lot like the repeat of the\npreviously debunked \"XT\" and \"Classic\" hysteria.\n\nThere is a reason that segwit2x is pretty much unanimously rejected by\nthe technical community. And just like with XT/Classic/Unlimited\nyou'll continue to see a strong correlation with people who are\nunwilling and unable to keep updating the software at an acceptable\nlevel of quality-- esp. because the very founding on their fork is\npredicated on discarding those properties.\n\nIf miners want to go off and create an altcoin-- welp, thats something\nthey can always do, and nothing about that will force anyone to go\nalong with it.\n\nAs far as prevent a chain split goes, all those things\n(148/91/segwit2x(per today)) effectively guarantee a chainsplit-- so I\ndon't think that holds.",
"sig": "e94487d41e742ac2e0bb152664251c3439907d347ea2ce2d527b6caf16a380ad64638f4de56d6e16d19f978396dcc72c2c656ed1a85171a81559f1c808a707f8"
}