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

Be able to differentiate local vs remote receivers #2853

Closed
Tracked by #2834
mkurapov opened this issue Aug 9, 2024 · 0 comments · Fixed by #2862
Closed
Tracked by #2834

Be able to differentiate local vs remote receivers #2853

mkurapov opened this issue Aug 9, 2024 · 0 comments · Fixed by #2862
Assignees

Comments

@mkurapov
Copy link
Contributor

mkurapov commented Aug 9, 2024

Context

In order to support local payments, we should be able to differentiate between remote and local receivers (incoming payments), before making the request to get a quote or send an outgoing payment. Since we are already doing this differentiation in the receiver service, we need to update the service/Receiver class to be able expose this local vs remote information to the callers of those methods.

@github-project-automation github-project-automation bot moved this to Backlog in Rafiki Aug 9, 2024
@mkurapov mkurapov changed the title Be able to differentiate local vs remote receiver (in the Receiver class, or elsewhere) Be able to differentiate local vs remote receiver Aug 9, 2024
@mkurapov mkurapov changed the title Be able to differentiate local vs remote receiver Be able to differentiate local vs remote receivers Aug 9, 2024
@mkurapov mkurapov moved this from Backlog to Todo in Rafiki Aug 9, 2024
@BlairCurrey BlairCurrey moved this from Todo to Ready for Review in Rafiki Aug 15, 2024
@github-project-automation github-project-automation bot moved this from Ready for Review to Done in Rafiki Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants