Ethereum evolution: a look at the removal of the Schnorr code from Bitcoin Core
In August 2016, a significant change took place in the Bitcoin ecosystem. The implementation of Schnorr’s signature, which allowed a more efficient and convenient transactions of the transactions, was removed from Bitcoin Core, the Open Source Code base that feeds Bitcoin. This decision aroused curiosity among fans and developers, leading us to explore the reasons behind this move.
SCHNORR signatures: a brief introduction
Before immersing us in the details of the removal, it is essential to understand what are the signatures of Schnorr. Developed by Mihai Alisie in 2014, Schnorr signatures are a type of digital signature that allows faster and safer transactions on the Bitcoin network. Unlike traditional public key encryption methods such as Ecdsa, Schnorr signatures use a simpler mathematical approach to verify identities and create unique digital signatures.
The implementation of Schnorr in Bitcoin Core
The implementation of Bitcoin Core Schnorr’s signatures was a significant deviation from the traditional ECDSA based method used by other cryptocurrency projects at the time. By incorporating the Schnorr algorithm, the Bitcoin network aimed to improve the efficiency of transactions, safety and scalability.
However, between some developers and users concerns about the stability and the safety implications of the use of Schnorr signatures have arisen. In particular, there were concerns that the implementation could lead to greater vulnerability to certain types of attacks, such as the compromise of the 2nd level wallet (2nd-l) or double-cost attacks.
The decision to remove the Schnorr code from Bitcoin Core
In November 2016 a patch was released to remove the implementation of Schnorr’s signature from Bitcoin Core. According to reports, the decision was made by the Bitcoin Foundation, which was responsible for maintaining and updating the main Bitcoin Code base since its institution in 2009.
There are several reasons that have contributed to this decision:
- Stability concerns
: some developers have raised concerns about the potential instability introduced by Schnorr’s signatures. By removing the implementation, the Foundation aimed to create a more stable and predictable environment for users.
- Scalability problems : Schnorr algorithm has been seen as a useless complexity in the efforts of scalability of the Bitcoin network. Removal would allow a cleaner and more efficient implementation of the underlying technology.
- Safety considerations : The removal of Schnorr’s signatures reflected the definition of the priority of the foundation of security compared to other considerations.
Impact on the Ethereum ecosystem
The removal of the Schnorr code from Bitcoin Core had significant implications within the wider ecosystem. Ethereum, which is strongly based on Schnorr’s algorithm to allow its intelligent contractual function, has been forced to re -evaluate and improve its implementation of the signature method.
The Ethereum team eventually decided to adopt a different approach to signature contracts, opting instead for a more traditional method based on ECDSA. This decision allowed Ethereum to maintain compatibility with existing tools and bookstores that are based on Schnorr’s signatures, guaranteeing continuous support and adoption through the ecosystem.
Conclusion
In conclusion, the removal of the Schnorr code from Bitcoin Core was a deliberated decision taken by the Foundation in response to concerns on stability, scalability and safety. The implications for the wider Ethereum ecosystem are clear: the transition to a different implementation of the signature has paved the way for continuous growth and innovation within the community.
While developers and enthusiasts continue to explore new developments within the Bitcoin ecosystem, it is essential to remain informed about the underlying architecture and its evolving panorama.