You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2024-10-29T17:08:53.642084Z INFO reth_payload_builder::service: New payload job created id=0x05abef14ca0a55fe parent=0x23c69610fb964fd0814fa84ccb37f4cacf5c8f8dd7b8cb572729b7a12145a605
2024-10-29T17:08:53.642182Z DEBUG payload_builder: building new payload id=0x05abef14ca0a55fe parent_hash=0x23c69610fb964fd0814fa84ccb37f4cacf5c8f8dd7b8cb572729b7a12145a605 parent_number=21682329
2024-10-29T17:08:53.642547Z DEBUG payload_builder: no best payload yet to resolve, building empty payload id=0x05abef14ca0a55fe
2024-10-29T17:08:53.642611Z DEBUG payload_builder: awaiting in progress payload build job id=0x05abef14ca0a55fe
2024-10-29T17:09:13.657726Z DEBUG payload_builder: building new payload id=0x05abef14ca0a55fe parent_hash=0x23c69610fb964fd0814fa84ccb37f4cacf5c8f8dd7b8cb572729b7a12145a605 parent_number=21682329
2024-10-29T17:09:13.658092Z DEBUG payload_builder: no best payload yet to resolve, building empty payload id=0x05abef14ca0a55fe
2024-10-29T17:09:13.658125Z DEBUG payload_builder: awaiting in progress payload build job id=0x05abef14ca0a55fe
The client will loop over this error. If you unwind some blocks, it will loop/error over that point as well.
Describe the bug
2024-10-29T17:08:53.642084Z INFO reth_payload_builder::service: New payload job created id=0x05abef14ca0a55fe parent=0x23c69610fb964fd0814fa84ccb37f4cacf5c8f8dd7b8cb572729b7a12145a605
2024-10-29T17:08:53.642182Z DEBUG payload_builder: building new payload id=0x05abef14ca0a55fe parent_hash=0x23c69610fb964fd0814fa84ccb37f4cacf5c8f8dd7b8cb572729b7a12145a605 parent_number=21682329
2024-10-29T17:08:53.642547Z DEBUG payload_builder: no best payload yet to resolve, building empty payload id=0x05abef14ca0a55fe
2024-10-29T17:08:53.642611Z DEBUG payload_builder: awaiting in progress payload build job id=0x05abef14ca0a55fe
2024-10-29T17:09:13.657726Z DEBUG payload_builder: building new payload id=0x05abef14ca0a55fe parent_hash=0x23c69610fb964fd0814fa84ccb37f4cacf5c8f8dd7b8cb572729b7a12145a605 parent_number=21682329
2024-10-29T17:09:13.658092Z DEBUG payload_builder: no best payload yet to resolve, building empty payload id=0x05abef14ca0a55fe
2024-10-29T17:09:13.658125Z DEBUG payload_builder: awaiting in progress payload build job id=0x05abef14ca0a55fe
The client will loop over this error. If you unwind some blocks, it will loop/error over that point as well.
I tested and the problem does not exist on the commit used by the Base team:
https://github.com/base-org/node/blob/main/reth/Dockerfile COMMIT=1ba631ba9581973e7c6cadeea92cfe1802aceb4a
The bug was introduced sometime in the last 18 days
Steps to reproduce
Restore chaindata from snapshot: publicnode.com/snapshots
Attempt normal run
Node logs
No response
Platform(s)
Linux (ARM)
What version/commit are you on?
main
What database version are you on?
main
Which chain / network are you on?
base
What type of node are you running?
Archive (default)
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: