> For the complete documentation index, see [llms.txt](https://game-changer.gitbook.io/game-changer-whitepaper-v0.1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://game-changer.gitbook.io/game-changer-whitepaper-v0.1/overview/game-changer-overview.md). # Game changer Overview Utilizing blockchain technology, Game changer establishes an expansive platform ecosystem by connecting points and digital assets from various platforms and games. Game changer provides an SDK called Virtual Swift, which can be integrated into games or platforms. It enables communication beyond conventional point systems by facilitating the conversion of points into NFTs and operates temporary record servers to minimize risks related to service databases and security. Additionally, it supports easy processing within the integrated wallet system at each stage. Through these diverse components and functionalities, Game changer enables point NFTization, GACH token exchange and usage, and interaction with various platforms. **Don't miss the opportunity to provide users with new value and experiences and join the ecosystem withGame changer** --- # 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://game-changer.gitbook.io/game-changer-whitepaper-v0.1/overview/game-changer-overview.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.