Unlocking Bitcoin Covenants: Understanding SIGHASH_ANYPREVOUT
Part 3 of a series on Bitcoin covenants explains BIP 118's SIGHASH_ANYPREVOUT. This soft-fork proposal removes the outpoint commitment in signatures, enabling reusable pre-signed transactions for layer-2 protocols while preserving script binding.
Quick Take
BIP 118 proposes SIGHASH_ANYPREVOUT as a soft-fork for taproot addresses.
Two variants allow varying levels of commitment to previous output data.
Enables signature reuse across compatible UTXOs for layer-2 efficiency.
Does not enable recursive covenants or transaction introspection by itself.
Market Impact Analysis
NeutralTechnical upgrade proposal with potential long-term implications for Bitcoin's programmability, but no imminent market catalyst.
Speculation Analysis
Key Takeaways
- BIP 118 proposes SIGHASH_ANYPREVOUT as a soft-fork upgrade restricted to Taproot addresses.
- The flag removes commitment to the outpoint, allowing signature reuse across compatible UTXOs.
- Two variants — ANYPREVOUT and ANYPREVOUTANYSCRIPT — offer different levels of script binding.
- Enables more flexible pre-signed transactions for layer-2 protocols without enabling recursive covenants.
What Happened
The Bitcoin community is examining BIP 118, which introduces SIGHASH_ANYPREVOUT — a new signature hash flag that removes the commitment to the specific UTXO being spent. This proposal, dating back to concepts from the 2016 Lightning Network paper, aims to unlock new covenant-like flexibility without full recursive capabilities. Unlike existing sighash flags, SIGHASH_ANYPREVOUT allows a signature to skip the outpoint, meaning a single pre-signed transaction can authorize spending any UTXO with matching conditions. The upgrade is designed as a soft fork and limited to Taproot addresses, keeping it backward-compatible.
The Numbers
No immediate market metrics apply, but the technical specifications are clear. BIP 118 defines two variants: SIGHASH_ANYPREVOUT, which still commits to the previous output's amount and script, and SIGHASH_ANYPREVOUTANYSCRIPT, which drops even those commitments — leaving only the transaction's other parts signed. Both exclude the outpoint (txid + index). Deployment would require a soft fork through Bitcoin's upgrade process, with activation possible only for Taproot-based outputs. The proposal follows a lineage from 2016, when SIGHASH_NOINPUT was first discussed on the bitcoin-dev mailing list.
Why It Happened
Bitcoin's ongoing covenant research seeks to improve layer-2 scaling and transaction design. Existing sighash modes bind signatures tightly to specific UTXOs, limiting flexibility for protocols like the Lightning Network. By removing the outpoint commitment, developers can create pre-signed transactions that work across multiple deposits, enabling smoother layer-2 operations without sacrificing Bitcoin's security model. The push reflects a broader effort to make Bitcoin more programmable while avoiding the complexity of recursive covenants.
Broader Impact
If adopted, SIGHASH_ANYPREVOUT could streamline Lightning Network watchtowers and other off-chain protocols, reducing operational friction. It also lays groundwork for future covenant designs, though it stops short of enabling general-purpose smart contracts. The soft fork's Taproot-only limitation ensures a cautious upgrade path. Industry watchers see this as a foundational step for Bitcoin's next evolution in programmability, potentially influencing developer tooling and layer-2 adoption.
What to Watch Next
- Community consensus: Watch for discussions on bitcoin-dev and signaling from major mining pools regarding soft fork activation.
- Layer-2 integration: Monitor whether Lightning Network implementations and other protocols begin incorporating ANYPREVOUT logic in testnet environments.
- Alternative proposals: Track competing covenant proposals like OP_CTV and OP_CHECKTEMPLATEVERIFY for comparative progress.
This article is for informational purposes only and does not constitute financial advice.
Always late to trends?
Join for the latest news, insights & more.
Disclaimer: Bytewit is an independent media outlet that delivers news, research, and data.
© 2026 Bytewit. All Rights Reserved. This article is for informational purposes only.
