Ethereum: Problems with deterministic ECDSA based on RFC6979 Bitcoin
Ethereum blockchain largely depends on the elliptical curve of the digital signature algorithm (ECDSA) for secure transactions and signatures. However, the recent discovery reveals that the introduction of a deterministic ECDSA based on the recommendation of safe electronic cryptography (RFC 6979) has a number of problems that could endanger the integrity of the network.
Determist ECDSA and Bitcoin Codebase
Bitcoin Codebase’s deterministic ECDSA is used to ensure that all transactions are signed with the same private key. This approach is based on cryptographic safe pseudo -numerical generator (CSPRNG) to generate an accidental secret key for each transaction. However, the use of CSPRNG has raised companies among security experts.
Problem: ECDSA NEEDMINISM
The deterministic ECDSA is based on the assumption that the attacher can provide the private key generated by the CSPRNG. In practice, this means that the attacher could potentially predict the private key and then the signature to the relevant transaction. This is an important group because it allows the attacher to create a fake transaction with malicious intentions.
Question: RFC 6979 implementation
The RFC 6979 is a widely accepted standard for safe electronic cryptography. However, its introduction to Bitcoin Codebase is criticized for a number of reasons:
1
Lack of coincidence
: The private key generated by CSPRNG may not be truly accidental, potentially causing predictable patterns and weaknesses.
- There is no protection against side channel attacks : Determist ECDSA does not provide any protection against side channel attacks, such as time schedule or power analysis attacks that may endanger signature security.
Conthequen: EIP-1559 and Hard Forks
As a result of these problems, the Ethereum Community has studied alternative solutions to ensure the security and integrity of transactions. The Ethereum Improvement Proposal (EIP) 1559 proposes a new way to generate private keys for a deterministic ECDSA, which uses CSPRNG instead of cryptographic safe pseudo -function (CSPRNG).
Conclusion
Problems with a deterministic ECDSA based on the RFC 6979 Bitcoin are important and have possible consequences for Ethereum’s network security. The aim of the proposal EIP-1559 is to address the dissertation issues, but its implementation is not yet complete. Until then, users need to be careful when generating private keys.
suggestions
To reduce the risks associated with the deterministic ECDSA:
1
Use alternative methods
: Consider using another method to generate private keys, such as hardware safety module (HSM) or safe key management system.
- Save your Ethereum Wallet Updated : Regularly update your Ethereum wallet software and firmware to make sure you have the latest security patches and features.
By aware of these issues and the necessary precautions, users can help ensure the long -term security and integrity of their Ethereum transactions.