Quote from: JayJuanGee on July 21, 2017, 07:53:46 AM

Quote from: Variogam on July 21, 2017, 07:48:24 AM

Quote from: -ck on July 21, 2017, 06:28:15 AM

There is nothing stopping all the miners from simply dropping the btc1 fork code and just using core after segwit is activated, and not all pools actually signed the agreement.

Pools were not the only ones signing the NYA agreement. Hard to believe every NYA signer going to toss his reputation by not honouring the agreement. And we are talking about the most important Bitcoin companies here...
https://medium.com/@DCGco/bitcoin-scaling-agreement-at-consensus-2017-133521fe9a77

Most bigger pools/companies use custom software, so the core vs btc1 code is not relevant here, what only matter is being compatible with Bitcoin, like accept up to 2M base blocks in about three months.

You make no sense...

No one is going to agree to be a lemming and to walk over a cliff just because all the lemmings in front of them are going over the cliff, right?

If the agreement is not clear and does not provide a clear and unambiguous mechanism, then how the fuck they going to be on the same page regarding what it is that they are agreeing to do, exactly?

There's no code to follow or review, so there are way too many ambiguities in the supposed agreement. And it is not even bad faith to have a different way of interpreting what it requires.

Another shill regurgitating the Core script without even reading the actual agreement.

The same bullshit ck- is pushing here.

I don't have time for you idiots today so I'll just quote from reddit.

Quote

https://www.reddit.com/r/btc/comments/6ohyyk/979_of_the_blocks_mined_today_supports_segwit2x/dki5f6m/

[]JustSomeBadAdvice 3 points 7 hours ago

> Are you sure? All I see is voting for BIP91 and BIP91 doesn't say anything about a 2 MB HF.

BIP91 is segwit2x. Core is trying to pretend that they are different, but the email that proposed BIP91 puts a lie to that claim in the very first line of it. BIP91 was a compatibility kluge, nothing else.

The btc1 client forks to bigger blocks 3 months after segwit locks in, regardless of anything else. Meaning those who are running that software at that time will be forking. The fork can't be rolled back unless it is completely abandoned, as it requires a >1mb block at fork time.

Now that BIP91 has locked in, segwit signaling will be forced in the next few days and segwit will activate shortly after that. 3 months from that moment, BTC1 and the big blockers will fork; Core's only challenge is whether or not their legacy chain will be viable or completely stuck due to lack of miners.

We're free of core now.

> And why do we need to rush Segwit? If we have three months to wait for 2 MB we would have had three months to wait for Segwit. There is no sane reason to do Segwit before the hardfork.

Segwit would have timed out before the hardfork upgrade could be safely rolled out to the users that needed the upgrade. That was the reason. BIP148 added more urgency, but it wasn't necessary. If anything the speed at which segwit2x just activated, before the final release client had even dropped, should be an indication of how badly miners want Bitcoin to Actually Scale instead of be Bitcoin Jr.

> So, to summarize, the NYA did, what the "Dragon's den" wanted.

It did not. Read the emails, comments, posts, and github comments they've been posting nonstop trying to make the project look bad. The project's charter explicitly called out that signatories must be willing to provide resources including developer support and testing/logistics support. They knew full well that they were going to have to do this without any assistance from Core whatsoever.

We're free man.

The bottom line is Core may be DCG/AXA's dog, but if the dog got rabies and started biting everyone, including the boss's friends, the owner have to put it down.

DCG have more than one dog. Core is replaceable.