Mining and Proof of Work

An application-specific integrated circuit, or ASIC, is a chip designed to perform a narrowly defined task efficiently. In Bitcoin mining, ASIC hardware repeatedly calculates the hashes used in the network's proof-of-work process. Specialization allows this equipment to perform far more relevant hashing work per unit of energy than general-purpose computers used for the same task. However, an ASIC designed for one mining algorithm cannot simply be reconfigured to mine every cryptocurrency. Its usefulness depends on algorithm compatibility, electricity requirements, cooling, reliability, and the competitiveness of other miners. Hash rate describes its calculation speed, while energy efficiency describes the power needed for that output; neither alone determines profitability. An ASIC does not hold authority to change Bitcoin's rules. It produces candidate proofs of work, and independent full nodes still reject blocks that violate consensus requirements, regardless of the hardware that generated them.

Sources: developer.bitcoin.org

A block header is the compact summary of a block that Bitcoin miners hash during proof-of-work calculations. The Bitcoin header is 80 bytes long and includes a version field, the previous block's hash, a Merkle root committing to transactions, a timestamp, an encoded difficulty target, and a nonce. These fields connect a candidate block to a particular history and set of contents. Changing the transaction list changes its commitment and therefore changes the header that miners must hash. A valid proof of work requires the resulting hash to fall at or below the applicable target. Headers make it possible to examine accumulated work without first downloading every transaction, but a header alone does not establish that all transactions obey consensus rules. Full validation requires the relevant block data and the state needed to check its spends.

Sources: bitcoincore.org · developer.bitcoin.org

The block reward is the compensation a miner may claim when producing a valid Bitcoin block. It consists of two separate components: the block subsidy, which introduces newly issued bitcoin, and the transaction fees paid by transactions included in that block. The miner claims the permitted amount through the coinbase transaction. These components should not be confused because the subsidy follows a predetermined reduction schedule, while fees depend on the transactions selected and their spending amounts. A block containing unusually high fees can therefore have a larger total reward than another block with the same subsidy. The reward is not spendable immediately; coinbase outputs must satisfy Bitcoin's maturity requirement. Mining pools may distribute proceeds according to their own accounting agreements, so an individual participant's payout is not necessarily the same thing as the network-level block reward.

Sources: bitcoincore.org · github.com

The block subsidy is the portion of a Bitcoin block's reward that creates new bitcoin according to the network's issuance rules. It began at 50 BTC per block and is reduced by half after each interval of 210,000 blocks. Because accounting uses whole satoshis, the scheduled reductions eventually bring newly permitted issuance to zero. Transaction fees are separate and may still compensate miners after that point. The subsidy is a maximum amount allowed by consensus, not a payment that a central administrator can increase at will. A miner attempting to claim more than the permitted subsidy and fees produces an invalid block. Lost private keys do not cause replacement coins to be issued, and a smaller circulating supply does not alter the schedule. This distinction separates Bitcoin's issuance policy from market supply, accessible holdings, and the total compensation earned through mining.

Sources: github.com · bitcoincore.org

The coinbase transaction is the special first transaction in a Bitcoin block through which the miner claims the permitted block subsidy and transaction fees. Unlike an ordinary transaction, it does not spend previously created outputs through a normal input. Its distinctive input contains block-related data rather than authorization to spend another person's funds. The total value of its outputs cannot exceed the allowable reward, although a miner may claim less. Coinbase outputs must mature for 100 blocks before they can be spent, reducing problems associated with rewards from blocks that later leave the accepted chain. A mining pool can direct the reward to addresses under its control and distribute participant payouts separately. The term is part of Bitcoin's transaction design and should not be confused with the cryptocurrency exchange that uses the same word as its company name.

Sources: github.com · developer.bitcoin.org

Difficulty adjustment is Bitcoin's mechanism for changing how hard it is to find a valid proof-of-work block as mining conditions change. On Bitcoin mainnet, the target is recalculated after each interval of 2016 blocks, using elapsed block time to move the average toward approximately ten minutes per block. More demanding difficulty corresponds to a lower numerical target that fewer hashes satisfy. If blocks have arrived too quickly, the next adjustment generally makes mining harder; if they have arrived too slowly, it generally makes mining easier, within the protocol's adjustment limits. The mechanism does not schedule individual blocks, which remain probabilistic, and it does not guarantee stable miner income. Increased hash rate can make blocks arrive faster before the next adjustment. Other networks, including Bitcoin testing networks, can use different rules, so mainnet's interval should not be treated as universal across cryptocurrencies.

Sources: github.com · developer.bitcoin.org

A halving is the scheduled reduction of Bitcoin's block subsidy by half after each interval of 210,000 blocks. Because Bitcoin aims for an average block interval of approximately ten minutes, halvings occur roughly every four years, but the protocol uses block height rather than a fixed calendar appointment. The event reduces newly permitted issuance per block; it does not halve existing wallet balances, transaction amounts, or the maximum supply. It also does not necessarily halve a miner's total block reward because transaction fees are a separate component. Mining revenue after a halving depends on several variables, including fees, market prices, operating costs, and competition. The schedule is a monetary rule, not a mechanism that guarantees a price increase. Discussions of an upcoming or past halving should therefore distinguish the directly specified subsidy change from uncertain market responses and individual business outcomes.

Sources: github.com · github.com

Hash rate measures how many hashing attempts mining equipment performs per second. Units such as terahashes per second and exahashes per second describe increasingly large quantities of calculations. A miner's hash rate affects its expected share of proof-of-work opportunities relative to other miners, but it does not guarantee a block discovery within a particular period. The network's total hash rate is generally estimated from observed block production and difficulty rather than measured by directly inspecting every machine. Short estimation windows can therefore be noisy. Hash rate also differs from energy efficiency: equipment may perform many calculations while consuming substantially different amounts of electricity. Comparisons across cryptocurrencies require caution because different mining algorithms perform different kinds of work. For Bitcoin, hash rate is one indicator of mining activity, not a direct measure of transaction throughput, user adoption, decentralization, or investment value.

Sources: bitcoincore.org · stratumprotocol.org

Merged mining allows work performed for one proof-of-work blockchain to contribute to securing another compatible blockchain. A common design commits information about the auxiliary chain into the parent chain's mining work, allowing the auxiliary network to verify an appropriate proof without requiring a completely separate hashing effort. The parent chain does not necessarily need to recognize or validate the auxiliary chain's transactions. Each network still has its own consensus rules, ledger, and asset. Merged mining therefore does not merge coin supplies or make an auxiliary token interchangeable with BTC. It can let miners participate in additional reward opportunities, but the auxiliary network's security depends on the work actually committed to it and its own validation design. Any bridge, federation, or redemption mechanism connecting the networks remains a separate source of assumptions. Sharing hashing work alone does not settle those custody questions.

Sources: dev.rootstock.io

Mining is the process of constructing candidate blocks and competing to satisfy a proof-of-work requirement. In Bitcoin, miners select transactions, create a coinbase transaction, assemble a block header, and repeatedly vary candidate data while searching for a hash below the required target. A successful candidate must still satisfy every other consensus rule before full nodes accept it. Mining helps order transactions and makes replacing accepted history costly, while permitted rewards create incentives for participation. It is not the same as running an ordinary full node, staking a token, or solving useful scientific calculations. Individual results are probabilistic, and operating costs can continue even when no block is found. Equipment efficiency, electricity costs, network competition, pool arrangements, and fees all affect a miner's economics. Increasing the number of mining machines does not directly increase Bitcoin's permitted transaction volume or alter its issuance schedule.

Sources: developer.bitcoin.org · github.com

A mining pool coordinates work from multiple miners and distributes proceeds according to an agreed payout method. Participants submit shares, which are proofs meeting a pool-defined target that is usually easier than the network's block target. Shares help estimate contributed work even when they are not valid network blocks. Pooling can make individual payouts less irregular than solo mining, but it does not increase the underlying probability that a given quantity of hashing work discovers a block. Payout methods differ in how they handle fees, variance, timing, and the operator's obligations. The pool's control over transaction selection can also matter for decentralization and censorship resistance. Mining protocols may give participants different levels of influence over templates. A pool account balance is a claim under the pool's arrangements, not an automatically enforced share of every coinbase output on the blockchain.

Sources: developer.bitcoin.org · stratumprotocol.org

A nonce is a value used within a protocol to distinguish operations or vary an input, but its exact role depends on context. In Bitcoin mining, the block header includes a 32-bit nonce field that miners can change while searching for a hash satisfying the target. Exhausting that field does not exhaust every possible candidate, because miners can also change other permitted data, such as information in the coinbase transaction that affects the Merkle root. In account-based systems such as Ethereum, an account transaction nonce instead helps order transactions and prevent repeated execution of the same authorized operation. Cryptographic signature schemes use another kind of nonce with strict security requirements. These meanings are related by the use of a distinguishing value, but they are not interchangeable. A miner's header nonce is not a wallet password, an account balance, or a measure of mining difficulty.

Sources: developer.bitcoin.org · ethereum.org

Proof of work is a mechanism that makes producing an acceptable result computationally costly while allowing others to check that result comparatively quickly. Bitcoin uses it by requiring a candidate block header's hash to meet a numerical target. Miners perform repeated trials, and finding a valid result provides evidence of an expected amount of hashing effort rather than a record of every calculation attempted. Nodes compare accumulated work when choosing among valid blockchain histories. This makes rewriting history require additional competitive work, but proof of work does not replace transaction validation or establish that any external information is true. It also does not mean miners are solving useful scientific problems; Bitcoin's work is specifically tied to its block-selection process. Difficulty adjusts the expected effort, while the random nature of hashing means individual miners can experience long or short intervals between successes.

Sources: developer.bitcoin.org · developer.bitcoin.org

Stratum is a family of communication protocols used to coordinate cryptocurrency mining equipment with pools and related infrastructure. It carries information about mining jobs and submitted work so that devices know what to hash and operators can evaluate their contributions. Stratum is not Bitcoin's consensus mechanism and does not change what full nodes consider a valid block. Stratum V2 includes distinct components for mining communication, job declaration, and template distribution, allowing different roles to be separated. Its design also supports stronger transport security and arrangements that can give miners more influence over transaction selection. Whether those capabilities are available depends on the actual equipment, software, pool support, and configuration. A connection labeled Stratum therefore does not establish a particular payout method or level of decentralization. The protocol handles coordination, while the pool agreement and underlying blockchain rules govern different parts of the mining process.

Sources: github.com · stratumprotocol.org