Can't fetch the block tip using op-reth for base mainnet #9053
Labels
A-op-reth
Related to Optimism and op-reth
C-bug
An unexpected or incorrect behavior
S-needs-investigation
This issue requires detective work to figure out what's going wrong
Describe the bug
I'm trying to sync a base mainnet archive node using op-reth. I first used a normal sync with op-node, after 5 days I got about 5M blocks synced, but the sync speed was really slowing down. So I searched in the reth telegram channel to see if anyone had been able to synchronize faster, and found that it was possible to use the
--debug.tip
flag. The users specified that it was necessary to test the hash of several blocks before being able to synchronize, but for my part none of them worked, even after waiting a whole night. The sync is stuck on:Fetching tip block from the network.
Steps to reproduce
op-reth node --chain base --rollup.sequencer-http https://sequencer.base.org --http --ws --http.api eth,debug,trace --ws.api eth,debug,trace --authrpc.port 9551 --authrpc.jwtsecret /data/base/secrets/jwt.hex --port 30303 --http.port 8547 --ws.port 8548 --datadir /data/base/execution --metrics 0.0.0.0:9001 --http.addr 0.0.0.0 --ws.addr 0.0.0.0 --enable-discv5-discovery --discovery.v5.port 30304 --debug.tip "0xf976207a3f98e8ae6752e632b4f2b04f564862fc0932574b9c01b26888c41f5f"
Node logs
reth Version: 1.0.0-rc.2-dev
Commit SHA: 7bfc604
Build Timestamp: 2024-06-19T04:20:46.851673219Z
Build Features: jemalloc,optimism
Build Profile: maxperf
Current database version: 2
Local database is uninitialized
The text was updated successfully, but these errors were encountered: