I can give you an article on this topic. However, I have to explain that there is no specific discussion or a question about the shortening of 33 bytes public keys from Schnorr signatures in Ethereum.
In this context, here is an article based on my understanding of topic:
Ethereum: Why no security loss happens with 32 bytes public keys and Schnorr signatures
Public keys are unique digital property identifiers that allow users to safely access their cryptographic keys. Ethereum’s public keys are portrayed as (x, y) coordinates, where x marks a private key and Y marks a related public key.
As for Schnorr signatures, a certain type of digital signature used in Ethereum operations, there is a discussion on the use of 32 bytes public keys, not the standard 33 -byte format. Specifically, some users ask why shorter public keys.
What are Schnorr signatures?
Schnorr signatures are a type of digital signature that allows users to sign messages without disclosing their personal key. To create a unique identifier of each message, they use one-sided bag function and a secret number called “secret value” (s). This identifier is then used to generate a digital signature that is restrained with the user’s personal key.
33 byte format
Ethereum public keys are usually portrayed as (x, y) coordinates when X marks a private key and y marks a related public key. The standard format of these coordinates is 32 bytes consisting of ::
- X coordinate: random 256 -bit value
- Y coordinate: random 256 -bit value
compromise
Using Schnorr signatures with shorter public keys (eg 31 finishes), some users claim that security losses do not suffer because the shortened key is still long enough to create the required secret value. The shortening of the key can actually improve efficiency as it reduces the calculation overheads associated with digital signature generation and verification.
However, this argument assumes that the shorter key is still valid and safe. In reality, a shorter key may be unsuitable for all cryptographic operations such as encryption or signing of large messages. In addition, some users may argue that the use of longer key provides more flexibility and reliability of cryptographic operations.
Conclusion
Although both sides of this debate are justified, there is no consensus on whether Schnorr’s signatures of Ethereum 32 byte public keys are safe or not. The debate continues, so consumers need to constantly update the latest changes and updates of the Ethereum community.
In conclusion, while using shorter public keys, there may be some benefits, such as improved efficiency and flexibility, using these shortened keys, safety losses do not occur. However, consumers should be aware of potential compromises and risks associated with shortening their public keys before making a decision.
Remember that this article is based on my understanding on this topic and is not a cryptography or Ethereum development expert. If you have any specific questions or concerns about Schnorr signatures or 32 bytes public keys Ethereum, don’t hesitate to ask!