Quote from: Qartada on April 20, 2017, 03:25:06 PM

They explicitly state that they won't run SegWit without a blocksize increase because they never expect Core to actually cave in and do a hard fork so they can get away with taking a moral

Proof?

Quote from: Qartada on April 20, 2017, 03:25:06 PM

Obviously no blocksize related hardfork proposal has support from Core devs, otherwise they wouldn't have written SegWit, they'd have written a blocksize related hardfork proposal.

Segwit and blocksize increase aren't mutually exclusive. In Feb 2016 they signed this:

Quote from: Hong Kong 2016 agreement

We understand that SegWit continues to be developed actively as a soft-fork and is likely to proceed towards release over the next two months, as originally scheduled.

We will continue to work with the entire Bitcoin protocol development community to develop, in public, a safe hard-fork based on the improvements in SegWit. The Bitcoin Core contributors present at the Bitcoin Roundtable will have an implementation of such a hard-fork available as a recommendation to Bitcoin Core within three months after the release of SegWit.

This hard-fork is expected to include features which are currently being discussed within technical communities, including an increase in the non-witness data to be around 2 MB, with the total size no more than 4 MB, and will only be adopted with broad support across the entire Bitcoin community.

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

We will only run Bitcoin Core-compatible consensus systems, eventually containing both SegWit and the hard-fork, in production, for the foreseeable future.

We are committed to scaling technologies which use block space more efficiently, such as Schnorr multisig.