...
Just to be clear, is the code you listed the latest bitcoin 0.16 code? I can add my code to this, but I want to check a couple more things before I start.
Most of the filenames I changed were also changed in the original code ... images, riecoind, riecoin-cli, a few others. I might have changed a couple extra in the qt code (bitcoingui.cpp -> riecoingui.cpp).
Similarly, a lot of the changes are text substitutions of bitcoin for riecoin. This was true in the original code and given how much the code has grown since then is worse now. It would be easy for me to do a separate commit of all the text substitutions so that the main riecoin changes are more obvious.
My approach was to change all filenames and all text (except copyrights and a couple others). Let me know if this is a problem. Changing some, but not others will make things more difficult.
I'm not sure if I will get the bounty but if I do I plan to share a portion with others contributing to Riecoin.
Yes,
https://github.com/riecointeam/riecoin master branch should be even with upstream bitcoin 0.16 branch (now v0.16.2).
Here is a great repo that nzsquirrell put together on minimal changes necessary that I find quite good. It's for 0.14 but is very close to 0.16:
https://github.com/nzsquirrell/testcoin14/commits/masterespecially this commit:
https://github.com/nzsquirrell/testcoin14/commit/3a2665eb070ed901ed28722e345ad61d75027d4cThere are surprisingly few name changes that need to be made, most of the missing ones from the above commit are in src/rpc for the rpc calls. We can always knock those out once the core logic is in place.