Sei’s EVM RPC

Sei supports the standard Ethereum JSON-RPC API  endpoints, along with a few which are specific to Sei.

see sei endpoints for details

Standard endpoints

Below is a list of EVM-RPC endpoints provided by default on a Sei RPC node. Your RPC provider may offer slightly different/extended specifications.

All endpoints are in the form of JSON-RPC and share the following request/response structure:

• Request
  • HTTP method: always “GET”.
  • header: accept: application/json
  • header: content-type: application/json
  • body (JSON):
  • id: an arbitrary string identifier.
  • jsonrpc: always “2.0”.
  • method: endpoint name (e.g. “eth_sendRawTransaction”).
  • params: an array that differs from endpoint to endpoint.
• Response
  • body (JSON):
  • id: the same identifier in request.
  • jsonrpc: always “2.0”.
  • result: an object that differs from endpoint to endpoint.

Send Transactions

eth_sendRawTransaction

Sends a signed transaction.

• Parameters:

• Result:

sei_associate

Sends a transaction to establish association between the signer’s Sei address and EVM address on-chain.

• Parameters:

Object Schema:

{
    custom_message: // Any string message
    r: // The R-part of the signature over the Keccak256 hash of the custom message.
    s: // The S-part of the signature over the Keccak256 hash of the custom message.
    v: // The V-part of the signature over the Keccak256 hash of the custom message.
}

Transaction Lookup

eth_getTransactionReceipt

Gets the receipt of a sent transaction

• Parameters:

• Result:

eth_getTransactionByBlockNumberAndIndex

Gets transaction by the block number and the index of the transaction in the block

• Parameters:

• Result:

eth_getTransactionByBlockHashAndIndex

Gets transaction by the block hash and the index of the transaction in the block.

• Parameters:

• Result:

eth_getTransactionByHash

Gets transaction by the transaction hash.

• Parameters:

• Result:

Account Information

eth_getTransactionCount

Gets the number of transactions sent by the account

• Parameters:

• Result:

eth_getBalance

Gets the balance in wei (i.e. 10^-12 usei) of the account

• Parameters:

• Result:

eth_getCode

Gets EVM code stored at the account address

• Parameters:

• Result:

eth_getStorageAt

Gets value at given key of the account

• Parameters:

• Result:

eth_getProof

Gets the IAVL proof (note: not a MPT proof) of the given keys for an account.

• Parameters:

• Result:

Object Schema:

{
    address: // The requested address.
    hexValues: // An array of the hexdecimal form of the values at the given keys.
    storageProof: // An array of storage proofs.
}

Note: The storage proofs in the return object follow this format .

Block Information

eth_getBlockTransactionCountByNumber

Gets the count of EVM transactions (i.e. excluding native Cosmos transactions) in a block by its number.

• Parameters:

• Result:

eth_getBlockTransactionCountByHash

Gets the count of EVM transactions (i.e. excluding native Cosmos transactions) in a block by its hash.

• Parameters:

• Result:

eth_getBlockByHash

Gets the block metadata and/or its EVM transactions by block hash

• Parameters:

• Result:

eth_getBlockByNumber

Gets the block metadata and/or its EVM transactions by block number.

• Parameters:

• Result:

eth_getBlockReceipts

Gets an array of EVM transaction receipt in a block by block number

• Parameters:

• Result:

Blockchain Information

eth_blockNumber

Gets the latest committed block number.

• Parameters:

None

• Result:

eth_chainId

Gets the chain ID.

• Parameters:

None

• Result:

eth_coinbase

Gets the fee collector address.

• Parameters:

None

• Result:

eth_feeHistory

Gets fee history over the requested block range.

• Parameters:

• Result:

eth_gasPrice

Gets the 50% percentile of gas prices in the most recent block.

• Parameters:

None

• Result:

net_version

Gets the version (equal to Chain ID).

• Parameters:

None

• Result:

web3_clientVersion

• Parameters:

None

• Result:

Filter Endpoints

Note that log filters are subject to the following limits by default:

• 10000 logs in one response if block range is open-ended
• 2000 blocks to query over if block range is close-ended

Your RPC provider may tweak these limits.

eth_newFilter

Creates a new log filter for later queries.

• Parameters:

• Result:

eth_newBlockFilter

Creates a new block filter for later queries.

• Parameters:

None

• Result:

eth_getFilterChanges

Gets all the updates since the filter was last queried.

• Parameters:

• Result:

eth_getFilterLogs

Get all logs for a given log filter, including the logs that have been returned before.

• Parameters:

• Result:

eth_getLogs

Get all logs for the given filter criteria.

• Parameters:

• Result:

When using this query, the logIndex is not unique. These queries are also limited to 2000 blocks or 10,000 logs (whichever comes first). If 10,000 logs are returned, it’s recommended to split and re-run the query in smaller chunks to ensure all logs are captured. There are no warnings when these limits are exceeded.

To address these issues, consider using the wrapper function described in our Developer Hub .

eth_uninstallFilter

Removes a created filter.

• Parameters:

• Result:

Simulation Endpoints

eth_estimateGas

Same as the official specification .

eth_call

Same as the official specification .

Debugging Endpoints

debug_traceTransaction

Same as Alchemy .

debug_traceBlockByNumber

Same as Alchemy .

debug_traceBlockByHash

Same as Alchemy .

sei endpoints

Additional custom endpoints exist for specific applications - typically to avoid application-side adjustments to the expected RPC responses.