Ethereum: Why can’t you get a private key from a public key?
Ethereum Public Contissation K = K * G may look like a simple formula that allows you to get a private key from a public key. However, this assumption is essentially defective in the context of blockchain cryptography and technology.
Cryptocurrencies and intellectual contract platforms, including Ethereum, public and private keys, are used for safe storage and sending of unannounced information, such as the rest, operations and cryptographic secrets. The idea of public key infrastructure (PKI), such as Ethereum, consists in the fact that a joint secret key called the key key (“K”) can be used to encrypt and decipher with the appropriate public key.
However, there are several reasons why you can’t get a private key from the Ethereum public key:
- However, this equation assumes that both sides have access to the same generator point (
G). This means that even if one of the parties knows his personal key (‘K), they cannot use it, encrypted the message and decipher without access to the appropriate public key.
- First, the multiplication of the f * g is an algorithm for doubles (ECDPA) of the elliptical curve (ECDPA), whose complexity is complex about (SQRT (N)
), where "N" is the row of the generator ('G). For practical purposes, this means that even if one of the parties knows his personal key, they cannot easily withdraw it from the public key.
- Mathematical restrictions:
The mathematical image of the point on the ellipse curve (ECC) can be seen as a set of 2D coordinates, in which each coordinate corresponds to the components of the “x” and “y” point. When implementing Ethereum, points are presented using 4 bytes (32 bits), which are relatively small compared to other cryptographic protocols that use more complex elliptical curve algorithms, such as NIST curves (such as SECP256K1 or ED25519)); This limited image size makes it difficult to show the complexity of the ECC point.
- Safety of hostages:
Ethereum in a private key often infected a nonce value, which can be used to prevent repetitions of attacks and ensuring transaction integrity. Even if one of the parties knows his personal key, it cannot easily use it without knowing the appropriate value.
To sum up, while the equation of the public key k = k * g may look like a simple formula that allows you to download a private key from a public key, it is basically defective due to the complexity of calculations, mathematical restrictions and causes of security. During Ethereum, other protocols and mechanisms are used to safely protect and exchange cryptographic secrets, such as the Elipse Curve (ECDSA) digital signature algorithm with HMAC-SHA256.
Recommendations:
- Use a safer protocol such as ECDSA with HMAC-SHA256 to use and replacement.
- Consider access to a zero evidence such as ZK-Snarks or ZK-Tex, to provide more efficient and safer cryptographic services.
- Always use safe practice, such as a password bag and soothing to protect the user’s identity and not published information.
I hope this explanation will help!
بدون نظر