ef1eff1058
When updating the channel routing policy, we encounter an inaccurate precision error when calculating the routing fee. The issue stems from the way the IEEE 754 standard works. The solution here is to add a uint64 parameter (as mentioned in the issue) and keep the float64 fee_rate parameter but rounding the product of the base and fee rate.
4.5 KiB
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.
Database
Build System
-
Export bitcoind port and other values for itests, useful for using itest harness outside of lnd.
-
Export
lntestbase node config so it can be re-used in LiT integration tests.
Bug fixes
-
We now always set a channel type if the other party signals the feature bit.
-
Ensure that the min relay fee is always clamped by our fee floor
-
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 a memory leak introduced by the new ping-header p2p enhancement
RPC Server
-
ChanStatusFlags is now exposed inside WaitingCloseResp from calling
PendingChannels. -
The
fee_rate_ppmparameter/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
RPCMiddlewareRequestmessages.
Routing
- Enable forced update of MC pair
history by adding the
forceflag to theXImportMissionControlRPC call.
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
- Yong Yu