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 public API and encodings #256

Open
Tracked by #347
tzemanovic opened this issue Feb 4, 2022 · 3 comments
Open
Tracked by #347

Document public API and encodings #256

tzemanovic opened this issue Feb 4, 2022 · 3 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@tzemanovic
Copy link
Member

tzemanovic commented Feb 4, 2022

In order to build the Ledger application we need to know how transactions are encoded and decoded, what transaction types exists, what address types exist, ... (really how to build a wallet and/or client from scratch).

This should include the types/API used for MASP.

@tzemanovic tzemanovic added the documentation Improvements or additions to documentation label Feb 4, 2022
@tzemanovic tzemanovic self-assigned this Feb 4, 2022
@tzemanovic
Copy link
Member Author

we have done the first part in anoma/anoma#887 - but we still need to add MASP once more stable

@tzemanovic tzemanovic transferred this issue from anoma/anoma Jul 7, 2022
@cwgoes
Copy link
Contributor

cwgoes commented Jan 12, 2023

@tzemanovic is this still accurate?

@tzemanovic
Copy link
Member Author

@tzemanovic is this still accurate?

yes, I think we still need to add masp types. The deployed spec is here https://d39rezrq9h4sx4.cloudfront.net/specs/encoding.html btw

@cwgoes cwgoes transferred this issue from anoma/namada Feb 5, 2024
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
No open projects
Status: WIP
Development

No branches or pull requests

2 participants