# L1/L2 Reorg Behaviour

**URL:** <https://community.starknet.io/t/l1-l2-reorg-behaviour/114431>\
**Category:** 🙏 Help and Support\
**Created:** [August 9, 2024, 5:58am UTC](https://community.starknet.io/t/l1-l2-reorg-behaviour/114431 "2024-08-09T05:58:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![caljoshba](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/caljoshba/32/85209_2.png) [@caljoshba](https://community.starknet.io/u/caljoshba)\
**Post date:** [August 9, 2024, 5:58am UTC](https://community.starknet.io/t/l1-l2-reorg-behaviour/114431/1 "2024-08-09T05:58:48Z")

</div>

Just doing some digging into chain reorgs and was hoping you might have some details on how Starknet handles them:

- In the instance of an L2 reorg (very unlikely but it did happen in back in April 2024):

- In the instance of an L1 reorg:

Any help here or pointing in the right direction would be very useful.
