# Exploring Token Information and Enhanced Asset Information

While you are free to put any type of description in the “description” field, <mark style="color:yellow;">some descriptions are supported to show correctly on Tokenscan and Freewallet.</mark>

TokenScan provides a simple "Enhanced Asset Information" standard to point to more information that could not just be stored in the description text.

These formats include: \
\- IMAGE Format\
\- JSON Format \
\- JSON Format with Hash\
\- IMGUR Format\
\- SOUNDCLOUD Format\
\- YOUTUBE Format\
\- IPFS Format\
\- STAMP Format\
\- ORDINALS Inscription Format

For more information on how to correctly input the description you wish to use [please reference CIP 25](https://github.com/CounterpartyXCP/Forum/blob/1e362f7f8668654d0241fe5b1f1c1c330a8b4368/cip-0025.md).

<figure><img src="https://3285406617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHOAdveIkUtULHe7q3v2%2Fuploads%2Ft7BMKdFmkheRCfubxPwM%2Fenhanced.png?alt=media&#x26;token=b1a504f0-6172-49bd-ab2e-8d46cdc6461c" alt=""><figcaption></figcaption></figure>

While these formats are commonly used, it is very common for users to experiment with description information as seen with [CCSATOSHI](https://xchain.io/asset/CCSATOSHI) (base-64 in description):

<figure><img src="https://3285406617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHOAdveIkUtULHe7q3v2%2Fuploads%2F4fxw2oT3hud0Zi1MF3Cs%2Fccsatoshi.png?alt=media&#x26;token=a84c5525-facd-400b-b2f0-a6be3d8f1ca1" alt=""><figcaption><p>Base-64 format without STAMP prefix on CCSATOSHI by Cornholio</p></figcaption></figure>

<mark style="color:yellow;">There are also many tools and 3rd party websites that offer the service of easily converting your data or file you would like to include in your description to be coded in these “standard” manners to show correctly on Tokenscan and other Counterparty Block Explorers.</mark>

These include, but are not limited to:

* [https://coindaddy.io](https://coindaddy.io/) - This is owned and operated by Jdog and requires a $5 fee to host your data to produce a json for your token. This resource will take you through the process from start to finish if you have not already minted your XCP asset. If you have already minted an asset, but are just looking to change the description and use Enhanced Asset Descriptions, you will have to first sign in with your BTC address by signing a message using Freewallet (or other Counterparty wallets).
* [https://easyasset.art](https://easyasset.art/) - This is more recent and uses Arweave to host your data and produce a json for your token. There is a [great informative video](https://www.youtube.com/watch?v=pENROu4fCTE) from RobotLoveCoffee to use this website with use on Counterparty Descriptions.
* You can also manually create a json file and host it using Arweave yourself, but the process is a little more in-depth and technically demanding. If you would like to go about this route (with long term data storage in mind) please reference [this informative video](https://www.youtube.com/watch?v=JNNCjDx2PD0) by RobotLoveCoffee. This process uses [this json tool](https://robotlovecoffee.io/XCPJsonTool.html) and [ArDrive](https://ardrive.io/).
* For Ordinal Inscriptions it has been recommended by the community to [use this tool](https://unisat.io/inscribe) to mint the details and media of your asset and then use [this separate tool](https://inscribe.art/) to correctly format your Inscription for your Counterparty Description which points to the Inscription. For more information on what an Inscription is, please reference [this guide](https://docs.ordinals.com/).
* It is also possible to host data associated with a token using a JSON hosted with a Github Repository. There is [a great Medium article](https://subterranean.medium.com/how-to-host-your-counterparty-images-and-json-files-on-github-c5ff89e14ee0) written by [Subterranean](https://x.com/subterranean_1) is avaliable to review how to do this in greater detail and is titled, 'How to Host Your Counterparty Images and Json Files on GitHub'.

\
Furthermore, using [FAKEDUST](https://xchain.io/asset/FAKEDUST) (an entire music album in a token with additional art) as an example of preparing a specific JSON to show information: &#x20;

<figure><img src="https://3285406617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHOAdveIkUtULHe7q3v2%2Fuploads%2FK9uCwK2kUq6vNfIP4R2Q%2Ffakedustinfo.png?alt=media&#x26;token=bbe00bba-04d6-480f-b70c-401368e94184" alt=""><figcaption><p>JSON of FAKEDUST shown in the description of the asset in Orange oval</p></figcaption></figure>

Many different enhanced asset information properties can be used at one time:

<figure><img src="https://3285406617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHOAdveIkUtULHe7q3v2%2Fuploads%2FfAdjqGC9J11HZzBxJQSD%2Ffakedust.png?alt=media&#x26;token=75153f97-5455-4359-b6d1-7cc5a6402be9" alt=""><figcaption></figcaption></figure>

For instance, take a look at the FAKEDUST enhanced information above. With just one JSON description a user can include:\
\
\- An entire album with a custom HTML player shown with the Red Arrow\
\- An attached digital artwork show with the Blue Arrow\
\- Attached Digital Video artwork shown with the Orange Arrow\
\- Categorized Enhanced Asset Information shown with the Green Arrow\
\- Links to the attached Arweave links shown with the Purple Arrow

<mark style="color:yellow;">Keep in mind Counterparty users have been experimenting with token usage, description info, distribution techniques and project rulesets for almost 10 years now.</mark> \
\
There is usually an example that can help you form the token you wish to create.\
\
For more historical tokens check out this [Historical Counterparty Token/Developer Timeline (2014-2021)](https://time.graphics/line/858561).


---

# 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://davestaxcp.gitbook.io/freewallet.io-user-manual/exploring-balances-history-exchange-and-dispensers/exploring-token-information-and-enhanced-asset-information.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.