ERC-831 Ethereum URI Format Standard (URI Format for Ethereum)
Stagnant · Accounts & wallets · created 2018-01-15
This proposal defines a common URI format. Embedding an "ethereum:" URI in a QR code, link, or email lets the user's usual wallet app open immediately when they click or scan it.
Why it is needed
Conveying Ethereum-related requests through QR codes, web page links, emails, or chat messages requires a format that different applications can understand in common. Without a unified URI format, each use case such as payment requests ends up using its own scheme, and users clicking a link or scanning a QR code have no way of knowing which wallet app should do what. The earlier EIP-67 first defined an Ethereum URI, but it was designed specifically for payments and was structurally hard to extend to other use cases. Solving this requires a more loosely coupled common URI framework that is not tied to a specific use case while remaining compatible with EIP-67.
In depth
Full URI grammar
A request takes the form request = "eth" ["ereum"] ":" [prefix "-"] payload. The scheme can be either "eth:" or "ethereum:", followed by an optional prefix and hyphen, and a required payload. Both prefix and payload are defined as STRING.
Role of the prefix and the omission rule
The prefix indicates what this URI is for and is optional. If the prefix is omitted, it is treated as defaulting to "pay-" for backward compatibility with EIP-67. When the prefix is omitted, the payload must start with 0x, and conversely a prefix must not start with 0x. This lets you immediately tell whether a prefix is present just by checking whether it starts with 0x.
Payload and per-use-case rules
The payload is required, and its content depends on the prefix. Defining the detailed structure of the payload is outside the scope of this document and is instead the role of the individual ERC covering each use case. For example, the payload structure used with the pay- prefix is defined in EIP-681.
Relationship with EIP-67
This proposal emerged while refining EIP-681. EIP-67 first defined the Ethereum URI, but it was designed specifically for payments, and this ERC aimed to create a simpler container not tied to a specific use case. As long as the prefix feature is not used, existing EIP-67 URIs remain valid and readable.
Reason for the open-ended prefix design
The open-ended prefix structure was chosen to keep accommodating new use cases that emerge in the future. The intent is not to lock the entire "ethereum:" scheme to the limited set of use cases that existed when this document was written. Instead, it was accepted that EIP-67 parsers could break only in cases where the prefix feature is used.
Proposal status
This ERC is in Stagnant status, a proposal that is no longer actively discussed and has stalled. Since it has not been finalized as a standard, actual implementation and adoption may vary by wallet and service.