diadata icon indicating copy to clipboard operation
diadata copied to clipboard

Published 20 hours ago • verified publisher icon diadata-org

Bump github.com/btcsuite/btcd from 0.22.0-beta to 0.24.0 in /cmd/services/filtersBlockService

Open dependabot[bot] opened this issue 9 months ago • 0 comments

Bumps github.com/btcsuite/btcd from 0.22.0-beta to 0.24.0.

Release notes

Sourced from github.com/btcsuite/btcd's releases.

btcd v0.24.0

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 <[email protected]>" [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

... (truncated)

Commits
  • b1b9420 Merge pull request #2082 from btcsuite/btcd-24
  • 4ec8f01 rpcclient: fix race condition in doDisconnect
  • 8d2ab63 build: bump version to btcd v0.24
  • 3c24785 chaincfg: update mainnet block hashes
  • bf23715 btcd: add SECURITY.md
  • d64de4a build: update to btcutil v1.1.5
  • 16684f6 Merge pull request #2073 from Roasbeef/wire-opts
  • 790c570 Merge pull request #2081 from Roasbeef/dont-serialize-tx-for-txhash
  • b0e9636 wire: consistently use defer for returning scratch buffers
  • e102a81 btcutil: add benchmarks for Hash + WitnessHash
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.

dependabot[bot] avatar May 06 '24 14:05 dependabot[bot]