About Reorg
What is Reorg?
Kaspa’s DAG structure may experience reorganizations (Reorgs):
A single Transaction can appear in multiple blocks.
The chain block dictates which of the transactions in the merged blocks are accepted.
It‘s possible that transactions, which were declared as accepted, are not accepted anymore. This happens only in the most recent blocks around the DAG tips.
How does Kasplex L2 handle Reorg?
Kasplex L2 handle Reorg via:
Monitoring: Layer 2 Nodes track reorgs in real-time.
State Rollback: If Layer 1 undergoes a reorganization, Layer 2 reverts all transactions within the reorganization range to ensure that the Layer 2 transaction order always aligns with Layer 1.
Before Reorg:
Selected Chain: A→B→C
Layer 2 Transaction Order: ( tx1, tx2, tx3, tx4, tx5, tx6 )
After Reorg:
( E ) is added, pointing to ( C ) and ( D ). Suppose ( D )’s subtree has higher blue work than ( C )’s, so ( E ) selects ( D ) as its parent.
Selected Chain: A→B→D→E
Layer 2 Transaction Order: ( tx1, tx2, tx3, tx4, tx7, tx8, tx5, tx6, tx9, tx10 )
Last updated