As is, we'll never get any add/remove features because the flag is
set as an int 64 slice but accessed as an int slice (which has no
value, and the cli doesn't fail if the flag doesn't exist).
The active probability estimator can be switched dynamically using the
`Set/GetMissionControl` API, maintaining backward compatibility. The
lncli commands `setmccfg` and `getmccfg` are updated around this
functionality. Note that deprecated configuration parameters were
removed from the commands.
With this commit, we can define an address type for default/imported
accounts in FundPsbt using '—change_type' flag. The value for this
flag can only be 'p2tr' at the moment. If not specified, we will use
P2WKH addresses for change outputs. Custom accounts don’t support
this flag as they have a unique scope.
adds the functionality in the lncli walletkit to sign and verify a
message with a single address. Signing works only with lnd default
wallet account. Verifying signature on messages with external addresses
is also supported.
This commit clarifies the htlc failure case in the lncli payment
command, by using the cardinal number as well as 'hop' in the
failure message.
[skip ci]
We deprecate `QueryProbability`, as it displays the same information as
`QueryMissionControl` less the probability. `QueryRoutes` still contains
the total probability of a route.
BIP 174 states that PSBTs can be encoded in 2 formats:
- plain text as base64
- in a file as binary
With this change, lncli will also try to read a PSBT as binary
Pass down a context from bumpCloseFee to getWaitingCloseCommitments,
to avoid another call to getContext that used to fail with "intercept
already active"
Add additional comment to `lnclic addinvoice`'s `--private` flag warning
about including a large number of private channel hints when using zero
ammounts.
Also added a comment to the `private` field in the `Invoice` proto
message.
A new flag skip_peer_alias_lookup is introduced that communicates to the
server if the peer alias lookup per forwarding event should be skipped
in order to improve performance.
If `lncli profile remove` is called when there are no existing profiles,
it will cause a "cap out of range" panic. So in this commit, a length
check is added to avoid this.
In the lnrpc proto, we use either int64 or uint32 for output index. So
to keep things consistent, we should use a bitsize of 64 when reading an
output index from a string. Otherwise, we fail could fail to parse an
index that is valid based on the types we define in the protos.
Add a new `metadata` string slice flag to lncli that allows the caller
to specify multiple key-value string pairs that should be appended to
the outgoing context.
Oliver Gugger