{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "ethereum-layer-2",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/ethereum-layer-2/",
  "collection": "ethereum",
  "title": "Ethereum layer 2: execution elsewhere, settlement on Ethereum",
  "description": "Follow an illustrative rollup payment to distinguish layer-2 execution, Ethereum settlement, separate balances, bridges and implementation-specific risks.",
  "aliases": [
    "L2",
    "Ethereum rollup",
    "layer two"
  ],
  "dates": {
    "published": "2026-10-02",
    "modified": "2026-10-02",
    "verified": "2026-10-02T15:10:23.134Z",
    "dataAsOf": null
  },
  "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": "An Ethereum layer 2 processes activity outside Ethereum’s main execution layer while using Ethereum for important security or settlement functions. Rollups publish data and state-related commitments to Ethereum and use disputes or validity proofs. Their actual guarantees also depend on their implementation, upgrade controls, data availability and exit mechanisms.",
    "claimId": "ethereum-layer-2-quick-answer",
    "sourceIds": [
      "scaling",
      "optimistic",
      "validity"
    ]
  },
  "keyFacts": [
    {
      "label": "Execution",
      "value": "A rollup processes transactions outside L1 execution",
      "sourceIds": [
        "scaling"
      ],
      "id": "execution",
      "claimId": "ethereum-layer-2-fact-execution"
    },
    {
      "label": "Validation model",
      "value": "Disputes or validity proofs, depending on design",
      "sourceIds": [
        "optimistic",
        "validity"
      ],
      "id": "validation-model",
      "claimId": "ethereum-layer-2-fact-validation-model"
    },
    {
      "label": "Sidechain",
      "value": "An independent consensus system is not automatically a rollup",
      "sourceIds": [
        "scaling"
      ],
      "id": "sidechain",
      "claimId": "ethereum-layer-2-fact-sidechain"
    }
  ],
  "prerequisites": [
    "what-is-ethereum",
    "ethereum-proof-of-stake-finality"
  ],
  "sections": [
    {
      "id": "division-of-work",
      "heading": "A rollup moves execution work while retaining a settlement relationship",
      "sourceIds": [
        "scaling",
        "data-availability"
      ],
      "paragraphs": [
        "Executing every small action directly on Ethereum is resource-intensive. A rollup executes a sequence of transactions elsewhere and publishes the information needed for its settlement model, sharing publication overhead across activity.",
        "Compression and batching can reduce per-user costs, but neither word is a security proof. The important questions are what gets published, how incorrect state can be rejected and how users can recover or exit."
      ]
    },
    {
      "id": "payment-example",
      "heading": "Example: a rollup receipt and Ethereum settlement are different milestones",
      "sourceIds": [
        "optimistic",
        "validity"
      ],
      "paragraphs": [
        "Suppose a user sends a token on a rollup and immediately sees an L2 receipt. The operator may later publish a batch to Ethereum. Its state commitment must then satisfy the rollup’s dispute or proof process.",
        "Calling every stage confirmed can hide these differences. A useful interface names the state: accepted by an operator, included in L2, data published, proof accepted or challenge conditions satisfied, and the relevant L1 finality."
      ]
    },
    {
      "id": "networks-and-assets",
      "heading": "The same address display does not combine all balances",
      "sourceIds": [
        "scaling",
        "accounts"
      ],
      "paragraphs": [
        "An EVM-style address can appear on several networks, but those networks keep separate state. A balance on one does not automatically become spendable on another because the address text matches.",
        "Moving an asset across networks requires a supported mechanism such as a bridge or a service transfer. Token identity, custody and withdrawal assumptions must be checked for that route, rather than inferred from a familiar symbol."
      ]
    },
    {
      "id": "security-questions",
      "heading": "Assess the deployed system, not only its category name",
      "sourceIds": [
        "optimistic",
        "validity",
        "scaling"
      ],
      "paragraphs": [
        "Rollups can differ in who sequences activity, who may submit proofs or challenges, who holds upgrade powers and what happens during an outage. Those details determine whether theoretical protections are usable in practice.",
        "A sidechain has its own consensus; a validium puts data availability elsewhere. Calling every low-fee EVM network layer 2 can erase the very distinctions a learner needs to understand."
      ]
    }
  ],
  "faq": [
    {
      "question": "Are all EVM-compatible networks Ethereum layer 2s?",
      "answer": "No. Compatibility concerns execution and tooling. An independent sidechain can be EVM-compatible while relying on its own consensus rather than rollup settlement.",
      "sourceIds": [
        "scaling"
      ]
    },
    {
      "question": "Does an L2 balance automatically appear on Ethereum mainnet?",
      "answer": "No. Different networks maintain different state. Asset movement requires a specific supported transfer or bridge process.",
      "sourceIds": [
        "scaling"
      ]
    },
    {
      "question": "Does a quick receipt mean the withdrawal is ready?",
      "answer": "Not necessarily. Operator acceptance, proof or dispute completion, L1 finality and withdrawal processing can be distinct milestones.",
      "sourceIds": [
        "optimistic",
        "validity"
      ]
    }
  ],
  "claims": [
    {
      "id": "ethereum-layer-2-quick-answer",
      "articleSlug": "ethereum-layer-2",
      "statement": "An Ethereum layer 2 processes activity outside Ethereum’s main execution layer while using Ethereum for important security or settlement functions. Rollups publish data and state-related commitments to Ethereum and use disputes or validity proofs. Their actual guarantees also depend on their implementation, upgrade controls, data availability and exit mechanisms.",
      "sourceIds": [
        "source-27bb64638570155e",
        "source-e415b897a2b02da7",
        "source-b267e88f1835f980"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-27bb64638570155e",
          "locator": "Layer 2 scaling; rollups; sidechains; validium"
        },
        {
          "sourceId": "source-e415b897a2b02da7",
          "locator": "Fraud proving; censorship resistance; exiting the rollup"
        },
        {
          "sourceId": "source-b267e88f1835f980",
          "locator": "Data availability; validity proofs; withdrawals; EVM compatibility"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T15:10:23.134Z",
        "reviewer": "automated independent verification",
        "notes": [
          "Compared scaling docs, optimistic/validity/dataavailability. Operator receipt distinct from settlement and bridge exit. EVMcompatibility not security identity."
        ]
      }
    },
    {
      "id": "ethereum-layer-2-fact-execution",
      "articleSlug": "ethereum-layer-2",
      "statement": "Execution: A rollup processes transactions outside L1 execution",
      "sourceIds": [
        "source-27bb64638570155e"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-27bb64638570155e",
          "locator": "Layer 2 scaling; rollups; sidechains; validium"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T15:10:23.134Z",
        "reviewer": "automated independent verification",
        "notes": [
          "Compared scaling docs, optimistic/validity/dataavailability. Operator receipt distinct from settlement and bridge exit. EVMcompatibility not security identity."
        ]
      }
    },
    {
      "id": "ethereum-layer-2-fact-validation-model",
      "articleSlug": "ethereum-layer-2",
      "statement": "Validation model: Disputes or validity proofs, depending on design",
      "sourceIds": [
        "source-e415b897a2b02da7",
        "source-b267e88f1835f980"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-e415b897a2b02da7",
          "locator": "Fraud proving; censorship resistance; exiting the rollup"
        },
        {
          "sourceId": "source-b267e88f1835f980",
          "locator": "Data availability; validity proofs; withdrawals; EVM compatibility"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T15:10:23.134Z",
        "reviewer": "automated independent verification",
        "notes": [
          "Compared scaling docs, optimistic/validity/dataavailability. Operator receipt distinct from settlement and bridge exit. EVMcompatibility not security identity."
        ]
      }
    },
    {
      "id": "ethereum-layer-2-fact-sidechain",
      "articleSlug": "ethereum-layer-2",
      "statement": "Sidechain: An independent consensus system is not automatically a rollup",
      "sourceIds": [
        "source-27bb64638570155e"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-27bb64638570155e",
          "locator": "Layer 2 scaling; rollups; sidechains; validium"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T15:10:23.134Z",
        "reviewer": "automated independent verification",
        "notes": [
          "Compared scaling docs, optimistic/validity/dataavailability. Operator receipt distinct from settlement and bridge exit. EVMcompatibility not security identity."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "scaling",
      "label": "Scaling overview",
      "publisher": "ethereum.org contributors",
      "url": "https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/index.md",
      "canonicalUrl": "https://ethereum.org/en/developers/docs/scaling/",
      "version": "dcc900ff125891da5b6c723b905a7113cf1bd864",
      "checkedAt": "2026-10-02T14:35:47.354550+00:00",
      "locator": "Layer 2 scaling; rollups; sidechains; validium",
      "sha256": "184af71e45f53390c4f782d936954caf42715feb82048072d79eb05495569a21",
      "note": "Supports rollup execution/settlement roles and distinct security assumptions of sidechains and offchain data systems.",
      "recordId": "source-27bb64638570155e",
      "contentSha256": "184af71e45f53390c4f782d936954caf42715feb82048072d79eb05495569a21"
    },
    {
      "id": "optimistic",
      "label": "Optimistic rollups",
      "publisher": "ethereum.org contributors",
      "url": "https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md",
      "canonicalUrl": "https://ethereum.org/en/developers/docs/scaling/optimistic-rollups/",
      "version": "dcc900ff125891da5b6c723b905a7113cf1bd864",
      "checkedAt": "2026-10-02T14:35:47.579696+00:00",
      "locator": "Fraud proving; censorship resistance; exiting the rollup",
      "sha256": "cb9e43862d4716e7fac18423a53aa8efde7597ef9ed4c19d65acb7ceca2f21cd",
      "note": "Supports challenge periods, dispute verification, sequencer ordering and withdrawal distinctions; concrete timings depend on the implementation.",
      "recordId": "source-e415b897a2b02da7",
      "contentSha256": "cb9e43862d4716e7fac18423a53aa8efde7597ef9ed4c19d65acb7ceca2f21cd"
    },
    {
      "id": "validity",
      "label": "Zero-knowledge rollups",
      "publisher": "ethereum.org contributors",
      "url": "https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md",
      "canonicalUrl": "https://ethereum.org/en/developers/docs/scaling/zk-rollups/",
      "version": "dcc900ff125891da5b6c723b905a7113cf1bd864",
      "checkedAt": "2026-10-02T14:35:47.579728+00:00",
      "locator": "Data availability; validity proofs; withdrawals; EVM compatibility",
      "sha256": "c3d22a952a4e66b8ee0bd45a80fd013b2a6ee9d78e1d346482297c2768fe2712",
      "note": "Supports validity proofs and public rollup data; no claim that every withdrawal is instant or that every ZK system is private.",
      "recordId": "source-b267e88f1835f980",
      "contentSha256": "c3d22a952a4e66b8ee0bd45a80fd013b2a6ee9d78e1d346482297c2768fe2712"
    },
    {
      "id": "data-availability",
      "label": "Data availability",
      "publisher": "ethereum.org contributors",
      "url": "https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/data-availability/index.md",
      "canonicalUrl": "https://ethereum.org/en/developers/docs/data-availability/",
      "version": "dcc900ff125891da5b6c723b905a7113cf1bd864",
      "checkedAt": "2026-10-02T14:35:47.112785+00:00",
      "locator": "Data availability problem; rollups; availability versus retrievability",
      "sha256": "8ef54fe5d3ff94dec32a7de22795770098bed269e308d5a2ad1dd6e542d909e9",
      "note": "Supports why a hash is not sufficient to reconstruct data and why availability differs from permanent historical storage.",
      "recordId": "source-73ba119e5fae20da",
      "contentSha256": "8ef54fe5d3ff94dec32a7de22795770098bed269e308d5a2ad1dd6e542d909e9"
    },
    {
      "id": "accounts",
      "label": "Ethereum accounts",
      "publisher": "ethereum.org contributors",
      "url": "https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/accounts/index.md",
      "canonicalUrl": "https://ethereum.org/en/developers/docs/accounts/",
      "version": "dcc900ff125891da5b6c723b905a7113cf1bd864",
      "checkedAt": "2026-10-02T14:35:40.369782+00:00",
      "locator": "Account types; an account examined; a note on wallets",
      "sha256": "774839a895f46d6d398c27ab56e3a3ba9eb445eae87374cf41a78e7f28ac7983",
      "note": "Supports accounts versus wallet software and account state fields. The older empty-code EOA description is qualified using EIP-7702.",
      "recordId": "source-d131f5d8edf3944c",
      "contentSha256": "774839a895f46d6d398c27ab56e3a3ba9eb445eae87374cf41a78e7f28ac7983"
    }
  ],
  "related": {
    "articles": [
      "optimistic-rollups",
      "validity-rollups",
      "ethereum-blobs-data-availability",
      "rollup-sequencers",
      "comparing-ethereum-layer-2s",
      "rollup-withdrawal-troubleshooting"
    ],
    "dossiers": [],
    "wallets": []
  },
  "revisionHistory": [
    {
      "date": "2026-10-02",
      "kind": "published",
      "summary": "First publication after primary-source research and independent automated verification."
    }
  ],
  "citation": "Degrees of Satoshi editorial project. “Ethereum layer 2: execution elsewhere, settlement on Ethereum.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-layer-2/"
}