The Barry Silbert segwit2x agreement with >80% miner support.

[classicsucks]

the emergent consensus will get ...

Emergent consensus has nothing to do with this. Forget anything to do with BU, that's been long forgotten by the power players. Any reference to EC in their block signature is there for legacy reasons and doesn't remotely mean they're interested in BU any more. BU supporters will insist this isn't the end for them and that it's still compatible with segwit2x, but then so is XT, classic and any other defunct attempt at a takeover from the past that never activates and stays on the current chain waiting to take it over at some unforeseen parallel universe future. Forget EC.

So... forget Segwit then? After all, it's also a defunct attempt at a takeover from the past that never activates... UASF is crap, and Segwit2x doesn't have a codebase or dev support last I checked.  Unlimited has both of those (inb4 "but it's buggy", etc.).

People seem very confident about what will happen based on what people are saying. Remember that miners don't trust Core at all after they breached the Hong Kong agreement. Miners are perfectly within the negotiating rules to say whatever they want. What they (and the other players in this game) will do is another matter entirely.

[1714926490]

1714926490

[1714926490]

1714926490

[1714926490]

1714926490

[allinvain]

83.3% support now with NYA in their coinbase so it's reached activation levels. This has been helped by bitclubnetwork joining them, however they've also actually started the real signalling on bit4/1 that activates it in mid-july. The reason is that the admin of that pool is the one that defined BIP91 and wrote the code for it so he's the first to use it as more than just proof of concept.

Well this is good news for a change!

You know, at this point Segwit2x is better than a chain split. Let's hope for the best.

[Nagadota]

the emergent consensus will get ...

Emergent consensus has nothing to do with this. Forget anything to do with BU, that's been long forgotten by the power players. Any reference to EC in their block signature is there for legacy reasons and doesn't remotely mean they're interested in BU any more. BU supporters will insist this isn't the end for them and that it's still compatible with segwit2x, but then so is XT, classic and any other defunct attempt at a takeover from the past that never activates and stays on the current chain waiting to take it over at some unforeseen parallel universe future. Forget EC.

So... forget Segwit then? After all, it's also a defunct attempt at a takeover from the past that never activates... UASF is crap, and Segwit2x doesn't have a codebase or dev support last I checked.  Unlimited has both of those (inb4 "but it's buggy", etc.).

People seem very confident about what will happen based on what people are saying. Remember that miners don't trust Core at all after they breached the Hong Kong agreement. Miners are perfectly within the negotiating rules to say whatever they want. What they (and the other players in this game) will do is another matter entirely.

The clock is ticking for miners.  If they've already agreed to activate SegWitx2 when they can, they can't really back out of it.  People would get pissed off and UASF would look a lot more realistic than it did before.

EC/BU is irrelevant because support has flatlined while SegWitx2 support is now soaring.

[-ck]

83.3% support now with NYA in their coinbase so it's reached activation levels. This has been helped by bitclubnetwork joining them, however they've also actually started the real signalling on bit4/1 that activates it in mid-july. The reason is that the admin of that pool is the one that defined BIP91 and wrote the code for it so he's the first to use it as more than just proof of concept.

Well this is good news for a change!

You know, at this point Segwit2x is better than a chain split. Let's hope for the best.

With the segwit component assured now, indeed it is at this point, until we get to the 2x part of it. That's when the next battle begins.

[hv_]

83.3% support now with NYA in their coinbase so it's reached activation levels. This has been helped by bitclubnetwork joining them, however they've also actually started the real signalling on bit4/1 that activates it in mid-july. The reason is that the admin of that pool is the one that defined BIP91 and wrote the code for it so he's the first to use it as more than just proof of concept.

Well this is good news for a change!

You know, at this point Segwit2x is better than a chain split. Let's hope for the best.

With the segwit component assured now, indeed it is at this point, until we get to the 2x part of it. That's when the next battle begins.

The 2x might buy some time to prepare next scaling steps. Not sure if community is prepared better if this is needed in some years.

[ComputerGenie]

The 2x might buy some time to prepare next scaling steps. Not sure if community is prepared better if this is needed in some years.

Since the pro-segwit crowd did such a great job in convincing people of the myths that LN is a great thing and that it's actually part of Bitcoin, 2x is the "next step". LN has plenty of commercial applications, but the average user will rarely, if ever, use it (and even when they do, most will find that the end-point number of transactions in the mempool for "average" users isn't as reduced as many have been led to believe). Yes, segwit will add to the number of available transactions in a given block, but it's far better to be in advance of the need for change than be behind trying to play "catch-up" like we are now.

Think of it in terms to running a mining farm (yes, I can hear the anti-miners groaning already). If you have a hashrate of x, then every 2 weeks you'll need to have x+(x*0.06) to earn the same income as you earned the day before. Your income becomes less impacted if you bring that +6% online before the next diff increase than it does if you do it after. The 2x is no different, it's better to have a ton of available empty space than be right back here ever again.

[ComputerGenie]

...yea yea i expect my post to get deleted even though it contains content about segwit2x

Maybe if you quit posting dumbass comments like that, then you'd stop pissing off the guy that can delete them? 

[-ck]

...yea yea i expect my post to get deleted even though it contains content about segwit2x

Maybe if you quit posting dumbass comments like that, then you'd stop pissing off the guy that can delete them?  

Actually it doesn't really matter what he says any more since I told him he is forbidden from posting on this thread and I have him on ignore so I can't even see what he's posting, just that he's posting and delete his posts on sight. He's done too much trolling for too long on too many threads to be able to redeem himself as far as I'm concerned. He is the no. 1 reason I made this thread self-moderated.

[franky1]

Segwit2x doesn't have a codebase or dev support last I checked.  Unlimited has both of those (inb4 "but it's buggy", etc.).

segwit2x does have a codebase
https://github.com/btc1/bitcoin/

https://github.com/btc1/bitcoin/blob/segwit2x/src/consensus/consensus.h
segwit2x now has code for a 2mb base block
33    if (!BIP102active(nHeight, fSegwitSeasoned))
34        return MAX_LEGACY_BLOCK_SIZE;
35
36    return (2 * 1000 * 1000);
37    }
...

which activates 3 months for th 2x after segwit
13    static const unsigned int BIP102_FORK_BUFFER = (144 * 90);

..

but not really a Release Candidate so its highly possible the pools flagging for segwit2x are not running the codebase
so all the flag waving of blocks is still kind of 'sybil' (empty/fake gesturing). so things are still up in the air.

Remember that miners don't trust Core at all after they breached the Hong Kong agreement.

the hong kong/ late 2015 consensus round table meetings  funded and sponsored by barry silbert.. is the same 'agreement' as segwit2x
but atleast there is some code available.

now we just have to see if we can get nodes to download it (once its finalised and reviewed for RC) to then get a NODE consensus... for pools to have confidence that if they made such blocks.. the nodes wont still be running old code to reject blocks bigger than (1*1000*1000).

what people seem to forget is its not simply about waving a flag in a block.. its about consensus of nodes actually running code rules that allow bigger base blocks and consensus of pools creating bigger base blocks.

at this moment the empty sybil flag waving will just cause segwit to activate, but no guarantee of base blocks over (1*1000*1000) being accepted because from bitnodes stats, it shows no one is actually running the segwit2x (btc1) codebase to enforce it

p.s only reason i rant/repeat myself. is due to the biased censorship deleting my posts to hide the facts, so i end up having to repeat things just for the hope that some posts get missed out in the deletions so that they actually get read.. because alot of the facts just get deleted. i would repeat myself alot less in topics if it wasnt for moderation deletions

[-ck]

If you guys tell me he's not trolling any more I'll reconsider.

[hv_]

If you guys tell me he's not trolling any more I'll reconsider.

I'd recommend.  I feel he's more ranting and overdoing rather than 'trolling'. Some USAF guys are 'ranting' same manner and we should be able to filter that kind of porn by ourselves - otherwise I read on reddit/bitcoin if I cant stand that kind.

 

[Variogam]

the hong kong/ late 2015 consensus round table meetings  funded and sponsored by barry silbert.. is the same 'agreement' as segwit2x
but atleast there is some code available.

now we just have to see if we can get nodes to download it (once its finalised and reviewed for RC) to then get a NODE consensus... for pools to have confidence that if they made such blocks.. the nodes wont still be running old code to reject blocks bigger than (1*1000*1000).

what people seem to forget is its not simply about waving a flag in a block.. its about consensus of nodes actually running code rules that allow bigger base blocks and consensus of pools creating bigger base blocks.

at this moment the empty sybil flag waving will just cause segwit to activate, but no guarantee of base blocks over (1*1000*1000) being accepted because from bitnodes stats, it shows no one is actually running the segwit2x (btc1) codebase to enforce it

You talk about importance of node numbers enforcing certain rules not for the first time, but how you know what nodes are economicaly important and what are basically worthless? Or you really believe 1 node = 1 vote

The only support/acceptance I find reliable is the statements from companies, and there seem enought SegWit2x support/acceptance from the important companies to guarantee 2MB. The only question remains whether there going to be split if 1MB gets enough holdout support.

[franky1]

You talk about importance of node numbers enforcing certain rules not for the first time, but how you know what nodes are economicaly important and what are basically worthless? Or you really believe 1 node = 1 vote

theres many aspects to it.. theres many reasons for having a distributed decentralised network of nodes.
things like (using torrent as an analogy)  if your connected to 8 seeds and need to sync(your the leacher for now) and the seeds have 4 nodes of 485,000 blocks but another 4 nodes have 484000 blocks. your going to grab data from the 485,000 nodes as you define that as the most complete list.

however you find out that the 485,000 nodes are on the old rules you end up orphaning them blocks and banning the nodes.. leaving you only seeing the 4 nodes with a height of 484,000(new rules) as that becomes the new visible highest height (complete chain)

so its not the case of just relying on one source of data... nodes prefer to have multiple sources that way if one source is 'wrong' they can grab data elsewhere..

so its important there are multiple sources of data, and that the majority of those multiple sources have the same rules as you do..

thats why its best that there are more then just 70 nodes all run just by merchants. but there are 'backup's too. which helps put less strain on the merchant nodes needing to be seeds because people can grab data from other locations, should a merchant get shutdown or ddosed or just over strained by too many leachers trying to connect to merchant nodes.

..
once you grasp the need for the decentralisation of the data.. you then can move on and grasp why its best that those decentralised diverse brand nodes also agree to the same rules as a majority, to avoid orphan drama.

..
once you grasp that. you realise by having your node agreeing to the merchant rules you can spend with that merchant because they see your tx. also to flip the argument, if the merchant see's its only getting bad data and the majority of the community is agreeing to other rules.. the merchants would treat the most popular chain as the main chain. and the bad data least popular nodes as the alt.

thus its not a sheep follow merchants who follow pools.. its about symbiotic relationship of consensus of everyone finding something agreeable.
..
having grasped that..you can then move on and grasp that bitcoin is revolutionary because it doesnt rely on everyone just leaching off of one pool of data but each node validates independently which makes the network stronger and less vulnerable to central-point-of-attack vectors. it also allows sharing of data to not put a strain on a central point..
it also ensures no central point decides the direction..

..
things would /could go very wrong if everyone was a leacher to just lets say 70 nodes all colluding to a single cartel. and this is why consensus only moves the network forward when independant people agree that the new rules that are in benefit to the community.. by the community having nodes that have the most reliable chain that is acceptable to the majority.

The only support/acceptance I find reliable is the statements from companies, and there seem enought SegWit2x support/acceptance from the important companies to guarantee 2MB. The only question remains whether there going to be split if 1MB gets enough holdout support.

signing a PDF is one thing.. changing a few bytes in a flag is one thing.
but in the end the nodes should only flag when they actually have the code to handle what they are flagging. otherwise its an empty gesture that falls flat on itself when 'activation' occurs.

EG lets say 80% want X and flag it,, but 75% actually are running A. X gets activated(false pretence). but then a clusterf**k of orphans because 75% are rejecting the activated rule. because they dont have the code to handle the new rule. they just waved a flag.

[bryant.coleman]

Forget about 80% consensus, we are now nearing 90% support, with SegWit2x being supported by 89.6% right now. In just around 24 hours, the support levels have increased from less than 80% to around 90%. Among the major mining pools, as far as I know only Slush Pool and GB Miners are resisting the implementation of SegWit2x. 

[-ck]

Forget about 80% consensus, we are now nearing 90% support, with SegWit2x being supported by 89.6% right now. In just around 24 hours, the support levels have increased from less than 80% to around 90%. Among the major mining pools, as far as I know only Slush Pool and GB Miners are resisting the implementation of SegWit2x. 

GBminers is already signalling segwit so even if they don't explicitly support segwit2x, they'll be fine once the segwit component activates, as will all other segwit signalling pools like mine. Slush is a quick mover and is offering segwit signalling anyway as one of his options and is currently talking about considering signalling segwit2x as well on his feeds so there's no way he'll be left with orphaned blocks come the actual activation time. That only leaves a handful of smaller pools that aren't signalling anything yet. No doubt once segwit is being signalled they'll simply see they have no choice but to come on board.

[allinvain]

I hope Slush starts offering a voting option for SegWit2x soon. At the moment I don't see that option in the voting selection box. I previously voted for USAF but I will change it to SegWit2x once that choice becomes available to me.

[franky1]

this week has proved one thing

89% pool agreement flagging is possible

segwit alone only got 10% in the first week and stalled around the 34% average of 6 months

2mb and segwit getting 89% in a week just goes to show all the chest beating from a particular group refusing to code 2mb was just wasting time. if only they released a 2mbsegwit in summer 2016 alot of drama could have been avoided

[JayJuanGee]

this week has proved one thing

89% pool agreement flagging is possible

segwit alone only got 10% in the first week and stalled around the 34% average of 6 months

2mb and segwit getting 89% in a week just goes to show all the chest beating from a particular group refusing to code 2mb was just wasting time. if only they released a 2mbsegwit in summer 2016 alot of drama could have been avoided

Your last paragraph is misleading.

The 89% is not signaling 2mb first.  They are signaling segwit first, and there is some contingency regarding the 2mb aspect of it, but don't mislead with your attempt to spin what is actually being signaled. 

By the way, a lot of us understand the whole ambiguity of this situation - in that some of the folks within the segwit2x are in fact wanting to argue that 2x is a given, when the only part that seems to be a given is the seg wit portion..

As already stated many times in this thread, the 2x part is contingent upon passage of time, code writing, testing and consensus.... the consensus component of the 2x, that you and some other big block nutjobs seem inclined to do, should not be assumed.

[Paashaas]

Impressive number so far, only 4% left.

I wonder what will happen after we get Segwit this summer and a smoooth HF 3 months 6 months later? War is finally over ore will Jihan push again for bigger blocks?

With Segwit+schnorr+2mb+Lightning+RSK+Mimblewimble+TumbleBit+Factom and more side-chains to come Bitcoin is settled for years to come.

[Viper1]

83.3% support now with NYA in their coinbase so it's reached activation levels. This has been helped by bitclubnetwork joining them, however they've also actually started the real signalling on bit4/1 that activates it in mid-july. The reason is that the admin of that pool is the one that defined BIP91 and wrote the code for it so he's the first to use it as more than just proof of concept.

Well this is good news for a change!

You know, at this point Segwit2x is better than a chain split. Let's hope for the best.

With the segwit component assured now, indeed it is at this point, until we get to the 2x part of it. That's when the next battle begins.

As long as the segwit2x code gets released and has no major bugs, I doubt there will be a battle. People will take the path of least resistance and they're sick of this entire debate.

What I just don't get is that, as far as I've seen, "core" (at least some portion of it), doesn't have an issue with increasing the block size, just "slower". But they had lots of time to do that. I know they're trying to come up with some solution that would not require a hard fork but for some of us, we still view bitcoin as very young and experimental and don't really have a problem with hard forks. In fact, as a developer myself, I think not doing these sorts of things is a mistake as you limit your options and fail to learn any lessons from doing them. Some of the developers talk about doing emergency hard forks if required but if you haven't done some in a controlled manner, then you increase the risk of screwing things up. But I'm just one tiny opinion among many so not like my opinion really matters.