> For the complete documentation index, see [llms.txt](https://docs.stargaze.zone/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stargaze.zone/create-and-launch/guidelines.md). # Guidelines Standards and best practices for launching on Stargaze. Following these keeps your collection in good standing and helps collectors trust it. ## What we encourage Collections that: * Feature **original artwork** * Have **clear, honest descriptions** * Provide genuine value to collectors * Represent real creative effort ## Not allowed The following will get a collection removed: * Stolen or plagiarized artwork * Copyright infringement * Impersonating other artists or projects * Spam or duplicate collections * Pornographic content ## Verification Notable collections may be verified with a **blue checkmark**, which adds visibility on the marketplace. Verification applications aren't open at the moment. ## Best practices * **Be transparent** — share a realistic roadmap (if you have one), disclose your team, and communicate openly about challenges. * **Get your metadata right** — accurate traits, clean image formatting, working external links, and complete descriptions. * **Price fairly** — research comparable collections, don't overprice the initial mint, and leave room for secondary growth. * **Build genuine community** — engage before, during, and after launch, and deliver on what you promise. ## Staying safe Scammers and impersonators are common in NFT communities. Protect yourself: * The **Stargaze team will never DM you first** — on Discord or anywhere else. * Don't click links sent by strangers, and don't trust anyone who messages you claiming to be Stargaze support. * Only use official links — start from [studio.stargaze.zone](https://studio.stargaze.zone) and the official Stargaze Discord. * **Never share your seed phrase or private keys** with anyone, for any reason. ## Reporting See something wrong? Use the **Report** button on any collection, or contact moderation via the Stargaze **Discord**. ## Questions? * Join the creator channels on **Discord** * Review the [FAQ](/create-and-launch/faq.md) * Contact **creator support** for specific situations --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.stargaze.zone/create-and-launch/guidelines.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.