Uncle Blocks

Uncle blocks — also called ommers — are a concept from proof-of-work chains: valid blocks that were mined at nearly the same time as the canonical block but lost the race to be included in the main chain. On those chains uncles are recorded and partially rewarded to compensate miners and protect security. The Avalanche C-Chain does not have uncle blocks at all. It does not use proof-of-work mining; it reaches agreement through Snowman consensus, which finalizes a single accepted block at each height in roughly one to two seconds. Because there is no mining race and no competing-but-valid blocks left behind, the C-Chain never produces ommers, and the uncle-related fields exist only as inert remnants of Ethereum's JSON-RPC shape. The rest of this guide explains what that means in practice and what the uncle RPC methods return on chainId 43114.

Understanding Uncle Blocks

• What would cause an uncle — and why it cannot here: on a PoW chain an uncle appears when two miners find valid blocks at the same height before one propagates network-wide. The Avalanche C-Chain has no such race: Snowman consensus repeatedly samples validators and converges on one accepted block per height, so no competing valid block is ever orphaned into an uncle.
• Why the concept exists elsewhere but serves no role here: uncles were designed to offset propagation latency and reward miners who lost a close race, strengthening PoW security. Snowman achieves security and fast finality through validator sampling rather than mining work, so there is no latency race to compensate and the incentive uncles provide is simply not needed.
• Reward structure: there is no uncle reward on the C-Chain because there are no uncles. Transaction fees on Avalanche are paid in AVAX with the base fee burned, and there is no PoW-style block-plus-uncle reward scheme.
• Effect on security and chain quality: the absence of uncles is not a weakness — it reflects that the C-Chain has at most one valid block per height, finalized in ~1-2s. There is no orphan rate to track as a chain-quality metric the way you would on a PoW network.

Implementation Examples

1// Get uncle count for a block
2const getUncleCount = async (blockNumber) => {
3  const block = await web3.eth.getBlock(blockNumber);
4  return block.uncles.length;
5};
6 
7// Get uncle block by index
8const getUncleBlock = async (blockNumber, uncleIndex) => {
9  return await web3.eth.getUncle(blockNumber, uncleIndex);
10};
11 
12// Monitor uncle rates
13const calculateUncleRate = async (blockRange = 100) => {
14  const latestBlock = await web3.eth.getBlockNumber();
15  const startBlock = latestBlock - blockRange;
16 
17  let totalUncles = 0;
18  for (let i = startBlock; i <= latestBlock; i++) {
19    const uncleCount = await getUncleCount(i);
20    totalUncles += uncleCount;
21  }
22 
23  return totalUncles / blockRange;
24};

Best Practices

• Confirmation safety: uncles play no part in C-Chain confirmation safety because none exist. Base your finality decisions on Snowman finality and confirmation depth (see the Block Confirmations guide), not on any uncle-inclusion reasoning carried over from PoW chains.
• "Uncle rate": the healthy uncle rate on Avalanche is exactly zero, and it stays zero by design. eth_getUncleCountByBlockNumber and eth_getUncleCountByBlockHash return "0x0" for every C-Chain block, so there is no rate to monitor — code that computes an uncle rate will simply average zeros.
• Mining profitability: the C-Chain is not mined and pays no uncle rewards, so uncle income never enters any profitability model here. Validator economics on Avalanche are based on staking AVAX and earning transaction tips, not PoW block-and-uncle rewards.
• Parsing block data: treat the uncles array as always empty and never dereference an uncle by index. eth_getUncleByBlockNumberAndIndex and eth_getUncleByBlockHashAndIndex return null on the C-Chain, so guard any inherited Ethereum code against that null instead of assuming an uncle object will be present.

See also

• eth_getUncleByBlockHashAndIndex - Retrieve uncle block by hash and index
• eth_getUncleByBlockNumberAndIndex - Retrieve uncle block by number and index
• Working with Blocks - General block handling