🏗️ Thread 5 — builder lifecycle on the request bus. Thread 4: bigger bytecode + Nick's factory. Finale: Amsterdam adds builder deposit/exit requests for ePBS. EIP-8282. 🧵
📦 Thread 4 — bigger contracts, same address everywhere. Thread 3: native ETH finally logs. Today: deploy larger bytecode + rely on Nick's CREATE2 factory. EIP-7954 + EIP-7997. 🧵
1
1
1
377
Status quo (EIP-7732 / Glamsterdam CL): Builders stake and exit through validator-style flows. Withdrawal credentials, voluntary exits, BLS hot keys. Works — but it blurs two different actors on one bus.
1
30
Amsterdam (EIP-8282): Two new EIP-7685 request types on the EL: • type 0x03 — BuilderDeposit • type 0x04 — BuilderExit Dedicated predeploys. Same end-of-block system-call pattern as EIP-7002. eips.ethereum.org/EIPS/eip-8…
1
16
The contracts (Glamsterdam-devnet v7 mined): Deposit: 0x0000bFF4…8282 Exit: 0x000064D6…8282 Builders register + top up via deposit calldata (184 bytes). Exit is authorized by execution_address — not the BLS bid key.
1
6
In @ethereumjs/vm: runBlock() on Hardfork.Amsterdam already calls accumulateRequests(). Builder requests append after deposit / withdrawal / consolidation. Read result.requests + result.requestsHash — same Prague+ pipeline, two new types.
1
5
Gotcha #1 — validate vs build: Validating: missing contracts → invalid block. Building (generate: true): missing/failing call → empty request. Local demos can seed STOP bytecode; devnets ship full contract code.

Sep 7, 2026 · 10:50 AM UTC

1
4
Gotcha #2 — EthereumJS is execution-layer: We accumulate EL requests + hash them. ePBS / builder consensus rules live on the CL side. Amsterdam preview — not production.
1
5
That wraps the Amsterdam deep-dive series 🎉 1 ⛽ two-dimensional gas 2 📋 BAL 3 📜 transfer logs 4 📦 code size + CREATE2 factory 5 🏗️ builder requests Full bundle: Hardfork.Amsterdam in @ethereumjs/[email protected] github.com/ethereumjs/ethere…
22