> For the complete documentation index, see [llms.txt](https://docs.visiongame.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visiongame.io/visiongame-ecosystem/visionsdk/the-sdk-evolution.md). # The SDK Evolution The journey of VisionSDK has been transformative, evolving from a multipurpose development tool designed for various blockchain networks to becoming the primary development resource for LayerVision. Initially conceived to support multiple chains, we quickly recognized the need for a dedicated SDK that fully harnessed the capabilities of our proprietary layer. This pivot allowed us to tailor VisionSDK specifically for LayerVision, optimizing it for seamless integration and enhanced functionality. By focusing on LayerVision, we ensure that onboarding is straightforward and intuitive for developers. This evolution revolutionizes the traditional SDK model for blockchain chains, making it easier for creators to jump in and start building without being overwhelmed by complexity. VisionSDK not only simplifies the development process but also fosters a robust community of developers, all working within a cohesive ecosystem. With this evolution, we’re setting a new standard for SDKs in the blockchain space, paving the way for innovation and creativity. --- # 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.visiongame.io/visiongame-ecosystem/visionsdk/the-sdk-evolution.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.