Our application UX is potentially sensitive to the uncle/ommer rate. I have been trying to understand the impact of PoS change on this phenomenon, but have not found any recent information that appears definitive, and old discussions are conflicting:

What is the expected mechanics of uncle/ommer block creation and rate following the merge?


I read the referenced comment on the block content.

It is indeed clear that uncles will no longer exist as block entries. Still, it does appear that, from the user perspective, a substantially similar phenomenon can occur if a validator fails to propose within their slot or other failure modes cause disagreements among parts of the network and subsequent reorgs.

In any case, the following spells out how uncles arise under PoS, and why it should be orders of magnitude rarer: https://www.reddit.com/r/ethdev/comments/vgzeae/what_is_the_uncleommer_block_mechanics_under_pos/

1 Answer 1


The short answer is that there will be no uncles anymore.

For the more detailed answer explaining how it will affect the block content I refer you to my previous answer concerning the merge here : block header structure change under proof of stake.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.