> For the complete documentation index, see [llms.txt](https://support.highlight.xyz/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.highlight.xyz/knowledge-base/for-developers/nft-contracts/erc721editionsdfs.md). # ERC721EditionsDFS The ERC721EditionsDFS contract is used for projects where the metadata for each token is the same, but it has an added set of functionality around the concept of “editions.” An edition is defined in the IEditionCollection interface, and lets you set a name, token supply, and initial token ID for a distinct grouping of tokens on the same contract. In the Highlight interface these will show up as distinct collections, and you can set the metadata for each edition separately. You can add new editions continuously over time, allowing you to reuse the same contract again and again. Each edition will have distinct metadata, but each token within an edition will have the same metadata. Note that on 3rd party platforms these will appear as grouped together into the same collection. ### Contract link {% embed url="" %} --- # 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://support.highlight.xyz/knowledge-base/for-developers/nft-contracts/erc721editionsdfs.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.