Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FOCIL Breakout Room #2 #1238

Open
matthewkeil opened this issue Jan 6, 2025 · 8 comments
Open

FOCIL Breakout Room #2 #1238

matthewkeil opened this issue Jan 6, 2025 · 8 comments

Comments

@matthewkeil
Copy link
Member

matthewkeil commented Jan 6, 2025

Meeting Information

  • Tuesday January 14th, 2025 @ 2pm UTC
  • Duration 60 min
  • Please add to Ethereum Calendar
  • zoom link
  • Previous Call FOCIL Break-Out Room #1210

Agenda

  • Discuss client progress on implementation
  • Create list of clients that are
    • in-progress
    • substantially complete (kurtosis testing ready)
    • devnet ready
  • Talk about Kurtosis testing setup and considerations
  • Find out schedule for Testing Group to create specs
@jihoonsong
Copy link

Is it Wednesday (8th) or Friday (10th)?

@matthewkeil
Copy link
Member Author

matthewkeil commented Jan 6, 2025

Is it Wednesday (8th) or Friday (10th)?

Good catch. That was a typo. Its the 8th @jihoonsong

@abcoathup
Copy link

@matthewkeil
Copy link
Member Author

OK @poojaranjan. The schedule is updated. Please move the meeting to biweekly cadence starting next Tuesday, Jan 14th. Thanks again for helping hit the moving target!!!

@poojaranjan
Copy link
Contributor

Updated calendar and made it recurring at biweekly cadence.

@nflaig
Copy link
Member

nflaig commented Jan 14, 2025

Would be good to quickly discuss how we wanna handle the (really rare) edge case if a node as 2 IL duties in the same slot. Based on how engine_getInclusionListV1 is defined currently we can only request a single IL per parentHash and in general this also adds complexity to the beacon-api and few other places if we assume there could be multiple and would only be valuable if the EL can produce two (or more) different ILs.

Since there is no penalty for missing IL duties we can just ignore more than one duty for the same slot on the validator client side or we sign and submit the same IL multiple times but there would be no extra value if they contain the same transactions.

@matthewkeil
Copy link
Member Author

matthewkeil commented Jan 14, 2025

Intro Topics

  • Discussion about IL boost / IL market. Check discord/telegram for more info

Call Links

Implementation Notes from Terrence

  • Block Processing / Syncing a non-current slot block lacks an inclusion list
  • Block Processing / Node remembrance of unsatisfied inclusion list block root
  • Block Processing / Unsatisfied inclusion list block root filters the head root
  • Block Building / Integrate inclusion lists into block building
  • Syncing / Gossip Validation Pipeline
  • Syncing / Inclusion list cache
  • Validator API / Inclusion list duty retrieval
  • Validator API / Inclusion list retrieval for validator signing
  • Validator API / Validator Client Changes

Implementation Note from Jacob

  • plan to shift most focus to reth
  • plan to launch reth on kurtosis devnet with prysm
  • initial testing plan based on custom mempool logic to filter based on e.g. calldata
  • transaction spammer would be configured to broadcast “censorable” transactions
  • reuse forkChoiceUpdated or new engine API
    • updateBlockWithInclusionList
    • work required to add new engine API to reth and wire up block production

Implementation Notes from Jihoon

Implementation Notes from NC (Lodestar)

  • Making progress and should be feature complete in a week
  • Worked on engine_api specs

Implementation Notes from Nethermind

  • Working on branch feature/eip-7805

Implementation Notes from Teku

  • Working on branch focil

@poojaranjan
Copy link
Contributor

Recording: https://youtu.be/8s4XUc8bg8A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants