> For the complete documentation index, see [llms.txt](https://docs.yam.finance/yam/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yam.finance/yam/projects/museum/introduction.md). # Introduction The Museum of Fine Yams (MoFY) is an NFT art museum and marketplace that focuses on the curation and display of high quality NFT artwork. There are 3 components to MoFY: [The MoFY dApp](https://nft.yam.xyz), [MoFY Magazine](https://mofy.yam.xyz), and [Virtual Gallery spaces](https://yam.museum) in CryptoVoxels. The goal of MoFY is to provide a unique and seamless experience where art and NFT lovers can mint NFTs inexpensively, browse curated work, and experience NFT art in a new way in CryptoVoxels. The MoFY dApp and marketplace is built on ZKsync, a new ZK-rollup layer 2 network on Ethereum. ZKsync allows artists and collectors to use the platform without worrying about paying the high gas fees on L1 Ethereum. Disclamer: This website is in Beta and some functionality is not yet available. ZKsync is also in beta and may have downtime or occasional issues with response times. If you have problems with the dApp, please come let us know in our discord server: . --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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.yam.finance/yam/projects/museum/introduction.md?ask= ``` 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.