Update everything to btcd v2 modules

[guggero]

Depends on:

• Update to btcd v2 modules lightning-onion#78
• Update to btcd v2 modules btcsuite/btcwallet#1266
• Update to btcd v2 modules lightninglabs/neutrino#364

Change Description

After merging btcsuite/btcd#1825, we'll need to update all btcd dependencies to the new v2 modules.

With the PRs linked above, we have everything we need to update lnd to consume the new modules.

BUT: This will have quite a big impact on the wider ecosystem, as changing lnd will require all of the following projects to also update in order to ever be able to build litd again:

• Loop
• Pool
• Faraday
• Taproot Assets
• Lightning Terminal
• Server components of above mentioned projects

So keep that in mind when merging.

Though eventually this needs to be done, as the following PRs are now directly blocked on this:

• Add Silent Payment send support #9398
• Add BIP-0322 message signing to SignMessageWithAddr RPC #10798

Steps to Test

No functional changes, a green CI should

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the lnd project to consume the new v2 modules of btcd. This is a foundational change required to support recent updates in the btcsuite ecosystem. While this update is necessary to unblock other development efforts, it necessitates a coordinated update across the wider Lightning ecosystem projects to ensure continued build compatibility.

Highlights

• Dependency Update: Updated all btcd dependencies to their new v2 modules, following the recent changes in btcd.
• Module Migration: Migrated imports across the codebase to reflect the new v2 module paths for btcutil, chaincfg, chainhash, txscript, wire, and others.
• Ecosystem Impact: Noted that this change requires downstream projects (Loop, Pool, Faraday, Taproot Assets, Lightning Terminal) to also update their dependencies to remain compatible.

New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request performs a major dependency upgrade across the codebase, transitioning various github.com/btcsuite/btcd sub-modules (such as btcutil, wire, chaincfg, chainhash, txscript, and psbt) to their v2 versions, and introducing address/v2. The review feedback highlights that the go.mod file currently relies on personal forks in its replace block for several critical dependencies, which must be replaced with official tagged releases before merging to prevent security risks and dependency resolution issues for downstream projects.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The replace block uses personal forks (github.com/guggero/...) for several critical dependencies. Before this pull request is merged, these temporary replacements must be removed and replaced with official tagged releases of the upstream repositories. Relying on personal forks in a merged release of lnd introduces security risks and breaks dependency resolution for downstream projects (such as Loop, Pool, Faraday, etc.) that consume lnd as a module.

[github-actions]

PR Severity: CRITICAL. This PR (Update everything to btcd v2 modules) touches channeldb/channel.go, channeldb/codec.go, channeldb/db.go (CRITICAL: channeldb/), and 23 channeldb migration files (always CRITICAL per DB migration rule), plus 19 HIGH chainntnfs/ and chanacceptor/* files. 68 non-test files changed exceeds the 20-file bump threshold; 3509 total lines changed exceeds the 500-line bump threshold. Classification was already CRITICAL. <!-- pr-severity-bot -->

[Roasbeef]

LGTM 🌜

[ziggie1984]

/gateway review

[lightninglabs-gateway]

❌ gateway review failed: could not fetch PR context: {"level":"info","script":"fetch-pr-context.sh","event":"fetch","outcome":"attempt","step":"pr","path":"repos/lightningnetwork/lnd/pulls/10913"} {"level":"info","script":"fetch-pr-context.sh","event":"fetch","outcome":"attempt","step":"diff","path":"repos/lightningnetwork/lnd/pulls/10913"} {"level":"error","script":"fetch-pr-context.sh","event":"fetch_diff","outcome":"failure","message":"fetch diff failed: gh: Sorry, the diff exceeded the maximum number of files (300). Consider using 'List pull requests files' API or locally cloning the repository instead. (HTTP 406) "}

See workflow logs for details.

[ziggie1984]

LGTM

Reminder:

A lot of new replacement directives which we need to eventually tag and cleanup.