lnd v0.16.0 - Release Candidate 1

29 views
Skip to first unread message

Suheb Khan

unread,
Mar 1, 2023, 11:17:42 PM3/1/23
to l...@lightning.engineering

Hey Everyone


The first release candidate for the upcoming 0.16.0 has been released!

Based on the initial testing so far, rc1 is a pretty stable release and a long awaited major version upgrade. We expect at least one more release candidate to patch a few minor issues.


The release itself can be found here:

https://github.com/lightningnetwork/lnd/releases/tag/v0.16.0-beta.rc1


Current draft of the release notes are here:

https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.16.0.md


This release arrived a bit later than we anticipated, owing to the ongoing work on taproot channels, which is now expected to land with 0.16.1. Even without taproot channels, this is a big release with significant changes and improvements, especially since the last major release was in June 2022 and a lot of features have been stacking up with this one.


Below are some major changes and improvements:

  • Watchtower bug fixes and optimizations
    • Reduce the disk space utilization (we observed significant space reduction in our simulations e.g. the db size went down by 16x in one of our tests)
    • Performance improvement and reduced memory utilization
    • Stability improvements
  • Pathfinding optimizations
    • Channel capacity now factored into existing a priori probability estimation model
    • New bi-modal model to reflect the empirical asymmetry of channel balances
  • Reliable HTLC outcome lookup: A new rpc `LookupHtlcResolution` has been added to lookup for the final settlement of the incoming HTLCs. This allows applications to wait for the HTLC to actually disappear from all valid commitment transactions, rather than assume that it will.
  • Gossip propagation improvements: LND now properly prioritizes sending out gossip updates generated locally to all connected peers regardless of their current gossip sync query status
  • Security improvements for Tor and TLS private key handling
  • Infrastructure update to include SQLite backend as a backend option to LND. Note with this upgrade, support for the `dragonfly-amd64`, `netbsd-386`, `netbsd-arm64` and `openbsd-386` platforms has been dropped
  • MuSig2 version bump to v1.0.0rc2: The experimental MuSig2 RPC in the signrpc package was upgraded to the BIP draft version v1.0.0rc2
  • Other interesting improvements:
    • `base_fee_msat` & `fee_rate_ppm` options added to `openchannel` requests so that the user can specify fees at the time of channel open (which can be different from the default config)
    • `ForwardingHistory` now enriches each forwarding event with inbound/outbound peer alias name if the rpc is invoked with a new `PeerAliasLookup` flag
    • `ListChannels` rpc also enriches the response with peer’s alias, if the rpc is invoked with `PeerAliasLookup` flag
    • `ListInvoiceRequest` and `ListPaymentsRequest` rpc response now includes `creation_data_start` and `creation_date_end` filter fields, this can help improve pagination and UI response for data heavy nodes
    • `QueryProbability` rpc is now deprecated. Internal Mission Control state can be obtained via `QueryMissionControl`
    • `SendCustomMessage` and `SubscribeCustomMessage` APIs can now be used to send and receive custom messages below the custom range if LND is built with the dev tag, and configured to opt into overriding a specific message type. This feature will enable an external application to send custom onion messages e.g. BOLT12 onion message via LND


In addition to above, there are a lot of bug fixes and minor changes which can be tracked via the release notes.


Feel free to reach out if you have any questions or concerns w.r.t. updating your nodes or if you've already updated and run into any issues.


Thanks

Suheb


Reply all
Reply to author
Forward
0 new messages