** Ethereum: Why is a signature hash distinguish for each entry in a multi -entry transaction?
In Ethereum, when a multi-entrance transaction is executed, signature hash transactions differ from the input hash. This can initially seem counter -attack, but it is crucial to understand why this choice of design is made.
BIP 14: Laspolos and Signed Hashes
Ethereum’s manufacturer’s block (BPI) block enables multiple inputs with multiple entries. In order to adapt to these cases, BIP 14 defines lubricants, which are intermediate hashe that allow effective transaction to execute.
When creating a subtitle, the virtual machine Ethereum (EVM) replaces the previous scrippubKey for each entrance, resulting in different Hesh’s signatures. This replacement is required because EVM must ensure that the output address and transaction values match the expected.
** Why different signatories?
Different signatures are not arbitrary; They serve a certain purpose:
- Consistency
: By using different entrances with the same
scrippubKey, we maintain consistency in output addresses and transaction values.
- Efficiency : EVM can use these substances to optimize transactions processing, reducing computer directing costs and improving overall efficiency.
- Security
: Using different entrances ensures that transactions cannot be maliciously executed by exploiting weakness in the system.
Finish
Hash with signature of multiple transactions different from its input hash due to the replacement of scrippubkeys. This choice of design is rooted in maintaining consistency, optimizing transactions and security securing. In Ethereum, we believe EVM’s ability to replace inputs properly, allowing us to effectively and safely perform transactions.
Example uses the case
Consider a multi-urezing transaction in which two users want to serve funds from one account to leave different scriptpubkeys. To execute this transaction, replacement scrippubkeys would be provided:
- Exit addresses are appropriate for expectations.
- Transaction processing is effective.
- Safety is maintained.
In short, various Heshes signatures in multiple input transactions are the result of EVM possibilities to replace scrippubkeys, which balances consistency, efficiency and safety.
