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

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

Closed
dstadulis opened this issue Jun 11, 2024 · 1 comment
Closed

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

dstadulis opened this issue Jun 11, 2024 · 1 comment
Labels
tech debt
Milestone
v0.5

Comments

@dstadulis
Copy link
Collaborator 

          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)
@dstadulis dstadulis added this to the v0.4.1 milestone Jun 11, 2024
@Roasbeef
Copy link
Member

Fixes #1048

@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Taproot-Assets Project Board Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
tech debt
Projects
Taproot-Assets Project Board
Status: ✅ Done
Milestone
v0.5
Development

No branches or pull requests
2 participants
@Roasbeef @dstadulis