Get Status

Breaking changes ahead: v1 is coming (hot fix 0.13.2)

Breaking changes ahead: v1 is coming (hot fix 0.13.2)

The countdown is on. In less than one month, our security audit kicks off in preparation for Status v1.

Today we're releasing hot fix 0.13.2 for iOS* to ensure that word gets out about our forthcoming v1 breaking changes. The hot fix includes several banners designed explicitly to notify you of what's in this blog post.

While I'd love to get into all the exciting new features shipping with our first public release—management of multiple Ethereum keys in one Status account, big gains in performance, and stickers for chat, to name a few—we have some business to attend to first.

Status v1 will be incompatible with beta versions of the app.

Here's what all users need to know ahead of v1, coming later this year:

  1. You will have to delete your previous version of Status before installing version 1. We've made some changes to the storage of app state, removing the database we used previously. If you don't install v1 from scratch, your app will be slower to load and you may experience unanticipated conflicts or bugs.
  2. When you install v1, you will get a brand new chat key. The chat key—previously contact code—is your connection to other users in Status chat.
  3. You can recover an existing Ethereum address—or 'wallet'—by using your seed phrase. When you onboard, you will have the option to access an existing Ethereum address, but you need your 12 word seed phrase to do so. Regardless, you will receive a new chat key.
  4. If you don't have your seed phrase, you need to move your funds to a secure wallet before installing v1. If you switch to v1 without your seed phrase, you will be unable to access your funds in Status on that device. Any ENS names purchased with that Ethereum address will also be unrecoverable! Note: If you created your Status wallet before March of 2018 and are still using beta, it's best that you remove your funds entirely as well.
  5. Beta versions will not communicate with v1. Protocol improvements mean that the two clients can not chat with each other, so to stay fresh, we recommend that all users install v1 when it becomes available.

In beta versions of Status, your Ethereum key is connected to your chat key. This is not ideal from a privacy perspective. Imagine that anyone in your Telegram groups could view the balance of your checking account.

With our new account structure, we decouple the chat key (used for communicating) from the Ethereum address (used for transacting). Now, you will only share your Ethereum address with other users if you do so explicitly by sending it to them or offering your QR code.

You can create more Ethereum addresses and manage them all from the same Status wallet; only your 'default' address is shared with contacts, so you have additional control over your exposure.

This change not only affords you greater privacy, it also enables you to protect your accounts with a Keycard if you so choose*. Keycard is our contactless hardwallet. When you use Keycard to encrypt your keys, you are ensuring that no transactions can be made from your account unless the hardwallet is used—in this case, by tapping it against your device to authorize each transaction.

So, to reiterate:

In preparation for v1, we ask that you back up your 12 word seed phrase for any Status accounts with funds in them, or with ENS names registered to them.
If you have lost your seed phrase, please transfer your funds to another secure account—the sooner the better!
When v1 becomes available, we'll remind you again to delete your previous version of the app and install v1 from scratch.

We do NOT intend to make significant breaking changes like this in the future. It was only after much consideration, debate and community input that we achieved consensus to go ahead with the major infrastructural upgrades that now require your action, and which make v1 a clean slate upon which we can build a better product.

As always, we welcome any questions or feedback in #Status.

Note: A previous version of this post stated that adding a user to your contacts in v1 will share your Ethereum address with that user. That is incorrect; only if you manually share your v1 Ethereum address will it be exposed.

* There will be no hot fix for Android for the reasons explained in this post.
* Keycard will be available for Android users only, beginning with v1.

Ready to Update to iOS v0.13.2?

Within TestFlight, make sure you see version 0.13.2 and tap ‘INSTALL.’

If you don’t currently have Status installed, access via TestFlight here: