Live prices are currently unavailable — the exchange feed could not be reached and no recent cached reading is held.

Security & Resilience

What if a miner tries to cheat?

A miner controls the order of transactions in the blocks it finds, and nothing else. It cannot create coins, spend coins it does not own, or change the rules that decide whether a block is valid. Those limits are not a matter of miner goodwill; they are enforced by every node on the network, which rejects an invalid block no matter who produced it.

Protocol referenceSource: Bitcoin Developer Guide, Block ChainDescribes the validation rules a block must satisfy before any node will accept it.

What hash power actually buys

A miner that finds a block gets to decide which transactions go into it and in what order. That is a real power, and it has real consequences: a miner can leave a transaction out, can prefer one transaction over another when fees differ, and can choose to mine on top of one of two competing chain tips. It can also, if it controls enough hash power, attempt to build a competing chain in secret and publish it later to undo its own recent transactions. None of these abilities require breaking a rule, which is why they are worth understanding separately from outright cheating.

What a miner cannot do is produce a block that violates the consensus rules and have the network accept it. The block subsidy may not exceed the scheduled amount. A transaction may not spend an output that does not exist or has already been spent. A signature must satisfy the condition attached to the output it spends. A block's proof of work must meet the target set by the difficulty adjustment. A block that breaks any of these is invalid, and every node that receives it discards it without regard to how much work went into finding it.

This is the part of the design that is easy to miss. A miner is not a trusted party whose blocks are accepted on the assumption that it behaved. It is an untrusted party whose blocks are checked from scratch by every node that receives them. The work in the proof of work buys the right to propose a block, not the right to have it accepted.

Why an invalid block is rejected by everyone

Suppose a miner produces a block that pays itself more than the subsidy plus the fees of the transactions it included. The block's header may be perfectly well formed, its proof of work may meet the target, and it may arrive first at some nodes. It will still be rejected, because the coinbase transaction claims more value than the protocol allows. A node that accepted it would compute a different ledger from every other node, and its view of the chain would be ignored by the rest of the network. Rejecting the block is not a choice the node makes; it is the only way for the node to stay on the same chain as everyone else.

The same logic applies to a block that tries to spend someone else's coins. To move an output, a transaction must present a signature that satisfies the output's spending condition. A miner cannot forge that signature, because it does not hold the private key. It can include a transaction that claims to spend the output, but the signature check will fail and the block will be rejected. This is why the common claim that a majority miner can steal coins is wrong. It can reorder and censor, and it can attempt to reverse its own recent payments, but it cannot take coins it does not control.

A miner also cannot change the rules by fiat. Consensus rules are enforced by the software every node runs, not by a vote among miners. A miner that began producing blocks under a different rule set would be producing blocks that other nodes consider invalid, and those blocks would be discarded. Changing a rule requires the economic participants who run nodes to adopt software that enforces the new rule, which is a much slower and more distributed process than a mining majority.

The cheating that is possible

The attacks that remain are the ones that stay inside the rules. A miner can censor transactions, refusing to include them and declining to build on blocks that contain them. A miner with enough hash power can attempt a double spend against its own transaction, which is the subject of the double spending page. A miner can also withhold a block it has found and release it later, a strategy known as selfish mining, which can waste the hash power of honest miners and marginally increase the withholding miner's share of rewards. These are real costs, and they are the reason the security budget matters: the cost of mounting them scales with the total hash power an attacker must outrun.

The practical conclusion is that the threat model is not "a miner breaks the rules." It is "a miner with a large share of hash power exercises the discretion the rules give it." That discretion is bounded, and the bounds are what make the system work without trusting any participant.

Sources

  • Bitcoin Developer Guide, Block Chain — the consensus rules a block must satisfy, including the coinbase limit and proof-of-work check.
  • Satoshi Nakamoto, Bitcoin: A Peer-to-Peer Electronic Cash System — section 11 states that an attacker cannot create value or take coins that never belonged to it.
  • Bitcoin Core, policy documentation — the relay policy that is deliberately separate from consensus.