About WalletConnect V2
TokenPocket, as a decentralized wallet, serves as the primary gateway for crypto users to access the vast blockchain ecosystem. DApps (Decentralized Applications) act as catalysts, driving the growth and prosperity of cryptocurrencies. In this context, WalletConnect plays a pivotal role by establishing seamless connections between decentralized wallets and DApps.
What is WalletConnect?
WalletConnect is an open-source protocol dedicated to enabling the connection between crypto wallets and decentralized applications (DApps). It allows users to securely connect to DApps by scanning QR codes with their mobile wallets, without the need to upload wallet keys. This provides a convenient and secure user experience for blockchain applications.
The WalletConnect protocol is developed and maintained by the WalletConnect community, which consists of over 70 global companies and individuals. The protocol’s code is entirely open source on GitHub, ensuring transparency throughout the development process. This enhances the security and trustworthiness of the protocol.
What are the differences between VI and V2?
Decentralized Message Relaying
V1 protocol was initially designed to be used on the Whisper network, while it was more important at the time that the protocol was adopted by as many applications as possible so it was implemented that messages be relayed through a centralized server that mimics a pub-sub architecture like Whisper. Now that WalletConnect is much better positioned to adopt a decentralized message relay network as its primary transport for messages.
WalletConnect V2 uses Waku 2.0 by default to relay messages in a decentralized manner which removes the previous requirement of two clients being connected to the same server. In fact, WalletConnect V2 does not even require clients to be connected to a server at all since Waku 2.0 is built on top of libp2p, and therefore it can relay messages client-side like a browser and propagate them through the network to reach the peer client.
Multi-Chain Support
Another drawback of V1 is that, just like another current tooling in this space, support for an application to connect to multiple chains simultaneously was missing. It has become normalized that a connection between an app and a wallet assumes a single active chain.
Simultaneous chain connections were long considered in CAIPs discussions prior to WalletConnect V2 development which is defined both by the account addresses to be suffixed by the chain identifier and also by the JSON-RPC standard to invoke requests with a target chain.
Thus, this new feature would enable a future where apps can interface with wallets on multiple chains without requiring any synchronization to switch context either automatically by the wallet or the user themselves.
Improved Session Management
Be dramatically improved in two areas: explicit expiries and request history.
Explicit expiries simply mean that session proposals include a Time to Live (TTL) which is by default set to one week but can be changed as the expiry is calculated on the wallet side after settlement which is then communicated back to the app. This eliminates the current scenario where either apps or wallets manage sessions indefinitely due to one of the parties not communicating its termination. Additionally, a mechanism to ping is also included to evaluate if the peer client is currently online or not. While WalletConnect does not require parties to be online for the whole duration of the session, it’s useful for apps to understand whether the wallet is immediately available to sign a request.
Request history is probably the only feature that was never asked before because the V1 delegated this responsibility to the server. For the V2 protocol, all clients will have a record of all the JSON-RPC requests made during a session and also which ones have already been responded. This enables a client to protect itself from receiving duplicate requests and track pending requests that need to be responded to.
These improvements ensure that sessions can be promptly terminated and their states can be deleted, enhancing the manageability and efficiency of sessions.
Pairing & Session Separation
A major bottleneck was that WalletConnect V1 required a user to scan a QR Code or use a deep link every time they wanted to connect to a new application from their wallet.
Fortunately, this is not the case with the V2 protocol where pairing and session have been decoupled. The app using the WalletConnect protocol will cache previously paired wallets which it can use to send new session proposals without pairing all over again. This relationship of a pairing will of course not be shared between wallets but it can be shared between applications in the same browser through an iframe.
Tips, The main contents are provided by WalletConnect, click and know more basic knowledge.
How to use WalletConnect V2 on TokenPocket?
- To access DApp on a PC Browser, click WalletConnect, open TokenPocket, and click the scan icon on the upper right corner to scan the QR Code. You can see that the V2 has added support for switching addresses and public chains.
2. You can view the currently supported default network (EVM chains) for the DApp. In the address selection, you have the flexibility to set available addresses from different public chains for seamless switching. There is no need to log out and reconnect; you can directly switch and use different chains effortlessly.
3. After connecting your wallet, you can view the statue. Back to the Assets page, click the pop-up icon to check the connect statue.
4. WalletConnect V2 supports connecting to multiple DApps, allowing for flexible switching between them. When performing on-chain operations within a DApp, the wallet will automatically prompt a detailed interface in which you can review the information and confirm the transaction. After confirming, you will need to enter your password to sign the transaction. (For public chains like BTC, ETH, etc., you can adjust the gas fee as needed.)
TokenPocket now fully supports WalletConnect V2. If you encounter any issues during usage, please contact us at service@tokenpocket.pro. Your feedback is highly valued as it will help us improve and optimize compatibility with WalletConnect V2. Thank you for your support of TokenPocket.
About TokenPocket
TokenPocket is the world’s leading multi-chain self-custodial wallet, which supports mainstream public chains including BTC, ETH, BSC, TRON, Polygon, Solana, HECO, Klaytn, Avalanche, OKC, HSC, Fantom, Polkadot, Kusama, etc. The trinity of TokenPocket mobile wallet, chrome extension wallet, and hardware wallet has been formally formed. The Secret Recovery Phrase and Private Key are stored in the user’s own device and the user can fully control his own crypto assets. TokenPocket has provided reliable services for over 20 million users around the world. The number of monthly active users exceeds 3.5 million and the users are located in more than 200 countries around the world.
| Website | Twitter |Telegram | Extension |Hardware Wallet|Fans Forum |
