On Glamsterdam, what intrinsic gas does a plain 1 wei transfer to an existing account use?
🐻❄️ Amsterdam now (Glamsterdam)
Naming
Glamsterdam is the catalog id; amsterdam is the Ethereum execution-layer alias. Both mean the same fork here. Default when you omit fork.
At launch this is the free product surface: the full upcoming Amsterdam hardfork on the hosted MCP, plus everything bundled with it. You do not need to name an EIP — ask about behavior and let your agent pick the run shape.
Prefer the visual twin? Many of these changes have browser explorations on the main site.
Start with these questions
These are the highest-signal checks for integrators and auditors — exact gas and receipts, not LLM guesses.
Prompts to copy
Run a 1 wei transfer to an empty account on Glamsterdam — what gas would a wallet need?
Cold SSTORE 9 into storage slot 1 when slot 1 already holds 7 — prefund slot 1 with 7 on the contract, run on Fusaka and on Glamsterdam, and compare call gas.
Run a plain 1 wei transfer on Glamsterdam — decode the EIP-7708 Transfer log in the result.
Run a lab block on Amsterdam with a transaction that clears storage and earns a refund — does the block header total still count the full gas for each transaction?
Also on Amsterdam
Compare to mainnet today
When you care about before vs after, ask for the same experiment on Fusaka (today’s mainnet EL) and Amsterdam, then diff gas or success. One Amsterdam-only run is always valid.
Fusaka (mainnet) · Historical forks
How your agent runs it
Per-EIP pages above or the full EIP catalogue.
Bundled rule changes that do not have their own exploration still apply on Amsterdam. SELFDESTRUCT no longer burns ETH. Access-list bytes pay the same 64-gas floor as calldata. Your agent uses generic Amsterdam runs without naming those ids.
EIP-7997 is unshown. The chain must already contain the CREATE2 factory, and this lab does not install it. EIP-8282 is unshown. A lab block does not return builder deposit or exit requests, and whether a builder is accepted is consensus.
Consensus-layer and networking EIPs scheduled beside Amsterdam are not executed in this lab — the EIP catalogue notes which ids to omit.
Related
| Pricing | Free now; paid tier for EIPs ahead of Amsterdam later |
| Limits | Determinism, BYOS, ceilings |
| EIP-7773 | Glamsterdam meta |
Preview Forks (Glamsterdam) Changelog
Preview Forks (Glamsterdam) Changelog
- v1.62026-10-06Amsterdam on the hosted MCP is open, the same day as Glamsterdam Sepolia.
- v1.52026-10-06Launch polish — prompt cards and icon cards; wording unchanged.
- v1.42026-10-04EIP-7778 joins the advertised twins — refunds stay on the bill, not the block.
- v1.32026-10-04EIP-8282 is coverage unshown. Lab blocks do not return builder requests.
- v1.22026-10-04EIP-7997 is coverage unshown. The fork does not install the CREATE2 factory.
- v1.12026-10-01EIP-7976 calldata floor joins the advertised twins. EIP-7981 stays bundled.
- v1.02026-10-01User-first Amsterdam page — gas/receipt questions first; probe jargon moved to catalogue.
- v0.92026-09-29EIP-2780 intrinsic gas joins the advertised Glamsterdam twins.
- v0.82026-09-29Networking (7975, 8070, 8136, 8159, 8189) and informational (7904, 8261) EIPs are out of this lab.
- v0.72026-09-29Consensus EIPs 7688, 7732, 8045, and 8061 are coverage consensus — out of this lab.
- v0.62026-09-29EIP-8246 is coverage supported: bundled on Glamsterdam, no twin page.
- v0.52026-09-17EIP-7954 contract creation added to advertised runnable twins.
- v0.42026-09-17Twin pages linked from this fork doc (sidebar no longer lists EIPs).
- v0.32026-09-17Canonical catalog id is glamsterdam; amsterdam is the EL alias.
- v0.22026-09-16Framed as preview/upcoming section; room for post-Glamsterdam forks (e.g. Hegota).
- v0.12026-09-16Named fork capability — generic Glamsterdam runs.