Bitcoin Inqusition 29.2

The discussion begins by addressing a misunderstanding about the behavior of two networks in response to a transaction that utilizes a new opcode, which is related to BIP 347, highlighting it as a soft fork scenario. Interestingly, there's a specific transaction in question that does appear on Signet explorers, as evidenced by the provided link. The conversation suggests a common oversight where one might check for the transaction's presence before it's actually included in a block. This would lead to confusion since regular Signet nodes deem such transactions as non-standard, thus refusing to accept them into their mempool. The clarification implies an important aspect of how transactions are treated differently depending on their timing and the specific network protocols in place.