A protocol, in the blockchain sense, is the set of rules that every participant's software follows so that thousands of independent computers end up agreeing on one shared ledger. It defines what a valid transaction looks like, how blocks are built and chained, which consensus mechanism decides between competing blocks, how new coins are issued and how nodes exchange data across the network.
The word comes from networking, where protocols such as TCP/IP and HTTP set the rules that let different computers talk. In crypto it is used at several levels: the base protocol of a blockchain such as Bitcoin or Ethereum; second-layer protocols such as the Lightning Network; and application protocols, such as lending or exchange systems built from smart contracts. A protocol is distinct from the software that implements it, from the network of machines running that software, and from any coin the network uses.
Protocol in plain terms
Think of the rules of the road. Nobody owns them and no single car enforces them, yet millions of drivers can share the same streets because they all agree to drive on the same side, stop at red lights and give way in the same situations. Different manufacturers build very different cars, but every car has to follow the same rules.
A blockchain protocol is the rules of the road for a network. The "cars" are the programs people run on their computers. They can be written by different teams in different languages, but if they all follow the same rules they keep agreeing on the same record of who owns what.
What a blockchain protocol specifies
- Data formats. How transactions, blocks and addresses are encoded, and which hash functions and signature schemes are used.
- Validity rules. What makes a transaction or block valid, such as correct signatures, no double spending and limits on block size or gas.
- Consensus. How the network chooses one history, for example proof of work with the most-work chain winning, or proof of stake with validators voting.
- Monetary policy. How and when new coins are created, such as Bitcoin's block reward and its periodic halving.
- Networking. How peers discover each other, relay transactions and share blocks.
Protocol, client and network
A client is a piece of software that implements a protocol. Bitcoin has no separate formal specification: in practice its protocol is defined by the behaviour of Bitcoin Core, the reference client that most nodes run, with proposals recorded as BIPs. Ethereum publishes formal execution-layer and consensus-layer specifications and deliberately supports several independent clients written by different teams, so that a bug in one does not take down the whole network. Changes are proposed as EIPs.
The network is the set of computers actually running clients, and mainnet is the live network where coins have real value, as opposed to a testnet used for trials. A full node checks every rule of the protocol for itself; lighter clients trust others for part of that work.
How protocols change
Because every node enforces the rules independently, changing a protocol means changing the software that thousands of people choose to run. A soft fork tightens the rules so that older nodes still accept new blocks, while a hard fork loosens or rewrites them and requires everyone to upgrade. When a community cannot agree, a hard fork can split one protocol into two, each with its own coin, as happened with Ethereum Classic (ETC) and Bitcoin Cash (BCH).
Who decides is a question of governance. Bitcoin relies on developer review, miner signalling and the choices of node operators. Some networks, such as Tezos and Polkadot, write governance into the protocol through on-chain voting.
Base protocols and application protocols
In everyday crypto speech, "protocol" also names applications built on top of a base chain. A decentralized exchange such as Uniswap or a lending market such as Aave is called a protocol because its rules are fixed in public smart contracts that anyone can use without permission, much as anyone can use a base chain. Together they form the DeFi ecosystem.
The distinction matters for risk. A base protocol's rules can only change through a network-wide upgrade, while an application protocol may be changed by whoever holds its admin keys or wins its token vote, sometimes within days and with little notice to users. Readers of a whitepaper calling a project "a protocol" should check which kind it is, who can change it, and whether it is truly open source and independently audited.