Tag Info

I've done a rebuild of 0.20.1 and I get the same results that you do. This would indicate that a build dependency has updated to produce slightly different results than the version that was in use at the time of the release. The build dependency versions are pinned unlike the actual software dependencies. IIRC this is common for gitian builds and attempting ...

Electrum's distributed binaries are determinisitc. Although Electrum is written in an interpreted language, the distributed binaries also need to provide the dependencies and the packaging process for producing binaries for python software is not deterministic. Electrum has their own process for ensuring dependency versions and determinism of their binaries. ...

So having a deterministic/reproducible build system is more of a software development practice than it is a single piece of software like Gitian. There are a variety of projects that try to implement this practice which are listed below: https://reproducible-builds.org/who/ Gitian handles the deterministic building through a virtual machine, and then the ...

The challenge with creating reproducible builds is that you need to ensure that the build process matches exactly across different operating systems and different architectures. Bitcoin uses Gitian, a deterministic build process to achieve that. Bitcoin Core provides the configuration and build instructions for various operating systems in the /contrib/...

As long as the underlying OS image is susceptible to changes, you will not get a reproducible build system that guarantees reproducibility over a long period of time. If the OS can update compiler toolchains, libc versions and whatever tools are used during a gitian build, changes in the future to the output are expected. Since this is the case since gitian ...

The compiled binaries on the website are built using gitian. This is deterministic so you'll get an identical build to everyone else who has built it, for verification purposes. You can find instructions on how to do this here: https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md

This question is a bit old now but the solution(s) are still valid. I have found that the most difficult part of getting gitian builder working is the setup of LXC. Apparently it is still valid to use the KVM method but I have never done this and from what I understand, KVM is the old method. Be sure to carefully read over the entire build instructions at ...

When you run the gitian-build.sh script, you need to specify additional arguments for it to build and produce gitian signatures. You need to specify the version (or commit or branch) that you want to build. You must also specify an identifier for the GPG key that you want to use to sign the gitian output. That identifier is the signer. For example, for me, ...

What stamps out a gitian build? A timestamp! (Silly joke - I know) I've been monitoring privacy coins and I verify their development practices (commit signing, gitian usage) a bit and I've seen the following projects use gitian for each release. I've had to wrestle with gitian in the past, I run my own gitian build machine to verify builds. Dealing with ...