Ethereum: How is a Transaction ID generated & when does it change? (with a new sequence ID?)
Understanding Ethereum transaction IDs
As a developer building an unconventional Ethereum client, you probably know the concept of transaction identifiers (TXIDS) at Blockchain Ethereum. In this article, we will deepen the way of generating these exclusive identifiers and what happens to them after each block.
Generating transaction identification
The transaction ID is an 18 -ragged hexagonal sequence that represents one bitcoin transaction. The generation process takes a few steps:
- Creating a block : The new block is created in the Ethereum network when a valid transaction is sent to the network.
- Hash transaction : Each transaction in the block is a shortcut using the
SHA256algorithm with a shortcut as the input and Merle root of all transactions as an additional input.
- Transaction ID Generation : Hash of the transaction is then used to generate the exclusive sequence of sixteen bytes known as a transaction ID (TXID).
TXID is generated in two parts:
* Block abbreviation
: This is a real shortcut, which is a combination of a block header and other metadata.
* MERKLE ROTH : This is an additional entry for the Transaction Hash algorithm that helps to ensure uniqueness and integrity.
TXID generation algorithm
The Ethereum community has developed a consensus algorithm called “KECCAK-256” to generate transaction identifiers. The algorithm takes two input data:
* Block abbreviation : This is a real shortcut.
* MERKLE ROT : This is an additional entry for the Merle root calculation.
The resulting TXID is generated using a block of block and Merle root, which causes 18 hexadecimal sequence hexadec.
When does this change?
After creating each block in the Ethereum network, the transaction identifier for this block changes. This change occurs because each new chain block has its own hash of transactions and Merle roots.
To illustrate this concept, consider the following example:
* block 1 : The new block is created with a specific shortcut (for example, 0x1234567890abdef).
* Transactive Hashas : Each of the 10 transactions in block 1 has its own exclusive abbreviation of the transaction using the KECCAK-256.
* MERKLECH ROOTS : Merle root is also generated for each of these transactions.
As a result, when we create new blocks in the Ethereum network, they will have their own shortcuts and Merle roots, which leads to changes in transactions related to these blocks.
Example of case use:
To show how it works, let’s consider an example with Python:
`Python
Import Hashlib
Import json
Def Generate_txid (Block_Hash):
Shortcut function used for KECCAK-256
Def Hash_Function (Input_string):
Return Hashlib.sha256 (Input_string.encode ()). Hexdigest ()
block_merkle_root = Hash_function (p. (Block_Hash))
transaction_hashes = []
Because during the break (10):
assuming 10 transactions
Txid = hash_function (json.dumps (i, sort_keys = true)) + block_merkle_root
transaction_hashes.append (TXID)
Return json.dumps (transaction_hashes), block_merkle_root
block_hash = "0x1234567890abdef"
Txids, merkle_root = general_txid (block_hash)
Print ("Hashes transaction:", txids)
Print ("Merkle Root:", Merkle_root)
In this example, we created a new block shortcut using the “Hash_Funk” function. Then we use this block shortcut as an input to the Transaction Hash algorithm and we stored the created TXID with the Merle root.
This process ensures that each new block in the Ethereum network has its own unique transaction ID and Root Merle, which leads to changes in transactions related to these blocks.
Application
Understanding the way the transaction identifiers is generated and changing is crucial for creating a reliable and efficient and non -professional Ethereum client.