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

Feature - Payment request #2867

Open
weilbith opened this issue Jul 23, 2021 · 0 comments
Open

Feature - Payment request #2867

weilbith opened this issue Jul 23, 2021 · 0 comments

Comments

@weilbith
Copy link
Contributor

Description

During the EthCC convention I realized the following after a couple of interesting talks: it is not always affordable/nice for a user to open a direct channel with a service provider he wants to pay. If you only need to do payments to the them once in a while or just on a not regular basis, it is better to just make a mediated transfer in the network. Here it would be nice if the service provider client could offer the user client to pay for the path finding service to find a path in the network. A solution therefore would be that a client can make a PFS request with himself as target. Then this client can send a payment request message to the sender of the intended payment (the first node in the path). This client probably should ask the user to confirm the payment. This capability might be only enabled for end-user clients which can interact with the client. And full-automated payment request acceptance could be configurable, maybe even with a while list. But I'm unsure how useful that actually is.
The feature shouldn't be hard to add (I hope the PFS interface already accepts explicit sender and target address parameters). But it could be very useful for applications using Raiden.

Acceptance criteria

Tasks

  • [ ]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant