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

Identify unfulfillable rate probe packets #205

Closed
wilsonianb opened this issue Dec 21, 2021 · 1 comment · Fixed by #730
Closed

Identify unfulfillable rate probe packets #205

wilsonianb opened this issue Dec 21, 2021 · 1 comment · Fixed by #730
Assignees
Labels
pkg: backend Changes in the backend package.
Milestone

Comments

@wilsonianb
Copy link
Contributor

#197 stops balance adjustments from happening at the sending connector for unfulfillable rate probe packets.
Being able do them same for forwarding and receiving connectors would help avoid peer and asset liquidity from being reserved for unfulfillable packets.

@wilsonianb wilsonianb added the pkg: backend Changes in the backend package. label Dec 21, 2021
@wilsonianb wilsonianb added this to Triage in Rafiki Tasks via automation Dec 21, 2021
@wilsonianb wilsonianb moved this from Triage to To do in Rafiki Tasks Dec 21, 2021
@matdehaast matdehaast added this to the Rafiki v1 milestone Aug 16, 2022
@matdehaast
Copy link
Collaborator

@wilsonianb intermediate connectors could never know that the packets are unfulfillable as they can't decode the packet.

I am wondering if there could be an issue though with enabling this on the recievers side. I can't seem to think of anything in particular. @adrianhopebailie @sabineschaller do you think there are any potential footguns in not doing balance adjustments for probing packets?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pkg: backend Changes in the backend package.
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants