In the context of https://discuss.walletconnect.org/t/qr-code-data-format/14 - I am thinking about a (Wallet) Connect EIP and would love to gather some Ideas/Feedback.

The EIP will be based on 831.

As the ERC-831 prefix I would suggest “connect”

walletconnect is a bit too long imho - the longer the QR code gets the harder it gets to scan.

wc would also be an idea - but it has a bit of a shitty ( ) connotation (maybe we ignore this as it is mostly seen by computers and not humans)

) connotation (maybe we ignore this as it is mostly seen by computers and not humans) connect is a bit broader - and not as opinionated - could be used for other use-cases in the future also

to encode the shared key I would suggest using base64 - which is easy to parse and saves some bytes compared to the hex encoding (also for making the QR code easier to scan) We should be open to updates from symetric to asymetric here also. Especially when these URLs are not only used for QR-Codes but also for Intents (think connecting a native Android dapp to a Wallet on the same device)

So I would suggest the following URL format:

“ethereum” “:” “connect-” sessionID “@” version “?” parameters

as parameters (taken from the current state of the art):

dappName

bridgeURL

symKey

Feedback/Ideas welcome!