SOFT / HARDSOURCE-LED COMPARISONS
Bitcoin soft fork vs hard fork: compatibility and consensus
Compare two ways of changing consensus rules and the compatibility consequences for nodes.
A soft fork narrows what is valid, so non-upgraded nodes can still accept upgraded blocks under their older rules. A hard fork permits something older nodes reject and therefore requires coordinated migration to avoid a lasting split.
Restricts the valid set of blocks or transactions.
Expands or otherwise changes validity beyond old rules.
May continue following the chain while not enforcing the new restriction.
Reject blocks using the new rules.
Poor coordination can still cause temporary splits or weaken enforcement.
Insufficient agreement can create permanently incompatible networks.
No BIP or software release forces users to adopt it.
No developer or miner can make old nodes accept incompatible rules.
“Backward compatible” does not mean risk-free or universally agreed. A soft fork changes what upgraded nodes enforce and still requires technical review, deployment strategy and social coordination.