Skip to content

btcd v0.20.0-beta
Compare
Choose a tag to compare
@Roasbeef Roasbeef released this 15 Oct 08:24
· 836 commits to master since this release
v0.20.0-beta
This tag was signed with the committer’s verified signature. The key has expired.
Roasbeef Olaoluwa Osuntokun
GPG key ID: BC13F65E2DC84465
Expired
Learn about vigilant mode.
a41498d
This commit was signed with the committer’s verified signature. The key has expired.
Roasbeef Olaoluwa Osuntokun
GPG key ID: BC13F65E2DC84465
Expired
Learn about vigilant mode.

This marks btcd's first release in nearly 5 years! Long live btcd ✊!!! One major change with this release, and all releases going forward for the foreseeable future is that Olaoluwa Osuntokun (roasbeef) is now the primary maintainer of btcd. As a result, rather than the existing conformal keys, roasbeef's key will be used in place for signing all git tags and releases. Going forward, our goal is to adopt a regular 3-month (or so) release cycle as needed.

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.0-beta.txt and manifest-v0.20.0-beta.txt.sig are in the current directory) with:

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

You should see the following if the verification was successful:

gpg: assuming signed data in 'manifest-v0.20.0-beta.txt'
gpg: Signature made Tue Oct 22 15:51:12 2019 PDT
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.0-beta

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

gpg: Signature made Tue 15 Oct 2019 08:13:46 AM UTC using RSA key ID 2DC84465
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>"
Primary key fingerprint: 9769 140D 255C 759B 1EB7  7B46 A963 87A5 7CAA E94D
     Subkey fingerprint: 4AB7 F8DA 6FAE BB3B 70B1  F903 BC13 F65E 2DC8 4465

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.0-beta.tar.gz are in the current directory, follow these steps:

tar -xvzf vendor.tar.gz
tar -xvzf btcd-source-v0.20.0.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

Rather than summarize 5 years of development in the release notes below, we've opted to mention only the most major features. Future releases will return to our prior method of enumerating each change in relevant areas of the codebase/system.

Changelog

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

Contributors (Alphabetical Order)

Albert Puigsech Galicia
Alex Akselrod
Alex Bosworth
Alex Manuskin
Alok Menghrajani
Anatoli Babenia
Andy Weidenbaum
Calvin McAnarney
Chris Martin
Chris Pacia
Chris Shepherd
Conner Fromknecht
Craig Sturdy
Cédric Félizard
Daniel Krawisz
Daniel Martí
Daniel McNally
Dario Nieuwenhuis
Dave Collins
David Hill
David de Kloet
GeertJohan
Grace Noah
Gregory Trubetskoy
Hector Jusforgues
Iskander (Alex) Sharipov
Janus Troelsen
Jasper
Javed Khan
Jeremiah Goyette
Jim Posen
Jimmy Song
Johan T. Halseth
John C. Vernaleo
Jonathan Gillham
Josh Rickmar
Jon Underwood
Jonathan Zeppettini
Jouke Hofman
Julian Meyer
Kai
Kamil Slowikowski
Kefkius
Leonardo Lazzaro
Marco Peereboom
Marko Bencun
Mawueli Kofi Adzoe
Michail Kargakis
Mitchell Paull
Nathan Bass
Nicola 'tekNico' Larosa
Olaoluwa Osuntokun
Pedro Martelletto
Ricardo Velhote
Roei Erez
Ruben de Vries
Rune T. Aune
Sad Pencil
Shuai Qi
Steven Roose
Tadge Dryja
Tibor Bősze
Tomás Senart
Tzu-Jung Lee
Vadym Popov
Waldir Pimenta
Wilmer Paulino
benma
danda
dskloet
esemplastic
jadeblaquiere
nakagawa
preminem
qshuai

Assets 36