Hard Fork Combinator

The Hard Fork Combinator (HFC) is a mechanism in the node software of Cardano (ADA) that allows the network to adopt new protocol rules while keeping a single, continuous chain. When an upgrade is scheduled, nodes running the new software carry on producing blocks under the old rules until an agreed point, then switch to the new rules automatically. Blocks from every earlier era remain part of the same history, so the chain does not need to be restarted and users do not need to move their funds.

On many blockchains, a hard fork is a change that makes old and new software incompatible, and if some participants refuse to upgrade, the chain can split in two. Cardano still uses the term hard fork for its upgrades, but the combinator is designed to make them smooth, planned events. It was first used in July 2020 to move from the Byron era to the Shelley era and has been used for each major upgrade since.

Imagine a train that needs to move from one type of track to another. Normally, the passengers would have to get off, walk to a new train and carry their luggage with them. The Hard Fork Combinator works like a special section of track that lets the same train roll from the old rails onto the new ones without stopping.

For Cardano users, that means an upgrade happens at a set moment, and nothing visible changes except that new features become available. Wallet balances stay the same, the history stays in one piece and the network keeps running.

Cardano's history is divided into eras, each with its own ledger rules and, in some cases, its own way of producing blocks. The node software contains the rules for every era and a description of how to translate the ledger's state from one era to the next. The combinator ties these together.

1. Developers release node software containing the rules for the new era, and stake pool operators and other node runners install it in advance.
2. An on-chain update, historically signed by holders of special keys and, since the arrival of on-chain governance, approved through Cardano's governance process, sets the time of the transition, counted in epochs.
3. Until that epoch, the upgraded nodes continue applying the old rules.
4. At the boundary, every upgraded node translates the ledger state and begins applying the new rules, while still being able to read and verify blocks from earlier eras.

Node operators who fail to upgrade before the boundary are left following the old rules and stop agreeing with the rest of the network, so upgrades are announced weeks or months ahead, and testnets rehearse each transition first. Because the transition point is agreed in advance and recorded on-chain, nodes can calculate time and slot numbers correctly across eras, even when eras use different slot lengths.

• Shelley, July 2020. Moved Cardano from federated block production by a small set of nodes to proof of stake run by community stake pools, ending the Byron phase.
• Allegra and Mary, December 2020 and March 2021. Added token locking and native tokens.
• Alonzo, September 2021. Enabled Plutus smart contracts, part of the Goguen phase.
• Vasil, September 2022. Improved smart-contract performance and efficiency.
• Chang, September 2024. Began the move to on-chain governance in which ADA holders and elected representatives vote on changes.

• Continuity. The chain keeps one unbroken history, which simplifies record-keeping for wallets, exchanges and blockchain explorers.
• Lower disruption. Planned transitions reduce the risk of downtime and of accidental chain splits.
• Flexibility. The method allows even large changes, such as a new consensus mechanism, to be introduced in stages.

The combinator does not remove the need for coordination. Exchanges, wallets, stake pool operators and application developers must still upgrade their software before the transition, and those who do not can fall out of step with the network. Critics have also noted that, for most of Cardano's history, the keys needed to trigger upgrades were held by a small group of founding entities, which raised questions about centralization; the move to on-chain governance was intended to address this. Other networks have their own approaches to upgrades, such as Ethereum's scheduled forks coordinated by client teams and Bitcoin's preference for backward-compatible soft forks.

• Cardano documentation