The Bitcoin network is a peer-to-peer system in which participants exchange transactions and blocks under Bitcoin’s protocol rules. Users create transactions, nodes check and relay them, and miners assemble candidate blocks; nodes validate those blocks before accepting them into the transaction history. A wallet or hosted service may interact with the network, but it is not the network itself. source source

What the Bitcoin network is

The Bitcoin network is the connected set of participants and software that exchange Bitcoin data and apply rules to transactions and blocks. Its peer-to-peer protocol lets full nodes exchange transactions and blocks and synchronize validated chain data. This describes the network’s communication and validation process, not the separate tools or services that people may use to access it. source

Bitcoin transactions use digital signatures to authorize transfers through a chain of signed ownership records. That transaction mechanism is part of how the network processes activity; it should not be confused with the wallet interface that helps a user prepare and authorize a transaction. source

Ethereum documentation describes smart contracts as programs with code and data at network addresses that users can invoke by submitting transactions. Bitcoin’s network should not be assumed to have that specific Ethereum smart-contract model: the focus here is Bitcoin’s transaction and block exchange and the rules nodes apply to them. source

The participants that keep the network operating

Users and wallets initiate transactions. Bitcoin transactions use digital signatures to authorize transfers, but a signature alone is not the full payment process: the network also applies transaction-validation and double-spend-prevention rules. Wallets and hosted services may submit activity to the network, but their interfaces and service operations are distinct from Bitcoin’s peer-to-peer protocol. source source

Full nodes exchange transactions and blocks with peers and synchronize validated chain data. A node generally relays a received transaction after independently checking that it satisfies applicable validity and relay-policy rules. Node policy can differ, so a transaction that is valid under consensus rules is not necessarily accepted into every node’s local mempool. A mempool is a node’s local holding area for transactions that have not yet been included in a valid block on the accepted chain. source source

Miners assemble candidate blocks and prepare block-header work for hashing hardware. Their role is to propose blocks through the proof-of-work process; node validation remains a separate check. A miner’s proposal does not, by itself, establish that the block follows the rules a node enforces. source

These roles describe different parts of the process. Users initiate transactions, nodes check and exchange network data, and miners propose blocks. A wallet, exchange, or other hosted provider may interact with Bitcoin, but that does not make its user-facing service identical to a node or the network protocol. source

How a Bitcoin transaction moves through the network

A basic transaction path can be understood in stages:

  1. A transaction is authorized. Bitcoin uses digital signatures to authorize transfers through signed ownership records. The signature is one part of the transaction system; the network’s validation rules also matter. source
  2. The transaction is shared with peers. Full nodes use Bitcoin’s peer-to-peer protocol to exchange transactions and blocks. A receiving node generally checks a transaction against applicable validity and relay-policy rules before relaying it. source source
  3. A node may hold the transaction locally. A transaction in a node’s mempool has no permanent ledger status until it is included in a valid block on the accepted chain. Mempools are local to nodes, and a node can drop, replace, or later re-accept transactions according to its state and policies. source
  4. A miner proposes a block. Miners assemble candidate blocks from transactions and send header work to hashing hardware. This is a proposal to extend the history, not a replacement for independent node checks. source
  5. Nodes assess the block. Nodes exchange and synchronize validated chain data. A proposed block must satisfy the rules enforced by the node to be accepted by that node. source source

This sequence explains the network-level process, not the behavior of every wallet or service. A provider may have its own transaction display, account records, or support procedures; those do not define how Bitcoin nodes validate transactions and blocks.

Consensus rules and the shared transaction history

Consensus rules are the protocol criteria nodes apply when checking transactions and blocks. The operational distinction is that miners can propose blocks, while nodes independently check received network data against applicable rules. Peer-to-peer exchange helps nodes synchronize validated chain data; it does not mean that a miner’s proposal is accepted simply because it was produced. source source

Bitcoin’s transaction signatures authorize transfers within the protocol, while node checks determine whether transaction and block data meet the applicable rules. These are related but separate functions: authorization by signature does not replace network validation. source source

The result is a process for exchanging and checking transactions and blocks across peers. This description stays at the level supported here: node exchange, independent checks under validity and relay-policy rules, and the distinction between a locally held transaction and one included in a valid block. It does not assign a universal confirmation threshold or make a claim about an individual transaction’s finality. source source

What the network does not guarantee

A transaction being received or relayed is not the same as permanent ledger status. Nodes maintain local mempools, and their state and policies can lead them to drop, replace, or later re-accept a transaction. Inclusion in a valid block on the accepted chain is the point at which the cited Bitcoin documentation describes a transaction as having ledger status. source

Protocol operation is also distinct from wallet recovery, custodial support, and transaction troubleshooting. The peer-to-peer protocol exchanges transactions and blocks; nodes apply validation and relay-policy checks. Those facts do not establish what a wallet or hosted service can recover, how its interface reports a transaction, or what support it provides. source source

In summary, the Bitcoin network coordinates transaction and block exchange through peers and node checks under applicable rules. Users and wallets initiate activity, miners propose blocks, and nodes check network data independently. These protocol roles should be kept separate from the functions and responsibilities of wallets and hosted services. source source source

Sources and references