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

[enhancement] Decide: Refactor `EncodeCustomRecords` RPC or Introduce New Payment-Specific RPCs #945

Open

dstadulis opened this issue Jun 11, 2024 · 0 comments

Labels

Milestone

Collaborator

dstadulis commented Jun 11, 2024

          I think so, yes. Or maybe not, given that with this it should be pretty easy to do the RPC calls in any language. I guess the question is: how much effort is it for the app devs to call 3 RPCs (buy/sell order, encode records, send payment) with the correct values vs. us threading all the payment and channel flags through some new RPC methods in tapd...

Originally posted by @guggero in #919 (comment)

The text was updated successfully, but these errors were encountered:

dstadulis added this to the v0.4.1 milestone

dstadulis added the tech debt label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment