Errors

The StarKey Ethereum provider follows the standard EIP-1193  provider error codes, plus standard JSON-RPC error codes for malformed or unsupported requests.

Provider error codes

JSON-RPC error codes

Rejection shape

Rejections throw an error object, most commonly in the form:

{ code: 4001, message: 'User rejected the request.' }

try {
  const accounts = await provider.request({ method: 'eth_requestAccounts' })
} catch (err: any) {
  if (err.code === 4001) {
    // user explicitly rejected — show a non-blocking message
  }
}

On-chain failure vs. rejection

A transaction can also fail after being accepted and mined — this is not a JavaScript exception. Check the status field on the transaction receipt ('0x1' success, '0x0' reverted) — see Sending a Transaction. A resolved eth_sendTransaction call only means the transaction was submitted, not that it succeeded.

Recommended handling

async function connectWallet() {
  try {
    const accounts = await provider.request({ method: 'eth_requestAccounts' })
    if (accounts.length === 0) {
      // no accounts available
      return
    }
    // proceed with accounts[0]
  } catch (err: any) {
    if (err.code === 4001) {
      // user rejected — don't retry automatically
    }
  }
}

async function switchToChain(chainId: string) {
  try {
    await provider.request({ method: 'wallet_switchEthereumChain', params: [{ chainId }] })
  } catch (err: any) {
    if (err.code === 4902) {
      // chain unrecognized — call wallet_addEthereumChain first, then retry the switch
    }
  }
}

Notes

• Don’t retry a rejected prompt-based call (eth_requestAccounts, eth_sendTransaction, personal_sign, etc.) automatically in a loop — the rejection is a deliberate user action.
• eth_accounts resolves to [] rather than rejecting when there’s no active connection — check the array length rather than expecting a thrown error.

Related pages

• Establish a Connection
• Sending a Transaction
• Signing Messages
• Network