gitian.sigs VS gitian-builder

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

A number of pull requests are still awaiting gitian checks. Unfortunately, my attempt to review and help pulling #2579 (that would make it much easier to do gitian checks) over the finish line, is not ready because the gitian-builder software that we need for this has a bug. I have opened a pull request with them to fix the issue but because Bitcoin Core is moving away from this software, it takes a little longer to get things merged there. If I see no progress on this until Friday the 20th, I will propose to temporarily fix it locally in our own scripts.

So I also faced errors even after finding these bad boys. I kept getting a system error but I solved that using help from stack overflow and some Linux forums. Bitcoin.org too was also my close friend. The error was that I haven't started apt-cacher-ng yet. so after solving that I got a new error. With this error it took about three days to find a solution because it was a problem with the code or not with the code but the Ubuntu server location. Ubuntu has moved some archive files from Archive.ubuntu to old-releases.ubuntu. But the gitian builder was still fetching from that place. So as a normal bug solver. I edited the code on GitHub and sent a pull request for DevRandom to review. Guess what MY PULL WAS CORRECT SO HE MERGED ITT!!!! I was soo excited that day that I showed it to all my friends whether they understood or not. I was happy that I had contributed to the software which is literally the backbone of all Altcoins who build through Gitian. I was also happy that I had contributed to the same repository as the names like Gavin Andresen, Luke Dashjr , Hebasto and other prominent developers in the Bitcoin Development community. The link of my two pull request can be found here

The release process we inherited from bitcoin can be quite painful. It uses gitian to build repeatable and deterministic binaries from the source code. This means that multiple people can all build the code on different machines (and even different operating systems) and still get the same exact release binaries. We can then all compare the results and then sign the release, certifying that we all agree that the published release is safe & accurate.

For those interested in reproducible builds, the gitian [1] project is a fairly simple VM which sets the up the necessary environment for doing this sort of thing.

The tooling and community around reproducible builds is growing all the time, and imo we should be insisting on it for things such as government apps.

[1] https://github.com/devrandom/gitian-builder

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