3.7 KiB
Release Notes
- Bug Fixes
- New Features
- Improvements
- Technical and Architectural Updates
- Contributors (Alphabetical Order)
Bug Fixes
-
Fix bug where channels with both policies disabled at startup could never be used for routing
-
Fix a case where resolving the to_local/to_remote output might take too long.
-
Fix a bug where repeated network addresses were added to the node announcement and
getinfooutput. -
Fix source node race condition which could prevent a node from starting up if two goroutines attempt to update the node's announcement at the same time.
-
Fix a startup issue in LND when encountering a deserialization issue in the mission control store. Now we skip over potential errors and also delete them from the store.
-
Fix potential sql tx exhaustion issue in LND which might happen when running postgres with a limited number of connections configured.
-
Add missing payment address/secret when probing an invoice. This makes sure the EstimateRouteFee API can probe Eclair and LDK nodes which enforce the payment address/secret.
-
Fix a bug where missing edges for own channels could not be added to the graph DB due to validation checks in the graph Builder that were resurfaced after the graph refactor work.
New Features
Functional Enhancements
RPC Additions
lncli Additions
Improvements
Functional Updates
RPC Updates
- The
EstimateRouteFeeRPC now implements an LSP detection heuristic that probes up to 3 unique Lightning Service Providers when route hints indicate an LSP setup. The implementation returns worst-case (most expensive) fee estimates for conservative budgeting and includes griefing protection by limiting the number of probed LSPs. It enhances the previous LSP design by being more generic and more flexible.
lncli Updates
Breaking Changes
Performance Improvements
- Added new Postgres configuration
options
db.postgres.channeldb-with-global-lockanddb.postgres.walletdb-with-global-lockto allow fine-grained control over database concurrency. The channeldb global lock defaults tofalseto enable concurrent access, while the wallet global lock defaults totrueto maintain safe single-writer behavior until the wallet subsystem is fully concurrent-safe.
Deprecations
Technical and Architectural Updates
BOLT Spec Updates
Testing
Database
Code Health
Tooling and Documentation
Contributors (Alphabetical Order)
- bitromortac
- Ziggie