⛽ Thread 1 — the 21,000-gas myth. A plain ETH transfer was always 21,000 gas. On Amsterdam, that number still exists — and it will still brick wallets. Here's why. 🧵
Amsterdam just got a public playground. 🐻‍❄️ Platåberget — Glamsterdam's first public testnet — is live. EthereumJS v10.1.3 is a close-to-ready 14-EIP Amsterdam preview. JavaScript is just the easy on-ramp. The fork is the story. 🧵
1
1
1
2
509
Status quo (today, mainnet): Send 1 wei to an address that has never been used. gasLimit: 21000 It works. Wallets, SDKs, and estimators baked that in for a decade.
1
112
Amsterdam splits gas into two dimensions: • regular — execution (the old meter) • state — creating new accounts, storage, code You pay the *sum*. The block is full when *either* dimension hits the limit. eips.ethereum.org/EIPS/eip-8…
1
30
Same 1-wei transfer. Recipient never existed. regular: 21,000 state: 183,600 you must set gasLimit ≥ 204,600 183,600 = 120 bytes × 1,530 Use 21,000 → out of gas. Tx included, ETH doesn't move.
1
71
Wait — 21,000 is still there? Yes. EIP-2780 just unpacks it: 12,000 sender / signature 3,000 touch the recipient 6,000 write value That's regular gas only. Creating the account is *runtime state* gas now. eips.ethereum.org/EIPS/eip-2…
1
8
You should print: regular: 21000 state: 183600 recommended gasLimit: 204600 That's the whole EIP in one transfer.
1
7
The gotcha: If a wallet still sends gasLimit 21000 to a never-used address, the tx is included and reverts. Existing recipients: still ~21,000 regular, 0 extra state. Estimators must look at state, not a constant.
1
18
One extra wrinkle (EIP-7778): totalGasSpent = what the sender pays blockGasSpent = what fills the block (refunds do *not* shrink the block) On this transfer they match. On SSTORE-heavy txs they won't. Experimental — not production. Next: Block-Level Access Lists. [END OF THREAD ]
17