Quote from: knightdk on June 25, 2016, 12:18:28 AM

Quote from: AliceGored on June 25, 2016, 12:16:24 AM

Quote from: knightdk on June 25, 2016, 12:05:00 AM

The Hong Kong agreement explicitly states that the hard fork code would be ready within 3 months of Segwit's release, something that has not happened yet. The miners agreed that they would run Segwit in production in the meantime. IT DOES NOT SAY THAT BOTH A HARD FORK AND SEGWIT WOULD BE DELIVERED AT THE SAME TIME.

While your capitalized sentence is correct... it doesn't tell the whole story.

SEGWIT WILL NOT BE ACTIVATED UNTIL/UNLESS HF CODE FOR A FUTURE (mid-late 2017) HF IS RELEASED IN A CORE BINARY.

So... people should not get too excited about the additional capacity generated by moving signatures to witness until the HF code is released by core.

Activated Live Segwit and HF (for 2017 activation) do come together as a package, yet they don't activate together.

Says who? I don't see it in any part of the agreement that segwit and a hard fork will come packaged together. If you are referencing antpool, then they are breaking the agreement as the agreement does not say that segwit and the hard fork will be activated at the same time.

Directly from the agreement:

Quote

We will run a SegWit release in production by the time such a hard-fork is released in a version of Bitcoin Core.

So... not running a Segwit release before the HF version of Core is released is perfectly allowable by the agreement.

All I can see is that Jihan is no fool. He knows that if he activates Segwit without getting Core to comply with their side of the bargain, he will be screwed over. Core will simply attempt to squeeze all additional demand into Lightning Network via artificial scarcity, which will siphon fees away from miners, destroying their business.