{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "zksync-era",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/zksync-era/",
  "collection": "ethereum",
  "title": "What is ZKsync Era? Validity proofs and Ethereum application compatibility",
  "description": "Understand ZKsync Era’s validity-proof model and why Ethereum tooling compatibility depends on the execution mode and documented differences.",
  "aliases": [
    "ZKsync Era explained",
    "ZKsync Ethereum compatibility"
  ],
  "dates": {
    "published": "2026-10-02",
    "modified": "2026-10-02",
    "verified": "2026-10-02T19:27:58.939Z",
    "dataAsOf": "2026-10-02"
  },
  "authorship": {
    "publisher": "Degrees of Satoshi editorial project",
    "process": "AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied."
  },
  "quickAnswer": {
    "text": "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.",
    "claimId": "zksync-era-quick-answer",
    "sourceIds": [
      "x425-eth-zksync",
      "x425-eth-zksync-compat"
    ]
  },
  "keyFacts": [
    {
      "label": "Validity proofs",
      "value": "The protocol verifies proofs of execution results through onchain contracts.",
      "sourceIds": [
        "x425-eth-zksync"
      ],
      "id": "validity-proofs",
      "claimId": "zksync-era-fact-validity-proofs"
    },
    {
      "label": "EraVM",
      "value": "EraVM is a distinct execution environment.",
      "sourceIds": [
        "x425-eth-zksync-compat"
      ],
      "id": "eravm",
      "claimId": "zksync-era-fact-eravm"
    },
    {
      "label": "Interpreter",
      "value": "An EVM bytecode interpreter supports an additional compatibility path.",
      "sourceIds": [
        "x425-eth-zksync-compat"
      ],
      "id": "interpreter",
      "claimId": "zksync-era-fact-interpreter"
    }
  ],
  "prerequisites": [
    "validity-rollups",
    "ethereum-virtual-machine"
  ],
  "sections": [
    {
      "id": "proofs",
      "heading": "Verification and data availability are separate needs",
      "sourceIds": [
        "x425-eth-zksync"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "example",
      "heading": "A contract can compile yet need compatibility checks",
      "sourceIds": [
        "x425-eth-zksync-compat"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "scope",
      "heading": "Do not infer privacy or instant settlement from the name",
      "sourceIds": [
        "x425-eth-zksync",
        "x425-eth-zksync-compat"
      ],
      "paragraphs": [
        "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."
      ]
    }
  ],
  "faq": [
    {
      "question": "Is EraVM exactly the Ethereum Virtual Machine?",
      "answer": "No. It has its own instruction set and execution model. The EVM interpreter adds a compatibility route with documented limitations.",
      "sourceIds": [
        "x425-eth-zksync-compat"
      ]
    },
    {
      "question": "Does ZKsync mean every transaction is confidential?",
      "answer": "No. A proof system used for execution validity does not automatically conceal application data. Privacy depends on the actual protocol and application design.",
      "sourceIds": [
        "x425-eth-zksync"
      ]
    }
  ],
  "claims": [
    {
      "id": "zksync-era-quick-answer",
      "articleSlug": "zksync-era",
      "statement": "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.",
      "sourceIds": [
        "source-fac628b4e8303ccd",
        "source-3299ab93a27e0e29"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-fac628b4e8303ccd",
          "locator": "ZKsync Era; execution; proofs"
        },
        {
          "sourceId": "source-3299ab93a27e0e29",
          "locator": "Execution environments; interpreter"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read protocol overview and entire EraVM EVM-interpreter guide. Validity computation and data availability distinct; stack supports rollup/validium configurations. Interpreter supports EVM bytecode but no cross-environment delegatecall; native EraVM not identical EVM. Proof of execution alone does not imply confidential application data or instant payout."
        ]
      }
    },
    {
      "id": "zksync-era-fact-validity-proofs",
      "articleSlug": "zksync-era",
      "statement": "Validity proofs: The protocol verifies proofs of execution results through onchain contracts.",
      "sourceIds": [
        "source-fac628b4e8303ccd"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-fac628b4e8303ccd",
          "locator": "ZKsync Era; execution; proofs"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read protocol overview and entire EraVM EVM-interpreter guide. Validity computation and data availability distinct; stack supports rollup/validium configurations. Interpreter supports EVM bytecode but no cross-environment delegatecall; native EraVM not identical EVM. Proof of execution alone does not imply confidential application data or instant payout."
        ]
      }
    },
    {
      "id": "zksync-era-fact-eravm",
      "articleSlug": "zksync-era",
      "statement": "EraVM: EraVM is a distinct execution environment.",
      "sourceIds": [
        "source-3299ab93a27e0e29"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-3299ab93a27e0e29",
          "locator": "Execution environments; interpreter"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read protocol overview and entire EraVM EVM-interpreter guide. Validity computation and data availability distinct; stack supports rollup/validium configurations. Interpreter supports EVM bytecode but no cross-environment delegatecall; native EraVM not identical EVM. Proof of execution alone does not imply confidential application data or instant payout."
        ]
      }
    },
    {
      "id": "zksync-era-fact-interpreter",
      "articleSlug": "zksync-era",
      "statement": "Interpreter: An EVM bytecode interpreter supports an additional compatibility path.",
      "sourceIds": [
        "source-3299ab93a27e0e29"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-3299ab93a27e0e29",
          "locator": "Execution environments; interpreter"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read protocol overview and entire EraVM EVM-interpreter guide. Validity computation and data availability distinct; stack supports rollup/validium configurations. Interpreter supports EVM bytecode but no cross-environment delegatecall; native EraVM not identical EVM. Proof of execution alone does not imply confidential application data or instant payout."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "x425-eth-zksync",
      "label": "ZKsync protocol introduction",
      "publisher": "ZKsync",
      "url": "https://docs.zksync.io/zksync-protocol/rollup",
      "locator": "ZKsync Era; execution; proofs",
      "note": "Validity-proof execution and Ethereum settlement; deployment-specific compatibility.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:27.606Z",
      "contentSha256": "35b05d2bb487f0fe5a555a8e4372646f1ae95cdda528cddb6e6ffb285b9c8886",
      "recordId": "source-fac628b4e8303ccd"
    },
    {
      "id": "x425-eth-zksync-compat",
      "label": "ZKsync EVM interpreter",
      "publisher": "ZKsync",
      "url": "https://docs.zksync.io/zksync-protocol/era-vm/evm-interpreter/overview",
      "locator": "Execution environments; interpreter",
      "note": "EVM bytecode interpretation and EraVM execution have documented compatibility boundaries.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:28.128Z",
      "contentSha256": "03b7c5d50ec1ed8eef7b4a315d86e9845870b567e2b62db6ba676ba7907b414f",
      "recordId": "source-3299ab93a27e0e29"
    }
  ],
  "related": {
    "articles": [
      "validity-rollups",
      "ethereum-virtual-machine",
      "delegatecall-explained",
      "optimism-op-mainnet",
      "starknet"
    ],
    "dossiers": [],
    "wallets": []
  },
  "revisionHistory": [
    {
      "date": "2026-10-02",
      "kind": "published",
      "summary": "First publication after primary-source research and separate automated verification."
    }
  ],
  "citation": "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/"
}