BIP-119 (OP_CHECKTEMPLATEVERIFY) (no activation)

Mar 5 - Dec 2, 2025

  • The ongoing discussion in the Bitcoin community, particularly around Bitcoin Core's Pull Request 31989 and related proposals like BIP-119 (CheckTemplateVerify), delves into the technical intricacies and potential impacts of introducing new functionalities to the Bitcoin protocol.

The key focus is on enhancing the protocol's capabilities through careful, incremental innovations that aim to preserve the network's security and efficiency. The debate underscores the importance of evaluating such proposals based solely on their technical merits, setting aside any biases stemming from historical challenges associated with similar enhancements.

BIP-119, spearheaded by Jeremy Rubin, introduces a conservative approach to integrating covenants into Bitcoin, aiming for a balanced expansion of the protocol’s functionality without overstepping bounds that might compromise its foundational principles. This proposal, along with its historical counterparts like OP_CHECKOUTPUTHASHVERIFY and OP_SECURETHEBAG, represents a thoughtful progression towards embedding more complex mechanisms within the Bitcoin architecture. However, concerns have been raised about the potential risks associated with combining CheckTemplateVerify with other primitives. Critics argue that this could inadvertently reintroduce vulnerabilities to specific types of attacks, such as those exploiting transaction withholding to manipulate miner incentives or disrupt time-sensitive Layer 2 protocols.

A particular point of contention revolves around the theoretical risk of costless bribe attacks, exemplified by the TxWithhold concept. Drawing parallels with the phenomenon of Miner Extractable Value (MEV) observed in other blockchain ecosystems, contributors express apprehension that unchecked expansions to Bitcoin's script capabilities might lay the groundwork for exploitative practices that could undermine the network's integrity. This perspective emphasizes the need for a cautious approach to developing and implementing new script primitives, advocating for a thorough assessment of potential threats and the identification of robust mitigations before proceeding.

Furthermore, the discussion touches upon speculative future developments, such as contracts powered by an OP_CSFS primitive, which could facilitate trust-minimized bribes to miners. Such advancements raise significant concerns about the long-term security and reliability of the Bitcoin network, highlighting the delicate balance between innovation and the preservation of a stable, secure underlying monetary system. The discourse reflects a broad spectrum of viewpoints, underlining the complexity of evolving a pioneering technology like Bitcoin in a manner that safeguards its core values while exploring avenues for meaningful progress.

Link to Raw Post
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiDecoding BitcoinWarnet
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project.

Give Feedback