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

As a Builder I want a centralized API for Creating & Retrieving Requests so I don't need to use the RN SDK #1389

Open
MantisClone opened this issue Apr 16, 2024 · 1 comment

Comments

@MantisClone
Copy link
Member

MantisClone commented Apr 16, 2024

Considerations

  • The caller must trust the Request Node to generate good random data for the paymentReference salt.
  • For encrypted requests, the caller must trust the Request Node to encrypt the data on their behalf.
  • Would this involve sending channel key over the internet?
@MantisClone MantisClone changed the title As a Builder I want a high-level API for Creating Requests so I don't need to use the RN SDK As a Builder I want a high-level API for Creating & Retrieving Requests so I don't need to use the RN SDK Apr 16, 2024
@MantisClone MantisClone changed the title As a Builder I want a high-level API for Creating & Retrieving Requests so I don't need to use the RN SDK As a Builder I want a centralized API for Creating & Retrieving Requests so I don't need to use the RN SDK Apr 30, 2024
@MantisClone
Copy link
Member Author

MantisClone commented Aug 14, 2024

Idea: Separate the Graph Node into "write" and "read".

Write part would continue to use REST API built on the Request Node.
Read part could use a new GraphQL API with subscriptions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✨ Backlog: Enhancements
Development

No branches or pull requests

1 participant