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

Document possible interfaces and serialization formats for front-end #15

Open
uhbif19 opened this issue Feb 1, 2024 · 1 comment
Open
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@uhbif19
Copy link
Contributor

uhbif19 commented Feb 1, 2024

This question is out of scope of current Catalyst Project. We believe that simple server-generates-tx-and-client-signs-it would be simple to implement, and more complex solutions are not planned in current milestones.

Still, as @euonymos correctly noted, this question is of huge importance for real-world applications. So we should document how interface is intended to be used in end of project.

@uhbif19 uhbif19 added the documentation Improvements or additions to documentation label Feb 1, 2024
@uhbif19 uhbif19 self-assigned this Feb 1, 2024
@uhbif19
Copy link
Contributor Author

uhbif19 commented Jun 30, 2024

@euonymos So far seems that in current design the only option is DSL to PureScript transpiler. But Plutarch may be inlined in DSL, and AFAIU PLC cannot be executed on fronted (as we do in Haskell offchain code), so the only option is to manually specify PureScript equivalent for each inlined Plutarch function.

UPD

@klntsky said that you can parse it at least

https://github.com/butaneprotocol/blaze-cardano/blob/df5842bdafb4530c372cc1a537b61fc19f0418df/packages/blaze-uplc/src/types.ts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant