> For the complete documentation index, see [llms.txt](https://swapsights.gitbook.io/swapsights-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://swapsights.gitbook.io/swapsights-whitepaper/disclaimer.md). # Disclaimer SwapSights Disclaimer: **1. Not Legal or Financial Advice** * This whitepaper and the information contained herein do not constitute legal, financial, or investment advice. It is for informational purposes only. Users should seek independent legal and financial advice before participating in any activities related to SwapSights. **2. Forward-Looking Statements** * Any statements contained in this whitepaper that are not historical facts, including statements regarding future performance, may be considered forward-looking statements within the meaning of applicable securities laws. Such forward-looking statements are subject to risks, uncertainties, and other factors that could cause actual results to differ materially from those expressed or implied in this whitepaper. **3. Token Value** * The value of SIGHTS Token can be highly volatile and subject to rapid fluctuations. Past performance is not indicative of future results, and there is no guarantee that the value of the token will appreciate or maintain its value. **4. Regulatory Risks** * The regulatory environment for cryptocurrencies and blockchain technology is evolving and subject to change. SIGHTS Token may be subject to regulatory actions or restrictions that could impact its utility or value. **5. Risk of Loss** * Users who acquire SIGHTS Token assume all risks associated with token ownership, including the risk of losing the entire investment. Users should only invest what they can afford to lose. **6. No Endorsement** * The inclusion of third-party information, references, or links in this whitepaper does not constitute an endorsement or approval of the content, products, or services provided by those third parties. SwapSights disclaims any responsibility for third-party content. **7. Technical and Security Risks** * Users should be aware of the technical and security risks associated with blockchain technology, including but not limited to hacking, wallet breaches, and other vulnerabilities. SwapSights is not responsible for any losses resulting from such risks. **8. No Guarantees** * There are no guarantees or warranties of any kind regarding the accuracy, completeness, or reliability of the information provided in this whitepaper. All information is subject to change without notice. **9. No Solicitation** * This whitepaper does not constitute a solicitation or an offer to buy or sell any securities, assets, or financial instruments. Users should not interpret it as such. **10. Changes and Updates** * SwapSights reserves the right to make changes, updates, or amendments to this whitepaper and the associated project at any time without prior notice. **11. Jurisdictional Compliance** * Users are responsible for ensuring that they comply with the laws and regulations of their respective jurisdictions when participating in SwapSights activities. **12. Contact Information** * For inquiries or additional information, please contact via email. --- # 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://swapsights.gitbook.io/swapsights-whitepaper/disclaimer.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.