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

Don't consider stubbed terminal block hash terminal (fixes #4094) #4096

Merged
merged 1 commit into from
Sep 8, 2022

Conversation

arnetheduck
Copy link
Member

No description provided.

@arnetheduck arnetheduck merged commit ee1465e into unstable Sep 8, 2022
@arnetheduck arnetheduck deleted the stubbed-hash branch September 8, 2022 08:57
Comment on lines +593 to +596
info "Exchanged engine configuration",
ttd = executionCfg.terminalTotalDifficulty,
terminalBlockHash = executionCfg.terminalBlockHash,
terminalBlockNumber = executionCfg.terminalBlockNumber.uint64
Copy link
Contributor

Choose a reason for hiding this comment

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

This one is quite useful, also to verify that the EL connection is indeed working fine.

@etan-status etan-status linked an issue Sep 8, 2022 that may be closed by this pull request
@etan-status
Copy link
Contributor

Validated fix using launch_local_testnet.

@etan-status
Copy link
Contributor

rm -rf local_testnet_data && scripts/launch_local_testnet.sh \
  --kill-old-processes --preset minimal --disable-htop --disable-vc --run-geth --dl-geth -- \
  --log-format=auto --max-peers=160

I ran this before this patch, and after this patch.

Without patch, network got stuck around block 17 and same message got logged about engine API usage. With patch, network proceeded as usual.

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.

Missed proposal getExecutionPayload: newExecutionPayload invalid
2 participants