op-reth is not informing safe and finalized blocks.

[qedgardo]

I'm running a base node (mainnet) with op-reth ( and op-node running in the same node. The node informs unsafe blocks, but safe and finalized blocks are always 0.

op-reth --version
reth-optimism-cli Version: 1.1.0
Commit SHA: 1ba631ba9581973e7c6cadeea92cfe1802aceb4a
Build Timestamp: 2024-10-14T18:00:59.446775093Z
Build Features: asm_keccak,jemalloc,optimism
Build Profile: release

op-node version: v1.9.3

I didn't find error logs, just:
Consensus client logs:

op-node: t=2024-10-22T15:14:15+0000 lvl=info msg="Sync progress" reason="new chain head block" l2_finalized=0x0000000000000000000000000000000000000000000000000000000000000000:0 l2_safe=0x0000000000000000000000000000000000000000000000000000000000000000:0 l2_pending_safe=0x0000000000000000000000000000000000000000000000000000000000000000:0 l2_unsafe=0x7fc2a9d25d585d3666f16ee94526ac4262f13121a12b4f403fdd213fed606a6f:21410354 l2_backup_unsafe=0x0000000000000000000000000000000000000000000000000000000000000000:0 l2_time=1729610055

Execution client logs:

INFO Executing stage pipeline_stages=9/14 stage=MerkleExecute checkpoint=21395584 target=21405791 stage_eta=2h 4m 1s

op-reth args:

op-reth node \
    --chain base \
    --rollup.sequencer-http https://mainnet-sequencer.base.org \
    --datadir /base/data \
    --http \
    --http.addr 0.0.0.0 \
    --http.port 8545 \
    --http.api web3,debug,eth,net,reth \
    --ws \
    --ws.addr 0.0.0.0 \
    --ws.port 8546 \
    --ws.api web3,debug,eth,net,reth \
    --authrpc.addr 127.0.0.1 \
    --authrpc.port 8551 \
    --authrpc.jwtsecret=/var/lib/base/jwt.txt \
    --metrics 0.0.0.0:6060 \
    --engine.experimental \
    --log.file.max-files 0 \
    --enable-discv5-discovery \
    --rollup.disable-tx-pool-gossip 

op-node args:

op-node \
    --l2.enginekind=reth \
    --l1.trustrpc \
    --l1.rpckind=basic \
    --l1=<l1-rpc-endpoint> \
    --l1.beacon=<l1-beacon-endpoint> \
    --l2=http://127.0.0.1:8551 \
    --rpc.addr=127.0.0.1 \
    --rpc.port=9545 \
    --l2.jwt-secret=/base/jwt.txt \
    --network=base-mainnet \
    --p2p.advertise.ip=<public-ip> \
    --rollup.load-protocol-versions=true \
    --syncmode=execution-layer \
    --rollup.halt=major

Do you know what I am missing? 
I appreciate any help you can provide.

[Rjected]

Has the node finished initial sync yet?

[qedgardo]

Hi @Rjected, thanks for your reply!
The node stills syncing:

curl -X POST http://127.0.0.1:8545 -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":1}' 
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "startingBlock": "0x146504f",
    "currentBlock": "0x1467880",
    "highestBlock": "0x1467880",
    "warpChunksAmount": null,
    "warpChunksProcessed": null,
    "stages": [
      {
        "name": "AccountHashing",
        "block": "0x146a05f"
      },
      {
        "name": "Bodies",
        "block": "0x146a05f"
      },
      {
        "name": "Execution",
        "block": "0x146a05f"
      },
      {
        "name": "Finish",
        "block": "0x1467880"
      },
      {
        "name": "Headers",
        "block": "0x146a05f"
      },
      {
        "name": "IndexAccountHistory",
        "block": "0x1467880"
      },
      {
        "name": "IndexStorageHistory",
        "block": "0x1467880"
      },
      {
        "name": "MerkleExecute",
        "block": "0x1467880"
      },
      {
        "name": "MerkleUnwind",
        "block": "0x146a05f"
      },
      {
        "name": "Prune",
        "block": "0x1467880"
      },
      {
        "name": "PruneSenderRecovery",
        "block": "0x146a05f"
      },
      {
        "name": "SenderRecovery",
        "block": "0x146a05f"
      },
      {
        "name": "StorageHashing",
        "block": "0x146a05f"
      },
      {
        "name": "TransactionLookup",
        "block": "0x1467880"
      }
    ]
  }
}

[qedgardo]

The unsafe reported block is up to date but, the node is still not adding safe and finalized blocks. What would be a proper time to wait until the Base mainnet node finish the initial sync?

[mattsse]

the head block will be updated once the entire pipeline finishes, then the node can start processing new forkchoice updates again and will update the safe/finalized blocks