Bitcoin Inqusition 29.2

The exploration of Bitcoin's Inquisition signet has led to insightful experiments with OP_CAT, focusing on a novel approach where data is embedded within the witness, and the script is tasked with verifying only the hash. This method ensures that only the possessor of specific parts (part_a/part_b) can execute a spend. The commitment transaction and the subsequent spend transaction are highlighted through their respective hashes: 084d5a9c6a8c176c24edc0a8b7ce54ed65808a326367d8a9299b4460ecaada09 leading to 00072d4aa354b5987eb8f2ffec440db7467b0581c5e845a6a0ef6999b2d05656. For those interested in delving deeper into the technical aspects, the code and complete transaction details are accessible at Aaron Recompile's GitHub.

An intriguing finding from these experiments is the behavior of commit transactions and reveal/spend transactions across different networks. While commit transactions are visible on both standard signet explorers such as mempool.space and Inquisition nodes, reveal/spend transactions are exclusively visible on Inquisition nodes. This discrepancy occurs because standard nodes do not recognize blocks containing new opcode spends, leading to a network fork at the point of introduction for a new opcode spend. This observation is crucial for researchers or enthusiasts attempting to verify transactions through public explorers, as it underscores the limitations of current infrastructure in accommodating experimental opcodes.

The ongoing experimentation will extend into other areas, including CSFS, CTV, and INTERNALKEY, indicating a robust agenda for further dissecting and understanding the capabilities and limitations of Bitcoin scripting through the Inquisition signet. These experiments not only contribute to the body of knowledge surrounding Bitcoin's scripting possibilities but also highlight the challenges and peculiarities of working within and across Bitcoin's evolving network infrastructure.