gitian.sigs VS dogecoin

Dogecoin core uses gitian technique to verify binaries. Do a SHA256SUM of the downloaded installation file and compare that value with the one in the gitian assert file (for example I think this is the assert file for 1.14.3 mac os) for the version you downloaded. If they match you have nothing to worry about, MacOs is probably written to yell at legitimate dogecoin-core.

git clone https://github.com/devrandom/gitian-builder git clone https://github.com/dogecoin/dogecoin git clone https://github.com/dogecoin/gitian.sigs pushd dogecoin git checkout v1.14.3 popd

The installers (and zipfiles, dmgs and tarballs) are signed with all our pgp keys, you can compare the hashes for windows binaries here https://github.com/dogecoin/gitian.sigs/tree/master/1.14.3-win (against our validated pgp keys)

If you just want to check if your binary is the signed one, and you're on, say windows 64-bit, you take one of the signer's lists that were published and dig out the sha256, eg: https://github.com/dogecoin/gitian.sigs/blob/master/1.14.2-win/langerhans/dogecoin-win-1.14-build.assert#L8

Have you checked the 1.14.7-dev branch on GitHub? https://github.com/dogecoin/dogecoin

🧾 Whitepaper

It already has the "fix" inherited from the Bitcoin code they reuse. Though you shouldn't count on that feature to not have bugs: the Dogecoin codebase is old and poorly maintained. If you run it on a cloud service, always turn on billing limits. https://github.com/dogecoin/dogecoin/blob/master/doc/reduce-...

Here's the release tracker for 1.14.7. We've been a little bit backed up with some work to migrate the testing system to a supported version of Ubuntu in GitHub, as well as a need for more people to do good code reviews.

read this dogecoin issue for more info (it also works with doge) https://github.com/dogecoin/dogecoin/issues/3243