Bitcoin Inqusition 29.2

This version includes the implementation of BIP 118 and BIP 119, which are crucial for SIGHASH_ANYPREVOUT and OP_CHECKTEMPLATEVERIFY functionalities, as specified in their respective pull requests PR84 and PR85. Additionally, this release integrates BIN-24-1 (BIP 347), reintroducing the OP_CAT operation, alongside BIN-24-3 and BIN-24-4, equivalent to BIP 348 and BIP 349, which introduce OP_CHECKSIGFROMSTACK and OP_INTERNALKEY operations. These updates are detailed in PR83, PR87, and PR86. Another noteworthy inclusion is BIP 54, labeled Consensus Cleanup, aimed at streamlining and improving existing consensus rules through PR90 and PR99. The activation of these features follows a predefined schedule on the default signet, starting with the first two active since September 6, 2022, at block 106704, and others activating subsequently at designated blocks, culminating with BIP 54's activation approximately five days post-triggering at block 290513.

Experiments conducted on the Bitcoin Inquisition signet have provided valuable insights into the functionality and implications of these updates. Initial tests focused on the OP_CAT operation, revealing that commit transactions are visible on both standard signet explorers and Inquisition nodes; however, reveal/spend transactions only appear on Inquisition nodes due to standard nodes rejecting the block entirely. This discovery underscores the importance of direct node connections for proper transaction propagation, recommended through specifying addnode=inquisition.bitcoin-signet.net in node configurations. It also highlights the differentiation of Bitcoin Inquisition nodes via a specific subversion string, details of which can be found in the version 23.0 announcement linked here.

Further experimentation corrected initial misunderstandings regarding network forks and transaction visibility. A presumed network fork attributed to a new opcode spend was clarified; transactions indeed show up on Signet explorers once included in a block, indicating a misunderstanding rather than a fundamental issue. This revelation emphasized the distinction between policy and consensus layers regarding transaction visibility and underscored the critical nature of block inclusion for transaction finality on the network.

Subsequent experiments with CSFS and CTV revealed nuanced aspects of transaction confirmation times and script constraints. These tests highlighted the differences in visibility and confirmation latency between policy and consensus layers, with the former affecting pre-confirmation visibility on standard signet mempools and the latter impacting overall network acceptance. Specifically, the experiments demonstrated how script-specific constraints influence transaction acceleration and confirmation, offering practical insights into miner policy behavior and network dynamics.

This progression and experimental analysis reflect the ongoing efforts within the Bitcoin development community to enhance the network's functionality, security, and consensus mechanisms. Through the implementation of strategic consensus changes and the meticulous investigation of their effects, the community continues to refine and expand the capabilities of the Bitcoin protocol, ensuring its robustness and adaptability in the face of evolving demands and technological advancements.