# What is ZKsync Era? Validity proofs and Ethereum application compatibility

ZKsync Era is a validity-rollup network within the ZKsync ecosystem. Proofs let Ethereum verify state-transition results without replaying every transaction there. Era’s execution environment and its EVM bytecode interpreter have documented differences from Ethereum. Familiar Solidity or wallet tooling does not mean every opcode, fee calculation or contract interaction behaves identically.

Evidence: [ZKsync protocol introduction](https://docs.zksync.io/zksync-protocol/rollup); [ZKsync EVM interpreter](https://docs.zksync.io/zksync-protocol/era-vm/evm-interpreter/overview)

Canonical: https://degreesofsatoshi.com/encyclopedia/zksync-era/
Published: 2026-10-02
Substantively modified: 2026-10-02
Independently verified by an automated reviewer: 2026-10-02T19:27:58.939Z
Data current through: 2026-10-02

AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied.

## Key facts

- **Validity proofs:** The protocol verifies proofs of execution results through onchain contracts. ([ZKsync protocol introduction](https://docs.zksync.io/zksync-protocol/rollup))
- **EraVM:** EraVM is a distinct execution environment. ([ZKsync EVM interpreter](https://docs.zksync.io/zksync-protocol/era-vm/evm-interpreter/overview))
- **Interpreter:** An EVM bytecode interpreter supports an additional compatibility path. ([ZKsync EVM interpreter](https://docs.zksync.io/zksync-protocol/era-vm/evm-interpreter/overview))

## Verification and data availability are separate needs

A validity proof supports the correctness of a computation under the proof system’s rules. The chain also needs data availability so observers can reconstruct relevant state. ZKsync’s broader technology supports multiple configurations, including rollups and validiums.

Therefore, identify the actual network and configuration before applying one ZKsync description to every chain built with the stack.

Evidence: [ZKsync protocol introduction](https://docs.zksync.io/zksync-protocol/rollup)

## A contract can compile yet need compatibility checks

Suppose a project wants to deploy existing EVM bytecode on Era. The documented interpreter provides a route for that bytecode, while native EraVM deployment is another execution mode. The project must still check the interpreter’s supported instructions and cross-environment call restrictions.

For example, the retrieved documentation does not support delegatecall between EVM and EraVM contracts. Passing an ordinary compilation step does not test that boundary.

Evidence: [ZKsync EVM interpreter](https://docs.zksync.io/zksync-protocol/era-vm/evm-interpreter/overview)

## Do not infer privacy or instant settlement from the name

A zero-knowledge proof system can be used to prove execution validity without making all application data private. The network’s actual transaction and data-publication design determines what observers can see.

Similarly, proof generation, Ethereum verification and withdrawal execution are separate parts of a user flow. Check the current network documentation rather than treating validity-rollup as a fixed-time payout guarantee.

Evidence: [ZKsync protocol introduction](https://docs.zksync.io/zksync-protocol/rollup); [ZKsync EVM interpreter](https://docs.zksync.io/zksync-protocol/era-vm/evm-interpreter/overview)

## Questions

### Is EraVM exactly the Ethereum Virtual Machine?

No. It has its own instruction set and execution model. The EVM interpreter adds a compatibility route with documented limitations.

Evidence: [ZKsync EVM interpreter](https://docs.zksync.io/zksync-protocol/era-vm/evm-interpreter/overview)

### Does ZKsync mean every transaction is confidential?

No. A proof system used for execution validity does not automatically conceal application data. Privacy depends on the actual protocol and application design.

Evidence: [ZKsync protocol introduction](https://docs.zksync.io/zksync-protocol/rollup)

## Claims and scope

### zksync-era-quick-answer

ZKsync Era is a validity-rollup network within the ZKsync ecosystem. Proofs let Ethereum verify state-transition results without replaying every transaction there. Era’s execution environment and its EVM bytecode interpreter have documented differences from Ethereum. Familiar Solidity or wallet tooling does not mean every opcode, fee calculation or contract interaction behaves identically.

Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

### zksync-era-fact-validity-proofs

Validity proofs: The protocol verifies proofs of execution results through onchain contracts.

Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

### zksync-era-fact-eravm

EraVM: EraVM is a distinct execution environment.

Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

### zksync-era-fact-interpreter

Interpreter: An EVM bytecode interpreter supports an additional compatibility path.

Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

## Sources

- [ZKsync protocol introduction](https://docs.zksync.io/zksync-protocol/rollup) — ZKsync. Validity-proof execution and Ethereum settlement; deployment-specific compatibility. Locator: ZKsync Era; execution; proofs. Retrieved: 2026-10-02T18:55:27.606Z.
- [ZKsync EVM interpreter](https://docs.zksync.io/zksync-protocol/era-vm/evm-interpreter/overview) — ZKsync. EVM bytecode interpretation and EraVM execution have documented compatibility boundaries. Locator: Execution environments; interpreter. Retrieved: 2026-10-02T18:55:28.128Z.

## Revision history

- 2026-10-02: First publication after primary-source research and separate automated verification.

## Cite this entry

Degrees of Satoshi editorial project. “What is ZKsync Era? Validity proofs and Ethereum application compatibility.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/zksync-era/