> For the complete documentation index, see [llms.txt](https://litepaper.gameswift.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://litepaper.gameswift.io/ecosystem/web3-gaming-infrastructure/gameswift-chain/zkevm.md). # zkEVM zkEVM is a recently announced solution developed by Polygon, which aims to truly revolutionize the scalability of the Ethereum network by introducing Layer 2 zero-knowledge proof rollups. This technology not only enables the world’s fastest transactions on top of the security inherited from the most decentralized blockchain but also offers a full EVM (Ethereum Virtual Machine) compatibility, which lets developers seamlessly deploy any Ethereum smart contract to Layer 2 while providing users with dApps and UX they are already familiar with. With the zkEVM upgrade right around the corner (Q1 2023), we plan to implement this technology as fast as possible and become the first zkEVM gaming chain ever created! --- # 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://litepaper.gameswift.io/ecosystem/web3-gaming-infrastructure/gameswift-chain/zkevm.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.