Login Register
SOLTAN · TOKEN METADATA

Make your Solana token easier to identify.

A liquidity pool makes a token tradable, but a pool does not automatically make every wallet, explorer or screener display the same logo, website and project information. This guide explains the correct metadata flow and where GitHub fits into it.

Solana Mainnet-betaToken metadataGitHub-hosted filesExplorer & screener verification
Important: GitHub can host public token images and JSON metadata, but putting files on GitHub does not automatically update every screener. Different services use different data sources and verification systems. The safest approach is to maintain correct token metadata first, then complete the relevant verification/listing steps for the platforms you want to appear on.
01 · UNDERSTAND THE PROBLEM

A pool is not the same thing as token metadata

When you create a Solana token and later create a liquidity pool, the pool provides the market infrastructure for trading. The token's name, symbol, logo and project links are a separate information layer.

Solana's current documentation explains that a mint contains core token information, while human-readable metadata such as a name, symbol and image can be attached through the Metaplex Token Metadata standard or, for Token-2022, the metadata extension. The metadata can point to an off-chain URI containing the richer JSON data.

Do not expect one update to control every platform. Wallets, explorers and market-data services can use different registries, APIs, cached data and verification rules. Solana Explorer, for example, aggregates multiple independent verification providers.
02 · THE CORRECT METADATA FLOW

Think of your token as three connected layers

1
On-chain token identity

Your unique Mint address identifies the actual token. Never use only the token name or symbol when checking identity.

2
Token metadata

The token metadata record contains the name, symbol and a URI. That URI can point to a public JSON file containing the logo and additional project information.

3
Platform-specific indexing and verification

Screeners and wallets decide how they ingest and verify this information. A correct metadata URI improves the source data, but it is not a universal listing switch.

Mint addressThe unique Solana token identifier.
Name / SymbolThe human-readable token identity.
Metadata URIA public URL resolving to your JSON metadata.
ImageA direct, publicly accessible logo URL.
WebsiteYour project's official website URL.
Social linksOptional project links such as X or Telegram.
03 · GITHUB

Use GitHub as a public metadata host

Solana's own developer documentation explicitly says that GitHub can be used as a centralized storage option for test-token metadata, using a raw GitHub URL. For production tokens, Solana recommends considering decentralized storage instead.

What GitHub is good for: a stable public place to store your logo file and metadata JSON, with a direct raw URL that your token metadata can reference.
  1. Create a GitHub account if you do not already have one.
  2. Create a new public repository for your token assets. Example: my-token-assets.
  3. Create a folder inside the repository, for example assets.
  4. Upload your square logo, preferably a clean PNG. Solana's token guide recommends a square image and gives 512×512 or 1024×1024 as practical sizes, with less than 100 KB preferred where possible.
  5. Commit the image to the repository.
  6. Open the image on GitHub and copy its raw URL. The URL should directly return the image file, not an HTML GitHub page.
  7. Keep the repository public and stable. Do not rename, move or delete the files after you have put their URLs into your token metadata unless you also update the metadata URI.
Example raw image URL https://raw.githubusercontent.com/YOUR-GITHUB-NAME/YOUR-REPOSITORY/main/assets/logo.png
04 · CREATE THE JSON FILE

Create metadata.json

Create a file named metadata.json in your GitHub repository. Use your real token information and the direct raw image URL from the previous step.

{ "name": "YOUR TOKEN NAME", "symbol": "SYMBOL", "description": "A short, accurate description of the project.", "image": "https://raw.githubusercontent.com/YOUR-GITHUB-NAME/YOUR-REPOSITORY/main/assets/logo.png", "website": "https://your-project.example", "twitter": "https://x.com/your-project", "telegram": "https://t.me/your-project" }

Solana's developer documentation uses the core fields name, symbol, description and image. Additional project links can be included where supported by the metadata consumer.

  1. Save the JSON. Make sure it is valid JSON: use double quotes, no comments and no trailing commas.
  2. Commit metadata.json.
  3. Open the file on GitHub and choose the raw view.
  4. Copy the raw URL. It should directly return JSON when opened in a browser.
Example raw metadata URL https://raw.githubusercontent.com/YOUR-GITHUB-NAME/YOUR-REPOSITORY/main/metadata.json
05 · CONNECT THE METADATA TO THE TOKEN

The GitHub file must actually be referenced by the token

This is the part that is often misunderstood. Uploading a JSON file to GitHub does not change a token by itself. The token's metadata must reference the public metadata URI, or the relevant platform must explicitly be submitted the information through its own process.

For tokens using the Metaplex Token Metadata standard, the metadata account contains a URI that points to the off-chain JSON. Solana's documentation also explains that Token-2022 can use its metadata extension, while the original Token Program can use Metaplex metadata.

  1. Check your Soltan token's Mint address. Use the exact Mint shown by Soltan's My Token Info page.
  2. Check the current metadata URI. Open the token in a Solana explorer and inspect its metadata.
  3. If the token's metadata authority is still available, update the metadata URI using the appropriate token-metadata method supported by the token type.
  4. Point the URI to your raw GitHub metadata.json.
  5. Verify the JSON and image from the raw URLs. Both must be publicly accessible without login.
  6. Wait for indexers to refresh. Some services cache metadata, so a correct change may not appear immediately.
Important for Soltan users: if your token was created with metadata that cannot be changed because the relevant update authority has been removed or is controlled elsewhere, do not tell users that uploading a new GitHub file will automatically fix the token. In that situation, the platform-specific submission/verification route may be required.
06 · SCREENERS, WALLETS & VERIFICATION

GitHub helps, but platform submissions still matter

There is no single GitHub repository that makes a token's logo and website appear everywhere. The old Solana Labs token-list repository is archived and explicitly marked end-of-life.

The current Solana Foundation Tokens repository is a different product and explicitly states that external pull requests for tokens, logos and metadata are not accepted. Therefore, Soltan users should not be instructed to submit a pull request to that repository as a universal token-listing method.

Solana Explorer verification guide ↗Official Solana documentation covering RugCheck, Jupiter, CoinGecko, Solflare and Bluprynt. Jupiter token verification ↗Jupiter's verification flow is integrated across parts of the Solana ecosystem. Jupiter documentation ↗Official documentation for Jupiter's token and verification systems. Archived Solana token list ↗Useful only to understand the legacy method. It is no longer the current submission route.
Why this matters: Solana's current verification guide says Jupiter, CoinGecko, Solflare and Bluprynt use their own processes, while RugCheck tracks tokens automatically. Verification by one provider can make a token discoverable in Solana Explorer, but verification is not an endorsement or guarantee of safety or value.

Birdeye also documents that token metadata can include fields such as name, symbol, logo URI and website, and its data systems may enrich token information from multiple sources. This is another reason a correct on-chain metadata source is useful, but it should not be presented as a guarantee that every field will immediately appear on every screener.

07 · FINAL CHECKLIST

Before you publish your token information

Never promise users that GitHub alone will make a token appear everywhere.

The accurate message is: GitHub can provide a public, stable source for image and off-chain JSON metadata. Each wallet, explorer and screener can independently decide how it indexes, caches and verifies that information.

SOLTAN RECOMMENDATION

Use this order

1Create tokenKeep the Mint address safe and verify the token details.
2Prepare metadataLogo + JSON + stable public URLs.
3Create poolMake the token tradable and record the pool address.
4Verify platformsUse the official process for each service you want to reach.
Open the main Soltan Guide Open Pool & Liquidity Open My Token Info