Skip to main content

Ethereum endpoint support

Etherlink nodes use Geth to provide access to both standard Ethereum RPC endpoints and Geth-specific RPC endpoints. These tables list these endpoints and whether Etherlink supports them:

Standard Ethereum endpoints

For information about these endpoints, see JSON-RPC API and the Ethereum JSON-RPC Specification in the Ethereum documentation.

EndpointSupportedNotes
debug_getBadBlocksNo
debug_getRawBlockNo
debug_getRawHeaderNo
debug_getRawReceiptsNo
debug_getRawTransactionNo
engine_exchangeCapabilitiesNo
engine_exchangeTransitionConfigurationV1No
engine_forkchoiceUpdatedV1No
engine_forkchoiceUpdatedV2No
engine_forkchoiceUpdatedV3No
engine_getPayloadBodiesByHashV1No
engine_getPayloadBodiesByHashV2No
engine_getPayloadBodiesByRangeV1No
engine_getPayloadBodiesByRangeV2No
engine_getPayloadV1No
engine_getPayloadV2No
engine_getPayloadV3No
engine_getPayloadV4No
engine_newPayloadV1No
engine_newPayloadV2No
engine_newPayloadV3No
engine_newPayloadV4No
eth_accountsYesThis endpoint always returns an empty list because the Etherlink EVM node does not manage any addresses
eth_blobBaseFeeNo
eth_blockNumberYes
eth_callYesEtherlink nodes use the standard Ethereum version of the eth_call endpoint instead of the Geth version; Etherlink does not support the state override set parameter
eth_chainIdYes
eth_coinbaseYes
eth_createAccessListNo
eth_estimateGasYes
eth_estimateGasYes
eth_feeHistoryYes
eth_gasPriceYes
eth_getBalanceYes
eth_getBlockByHashYes
eth_getBlockByNumberYes
eth_getBlockReceiptsYes
eth_getBlockTransactionCountByHashYes
eth_getBlockTransactionCountByNumberYes
eth_getCodeYes
eth_getFilterChangesNo
eth_getFilterLogsNo
eth_getLogsYes
eth_getProofNo
eth_getStorageAtYes
eth_getTransactionByBlockHashAndIndexYes
eth_getTransactionByBlockNumberAndIndexYes
eth_getTransactionByHashYes
eth_getTransactionCountYes
eth_getTransactionReceiptYes
eth_getUncleByBlockHashAndIndexYes
eth_getUncleByBlockNumberAndIndexYes
eth_getUncleCountByBlockHashYes
eth_getUncleCountByBlockNumberYes
eth_hashrateNo
eth_maxPriorityFeePerGasYes
eth_miningNo
eth_newBlockFilterNo
eth_newFilterNo
eth_newPendingTransactionFilterNo
eth_protocolVersionNo
eth_sendRawTransactionYes
eth_sendTransactionNo
eth_signNo
eth_signTransactionNo
eth_syncingNo
eth_uninstallFilterNo
net_listeningNo
net_peerCountNo
net_versionYes
web3_clientVersionYes
web3_sha3Yes

Geth-specific endpoints

This table shows the Geth endpoints that Etherlink nodes support. All other Geth endpoints are not supported. For information about these endpoints, see the Geth documentation at https://geth.ethereum.org/docs.

EndpointSupportedNotes
debug_traceTransactionPartiallySupported on Ghostnet but not Mainnet
eth_callNoEtherlink nodes use the standard Ethereum version of the eth_call endpoint instead of the Geth version
txpool_contentPartiallyReturns the transaction pool on Ghostnet but always returns an empty pool on Mainnet

ethers.js SDK methods

The Etherlink EVM node supports these ethers.js methods:

MethodSupportedNotes
provider.getBlockYes
provider.getTransactionReceiptYes
provider.getBlockNumberYes
provider.getBalanceYes
signer.sendTransactionYes

Additional information

Comments
Whitelisting Fireblocks IP addressesNot Supported
Native Token Decimals18
Fee StructurePost London (Fee market is not implemented yet, but the rollup supports EIP-1559 transaction types)