WalletConnect URI Format

The five-minute read

One action, walked through

1. Open ERC 1328 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: This standard defines how the data to connect some application and a wallet can be encoded with a URI.
3. Name the object that changes: URI, STRING.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing ERC 1328 at the status the text itself states: Final.
• The object that has to change is URI, STRING. A neighbouring document with a similar name is not this one.
• This page is not a guide to moving funds.

What happened after the paper

The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What is the timeout in WalletConnect URI Format, and who can take the coins when it expires?
• Which chain, if any, adjudicates the dispute?
• Which fields are committed: URI, STRING?

Terms

ERC 1328

The public text titled WalletConnect URI Format.

Final

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

A payment or a bridge that cannot name the dispute path is a custodial promise with extra steps.

What the design proposes

• 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.
• ### Syntax WalletConnect request URI with the following parameters: request = "wc" ":" topic [ "@" version ][ "?" parameters ] topic = STRING version = 1DIGIT parameters = parameter ( "&" parameter ) parameter = key "=" value key = STRING value = STRING ### Semantics 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 ### Example # 1.0 wc:8a5e5bdc-a0e4-4702-ba63-8f1a5655744f@1?bridge=https%3A%2F%2Fbridge.walletconnect.org&key=41791102999c339c844880b23950704cc43aa840f3739e365323cda4dfa89e7a # 2.0 wc:7f6e504bfad60b485450578e05678ed3e8e8c4751d3c6160be17160d63ec90f9@2?relay-protocol=irn&symKey=587d5484ce2a2a6ee3ba1962fdd7e8588e06200c46823bd18fbd67def96ad303&methods=[wc_sessionPropose],[wc_authRequest,wc_authBatchRequest]"&expiryTimestamp=1705934757.

How the mechanism is specified

• Taken from the specification, the next constraint is: This URI can then be shown either as a QR code or as a link.
• Locate URI, STRING in ERC 1328 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• A specification of a hash lock is not a working route, and not a guarantee the counterparty is online.
• This page is not a guide to moving funds.
• The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use ERC 1328 when a pitch says 'WalletConnect URI Format' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.