Skip to content

get route with a different source_id routing to own node with exclude parameter set ignores the reserve requirements when finding route #5772

@PatrickGeyer

Description

@PatrickGeyer

Issue and Steps to Reproduce

Trying to get a route from a remote node to own node, whilst excluding a specific channel.
The result (last hop) uses a channel which has a reserve requirement, yet getroute still tries to use it, generating WIRE_TEMPORARY_FAILURE errors.

Screenshot 2022-12-03 at 15 54 22

Screenshot 2022-12-03 at 15 57 05

Screenshot 2022-12-03 at 15 58 27

getinfo output

{
"id": "035df40d260523db32cc90dd178176d60965e23b6abe076861909c40aeb56120ff",
"alias": "sudonym",
"color": "035df4",
"num_peers": 6,
"num_pending_channels": 0,
"num_active_channels": 5,
"num_inactive_channels": 0,
"address": [],
"binding": [
{
"type": "ipv4",
"address": "0.0.0.0",
"port": 9735
}
],
"version": "v0.12.1",
"blockheight": 765775,
"network": "bitcoin",
"msatoshi_fees_collected": 101760,
"fees_collected_msat": "101760msat",
"lightning-dir": "/root/.lightning/bitcoin",
"our_features": {
"init": "08a080080a69a2",
"node": "88a080080a69a2",
"channel": "",
"invoice": "02000000024100"
}
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions