EL Specs Calls, Tue 6th October & Thu 8th October, 2026 #146

Activity

1. github-actions

   added

   meeting

   on Oct 1, 2026
2. jochem-brouwer commented on Oct 5, 2026

   

   jochem-brouwer

   on Oct 5, 2026

   Last edited by jochem-brouwer

   More actions

   I want to discuss EIP-8253 because this spec (the EIP spec) is more tricky than we initially thought.
3. jochem-brouwer commented on Oct 5, 2026

   

   jochem-brouwer

   on Oct 5, 2026

   Last edited by jochem-brouwer

   More actions

   I want to take about 2-3 minutes for the wheel, to talk about my workflow (improvements) and above. (on Oct 6)
4. LouisTsai-Csie commented on Oct 6, 2026

   

   LouisTsai-Csie

   on Oct 6, 2026

   Contributor

   More actions

   Sharing the status of CFI EIPs:

   Spec & test ready:

   • EIP-7805 (FOCIL): Fork-choice enforced inclusion lists
   • EIP-8141 (Frame): Frame transaction base; required by 8250/8272

   PR ready:

   • EIP-7668: Remove bloom filters (feat(spec-specs,tests): implement EIP-7668 empty logs bloom in Bogota ethereum/execution-specs#3719)
   • EIP-8163: Reserve EXTENSION (0xae) opcode (feat(tests): Add EIP-8163 EXTENSION opcode test ethereum/execution-specs#3454)
   • EIP-8250: Keyed nonces for frame txs (depends on 8141) (feat(specs,tests): implement EIP-8250 keyed nonces for frame transactions spencer-tb/execution-specs#70)
   • EIP-8253: Bump nonce for zero-nonce storage accounts (feat(spec-specs, tests): implement EIP-8253, bump nonce of zero-nonce storage accounts ethereum/execution-specs#3535)

   PR needs follow-up:

   • EIP-7979: Call and return opcodes for EVM (feat(forks,tests): implement EIP-7979 Call and Return Opcodes ethereum/execution-specs#3575)
   • EIP-8131: Unified transaction content floor (feat(spec-specs,tests): add EIP-8131 unified transaction content floor ethereum/execution-specs#3350, by Toni)
   • EIP-8279: Block access list byte floor (feat(spec-specs): add EIP-8279 block access list byte floor ethereum/execution-specs#3351, by Toni)

   PR in progress:

   • EIP-7906: Transaction assertions via state diff opcode
   • EIP-8272: Recent roots for frame txs (depends on 8141) (feat(spec-specs, tests): implement EIP-8272 recent roots for frame transactions spencer-tb/execution-specs#71)

   No ownership:

   • EIP-3298: Remove storage-clear refund and refund cap
5. gurukamath commented on Oct 6, 2026

   

   gurukamath

   on Oct 6, 2026

   Collaborator

   More actions

   I think we should move all the dev work to forks/bogota asap. Need to rebase on `forks/amsterdam. Would like to discuss the next steps on this topic

   👍React with 👍1Reacted by 蔡佳誠 Louis Tsai
6. spencer-tb commented on Oct 6, 2026

   

   spencer-tb

   on Oct 6, 2026

   Collaborator

   More actions

   Tuesday Notes

   • Change default branch to forks/bogota for now (decide on using main/ on Thursday). Freezing forks/amsterdam. Change all PRs base branch to forks/bogota.
   • Ask about quick slots in tmo's Specs call, align in call on the hegota-devnet-0 plan. Should it be tested on an individual devnet first then add it to the hegota devnets? Devnet inclusion can only occur in ACDT?
   • Need to specify what all the nonce edge cases for 8253!

   ❤️React with ❤️1Reacted by danceratopz
7. danceratopz commented on Oct 8, 2026

   

   danceratopz

   on Oct 8, 2026

   Collaborator

   More actions

   Hey Akash reached out about speaking at the EIP Hub during Devcon. I quickly wanted to let y'all about this (if you didn't get a ping from him)!

   The four days will be organized around different themes:

   Day 1: Understanding EIPs
   Day 2: Protocol & Core Ethereum
   Day 3: Applications & ERC Standards
   Day 4: Enterprise & Adoption

   We’d love to explore having you give a talk at the Hub. We’re particularly interested in an EIP-related topic or something around your work that you think would be relevant and interesting for the Ethereum community.
8. danceratopz commented on Oct 8, 2026

   

   danceratopz

   on Oct 8, 2026

   Collaborator

   More actions

   Hey I know we need to set aside for the retro/outlook today, but could we do a quick temp check on the team to see how aligned people are with Lukasj's "fork acceleration" post [from ACDC here](create a new worktree wt switch -c disambiguate-7906). I think it's important we know how each individual feel about this before anyone speaks for the team.

   I can share my thoughts here:

   I'm pro, but not as optimistic as 4 forks/year. I would be happy with 2, or even with 1.5. But tbh, I don't think we should pin a number now, I'm more along the lines of yes! Let's add all this automated tooling and get Hegota shipped asap (under the condition that mental health and Ethereum's security come first). Coordination will remain the difficultly. From chatting with @spencer-tb: If we're fast, we need to be lining up our ducks: I.e, scoping I* early. This will split attention and be difficult to sustain, but it doesn't mean we shouldn't try it!

   👍React with 👍1Reacted by Jochem Brouwer
9. jochem-brouwer commented on Oct 8, 2026

   

   jochem-brouwer

   on Oct 8, 2026

   Last edited by jochem-brouwer

   More actions

   Cool I also wanted to bring up this topic, lets share our ideas on it
10. github-actions commented on Oct 8, 2026

    

    github-actionsBot

    on Oct 8, 2026 – with GitHub Actions

    Author

    More actions

    Closed automatically after Thursday's EL Specs call.
11. github-actions

    closed this as completedon Oct 8, 2026