# Can parallel validation side-step the slow block issue?

**URL:** <https://delvingbitcoin.org/t/can-parallel-validation-side-step-the-slow-block-issue/1288>\
**Category:** Protocol Design\
**Created:** [November 28, 2024, 2:01pm UTC](https://delvingbitcoin.org/t/can-parallel-validation-side-step-the-slow-block-issue/1288 "2024-11-28T14:01:03Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![sjors](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/sjors/32/59_2.png) [@sjors](https://delvingbitcoin.org/u/sjors)\
**Post date:** [November 29, 2024, 9:00am UTC](https://delvingbitcoin.org/t/can-parallel-validation-side-step-the-slow-block-issue/1288/8 "2024-11-29T09:00:41Z")

</div>

> [@evoskuil](#):
>
> This seems to assume that all blocks of the same height have the same amount of work.

A reorg more than 6 blocks deep would probably cause more economic harm than a block that takes an hour to validate.

But there’s also the edge of a retarget period to consider. An attacker could set the timestamp of the last block as early as allowed so the difficulty increase is maximal. And then also mine the first block in the new retarget period, and reveal both at the same time. Without manual intervention an honest miner would use wall time and thus their two blocks would have less cumulative difficulty.

> [@evoskuil](#):
>
> If the script is inherently an attack, then why not soft fork it out?

If you know the attack long in advance you can do that. But you might only discover the attack when it happens. That’s what I referred to with “unknown unknowns”.

> [@ajtowns](#):
>
> I think making sure core could still quickly do compact block relay (of missing transactions) while the block was being validating, would improve things a bunch.

So that wouldn’t discourage slow-to-validate blocks, but simply make them less harmful.

---

_[View the full topic](https://delvingbitcoin.org/t/can-parallel-validation-side-step-the-slow-block-issue/1288)._
