# Blockpipelining

**URL:** <https://forum.algorand.co/t/blockpipelining/7823>\
**Category:** Uncategorized\
**Created:** [September 11, 2022, 9:47pm UTC](https://forum.algorand.co/t/blockpipelining/7823 "2022-09-11T21:47:48Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Titi](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/titi/32/3632_2.png) [@Titi](https://forum.algorand.co/u/Titi)\
**Post date:** [September 11, 2022, 9:47pm UTC](https://forum.algorand.co/t/blockpipelining/7823/1 "2022-09-11T21:47:48Z")

</div>

How does algorand prevent validators in one round from being selected in and almost concurrent round of certification i.e the pipelined block. Because this might validators in round r can be selected for round r +1 and might create conflicts. Furthermore Unlike other chains who have their validators already selected, they can schedule and forward to the validator of the next round, validators don’t know who the next leader might be to forward to.

---

_[View the full topic](https://forum.algorand.co/t/blockpipelining/7823)._