Transaction Rollback: UTXO Management During Reorgs

When a Bitcoin node performs a Chain Reorganization, it must do more than just update a pointer. It must physically "roll back" the state of the global UTXO (Unspent Transaction Output) Set to ensure that the ledger remains consistent.

This guide explores the high-performance database operations that occur during a reorg: DisconnectBlock and ConnectBlock.

---

💾 1. The UTXO Set: The Source of Truth

The UTXO set (stored in chainstate/) is the list of all spendable coins. * When a block is Connected, its inputs are removed from the set, and its outputs are added. * When a block is Disconnected, the process is reversed: its outputs are removed, and its inputs are restored.

---

🔙 2. DisconnectBlock: Undoing History

If a node decides a block is no longer part of the best chain, it calls DisconnectBlock.

1. Removing Outputs: Every UTXO created by this block is deleted from the database.
2. Restoring Inputs: The node looks at the "undo data" (stored in .dat files on disk). This data contains the original scripts and values of the UTXOs that were consumed by this block. The node re-inserts these into the active UTXO set.
3. Result: The ledger state is now exactly as it was before this block existed.

---

📥 3. Mempool Re-insertion

What happens to the transactions from the disconnected block? * Nodes don't want to lose these transactions. * They are moved into the Mempool. * If these transactions are still valid (i.e., they don't conflict with the new winning branch), they will be available for inclusion in the next block.

---

🚀 4. Performance: The "Undo" Data

To make reorgs fast, Bitcoin Core pre-calculates "Undo Data" (CBlockUndo) whenever a block is first connected.

Without this data, a node would have to search the entire blockchain history to find the original values of the consumed inputs just to roll back a single block. By storing the inputs' original states alongside the block, Bitcoin can perform reorgs of hundreds of blocks in just a few seconds.

---

🛡️ 5. Consistency Guarantees

The UTXO set and the Block Tree are always kept in sync. If a node crashes during a reorg, it uses a journaling system to either finish the reorg or roll back to the last known good state upon restart. This ensures that a node never ends up with a "corrupted" view of who owns which coins.