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

Engine API: more clarity around terminalBlockNumber field #179

Merged
merged 1 commit into from
Mar 2, 2022

Conversation

mkalinin
Copy link
Collaborator

  • Removes confusing "terminalBlockNumber MUST be set to 0"
  • States that CL clients may use 0 value as input for terminalBlockNumber as there is no TERMINAL_BLOCK_NUMBER setting on CL side

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.

2 participants