Would someone please be so kind as to explain how a block with a 43 second prop time wins a height battle???

  • Block #: 6777986
  • Pool ID: 2cf87fadec7130c7e41910492073ae4dbe65ca462c1fdc3d2a56d015

Perhaps I could use a refresher on shallow forks/rollbacks, but this just doesn't add up in my head... as far as I understand, the only way this is possible is if the higher-slot leader does not "receive" the previous block, and posts their own block in place of the most recent one. For such a large prop time, this seems like a massive arbitrage opportunity for the higher slot leader.

What can be done about, or is there a way to minimize, this?

enter image description here

2 Answers 2


Here's a very good article about slot battles, but in short, prop time is not a factor in winning or losing...


  • Nice article! I see why prop time alone not a factor in winning/losing a height battle. What I am more concerned about is the idea that such a high prop time may be indicative of some sort of malicious MEV. If I understood the article correctly, the stake pool in question here did not receive IOGP's block for a whole 40 seconds before pushing their block to the network. Does this mean that any SPO can orphan any block that comes before theirs just by not accepting it before publishing their own?
    – zhekson
    Commented Jan 20, 2022 at 17:47
  • 1
    OP and @nomad0 Great question and answer. The answer would be even better if it followed the guidelines at: cardano.stackexchange.com/help/referencing
    – gRebel
    Commented Jan 22, 2022 at 23:23

Here is interesting discussion about height and slot battles, what I had.


Here some more details from @BEAVR:

I should clarify and probably update my blog post regarding Height Battles.

From my experience, height battles are actually won by whichever block was received first. The slot number has no effect. We discovered that relays accept which block comes first when looking into this problem:



Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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