snip
It is possible to upload executables (.exe) to GitHub (closed source) if they are 100% your own work. Encrypting the private key (pk) also infringes the license because, in a way, you are indirectly profiting from it. In short, if all the code were yours, you could do it without any problem. However, if you include third-party code or libraries, check their licenses to understand what you can and cannot do.
Thanks.. that is what i want to know... you are saying that if i wrote 100% of the code myself, then i could legally upload an .exe and even encrypt private keys function. However, if i used third-party code or libraries, i need to follow their license terms.
I understand your point. I did write the majority of the code from scratch, but I used several dependencies and repositories from him for faster address generation, such as
"sha256_avx2.h", "ripemd160_avx2.h" and "SECP256K1.h"... etc, The rest of the code is entirely mine.
Given this, what would be the proper way to proceed? Should I remove the repository entirely, or is there a way to comply with the license while keeping my work available?
You just need to make the repository private, remove the .exe file, and rebuild from scratch the files that are not part of your audit. After all, what truly matters is the logic, and ideas like "sha256_avx2.h," "ripemd160_avx2.h," and "SECP256K1.h" are not protected by patents safeguarding their logic. Simply rewrite anything protected based on your understanding of the idea and in accordance with the licenses. Some of these may simply require proper attribution to use without modification, depending on the license terms. However, another option would be to give up and simply delete everything, as the culture of donations has practically disappeared (99% dead), leaving only criticism alive.