Decision of Ethereum transactions: Where is the signature saved?
Ethereum, a popular decentralized platform for creating intelligent contracts and DAPP (digital applications), has undergone significant improvements in the introduction Bitcoins that allow more transactions.
However, an aspect of Segwit transactions remains unchanged: signatures are stored. In traditional bitcoin and other cryptocurrencies based on blockchain, such as Litecoin, Ethereum uses to sign public cryptography transactions. This process is often called “signature” or “admission signature”.
In the Ethereum transaction, the signature is actually stored in the form of a public key that is usually generated by a private key (one that is associated with the address of the sender Ethereum). The public key serves as a digital identifier for the sender and can be used to verify the authenticity of the signature.
How are signatures stored in segwit transactions?
So where is this signature stored in the Ethereum transaction that uses Segwit? The answer consists of the “Chaincode" script (also known as the "transaction script") associated with each block. When creating a new Segwit transaction, a script is included that generates a public key used to sign a transaction.
In other words, the signature is stored in the "scripting structure of data transactions. The "Scriptsig" field contains information about the sender's identity, including their public key and a small phrase connected to it.
Here is a simplified example of the Ethereum script that generates a private signature key:
JavaScript
Signransction function (Privatekey) {
Const signature = privatekey.sign (data);
The return signature;
}
`
In this example, the “data” are replaced by the real structure of transactions and the appropriate private key. The generated signature is then returned.
Conclusion
While Segwit has undoubtedly improved the effectiveness of Ethereum transactions by reducing the size of the block, signature storage remains a critical aspect of the platform identity checking. By saving the signatures in the form of public keys within the transaction scripts, the Ethereum network ensures that users can verify the authenticity and validity of transactions to blockchain.
This unique approach has both advantages and disadvantages over traditional cryptography methods. On the one hand, it offers another safety layer, allowing decentralized verification by exchange of decentralized keys (DKE). On the other hand, it can introduce a certain complexity in terms of private keys and scalability concerns due to the increased size of transaction structures.
When Ethereum is constantly evolving, it will be interesting to find out how this signature storage mechanism is improved and adapted to meet the growing community requirements.