This standard defines how the data to connect some application and a wallet can be encoded with a URI. This URI can then be shown either as a QR code or as a link.



WalletConnect request URI with the following parameters:

request       = "wc" ":" topic [ "@" version ][ "?" parameters ]
topic         = STRING
version       = 1*DIGIT
parameters    = parameter *( "&" parameter )
parameter     = key "=" value
key           = STRING
value         = STRING


Required parameters are dependent on the WalletConnect protocol version:

For WalletConnect v1.0 protocol (version=1) the parameters are:

  • key - symmetric key used for encryption
  • bridge - url of the bridge server for relaying messages

For WalletConnect v2.0 protocol (version=2) the parameters are:

  • symKey - symmetric key used for encrypting messages over relay
  • methods - jsonrpc methods supported for pairing topic
  • relay-protocol - transport protocol for relaying messages
  • relay-data - (optional) transport data for relaying messages
  • expiryTimestamp - (optional) unix epoch in seconds when pairing expires


# 1.0

# 2.0


This proposal moves away from the JSON format used in the alpha version of the WalletConnect protocol because it suffered from very inefficient parsing of the intent of the QR code, thereby making it easier to create better QR code parsers APIs for wallets to implement. Also by using a URI instead of JSON inside the QR-Code the Android Intent system can be leveraged.

Backwards Compatibility

Versioning is required as part of the syntax for this URI specification to allow the WalletConnect protocol to evolve and allow backwards-compatibility whenever a new version is introduced.

Security Considerations

URIs should be shared between user devices or applications and no sensitive data is shared within the URI that could compromise the communication or would allow control of the user’s private keys.

Copyright and related rights waived via CC0.