Quote from: gmaxwell on May 24, 2016, 05:43:23 PM

Segwit's implementation is done, and has been for some time now. It's in review and testing (both on testnet and the dedicated segnet) right now.

Any person or organization who is interested can help hurry it along by contributing to review and testing.

Bringing it back on topic: Looks like "Bitcoin Classic" has still not integrated CSV support. The CSV BIP is 9 months old now-- and was almost deployed in Core along with 0.12.0, but was given more time to mature first. It's now been out in Core for over a month-- and the BIP9 starting date was sent a bit in the future, in part to give other implementations time to update.

Signaling for it has started now and is already hitting half the hashrate. This triggered "Classic" nodes to start warning that they didn't appear to be consistent with half the hashrate. Did this spur a quick catch up? No: The response of classic's developer was to rip out the notice infrastructure. Ironic: That this is happening after months of "Bitcoin Classic" advocates howling incorrectly about soft-forks silently downgrading the level of validation their nodes do... Doubly ironic: If changes like this were hardforks users of under-maintained projects like "Bitcoin Classic" and Bitcoin XT would be forced by the change to use Bitcoin Core instead of their preferred software.

What is CSV support?