Protocol Upgrade
governance · blockchain
A coordinated change to the rules, messages, or policies implemented by network software.
A protocol upgrade changes how compatible software validates, produces, relays, or interprets network data. Consensus upgrades require participants to coordinate around rules that determine valid blocks or state transitions.
A soft fork tightens validity rules so upgraded nodes reject some blocks older nodes would accept. A hard fork allows or requires behavior older nodes reject. Either approach can split the network if economically relevant participants enforce incompatible histories.
Miner signaling, validator votes, node releases, user choices, exchange policy, and application support can all matter, but no single metric universally defines "community approval." A sound review asks which rules activate, who enforces them, how failure is detected, and whether independent implementations agree.
Related terms
Fork
→A fork is a blockchain divergence caused by competing blocks, software changes, or incompatible consensus rules.
blockchain · event
Soft Fork
→A backward-compatible protocol change where upgraded nodes enforce stricter rules without splitting the network.
governance · consensus
Node
→Software that participates in a peer-to-peer network by validating, serving, relaying, or requesting blockchain data.
network · blockchain
Protocol
→The formal set of rules that define how participants in a network communicate and reach consensus.
blockchain · networking
Consensus
→The process by which blockchain participants agree on valid transactions, blocks, and ledger history.
security · blockchain