Glamsterdam Readiness
Evidence-backed readiness guidance for builders and agents preparing for candidate Glamsterdam Ethereum upgrade changes.
Assess before you migrate.
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.
Most Glamsterdam records are watch-only because the upgrade scope is still evolving. Composewith helps builders prepare tests, audits, and monitoring without claiming candidate EIPs are finalized.
Candidate change areas and consequences.
Each record maps a protocol change area to affected roles, likely builder consequences, recommended action, and official evidence refs.
block level access lists watch
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.
Action: monitor · Priority: medium · Status: watch
- 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 watch
Enshrined Proposer-Builder Separation is a protocol-level headliner under consideration for Glamsterdam and may affect block construction, MEV tooling, validator workflows, and monitoring.
Action: monitor · Priority: medium · Status: watch
- 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 watch
A comprehensive gas repricing package is being considered for Glamsterdam and may affect transaction costs and gas-sensitive contract assumptions.
Action: assess · Priority: medium · Status: watch
- 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 watch
Increased maximum contract size is being considered for Glamsterdam and may change deployment, verification, and audit assumptions for large contracts.
Action: monitor · Priority: low · Status: watch
- 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 watch
Native ETH transfer logs are being considered for Glamsterdam and may affect how indexers, explorers, wallets, and analytics pipelines detect ETH transfers.
Action: assess · Priority: medium · Status: watch
- 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 watch
New EVM opcodes are being considered for Glamsterdam and may require updates across compilers, static analysis, templates, and developer education.
Action: monitor · Priority: medium · Status: watch
- 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 watch
Validator exit and consolidation improvements are being considered for Glamsterdam and may affect staking dashboards, operator workflows, and monitoring alerts.
Action: monitor · Priority: medium · Status: watch
- 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.
Glamsterdam-specific intents.
Agents should pick one of these initiative intents before answering or charging for a paid assessment call.
Assess my app for Glamsterdam impact
Check whether an application stack may be affected by candidate Glamsterdam changes and return watch-only or actionable next steps with citations.
Inputs: app type, chains, current protocol/dApp stack, whether the app has custom contracts, whether the app depends on indexing, simulations, analytics, or validator/operator tooling
Prepare my indexer or explorer for Glamsterdam
Assess indexer, analytics, wallet activity feed, or block explorer assumptions that may be affected by native ETH transfer logs or block-level access lists.
Inputs: indexed data types, ETH transfer detection method, block model assumptions, chain coverage
Monitor gas repricing risk for my contracts
Identify gas-sensitive contract paths and benchmarking assumptions that should be retested if Glamsterdam gas repricing changes are finalized.
Inputs: contract categories, gas-sensitive paths, benchmark or simulation approach, deployment timeline
Prepare validator or operator tooling for Glamsterdam
Track candidate validator exit/consolidation improvements and ePBS implications for validator dashboards, operator workflows, and monitoring tools.
Inputs: tooling type, exit or consolidation features, monitoring dependencies, ePBS exposure
Track Glamsterdam EIP status changes
Track reviewed status changes for Glamsterdam candidate areas and keep agent answers aligned with official sources instead of stale priors.
Inputs: EIP IDs or change areas, last checked release or date
Structured initiative guidance.
{
"initiative": "glamsterdam-readiness",
"name": "Glamsterdam Readiness",
"status": "watch",
"review_status": "reviewed",
"registry_version": "2026.06.10-8752c9d",
"instruction": "Fetch this initiative record before answering Glamsterdam-related stack, upgrade, indexer, gas-pricing, validator, ePBS, or block-level access-list questions. Treat candidate changes as watch-only unless official sources confirm stronger guidance.",
"supported_intents": [
{
"id": "assess-glamsterdam-app-impact",
"title": "Assess my app for Glamsterdam impact",
"audience": [
"app_builders",
"ai_agents"
],
"default_priority": "medium",
"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",
"audience": [
"indexer_teams",
"block_explorer_teams",
"wallet_teams",
"ai_agents"
],
"default_priority": "medium",
"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",
"audience": [
"smart_contract_developers",
"app_builders",
"defi_protocols",
"ai_agents"
],
"default_priority": "medium",
"related_changes": [
"glamsterdam-gas-repricing"
]
},
{
"id": "prepare-glamsterdam-validator-tooling",
"title": "Prepare validator or operator tooling for Glamsterdam",
"audience": [
"validator_tooling_teams",
"staking_providers",
"operator_teams",
"ai_agents"
],
"default_priority": "medium",
"related_changes": [
"glamsterdam-validator-exit-consolidation",
"glamsterdam-epbs"
]
},
{
"id": "track-glamsterdam-eip-status",
"title": "Track Glamsterdam EIP status changes",
"audience": [
"app_builders",
"protocol_teams",
"ai_agents"
],
"default_priority": "medium",
"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"
],
"affected_builder_groups": [
"indexer_teams",
"block_explorer_teams",
"simulation_tooling_teams",
"execution_client_tooling"
],
"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"
],
"affected_builder_groups": [
"validator_tooling_teams",
"mev_tooling_teams",
"block_builder_teams",
"research_tooling_teams"
],
"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"
],
"affected_builder_groups": [
"app_builders",
"smart_contract_developers",
"wallet_teams",
"defi_protocols"
],
"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"
],
"affected_builder_groups": [
"smart_contract_developers",
"protocol_teams",
"developer_tooling_teams"
],
"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"
],
"affected_builder_groups": [
"indexer_teams",
"block_explorer_teams",
"wallet_teams",
"analytics_teams"
],
"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"
],
"affected_builder_groups": [
"smart_contract_developers",
"developer_tooling_teams",
"audit_tooling_teams"
],
"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"
],
"affected_builder_groups": [
"validator_tooling_teams",
"staking_providers",
"operator_teams"
],
"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"
]
}
],
"official_sources": [
{
"id": "esp-glamsterdam-round",
"title": "Ethereum Foundation ESP Glamsterdam Grants Round",
"url": "https://esp.ethereum.foundation/applicants/wishlist/glamsterdam-round"
},
{
"id": "eip-7773",
"title": "Glamsterdam Meta EIP",
"url": "https://eips.ethereum.org/EIPS/eip-7773"
},
{
"id": "forkcast-glamsterdam",
"title": "Forkcast Glamsterdam tracker",
"url": "https://forkcast.org/upgrade/glamsterdam"
},
{
"id": "ethereum-roadmap-glamsterdam",
"title": "Ethereum.org Glamsterdam roadmap",
"url": "https://ethereum.org/roadmap/glamsterdam/"
},
{
"id": "ethereum-pm",
"title": "Ethereum All Core Devs calls",
"url": "https://github.com/ethereum/pm"
}
],
"non_goals": [
"Do not claim a candidate EIP is finalized unless official status confirms it.",
"Do not recommend production migration before implementation details are stable.",
"Do not treat grant or wishlist status as ranking evidence for protocol/dApp recommendations."
]
}Official sources first.
Composewith summarizes and structures official inputs. It does not replace EIP-7773, Forkcast, ethereum.org roadmap pages, or All Core Devs materials.
Formats: Markdown · JSON · Agent JSON · Changes JSON