Another hard fork of bit coin is scheduled on November 16, 2017, which is target tot increase the size of the block chain.
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.
This new fork migh causes for some safety issues;
One of the main concerns people have is that SegWit2x does not provide replay protection (until recently, when Jeff Garzik, the overseer of development for SegWitx, introduced an opt-in replay protection scheme).
A replay attack works as follows. Following a fork, if Bob sends Alice 10 Bitcoins on the forked chain, an attacker can copy that transaction onto the legacy chain and cause Bob to send 10 Bitcoins on that chain as well. Because SegWit2x does not include replay protection--unless you opt in--the Segwit2x fork leaves users susceptible to a replay attack.
Read more: https://cointelegraph.com/news/bitcoins-upcoming-segwit2x-hard-fork-put-in-laymans-terms
