LND V0.19.2 Released With Key Bug Fixes And Performance Upgrades

    9
    0


    At this time, 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 embrace a bug that brought about missed fee confirmations, a uncommon concern that might freeze the node throughout startup, and a reminiscence leak that made the software program use extra sources 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 optionally available migration to scale back the dimensions of the “decayed log database” (sphinxreplay.db), which helps decrease disk and reminiscence utilization. This cleanup runs mechanically until turned off within the settings.

    “The migration is optionally available however turned on by default,” said the discharge notes. “Should you encounter points, you may 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.”

    Code Health.

    Different adjustments embrace higher dealing with of peer-to-peer (P2P) connections, improved monitoring of payments in logs, and extra correct price calculations. The replace additionally improves compatibility with take a look at networks and provides small updates to command line instruments (lncli).

    Verifying the Docker Images.

    Further enhancements embrace 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.

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

    Verify the fag itself.

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





    Source link

    LEAVE A REPLY

    Please enter your comment!
    Please enter your name here