FOCIL Breakout #3

[matthewkeil]

Schedule

• Tuesday January 28th, 2025 @ 2pm UTC
• Duration 60 min
• Recurring meeting already on Ethereum Calendar
• zoom link
• Previous Call FOCIL Breakout Room #2 #1238

Topics

• Client Status Updates and Readiness for Interop testing
  ⁃ Prysm <> Geth Interop: https://hackmd.io/@ttsao/focil-interop-notes
  - Use configs EIP7805_FORK_NUMBER moving forward
  ⁃ FOCIL high level test cases: https://hackmd.io/@ttsao/focil-interop-test-cases
  ⁃ Support for EIP-7805 in ethpandaops Kurtosis package
  • Call for helping build a mempool visualizer that could be useful to debut FOCIL: https://github.com/ethpandaops/tooling-wishlist/blob/master/open-ideas/txpool-viz.md

[poojaranjan]

Recording: https://www.youtube.com/live/azvPMD2us0Y

Links shared in meeting

• https://hackmd.io/@ttsao/focil-interop-test-cases
• https://hackmd.io/@jihoonsong/ByFgyGRDJg
• Add EIP-7805 (FOCIL) endpoints beacon-APIs#490
• https://github.com/ethpandaops/tooling-wishlist/blob/master/open-ideas/txpool-viz.md

[abcoathup]

Eth Magicians: https://ethereum-magicians.org/t/focil-breakout-3-january-28-2025/22704

[poojaranjan]

Summary

The meeting had no formal presentation but was focused on updates and discussions related to progress on the implementation and testing of features for clients. Key highlights include:

• Terence suggested the inclusion of FOCIL as its own hard fork rather than merging it into Fulu. This approach provides better flexibility for tooling and testing.
• Initial testing scenarios focused on transaction inclusion and basic functionalities. However, censorship testing and equivocation scenarios still need to be explored.
• Issues around handling multiple EL scenarios and ensuring sufficient testing coverage were noted.
• Various methods to simulate censorship behavior were discussed, including modifying mempools or creating controlled testing environments.
• Jihoon highlighted testing challenges with client variations, including censoring and equivocating behaviors, and suggested using tools like Kurtosis to create reproducible scenarios.
• Additional insights into interop testing and transaction handling were shared.

Updates from Other Teams

• Lodestar: Implementation progress is at 95%, with plans for further internal reviews. Initial local P2P testing is working well.
• Prysm: Work continues on testing and implementing inclusion-related features, with a focus on Beacon API improvements.
• Lighthouse: LH is taking over efforts to push the implementation forward, with limited bandwidth allocated to the task.
• Erigon: P2P layers have been implemented, and work is ongoing on the RPC side, aiming for a minimal working implementation within two weeks.

Tooling and Visualization

• Efforts to standardize metrics naming conventions and develop a mempool visualizer were discussed. These tools will help analyze and improve testing scenarios.
• Suggestions for additional API improvements and streaming endpoints for inclusion lists were made.

Next Steps

• Client teams aim to complete working implementations for FOCIL testing before the next meeting.
• Continued focus on interop testing across clients and further refining testing scenarios for real-world use cases.
• Discussions on privacy for IL committee members and potential methods to evaluate censorship resistance will be presented in future meetings.
• Participants acknowledged significant progress across multiple teams and looked forward to gathering results and metrics in upcoming sessions.
• The next meeting is scheduled in two weeks, with more updates expected on FOCIL implementations and interop testing.

[jochem-brouwer]

FOCIL meeting 4 minutes: #1291