Exodus info on BIP91 - SegWit2X - BIP148 and hard forks

Last updated: Monday, July 24th, 2017

Exodus is designed to allow you to control your own wealth. With this control comes the ability to make decisions for yourself and also have 100% control over your funds - this includes Bitcoin and all assets.

This control gives the power to you to decide how you want to proceed in the case of a fork. No matter the decision of Exodus, the software is designed to give you total ownership and full autonomy over all assets, unlike a hosted wallet or exchange.

You have full control of your private keys. With these private keys, you control both sets of coins if or when a fork takes place.

Since Exodus is a light-wallet that depends upon information from other services like ShapeShift, BlockCypher, and Bitpay Insight Exodus is dependent upon their decisions.

Since the last update to this article, the New York Agreement (NYA) or SegWit2x (BIP91), has been locked-in and blocks not signaling readiness for SegWit are being rejected by the miners since Sunday, July 23rd. Complete SegWit activation on the network is projected to happen sometime in the last half of August 2017.

The New York Agreement locked-in with almost 90% of hashing power and because it activates SegWit, it essentially nullifies BIP148 and the UASF. This means if everything moves according to the agreement, there will not be a chain split.

Here are dates that you need to be aware of:

2017 July 23 18:00 GMT onward — Every block signals BIP141 (SegWit)

2017 July 27 or thereabouts — New Difficulty Adjustment Period Begins (2016 blocks). Every block will be signaling for Segwit.

2017 August 1 00:00 GMT — BIP148 starts, but does nothing since every block is signaling BIP141 due to BIP91.

2017 August 10 or thereabouts — Difficulty Adjustment Period closes with >95% signaling and BIP141 locks-in.

2017 August 23 or thereabouts — Difficulty Adjustment Period closes and BIP141 (SegWit) is active.

2017 November 18 or thereabouts — 2x Hard Fork (scheduled)

Depending upon the events leading up to any of the above dates, Exodus may disable Bitcoin trading in the exchange. You will always be able to send/receive Bitcoin, but if the events become even more contentious, it's advised you don't send Bitcoin during this period.

Exodus will continue to keep you up-to-date via the new built-in status notification system found versions 1.29.0 and above.

Again, we want to stress, the power of Exodus is that it gives you the user 100% control over all assets. No matter what Exodus as a company decides to do in a fork situation, you always have and maintain full control and management of your assets.

References:

https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki

https://www.weusecoins.com/uasf-guide/

https://bitcoinmagazine.com/articles/bitcoin-beginners-guide-surviving-bip-148-uasf/

https://medium.com/@jimmysong/uasf-segwit2x-scenarios-and-timelines-1a540336c4be

https://medium.com/@wintercooled/explaining-segwit2x-and-bip-148-uasf-compatibility-39ca7e3296ed

https://bitcoinmagazine.com/articles/countdown-segwit-these-are-dates-keep-eye/

Still need help? Contact Us Contact Us