Encyclopedia Ethereum · Entry 279
What is ZKsync Era? Validity proofs and Ethereum application compatibility
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Validity proofs | The protocol verifies proofs of execution results through onchain contracts. | [1] |
| EraVM | EraVM is a distinct execution environment. | [2] |
| Interpreter | An EVM bytecode interpreter supports an additional compatibility path. | [2] |
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.
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.
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.
Direct answers
Questions people ask
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.
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.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
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: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimValidity proofs: The protocol verifies proofs of execution results through onchain contracts.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimEraVM: EraVM is a distinct execution environment.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimInterpreter: An EVM bytecode interpreter supports an additional compatibility path.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimRevision history
- — First publication after primary-source research and separate automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- ZKsync protocol introductionZKsync
Validity-proof execution and Ethereum settlement; deployment-specific compatibility.
Locator: ZKsync Era; execution; proofs · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:27.606ZOpen source - ZKsync EVM interpreterZKsync
EVM bytecode interpretation and EraVM execution have documented compatibility boundaries.
Locator: Execution environments; interpreter · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:28.128ZOpen source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees 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/