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

Asset deployment error messages could be more informative #443

Open
OrsonJ opened this issue Jun 7, 2024 · 2 comments
Open

Asset deployment error messages could be more informative #443

OrsonJ opened this issue Jun 7, 2024 · 2 comments

Comments

@OrsonJ
Copy link
Contributor

OrsonJ commented Jun 7, 2024

I've been trying to deploy a CA (using simplewallet) for a community member. Max and current supply was to be 900m with 12 decimal points, but it fails with the message: "Error: Failed to load json file with asset specification". Only by deploying a test asset (with a lower supply) did it become clear that this combination of values wasn't permitted.

It'd be helpful if the error messages explained exactly why an asset deployment fails and if info on these types of restrictions were added to the docs. Thanks!

@cryptozoidberg
Copy link
Member

@OrsonJ thanks for the report, as it turned out deploying assets via json file has become a pain, we already working on UI version of asset's deployment/minting. Meanwhile, to figure out the issue, can you send me the json that we used and exact steps to reproduce? (because it could be RPC command or CLI wallet command). You may send it to DM to if it's better.

@OrsonJ
Copy link
Contributor Author

OrsonJ commented Jun 11, 2024

It was using the CLI wallet command deploy_new_asset. Here's the content of the .json file:

{
  "ticker": "TKN",
  "full_name": "Token",
  "total_max_supply": 900000000000000000000,
  "current_supply": 900000000000000000000,
  "decimal_point": 12,
  "meta_info": ""
}

It fails with the same message ("Error: Failed to load json file with asset specification: [PATH_TO_FILE]") when it can't find the json file, so it's unclear what corrective action should be taken.

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

No branches or pull requests

2 participants