Skip to content

Releases: btcsuite/btcd

v0.26.2

Choose a tag to compare

@Roasbeef Roasbeef released this 24 Jul 23:51
v0.26.2
05585e0

What's Changed

  • multi: reject trailing characters when parsing inputs by @starius in #2558
  • psbt: reject trailing final witness data by @starius in #2567
  • netsync: avoid clock tick race in sync state test by @starius in #2564
  • psbt: compact witness utxo scripts after parsing by @starius in #2563
  • btcec/schnorr: reject s >= group order in ParseSignature by @Lrifton92 in #2561
  • blockchain/indexers: fix dropped error by @alrs in #2486
  • psbt: reject nil taproot leaf scripts by @0xjc65eth in #2539
  • btcutil: reject out-of-range private keys in DecodeWIF by @Lrifton92 in #2545
  • multi: tighten inbound connection admission by @starius in #2576
  • address: reject v2-v16 segwit addresses encoded with bech32 (BIP-350) by @Lrifton92 in #2544
  • multi: relax trailing byte handling for DB blocks and PSBT readers by @Roasbeef in #2575
  • rpcclient: make HTTP Basic Auth optional via DisableAuth by @ThomsenDrake in #2514
    /pull/2580

New Contributors

Full Changelog: v0.26.0...v0.26.2

v0.26.0

Choose a tag to compare

@Roasbeef Roasbeef released this 18 Jun 23:03
v0.26.0
280d4d2

What's Changed

New Contributors

Full Changelog: v0.25.0...v0.26.0

v0.26.0-beta.rc1

v0.26.0-beta.rc1 Pre-release
Pre-release

Choose a tag to compare

@Roasbeef Roasbeef released this 20 May 23:08
v0.26.0-beta.rc1
b3cbf4f

What's Changed

New Contributors

Full Changelog: v0.25.0...v0.26.0-beta.rc1

v0.25.0

Choose a tag to compare

@Roasbeef Roasbeef released this 04 Nov 02:03
v0.25.0
e764c17

What's Changed

New Contributors

Full Changelog: v0.24.2...v0.25.0

v0.25.0-beta.rc1

v0.25.0-beta.rc1 Pre-release
Pre-release

Choose a tag to compare

@Roasbeef Roasbeef released this 25 Sep 01:55
v0.25.0-beta.rc1
e8097a1

What's Changed

New Contributors

Full Changelog: v0.24.2...v0.25.0-beta.rc1

v0.24.2

Choose a tag to compare

@Roasbeef Roasbeef released this 25 Jun 20:44
cc26860

This release includes important bug fixes related to subtle interactions related to re-orgs and the UTXO set cache. These fixed are considered security critical.

This release also includes implementations of invalidateblock and reconsiderblock which can be useful in helping nodes that were afflicted by the aforementioned bugs to recover without needing to resync the entire chain.

WIth this release, btcd now also implements the testmempoolaccept RPC which can be useful to check a transaction candidate for validity from a policy and conflict perspective before broadcasting. Along the way, we've added some additional policy checks that exist in other Bitcoin full node implementations.

This release also contains fixes to some parsing issues discovered via fuzz testing.

Finally, as mentioned above release includes important security fixes, with full details to be disclosed in 90 days.

What's Changed

New Contributors

Full Changelog: v0.24.0...v0.24.2

v0.24.2-beta.rc1

v0.24.2-beta.rc1 Pre-release
Pre-release

Choose a tag to compare

@Roasbeef Roasbeef released this 18 Mar 22:02
8b2f43e

What's Changed

New Contributors

Full Changelog: v0.24.0...v0.24.2-beta.rc1

btcd v0.24.0

Choose a tag to compare

@Roasbeef Roasbeef released this 31 Dec 01:22
b1b9420

This release is a major release that includes several general bug fixes, security bug fixes (please update!), and also a series of performance improvements that dramatically reduce the time for initial block download from ~45 hours+ to around 6 hours! With this release,btcd now also supports BIP 155 and has gained support for pruning (--prune=MiB).

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/roasbeef.asc | gpg --import

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

gpg --verify manifest-roasbeef-v0.24.0.sig manifest-v0.24.0.txt

You should see the following if the verification was successful:

gpg: Signature made Sat Dec 30 17:11:22 2023 PST
gpg:                using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
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.

What's Changed

New Contributors

Read more

btcd v0.23.3

Choose a tag to compare

@guggero guggero released this 01 Nov 14:44
v0.23.3
1d767de

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

btcd v0.23.2

Choose a tag to compare

@Roasbeef Roasbeef released this 10 Oct 01:38
6b5418d

What's Changed

New Contributors

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