Understanding Bitcoin: Like pre-sigwin interprete taproot op_checksigadd transactions
As for the improvement of the Bitcoin witness (Segwit), users often wonder how the nodes before Sigwin – those that support and verify the old SEGWIT transaction system before its replacement in November 2021 – interpret transactions containing a new Taproot protocol. In this article, we will delve into the way these nodes support blocks with Segwit transactions, in particular focusing on the impact of the Taproot OP_CHECKSIGADD (OPCHECKSIGADD) instructions.
Segwit transactions and nodes before Sigwin
Before Segwit, users can issue any unsweetened transaction performance without knowing who sent it. However, this led to an increase in expenses and a decrease in the portfolio balances, because some transactions remained unused. Segwit has been designed to solve these problems by introducing the concept of the functionality of “published everyone can spend” (SAP). This enabled the nodes to check whether the output was issued before marking it as issued.
Along with the introduction of Segwit, pre-sigwin nodes would now encounter blocks containing transactions with SAP instructions. However, they will not be able to verify these transactions in the same way as the nodes after Sigwin. Instead, they perceive them as “released everyone can spend” transactions and continue to process the block.
taproot op_checksigadd
Let’s now focus on the Taproot protocol, which is a key element of Segwit, which allows for a more efficient validation of the transaction. Opchecksigadd’s manual is a specific type of OP checking instructions in the Taproot standard. It verifies whether the exit was released or not before marking it as released.
When the node in front of Sigwin encounters a block with a block header containing the Taproot OP_CHECKSIGADD instructions, he will interpret this instructions as follows:
- The input script is checked for unsweetened output data.
- If an unsweetened output has been found, the Taproot engine verifies whether it has been issued or not using the Opchecksigadd instructions.
- If the edition has been issued, the message is sent to the sender indicating that he has no claim.
influence on the nodes in front of Sigwin
Pre-sigwin nodes will see blocks containing Taproot OP_CHECKSIGADD instructions, because “everyone can spend” transactions and go to block processing. This means that these nodes:
- Let users spend unreleased outputs without knowing who sent them.
- Reduce the wallet balance, enabling some transactions.
However, the nodes before Sigwin must also check whether these transactions are really important and observe all important rules, including the Taproot standard. They can simply not accept any transaction as “released” or “important”.
Application
To sum up, the pre-sigwin nodes will interpret blocks with Segwit transactions containing the Taproot OP_CHECKSIGADD instructions, because “everyone can spend” transactions, which means that it will allow some improper outputs without verifying their validity. Although this can lead to a reduction in the balance of the portfolio and increased expenses, it also allows the use of Segwit in a more efficient way.
The key amount is that the nodes before Sigwin must be careful when using blocks with Taproot OP_CHECKSIGADD instructions, because they require additional verification steps outside seeing the label “published everyone can spend”. In this way, they make sure that the transactions are correctly approved and the wallet balances remain accurate.
Additional resources
For more information on the update of the Bitcoin witness (Segwit) and its impact on the nodes before Sigwin, consult the following resources:
- [Wikipedia: segregated witness] ( (Bitcoin))))
- …