Why a valid transaction still needs an accepted history
Imagine a ticket counter with two clerks who momentarily receive different instructions. A blockchain has a related coordination problem: checking an individual instruction is not enough when two instructions conflict. Follow a fictional payment through validation, block inclusion and finality without treating all blockchains as the same system.
Separate validity from ordering
In our example, a sender produces two transactions that try to spend the same Bitcoin output. Each may contain a valid signature, but both cannot be accepted in the same history. Nodes need rules about available funds, spending conditions and conflicts, as well as a method for deciding which valid chain to follow.
A transaction is the proposed operation. A block collects operations into a larger record. The blockchain links those records, and consensus supplies the rules participants use to maintain a shared view. Saying a signature is valid answers one question about authorization. It does not settle which conflicting transaction was accepted.
Hashes expose changes; consensus gives them consequences
A cryptographic hash produces a compact digest of data. In Bitcoin, a block header commits to the previous block header and to the transactions through a Merkle root. Editing an earlier recorded transaction changes these commitments. A person cannot quietly change the transaction while preserving the same chain of commitments.
Hashing alone does not decide who may publish the next accepted block. Anyone can calculate a new hash for an edited file. The relevant consensus mechanism and validation rules determine whether other participants accept the resulting history. This is why 'it uses hashes' and 'it is resistant to rewriting' are different claims.
Ask what confirmed means on this network
A newly included Bitcoin transaction has one confirmation in the chain being followed. Further blocks build additional work above it. Temporary competing tips can occur, and a reorganization can replace recent history. Confidence is therefore probabilistic rather than a universal point at which rewriting becomes mathematically impossible.
Ethereum's proof-of-stake system also distinguishes inclusion from finality. Validators vote on checkpoints, and finalization depends on the required supermajority of stake. This is a different mechanism from counting Bitcoin proof-of-work confirmations. A wallet's generic Completed label should not replace the network's own definitions.
For a practical reading habit, identify the chain first, then ask whether a status means broadcast, included, confirmed to a chosen depth or finalized under that chain's rules. Also distinguish a network observation from a service's decision to credit a payment. A provider can apply its own waiting policy without changing the blockchain protocol.
Read three status messages carefully
A learner sees these messages for an imaginary payment. None should be silently substituted for another. The right waiting policy depends on the network, the value at risk and the recipient's requirements; this example sets no universal confirmation threshold.
| Message | What it establishes | What it does not establish |
|---|---|---|
| Broadcast | The app submitted the request. | A block has accepted it. |
| Included | A particular block contains it. | All possible reorganizations are ruled out. |
| Finalized | The chain's finality conditions were met. | The underlying transaction was commercially wise or the recipient trustworthy. |
Check your understanding
Can a block explorer's inclusion proof establish that a seller will deliver a product?
No. A proof about recorded data is narrower than a claim about a person's conduct. It can help establish inclusion in a particular history; it cannot verify the real-world promises attached to that transaction.
Check the primary sources
These references explain the rules behind the lesson. The examples above are fictional teaching scenarios written for this dictionary.