Skip to content

Releases: btcsuite/btcd

btcd v0.23.3

01 Nov 14:44
@guggero guggero
v0.23.3
This tag was signed with the committer’s verified signature.
guggero Oliver Gugger
GPG key ID: 8E4256593F177720
Learn about vigilant mode.
1d767de
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: 4AEE18F83AFDEB23
Learn about vigilant mode.
Compare
Choose a tag to compare
btcd v0.23.3 Latest
Latest

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://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/guggero.asc | gpg --import

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

gpg --verify manifest-guggero-v0.23.3.sig manifest-v0.23.3.txt

You should see the following if the verification was successful:

gpg: Signature made Di 01 Nov 2022 14:00:20 CET
gpg:                using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg: Good signature from "Oliver Gugger <gugger@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.

What's Changed

New Contributors

Full Changelog: v0.23.2...v0.23.3

Contributors

Roasbeef, guggero, and 2 other contributors
Assets 35

btcd v0.23.2

10 Oct 01:38
@Roasbeef Roasbeef
v0.23.2
This tag was signed with the committer’s verified signature.
Roasbeef Olaoluwa Osuntokun
GPG key ID: 3BBD59E99B280306
Learn about vigilant mode.
6b5418d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: 4AEE18F83AFDEB23
Learn about vigilant mode.
Compare
Choose a tag to compare
btcd v0.23.2

What's Changed

New Contributors

Full Changelog: v0.23.1...v0.23.2

Contributors

Roasbeef, shyba, and 3 other contributors
Assets 2

btcd v0.22.2

10 Oct 22:07
@Roasbeef Roasbeef
v0.22.2
This tag was signed with the committer’s verified signature.
Roasbeef Olaoluwa Osuntokun
GPG key ID: 3BBD59E99B280306
Learn about vigilant mode.
2ca4f4c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: 4AEE18F83AFDEB23
Learn about vigilant mode.
Compare
Choose a tag to compare
btcd v0.22.2

What's Changed

  • [release-v0.22.1] multi: Switch to chaincfg/chainhash module. by @davecgh in #1851
  • release: create release branch for v0.22.2 to backport block parsing issue by @Roasbeef in #1901

Full Changelog: v0.22.1...v0.22.2

Contributors

Roasbeef and davecgh
Assets 2

btcd v0.23.1-beta

30 Aug 23:01
@Roasbeef Roasbeef
v0.23.1
This tag was signed with the committer’s verified signature.
Roasbeef Olaoluwa Osuntokun
GPG key ID: 3BBD59E99B280306
Learn about vigilant mode.
04aac1e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: 4AEE18F83AFDEB23
Learn about vigilant mode.
Compare
Choose a tag to compare
btcd v0.23.1-beta

What's Changed

New Contributors

Full Changelog: v0.22.0-beta...v0.23.1

Contributors

dekokun, naveensrinivasan, and 24 other contributors
Assets 2

btcd v0.22.0-beta

08 Jun 14:18
@jcvernaleo jcvernaleo
v0.22.0-beta
This tag was signed with the committer’s verified signature.
jcvernaleo John C. Vernaleo
GPG key ID: B15210D35378BD54
Learn about vigilant mode.
63438c6
Compare
Choose a tag to compare
btcd v0.22.0-beta

This release of btcd is primarily to act as a catchup for the various changes that have accumulated.

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:

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

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

You should see the following if the verification was successful:

gpg: assuming signed data in 'manifest-v0.22.0-beta.txt'
gpg: Signature made Tue 08 Jun 2021 10:07:53 AM EDT
gpg:                using DSA key 0DB39EAF526568682088EEDFB15210D35378BD54
gpg: Good signature from "John C. Vernaleo <john@netpurgatory.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.16.5, 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.22.0-beta

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

gpg: Signature made Tue 08 Jun 2021 09:42:52 AM EDT
gpg:                using DSA key 0DB39EAF526568682088EEDFB15210D35378BD54
gpg: Good signature from "John C. Vernaleo <john@netpurgatory.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.22.0-beta.tar.gz are in the current directory, follow these steps:

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

Protocol and network-related changes:

  • Added support for witness tx and block in notfound msg. (#1625)

  • Added support for receiving sendaddrv2 messages from a peer. (#1670)

  • Fixed bug in peer package causing last block height to go backwards. (#1606)

  • Added chain parameters for connecting to the public Signet network. (#1692, #1718)

    Also added --signet command line flag to btcctl and btcd utilities.

Crypto changes:

  • Fixed bug causing panic due to bad R and S signature components in btcec.RecoverCompact. (#1691)
  • Set the name (secp256k1) in the CurveParams of the S256 curve. (#1565)

Notable developer-related package changes:

  • Improve gc for txscript.IsUnspendable method. (#1615)

    Significantly reduced allocations, which should bring a performance gain during sync.

  • Used RLock/RUnlock when possible in the addrmgr package. (#1697)

  • Removed unknown block version warning in the blockchain package, due to false positives triggered by AsicBoost. (#1463)

  • Added proper types for flag field and improve docs, for msgtx in the wire package. (#1632)

  • Added chaincfg.RegisterHDKeyID function to populate HD key ID pairs. (#1617)

  • Fixed flaky hash cache test due to resetting RNG. (#1689)

  • Added new method mining.AddWitnessCommitment to add the witness commitment as an OP_RETURN output within the coinbase transaction. (#1716)

RPC changes:

  • Implemented Batch JSON-RPC in rpcclient and server. (#1583)

    Please refer to rpcclient/examples/bitcoincorehttpbulk/README.md for examples.

  • Implemented rpcclient method to invoke getdescriptorinfo JSON-RPC command. (#1578)

  • Updated the rpcserver handler for validateaddress JSON-RPC command to have parity with the bitcoind 0.20.0 interface. (#1613)

  • Implemented rpcclient method to invoke getblockfilter JSON-RPC command. (#1579)

  • Implemented signmessagewithprivkey JSON-RPC command in rpcserver. (#1585)

  • Implemented rpcclient method to invoke importmulti JSON-RPC command. (#1579)

  • Implemented watchOnly argument in rpcclient method to invoke listtransactions JSON-RPC command. (#1628)

  • Updated btcjson.ListTransactionsResult for compatibility with Bitcoin Core 0.20.0. (#1626)

    Two new fields BlockHeight and Label were added as optional, to keep backwards compatibility.

  • Implemented nullable optional JSON-RPC parameters. (#1594)

    Fixed command marshalling dropping params that follow params with nil value.

  • Implemented rpcclient and server method to invoke getnodeaddresses JSON-RPC command. (#1590)

  • Implemented rpcclient methods to invoke PSBT JSON-RPC commands. (#1596)

    The walletcreatefundedpsbt and walletprocesspsbt commands were implemented.

  • Implemented rpcclient method to invoke listsinceblock with the include_watchonly parameter enabled. (#1451)

  • Implemented rpcclient method to invoke deriveaddresses JSON-RPC command. (#1631)

  • Implemented rpcclient method to invoke getblocktemplate JSON-RPC command. (#1629)

    The corresponding btcjson structs were also updated to reflect changes in Bitcoin Core.

  • Implemented rpcclient method to invoke getaddressinfo JSON-RPC command. (#1633)

  • Implemented rpcclient method to invoke getwalletinfo JSON-RPC command. (#1638)

  • Fixed error message in rpcserver when an unknown RPC command is encountered. (#1695)

  • Fixed error message returned by estimatefee when the number of blocks exceeds the max depth. (#1678)

  • Updated btcjson.GetBlockChainInfoResult to include new fields in Bitcoin Core. (#1676)

    Two new fields InitialBlockDownload and SizeOnDisk were added.

  • Added ExtraHeaders in rpcclient.ConnConfig struct. (#1669)

    It's useful when the RPC provider needs customized headers, for example, the X-Auth-Token header.

  • Fixed bitcoind compatibility issue with the sendrawtransaction JSON-RPC command. (#1659)

  • Added new JSON-RPC errors to btcjson package, and documented them. (#1648)

  • Implemented rpcclient method to invoke createwallet JSON-RPC command. (#1650)

    This is also the first rpcclient method that uses the functional options pattern, which will be used more and more in future.

  • Implemented rpcclient methods to invoke backupwallet, dumpwallet, loadwallet and unloadwallet JSON-RPC commands. (#1645)

  • Fixed unmarshalling error in getmininginfo JSON-RPC command, for valid integers in scientific notation. (#1644)

  • Implemented rpcclient method to invoke gettxoutsetinfo JSON-RPC command. (#1641)

  • Implemented rpcclient method to invoke signrawtransactionwithwallet JSON-RPC command. (#1642)

  • Added txid to getblocktemplate response of rpcserver. (#1639)

  • Fixed monetary unit used in createrawtransaction JSON-RPC command in rpcserver. (#1614)

  • Added rawtx field to btcjson.GetBlockVerboseTxResult to provide backwards compatibility with older versions of Bitcoin Core. (#1677)

Misc changes:

Changelog

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

Contributors (Alphabetical Order)

10gic
Andrew Tugarinov
Anirudha Bose
Appelberg-s
Armando Ochoa
Aurèle Oulès
Calvin Kim
Christian Lehmann
Conner Fromknecht
Dan Cline
David Mazary
Elliott Minns
Federico Bond
Friedger Müffke
Gustavo Chain
Hanjun Kim
Henry Fisher
Iskander Sharipov
Jake Sylvestre
Johan T. Halseth
John C. Vernaleo
Liran Sharir
Mikael Lindlof
Olaoluwa Osuntokun
Oliver Gugger
Rjected
Steven Kreuzer
Torkel Rogstad
Tristyn
Victor Lavaud
Vinayak Borkar
Wilmer Paulino
Yaacov Akiba Slama
ebiiim
ipriver
wakiyamap
yyforyongyu

Assets 35

btcd v0.21.0-beta

28 Aug 20:40
@jcvernaleo jcvernaleo
v0.21.0-beta
This tag was signed with the committer’s verified signature.
jcvernaleo John C. Vernaleo
GPG key ID: B15210D35378BD54
Learn about vigilant mode.
56cc42f
Compare
Choose a tag to compare
btcd v0.21.0-beta

This release of btcd is primarily to act as a catchup for the various changes that have accumulated and to help move back to a more regular schedule.

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:

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

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

You should see the following if the verification was successful:

gpg: assuming signed data in 'manifest-v0.21.0-beta.txt'
gpg: Signature made Fri 28 Aug 2020 12:40:24 PM EDT
gpg:                using DSA key 0DB39EAF526568682088EEDFB15210D35378BD54
gpg: Good signature from "John C. Vernaleo <john@netpurgatory.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.14, 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.21.0-beta

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

gpg: Signature made Fri 28 Aug 2020 09:58:10 AM EDT
gpg:                using DSA key 0DB39EAF526568682088EEDFB15210D35378BD54
gpg: Good signature from "John C. Vernaleo <john@netpurgatory.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.21.0-beta.tar.gz are in the current directory, follow these steps:

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

Network-related changes:

  • Handle notfound messages from peers in netsync package. (#1603)

RPC changes:

  • The Verbose and VerboseTx boolean fields in btcjson.GetBlockCmd have been replaced with a single integer field called Verbosity, to reflect the new getblock RPC call parameters introduced in Bitcoin Core 0.15.0. (#1529)

    The getblock RPC server command in btcd has also been updated with this change.
    Backwards compatibility has been maintained in rpcclient. (#1577)

  • Added an optional Params field to rpcclient.ConnConfig, to represent the network that the server is running. (#1467)

  • Added a new error code ErrRPCInWarmup in btcjson. (#1541)

  • Updated btcjson.GetMempoolEntryResult to reflect the new getmempoolentry response in Bitcoin Core 0.19.0. (#1524)

  • Implemented rpcclient methods to invoke estimatesmartfee and generatetoaddress JSON-RPC commands. (#1500)

  • Implemented rpcclient method to invoke getblockstats JSON-RPC command. (#1500)

  • Parse serialized transaction from createrawtransaction JSON-RPC command using both segwit, and legacy format. (#1502)

  • Support cookie-based authentication using a new CookiePath field in rpcclient.ConnConfig. (#1460)

  • Implemented rpcclient method to invoke getchaintxstats JSON-RPC command. (#1571)

  • Implemented rpcclient method to invoke fundrawtransaction JSON-RPC command. (#1553)

  • Implemented rpcclient method to invoke getbalances JSON-RPC command. (#1595)

  • Added a new method rpcclient.GetTransactionWatchOnly to support passing the include_watchonly argument to gettransaction JSON-RPC command. (#1592)

Crypto changes:

  • Fixed panic in fieldVal.SetByteSlice when called with a value larger than 32 bytes. The improved version is approximately 35% faster. (#1602)

btcctl changes:

  • Added -regtest mode to btcctl. (#1556)

Misc changes:

  • Fixed a bug due to a deadlock in connmgr's dynamic ban scoring. (#1509)
  • Replaced TravisCI with GitHub Actions. (#1575)
  • Improved chain state init efficiency. (#1580)
  • Added blockchain.NewUtxoEntry() to directly create entries for UtxoViewpoint. (#1588)
  • Switch to a generic LRU implementation in the peer package, from decred/dcrd. (#1599)

Changelog

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

Contributors (Alphabetical Order)

Anirudha Bose
Antonin Hildebrand
Dan Cline
Daniel McNally
David Hill
Federico Bond
George Tankersley
Henry
Henry Harder
Iskander Sharipov
Ivan Kuznetsov
Jake Sylvestre
Javed Khan
JeremyRand
Jin
John C. Vernaleo
Kulpreet Singh
Mikael Lindlof
Murray Nesbitt
Nisen
Olaoluwa Osuntokun
Oliver Gugger
Steven Roose
Torkel Rogstad
Tyler Chambers
Wilmer Paulino
Yash Bhutwala
adiabat
jalavosus
mohanson
qqjettkgjzhxmwj
qshuai
shuai.qi
tpkeeper

Assets 36

btcd v0.20.1-beta

13 Nov 03:29
@Roasbeef Roasbeef
v0.20.1-beta
This tag was signed with the committer’s verified signature. The key expired after the commit was signed.
Roasbeef Olaoluwa Osuntokun
GPG key ID: BC13F65E2DC84465
Expired
Learn about vigilant mode.
f3ec130
This commit was signed with the committer’s verified signature. The key expired after the commit was signed.
Roasbeef Olaoluwa Osuntokun
GPG key ID: BC13F65E2DC84465
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
btcd v0.20.1-beta

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:

Contributors (Alphabetical Order)

Olaoluwa Osuntokun
Wilmer Paulino
Eugene Zeigel

Assets 36

btcd v0.20.0-beta

15 Oct 08:24
@Roasbeef Roasbeef
v0.20.0-beta
This tag was signed with the committer’s verified signature. The key expired after the commit was signed.
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 expired after the commit was signed.
Roasbeef Olaoluwa Osuntokun
GPG key ID: BC13F65E2DC84465
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
btcd v0.20.0-beta

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

btcd v0.12.0-beta

21 Nov 17:33
@davecgh davecgh
BTCD_0_12_0_BETA
cea5d3c
Compare
Choose a tag to compare
btcd v0.12.0-beta Pre-release
Pre-release

Protocol and network related changes:

  • Add a new checkpoint at block height 382320 (#555)
  • Implement BIP0065 which includes support for version 4 blocks, a new consensus opcode (OP_CHECKLOCKTIMEVERIFY) that enforces transaction lock times, and a double-threshold switchover mechanism (#535, #459, #455)
  • Implement BIP0111 which provides a new bloom filter service flag and hence provides support for protocol version 70011 (#499)
  • Add a new parameter --nopeerbloomfilters to allow disabling bloom filter support (#499)
  • Reject non-canonically encoded variable length integers (#507)
  • Add mainnet peer discovery DNS seed (seed.bitcoin.jonasschnelli.ch) (#496)
  • Correct reconnect handling for persistent peers (#463, #464)
  • Ignore requests for block headers if not fully synced (#444)
  • Add CLI support for specifying the zone id on IPv6 addresses (#538)
  • Fix a couple of issue where the initial block sync could stall (#518, #229, #486)
  • Fix an issue which prevented the --onion option from working as intended (#446)

Transaction relay (memory pool) changes:

  • Require transactions to only include signatures encoded with the canonical 'low-s' encoding (#512)
  • Add a new parameter --minrelaytxfee to allow the minimum transaction fee in BTC/kB to be overridden (#520)
  • Retain memory pool transactions when they redeem another one that is removed when a block is accepted (#539)
  • Do not send reject messages for a transaction if it is valid but causes an orphan transaction which depends on it to be determined as invalid (#546)
  • Refrain from attempting to add orphans to the memory pool multiple times when the transaction they redeem is added (#551)
  • Modify minimum transaction fee calculations to scale based on bytes instead of full kilobyte boundaries (#521, #537)

Implement signature cache:

  • Provides a limited memory cache of validated signatures which is a huge optimization when verifying blocks for transactions that are already in the memory pool (#506)
  • Add a new parameter --sigcachemaxsize which allows the size of the new cache to be manually changed if desired (#506)

Mining support changes:

  • Notify getblocktemplate long polling clients when a block is pushed via submitblock (#488)
  • Speed up getblocktemplate by making use of the new signature cache (#506)

RPC changes:

  • Implement getmempoolinfo command (#453)
  • Implement getblockheader command (#461)
  • Modify createrawtransaction command to accept a new optional parameter locktime (#529)
  • Modify listunspent result to include the spendable field (#440)
  • Modify getinfo command to include errors field (#511)
  • Add timestamps to blockconnected and blockdisconnected notifications (#450)
  • Several modifications to searchrawtranscations:
    • Accept a new optional parameter vinextra which causes the results to include information about the outputs referenced by a transaction inputs (#485, #487)
    • Skip entries in the mempool too (#495)
    • Accept a new optional parameter reverse to return the results in reverse order (most recent to oldest) (#497)
    • Accept a new optional parameter filteraddrs which causes the results to only include inputs and outputs which involve the provided addresses (#516)
  • Change the notification order to notify clients about mined transactions (recvtx, redeemingtx) before the blockconnected notification (#449)
  • Update verifymessage RPC to use the standard algorithm so it is compatible with other implementations (#515)
  • Improve ping statistics by pinging on an interval (#517)

Websocket changes:

  • Implement session command which returns a per-session unique id (#500, #503)

btcctl utility changes:

  • Add getmempoolinfo command (#453)
  • Add getblockheader command (#461)
  • Add getwalletinfo command (#471)

Notable developer-related package changes:

  • Introduce a new peer package which acts a common base for creating and concurrently managing bitcoin network peers (#445)
  • Blocks heights now consistently use int32 everywhere (#481)
  • The BlockHeader type in the wire package now provides the BtcDecode and BtcEncode methods (#467)
  • Update wire package to recognize BIP0064 (getutxo) service bit (#489)
  • Export LockTimeThreshold constant from txscript package (#454)
  • Export MaxDataCarrierSize constant from txscript package (#466)
  • Provide new IsUnspendable function from the txscript package (#478)
  • Export variable length string functions from the wire package (#514)
  • Export DNS Seeds for each network from the chaincfg package (#544)
  • Preliminary work towards separating the memory pool into a separate package (#525, #548)

Misc changes:

Contributors (alphabetical order):

  • Ben Echols
  • Bruno Clermont
  • danda
  • Daniel Krawisz
  • Dario Nieuwenhuis
  • Dave Collins
  • David Hill
  • Javed Khan
  • Jonathan Gillham
  • Joseph Becher
  • Josh Rickmar
  • Justus Ranvier
  • Mawuli Adzoe
  • Olaoluwa Osuntokun
  • Rune T. Aune

MSI Checksums:

SHA256(btcd_standalone_0.12.0-beta_x64.msi)= 024274804600e0a37ba5e7ac5abc9fdfe91b071e92c9251f38f01bec6785fb77
SHA256(btcd_standalone_0.12.0-beta_x86.msi)= b122bb7cd29e0e5e32ada279a12eeef3d44d58f3bb377ea7ce8b1f42ca0bdba3
SHA512(btcd_standalone_0.12.0-beta_x64.msi)= 725266286cb5ba62d435b992353b83aef4a3586e5ee9aeecfcc90b8026225f12c081471d56fb0f02d92ca5d92965eb99429209125b108c47599c8b1b619fb852
SHA512(btcd_standalone_0.12.0-beta_x86.msi)= d2849eef7cce9ec88a9538940c3ebfb08c2ecbf4be88f4029552bac5db2cdc203e31e8a401cf54dab694d4f49dd640bc8bb962cb5d70227bde91d785364823cb
Assets 4

btcd v0.11.1-beta

27 May 17:20
@davecgh davecgh
BTCD_0_11_1_BETA
d12b3a1
Compare
Choose a tag to compare
btcd v0.11.1-beta Pre-release
Pre-release

Protocol and network related changes:

  • Use correct sub-command in reject message for rejected transactions (#436, #437)
  • Add a new parameter --torisolation which forces new circuits for each connection when using tor (#430)

Transaction relay (memory pool) changes:

  • Reduce the default number max number of allowed orphan transactions to 1000 (#419)
  • Add a new parameter --maxorphantx which allows the maximum number of orphan transactions stored in the mempool to be specified (#419)

RPC changes:

  • Modify listtransactions result to include the involveswatchonly and vout fields (#427)
  • Update getrawtransaction result to omit the confirmations field when it is 0 (#420, #422)
  • Update signrawtransaction result to include errors (#423)

btcctl utility changes:

  • Add gettxoutproof command (#428)
  • Add verifytxoutproof command (#428)

Notable developer-related package changes:

  • The btcec package now provides the ability to perform ECDH encryption and decryption (#375)
  • The block and header validation in the blockchain package has been split to help pave the way toward concurrent downloads (#386)

Misc changes:

  • Minor peer optimization (#433)

Contributors (alphabetical order):

  • Dave Collins
  • David Hill
  • Federico Bond
  • Ishbir Singh
  • Josh Rickmar

MSI Checksums:

SHA256(btcd_standalone_0.11.1-beta_x64.msi)= 14d5a2aaa3cbbcd37a706c9cd8918093d93f9cc826f0eed3af213c673089f126
SHA256(btcd_standalone_0.11.1-beta_x86.msi)= eb6e558a81e406d4497de1ad5ca94b12d57be62745fdcc1669b254716f5aa1c0
SHA512(btcd_standalone_0.11.1-beta_x64.msi)= 2519b2c8e2990e9cdc4ae36f236ed7544848890fd4f8b0ff4e1a7596099806feb39aa47c4e10c231c51f115daf12e4484a6a85958877589e792bb95dd2519781
SHA512(btcd_standalone_0.11.1-beta_x86.msi)= 74d52f60feef618055556a779b38f0773df8e997e1c691db6559dea28f5e0784f8f362cf3f37dc7cd91f22cc7ae9e17940955da8b81d903910e06d3f9ae8523c
Assets 4