EIP-6963 — multi-wallet provider discovery · PolyArb

EIP-6963 is an Ethereum standard for multi-wallet provider discovery. In practice, it defines a small JavaScript interface that lets web apps detect and enumerate multiple injected wallet providers in the browser so that users can choose which wallet to connect.

Key takeaways

EIP-6963 standardises how websites discover multiple injected wallets in the same browser.
Polymarket uses EIP-6963 to list available wallets (for example MetaMask, Rabby, Bitget) when you connect.
The standard is focused on discovery and identification; signing, transaction submission, and wallet-specific flows still follow each wallet's API (e.g., EIP-1193).

How EIP-6963 works

EIP-6963 exposes a predictable, minimal JavaScript entry point that wallet authors populate when they inject into the page. A website checks that entry point and receives a list of providers with metadata such as name, icon, and the standard interfaces they support. This lets the site present a chooser UI instead of assuming a single injected provider.

Where you'll see it on Polymarket

Polymarket uses EIP-6963 during wallet connection flows to enumerate installed browser wallets. When you click Connect Wallet on Polymarket, the site can show multiple detected options (MetaMask, Rabby, Bitget, OKX, and others that implement the standard) rather than a single default. The actual connection handshake and transaction signing follow each wallet's supported standards (for example EIP-1193), and the Relayer still sponsors gas for transactions.

Limitations and privacy considerations

EIP-6963 is a discovery mechanism only. It does not bypass any consent prompts: wallets must still prompt the user to approve connections and account access. Browser extensions can choose how much metadata to expose; implementations vary. Because discovery reveals which wallet extensions are present, sites should treat that information as potentially sensitive.