lnd/docs/release-notes/release-notes-0.19.3.md

Release Notes

• Bug Fixes
• New Features
  • Functional Enhancements
  • RPC Additions
  • lncli Additions
• Improvements
  • Functional Updates
  • RPC Updates
  • lncli Updates
  • Breaking Changes
  • Performance Improvements
  • Deprecations
• Technical and Architectural Updates
  • BOLT Spec Updates
  • Testing
  • Database
  • Code Health
  • Tooling and Documentation

Bug Fixes

• Fixed a deadlock that could occur when multiple goroutines attempted to send gossip filter backlog messages simultaneously. The fix ensures only a single goroutine processes the backlog at any given time using an atomic flag.

• Fix a bug where child logger's derived via WithPrefix did not inherit change log level changes from their parent loggers.

• Fixed a deadlock that can cause contract resolvers to be stuck at marking the channel force close as being complete.

• Fixed a bug in btcwallet that caused issues with Tapscript addresses being imported in a watch-only (e.g. remote-signing) setup.

• Fixed a case in the payment lifecycle where we would retry the same route over and over again in situations where the sending amount would violate the channel policy restriction (min,max HTLC).

• Fixed a case where we would not resolve all outstanding payment attempts after the overall payment lifecycle was canceled due to a timeout.

New Features

Functional Enhancements

• The default value for gossip.msg-rate-bytes has been increased from 100KB to 1MB, and gossip.msg-burst-bytes has been increased from 200KB to 2MB.

• Previously, when sweeping non-time sensitive anchor outputs, they might be grouped with other non-time sensitive outputs such as to_local outputs, which potentially allow the sweeping tx to be pinned. This is now fixed by moving sweeping anchors into its own tx, which means the anchor outputs won't be swept in a high fee environment.

• Added NoOp HTLCs. This allows sending HTLCs to the remote party without shifting the balances of the channel. This is currently only possible to use with custom channels, and only when the appropriate TLV flag is set. This allows for HTLCs carrying metadata to reflect their state on the channel commitment without having to send or receive a certain amount of msats.

RPC Additions

lncli Additions

Improvements

Functional Updates

RPC Updates

lncli Updates

Code Health

Breaking Changes

Performance Improvements

Deprecations

Technical and Architectural Updates

BOLT Spec Updates

Testing

Database

Code Health

• The Golang version used was bumped to v1.23.12 to fix a potential issue with the SQL API.

Tooling and Documentation

Contributors (Alphabetical Order)

• Elle Mouton
• Olaoluwa Osuntokun
• Oliver Gugger
• Yong Yu
• Ziggie