Ethereum Provider API (EIP-1193)
Abbreviation: EIP-1193
Pronunciation: ih-THEER-ee-um pruh-VY-der A-P-I
Also known as: EIP-1193 Provider, Ethereum JavaScript Provider API, EIP-1193
Definition
Ethereum Provider API (EIP-1193) is a minimal JavaScript interface that standardizes how applications request Ethereum RPC methods from a provider and receive connection, account, chain, and message events. The provider is an untrusted transport-facing object from the application’s perspective and is not itself a wallet security boundary or guarantee of user approval.
Overview
Meaning and scope
Ethereum Provider API (EIP-1193) is a minimal JavaScript interface that standardizes how applications request Ethereum RPC methods from a provider and receive connection, account, chain, and message events. The provider is an untrusted transport-facing object from the application’s perspective and is not itself a wallet security boundary or guarantee of user approval.
Mechanism and operation
When nodes disagree during Ethereum Provider API (EIP-1193), the application should preserve both observations and defer irreversible action until the authoritative chain state is clear. A production implementation should validate chain and accounts, handle provider events, request permissions deliberately, treat returned data as untrusted, recover from disconnects, and avoid assuming one wallet-specific extension. Observability for Ethereum Provider API (EIP-1193) should correlate request ID, provider, method, latency, error code, block reference, and transaction state. Useful measures include request rejection rate, disconnects, chain-switch failures, account-change events, unsupported-method errors, and transactions blocked because provider state was stale.
Practical payment example
A browser application asks an injected wallet provider for accounts and a chain change, then handles rejection and disconnect events without assuming a transaction completed.
Operational checks
A Ethereum Provider API (EIP-1193) client should validate network identity, units, encoding, and method semantics before acting on provider data. The Ethereum Provider API (EIP-1193) recovery procedure should distinguish a rejected RPC call from a transaction that was broadcast but not acknowledged. For Ethereum Provider API (EIP-1193), the client should retain chain, method, block or transaction reference, provider response, and the final on-chain observation.
Distinctions and limits
Key risks include wrong-chain transactions, stale account state, malicious or compromised providers, ignored chain-change events, unsupported methods, user rejection, and race conditions during connection changes.
Related reading
Related definitions: Ethereum JSON-RPC, Wallet Adapter.
Example
A browser application asks an injected wallet provider for accounts and a chain change, then handles rejection and disconnect events without assuming a transaction completed.
Comparison
The provider is an untrusted transport-facing object from the application’s perspective and is not itself a wallet security boundary or guarantee of user approval. Key risks include wrong-chain transactions, stale account state, malicious or compromised providers, ignored chain-change events, unsupported methods, user rejection, and race conditions during connection changes.
Key Takeaway
Validate chain and accounts, handle provider events, request permissions deliberately, treat returned data as untrusted, recover from disconnects, and avoid assuming one wallet-specific extension.
Sources
- EIP-1193: Ethereum Provider JavaScript API — Ethereum Improvement Proposals (2026-08-03)
- JSON-RPC API — Ethereum Foundation (2026-08-03)
- EIP-1474: Remote procedure call specification — Ethereum Improvement Proposals (2026-08-03)