# FAQ

**- Is this collection 100% fully on-chain?**

Yes. Each token is stored on-chain, including the metadata and artwork.

**- What does edit metadata mean?**

Metadata is stored on-chain and reflected in the tokenURI function in the contract. There's a special attribute called "Metadata" that can store a string (text) of up to 100 characters. That attribute is included when NFT marketplaces (Blur, OpenSea, etc) ask the contract for information about a token.

**- What happens to burned art?**

Burned tokens have their attributes wiped and artwork replaced with a special design. Burned tokens cannot be traded, since they're no longer owned by anyone.

**- What’s the system UI font?**

The system UI font is a way to ensure maximum artwork compatibility across devices and operating systems. [Read more from Google](https://fonts.google.com/knowledge/glossary/system_font_web_safe_font).

**- What are the token states for metadate/a?**

Metadate/a tokens can be Edited or Not Edited. Tokens that are Edited can only be edited again if they are a Super Rare. Tokens that are Not Edited can be edited if they are a Blank, or if 4 other Common tokens are being burned.

**- What is the burned token filter?**

NFT marketplaces often implement filters for token attributes. Metadate/a tokens have a "Burned" attribute which can be used to filter out (or in) burned tokens on marketplaces.

**- Why is (1) token already minted?**&#x20;

The contract was programmed to mint token ID #1 to auction for charity.&#x20;


---

# 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://metadatea.gitbook.io/metadate/faq.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.
