WalletConnect (v2.0 protocol)

Most importantly we must migrate Wallets before Dapps can start supporting v2.0. This is because Wallets can support both versions in parallel and route connection requests to corresponding clients using the version number specified in the URI present in the QR Code or Deep Link. Once we reach a signficant quota of Wallets supporting v2.0 then we can start migrating Dapps as they will be able to simply upgrade the major version of their packages on NPM. The v2.0 protocol establishes a remote pairing between two apps and/or devices using a Relay server to relay payloads. These payloads are symmetrically encrypted through a shared key between the two peers. The pairing is initiated by one peer displaying a QR Code or deep link with a standard WalletConnect URI and is established when the counter-party approves this pairing request. Currently the WalletConnect protocol has references implementations written in Typescript for the Client and the Relay Server To quickly setup for your Dapp or Wallet, install and extension To read in more detail about the WalletConnect protocol, go to GitHub Additionally you can also consult the API references for Client and Relay Server.