EIP-1193 Provider Connector

WHAT IT DOES

EIP-1193 Provider Connector is a diagnostic and testing tool for EIP-1193-compliant providers. It provides a graphical interface for sending JSON-RPC requests to your connected wallet provider and viewing request/response logs. The tool supports all standard EIP-1193 methods including eth_chainId, eth_accounts, net_version, eth_blockNumber, eth_gasPrice, eth_getBalance, personal_sign, eth_sendTransaction, and wallet_switchEthereumChain. It also supports custom method calls with JSON parameters, making it a versatile debugging tool for provider interactions.

HOW TO USE

Install the app through the BotSurf interface. Click Connect to link your wallet via the BGWallet bridge. Select a method from the dropdown—common EIP-1193 methods are pre-configured. Enter parameters as a JSON array (e.g., ["0x742d35...", "latest"] for eth_getBalance). Click "Send Request" to execute the RPC call. The tool logs the request and response in the output panel, with timestamps and status indicators. For methods that require user interaction (like personal_sign or eth_sendTransaction), the tool prompts for required inputs. Use the Custom option to test any RPC method supported by your provider.

EIP-1193 REQUEST ENGINE WITH DYNAMIC PARAMETER HANDLING

The tool uses the provider interface from the BGWallet bridge to send JSON-RPC requests. It accepts method names and parameters as input, then calls provider.send(method, params) following the EIP-1193 specification. The engine includes special handling for common methods: wallet_switchEthereumChain prompts for chain ID, personal_sign prompts for the message and uses the connected account, eth_sendTransaction prompts for recipient and amount, and eth_getBalance uses the connected account if no address is provided. All request parameters are validated as JSON arrays before sending. Responses are formatted and displayed with color-coded status indicators—green for success, red for errors. The output panel maintains a history of all requests and responses with timestamps, making it easy to trace provider interactions.

WHAT IT CANNOT SEE

The tool cannot inject or modify the provider if one is not already present in the environment. It relies entirely on the provider implementing the EIP-1193 standard; if the provider uses a non-standard interface, requests will fail. The tool cannot debug requests that are rejected by the provider without proper error handling—it displays the error message returned by the provider but cannot interpret or recover from provider-side failures. It is limited to methods supported by the underlying provider; if the provider does not support a specific method, the request will fail. The tool cannot handle non-standard provider implementations or extensions that deviate from EIP-1193.

PLEASE NOTE

This tool requires the BotSurf interface and a connected EVM wallet via the BGWallet bridge. It is designed for development and debugging of provider interactions. Always verify transaction details before signing—the tool does not validate transaction parameters. The tool does not store or transmit any data; all state is local to your session. Some methods (personal_sign, eth_sendTransaction) will trigger wallet approval dialogs—always review requests carefully before confirming.