Bitcoin Covenants Part 3: SIGHASH_ANYPREVOUT Explained

Bitcoin's covenant capabilities are expanding with BIP 118, which introduces a new signature hash type called SIGHASH_ANYPREVOUT (APO). This proposal allows a Bitcoin signature to authorize spending from any compatible UTXO rather than being tied to a specific previous transaction output. The change is significant for layer-2 protocols and smart contract designs on Bitcoin.

BIP 118, authored by Bitcoin developer Anthony Towns, modifies the signature verification process so that the signature does not commit to the exact outpoint being spent. Instead, it commits only to the value and script of the UTXO, or even less. This enables what are called "rebindable" pre-signed transactions: a transaction signed once can be reused with different UTXOs that share the same script and value. For Lightning Network channels, this means channel states can be updated without generating new signatures for each state, reducing overhead and improving efficiency. Similarly, vaults and other covenant-based constructions can benefit from simpler key management.

The proposal has been under discussion for years and is seen as a key building block for more expressive Bitcoin smart contracts. While not yet activated, it has gained support among developers working on scaling solutions. If implemented, APO could reduce the complexity of multi-party protocols and enable new types of Bitcoin-native applications without requiring changes to the base layer's security model.

For traders and investors, the development of covenants like APO signals Bitcoin's ongoing evolution as a programmable asset. While the immediate price impact is minimal, the long-term implications for Bitcoin's utility and network effects are substantial. NowPrice's live Bitcoin charts and data allow users to monitor market sentiment as these technical upgrades progress. The next step is community review and potential inclusion in a future soft fork, with timelines still uncertain.