From d020db2410b3ea2fc075783f2e3d190bcab4c3d5 Mon Sep 17 00:00:00 2001 From: Pedro Gomes Date: Thu, 16 Aug 2018 21:29:55 +0100 Subject: [PATCH 1/3] eip-1328 --- EIPS/eip-1328.md | 49 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 49 insertions(+) create mode 100644 EIPS/eip-1328.md diff --git a/EIPS/eip-1328.md b/EIPS/eip-1328.md new file mode 100644 index 0000000000000..52f3084a7eb22 --- /dev/null +++ b/EIPS/eip-1328.md @@ -0,0 +1,49 @@ +--- +eip: 1328 +title: WalletConnect Standard URI Format +authors: ligi , Pedro Gomes +type: Standards Track +category: ERC +status: WIP +created: 2018-08-15 +discussions-to: https://ethereum-magicians.org/t/wallet-connect-eip/850 +requires: 831 +--- + +## Simple Summary + +A standard way of creating WalletConnect URIs for establishing connections between wallets and dapps + +## Abstract + +Sesion data in QR codes for initiating a connection between a wallet and dapp using the WalletConnect standard require a standardized URI format for effictively parsing the intenet. This ERC is expandable between versions of the standard and also mobile-to-mobile deep links. + +## Specification + +### Syntax + +Function call URIs follow the ERC-831 URI format, with the following parameters: + + request = "ethereum" ":" [ "wc-" ]sessionID [ "@" version ][ "?" parameters ] + sessionID = STRING + version = 1*DIGIT + parameters = parameter *( "&" parameter ) + parameter = key "=" value + key = "name" / "bridge" / "symKey" + value = NUMBER / STRING + +### Semantics + +Required parameters are dependent on the WalletConnect standard version which currently is specified to only include mobile-to-desktop connection sessions which only require `name` which describes the dapp name, `bridge` which includes the bridge URL, `symKey` which includes the symmetric key in base64. + +## Rationale + +The need for this ERC stems from the discussion to move away from JSON format used in current beta version of the WalletConnect standard 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 for other compatible EIPs using the ERC-831 URI format for Ethereum. + +## References + +1. ERC-831, http://eips.ethereum.org/EIPS/eip-831 + +## Copyright + +Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). From 0e832526ac89bc662cea541d989621cb10b6a30a Mon Sep 17 00:00:00 2001 From: Pedro Gomes Date: Sat, 18 Aug 2018 10:56:41 +0100 Subject: [PATCH 2/3] draft --- EIPS/eip-1328.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-1328.md b/EIPS/eip-1328.md index 52f3084a7eb22..e280e7a485a65 100644 --- a/EIPS/eip-1328.md +++ b/EIPS/eip-1328.md @@ -4,7 +4,7 @@ title: WalletConnect Standard URI Format authors: ligi , Pedro Gomes type: Standards Track category: ERC -status: WIP +status: Draft created: 2018-08-15 discussions-to: https://ethereum-magicians.org/t/wallet-connect-eip/850 requires: 831 From a621c5640a1b4ff7e5a41675c6938ee3e4589164 Mon Sep 17 00:00:00 2001 From: Pedro Gomes Date: Wed, 22 Aug 2018 13:43:50 +0100 Subject: [PATCH 3/3] review changes --- EIPS/eip-1328.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/EIPS/eip-1328.md b/EIPS/eip-1328.md index e280e7a485a65..90fb6d21a5c0d 100644 --- a/EIPS/eip-1328.md +++ b/EIPS/eip-1328.md @@ -12,11 +12,11 @@ requires: 831 ## Simple Summary -A standard way of creating WalletConnect URIs for establishing connections between wallets and dapps +A standard to create WalletConnect URIs for establishing connections between wallets and applications. ## Abstract -Sesion data in QR codes for initiating a connection between a wallet and dapp using the WalletConnect standard require a standardized URI format for effictively parsing the intenet. This ERC is expandable between versions of the standard and also mobile-to-mobile deep links. +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 @@ -38,7 +38,7 @@ Required parameters are dependent on the WalletConnect standard version which cu ## Rationale -The need for this ERC stems from the discussion to move away from JSON format used in current beta version of the WalletConnect standard 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 for other compatible EIPs using the ERC-831 URI format for Ethereum. +The need for this ERC stems from the discussion to move away from JSON format used in current beta version of the WalletConnect standard 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 for other compatible EIPs using the ERC-831 URI format for Ethereum. Also by using a URI instead of a JSON inside the QR-Code the Android Intent system can be leveraged. ## References