Bitcoin Inqusition 29.2

This version, building upon Bitcoin Core 29.3rc2, integrates support for BIP 118 and BIP 119 through implementations of SIGHASH_ANYPREVOUT and OP_CHECKTEMPLATEVERIFY respectively, as detailed in their corresponding pull requests. Additionally, it includes BIN-24-1 (BIP 347) which reintroduces the OP_CAT operation, alongside BIN-24-3 and BIN-24-4, equivalent to BIP 348 and BIP 349, adding OP_CHECKSIGFROMSTACK and OP_INTERNALKEY operations. The release also merges BIP 54, labeled Consensus Cleanup, to streamline and enhance existing consensus rules. These features are activated on a schedule on the default signet, with activations beginning September 6, 2022, at block 106704, and subsequent features following at specified later dates. For effective transaction propagation, users are recommended to connect directly with other Inquisition nodes. This release underscores the ongoing efforts to refine and extend the capabilities of the Bitcoin network through thoughtful consensus changes.

Recent experiments within the Bitcoin Inquisition signet have explored innovative approaches using OP_CAT for embedding data within the witness component of a transaction. This method ensures that only parties possessing specific data parts can execute a spend, with the commitment and spend transactions being uniquely identified by their hashes. These experiments have revealed important insights into the behavior of commit and reveal/spend transactions across different networks, highlighting a discrepancy where reveal/spend transactions are only visible on Inquisition nodes due to standard nodes not recognizing blocks containing new opcode spends. This observation is crucial for researchers or enthusiasts verifying transactions through public explorers and highlights the limitations of current infrastructure in accommodating experimental opcodes.

A discussion on the behavior of two networks in response to a transaction utilizing a new opcode related to BIP 347 clarified a common misunderstanding about soft fork scenarios and transaction visibility on Signet explorers. Regular Signet nodes consider such transactions non-standard, refusing them entry into their mempool until they are included in a block. This clarification emphasizes the importance of understanding blockchain protocols and node behaviors to avoid misconceptions regarding network forks and transaction visibility.

Further analysis delved into the impact of specific opcodes under the Tapscript protocol and their treatment by non-upgrade nodes, leading to insights on how easily misunderstandings about network forks can arise without in-depth technical knowledge. Ongoing experimentation extends into areas like CSFS, CTV, and INTERNALKEY, providing a robust framework for examining Bitcoin scripting's capabilities and limitations. These studies highlight the critical nature of thorough analysis in understanding the nuances of Bitcoin transactions and the impact of script constraints on transaction acceleration and visibility, contributing valuable lessons in the examination of blockchain operations.

Additionally, an exploration of an IK + CSFS composition using OP_INTERNALKEY for sourcing the pubkey from Taproot execution context rather than witness has been shared. This approach shifts authorization dynamics and highlights the importance of fixed messages for replayability across UTXOs with the same internal key. Such experiments offer deep insights into the dynamics of Bitcoin transactions, promoting a broader understanding of miner policy behavior and the complex processes underlying blockchain operations.