op-reth finalized block is far behind https://mainnet.base.org finalized block

upnodedev commented 5 months ago

Describe the bug

At the time of writing

Latest block: 12776875
op-reth finalized block: 12124550 (652,325 blocks ~ 2 weeks behind latest)
https://mainnet.base.org finalized block: 12776230 (645 blocks ~ half an hour behind latest)

The gap between 2 weeks and half an hour IS EXTREMELY LARGE!

We are running an OP Stack L3 on Base and this greatly impacts our node operation

Steps to reproduce

Note: Latest block at the time of writing 12776875

Sync an op-reth base node
Query the finalized block number from the op-reth node

curl -X POST -H "Content-Type: application/json" http://127.0.0.1:8545 --data '{"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["finalized", false],"id":1}' | jq .result.number

"0xb90186" = 12124550

Query the finalized block number form https://mainnet.base.org

curl -X POST -H "Content-Type: application/json" https://mainnet.base.org --data '{"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["finalized", false],"id":1}' | jq .result.number

"0xc2f326" = 12776230

Notice a huge difference (2 weeks vs half an hour behind latest)

Node logs

op-reth[3004943]: 2024-04-05T18:48:30.628633Z  INFO Canonical chain committed number=12776781 hash=0x8660d58b8ca0148b7dadbd2e2b4419b37e3203533b9ff0390b1f54089d56c9e1 elapsed=168.841904ms

Nothing wrong with logs

Platform(s)

Linux (x86)

What version/commit are you on?

reth Version: 0.1.0-alpha.22 Commit SHA: a9ac903ee Build Timestamp: 2024-03-13T16:58:11.796169604Z Build Features: jemalloc,optimism,reth_optimism_payload_builder Build Profile: release

What database version are you on?

Current database version: 1 Local database version: 1

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

make install-op

Code of Conduct

[X] I agree to follow the Code of Conduct

github-actions[bot] commented 4 months ago

This issue is stale because it has been open for 21 days with no activity.

emhane commented 3 months ago

what command are you using to sync the op-reth base node @upnodedev ?

upnodedev commented 3 months ago

op-reth

[Unit]
Description=base op-reth node
After=network.target

[Service]
ExecStart=/home/reth/.cargo/bin/op-reth node \
    --chain base \
    --rollup.sequencer-http https://mainnet-sequencer.base.org \
    --http \
    --http.port 6545 \
    --http.addr 0.0.0.0 \
    --ws \
    --ws.port 6545 \
    --ws.addr 0.0.0.0 \
    --authrpc.port 6551 \
    --authrpc.jwtsecret /home/reth/.jwt/base_jwt.txt
WorkingDirectory=/home/reth
Restart=always
User=reth
#Environment=RUST_LOG=jsonrpsee

op-node

[Unit]
Description=base op-node
After=network.target

[Service]
ExecStart=/home/reth/optimism/op-node/bin/op-node \
    --l1=<QUICKNODE> \
    --l1.beacon=<QUICKNODE> \
    --l2=http://localhost:6551 \
    --rollup.config=/home/reth/node/mainnet/rollup.json \
    --l2.jwt-secret=/home/reth/.jwt/base_jwt.txt \
    --rpc.addr=0.0.0.0 \
    --rpc.port=6000 \
    --network=base-mainnet \
    --l1.rpckind=quicknode
WorkingDirectory=/home/reth
Restart=always
User=reth

[Install]
WantedBy=multi-user.target

@emhane I start op-reth node in a service file with above definition

emhane commented 3 months ago

try updating to latest beta version @upnodedev, syncing to base mainnet on latest beta takes about 9 hours

emhane commented 3 months ago

alpha 22 doesn't have discv5 support, the op stack uses only discv5 by default https://github.com/paradigmxyz/reth/tree/v0.1.0-alpha.22/crates/net

github-actions[bot] commented 2 months ago

This issue is stale because it has been open for 21 days with no activity.

paradigmxyz / reth