> For the complete documentation index, see [llms.txt](https://docs.seedify.fund/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seedify.fund/seedify-vibecoins/vibecoins-by-seedify/legal-tips.md). # Legal Tips When launching a Vibecoin, it is important to follow guidelines that help reduce legal risks and keep your project focused on utility and community value. These tips are for general guidance only and are not legal advice. *** ### Key Points * Your token should be treated as digital merchandise, not equity * Do not promise or imply profits, dividends, or any form of returns to holders * Avoid presenting your token as an investment offer; focus on its utility and community benefits * Follow standard market rules on information disclosure and avoid sharing non-public information for trading purposes *** ***Note**:* * *Founders will need to pass KYC with Seedify* * *For specific compliance requirements in your region, consult a qualified legal professional* --- # 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://docs.seedify.fund/seedify-vibecoins/vibecoins-by-seedify/legal-tips.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.