Skip to content

ChannelDetails::outbound_capacity_msat needs to be more exact #1126

Closed
@TheBlueMatt

Description

@TheBlueMatt

I had an issue locally where I'd be stuck unable to send a payment because the router kept selecting a channel and use all of the availability listed as outbound_capacity_msat before adding other MPP hops. However, outbound_capacity_msat isn't exact, and slightly over-counts the amount we can reasonably send (as documented, and ignored in get_route). This resulted in an un-sendable payment. The sample gave me this:

ERROR: failed to send payment: PartialFailure([Err(Cannot send value that would put our balance under counterparty-announced channel reserve value (30000000)), Ok(()), Err(Cannot send value that would not leave enough to pay for fees. Pending value to self: 38978302. local_commit_tx_fee 1656000)])

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions