Ethereum: Has anyone ported the Bitcoin software to plain C or Objective C?
Ethereuum: Store Bitcoin Software to Smooth C or Object C
The Ethereum blockchain is built on the top of a cryptographic frame known as Bitcoin designed by Satoshi Nakamoto. While the Bitcoin Software was transferred to different languages and platforms, including C ++ and Boost, they tried to rewrite the underlying cryptocurrency in the Smooth ANSI C and object C.
Smooth ANSI C Port
In 2009, a Development Group LED by Mihir Patel Tried to Rewrite Bitcoin Software in Plain Ansi C. The AIM of the Project is to create a cryptographic, open source implementation of the Bitcoin Protocol. However, the project was adopted in the Bitcoin Community with significant criticism and skepticism.
The main reasons for criticism were:
- Safety : Smooth ANSI C is not as Safe as other languages, such as C ++ or rust because of no memory security properties and the built -In support of cryptographic primitives.
- Performance : Smooth ANSI C has a slower execution time, such as C ++ or rust designed to optimize performance.
- Complexity : Bitcoin protocol is complex and deep understanding of cryptography, hash algorithms and other underlying technologies.
Despite these Challenges, Plain Ansi C Port has never been allowed as a separate bitcoin. However, some developers continued to maintain and update the code base over time.
Objective-C Port
In 2011, Richard M. Blank’s Developer Group Tried to Rewrite Bitcoin Software in the Object-C. The AIM of the project is to create a cryptographic, open source implementation of the Bitcoin Protocol, which can be used on MacOS, iOS and watchos devices.
The main purpose of the project was:
- Easy use : Create an objective-C port that was easy to use and can be integrated with existing Apple Frames.
- Safety : provide a safer alternative to smooth ANSI and other languages.
- Power : Optimizing the Bitcoin Protocol Power for Mobile Devices.
Although this project was partially successful, it eventually failed in terms of security and performance, like other alternatives.
Conclusion
The attempt to re -write Bitcoin Smooth Ansi C or C objective has not provided a commercially viable solution that is widely used in the Cryptocurrency Community. The reasons for this are complex and diverse, but they contain the following:
- Safety : Smooth ANSI C and Object-C are missing the built-in support for cryptographic primitives and other security features required by modern cryptocurrencies.
- Performance : These languages have a slower implementation time than languages such as C ++ or rust.
- Complexity : Bitcoin protocol is complex and deep understanding of cryptography, hash algorithms and other underlying technologies.
As the cryptocurrency area further development, it will be interested to see that alternative implementations will better balance security, performance and complexity.
Bir yanıt yazın