Multi Injected Provider Discovery

The five-minute read

One action, walked through

1. Open EIP 6963 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: An alternative discovery mechanism to window.ethereum for EIP-1193 providers which supports discovering multiple injected Wallet Providers in a web page using Javascript's window events.
3. Name the object that changes: Multi Injected Provider Discovery.
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 EIP 6963 at the status the text itself states: Final.
• The object that has to change is Multi Injected Provider Discovery. A neighbouring document with a similar name is not this one.
• Measurements of delay in one year do not travel with the specification.

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

• Which message does Multi Injected Provider Discovery add, and which old peer must still be answered?
• What does a node do when the short form fails and the full object is required?
• Which names are normative: Multi Injected Provider Discovery?

Terms

EIP 6963

The public text titled Multi Injected Provider Discovery.

Final

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

The problem the paper names

A node that cannot fetch, filter, or relay the data it is supposed to validate is not a peer of the network the paper describes.

What the design proposes

• An alternative discovery mechanism to window.ethereum for EIP-1193 providers which supports discovering multiple injected Wallet Providers in a web page using Javascript's window events.
• Currently, Wallet Provider that offer browser extensions must inject their Ethereum providers (EIP-1193) into the same window object window.ethereum; however, this creates conflicts for users that may install more than one browser extension.
• Browser extensions are loaded in the web page in an unpredictable and unstable order, resulting in a race condition where the user does not have control over which Wallet Provider is selected to expose the Ethereum interface under the window.ethereum object.

How the mechanism is specified

• Taken from the specification, the next constraint is: Currently, Wallet Provider that offer browser extensions must inject their Ethereum providers (EIP-1193) into the same window object window.ethereum; however, this creates conflicts for users that may install more than one browser extension.
• Locate Multi Injected Provider Discovery in EIP 6963 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 peer protocol is not a consensus rule. A peer can disconnect. A block is still valid or not on its own.
• Measurements of delay in one year do not travel with the specification.
• 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 EIP 6963 when a pitch says 'Multi Injected Provider Discovery' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.