Skip to content
Blockchain LabBlockchain LabTHE VENTURE STUDIO

LibraryStorage and networks2018Design paperCorpus record

Ethereum Provider JavaScript API

EIP 1193. Fabian Vogelsteller , Ryan Ghods , Victor Maia , Marc Garreau , Erik Marks.

EIP 1193, Ethereum Provider JavaScript API. A common convention in the Ethereum web application ("dapp") ecosystem is for key management software ("wallets") to expose their API via a JavaScript object in the web page.

Status in the source: Final. A reading of the public specification, not a copy of it and not a certification.

Ethereum Provider JavaScript API is worth reading for the rule it actually adds: A common convention in the Ethereum web application ("dapp") ecosystem is for key management software ("wallets") to expose their API via a JavaScript object in the web page.
Evidence
Primary paper
Re-measured
No
Assumptions
3
Records linked
3

Code

Source, repository, and what is actually hosted

  • EIP 1193https://eips.ethereum.org/EIPS/eip-1193
  • The source URL is not a GitHub repository. No code remote is invented.
  • Full text is not mirrored. Public availability is not a licence to copy the file onto this site.
  • Add to a reading list

01 Claim ledger

What the paper is allowed to say

Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.

  1. Claim 01 · Paper model

    The rule

    A common convention in the Ethereum web application ("dapp") ecosystem is for key management software ("wallets") to expose their API via a JavaScript object in the web page.

  2. Claim 02 · Paper model

    What was already failing

    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.

  3. Claim 03 · Paper model

    What the number does not mean

    The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

  4. Claim 04 · Paper model

    What a builder should be able to point at

    An implementation either constrains API, RPC, MUST or it is a different design.

02 Three cuts

Observation, model, falsifier

A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.

  1. 01 The rule

    Observation

    What the study says

    A common convention in the Ethereum web application ("dapp") ecosystem is for key management software ("wallets") to expose their API via a JavaScript object in the web page.

    Model

    What has to hold

    The object that has to change is API, RPC, MUST. A neighbouring document with a similar name is not this one.

    Falsifier

    What would retire it

    Which message does Ethereum Provider JavaScript API add, and which old peer must still be answered?

  2. 02 What was already failing

    Observation

    What the study says

    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.

    Model

    What has to hold

    The object that has to change is API, RPC, MUST. A neighbouring document with a similar name is not this one.

    Falsifier

    What would retire it

    What does a node do when the short form fails and the full object is required?

  3. 03 What the number does not mean

    Observation

    What the study says

    The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

    Model

    What has to hold

    You are implementing EIP 1193 at the status the text itself states: Final.

    Falsifier

    What would retire it

    Which names are normative: API, RPC, MUST?

  4. 04 What a builder should be able to point at

    Observation

    What the study says

    An implementation either constrains API, RPC, MUST or it is a different design.

    Model

    What has to hold

    You are implementing EIP 1193 at the status the text itself states: Final.

    Falsifier

    What would retire it

    Which message does Ethereum Provider JavaScript API add, and which old peer must still be answered?

03 Sequence

One action, as an operating tape

  1. 01Open EIP 1193 and read the status line before the examples.
  2. 02Write down the rule in one sentence. A fair version of that sentence is: A common convention in the Ethereum web application ("dapp") ecosystem is for key management software ("wallets") to expose their API via a JavaScript object in the web page.
  3. 03Name the object that changes: API, RPC, MUST.
  4. 04Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

04 Load-bearing

The argument, and where a pitch drops it

  1. What the text is allowed to settle

    The cut

    Ethereum Improvement Proposal 1193 can settle the shape of Ethereum Provider JavaScript API. It cannot settle whether a later client, a later fork, or a later wallet still does this.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A peer protocol is not a consensus rule. A peer can disconnect. A block is still valid or not on its own.

  2. What this page will not pretend

    The cut

    There is no benchmark, no adoption number, and no claim that the mechanism is safe outside the assumptions written in the source.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

05 Register

What has to be true

  • Model · Not re-measured

    You are implementing EIP 1193 at the status the text itself states: Final.

  • Model · Not re-measured

    The object that has to change is API, RPC, MUST. A neighbouring document with a similar name is not this one.

  • Network · Not re-measured

    Measurements of delay in one year do not travel with the specification.

06 Divergence

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.

A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.

07 Pre-mortem

What to check before you use the idea

  4. 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.

08 Anatomy

The paper, in the order a builder needs

The problem it 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

  • A common convention in the Ethereum web application ("dapp") ecosystem is for key management software ("wallets") to expose their API via a JavaScript object in the web page.
  • Historically, Provider implementations have exhibited conflicting interfaces and behaviors between wallets.
  • This EIP formalizes an Ethereum Provider API to promote wallet interoperability.

How the mechanism is specified

  • Taken from the specification, the next constraint is: Historically, Provider implementations have exhibited conflicting interfaces and behaviors between wallets.
  • Locate API, RPC, MUST in EIP 1193 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 the desk still reads it

Use EIP 1193 when a pitch says 'Ethereum Provider JavaScript API' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.

09 Lexicon

Terms, opened into the record

EIP 1193
The public text titled Ethereum Provider JavaScript API.
Final
The document's own label for how finished the text is. It is not a market fact.

10 Repository

Every linked record on this page

Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.

Protocols

This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.

Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.