Bitcoin PIPEs v2

Feb 12 - Feb 26, 2026

  • Bitcoin PIPEs version 2 introduces a novel method for enforcing spending conditions on the Bitcoin blockchain without altering its consensus rules or introducing additional trust mechanisms.

This approach employs cryptographic techniques, specifically witness encryption, to ensure that a valid Schnorr signature can only be produced when predefined conditions are met. By embedding spending conditions into cryptography, PIPEs v2 offers a more expressive set of policies that can be enforced directly on-chain. This innovation shifts the enforcement of spending conditions from the blockchain to cryptography, allowing for the creation of conditional signatures without new opcodes or optimistic challenge mechanisms.

The discussion further explores the limitations within Bitcoin's scripting capabilities, particularly focusing on transaction validation methods like signatures and hashlocks. It highlights the challenges posed by hashlocks' transparency and the potential of advancements like HTLC (Hashed Timelock Contracts) and taproot structures combined with Script to offer nuanced authorization methods. These developments aim at attaching identities to transactions, offering enhanced security and flexibility. Meanwhile, witness encryption is discussed as a means to extend control over UTXO (Unspent Transaction Output), diverging from traditional covenants in Bitcoin which constrain output spending. This exploration indicates ongoing interest in expanding Bitcoin's transaction scripting capabilities to achieve more granular control over transactions.

In terms of transaction security, employing a 3-3 musig2 signature setup involving a counterparty operator is highlighted for its robustness in preventing unauthorized fund movement. This setup necessitates multiple approvals for any transaction, thereby enhancing security against potential theft. The discussion also questions the uniqueness of referring to this mechanism as a "covenant," suggesting that operational constraints implemented by the operator may play a larger role than the musig2 signature scheme itself in controlling transactions.

Function Encryption (FE)-based PIPEs present a solution for emulating post-covenant structures cryptographically, though practical limitations exist with PIPEs v1, leading to an interim reliance on PIPEs v2-based pre-covenants or binary-predicate covenants. This allows for integrating additional restrictions directly within the covenant's circuit design, indicating a community-driven approach towards enhancing PIPEs' effectiveness.

The integration of Witness Encryption (WE) with multisig setups offers a unique security mechanism by combining enforcement capabilities of covenants with automated condition verification provided by WE. However, this approach's applicability may be restricted due to specific deployment prerequisites, highlighting its innovative yet conditional utility.

Layer 2 application covenants rely less on interactivity among parties when scripts are utilized, emphasizing security and consensus via multi-signature arrangements. Trust assumptions are crucial for executing L2 protocols, with mechanisms ensuring transactional integrity and mitigating deception risks. Early revelation of a 3-3 musig by an operator could trigger protocol procedures, contrasting with simpler scenarios where risk to the user from potential operator deception exists.

The comparison between BitVM and its PIPE variant reveals differences in their operational frameworks concerning witness fixation timing. BitVM's flexibility in setup phase contrasts with BitVM PIPE's requirement for prior knowledge of w, although both maintain identical mechanics for verification and disputes. Questions regarding BitVM's emulation of covenants and the necessity for collaborative efforts during updates are raised, indicating a need for clarification on fundamental principles.

Lastly, the cost implications of implementing covenants in cryptocurrency systems are addressed, considering current cloud services pricing. The discussion underscores the goal of achieving "trustless non-simultaneously-online setup" over "arbitrary spending conditions" to enhance multiparty offchain cryptocurrency systems, emphasizing the importance of economic viability and practical considerations in the development of such technologies.

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