WalletConnect v1.0 Shutdown: What to Expect and How to Prepare

The WalletConnect v1.0 shutdown is nearly upon us!

With just one week to go, here is how you can expect the June 28 shutdown to roll out. First, let’s go over what exactly this shutdown means and the immediate impact it will have.

What exactly does “shutdown” mean?

WalletConnect v1.0 will be shut down at 2pm UTC on June 28. At this very moment, the DNS records for “bridge.walletconnect.org” will be switched to no longer point to our hosted WalletConnect v1.0 bridge servers.

When this happens, the WalletConnect v1.0 bridge servers will go offline. Do not expect a brown-out or a gradual shutdown; the shutdown will take effect immediately.

What happens once the WalletConnect v1.0 shutdown occurs?

The immediate impact on your wallet or app, as well as on your end users, will depend on where you are in your migration to WalletConnect v2.0.

• WalletConnect v1.0 wallets and apps: Users will encounter connectivity issues right away. Please migrate to WalletConnect v2.0 to avoid this scenario.
• WalletConnect v2.0 wallets and apps: Users will be able to connect, but this also depends on the quality of your WalletConnect v2.0 integration. Please make sure that you run through our integration checklist for wallets and apps to test your implementation.
• WalletConnect v2.0 mobile apps: If your users have upgraded to the version with WalletConnect v2.0 support, they will be able to connect. If they have not upgraded to the version with WalletConnect v2.0 support, they will encounter connectivity issues right away. We recommend that you remind your users repeatedly this week to update.

We are actively working with wallets and apps to minimize the impact of this shutdown on the end user experience. However, we recognize that downtime cannot be entirely avoided and believe that a tightly coordinated path forward can help reduce the potential for outages, as well as uncertainty.

We therefore propose the following plan of action to wallets and apps to ensure minimal disruption for end users.

The WalletConnect v1.0 shutdown rollout

June 27 at 7am UTC: Apps switch to WalletConnect v2.0

We recommend that apps switch to WalletConnect v2.0 in their production deployments a full day ahead of the official shutdown to test connectivity and allow for last-minute fixes.

Who will be impacted?

Since wallets are able to support both WalletConnect v1.0 and v2.0 in parallel, users of wallets that already support WalletConnect v2.0 will be able to connect using WalletConnect v2.0 from then onward. Please note, however, that users of mobile app wallets must have updated to the version with WalletConnect v2.0 support.

Users of wallets that only support WalletConnect v1.0 and users of outdated mobile apps will be unable to connect from this time onward.

June 28 at 2pm UTC: WalletConnect v1.0 bridge servers go offline

At this moment, WalletConnect v1.0 will cease to operate.

Who will be impacted?

The users of wallets and apps that still only support WalletConnect v1.0 will encounter connectivity issues immediately. Users of mobile apps who have yet to update to the version with WalletConnect v2.0 support will also be affected.

Shutdown-related user outreach

If you do not expect to support WalletConnect v2.0 at the time of shutdown, we advise you to communicate potential downtime for WalletConnect usage after 2pm UTC on June 28 to your users immediately.

If you have a mobile app, we advise you to notify your users to update to the version with WalletConnect v2.0 support as soon as possible. If they do not update to the correct version, they will not be able to use WalletConnect after 2pm UTC on June 28.

If you already support WalletConnect v2.0, please take this time to verify the quality of your WalletConnect v2.0 integration as this may impact connectivity. For wallets, please refer to this checklist in our migration docs. For apps, please test with as wide a range of wallets as possible to ensure that your implementation is correct.

WalletConnect technical support

The WalletConnect team will be on stand-by and is expediting all WalletConnect v2.0-related queries and fixes. If you have encountered a technical issue and require support, please raise it on the WalletConnect GitHub immediately. We will acknowledge receipt of your issue as soon as possible.

As a service commitment to our users, WalletConnect also ensures 24/7 on-call support for WalletConnect v2.0 services. For a real-time look at the health of WalletConnect v2.0 services, you can head to WalletConnect Status. Furthermore, you can also subscribe to receive updates on scheduled downtime and issues as they arise.

To keep up with our announcements, join our Discord and follow us on Twitter. If you are a wallet or an app that is interested in integrating WalletConnect, head over to our website and explore our documentation.