# Update Token Details

Solscan has switched to using Metaplex Metadata as the newest token standard across the network. 

When you create a token, you want to make sure that the token shows up in user's wallets with a name, ticker, and image. Solana uses the [Token Metadata Program from Metaplex](https://docs.metaplex.com/token-metadata/specification#token-standards) to achieve this.

The metadata account address is derived from the mint account. The metadata field requires a JSON file to be populated with at least the following:

```
{
  "name": "Coin name",
  "symbol": "Symbol",
  "image": "Image link"
}
```

To attach the metadata to the mint account, you can use `CreateMetadataV2`.

**Some background for users and developers:**

The concept of tokens on Solana is not binary anymore as there are different types of tokens on Solana than simply “fungible” and “non-fungible” tokens.

The Metaplex’s token standard field can have the following values: 

* NonFungible: A non-fungible token with a Master Edition. 
* FungibleAsset: A token with metadata that can also have attributes, sometimes called Semi-Fungible. 
* Fungible: A token with simple metadata. 
* NonFungibleEdition: A non-fungible token with an Edition account (printed from a Master edition).

This section serves two goals: Assist developers with the process of creating new Token using Metaplex Token Standard: Also help them update “legacy tokens” metadata with the Metaplex standard.

The JSON schema for the tokens according to the Metaplex Fungible Token Metadata Standard includes the following:

* More details from[ Metaplex docs](https://docs.metaplex.com/programs/token-metadata/changelog/v1.1)

###

\ <br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.solscan.io/integration/update-token-details.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.