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

Consensus-layer Call 103 #731

Closed
djrtwo opened this issue Feb 21, 2023 · 5 comments
Closed

Consensus-layer Call 103 #731

djrtwo opened this issue Feb 21, 2023 · 5 comments

Comments

@djrtwo
Copy link
Collaborator

djrtwo commented Feb 21, 2023

Consensus-layer Call 103 Agenda

prev: call 102

Meeting Date/Time: Thursday 2023/2/23 at 14:00 UTC
Meeting Duration: 1.5 hours

livestream

  1. Capella
    • testnet updates
    • relayer/builder testing progress
    • mev-boost update and SSE subscriptions
    • beacon-apis release plan
  2. Deneb
  3. Research, spec, etc
  4. Open Discussion/Closing Remark
@metachris
Copy link

metachris commented Feb 22, 2023

Happy to give an update about the mev-boost implementation & testing status re Capella.

Also would love to touch on SSE subscription to trigger block building (which includes withdrawals) - see also ethereum/beacon-APIs#244 (comment) (latest proposal by @michaelsproul)

@paulhauner
Copy link

Lighthouse has published a Capella-ready release: https://github.com/sigp/lighthouse/releases/tag/v3.5.0

This means that Capella is now in our stable branch and we're on a clean path towards Goerli and mainnet release. We have a handful of remaining tasks for Capella which we can easily accomplish in the current Goerli/mainnet time frames.

Notably, @michaelsproul has been maintaining an alpha version of his "tree states" upgrade to Lighthouse which represents the BeaconState as a data-sharing tree. That alpha will not be updated in time for Capella (but might be for Goerli/mainnet). Anyone using it shouldn't expect it to survive Capella. No one should be using it for production, anyway.

@rolfyone
Copy link

Also would love to touch on SSE subscription to trigger block building (which includes withdrawals) - see also ethereum/beacon-APIs#244 (comment) (latest proposal by @michaelsproul)

Re. #244, happy to progress it if there's a PR, probably not going to get to the beacon-api PR first at this point, though I have raised a teku issue for it. SSE subscriptions are possible from the teku perspective, if that's what's required. Endpoints would potentially be more reliable, you may miss things if a disconnect happens at a bad time.

Re. #301, potentially makes more sense to me than SSE, but happy to look at both.

While on the topic of beacon-apis, it's becoming a blocker that the 1.3 spec is not yet released. beacon-apis was waiting for 1.3 to be versioned so we could release the Capella api version, but now 1.3 seems to be leaking a lot of Deneb configuration, it's starting to look like we won't be making a clean version of the beacon-apis before merging all the Deneb endpoints into the spec.

If we could get guidance on the plan for the spec, whether 1.3 is going to be wrapped up for Capella, or if it's continuing on? Otherwise at the moment the beacon-apis is basically stalled.

@benjaminion
Copy link

Quick call notes.

@metachris
Copy link

Documentation of MEV-Boost changes for Capella: https://flashbots.notion.site/MEV-Boost-Capella-Upgrades-00cea01704794f6eb4f792c55b69c441

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

6 participants