A hard fork represents a significant alteration in a blockchain network's protocol. Such a change is not backward compatible, implying that every network participant must upgrade their software to the latest version to remain an active participant within the network. Upon the execution of the hard forks, all network participants are expected to update their nodes to the newest version. Failure to do so will render them incapable of participating in the validation and verification of new transactions on the blockchain.
It's helpful to visualize a hard fork as a split in the blockchain's course. Prior to the hard fork, all participants traveled along the same trajectory. However, following the hard fork, this single path divides into two distinct paths. One continues under the old rules, while the other adheres to the newly implemented rules.
However, hard forks are typically preplanned and generally agreed upon by the community in advance, in which case the old blockchain typically ceases to exist. All members upgrade their systems, and the outdated version becomes obsolete.
This section itemizes the hard forks of Conflux and provides a description of the associated modifications.
In the Hydra hardfork (v2.0) Conflux will introduce serveral big upgrades through 8 CIPs (Conflux improvement proposal).
Conflux-Rust v2.1.0 is a small hardfork upgrade. In this upgrade 5 new CIPs will be activate, and also some improvement about storage and RPC.
| Key Information | Details |