> For the complete documentation index, see [llms.txt](https://solana-classic.gitbook.io/solana-classic-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solana-classic.gitbook.io/solana-classic-whitepaper/overview/mission.md). # Mission Solana Classic is dedicated to empowering the Solana blockchain community by providing innovative, accessible, and user-friendly tools for developers, projects, and enthusiasts. Our mission is to foster a thriving ecosystem where collaboration and creativity thrive. We aim to democratize access to blockchain technology, making it simple for users to create, manage, and promote their projects through streamlined utilities like the Classic Token Creator and the Solana Classic Hub. Through a sustainable model of reinvestment, we use revenues from our utilities for strategic buybacks, burns, ecosystem development, and community marketing. As we grow, our mission remains clear: to support the long-term success of the Solana ecosystem while promoting transparency, innovation, and accessibility for all participants. By building a robust and inclusive infrastructure, Solana Classic is committed to being a leading force in shaping the future of decentralized innovation on the Solana blockchain. --- # 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://solana-classic.gitbook.io/solana-classic-whitepaper/overview/mission.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.