PrevNext

Academy Node

Consensus Rules vs Policy

📜 Rule

Type: RuleDifficulty: 2/4consensus-rules-vs-policyVerified: 2026-02-12

Summary

Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. decides what is valid chain history; policy decides what a Full NodeSoftware that independently validates blocks and transactions against consensus rules. relays or mines before confirmation.

Story

Two Full NodeSoftware that independently validates blocks and transactions against consensus rules. can disagree on relay behavior and still remain on one chain. That is the policy-versus-Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. boundary. Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. are hard requirements: if you violate them, blocks are invalid everywhere. Policy rules are local preferences used for MempoolNode-local pool of valid, unconfirmed transactions awaiting block inclusion. hygiene, spam resistance, and fee optimization. This distinction is foundational for newcomers because many debates confuse relay preferences with protocol validity. Raw Block surfaces this explicitly so users can reason about RBF, standardness, and fee filters without mistaking them for Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. changes. Understanding the boundary also clarifies why Bitcoin upgrades are conservative: Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. changes require broad coordination, while policy refinements can iterate faster and independently.

Deep Dive

Consensus scope

  • Defines valid block format, script execution, Block SubsidyProtocol-defined new bitcoin issuance in each block, halving every 210,000 blocks. bounds, and UTXOUnspent Transaction Output. A spendable bitcoin output created by a prior transaction. spend rules.
  • Violations trigger block rejection and potential chain splits.
  • Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. changes require coordinated protocol rollout and broad adoption.

Policy scope

  • Controls relay admission, replacement handling, and standardness templates.
  • Policy diversity across Full NodeSoftware that independently validates blocks and transactions against consensus rules. is expected and non-forking.
  • MinerParticipant that assembles candidate blocks and performs proof-of-work to extend the chain. may override default policy in block template decisions.

Real Data

Relay Pressure Signal

Loading...

High recommended fees typically indicate stricter practical relay conditions.

Policy Snapshot Time

Loading...

Timestamp for the latest fetched fee/policy context.

Key Takeaways

  • Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. invalidity is global; policy rejection is local.
  • Policy helps protect resources without redefining money rules.
  • Do not infer Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. from MempoolNode-local pool of valid, unconfirmed transactions awaiting block inclusion. behavior alone.

Security Notes

  • Conflating policy and Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. can cause serious operator misconfigurations.
  • Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. bugs are systemic; policy bugs are usually local and recoverable.

Node Security Panel

Vulnerabilities (1)

Attacks (0)

    Assumptions (0)

      Policy vs Consensus (4)

      Policy vs Consensus

      Policy is a pre-Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. admission layer; Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. is the final and universal validity layer.

      Consensus Rules

      • ConsensusMAX_BLOCK_WEIGHT (4,000,000 weight units from SegWit2017 Bitcoin upgrade separating witness data, fixing transaction malleability vectors, and improving capacity efficiency./BIP141) is a Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. block validity rule.
      • ConsensusCoinbase TransactionThe first transaction in a block that pays the block subsidy and collected fees to the miner. maturity, script validity, and UTXOUnspent Transaction Output. A spendable bitcoin output created by a prior transaction. spend constraints are Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions.-enforced.
      • ConsensusBlock structure commitments and Proof-of-WorkConsensus mechanism where miners expend hashpower to find valid blocks below the target threshold. target validity are mandatory Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. checks.

      Policy Rules

      • PolicyStandardness filtering of uncommon scripts in default relay settings.
      • PolicyMinimum relay feerate and RBF replacement policy affect MempoolNode-local pool of valid, unconfirmed transactions awaiting block inclusion. admission and replacement.
      • PolicyMempoolNode-local pool of valid, unconfirmed transactions awaiting block inclusion. eviction and package relay behavior are implementation policy choices.

      Security Research Panel

      CVE-2018-17144

      2018

      Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. validation regression demonstrated systemic risk when core validity checks fail.

      Explorer Deep Links

      Some sources are external. When an internal Raw Block view is available, we'll surface it here.

      Claim Sources

      Consensus and policy are separate enforcement layers in Bitcoin Core.

      RBF and relay replacement behavior are policy-level mechanisms.

      Claim Registry Links

      • Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. determine block/transaction validity for all Full NodeSoftware that independently validates blocks and transactions against consensus rules., while policy rules are local relay/MempoolNode-local pool of valid, unconfirmed transactions awaiting block inclusion. decisions.

        Verified: 2026-02-12

        Source

      Further Reading

      Graph Neighbors

      DirectionRelationNode
      OutgoingDEPENDS_ONLightning Network Maturity
      OutgoingDEPENDS_ONSegWit and Taproot Upgrades
      IncomingDEPENDS_ONDifficulty Adjustment (2016)

      Related Nodes