Anyone have experience with Openssl? Bitcoin removed OpenSSL for sha256, qt, and a few other places. It was used in many places. However, we still need it for Scrypt. Litecoin still uses it as well. I am all for fully removing it, but it takes doing and reworking.
From Josiah's article:
"Barry had also done some other major work with things like the removal of OpenSSL. Bitcoin Core had removed the OpenSSL library from 0.19, which the Scrypt algorithm uses. This is part of what had caused so many issues with 8.19 for Jared back in January of 2020, and Akshaynexus had attempted to readd as a “quick fix” to get things working again. Instead of taking the quick route, Barry implemented a single-file scrypt copy, which had an integrated sha256d function, which got us by, so that OpenSSL would no longer be required. This was no mean feat, and not the kind of thing some junior coder could accomplish (We saw relatively skilled people simply trying to add it back in), nor is it the sort of thing someone could ‘fluke’. This is the kind of thing that requires a LOT of skill and intricate knowledge of how all of the pieces tied together, and making the hashes match what they should be.
We had a fresh implementation, with new code, and outside of Odocrypt, DigiByte had not seen this kind of improvement in the last half a decade."
He did this in November/December I believe.
opensslreturns release notes and other references that we don't need to worry about
Once again, I want to clearly state that an upstream merge from BTC v22 into our latest stable 7.17.3 is a massive undertaking, with lots of chances for things to go wrong. Which is why we started a new documented process to do this with many people. And have had great controbutions from @gto90 @ycagel @j50ng @SmartArray @digicontributer & others. So thank you all for being involved.
Things really are in a much better, more tested, more reviewed and better process now. Jo & Barry are and have always been free to be part of this effort. And are still welcome to contribute. The more hands on deck the better all this becomes.
People cannot get mad an volunteer, open source devs for not “finishing” ideas and code that have never been submitted as a Pull request for us to review for main code base. This is why we need to clear up all the misscommunication here in a polite, professional manner that is best for all of us and most importantly best for DigiByte in the end. All input is welcome here. And by achieving a group consenus everything is in a much stronger & better place.