GlcoinCore/lnd
1
0
Fork 0
mirror of https://github.com/lightningnetwork/lnd.git synced 2026-08-13 12:32:48 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 7
lnd/docs/release-notes/release-notes-0.20.2.md
ziggie bd6e91a369
docs: add 0.20.2 and 0.20.3 release notes to master 
Master carries the release notes for 0.20.0 and 0.20.1, and the 0.21
line is complete through 0.21.2, but the 0.20 patch notes stopped
being forward-ported after 0.20.1. Copy release-notes-0.20.2.md and
release-notes-0.20.3.md over from v0.20.x-branch so master holds the
full historical record.

Both files are byte-identical to their counterparts on the release
branch, and the 0.20.2 notes also match the content published at the
v0.20.2-beta tag.
2026-08-07 13:55:36 -03:00

2.8 KiB
Raw Permalink Blame History

Release Notes

Bug Fixes

  • Fixed a panic in the DNS fallback SRV lookup, which unconditionally type-asserted each DNS Answer record to *dns.SRV and crashed the daemon when the response contained a non-SRV record. Non-SRV records are now skipped, and an empty LookupHost result for the shim no longer triggers an out-of-bounds index.
  • Fixed on-chain forward interceptor settlement after the incoming channel force closes. Held forwards are now tracked as off-chain or on-chain entries, allowing an on-chain re-offer to replace the old off-chain hold so settlement reaches the witness beacon. Go callers of the exported htlcswitch.InterceptedPacket type should use the new Deadline field to distinguish off-chain auto-fail heights from on-chain settlement deadlines, or AutoFailHeight() if they only need the legacy flattened value.

New Features

Functional Enhancements

RPC Additions

lncli Additions

Improvements

Functional Updates

  • lnd now validates the CLTV expiry of HTLCs at the final hop. A final HTLC whose CLTV expiry falls outside the node's receive policy is failed back, bringing the final hop in line with the CLTV delta limits already enforced on the forwarding path. As part of this change, the channel policy TimeLockDelta is now validated against LND's supported forwarding bounds: any node that previously set a per-channel TimeLockDelta greater than 2016 (the maximum default value) will now have its UpdateChannelPolicy request rejected, and must lower the value accordingly below the specified maximum.

RPC Updates

lncli Updates

Breaking Changes

Performance Improvements

Deprecations

Technical and Architectural Updates

BOLT Spec Updates

Testing

Database

Code Health

Tooling and Documentation

Contributors (Alphabetical Order)

  • Erick Cestari
  • Ziggie