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.

Sign up for GitHub

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

Jump to bottom

Payments within a Rafiki instance a.k.a. local payments #2834

Open
2 of 4 tasks
sabineschaller opened this issue Aug 2, 2024 · 0 comments
Open
2 of 4 tasks

Payments within a Rafiki instance a.k.a. local payments #2834

sabineschaller opened this issue Aug 2, 2024 · 0 comments
Assignees
@BlairCurrey
Labels
pkg: backend Changes in the backend package. story Major feature that can be broken up into smaller tasks

Comments

@sabineschaller
Copy link
Member

sabineschaller commented Aug 2, 2024 •
edited by mkurapov
Loading

Context

Currently, every payment is going through the ILP connector within Rafiki, no matter whether it's local, i.e. from one account to another account within the same Rafiki instance, or whether it is to a peer's account.

We should be able to improve performance if we account for those local payments directly without going through the connector. Additionally, no slippage is required for these payments since no packets can be lost.

Todos
@sabineschaller sabineschaller changed the title Payments within a Rafiki instance Payments within a Rafiki instance a.k.a. local payments Aug 2, 2024
@sabineschaller sabineschaller added pkg: backend Changes in the backend package. story Major feature that can be broken up into smaller tasks labels Aug 2, 2024
@BlairCurrey BlairCurrey self-assigned this Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BlairCurrey BlairCurrey

Labels
pkg: backend Changes in the backend package. story Major feature that can be broken up into smaller tasks
Projects
Rafiki
Status: In Progress
Milestone
No milestone
Development

No branches or pull requests
2 participants
@BlairCurrey @sabineschaller