> For the complete documentation index, see [llms.txt](https://docs.nezohub.com/nezohub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nezohub.com/nezohub/overview/research/zk-evm.md).

# zk-EVM

### What is a zk-EVM?

ZK-EVM, short for Zero-Knowledge Ethereum Virtual Machine, is a layer 2 scaling solution built on the Ethereum network. It operates as a zero-knowledge (ZK) rollup technology, leveraging cryptographic primitives known as ZK proofs to verify transactions and state transitions without revealing sensitive information.\
\
ZK-EVM aims to improve the scalability and efficiency of Ethereum by offloading transaction processing and computation from the main chain to layer 2 networks, thereby reducing congestion and transaction costs. This technology allows developers to deploy smart contracts and interact with decentralized applications (dApps) on Ethereum while benefiting from improved performance and lower fees.

### Polygon zk-EVM

Polygon zkEVM serves as a Layer 2 framework for the Ethereum Virtual Machine (EVM), functioning as a scaling solution based on zero-knowledge (ZK) rollup technology. Utilizing cryptographic primitives known as ZK proofs, Polygon zkEVM validates state transitions securely.

Polygon zkEVM maintains EVM compatibility, accommodating the majority of Ethereum Improvement Proposals (EIPs), precompiles, and opcodes. This compatibility ensures that developers can seamlessly deploy smart contracts, utilize developer tools, and interact with wallets already operational on Ethereum, all within an ecosystem featuring substantially reduced costs.


---

# 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.nezohub.com/nezohub/overview/research/zk-evm.md?ask=<question>&goal=<endgoal>
```

`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.