🔵 Base
eth_getUncleByBlockHashAndIndex

⚠️ eth_getUncleByBlockHashAndIndex - Base Chain

Important Note

The eth_getUncleByBlockHashAndIndex method is not applicable on Base chain. This method will always return null when called on Base.

️⚠️

Base is a Layer 2 (L2) rollup that does not have uncle blocks. Uncle blocks are specific to Proof of Work (PoW) blockchains like Ethereum mainnet before The Merge, where multiple miners could find valid blocks at approximately the same time.

Why Uncle Blocks Don't Exist on Base

Base uses a different consensus mechanism than the original Ethereum Proof of Work:

  1. Base is a rollup: It batches transactions and publishes them to Ethereum mainnet
  2. No mining competition: There's a single sequencer producing blocks, not multiple miners competing
  3. Inherited security: Base inherits its security from Ethereum, rather than having its own mining network

Therefore, the concept of "uncle blocks" doesn't apply to Base chain.

Parameters

While this method isn't functional on Base, these are the parameters it would typically accept:

ParameterDescription
blockHashThe hash of a block
uncleIndexThe position of the uncle in the block's uncle list (hex)

Response

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": null
}

The response will always be null when called on Base chain.

Alternative Methods

Instead of looking for uncle blocks on Base, you may want to use these methods:

Example Request

  • HTTPS POST Request with a JSON RPC call in the body
  • Replace YOUR-API-KEY with the API key from your Chainnodes.org Dashboard
  • You can use a different supported network by replacing base-mainnet
curl https://base-mainnet.chainnodes.org/YOUR-API-KEY \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_getUncleByBlockHashAndIndex","params": ["0x54751c3cb4f7c95b249ab5ed702a708a6782cc937b1d399f25be4b40d9e0f5d4","0x0"],"id":1}'

Example Response

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": null
}