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

chore(binaries): Small tweaks for latest reth and lighthouse. #20

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

ryanschneider
Copy link
Collaborator

@ryanschneider ryanschneider commented Oct 1, 2024

  • Lighthouse dropped the "-portable" suffix as of 5.3.0, now all the image are "portable"
  • They also now require the --suggested-fee-recipient when running bn as well, I copied the same recipient as the validator.

However, keeping this a draft until I figure out why the bn isn't synced in time:

Stopping reth
Stopping beacon_node
Stopping validator
Error: failed to create relay: beacon client failed to start

Edit: it must be some other change to LH, seems to be coming up on the wrong fork:

Oct 01 22:13:07.004 INFO Ready for Bellatrix                     current_difficulty: 0, terminal_total_difficulty: 0, service: slot_notifier

Edit 2: After diffing the two logs, these are all the log lines that are included in the 5.3.0 log that aren't in 5.2.1:

>  INFO Prepared beacon proposer                parent_root: 0x68a8afe0f967f0087769172706a6f89524b565fc7726f290ccf99722a420b5a2, validator: 78, prepare_slot: 1, service: beacon
>  INFO Found terminal block hash               block_hash: 0xb62f7a677c9034d497d5547514d886145a105b1b358300bf02f70ab299ca6a29, terminal_total_difficulty: 0, terminal_block_hash_override: 0x0000000000000000000000000000000000000000000000000000000000000000, service: exec
>  INFO Prepared POS transition block proposer  slot: 1, service: beacon
>  INFO Execution engine online                 service: exec
>  INFO Issuing forkchoiceUpdated               forkchoice_state: ForkchoiceState { head_block_hash: 0xb62f7a677c9034d497d5547514d886145a105b1b358300bf02f70ab299ca6a29, safe_block_hash: 0x0000000000000000000000000000000000000000000000000000000000000000, finalized_block_hash: 0x0000000000000000000000000000000000000000000000000000000000000000 }, service: exec
>  WARN Low peer count                          peer_count: 0, service: slot_notifier
>  INFO Searching for peers                     current_slot: 0, head_slot: 0, finalized_epoch: 0, finalized_root: 0x68a8…b5a2, peers: 0, service: slot_notifier
>  WARN Syncing deposit contract block cache    est_blocks_remaining: initializing deposits, service: slot_notifier
>  INFO Ready for Bellatrix                     current_difficulty: 0, terminal_total_difficulty: 0, service: slot_notifier

Edit 3: Ok, I got confirmation from the lighthouse team that 5.3.0 has some regressions for single node testnets like ours that our fixed in unstable. I was able to confirm that using a self-built version of lighthouse unstable alongside --use-bin-path works with the changes in this PR, so I think I'll just keep it a draft until there's another LH release.

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.

1 participant