chore(binaries): Small tweaks for latest reth and lighthouse. #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
--suggested-fee-recipient
when runningbn
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:
Edit: it must be some other change to LH, seems to be coming up on the wrong fork:
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:
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 inunstable
. I was able to confirm that using a self-built version of lighthouseunstable
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.