Skip to content

Add QoS for transition config endpoint#189

Merged
djrtwo merged 2 commits intoethereum:mainfrom
paulhauner:patch-2
Mar 3, 2022
Merged

Add QoS for transition config endpoint#189
djrtwo merged 2 commits intoethereum:mainfrom
paulhauner:patch-2

Conversation

@paulhauner
Copy link
Copy Markdown
Contributor

This follows from a Discord conversation about using the engine_exchangeTransitionConfigurationV1 endpoint as a "ping" to allow an EL to be aware when it's CL is offline. (cc @djrtwo @mkalinin)

I imagine this to be particularly helpful in the space between:

  1. Beacon chain Bellatrix fork
  2. Terminal PoW block

During this period all ELs must be paired with a CL, but there's presently no way for them to know that the CL is connected and live.

Copy link
Copy Markdown
Contributor

@terencechain terencechain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏼

Should we explicitly specify that polling is only required between the Bellatrix fork and the terminal pow block?

Copy link
Copy Markdown
Contributor

@mkalinin mkalinin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In general this looks good to me, and it should also be a good way for users to know that their EL part of the node is ready for transition.

cc'ing @ryanschneider to get input from infra providers' perspective

@ryanschneider
Copy link
Copy Markdown
Contributor

ryanschneider commented Mar 1, 2022 via email

@djrtwo
Copy link
Copy Markdown
Contributor

djrtwo commented Mar 2, 2022

looks good to me

I think the plan @terencechain is to remove this functionality in a subsequent upgrade if it is not of clear value anymore.

I'm okay with putting a restriction on it being only until the transition occurs but am okay either way

@terencechain
Copy link
Copy Markdown
Contributor

looks good to me

I think the plan @terencechain is to remove this functionality in a subsequent upgrade if it is not of clear value anymore.

I'm okay with putting a restriction on it being only until the transition occurs but am okay either way

I'm okay either way. Prysm doesn't have a restriction. We plan to remove the functionality at some release post-transition, so that means we'll have to coordinate on the timing with all the execution layer client teams

@djrtwo djrtwo merged commit 596ad14 into ethereum:main Mar 3, 2022
bors bot pushed a commit to sigp/lighthouse that referenced this pull request Mar 8, 2022
## Issue Addressed

There has been an [`engine_exchangetransitionconfigurationv1`](https://github.com/ethereum/execution-apis/blob/main/src/engine/specification.md#engine_exchangetransitionconfigurationv1) method added to the execution API specs.

The `engine_exchangetransitionconfigurationv1` will be polled every 60s as per this PR: ethereum/execution-apis#189. If that PR is merged as-is, then we will be matching the spec. If that PR *is not* merged, we are still fully compatible with the spec, but just doing more than we are required.

## Additional Info

- [x] ~~Blocked on #2837~~
- [x] Add method to EE integration tests
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

Successfully merging this pull request may close these issues.

5 participants