Bump github.com/btcsuite/btcd from 0.23.4 to 0.24.0

[dependabot]

Bumps github.com/btcsuite/btcd from 0.23.4 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

• Musig2: Update to 1.0.0.rc2 by @​sputn1ck in btcsuite/btcd#1913
• btcec/schnorr/musig2: fix BenchmarkPartialVerify by @​Roasbeef in btcsuite/btcd#1920
• base58: fix decoding issue by @​guggero in btcsuite/btcd#1923
• Update Docker documentation towards building your own image by @​guiand888 in btcsuite/btcd#1925
• chainhash: JSON marshal hash as string by @​ffranr in btcsuite/btcd#1932
• Update Dockerfile to Alpine 3.16 by @​guiand888 in btcsuite/btcd#1924
• Fix memory leak in connmanager by @​hxw in btcsuite/btcd#1576
• Update mining.md by @​jagottsicher in btcsuite/btcd#1938
• Sighash taproot keyspend bug fix by @​Roasbeef in btcsuite/btcd#1941
• btcutil/psbt: export helper functions, fix/add encoding of unknown fields by @​guggero in btcsuite/btcd#1942
• docs: Update Go version as per the Readme. by @​hristog in btcsuite/btcd#1944
• txscript: Fix typo in IsUnspendable() comment by @​kcalvinalvin in btcsuite/btcd#1945
• txscript: allow script builder capacity to be specified by @​guggero in btcsuite/btcd#1954
• Export MakeScritpNum, AsSmallInt, and IsSmallInt by @​martonp in btcsuite/btcd#1956
• chainhash: JSON Unmarshal hash from appropriate string. by @​LindenWang01 in btcsuite/btcd#1952
• psbt: add verification method for utxo data by @​ziggie1984 in btcsuite/btcd#1964
• txscript: fix typos by @​hieblmi in btcsuite/btcd#1957
• chaincfg: Update checkpoints by @​kcalvinalvin in btcsuite/btcd#1968
• btcd: Add memory profiling flag by @​kcalvinalvin in btcsuite/btcd#1953
• blockchain: Use slices when fetching utxos by @​kcalvinalvin in btcsuite/btcd#1972
• main: Update README.md's minimum go version by @​kcalvinalvin in btcsuite/btcd#1977

... (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 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.

[coderabbitai]

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.