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

feat (pop api): implement asset management interfaces local fungibles #92

Closed
Tracked by #132
Daanvdplas opened this issue Jul 5, 2024 · 1 comment · Fixed by #151
Closed
Tracked by #132

feat (pop api): implement asset management interfaces local fungibles #92

Daanvdplas opened this issue Jul 5, 2024 · 1 comment · Fixed by #151

Comments

@Daanvdplas
Copy link
Collaborator

Daanvdplas commented Jul 5, 2024

Implement the functionality regarding Asset Management:

  • create
  • start_destroy
  • destroy_accounts
  • destroy_approvals
  • finish_destroy
  • set_metadata
  • clear_metadata

An open question here is whether creating assets should be put in the constructor of a contract using the local fungibles api or not. In other words, no contract will create an asset other than in the contract. I'm not sure about this at the moment and needs to be looked at. As a result of this, example contracts should be made that help developers understand how to manage assets in their contracts using the api (#108).

Include integration-tests.

@Daanvdplas Daanvdplas added the good first issue Good for newcomers label Jul 5, 2024
@Daanvdplas Daanvdplas changed the title feat: implement asset management interfaces Pop API local fungibles feat (pop api): implement asset management interfaces local fungibles Jul 17, 2024
@Daanvdplas Daanvdplas removed the good first issue Good for newcomers label Jul 18, 2024
@Daanvdplas Daanvdplas mentioned this issue Jul 30, 2024
5 tasks
@Daanvdplas Daanvdplas linked a pull request Jul 30, 2024 that will close this issue
5 tasks
@Daanvdplas Daanvdplas mentioned this issue Jul 31, 2024
5 tasks
@chungquantin chungquantin linked a pull request Aug 4, 2024 that will close this issue
5 tasks
@Daanvdplas
Copy link
Collaborator Author

Closed by #151

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

Successfully merging a pull request may close this issue.

1 participant