📅 Original date posted:2017-06-21
📝 Original message:Well, this Saturday's "Chinese roundtable" statement from a bunch of
miners (https://pastebin.com/b3St9VCF) says they intend "NYA" in the
coinbase as support for "the New York consensus SegWit2x program btc1 (
https://github.com/btc1)", whose code includes the (accelerated 336-block)
BIP 91 change. So, other facts or interpretations could come to light, but
until they do we should probably assume that's what the "NYA" (which just
broke 80% over the last 24h) means.
On Tue, Jun 20, 2017 at 10:11 PM, Mark Friedenbach <mark at friedenbach.org>
wrote:
> 80% have set "NYA" in their coinbase string. We have no idea what that
> means. People are equating it to BIP 91 -- but BIP 91 did not exist at
> the time of the New York agreement, and differs from the actual text
> of the NYA in substantive ways. The "Segwit2MB" that existed at the
> time of the NYA, and which was explicitly referenced by the text is
> the proposal by Sergio Demian Lerner that was made to this mailing
> list on 31 March. The text of the NYA grants no authority for
> upgrading this proposal while remaining compliant with the agreement.
> This is without even considering the fact that in the days after the
> NYA there was disagreement among those who signed it as to what it
> meant.
>
> I feel it is a very dangerous and unwarranted assumption people are
> making that what we are seeing now is either 80% support for BIP-91 or
> for the code in the btc1 repo.
>
> On Tue, Jun 20, 2017 at 6:36 PM, Erik Aronesty <erik at q32.com> wrote:
> > # Jacob Eliosoff:
> >
> >> will start orphaning non-bit-1 blocks before Aug 1, and we avoid a
> split.
> >
> > Correct. There are 2 short activation periods in BIP91 either of which
> > would avoid a split.
> >
> > # Gregory Maxwell:
> >
> >> unclear to me _exactly_ what it would need to implement to be
> consistent.
> >
> > This is the relevant pull req to core:
> >
> > https://github.com/bitcoin/bitcoin/pull/10444
> >
> > Seems OK. It's technically running now on testnet5. I think it (or a
> > -bip148 option) should be merged as soon as feasible.
> >
> >> previously debunked "XT" and "Classic" hysteria.
> >
> > apples vs oranges, imo. segwit is not a contentious feature. the
> > "bundling" in segwit2x is, but that's not the issue here. the issue is
> we
> > are indirectly requiring miners that strongly support segwit to install
> > consensus protocol changes outside of bitcoin's standard reference.
> 80% of
> > them have signaled they will do so. these are uncharted waters.
> >
> >
> > On Tue, Jun 20, 2017 at 6:57 PM, Jacob Eliosoff via bitcoin-dev
> > <bitcoin-dev at lists.linuxfoundation.org> wrote:
> >>
> >> I could be wrong, but the latest BIP91 implementation (also included in
> >> Segwit2x) cuts the activation period to 336 blocks (2.33 days). (This
> has
> >> been updated at
> >> https://github.com/bitcoin/bips/blob/master/bip-0091.mediawiki.) So
> if 80%
> >> of hashpower is actually running that code and signaling on bit 4 by
> July 25
> >> or so, then those 80+% will start orphaning non-bit-1 blocks before Aug
> 1,
> >> and we avoid a split.
> >>
> >> There may still be a few non-bit-1 blocks that get orphaned after Aug 1,
> >> because they're mined by old BIP141 nodes. But it seems like very few
> >> miners won't be signaling either Segwit2x *or* BIP141 by then...
> >>
> >> Make sense?
> >>
> >>
> >> On Tue, Jun 20, 2017 at 6:48 PM, Mark Friedenbach <mark at friedenbach.org
> >
> >> wrote:
> >>>
> >>> Why do you say activation by August 1st is likely? That would require
> an
> >>> entire difficulty adjustment period with >=95% bit1 signaling. That
> seems a
> >>> tall order to organize in the scant few weeks remaining.
> >>>
> >>> On Jun 20, 2017, at 3:29 PM, Jacob Eliosoff via bitcoin-dev
> >>> <bitcoin-dev at lists.linuxfoundation.org> wrote:
> >>>
> >>> If segwit is activated before Aug 1, as now seems likely, there will be
> >>> no split that day. But if activation is via Segwit2x (also likely),
> and at
> >>> least some nodes do & some don't follow through with the HF 3mo later
> >>> (again, likely), agreed w/ Greg that *then* we'll see a split -
> probably in
> >>> Sep/Oct. How those two chains will match up and how the split will
> play out
> >>> is anyone's guess...
> >>>
> >>>
> >>>
> >>> On Jun 20, 2017 6:16 PM, "Hampus Sjöberg via bitcoin-dev"
> >>> <bitcoin-dev at lists.linuxfoundation.org> wrote:
> >>>
> >>> > 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.
> >>>
> >>> Well, they're doing some kind of "pre-signaling" in the coinbase at the
> >>> moment, because the segwit2x project is still in alpha-phase according
> to
> >>> the timeline. They're just showing commitment.
> >>> I'm sure they will begin signaling on version bit 4/BIP91 as well as
> >>> actually running a segwit2x node when the time comes.
> >>>
> >>>
> >>> > 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.
> >>>
> >>> Segwit2x/BIP91/BIP148 will orphan miners that do not run a Segwit2x (or
> >>> BIP148) node, because they wouldn't have the new consensus rule of
> requiring
> >>> all blocks to signal for segwit.
> >>> I don't believe there would be any long lasting chainsplit though
> >>> (because of the ~80% hashrate support on segwit2x), perhaps 2-3 blocks
> if we
> >>> get unlucky.
> >>>
> >>> Hampus
> >>>
> >>> 2017-06-20 23:49 GMT+02:00 Gregory Maxwell via bitcoin-dev
> >>> <bitcoin-dev at lists.linuxfoundation.org>:
> >>>>
> >>>> 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.
> >>>> _______________________________________________
> >>>> bitcoin-dev mailing list
> >>>> bitcoin-dev at lists.linuxfoundation.org
> >>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> bitcoin-dev mailing list
> >>> bitcoin-dev at lists.linuxfoundation.org
> >>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >>>
> >>>
> >>> _______________________________________________
> >>> bitcoin-dev mailing list
> >>> bitcoin-dev at lists.linuxfoundation.org
> >>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >>
> >>
> >>
> >> _______________________________________________
> >> 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/20170621/9b66620b/attachment-0001.html>;
Jacob Eliosoff [ARCHIVE] /
npub1ml…4yf8d
2023-06-07 18:03:30
in reply to nevent1q…2ljm
Author Public Key
npub1mlpmsc5sm93tw2fp2dhhuwmxcqm59wz6hjg5g3afq5rucfll3f9sh4yf8dPublished at
2023-06-07 18:03:30Event JSON
{
"id": "651a62966866077318b6dc4ed8113d7322ef94689d1d57b454142f32c604193b",
"pubkey": "dfc3b86290d962b72921536f7e3b66c03742b85abc914447a90507cc27ff8a4b",
"created_at": 1686161010,
"kind": 1,
"tags": [
[
"e",
"f10d3c1837e5518719736f82b51f13e32ba605e8e3996b8db87dad10332b09a3",
"",
"root"
],
[
"e",
"4080783a7a571bd175902f5898661bcca6857a134f56536f62c7216b291c4b49",
"",
"reply"
],
[
"p",
"1c61d995949cbfaf14f767784e166bde865c7b8783d7aa3bf0a1d014b70c0069"
]
],
"content": "📅 Original date posted:2017-06-21\n📝 Original message:Well, this Saturday's \"Chinese roundtable\" statement from a bunch of\nminers (https://pastebin.com/b3St9VCF) says they intend \"NYA\" in the\ncoinbase as support for \"the New York consensus SegWit2x program btc1 (\nhttps://github.com/btc1)\", whose code includes the (accelerated 336-block)\nBIP 91 change. So, other facts or interpretations could come to light, but\nuntil they do we should probably assume that's what the \"NYA\" (which just\nbroke 80% over the last 24h) means.\n\n\nOn Tue, Jun 20, 2017 at 10:11 PM, Mark Friedenbach \u003cmark at friedenbach.org\u003e\nwrote:\n\n\u003e 80% have set \"NYA\" in their coinbase string. We have no idea what that\n\u003e means. People are equating it to BIP 91 -- but BIP 91 did not exist at\n\u003e the time of the New York agreement, and differs from the actual text\n\u003e of the NYA in substantive ways. The \"Segwit2MB\" that existed at the\n\u003e time of the NYA, and which was explicitly referenced by the text is\n\u003e the proposal by Sergio Demian Lerner that was made to this mailing\n\u003e list on 31 March. The text of the NYA grants no authority for\n\u003e upgrading this proposal while remaining compliant with the agreement.\n\u003e This is without even considering the fact that in the days after the\n\u003e NYA there was disagreement among those who signed it as to what it\n\u003e meant.\n\u003e\n\u003e I feel it is a very dangerous and unwarranted assumption people are\n\u003e making that what we are seeing now is either 80% support for BIP-91 or\n\u003e for the code in the btc1 repo.\n\u003e\n\u003e On Tue, Jun 20, 2017 at 6:36 PM, Erik Aronesty \u003cerik at q32.com\u003e wrote:\n\u003e \u003e # Jacob Eliosoff:\n\u003e \u003e\n\u003e \u003e\u003e will start orphaning non-bit-1 blocks before Aug 1, and we avoid a\n\u003e split.\n\u003e \u003e\n\u003e \u003e Correct. There are 2 short activation periods in BIP91 either of which\n\u003e \u003e would avoid a split.\n\u003e \u003e\n\u003e \u003e # Gregory Maxwell:\n\u003e \u003e\n\u003e \u003e\u003e unclear to me _exactly_ what it would need to implement to be\n\u003e consistent.\n\u003e \u003e\n\u003e \u003e This is the relevant pull req to core:\n\u003e \u003e\n\u003e \u003e https://github.com/bitcoin/bitcoin/pull/10444\n\u003e \u003e\n\u003e \u003e Seems OK. It's technically running now on testnet5. I think it (or a\n\u003e \u003e -bip148 option) should be merged as soon as feasible.\n\u003e \u003e\n\u003e \u003e\u003e previously debunked \"XT\" and \"Classic\" hysteria.\n\u003e \u003e\n\u003e \u003e apples vs oranges, imo. segwit is not a contentious feature. the\n\u003e \u003e \"bundling\" in segwit2x is, but that's not the issue here. the issue is\n\u003e we\n\u003e \u003e are indirectly requiring miners that strongly support segwit to install\n\u003e \u003e consensus protocol changes outside of bitcoin's standard reference.\n\u003e 80% of\n\u003e \u003e them have signaled they will do so. these are uncharted waters.\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e On Tue, Jun 20, 2017 at 6:57 PM, Jacob Eliosoff via bitcoin-dev\n\u003e \u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003e\u003e\n\u003e \u003e\u003e I could be wrong, but the latest BIP91 implementation (also included in\n\u003e \u003e\u003e Segwit2x) cuts the activation period to 336 blocks (2.33 days). (This\n\u003e has\n\u003e \u003e\u003e been updated at\n\u003e \u003e\u003e https://github.com/bitcoin/bips/blob/master/bip-0091.mediawiki.) So\n\u003e if 80%\n\u003e \u003e\u003e of hashpower is actually running that code and signaling on bit 4 by\n\u003e July 25\n\u003e \u003e\u003e or so, then those 80+% will start orphaning non-bit-1 blocks before Aug\n\u003e 1,\n\u003e \u003e\u003e and we avoid a split.\n\u003e \u003e\u003e\n\u003e \u003e\u003e There may still be a few non-bit-1 blocks that get orphaned after Aug 1,\n\u003e \u003e\u003e because they're mined by old BIP141 nodes. But it seems like very few\n\u003e \u003e\u003e miners won't be signaling either Segwit2x *or* BIP141 by then...\n\u003e \u003e\u003e\n\u003e \u003e\u003e Make sense?\n\u003e \u003e\u003e\n\u003e \u003e\u003e\n\u003e \u003e\u003e On Tue, Jun 20, 2017 at 6:48 PM, Mark Friedenbach \u003cmark at friedenbach.org\n\u003e \u003e\n\u003e \u003e\u003e wrote:\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e Why do you say activation by August 1st is likely? That would require\n\u003e an\n\u003e \u003e\u003e\u003e entire difficulty adjustment period with \u003e=95% bit1 signaling. That\n\u003e seems a\n\u003e \u003e\u003e\u003e tall order to organize in the scant few weeks remaining.\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e On Jun 20, 2017, at 3:29 PM, Jacob Eliosoff via bitcoin-dev\n\u003e \u003e\u003e\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e If segwit is activated before Aug 1, as now seems likely, there will be\n\u003e \u003e\u003e\u003e no split that day. But if activation is via Segwit2x (also likely),\n\u003e and at\n\u003e \u003e\u003e\u003e least some nodes do \u0026 some don't follow through with the HF 3mo later\n\u003e \u003e\u003e\u003e (again, likely), agreed w/ Greg that *then* we'll see a split -\n\u003e probably in\n\u003e \u003e\u003e\u003e Sep/Oct. How those two chains will match up and how the split will\n\u003e play out\n\u003e \u003e\u003e\u003e is anyone's guess...\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e On Jun 20, 2017 6:16 PM, \"Hampus Sjöberg via bitcoin-dev\"\n\u003e \u003e\u003e\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e \u003e Ironically, it looks like most of the segwit2x signaling miners are\n\u003e \u003e\u003e\u003e \u003e faking it (because they're not signaling segwit which it requires).\n\u003e \u003e\u003e\u003e \u003e It'll be unfortunate if some aren't faking it and start orphaning\n\u003e \u003e\u003e\u003e \u003e their own blocks because they are failing to signal segwit.\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e Well, they're doing some kind of \"pre-signaling\" in the coinbase at the\n\u003e \u003e\u003e\u003e moment, because the segwit2x project is still in alpha-phase according\n\u003e to\n\u003e \u003e\u003e\u003e the timeline. They're just showing commitment.\n\u003e \u003e\u003e\u003e I'm sure they will begin signaling on version bit 4/BIP91 as well as\n\u003e \u003e\u003e\u003e actually running a segwit2x node when the time comes.\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e \u003e As far as prevent a chain split goes, all those things\n\u003e \u003e\u003e\u003e \u003e (148/91/segwit2x(per today)) effectively guarantee a chainsplit-- so\n\u003e I\n\u003e \u003e\u003e\u003e \u003e don't think that holds.\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e Segwit2x/BIP91/BIP148 will orphan miners that do not run a Segwit2x (or\n\u003e \u003e\u003e\u003e BIP148) node, because they wouldn't have the new consensus rule of\n\u003e requiring\n\u003e \u003e\u003e\u003e all blocks to signal for segwit.\n\u003e \u003e\u003e\u003e I don't believe there would be any long lasting chainsplit though\n\u003e \u003e\u003e\u003e (because of the ~80% hashrate support on segwit2x), perhaps 2-3 blocks\n\u003e if we\n\u003e \u003e\u003e\u003e get unlucky.\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e Hampus\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e 2017-06-20 23:49 GMT+02:00 Gregory Maxwell via bitcoin-dev\n\u003e \u003e\u003e\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e:\n\u003e \u003e\u003e\u003e\u003e\n\u003e \u003e\u003e\u003e\u003e On Tue, Jun 20, 2017 at 3:44 PM, Erik Aronesty via bitcoin-dev\n\u003e \u003e\u003e\u003e\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003e\u003e\u003e\u003e \u003e Because a large percentage of miners are indifferent, right now\n\u003e miners\n\u003e \u003e\u003e\u003e\u003e \u003e have\n\u003e \u003e\u003e\u003e\u003e \u003e to choose between BIP148 and Segwit2x if they want to activate\n\u003e Segwit.\n\u003e \u003e\u003e\u003e\u003e\n\u003e \u003e\u003e\u003e\u003e Miners can simply continuing signaling segwit, which will leave them\n\u003e \u003e\u003e\u003e\u003e at least soft-fork compatible with BIP148 and BIP91 (and god knows\n\u003e \u003e\u003e\u003e\u003e what \"segwit2x\" is since they keep changing the actual definition and\n\u003e \u003e\u003e\u003e\u003e do not have a specification; but last I saw the near-term behavior the\n\u003e \u003e\u003e\u003e\u003e same as BIP91 but with a radically reduced activation window, so the\n\u003e \u003e\u003e\u003e\u003e story would be the same there in the near term).\n\u003e \u003e\u003e\u003e\u003e\n\u003e \u003e\u003e\u003e\u003e Ironically, it looks like most of the segwit2x signaling miners are\n\u003e \u003e\u003e\u003e\u003e faking it (because they're not signaling segwit which it requires).\n\u003e \u003e\u003e\u003e\u003e It'll be unfortunate if some aren't faking it and start orphaning\n\u003e \u003e\u003e\u003e\u003e their own blocks because they are failing to signal segwit.\n\u003e \u003e\u003e\u003e\u003e\n\u003e \u003e\u003e\u003e\u003e I don't think the rejection of segwit2x from Bitcoin's developers\n\u003e \u003e\u003e\u003e\u003e could be any more resolute than what we've already seen:\n\u003e \u003e\u003e\u003e\u003e https://en.bitcoin.it/wiki/Segwit_support\n\u003e \u003e\u003e\u003e\u003e\n\u003e \u003e\u003e\u003e\u003e On Tue, Jun 20, 2017 at 5:22 PM, Mark Friedenbach via bitcoin-dev\n\u003e \u003e\u003e\u003e\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003e\u003e\u003e\u003e \u003e I think it is very naïve to assume that any shift would be\n\u003e temporary.\n\u003e \u003e\u003e\u003e\u003e \u003e We have a hard enough time getting miners to proactively upgrade to\n\u003e \u003e\u003e\u003e\u003e \u003e recent versions of the reference bitcoin daemon. If miners interpret\n\u003e \u003e\u003e\u003e\u003e \u003e the situation as being forced to run non-reference software in order\n\u003e \u003e\u003e\u003e\u003e \u003e to prevent a chain split because a lack of support from Bitcoin\n\u003e Core,\n\u003e \u003e\u003e\u003e\u003e \u003e that could be a one-way street.\n\u003e \u003e\u003e\u003e\u003e\n\u003e \u003e\u003e\u003e\u003e I think this is somewhat naive and sounds a lot like the repeat of the\n\u003e \u003e\u003e\u003e\u003e previously debunked \"XT\" and \"Classic\" hysteria.\n\u003e \u003e\u003e\u003e\u003e\n\u003e \u003e\u003e\u003e\u003e There is a reason that segwit2x is pretty much unanimously rejected by\n\u003e \u003e\u003e\u003e\u003e the technical community. And just like with XT/Classic/Unlimited\n\u003e \u003e\u003e\u003e\u003e you'll continue to see a strong correlation with people who are\n\u003e \u003e\u003e\u003e\u003e unwilling and unable to keep updating the software at an acceptable\n\u003e \u003e\u003e\u003e\u003e level of quality-- esp. because the very founding on their fork is\n\u003e \u003e\u003e\u003e\u003e predicated on discarding those properties.\n\u003e \u003e\u003e\u003e\u003e\n\u003e \u003e\u003e\u003e\u003e If miners want to go off and create an altcoin-- welp, thats something\n\u003e \u003e\u003e\u003e\u003e they can always do, and nothing about that will force anyone to go\n\u003e \u003e\u003e\u003e\u003e along with it.\n\u003e \u003e\u003e\u003e\u003e\n\u003e \u003e\u003e\u003e\u003e As far as prevent a chain split goes, all those things\n\u003e \u003e\u003e\u003e\u003e (148/91/segwit2x(per today)) effectively guarantee a chainsplit-- so I\n\u003e \u003e\u003e\u003e\u003e don't think that holds.\n\u003e \u003e\u003e\u003e\u003e _______________________________________________\n\u003e \u003e\u003e\u003e\u003e bitcoin-dev mailing list\n\u003e \u003e\u003e\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e \u003e\u003e\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e _______________________________________________\n\u003e \u003e\u003e\u003e bitcoin-dev mailing list\n\u003e \u003e\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e \u003e\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e\n\u003e \u003e\u003e\u003e _______________________________________________\n\u003e \u003e\u003e\u003e bitcoin-dev mailing list\n\u003e \u003e\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e \u003e\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e \u003e\u003e\n\u003e \u003e\u003e\n\u003e \u003e\u003e\n\u003e \u003e\u003e _______________________________________________\n\u003e \u003e\u003e bitcoin-dev mailing list\n\u003e \u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e \u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e \u003e\u003e\n\u003e \u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170621/9b66620b/attachment-0001.html\u003e",
"sig": "a5dbcb1f9f7d594db42cc4869a51c34f3a22e3fd9b768f3585a15966e385b7b33733818fbc7456a0e82449fa1d9963ba1df16d34833e4cd9d6cad96f9a389ea8"
}