Ethereum: What is the maximum size of a DER encoded ECDSA signature?

Maximum Size ECDSA coded by DER: deep immersion in Bitcoin

As an experienced Bitcoin enthusiast, you are not alien to the complexity of digital firms in this cryptocurrency. An aspect of these firms that caused their curiosity is the maximum size limit established by Ethereum (encrypted data) coded by ECDSA firms.

To answer your question directly, there is no clear answer. However, I will provide an analysis based on the information provided and other related sources.

Restrictions

Bitcoin ECDSA firms usually have 64 bytes in length to allow public keys to sign. This is due to several factors:

* Clustpresper : To reduce storage requirements, Bitcoin implementation uses a variable length coding scheme (VLE) that compresses the firm in a shorter way.

* Security

: Although longer signatures provide more security, such as Oracle attacks, additional costs and storage requirements also increase.

Ethereum attitude

When it comes to ECDSA signatures encoded by DER in Ethereum, the situation is different. According to the response of why the Bitcoin community hates Ethereum, an experienced co -authorist mentions that public keys can have up to 75 bytes in length.

To understand why this is possible, we immerse ourselves in the installation details of Ethereum. Ethereum blockchain uses the ECDSA algorithm version with a compressed public key version that allows a longer signature length.

Math **

To calculate the maximum size limit, we must consider the compression coefficient and the coding scheme used by Ethereum. Arrogant

• Compressed public key: 8 bytes

• ECDSA compression coefficient: approximately 0.5

• Compressed signature length: 32 bytes

Adding these components, we get the maximum compressed signature length of approximately 64 bytes.

Conclusion

Although there is no final answer to the question of what is the maximum limit of the ECDSA “Ethereum” firm, based on existing knowledge and research, it seems that public key signatures can have up to 75 bytes in length. However, this is probably excessive simplification and may not reflect real implementation or restrictions in practice.

As with any complex cryptographic issue, the best way is to consult with the respective sources and experts in the field to be more precise.