T-1 Month! Last Call to Migrate Before the WalletConnect v1.0 Shutdown

We have officially entered the final stretch of the WalletConnect v2.0 migration!

With just one month to go, we are calling on all wallets and dapps to make their final preparations before WalletConnect v1.0 is shut down forever at 2pm UTC on June 28. It is essential for everyone to complete their migration ASAP in order to prevent any disruption for your users when the shutdown finally comes into effect.

We’re nearly there, everyone — let’s do this!

Wallets

If you’re a wallet and not yet live on WalletConnect v2.0, please act now. Wallets can support both WalletConnect v1.0 and v2.0 simultaneously, so why wait until the last minute to migrate? Many of your fellow wallets already support WalletConnect v2.0, and the list is growing by the day.

Haven’t started your migration yet?

Direct yourself to our docs immediately. You will find guidance for the following platforms: iOS, Android, React Native, browser-based, Unity, and Flutter.

Working on your WalletConnect v2.0 integration — or already done?

Please verify the items below, even if you are already on WalletConnect v2.0. This is to ensure that your implementation is up-to-date and provides a truly frictionless experience for your users.

Web3Wallet SDK version

Make sure you are using the latest version of the Web3Wallet SDK to ensure optimal compatibility with dapps.

• Web3Wallet SDK for JS (example wallet here)
• Web3Wallet SDK for Swift (example wallet here)
• Web3Wallet SDK for Kotlin (example wallet here)

Chain switching

WalletConnect v2.0 makes chain switching possible, but implementing it requires the utilization of a namespace, a standardized object defined by the Chain Agnostic Improvement Proposals (CAIP) that ensures a common industry standard for chain-agnostic development. Here’s a quick overview of namespaces and WalletConnect’s implementation of it. You can also read more about it in each language’s docs and test out your wallet’s chain switching experience with the corresponding example dapp.

• JS docs and JS example dapp
• Kotlin docs and Kotlin example dapp
• Swift docs and Swift example dapp

Account switching

Users may seek to sign a message from a different account than the one initially proposed in the session. To ensure that account switching works flawlessly for your users, explore this in greater detail for your language.

• JS docs
• Kotlin docs
• Swift docs

The WalletConnect Auth API

This plays a critical role when dapps offer off-chain signatures, and you can read more here. To dive in further, check out our docs for each language below and then test your implementation with the corresponding example dapp.

• JS docs and JS example dapp
• Kotlin docs and Kotlin example dapp
• Swift docs and Swift example dapp

Automatic redirect

When a wallet signs and authorizes an account, the wallet should immediately redirect to the dapp. This test assesses the user flow and verifies the wallet’s ability to redirect to the dapp after a user signs or sends a transaction.

• JS example dapp
• Kotlin docs and Kotlin example dapp
• Swift docs

Sign notifications

This is to ensure that users receive a push notification for any pending dapp request, even when their wallet isn’t open. It’s an extremely important feature that enhances web3 UX significantly, so we recommend taking the time to check your implementation with the following resources.

• JS example dapp
• Kotlin docs and Kotlin example dapp
• Swift docs and Swift example dapp

Ready to test your WalletConnect v2.0 integration before you go live?

To ensure a seamless launch, it’s important to test your integration, ideally with as many dapps as possible. Many dapps have already set up staging sites, which allow you to test connecting on WalletConnect v2.0 today. They include Aave, Polygon Bridge, Uniswap, and more.

For a list of dapps that you can currently test with, head to this page in our docs, which we are actively maintaining.

Already on WalletConnect v2.0 and have a mobile app?

First, make sure to update your listing on our Explorer or create one if you haven’t already by clicking on the “Add” button.

Also, don’t forget to let your users know to update to the latest version of your app immediately (just like Uniswap did). This will help ensure that they are using the version with WalletConnect v2.0 support come shutdown.

Dapps

One of the complexities of this migration is that dapps can only support a single version of WalletConnect at a given time. The good news, however, is that switching between different versions of WalletConnect may be as easy as changing a single line of code or updating a package, depending on your implementation of WalletConnect.

While the switch may be straightforward, we do not recommend that you leave this all to the last minute. It is absolutely vital for you to test your WalletConnect v2.0 integration first, to cover as many scenarios as possible. Many dapps have already set up staging branches in order to do so, and we strongly encourage you to follow in their footsteps so that you can test with the many wallets that are already on WalletConnect v2.0.

Haven’t started your migration yet?

Direct yourself to our docs immediately.

If you are using Web3Modal v1.0, you have three potential paths:

• Upgrade the WalletConnect ethereum-provider to the latest version on NPM here.
• Upgrade to WalletConnectModal: This is a lightweight modal to add into your existing workflows.
• Upgrade to Web3Modal: This is the feature-rich modal with wagmi, has WalletConnect, extension wallets, connectors, chain switching, the account modal, and more.

If you are not using Web3Modal, we also have migration paths for other providers and libraries including web3-provider, ethereum-provider, react-native-dapp, web3-onboard, solana-labs/wallet-adapter, Dynamic, ConnectKit, and Web3-React.

We are actively maintaining this list and will share updates as they occur with you on Twitter.

Looking to migrate, but still blocked?

We are aware that certain libraries have yet to upgrade to WalletConnect v2.0 and are working closely with them to ensure that this happens as soon as possible.

If you are unsure of your library’s status, please reach out to us by creating a new discussion on GitHub.

We have also created a WalletConnect v2.0 Migration Lab, which demonstrates how to use the libraries that use WalletConnect v2.0, such as Blocknative’s Web3-Onboard and ConnectKit.

Moreover, we will share updates on Twitter and in our docs as they happen, as well as next steps for you.

Working on your WalletConnect v2.0 integration and unsure of next steps?

Before going live, you need to test. We generally recommend dedicating at least two weeks to testing (which means setting up your staging site by June 14 at the latest). Of course, the more time for testing, the better.

You can already test with the many wallets already live on WalletConnect v2.0. We will also continue to announce on Twitter when new wallets go live on WalletConnect v2.0.

Once you’re ready, then it’s time to flip the switch! Don’t forget to update or add your dapp’s Explorer listing and let your users know. We’re eagerly waiting for you on the other side.

Resource Recap

• Migration overview docs
• Wallet migration docs and Web3Wallet SDK docs
• Dapp migration docs and Web3Modal SDK docs
• WalletConnect GitHub for technical support
• Key differences between WalletConnect v1.0 and. v2.0

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.