The token extensions with metadata example uses this TokenMetadata
From @solana/spl-token-metadata/src/state.ts
export interface TokenMetadata {
// The authority that can sign to update the metadata
updateAuthority?: PublicKey;
// The associated mint, used to counter spoofing to be sure that metadata belongs to a particular mint
mint: PublicKey;
// The longer name of the token
name: string;
// The shortened symbol for the token
symbol: string;
// The URI pointing to richer metadata
uri: string;
// Any additional metadata about the token as key-value pairs
additionalMetadata: [string, string][];
}Almost all the old things that used to be in the JSON file - name, symbol, description, key/value attribute pairs - are now in the TokenMetadata object.
Why not add image?
Use case
Someone wishes to make an SPL token with minimum features. Right now they need to make a JSON file with:
{
"image": "https://raw.githubusercontent.com/solana-developers/opos-asset/main/assets/CompressedCoil/image.png",
}
As the only contents, and add that as a uri in their TokenMetadata instance.
Instead, we could allow image (or some other other equivalent) to the TokenMetadata instance and save people the effort.
The token extensions with metadata example uses this TokenMetadata
From @solana/spl-token-metadata/src/state.ts
Almost all the old things that used to be in the JSON file - name, symbol, description, key/value attribute pairs - are now in the
TokenMetadataobject.Why not add
image?Use case
Someone wishes to make an SPL token with minimum features. Right now they need to make a JSON file with:
As the only contents, and add that as a
uriin theirTokenMetadatainstance.Instead, we could allow
image(or some other other equivalent) to theTokenMetadatainstance and save people the effort.