> For the complete documentation index, see [llms.txt](https://gamerse.gitbook.io/gamerse/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gamerse.gitbook.io/gamerse/features/multi-chain-support.md). # Multi-Chain Support The NFT industry is expanding at an exponential rate and so are the number of NFT blockchains. NFT's are now in almost every chain out there including and not limited to Ethereum, Polygon, Phantom, BSC, Avalanche, Harmony, Solana, and beyond. Every chain has its support for NFTs; however the industry needs one platform to bring all these chains together. \ \ Gamerse will be integrating more blockchains and establishing ourselves as an ideal multi-chain NFT aggregator as we expand. Our first token bridge will be to the polygon network as we have an official partnership. Our social aggregator marketplace (SAM) will include multi-chain capability for Etereum, Phantom, Solana, Avalanche, and beyond in our ever-expanding development to host a world of NFTs. --- # 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, and the optional `goal` query parameter: ``` GET https://gamerse.gitbook.io/gamerse/features/multi-chain-support.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.