Quote from: Lauda on May 21, 2016, 08:17:54 PM

No. The ETA was April for the code to be released, not merged (!). There's a huge difference here and it seems like users do not know. The code is being thoroughly tested while also some missing pieces are being added. The last time that I was looking into this, the information pointed towards a release in Core 0.12.2 which is the next version.

Yeah, the difference being whether it has some impact on the capacity of the network, or none.

Quote from: Lauda on May 21, 2016, 08:17:54 PM

Quote from: beastmodeBiscuitGravy on May 21, 2016, 07:17:28 PM

Peter Todd's AMA on the chinese forum.

Quote

much of the hashing power has already said they're not going to run segwit until a hard-fork is released

There's a difference between releasing code and merging it. From what I understand, the people that were part of the HK agreement are currently working on a proposal and it should be released in < 2 months.

So Core is planning to author a HF pull req that they have zero intention of merging... I'm sure that'll go over well with miners.

Here's what the guy with 25-30% of the hashrate says:

All this year, by you and others, we were told "Segwit in April!"

Now, you say < 2 months... Is this some kind of twist on the BFL "2 weeks" strategy?