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

spl-token create-token can't add metadata to new legacy SPL token #35602

Closed
SolBugz opened this issue Jul 15, 2024 · 1 comment
Closed

spl-token create-token can't add metadata to new legacy SPL token #35602

SolBugz opened this issue Jul 15, 2024 · 1 comment
Labels
community Community contribution

Comments

@SolBugz
Copy link

SolBugz commented Jul 15, 2024

Problem

With Token2022, create-token works just fine; you can just "--enable-metadata" and have the metadata stored at the mint address itself. But you can't do this if you just use Token. It just says that the program-id is invalid, which isn't the problem.

Proposed Solution

Instead of saying that Token is an invalid program ID, please give an informative error message as to why "--enable-metadata" can't work with Token or, ideally, enable a way to deploy the metadata (just the basics, not even the extended JSON) in the process of creating a standard Token. Maybe there's a way to use "--metadata-address" to point to some other account which holds the metadata (besides the mint address) but it's not obvious how to get the metadata into that account to begin with. Seems like this should be trivial to do via CLI at this point.

@SolBugz SolBugz added the community Community contribution label Jul 15, 2024
Copy link
Contributor

This repository is no longer in use. Please re-open this issue in the agave repo: https://github.com/anza-xyz/agave

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

No branches or pull requests

1 participant