This is a minor release of btcd that fixes some bugs in the p2p sub-system, and also updates relevant parts of btcjson to be compatible with bitciond 0.19.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://keybase.io/roasbeef/pgp_keys.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest-v0.20.1-beta.txt and manifest-v0.20.1-beta.txt.sig are in the current directory) with:

gpg --verify manifest-v0.20.1-beta.txt.sig

You should see the following if the verification was successful:

gpg: assuming signed data in 'manifest-v0.20.1-beta.txt'
gpg: Signature made Tue Nov 12 19:08:07 2019 PST
gpg:                using RSA key 4AB7F8DA6FAEBB3B70B1F903BC13F65E2DC84465
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

Verifying the Release Binaries

As of this release, our release binaries are fully reproducible thanks to go1.13! Third parties are now able to verify that the release binaries were produced properly without having to trust the release manager(s). See our reproducible builds guide for how this can be achieved. The release binaries are compiled with go1.13.1, which is required by verifiers to arrive at the same ones.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.20.1-beta

You should see something along the lines of this in the case of a valid tag:

gpg: Signature made Tue Nov 12 18:29:03 2019 PST
gpg:                using RSA key 4AB7F8DA6FAEBB3B70B1F903BC13F65E2DC84465
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]

Building the Contained Release

Users are able to rebuild the target release themselves without having to fetch any of the dependencies. In order to do so, assuming that vendor.tar.gz and btcd-source-v0.20.1-beta.tar.gz are in the current directory, follow these steps:

tar -xvzf vendor.tar.gz
tar -xvzf btcd-source-v0.20.1.tar.gz
GO111MODULE=on go install -v -mod=vendor 
GO111MODULE=on go install -v -mod=vendor ./cmd/btcctl

The -mod=vendor flag tells the go build command that it doesn't need to fetch the dependencies, and instead, they're all enclosed in the local vendor directory.

Additionally, it's also possible to use the enclosed release.sh script to bundle a release for a specific system like so:

BTCBUILDSYS="linux-arm64 darwin-amd64" ./build/release/release.sh

Release Notes

The btcjson package as been updated to be compatible with bitcoind v0.19.0 as required by the lnd project.

A race condition in the server related to the set of known addresses for a peer has been eliminated.

We've cleaned up some logic that previously caused log spam due to the stricter version handshake we now enforce.

Changelog

The full list of changes since v0.20.0-beta can be found here:

• https://github.com/btcsuite/btcd/compare/v0.20.0-beta..v0.20.1-beta

Contributors (Alphabetical Order)

Olaoluwa Osuntokun Wilmer Paulino Eugene Zeigel