# Glamsterdam Readiness

> Evidence-backed readiness guidance for builders and agents preparing for candidate Glamsterdam Ethereum upgrade changes.

- Status: watch
- Review status: reviewed
- Last verified: 2026-06-07

## Why it matters

Glamsterdam may change EVM capabilities, gas pricing, protocol architecture, block construction, native ETH transfer observability, and validator/operator workflows. Builders need a structured way to understand which stack assumptions to assess, monitor, or update as official upgrade scope evolves.

## Candidate change areas

### block level access lists
- Status: watch
- Action: monitor
- Recommendation strength: watch
- Priority: medium
- Summary: Block-Level Access Lists are a protocol-level headliner under consideration for Glamsterdam and may affect block data models, state-access analysis, simulation tooling, indexers, and explorers.
- Possible consequences:
  - Block schemas and explorer views may need new fields or explanations.
  - State-access analysis tools may need updated data sources.
  - Simulation tools may need to incorporate block-level access list semantics.

### epbs
- Status: watch
- Action: monitor
- Recommendation strength: watch
- Priority: medium
- Summary: Enshrined Proposer-Builder Separation is a protocol-level headliner under consideration for Glamsterdam and may affect block construction, MEV tooling, validator workflows, and monitoring.
- Possible consequences:
  - Block construction assumptions may need to be revisited.
  - Monitoring dashboards may need new protocol-level signals.
  - Validator and builder workflows may need updated guidance once design details stabilize.

### gas repricing
- Status: watch
- Action: assess
- Recommendation strength: watch
- Priority: medium
- Summary: A comprehensive gas repricing package is being considered for Glamsterdam and may affect transaction costs and gas-sensitive contract assumptions.
- Possible consequences:
  - Existing gas benchmarks may become stale.
  - Contracts relying on tight gas assumptions may need retesting.
  - Wallet gas estimation heuristics may need updates.
  - Simulation and benchmarking tools may need new baselines.

### max contract size
- Status: watch
- Action: monitor
- Recommendation strength: watch
- Priority: low
- Summary: Increased maximum contract size is being considered for Glamsterdam and may change deployment, verification, and audit assumptions for large contracts.
- Possible consequences:
  - Protocols constrained by size limits may revisit architecture choices.
  - Deployment and verification tools may need updated assumptions.
  - Audit workflows may need to account for larger deployable contracts.

### native eth transfer logs
- Status: watch
- Action: assess
- Recommendation strength: watch
- Priority: medium
- Summary: Native ETH transfer logs are being considered for Glamsterdam and may affect how indexers, explorers, wallets, and analytics pipelines detect ETH transfers.
- Possible consequences:
  - ETH transfer detection assumptions may change.
  - Explorers and wallet activity feeds may need new test cases.
  - Analytics and accounting pipelines may need updated parsing logic.
  - Historical and post-upgrade transfer views may need clear boundary handling.

### new evm opcodes
- Status: watch
- Action: monitor
- Recommendation strength: watch
- Priority: medium
- Summary: New EVM opcodes are being considered for Glamsterdam and may require updates across compilers, static analysis, templates, and developer education.
- Possible consequences:
  - Compiler and tooling support may lag protocol specification updates.
  - Static analyzers and linters may need opcode-aware updates.
  - Examples and templates may need revision once specific opcodes are finalized.

### validator exit consolidation
- Status: watch
- Action: monitor
- Recommendation strength: watch
- Priority: medium
- Summary: Validator exit and consolidation improvements are being considered for Glamsterdam and may affect staking dashboards, operator workflows, and monitoring alerts.
- Possible consequences:
  - Exit and consolidation status displays may need updates.
  - Operator runbooks and alerting rules may need revision.
  - Staking products may need to explain changed workflows to users.

## Initiative intents

- **Assess my app for Glamsterdam impact** (assess-glamsterdam-app-impact) — Check whether an application stack may be affected by candidate Glamsterdam changes and return watch-only or actionable next steps with citations.
- **Prepare my indexer or explorer for Glamsterdam** (prepare-glamsterdam-indexer) — Assess indexer, analytics, wallet activity feed, or block explorer assumptions that may be affected by native ETH transfer logs or block-level access lists.
- **Monitor gas repricing risk for my contracts** (monitor-glamsterdam-gas-risk) — Identify gas-sensitive contract paths and benchmarking assumptions that should be retested if Glamsterdam gas repricing changes are finalized.
- **Prepare validator or operator tooling for Glamsterdam** (prepare-glamsterdam-validator-tooling) — Track candidate validator exit/consolidation improvements and ePBS implications for validator dashboards, operator workflows, and monitoring tools.
- **Track Glamsterdam EIP status changes** (track-glamsterdam-eip-status) — Track reviewed status changes for Glamsterdam candidate areas and keep agent answers aligned with official sources instead of stale priors.

## Official sources

- [Ethereum Foundation ESP Glamsterdam Grants Round](https://esp.ethereum.foundation/applicants/wishlist/glamsterdam-round)
- [Glamsterdam Meta EIP](https://eips.ethereum.org/EIPS/eip-7773)
- [Forkcast Glamsterdam tracker](https://forkcast.org/upgrade/glamsterdam)
- [Ethereum.org Glamsterdam roadmap](https://ethereum.org/roadmap/glamsterdam/)
- [Ethereum All Core Devs calls](https://github.com/ethereum/pm)

## What the agent receives

```json
{
  "initiative": "glamsterdam-readiness",
  "name": "Glamsterdam Readiness",
  "status": "watch",
  "registry_version": "2026.06.10-8752c9d",
  "supported_intents": [
    {
      "id": "assess-glamsterdam-app-impact",
      "title": "Assess my app for Glamsterdam impact",
      "related_changes": [
        "glamsterdam-gas-repricing",
        "glamsterdam-new-evm-opcodes",
        "glamsterdam-max-contract-size",
        "glamsterdam-native-eth-transfer-logs",
        "glamsterdam-epbs",
        "glamsterdam-block-level-access-lists"
      ]
    },
    {
      "id": "prepare-glamsterdam-indexer",
      "title": "Prepare my indexer or explorer for Glamsterdam",
      "related_changes": [
        "glamsterdam-native-eth-transfer-logs",
        "glamsterdam-block-level-access-lists"
      ]
    },
    {
      "id": "monitor-glamsterdam-gas-risk",
      "title": "Monitor gas repricing risk for my contracts",
      "related_changes": [
        "glamsterdam-gas-repricing"
      ]
    },
    {
      "id": "prepare-glamsterdam-validator-tooling",
      "title": "Prepare validator or operator tooling for Glamsterdam",
      "related_changes": [
        "glamsterdam-validator-exit-consolidation",
        "glamsterdam-epbs"
      ]
    },
    {
      "id": "track-glamsterdam-eip-status",
      "title": "Track Glamsterdam EIP status changes",
      "related_changes": [
        "glamsterdam-gas-repricing",
        "glamsterdam-new-evm-opcodes",
        "glamsterdam-max-contract-size",
        "glamsterdam-native-eth-transfer-logs",
        "glamsterdam-validator-exit-consolidation",
        "glamsterdam-epbs",
        "glamsterdam-block-level-access-lists"
      ]
    }
  ],
  "changes": [
    {
      "id": "glamsterdam-block-level-access-lists",
      "type": "protocol_architecture",
      "status": "watch",
      "priority": "medium",
      "recommended_action": "monitor",
      "recommendation_strength": "watch",
      "affected_roles": [
        "block_data_models",
        "state_access_analysis",
        "simulation_tooling",
        "indexers",
        "block_explorers"
      ],
      "possible_consequences": [
        "Block schemas and explorer views may need new fields or explanations.",
        "State-access analysis tools may need updated data sources.",
        "Simulation tools may need to incorporate block-level access list semantics."
      ],
      "evidence_refs": [
        "official:esp-glamsterdam-round",
        "official:eip-7773",
        "official:forkcast-glamsterdam"
      ]
    },
    {
      "id": "glamsterdam-epbs",
      "type": "protocol_architecture",
      "status": "watch",
      "priority": "medium",
      "recommended_action": "monitor",
      "recommendation_strength": "watch",
      "affected_roles": [
        "block_building",
        "mev_tooling",
        "validator_workflows",
        "relay_monitoring",
        "protocol_research"
      ],
      "possible_consequences": [
        "Block construction assumptions may need to be revisited.",
        "Monitoring dashboards may need new protocol-level signals.",
        "Validator and builder workflows may need updated guidance once design details stabilize."
      ],
      "evidence_refs": [
        "official:esp-glamsterdam-round",
        "official:eip-7773",
        "official:forkcast-glamsterdam"
      ]
    },
    {
      "id": "glamsterdam-gas-repricing",
      "type": "gas_pricing",
      "status": "watch",
      "priority": "medium",
      "recommended_action": "assess",
      "recommendation_strength": "watch",
      "affected_roles": [
        "smart_contracts",
        "gas_estimation",
        "benchmarking",
        "simulations",
        "wallet_gas_ux"
      ],
      "possible_consequences": [
        "Existing gas benchmarks may become stale.",
        "Contracts relying on tight gas assumptions may need retesting.",
        "Wallet gas estimation heuristics may need updates.",
        "Simulation and benchmarking tools may need new baselines."
      ],
      "evidence_refs": [
        "official:esp-glamsterdam-round",
        "official:eip-7773",
        "official:forkcast-glamsterdam"
      ]
    },
    {
      "id": "glamsterdam-max-contract-size",
      "type": "evm_capability",
      "status": "watch",
      "priority": "low",
      "recommended_action": "monitor",
      "recommendation_strength": "watch",
      "affected_roles": [
        "contract_development",
        "deployment_tooling",
        "verification_tooling",
        "audit_workflows"
      ],
      "possible_consequences": [
        "Protocols constrained by size limits may revisit architecture choices.",
        "Deployment and verification tools may need updated assumptions.",
        "Audit workflows may need to account for larger deployable contracts."
      ],
      "evidence_refs": [
        "official:esp-glamsterdam-round",
        "official:eip-7773",
        "official:forkcast-glamsterdam"
      ]
    },
    {
      "id": "glamsterdam-native-eth-transfer-logs",
      "type": "indexer_surface",
      "status": "watch",
      "priority": "medium",
      "recommended_action": "assess",
      "recommendation_strength": "watch",
      "affected_roles": [
        "indexers",
        "block_explorers",
        "wallet_activity_feeds",
        "analytics",
        "accounting_tools"
      ],
      "possible_consequences": [
        "ETH transfer detection assumptions may change.",
        "Explorers and wallet activity feeds may need new test cases.",
        "Analytics and accounting pipelines may need updated parsing logic.",
        "Historical and post-upgrade transfer views may need clear boundary handling."
      ],
      "evidence_refs": [
        "official:esp-glamsterdam-round",
        "official:eip-7773",
        "official:forkcast-glamsterdam"
      ]
    },
    {
      "id": "glamsterdam-new-evm-opcodes",
      "type": "evm_capability",
      "status": "watch",
      "priority": "medium",
      "recommended_action": "monitor",
      "recommendation_strength": "watch",
      "affected_roles": [
        "contract_development",
        "compiler_tooling",
        "static_analysis",
        "templates"
      ],
      "possible_consequences": [
        "Compiler and tooling support may lag protocol specification updates.",
        "Static analyzers and linters may need opcode-aware updates.",
        "Examples and templates may need revision once specific opcodes are finalized."
      ],
      "evidence_refs": [
        "official:esp-glamsterdam-round",
        "official:eip-7773",
        "official:forkcast-glamsterdam"
      ]
    },
    {
      "id": "glamsterdam-validator-exit-consolidation",
      "type": "validator_tooling",
      "status": "watch",
      "priority": "medium",
      "recommended_action": "monitor",
      "recommendation_strength": "watch",
      "affected_roles": [
        "validator_tooling",
        "operator_dashboards",
        "staking_workflows",
        "monitoring"
      ],
      "possible_consequences": [
        "Exit and consolidation status displays may need updates.",
        "Operator runbooks and alerting rules may need revision.",
        "Staking products may need to explain changed workflows to users."
      ],
      "evidence_refs": [
        "official:esp-glamsterdam-round",
        "official:eip-7773",
        "official:forkcast-glamsterdam"
      ]
    }
  ]
}
```

---
Canonical: https://composewith.eth/initiatives/glamsterdam-readiness · JSON: https://composewith.eth/initiatives/glamsterdam-readiness/index.json