You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: