![Segwit2x-new-code-release.jpg](https://steemitimages.com/DQmQJCByGa96Abe6NnuDPdaDGz5rnxA5i1JQSvgGsDx7PHG/Segwit2x-new-code-release.jpg)


Not everybody was happy with just implementing SegWit, and preferred to increase the maximum size of Bitcoin’s blocks as well. This would give the network some more room for growth while lightning network was being deployed. Bitcoin’s Core developers do not want to increase the block size, primarily because that involves a hard fork, which is potentially dangerous. A hard fork happens when computers running new versions of the software are no longer compatible with computers that run the old (legacy) version. If done incorrectly, this can cause really bad things to happen.

On May 23rd, 2017, the Digital Currency Group published the New York Agreement (NYA). The New York Agreement was signed by a large number of Bitcoin companies and by miners representing over 80% of Bitcoin’s hashpower. The signatories of the agreement accepted a compromise called SegWit2x. This plan would call for the near-immediate activation of SegWit, and would follow that with a hard fork in November to double the block size.

Segwit2x Will Stay on Bitcoin Core Version 14 Through the November Fork Due to Version 15 Bugs


The developer also explains the BTC1 source code is a fork of the Core software, and the team tracks that repository’s updates. Additionally, Garzik gives a link to the production release branch and explains that specific Segwit2x code is based on Core version 0.14.x, and the developer release is associated with version 0.15.x.

“I’ve been paying close attention to the Bitcoin Core 0.15.x rollout,” explains Garzik. Based on instability and bugs that upstream Bitcoin Core project is seeing – ie. Core’s bugs, not ours – Segwit2x will stay on Bitcoin Core 0.14.x. through the November fork.”