On Glamsterdam, what intrinsic gas does a plain 1 wei transfer to an existing account use?
What you can ask
You do not talk to the EVM in JSON. You talk to your agent, and the agent calls one hosted lab. These are the jobs the server runs now — on Amsterdam (Glamsterdam) by default, free.
1. Wallet and transaction gas
Example prompts
Call an existing account on Amsterdam with calldata of 100 zero bytes — what is intrinsic gas on Fusaka versus Amsterdam?
Deploy contract-creation initcode whose runtime code is exactly 24,577 bytes — does it succeed on Fusaka and on Glamsterdam?
Run a plain 1 wei transfer on Glamsterdam — decode the EIP-7708 Transfer log in the result.
Run a 1 wei transfer to an empty account on Glamsterdam — what gas would a wallet need?
Compare (only when you ask): run the same transfer on Fusaka then Amsterdam and compare paid gas.
2. Bytecode, opcodes, and precompiles
Example prompts
Run PUSH1 1 PUSH1 2 ADD on Amsterdam and show me the gas and the final stack.
On Pectra then Fusaka, run the same 32-byte ModExp CALL (base, exponent, and modulus each 32 bytes of 0x02) — how much did gas increase?
On Fusaka, CALL precompile 0x100 with a standard valid P-256 test vector (message hash, r, s, pubX, pubY) — does it return 0x01?
Give me a minimal DUPN example for depth 17, encode it as bytecode, and run it on Glamsterdam with trace.
You supply bytecode (and optional demo accounts) — the server does not ship demo contracts.
3. Storage gas and program gas
Example prompts
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.
On Glamsterdam, run bytecode that cold SSTOREs 9 into storage slot 1 when slot 1 already holds 7 — prefund slot 1 with 7 on the contract first. How much gas does the call use?
Bytecode path vs transaction path: program gas often belongs in a bytecode run; paid tx totals belong in a transaction run. Your agent can choose; both are supported for 8038.
4. Small lab blocks
Example prompts
Run a lab block on Amsterdam with two plain 1 wei transfers — show each receipt.
Run a lab block on Amsterdam with header slot 42 — one transaction calls a contract whose runtime runs SLOTNUM and returns the slot number. What value is returned?
Clear a nonzero storage slot on Glamsterdam — what do I pay, and what does the block count?
Up to 8 transactions per block. Not historical chain replay.
5. Artifacts without executing chain history
Example prompts
Generate a BAL for a lab block on Amsterdam with one plain 1 wei ETH transfer — what does the access list contain?
Generate a BAL on Amsterdam for one plain transfer, then inspect that BAL JSON — is it well formed and does the hash match?
What we do not do
- Compile Solidity or fetch mainnet state
- Run long historical multi-block replays
- Replace your archive node or RPC provider
Details: Limits. Fork catalogue: Amsterdam, EIP index.
For integrators — tool names
The agent maps your question to a small set of MCP tools. You rarely need these names; they are listed under Reference → Tool schemas when you debug integrations.
| Job (above) | Typical MCP tool |
|---|---|
| Discover what is runnable | describe_capabilities |
| Bytecode / opcodes / traces | run_bytecode |
| Paid tx / receipts / wallet gas | run_transaction |
| Multi-tx lab block | run_block |
| BAL generate / inspect | generate_artifact, inspect_artifact |
Capabilities Changelog
Capabilities Changelog
- v0.212026-10-06These jobs are live on the hosted MCP, not waiting for a launch window.
- v0.202026-10-06Launch polish — prompt cards per job; wording unchanged.
- v0.192026-10-01Reframed as five user jobs; tool table moved to integrator footnote.
- v0.182026-09-22Probe queryShapes dictionary; EIP/fork rows list tools (MCP names), not shapes.
- v0.172026-09-22Renamed generate → generate_artifact and inspect → inspect_artifact.
- v0.162026-09-17Fusaka runs are first-class for current-mainnet features, not only preview compares.
- v0.152026-09-16generate + inspect — BAL from lab block; inspect without chain state.
- v0.142026-09-16Generic hardfork runs (Glamsterdam default) are first-class — EIP modules remain the per-change catalogue.
- v0.122026-09-14BYOS clarified: isolated from chain, demand-built prestate in-call; not an empty-world rule.
- v0.112026-09-10Fourth tool run_block — lab header snapshot and per-tx receipts.
- v0.102026-09-08Third tool run_transaction; renamed run_evm_bytecode → run_bytecode.
- v0.92026-09-02Status is implemented vs public launch — no stdio / self-host product path.
- v0.82026-08-27Renamed simulate_evm_bytecode → run_evm_bytecode.
- v0.62026-08-27Probe lists opcode/encoding facts; no demo scenarios on the catalog.
- v0.42026-07-22Probe + simulate MCP tools live on stdio gateway v0.1.
- v0.32026-07-20Split from overview — end-user capability summary under use/.