Ethereum: Why is replacement not supported
The Ethereum community has long discussed the potential traditional transactions with new discussions in order to replace more effective and scaling. One of the main features that prevents it from being called “replacement”.
The replacement refers to the process of creating a new transaction that replaces the existing blockchain. This is similar to the functionality of the blocking system on a website on which your account will be inaccessible when you try to apply again after shutdown, until the problem can be resolved.
The replacement of Ethereum is introduced using a mechanism called “sequence numbers”. If two transactions are created by the same sender, they have different sequence numbers. However, there is a catch: if one of these transactions is processed and approved, the number of sequence becomes higher than the other transaction.
This means that it is not possible to link them one after the other if we created new reserve transactions for existing ones. The reason for this is simple: the high number of order makes it impractical to predict which will be first and why.
Another problem with replacing traditional business is the fact that the current agreement algorithm (ETHash) should prioritize the sequence of blocks based on their block height and not the chronological sequence. This means that if we were replaced by all existing transactions in a certain block, they would cause conflicts between them and the new ones.
To show this concept further, we look at an example:
Suppose we have two transactions – A and B, with sequence numbers 1234567890 or 9876543210, if we replace transaction A with a safety transaction C (the same sequence number as A), it would generate conflicts because the block is processed according to D and e Block.
In summary, it can be said that the mechanism of the Ethereum sequence number replaces part of the transactions, but basic elements that prevent it from appearing on a large scale. The current algorithm of the consensus over the priority determines the height of the blocks above the chronological sequence, which makes it difficult to bind a sophisticated replacement transactions one after the other.