-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature]: Add CanSend
amount to listchannels output
#8817
Comments
Good point. Let me drop two comments:
|
As just discussed with @ziggie1984 , please also add the total |
would it be tricky in terms of thinking about the offchain send actually expands the commit fee, so like how much would the weight expand for a send, how much fee rate would that be, and what is the expectation for number of htlcs, like what if you actually need to add 10 mpp htlcs to effectively send all the balance in a single payment? |
I am not sure I understand your vision, could you elaborate further ? The current idea in my mind would be something like: Consider sending the whole amount in one htlc or capping it with the I wonder how we would find out that the full amount can only be send via a 10 mpp payment, you mean because of the channel constraint restriction ? |
right so it could be multiple htlcs that you want to send the entire balance, or you are forced to via the pending values or max htlc values. so if you add multiple htlcs each htlc expands the commitment weight and therefore fee and therefore reduces the balance available for paying? maybe we can't really know then what the canpay value is at all, it's more of an interactive question, in that case it could be that instead of revealing an opaque sum that you would reveal the per htlc cost and the fee buffer and documenting how to come up with a canspend on the client side given various assumptions |
Add a
CanSend
amount in MilliSats to thelistchannels
rpc output which shows the exact bandwidth of a channel which can be used.Right now we only have the local_balance and the remote balance, tho this only accounts for the reserve and the current commitment fee, since LND 18 we also keep a Buffer so it makes sense to introduce a field called
CanSend
which shows in detail how much liquidity can be used on this channel.The text was updated successfully, but these errors were encountered: