release-notes-0.18.4.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

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

• Make the contract resolutions for the channel arbitrator optional.

• Fixed a bug to prevent potential deadlocks when LND depends on external components (e.g. aux components, hooks).

• Make sure blinded payment failures are handled correctly in the mission controller.

New Features

The main channel state machine and database now allow for processing and storing custom Taproot script leaves, allowing the implementation of custom channel types in a series of changes:

• #9025
• #9030
• #9049
• #9072
• #9095
• #8960
• #9194
• #9288

Functional Enhancements

• A new protocol.simple-taproot-overlay-chans configuration item/CLI flag was added to turn on custom channel functionality.

• Compatibility with bitcoind v28.0 was ensured by updating the version the CI pipeline is running against.

RPC Additions

• Some new experimental RPCs for managing SCID aliases were added under the routerrpc package. These methods allow manually adding and deleting SCID aliases locally to your node.

  NOTE: these new RPC methods are marked as experimental (XAddLocalChanAliases & XDeleteLocalChanAliases) and upon calling them the aliases will not be communicated with the channel peer.

• The responses for the ListChannels, PendingChannels and ChannelBalance RPCs now include a new custom_channel_data field that is only set for custom channels.

• The routerrpc.SendPaymentV2 RPC has a new field first_hop_custom_records that allows the user to send custom p2p wire message TLV types to the first hop of a payment. That new field is also exposed in the routerrpc.HtlcInterceptor, so it can be read and interpreted by external software.

• The routerrpc.HtlcInterceptor now allows some values of the HTLC to be modified before they're validated by the state machine. The fields that can be modified are outgoing_amount_msat (if transported overlaid value of HTLC doesn't match the actual BTC amount being transferred) and outgoing_htlc_wire_custom_records (allow adding custom TLV values to the p2p wire message of the forwarded HTLC).

• A new invoicesrpc.HtlcModifier RPC now allows incoming HTLCs that attempt to satisfy an invoice to be modified before they're validated. This allows custom channels to determine what the actual (overlaid) value of an HTLC is, even if that value doesn't match the actual BTC amount being transferred by the HTLC.

lncli Additions

Improvements

Functional Updates

RPC Updates

lncli Updates

Code Health

Breaking Changes

Performance Improvements

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

Technical and Architectural Updates

BOLT Spec Updates

Testing

Database

Code Health

Tooling and Documentation

Contributors (Alphabetical Order)

• Elle Mouton
• ffranr
• George Tsagkarelis
• Olaoluwa Osuntokun
• Oliver Gugger
• Ziggie