SegWit is part of a set of different proposals that are being worked on to improve scalability . It is neither the only capacity improvement , nor the only scaling improvement in the pipeline . I see very little chance of Core developer consensus for a hard fork blocksize increase before the adoption of SegWit . The reasons have been sufficiently often elaborated for anyone to understand , as long as they are willing to assume it ' s not a conspiracy but said developers actually believe what they say . And with that I mean that the reader will be able to understand the position , even if they end up disagreeing with the sentiment . I see very good chances of further capacity improvements following SegWit , or being provided by other means should SegWit not activate . In the longterm I think it ' s extremely likely that there will also be hard fork blocksize increases , both because the potential negative impact of such an upgrade will be alleviated by changes in SegWit and other improvements , as well as it being a part of the scalability roadmap . However , a hard fork upgrade will become much less likely , if the community remains as torn as it currently is .