On Glamsterdam, what intrinsic gas does a plain 1 wei transfer to an existing account use?
Why this server
Prefer the browser?
feelyourprotocol.org is the interactive textbook — no MCP setup. This site is for people who want their agent to run exact protocol experiments.
The server is open
6 October 2026 — https://mcp.feelyourprotocol.org/mcp is live, the same day Glamsterdam reaches Sepolia. Connect is the shortest path in.
| Cost now | Free — full Amsterdam (Glamsterdam) hardfork, no wallet, no API key |
| What you bring | Bytecode, transactions, optional demo accounts per call (no mainnet RPC) |
| Later | New EIPs ahead of Amsterdam move to a paid tier — Pricing · what opened |
The gap
Large language models sound confident about gas, opcodes, and fork diffs. They are not executing the EVM. When Amsterdam lands, a wrong intrinsic gas number or a missed first-touch state cost is not a typo — it is a product bug waiting in your wallet logic, your deploy script, or your audit report.
Feel Your Protocol closes that gap with a hosted lab: the same EthereumJS execution stack that powers our public explorations, exposed to your agent through MCP. You ask in plain language; the server runs under the fork you need and returns deterministic results — gas, receipts, traces, provenance — not a guess.
How a run works: your question → your agent → one isolated lab run → fork, gas, and traces you can cite.
Why this implementation
Try these first on Amsterdam
After Connect, paste a prompt — you do not need EIP numbers in conversation.
Gas and receipts
Call an existing account on Amsterdam with calldata of 100 zero bytes — what is intrinsic gas on Fusaka versus Amsterdam?
Run a 1 wei transfer to an empty account on Glamsterdam — what gas would a wallet need?
Run a plain 1 wei transfer on Glamsterdam — decode the EIP-7708 Transfer log in the result.
Storage and blocks
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 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?
More on the Amsterdam bundle: deploy limits, block access lists, stack opcodes, SLOTNUM. Already on mainnet here: ModExp, P-256 on Fusaka.
Where to go next
Want to click through a change first? The website explorations are the visual twin of many Amsterdam EIPs — same questions, human UI.
Introduction Changelog
Introduction Changelog
- v0.182026-10-06The hosted MCP is live — the public-launch section is no longer a countdown.
- v0.172026-10-06Launch polish — icon cards, prompt cards with EIP links; wording unchanged.
- v0.162026-10-01Launch table and Amsterdam prompt table moved from home — home is hero + features only.
- v0.152026-10-01User-facing rewrite — why deterministic Amsterdam lab; removed internals-first framing.
- v0.142026-10-01Launch is a free Glamsterdam MCP. Paid tier for newer EIPs comes later.
- v0.132026-09-22Six launch tools — generate_artifact and inspect_artifact with the four run/probe verbs.
- v0.112026-09-08Three launch tools — describe_capabilities, run_bytecode, run_transaction.
- v0.102026-09-02User docs describe the hosted product only — no local stdio / self-host early access.
- v0.92026-08-31Lead with not publicly launched — website explorations for most visitors; local stdio as early access only.
- v0.82026-08-27Fusaka mainnet baseline fork for run-twice comparisons against Glamsterdam preview.
- v0.72026-08-27Two live MCP tools — compare removed; use simulate twice.
- v0.62026-08-27Catalog describes capabilities (opcodes/encoding), not website demo programs.
- v0.42026-07-22Local stdio gateway v0.1 live — two MCP tools.
- v0.32026-07-20Split from overview — end-user introduction under use/.
- v0.12026-07-15Initial overview content (pre-split).