lnd/docs/release-notes/release-notes-0.14.2.md

Release Notes

Remote signing

The remote signing setup was simplified in that the signing node now does not need to be hooked up to its own chain backend. A new mock chain backend can be specified with --bitcoin.node=nochainbackend. That way a wallet will be created and all signing RPCs work but the node will not look at any chain data. It can therefore be fully offline except for a single incoming gRPC connection from the watch-only node.

Wallet

• A bug that prevented opening anchor-based channels from external wallets when the internal wallet was empty even though the transaction contained a sufficiently large output belonging to the internal wallet was fixed. In other words, freshly-installed LND can now be initialized with multiple channels from an external (e.g. hardware) wallet in a single transaction.

• A bug that allowed fees to be up to 100% of the payment amount was fixed by introducing a more sane default value of 5% routing fees (except for small amounts <= 1k satoshis where the 100% routing fees are kept to accommodate for the base fee in channels). To avoid falling back to a default value, users should always set their own fee limits by using the --fee_limit or --fee_limit_percent flags on the lncli payinvoice, lncli sendpayment and lncli queryroutes commands. Users of the gRPC or REST API should set the fee_limit field on the corresponding calls (SendPayment, SendPaymentSync, QueryRoutes).

Database

• Speed up graph cache loading on startup with Postgres

Build System

• Clean up Makefile by using go install.

• Make etcd max message size configurable.

• Export bitcoind port and other values for itests, useful for using itest harness outside of lnd.

• Export lntest base node config so it can be re-used in LiT integration tests.

Bug fixes

• A new resolver for breach closes was introduced that handles sweeping anchor outputs and failing back HTLCs.

• Return the nearest known fee rate when a given conf target cannot be found from Web API fee estimator.

• We now always set a channel type if the other party signals the feature bit.

• Add --json flag to trackpayment.

• Clarify invalid config timeout constraints.

• Fix memory corruption in Mission Control Store

• Ensure that the min relay fee is always clamped by our fee floor

• Clarify log message about not running within systemd

• Fix Postgres context cancellation

• A conflict was found in connecting peers, where the peer bootstrapping process and persistent connection could compete connection for a peer that led to an already made connection being lost. This is now fixed so that bootstrapping will always ignore the peers chosen by the persistent connection.

• Fix Postgres itests max connections

• Fix duplicate db connection close

• Fix a memory leak introduced by the new ping-header p2p enhancement

• Fix an issue that would prevent very old nodes from starting up due to lack of a historical channel bucket

• Fixes a bug that would cause incorrect rounding when translating a decimal fee rate to ppm

RPC Server

• ChanStatusFlags is now exposed inside WaitingCloseResp from calling PendingChannels.

• Fix missing label on streamed transactions.

• The fee_rate_ppm parameter/argument was added to
  update channel policy to prevent truncation error with tiny fee rates.

• Closing txid is now exposed inside WaitingCloseResp from calling PendingChannels.

• CustomCaveatCondition is now properly set on RPCMiddlewareRequest messages.

• Adds a new FeeRatePpm to the UpdateChanPolicy call to allow fee rate expression in the native protocol unit

Routing

• Enable forced update of MC pair history by adding the force flag to the XImportMissionControl RPC call.

Documentation

• General improvements to the mobile documentation.

Contributors (Alphabetical Order)

• Andras Banki-Horvath
• Andreas Schjønhaug
• Bjarne Magnussen
• Daniel McNally
• Elle Mouton
• Erik Ek
• Harsha Goli
• Joost Jager
• Martin Habovštiak
• Naveen Srinivasan
• Oliver Gugger
• Olaoluwa Osuntokun
• Yong Yu