> For the complete documentation index, see [llms.txt](https://metadatea.gitbook.io/metadate/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metadatea.gitbook.io/metadate/faq.md).

# 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?** 

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