EL Specs Calls, Tue 21st July & Thu 23rd July, 2026

[github-actions]

Weekly Agenda

Rapid-fire Status Updates

Every team member gives a 60 second TLDR on their current work, highlighting any blockers, chosen by the Wheel.

Anything that can't be resolved within 60s should be scheduled for discussion later in the call.

Tuesday Agenda Points

• Glamsterdam
• Hegota
  • Branching strategy @gurukamath
• Benchmarking
  • refactor(test-benchmark): organize stateful folder, add post-state validation, opcode count record ethereum/execution-specs#3201
  • feat(test-benchmark): add deployment contract script, no-rewind flag ethereum/execution-specs#3194
  • feat(test-benchmark): on-chain account verification ethereum/execution-specs#3197

Thursday Agenda Points

• Glamsterdam
  • Test Release Tracker: glamsterdam-devnet@v8.0.0 ethereum/execution-specs#3167
  • Test Release Tracker: tests@v21.0.0 (Glamsterdam Testnet) ethereum/execution-specs#3217
• Hegota
  • FOCIL
  • Frames
  • Folder branching strategy @gurukamath
• Benchmarking
• State
• zkEvm
• Protocol Strategy Doc Priorities
  • Subtraction? Think about what EL specs can subtract - discuss more tmo!
• SSZ model base types PR
  • feat(test-types): Introduce SSZ model into base types ethereum/execution-specs#3196
• CFI-ing EIP-8025 (Optional Proofs) in Hegota, for improving ZkEvm work stream. Greatly simplifying our releases.
• JSON-RPC testing? Should we pick it up?

[RazorClient]

• ssz related discussions(feat(test-types): Introduce SSZ model into base types ethereum/execution-specs#3196)

[gurukamath]

I want to discuss the folder/branching strategy for Hegota.

My take:

I think we shouldn't yet create the bogota folder on any of these branches. Instead continue to build focil / frames on top of amsterdam. The upstream branch will be eips/amsterdam/eip-7805 and eips/amsterdam/eip-8141 respectively. Once amsterdam is stable enough and we decide to make forks/bogota the default (with the bogota spec folder), is when we should move the EIP implementations over. This will be as simple as porting over the diffs between forks/amsterdam and eips/amsterdam/eip-xx in a single PR.

If we already create the bogota folder while the amsterdam one is still changing reasonably frequently, rebases become way more involved.

Would love to hear everyone's thoughts

[spencer-tb]

I think we shouldn't yet create the bogota folder on any of these branches. Instead continue to build focil / frames on top of amsterdam. The upstream branch will be eips/amsterdam/eip-7805 and eips/amsterdam/eip-8141 respectively. Once amsterdam is stable enough and we decide to make forks/bogota the default (with the bogota spec folder), is when we should move the EIP implementations over. This will be as simple as porting over the diffs between forks/amsterdam and eips/amsterdam/eip-xx in a single PR.

If we already create the bogota folder while the amsterdam one is still changing reasonably frequently, rebases become way more involved.

Fully agree here!

[github-actions]

Closed automatically after Thursday's EL Specs call.