Error messages and codes

When making requests to Phantom in establishing a connection, sending a transaction, or signing a message, Phantom may respond with an error. The following is a list of all possible error codes and their meanings. These error messages are inspired by Ethereum’s EIP-1474 and EIP-1193.

Code	Title	Description
4900	Disconnected	Phantom could not connect to the network.
4100	Unauthorized	The requested method and/or account has not been authorized by the user.
4001	User Rejected Request	The user rejected the request through Phantom.
-32000	Invalid Input	Missing or invalid parameters.
-32002	Requested resource not available	This error occurs when a dapp attempts to submit a new transaction while Phantom’s approval dialog is already open for a previous transaction. Only one approve window can be open at a time. Users should approve or reject their transaction before initiating a new transaction.
-32003	Transaction Rejected	Phantom does not recognize a valid transaction.
-32601	Method Not Found	Phantom does not recognize the method.
-32603	Internal Error	Something went wrong within Phantom.

Typically, these errors will be easily parseable and have both a code and an explanation. For example:

try {
  await window.solana.signMessage();
} catch (err) {
  //  {code: 4100, message: 'The requested method and/or account has not been authorized by the user.'}
}

Send a legacy transaction Get started with EVM networks

⌘I

Overview

Developer tools

Security and validation

Solana features

Testing and debugging

Best practices

Resources

Traditional Provider

Mobile Deep Links