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

Royalty token issue -- mandatory metadata #117

Closed
eric248550 opened this issue Apr 12, 2023 · 0 comments
Closed

Royalty token issue -- mandatory metadata #117

eric248550 opened this issue Apr 12, 2023 · 0 comments

Comments

@eric248550
Copy link

eric248550 commented Apr 12, 2023

Currently, there is no way to mint royalty tokens without the policy id attached.
I was able to generate a token with the 777 label, the issue is that it had the policy id and asset name attached in the metadata. Wondering if there's a way to get rid of this metadata.

TokenI mint using mesh:

{
   "policyId": {
      "": {
         "addr": [ "addr_test1djfkh8skjne8u8wknsafnekjaikjkkasfgj9w89nsakjf84nuknsf9",
            "msf4jj70v7n30289afjknr4389wjknfsa893jknfs893"
         ],
         "rate": "0.025"
      }
   }
}

What royalty token should be:

{
  "addr": [ "addr_test1djfkh8skjne8u8wknsafnekjaikjkkasfgj9w89nsakjf84nuknsf9",
    "msf4jj70v7n30289afjknr4389wjknfsa893jknfs893"
  ],
  "rate": "0.025"
}

After went through the repo, I found the issue is the metadata format being fixed by forgeAssetsIfNeeded(), forge()

private async forgeAssetsIfNeeded() {

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

1 participant