Skip to content
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

router: inbound fees support for BuildRoute #7060

Closed

Conversation

joostjager
Copy link
Contributor

@joostjager joostjager commented Oct 19, 2022

Adapting BuildRoute for inbound fees is a bit complicated with the three passes that it does (backwards - forward - backward).

I've been experimenting with reducing the number of passes (#6920) and going one step further by re-routing buildroute to pathfinding (#6921).

This PR attempts to add inbound fees support without a major overhaul in how BuildRoute works.

Builds on #6934. Review first commits there.

In this commit, the tlv extension of a channel update message is parsed.
If an inbound fee schedule is encountered, it is reported in the
graph rpc calls.
Preparation for negative fees.
Ensure that negative fees are backwards compatible.
Preparation so that we can have the inbound fee available
in addition to the outgoing policy.
Add sender-side support for inbound fees in pathfinding
and route building.
@feelancer21
Copy link
Contributor

@joostjager I think this can be closed because of #8886

@guggero
Copy link
Collaborator

guggero commented Aug 8, 2024

I think so too. @joostjager feel free to re-open if there's functionality in this PR that wasn't included in #8886.

@guggero guggero closed this Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inbound fee Changes related to inbound routing fee P2 should be fixed if one has time routing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants