{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "comparing-ethereum-layer-2s",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/comparing-ethereum-layer-2s/",
  "collection": "ethereum",
  "title": "Comparing Ethereum layer 2s: the questions behind a cheap transfer",
  "description": "Compare Ethereum scaling networks using data location, proof design, operational controls, compatibility and exit conditions.",
  "aliases": [
    "compare Ethereum layer 2 networks",
    "rollup security differences"
  ],
  "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": "Compare a layer-2 network by what Ethereum verifies, where users can obtain its data, who orders transactions, who can change its contracts and how assets exit. Also check application compatibility and the exact token route. A low fee or a familiar EVM interface answers only part of that comparison; a broad label such as rollup does not describe every current deployment detail.",
    "claimId": "comparing-ethereum-layer-2s-quick-answer",
    "sourceIds": [
      "x425-eth-eth-l2",
      "x425-eth-arbitrum-nitro",
      "x425-eth-op-intro",
      "x425-eth-zksync"
    ]
  },
  "keyFacts": [
    {
      "label": "Data",
      "value": "Ethereum publication and committee-backed availability have different assumptions.",
      "sourceIds": [
        "x425-eth-arbitrum-nitro"
      ],
      "id": "data",
      "claimId": "comparing-ethereum-layer-2s-fact-data"
    },
    {
      "label": "Proofs",
      "value": "Optimistic and validity systems establish state claims through different mechanisms.",
      "sourceIds": [
        "x425-eth-arbitrum-nitro",
        "x425-eth-zksync"
      ],
      "id": "proofs",
      "claimId": "comparing-ethereum-layer-2s-fact-proofs"
    },
    {
      "label": "Compatibility",
      "value": "EVM tooling compatibility can still have documented execution differences.",
      "sourceIds": [
        "x425-eth-zksync-compat",
        "x425-eth-op-intro"
      ],
      "id": "compatibility",
      "claimId": "comparing-ethereum-layer-2s-fact-compatibility"
    }
  ],
  "prerequisites": [
    "ethereum-layer-2"
  ],
  "sections": [
    {
      "id": "security",
      "heading": "Ask what evidence the parent chain checks",
      "sourceIds": [
        "x425-eth-eth-l2",
        "x425-eth-arbitrum-nitro",
        "x425-eth-zksync"
      ],
      "paragraphs": [
        "For a rollup, identify how state claims are verified and how data is made available. A validity proof and an optimistic challenge mechanism are different designs. A committee certificate adds an availability assumption distinct from publishing full data to Ethereum.",
        "Then examine the actual implementation and operational controls. A theoretical design description does not tell you whether every feature is deployed or who can upgrade the bridge contracts."
      ]
    },
    {
      "id": "example",
      "heading": "Two cheap transfers can hide different exit paths",
      "sourceIds": [
        "x425-eth-op-withdrawals",
        "x425-eth-base-finality"
      ],
      "paragraphs": [
        "Suppose two networks both quote a small local transfer fee. One withdrawal route may require several later Ethereum transactions and waiting conditions, while another uses a different proof and finalization path. The local transfer price alone cannot compare the complete cost or time of moving funds back.",
        "Use the whole intended journey: entry, activity and exit. Quote live costs only with their network, action and observation time."
      ]
    },
    {
      "id": "fit",
      "heading": "Match the network to the operation",
      "sourceIds": [
        "x425-eth-zksync-compat",
        "x425-eth-starknet-accounts",
        "x425-eth-eth-l2"
      ],
      "paragraphs": [
        "A familiar EVM application, a native smart-account application and a cross-chain treasury can have different requirements. Check wallet support, execution differences, destination asset identity and recovery options for that particular task.",
        "Keep the result as a documented comparison rather than a universal safety ranking. A configuration or upgrade can change a material assumption after a comparison is written."
      ]
    }
  ],
  "faq": [
    {
      "question": "Is the lowest displayed fee enough to choose a network?",
      "answer": "No. Include the intended transfer route, later fees, waiting conditions, asset support and the network’s documented trust assumptions.",
      "sourceIds": [
        "x425-eth-eth-l2",
        "x425-eth-op-withdrawals"
      ]
    },
    {
      "question": "Does using Ethereum settlement make every L2 equally secure?",
      "answer": "No. Data availability, proof deployment, administrative controls and bridges can differ. Inspect the particular network rather than relying only on its category.",
      "sourceIds": [
        "x425-eth-eth-l2",
        "x425-eth-arbitrum-nitro",
        "x425-eth-zksync"
      ]
    }
  ],
  "claims": [
    {
      "id": "comparing-ethereum-layer-2s-quick-answer",
      "articleSlug": "comparing-ethereum-layer-2s",
      "statement": "Compare a layer-2 network by what Ethereum verifies, where users can obtain its data, who orders transactions, who can change its contracts and how assets exit. Also check application compatibility and the exact token route. A low fee or a familiar EVM interface answers only part of that comparison; a broad label such as rollup does not describe every current deployment detail.",
      "sourceIds": [
        "source-3bb455cecdb5481e",
        "source-2d1073e5ab3a8020",
        "source-bba91fdf8532e63b",
        "source-fac628b4e8303ccd"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-3bb455cecdb5481e",
          "locator": "Rollups; sidechains; bridges; considerations"
        },
        {
          "sourceId": "source-2d1073e5ab3a8020",
          "locator": "Transaction journey; rollup; AnyTrust"
        },
        {
          "sourceId": "source-bba91fdf8532e63b",
          "locator": "OP Stack; components; deployments"
        },
        {
          "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": [
          "Checked each comparison against Nitro, ZKsync, OP, Base, Starknet and Ethereum L2 sources. Added Nitro to proof-design key fact because current generic L2 landing page does not itself explain optimistic challenge mechanics. Data publication, committee availability, controls, compatibility and full withdrawal journey remain separate dimensions, with no live ranking or fee estimate."
        ]
      }
    },
    {
      "id": "comparing-ethereum-layer-2s-fact-data",
      "articleSlug": "comparing-ethereum-layer-2s",
      "statement": "Data: Ethereum publication and committee-backed availability have different assumptions.",
      "sourceIds": [
        "source-2d1073e5ab3a8020"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-2d1073e5ab3a8020",
          "locator": "Transaction journey; rollup; AnyTrust"
        }
      ],
      "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": [
          "Checked each comparison against Nitro, ZKsync, OP, Base, Starknet and Ethereum L2 sources. Added Nitro to proof-design key fact because current generic L2 landing page does not itself explain optimistic challenge mechanics. Data publication, committee availability, controls, compatibility and full withdrawal journey remain separate dimensions, with no live ranking or fee estimate."
        ]
      }
    },
    {
      "id": "comparing-ethereum-layer-2s-fact-proofs",
      "articleSlug": "comparing-ethereum-layer-2s",
      "statement": "Proofs: Optimistic and validity systems establish state claims through different mechanisms.",
      "sourceIds": [
        "source-2d1073e5ab3a8020",
        "source-fac628b4e8303ccd"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-2d1073e5ab3a8020",
          "locator": "Transaction journey; rollup; AnyTrust"
        },
        {
          "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": [
          "Checked each comparison against Nitro, ZKsync, OP, Base, Starknet and Ethereum L2 sources. Added Nitro to proof-design key fact because current generic L2 landing page does not itself explain optimistic challenge mechanics. Data publication, committee availability, controls, compatibility and full withdrawal journey remain separate dimensions, with no live ranking or fee estimate."
        ]
      }
    },
    {
      "id": "comparing-ethereum-layer-2s-fact-compatibility",
      "articleSlug": "comparing-ethereum-layer-2s",
      "statement": "Compatibility: EVM tooling compatibility can still have documented execution differences.",
      "sourceIds": [
        "source-3299ab93a27e0e29",
        "source-bba91fdf8532e63b"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-3299ab93a27e0e29",
          "locator": "Execution environments; interpreter"
        },
        {
          "sourceId": "source-bba91fdf8532e63b",
          "locator": "OP Stack; components; deployments"
        }
      ],
      "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": [
          "Checked each comparison against Nitro, ZKsync, OP, Base, Starknet and Ethereum L2 sources. Added Nitro to proof-design key fact because current generic L2 landing page does not itself explain optimistic challenge mechanics. Data publication, committee availability, controls, compatibility and full withdrawal journey remain separate dimensions, with no live ranking or fee estimate."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "x425-eth-eth-l2",
      "label": "Ethereum layer 2",
      "publisher": "ethereum.org contributors",
      "url": "https://ethereum.org/en/layer-2/",
      "locator": "Rollups; sidechains; bridges; considerations",
      "note": "Rollup comparison dimensions and limits of transferring broad labels to a named deployment.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:27.801Z",
      "contentSha256": "eaf6582da260acaa246e6373d541902af66ee1a2c9af6c6e116ae30ad1e47bbe",
      "recordId": "source-3bb455cecdb5481e"
    },
    {
      "id": "x425-eth-arbitrum-nitro",
      "label": "Inside Arbitrum Nitro",
      "publisher": "Offchain Labs",
      "url": "https://docs.arbitrum.io/how-arbitrum-works/inside-arbitrum-nitro",
      "locator": "Transaction journey; rollup; AnyTrust",
      "note": "Nitro rollup execution and Ethereum batch publication versus AnyTrust committee assumptions.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:27.094Z",
      "contentSha256": "b0e9819a15eacadbab163dd3255ded4025880453fde823e0aa5df2ff03d83990",
      "recordId": "source-2d1073e5ab3a8020"
    },
    {
      "id": "x425-eth-op-intro",
      "label": "OP Stack overview",
      "publisher": "Optimism",
      "url": "https://docs.optimism.io/stack/getting-started",
      "locator": "OP Stack; components; deployments",
      "note": "Reusable rollup software and chain-specific configuration.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:27.607Z",
      "contentSha256": "a4389f228bd876c5659c6d6cd66dedef48ac6d87844bb0a8e586e0be98e53c6e",
      "recordId": "source-bba91fdf8532e63b"
    },
    {
      "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"
    },
    {
      "id": "x425-eth-op-withdrawals",
      "label": "OP Stack withdrawal flow",
      "publisher": "Optimism",
      "url": "https://docs.optimism.io/stack/transactions/withdrawal-flow",
      "locator": "Initiate; prove; finalize; fault proofs",
      "note": "L2-to-L1 withdrawals require distinct onchain stages and protocol waits.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:27.608Z",
      "contentSha256": "445bbe7491370f3ca29ea4b597dcc3c10376c9d98a7415617f67df6267c31f51",
      "recordId": "source-78235bf07c29d69c"
    },
    {
      "id": "x425-eth-base-finality",
      "label": "Base transaction finality",
      "publisher": "Base",
      "url": "https://docs.base.org/specifications/transactions/transaction-finality",
      "locator": "Finality stages",
      "note": "Distinguish Base preconfirmation, block inclusion, Ethereum data finality and withdrawal completion.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:27.802Z",
      "contentSha256": "efb1d2a37a948b7f760bd3fc7aa4f3215b157de8f3988f491267ccccd78a25c7",
      "recordId": "source-1a6f029f321db9d7"
    },
    {
      "id": "x425-eth-starknet-accounts",
      "label": "Starknet accounts",
      "publisher": "Starknet",
      "url": "https://docs.starknet.io/learn/protocol/accounts.md",
      "locator": "Account abstraction; validation",
      "note": "Native contract-account validation and execution differ from Ethereum EOAs.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:28.472Z",
      "contentSha256": "eb127957d409f1ad4df0c20fb981a6e2b43a105a2d559f962bd0528fae4b1102",
      "recordId": "source-d3fa7c1cf136824b"
    }
  ],
  "related": {
    "articles": [
      "optimistic-rollups",
      "validity-rollups",
      "rollup-sequencers",
      "ethereum-blobs-data-availability",
      "base-network",
      "rollup-withdrawal-troubleshooting"
    ],
    "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. “Comparing Ethereum layer 2s: the questions behind a cheap transfer.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/comparing-ethereum-layer-2s/"
}