Pages:
Author

Topic: SegWit2x seriously losing support? - page 3. (Read 3130 times)

member
Activity: 98
Merit: 10
October 13, 2017, 04:38:00 PM
#15
Hmm interesting so is it possible that we will be able to avoid the fork if 2x keeps losing support? Let's say only 49% of the network is signaling 2x, could this mean a fork would be avoided? If not what would it take to avoid it or is it too late?
staff
Activity: 3458
Merit: 6793
Just writing some code
October 13, 2017, 03:44:18 PM
#14
Actually, BIP91 predated that NYA entirely and was written as a tool for miners to avoid a BIP148 introduced split.
I don't think so. The email proposing it literally references "the Barry Silbert proposal" which, although it may not have been published at that time, was leaked a day or two before it was actually published.
staff
Activity: 4284
Merit: 8808
October 13, 2017, 01:29:55 PM
#13
And BIP91
Actually, BIP91 predated that NYA entirely and was written as a tool for miners to avoid a BIP148 introduced split.

BTC1 adopted it (with some prodding by its author) and also kept its signaling the same, forever obfuscating the activation.  All of the miners I've spoken to were running segsignal (BIP91) and not 2x.

the Segwit guys
Were never involved with the "NYA" at all.

It's like your neighbors making a deal among themselves to divide up your home and assets... and now people are calling you out for reneging on an agreement that you never agreed to!
member
Activity: 66
Merit: 10
October 13, 2017, 10:05:57 AM
#12
I don't even get why they need all those SegWit2x and Forks for bitcoin, it seems like they just try to get new coins to sell them ,as you saw in BCH it was $800 and now $300 Smiley
legendary
Activity: 3430
Merit: 3080
October 13, 2017, 04:33:39 AM
#11
Is that about right? Basically the Segwit guys are screwing over the big blockers by reneging on the deal now that their part is passed?

No.

Supporters of Segwit BIP142 (aka Bitcoin Core's original version) weren't involved in any deal. The NYA deal was unilaterally agreed by it's miner/service company signatories, and these companies, especially the miners, were split on whether to activate Segwit BIP 142 beforehand.

And BIP91 (which was a simple block orphaning mechanism used to activate Segwit's BIP142) was written by 1 programmer, representing no-one except himself, and with the intention of resolving incompatibilities between the NYA Segwit deployment and the BIP142 Segwit deployment.
legendary
Activity: 1806
Merit: 1521
October 13, 2017, 03:48:01 AM
#10
Quote from: Kyle Torpey
While everyone was worried about #bitcoin mining centralization, @blockchain was processing 40% of on-chain transactions.
Is the above true?
It's something that blockchain claims but I am fairly confident that it has no basis in reality. They base the claim on how many transactions are submitted through their API, but many people pick up random transactions from the network and submit it to their API because it has, at times, been the only way to make transactions reliably display on their site, because their nodes are sometimes down.  Transactions generated by their wallet have been historically distinctive in a number of ways-- they are not generating anywhere near that number of transactions on the network.

Thanks for the reassurance. I suspected the numbers were being fudged somehow. At the same time, I know that BCI is a favorite among noobs, so I'm definitely concerned about their support for Segwit2x should it be the stronger-POW chain. It's also not clear what timeframe Xapo and BCI are talking about. What if both chains -- at various times -- have more cumulative POW than the other? I can't tell from their posts what happens if there is no clear cut "winner" (in terms of difficulty).

Recently,95%of hash power was signaled towards segwit 2x.Now,f2Pool which has 10% of hash power has withdrawn.So only 85%support for segwit 2x.Its been celebrated as a great victory for the core team.

F2Pool said they were dropping out like a month ago. They said they would stop signalling the NYA on the next pool server restart. Why are they still signalling the NYA? There are rumors of various threats coming Wang Chun's way (from Bitmain mostly) but I don't know the details or if there is any truth to the rumors.
hero member
Activity: 544
Merit: 507
October 13, 2017, 03:47:49 AM
#9
Until  now,three companies have abandoned the New York Agreement so far.

1.Bitwala
2.F2Pool.
3.Wayniloans.

Out of these,two have said that they expected that bitcoin core team would support segwit 2x and now having known that they don't support,they are also withdrawing the support.

Recently,95%of hash power was signaled towards segwit 2x.Now,f2Pool which has 10% of hash power has withdrawn.So only 85%support for segwit 2x.Its been celebrated as a great victory for the core team.

But the operator of F2Pool wang chung is already known for his controversial statements.so,we would have to wait and see whether hard fork would occur or not.

If F2Pool has abandoned the New York Agreement then, from my point of view, 2X is dead.
It is one of the mayor pools in the world.

And as other has mentioned before, if it does not have the support from developers and it is something created to fulfill some shady intentions from certain individuals..

you don't need to think too much about its premature death.
legendary
Activity: 1218
Merit: 1003
October 13, 2017, 02:46:01 AM
#8
It does speak to the character of the people involved in the whole business of Bitcoin how the NYA agreement was made and what has happened since.
As I see it: Segwit wasn't going to get deployed, it didn't have enough support.  Big blockers wanted bigger blocks rather than Segwit, Segwitters didn't really want big blocks.

So they all agree: we do Segwit, then we double the block size. That gets enough votes and Segwit goes live, then the segwitters decide that they don't want big blocks and they already have what they want, so stop voting for the block size increase.

Is that about right? Basically the Segwit guys are screwing over the big blockers by reneging on the deal now that their part is passed?
legendary
Activity: 2898
Merit: 1823
October 13, 2017, 01:35:46 AM
#7
OP, there was really no support from the people that matter. The Core engineers, who are the best minds in Bitcoin, and the community, and I do not mean the people. I mean the ones who are running the full nodes. The good majority of them still run Core software.



They let their actions speak. "Signalling" from the miners and the merchants signing the NYA mean nothing. This is Bitcoin.
hero member
Activity: 742
Merit: 500
October 13, 2017, 12:49:10 AM
#6
Until  now,three companies have abandoned the New York Agreement so far.

1.Bitwala
2.F2Pool.
3.Wayniloans.

Out of these,two have said that they expected that bitcoin core team would support segwit 2x and now having known that they don't support,they are also withdrawing the support.

Recently,95%of hash power was signaled towards segwit 2x.Now,f2Pool which has 10% of hash power has withdrawn.So only 85%support for segwit 2x.Its been celebrated as a great victory for the core team.

But the operator of F2Pool wang chung is already known for his controversial statements.so,we would have to wait and see whether hard fork would occur or not.
staff
Activity: 4284
Merit: 8808
October 12, 2017, 11:52:36 PM
#5
And a couple hours later, we see Blockchain.info double down in support of Segwit2x. They basically issued a repeat of Xapo's statement. They will consider the strongest chain to be "Bitcoin" regardless of anything else, and will not support the minority chain in the long term (though they will likely make it available for withdrawal).

But in one sense it is the weakest possible support short of outright opposition.

It is effectively saying "we will do whatever other people do"...  So if you have a dispute between two groups, one saying "We'll do what other people do" and another group saying "We absolutely positively will not do thing-B but will instead do thing-A"  ... what do you think is going to happen?

In the presence of a considerable part of the community that won't follow B2X under almost any condition bc.i's statement is not really all that supportive.

Quote
Quote from: Kyle Torpey
While everyone was worried about #bitcoin mining centralization, @blockchain was processing 40% of on-chain transactions.
Is the above true?
It's something that blockchain claims but I am fairly confident that it has no basis in reality. They base the claim on how many transactions are submitted through their API, but many people pick up random transactions from the network and submit it to their API because it has, at times, been the only way to make transactions reliably display on their site, because their nodes are sometimes down.  Transactions generated by their wallet have been historically distinctive in a number of ways-- they are not generating anywhere near that number of transactions on the network.
hero member
Activity: 770
Merit: 509
October 12, 2017, 05:02:26 PM
#4
Something strange is happening right now.
 I do not fully understand what yet but it seems some members of Pro-segwit2x group are publicly withdrawing their support for SegWit2x

Could this mean the hard fork won't be going on again? Seems they aren't too happy the way Bitcoin price is shooting up or it is just normal and expected withdraws?



F2Pool controlled by chinese miner Wang Chung recently withdrew support from the "intention" signaling as he promised, so we already have Slushpool and F2Pool to survive after the hardfork:

https://www.reddit.com/r/Bitcoin/comments/75wh5b/block_489492_f2pool_doesnt_signal_nya_anymore/

The question is: Is this enough hashrate to survive a potential 51% attack by the NYAers?
legendary
Activity: 1806
Merit: 1521
October 12, 2017, 04:44:01 PM
#3
Something strange is happening right now.
 I do not fully understand what yet but it seems some members of Pro-segwit2x group are publicly withdrawing their support for SegWit2x

Could this mean the hard fork won't be going on again? Seems they aren't too happy the way Bitcoin price is shooting up or it is just normal and expected withdraws?

And a couple hours later, we see Blockchain.info double down in support of Segwit2x. They basically issued a repeat of Xapo's statement. They will consider the strongest chain to be "Bitcoin" regardless of anything else, and will not support the minority chain in the long term (though they will likely make it available for withdrawal). See here: https://twitter.com/blockchain/status/918576340789616640

Their wallet was already less secure than a lightweight desktop client like Electrum, anyway. There's definitely no reason to use them now. But this raises an important question:

Quote from: Kyle Torpey
While everyone was worried about #bitcoin mining centralization, @blockchain was processing 40% of on-chain transactions.

Is the above true? If so, that could have serious ramifications for network activity when the November fork takes place. This could mean a lot of lost bitcoins. It could also mean claims that the 2X chain not only is stronger POW-wise, but has more economic activity. Source: https://twitter.com/kyletorpey/status/918583640317075457
legendary
Activity: 3430
Merit: 3080
October 12, 2017, 03:04:18 PM
#2
Well, there's little more than 1 programmer working on Segwit2x, and that's a serious contrast to the Bitcoin Core team (30 or 40 programmers) when you look at the Github account for the S2x (confusing named "BTC1") software client.

So claims of industry-wide consensus, a professional team or decentralised development are looking a little different in reality. At least 1 of the NYA signatories made comments to that effect.
Ucy
sr. member
Activity: 2674
Merit: 403
Compare rates on different exchanges & swap.
October 12, 2017, 01:59:57 PM
#1
Something strange is happening right now.
 I do not fully understand what yet but it seems some members of Pro-segwit2x group are publicly withdrawing their support for SegWit2x

Could this mean the hard fork won't be going on again? Seems they aren't too happy the way Bitcoin price is shooting up or it is just normal and expected withdraws?

Pages:
Jump to: