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

Release Notes

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

Bug Fixes

• Fixed a bug to correctly propagate mission control and debug level config values to the main LND config struct so that the GetDebugInfo response is accurate.

• Fix a bug that would cause a nil pointer dereference during the probing of a payment request that does not contain a payment address.

• Fixed a bug where we would not signal an error when trying to bump an non-anchor channel but instead report a successful cpfp registration although no fee bumping is possible for non-anchor channels anyways.

• Use the required route blinding feature-bit for invoices containing blinded paths.

• Fix a bug that prevented a graceful shutdown of LND during the main chain backend sync check in certain cases.

New Features

Functional Enhancements

RPC Additions

• Add a new rpc endpoint BumpForceCloseFee which moves the functionality soley available in the lncli to LND hence making it more universal.

lncli Additions

• A pre-generated macaroon root key can now be specified in lncli create and lncli createwatchonly to allow for deterministic macaroon generation.

Improvements

Functional Updates

• Allow the compression of logs during rotation with ZSTD via the logging.file.compressor startup argument.

• The SCB file now [contains more data][https://github.com/lightningnetwork/lnd/pull/8183] that enable a last resort rescue for certain cases where the peer is no longer around.

• LND updates channel.backup file at shutdown time.

RPC Updates

lncli Updates

Code Health

• Add retry logic for watchtower block fetching with a max number of attempts and exponential back-off.

• Moved profile related config settings to its own dedicated group. The old ones still work but will be removed in a future release.

• Update to use structured logging. This also introduces a new --logging.console.disable option to disable logs being written to stdout and a new --logging.file.disable option to disable writing logs to the standard log file. It also adds --logging.console.no-timestamps and --logging.file.no-timestamps which can be used to omit timestamps in log messages for the respective loggers. The new --logging.console.call-site and --logging.file.call-site options can be used to include the call-site of a log line. The options for this include "off" (default), "short" (source file name and line number) and "long" (full path to source file and line number). Finally, the new --logging.console.style option can be used under the dev build tag to add styling to console logging.

• Add max files and max file size options to the logging config namespace under new --logging.file.max-files and --logging.files.max-file-size options. The old options (--maxlogfiles and --maxlogfilesize) will still work but deprecation notices have been added and they will be removed in a future release. The defaults values for these options have also been increased from max 3 log files to 10 and from max 10 MB to 20 MB.

Breaking Changes

Performance Improvements

• Log rotation can now use ZSTD

• A new method AssertTxnsNotInMempool has been added to lntest package to allow batch exclusion check in itest.

Technical and Architectural Updates

BOLT Spec Updates

• Add new lnwire messages for the Gossip 1.75 protocol.

Testing

Database

• Migrate the mission control store to use a more minimal encoding for payment attempt routes as well as use pure TLV encoding.

• Migrate the mission control store so that results are namespaced. All existing results are written to the "default" namespace.

Code Health

Tooling and Documentation

• Improved lncli create command help text by replacing the word argument with input in the command description, clarifying that the command requires interactive inputs rather than arguments.

Contributors (Alphabetical Order)

• Animesh Bilthare
• Boris Nagaev
• CharlieZKSmith
• Elle Mouton
• Pins
• Viktor Tigerström
• Ziggie