-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Unable to sync Lisk Mainnet with the latest version (v1.1.1) #12470
Comments
there's a 5min diff between those logs could you provide matching logs when this error first appears? |
perhaps you can also try to increase the --builder.deadline |
I've executed Reth with New logs:
Reth:
|
could you provide trace level for |
Hi @mattsse, Could you please guide me on how do we build the op-reth client with We currently run the following command to build the client: |
you can configure this via |
@mattsse
|
thanks for flagging, |
Describe the bug
After updating the Reth client to the latest version (v1.1.1), the op-node v1.9.5 (as well as the previous version v1.9.4) generates the following logs:
Failed to get payload
andCannot seal block, payload ID is unknown.
Additionally, Reth stalls atNew payload job created id=0x039f75b9b517fb98 parent=0xc1ed6db609d23ec3050258d409f4fcae537f7fd0ec6d29d54f0191f7ec8bc79f
.PR for updating the Reth client for the Lisk network:
LiskHQ/lisk-node#45
Steps to reproduce
CLIENT=reth docker compose up --build --detach
Node logs
Platform(s)
Mac (Apple Silicon)
What version/commit are you on?
v1.1.1
What database version are you on?
N/A
Which chain / network are you on?
Lisk Mainnet
What type of node are you running?
Full via --full flag
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: