LND

channeldb: add tests for DeleteForwardingEvents

In this commit, we add test coverage for the new DeleteForwardingEvents
method. The tests cover basic deletion, partial deletion by time range,
batch processing across multiple transactions, idempotency, empty
database handling, and exact boundary conditions.

Property-based tests using the rapid package validate key invariants
across randomized inputs: correct event counts, fee calculation
accuracy, time boundary enforcement, and idempotent behaviour.

docs: add release notes for v1 taproot funding script fix

graph/db: honor taproot feature bit in v1 funding script construction

Fix FundingPKScript() to check for the taproot staging feature bit on
v1 channel edges. When present, reconstruct a taproot funding script
via GenTaprootFundingScript instead of the legacy P2WSH multisig.

This is a pre-existing bug: private taproot channels have always been
stored as v1 gossip objects with the taproot feature bit, but
FundingPKScript() never checked for it. The discovery/gossiper layer
(makeFundingScript) already handled this correctly on the insertion
path, but any read path that called FundingPKScript() -- notably
ChannelView() used for chain filter reconstruction on restart --
would produce the wrong script.

Update the tests from the previous commit to assert the correct
taproot funding script instead of the legacy P2WSH script.

graph/db: add tests to document v1 taproot funding script bug

Private taproot channels are currently represented in the gossip/graph
layer as v1 gossip objects with the SimpleTaprootChannelsRequiredStaging
feature bit set on the v1 ChannelAnnouncement1.

However, FundingPKScript() on a v1 ChannelEdgeInfo unconditionally
reconstructs a legacy 2-of-2 P2WSH multisig script, ignoring the
taproot feature bit entirely. This means that code paths such as
ChannelView() (used to rebuild the chain watch filter on restart)
produce the wrong funding script for these channels.

This bug has always been present since private taproot channels were
first introduced. The discovery/gossiper path (makeFundingScript)
correctly honors the taproot bit when validating announcements on
insertion, but the graph DB read paths never did.

Add failing tests at both the model level (FundingPKScript) and the
graph level (ChannelView round-trip) to document this mismatch. The
next commit fixes the behavior so these tests pass.

docs: update release note

lnwire: remove stale pong limit error

Drop the unused pong limit decode error now that ping deserialization
accepts the full uint16 wire range. Update the randomized ping generator
to cover the full range so the property tests exercise the no-reply
sentinel values too.

lnwire+peer: ignore no-reply pings

Allow pings in the BOLT 1 no-reply range to decode and be ignored
instead of disconnecting peers. This keeps reconnects compatible with
peers that pad channel_reestablish with no-reply pings.

peer: include ping pong-size in debug summaries

Expose num_pong_bytes in the ping message summary so ignored no-reply
pings are visible in debug logs. Add a focused test covering the summary
output for the sentinel range.

gitignore: ignore `.worktrees`

make: add `lint-native` target for running linter without Docker

In this commit, we add a new `make lint-native` target that builds and
runs the custom golangci-lint binary directly on the host, bypassing
Docker entirely. On macOS in particular, the Docker volume sync overhead
makes `make lint` painfully slow for iterative development.

The native target builds `custom-gcl` from the `tools/` directory using
`go tool golangci-lint custom`, then runs it with `GOWORK=off` and
`--new-from-rev=$(git merge-base HEAD master)` so only changes on the
current branch are linted.

lnwallet: add tests for LocalNonces sync

lnwallet+channeldb: integrate LocalNonces in channel sync logic

lnwire: update ChannelReestablish with LocalNonces field

Extends the ChannelReestablish message to include a new optional
LocalNonces field alongside the existing LocalNonce field. This enables
backwards-compatible transmission of multiple nonces for different
purposes during channel reestablishment.

Changes include:
- Add LocalNonces field to ChannelReestablish struct
- Update Encode/Decode methods to handle the new TLV field
- Extend property-based testing to randomly include LocalNonces
- Maintain full backwards compatibility with existing LocalNonce field

lnwire: add LocalNonces TLV structure and tests

This commit introduces a new TLV structure LocalNoncesData that contains
a map of transaction IDs to MuSig2 nonces. This structure enables
coordinating multiple nonces for different purposes (e.g., channel
commits, splice operations) within a single wire message.

This is a prep for upcoming spec changes to allow a party that has
in-prorgess splices to tell the remote party which nonces to use for
which splice.

docs: add release notes for missing lncli tags fix

routerrpc: add missing lncli tags for RPC documentation

Add lncli: tags to SendPaymentV2, SendToRouteV2, and EstimateRouteFee
proto definitions so the generated API docs correctly show their
corresponding CLI commands (sendpayment, sendtoroute, estimateroutefee)
instead of "There is no CLI command for this RPC".

lnrpc: add lncli command hint for API docs generator

lncli: add `sign` subcommand to `lncli wallet psbt`

Adds a new sub command `lncli wallet psbt sign` to `lncli` that calls
the wallet RPC's `SignPsbt` method.

docs: add release notes

lntest: disable bitcoind v2 P2P transport in itests

bitcoind v29 attempts a v2 P2P handshake when connecting to the btcd
miner, but btcd doesn't support v2 transport. The handshake times out
after 30s before falling back to v1, which consumes the entire
DefaultTimeout budget and causes flakes in tests that rely on timely
block propagation after reconnecting (e.g. open_channel_reorg_test).

Add -v2transport=0 to both the itest chain backend and the bitcoind
miner backend, matching what the unit test backend already does.

peer: add mock BestBlockView to test peer config

The test Config in createTestPeer left BestBlockView nil. When the
PingManager's timer fires during a test, it calls
BestBlockView.BestBlockHeader() which panics on the nil receiver.
This was a flaky failure since it depended on a race between the
timer and test completion.

Add a trivial mockBestBlockView that returns an empty block header
and wire it into the test Config.

peer: fix nil deref in newPingPayload on BestBlockHeader error

The condition guarding the early return used && when it should have
used ||. When BestBlockHeader returns an error with a nil header, the
old code only short-circuited if the nil header equalled
lastBlockHeader. Otherwise it fell through to header.Serialize(),
causing a nil pointer dereference panic.

Change the condition to return the cached serialized header whenever
there is an error OR when the header is unchanged.

lnrpc: expose graph cache state in GetInfo

Add a GraphCacheStatus enum to GetInfoResponse so callers can tell
whether the graph cache is disabled, still loading, or fully loaded.

This makes the async graph cache startup state visible to operators and
clients without changing the existing DB fallback behaviour for reads.

docs: add release notes

multi: add --db.sync-graph-cache-load option

Add a new option to opt out of the new asynchronous graph cache loading
feature.