RSS News Feed

LND V0.19.2 Launched With Key Bug Fixes And Efficiency Upgrades


At present, a brand new model of the Lightning Community Daemon (LND), model 0.19.2, has been launched. This replace focuses totally on bug fixes and efficiency enhancements.

A few of the main fixes embody a bug that triggered missed fee confirmations, a uncommon concern that might freeze the node throughout startup, and a reminiscence leak that made the software program use extra assets over time. It additionally fixes crashes that might occur when the node was beginning up in sure modes or dealing with backups.

The discharge contains an non-compulsory migration to cut back the scale of the “decayed log database” (sphinxreplay.db), which helps decrease disk and reminiscence utilization. This cleanup runs routinely except turned off within the settings.

“The migration is non-compulsory however turned on by default,” acknowledged the discharge notes. “In the event you encounter points, you possibly can opt-out of the migration by setting no-gc-decayed-log=true within the config. This migration doesn’t forestall downgrading to earlier v0.19.x-beta variations.”

LND V0.19.2 Launched With Key Bug Fixes And Efficiency Upgrades

Different adjustments embody higher dealing with of peer-to-peer (P2P) connections, improved monitoring of funds in logs, and extra correct payment calculations. The replace additionally improves compatibility with check networks and provides small updates to command line instruments (lncli).

Verifying the Docker Images.Verifying the Docker Images.

Extra enhancements embody higher connection dealing with, improved aux site visitors shaping, and updates to the RPC interface for simpler debugging. The Lightning Seed service now helps testnet4 and signet, making peer discovery simpler for brand new nodes.

RPC Additions.RPC Additions.

The replace was constructed utilizing go1.23.9 and permits others to substantiate that the launched information match the unique supply code. Docker customers may also run a script to verify the set up earlier than beginning the container.

Verify the fag itself.Verify the fag itself.

The discharge might be verified utilizing PGP signatures and OpenTimestamps to substantiate it hasn’t been tampered with. Full particulars and directions can be found right here.





Source link