1.9 KiB
| eip | title | author | type | category | status | created | discussions-to |
|---|---|---|---|---|---|---|---|
| 1328 | WalletConnect Standard URI Format | ligi <ligi@ligi.de>, Pedro Gomes <pedrouid@protonmail.com> | Standards Track | ERC | Draft | 2018-08-15 | https://ethereum-magicians.org/t/wallet-connect-eip/850 |
Simple Summary
A standard to create WalletConnect URIs to initiate connections between applications and wallets.
Abstract
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 for mobile to mobile as a link.
Specification
Syntax
WalletConnect request URI with the following parameters:
request = "wc" ":" topic [ "@" version ][ "?" parameters ]
topic = STRING
version = 1*DIGIT
parameters = parameter *( "&" parameter )
parameter = key "=" value
key = "bridge" / "key"
value = STRING
Semantics
Required parameters are dependent on the Walletconnect protocol version which currently includes the key, hex string of symmetric key, and bridge, encoded url of the bridge used for establishing the connection.
Example
wc:8a5e5bdc-a0e4-4702-ba63-8f1a5655744f@1?bridge=https%3A%2F%2Fbridge.walletconnect.org&key=41791102999c339c844880b23950704cc43aa840f3739e365323cda4dfa89e7a
Rationale
The need for this ERC stems from the discussion to move away from JSON format used in the alpha version of the WalletConnect protocol which makes for very inneficient parsing of the intent of the QR code, making it easier to create better QR code parsers APIs for Wallets to implement. Also by using a URI instead of a JSON inside the QR-Code the Android Intent system can be leveraged.
References
- WalletConnect Technical Specification, https://docs.walletconnect.org/tech-spec
Copyright
Copyright and related rights waived via CC0.