Update Reth client to v1.1.1

[matjazv]

What was the problem?

This PR resolves #LISK-1248.

How was it solved?

• Update op-reth client to v1.1.1.
• Remove --engine.experimental flag for op-reth client as experimental engine is default now and the --engine.experimental flag is deprecated.
• Update README to reflect the update in the op-reth start command when running with the CLI.

How was it tested?

• CLIENT=reth docker compose up --build --detach

[sameersubudhi]

I ran the node multiple times and following warnings always recur in the op-node logs. Did you encounter this? These don't occur on the main branch though.

2024-11-11 23:04:59 t=2024-11-11T22:04:59+0000 lvl=info msg="Received signed execution payload from p2p" id=0xd4b1980ff702a65acef01e1be18af2406dae04be11ba9efea6f0658d149bb186:8316954 peer=16Uiu2HAmBuVpfZwoRodETmKQPiiE7awhs53vGaBzJCuZnSuU2zyb txs=1
2024-11-11 23:04:59 t=2024-11-11T22:04:59+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0xd4b1980ff702a65acef01e1be18af2406dae04be11ba9efea6f0658d149bb186:8316954
2024-11-11 23:05:01 t=2024-11-11T22:05:01+0000 lvl=warn msg="Failed to get payload" payload_id=0x036cceadd1e96b2d payload_id=0x036cceadd1e96b2d err="Unknown payload"
2024-11-11 23:05:01 t=2024-11-11T22:05:01+0000 lvl=warn msg="Cannot seal block, payload ID is unknown" payloadID=0x036cceadd1e96b2d payload_time=1714728793 started_time=2024-11-11T22:05:01+0000
2024-11-11 23:05:01 t=2024-11-11T22:05:01+0000 lvl=warn msg="Block sealing job of derived attributes expired, job will be re-attempted." build_id=0x036cceadd1e96b2d timestamp=1714728793 err="failed to seal execution payload (ID: 0x036cceadd1e96b2d): input error -38001: Unknown payload"
2024-11-11 23:05:01 t=2024-11-11T22:05:01+0000 lvl=info msg="Received signed execution payload from p2p" id=0xa4bcb8feafb55669d10bd01f534883eb3d018c35b0f6d6f9d005c62a0ab6f612:8316955 peer=16Uiu2HAmBuVpfZwoRodETmKQPiiE7awhs53vGaBzJCuZnSuU2zyb txs=1
2024-11-11 23:05:01 t=2024-11-11T22:05:01+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0xa4bcb8feafb55669d10bd01f534883eb3d018c35b0f6d6f9d005c62a0ab6f612:8316955
2024-11-11 23:05:04 t=2024-11-11T22:05:04+0000 lvl=info msg="Received signed execution payload from p2p" id=0xb002b9adc0d752d7f51a31f433e4a91cdbf54ea51c214355828b387b94825db5:8316956 peer=16Uiu2HAmBuVpfZwoRodETmKQPiiE7awhs53vGaBzJCuZnSuU2zyb txs=1
2024-11-11 23:05:04 t=2024-11-11T22:05:04+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0xb002b9adc0d752d7f51a31f433e4a91cdbf54ea51c214355828b387b94825db5:8316956

[matjazv]

I ran the node multiple times and following warnings always recur in the op-node logs. Did you encounter this? These don't occur on the main branch though.

2024-11-11 23:04:59 t=2024-11-11T22:04:59+0000 lvl=info msg="Received signed execution payload from p2p" id=0xd4b1980ff702a65acef01e1be18af2406dae04be11ba9efea6f0658d149bb186:8316954 peer=16Uiu2HAmBuVpfZwoRodETmKQPiiE7awhs53vGaBzJCuZnSuU2zyb txs=1
2024-11-11 23:04:59 t=2024-11-11T22:04:59+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0xd4b1980ff702a65acef01e1be18af2406dae04be11ba9efea6f0658d149bb186:8316954
2024-11-11 23:05:01 t=2024-11-11T22:05:01+0000 lvl=warn msg="Failed to get payload" payload_id=0x036cceadd1e96b2d payload_id=0x036cceadd1e96b2d err="Unknown payload"
2024-11-11 23:05:01 t=2024-11-11T22:05:01+0000 lvl=warn msg="Cannot seal block, payload ID is unknown" payloadID=0x036cceadd1e96b2d payload_time=1714728793 started_time=2024-11-11T22:05:01+0000
2024-11-11 23:05:01 t=2024-11-11T22:05:01+0000 lvl=warn msg="Block sealing job of derived attributes expired, job will be re-attempted." build_id=0x036cceadd1e96b2d timestamp=1714728793 err="failed to seal execution payload (ID: 0x036cceadd1e96b2d): input error -38001: Unknown payload"
2024-11-11 23:05:01 t=2024-11-11T22:05:01+0000 lvl=info msg="Received signed execution payload from p2p" id=0xa4bcb8feafb55669d10bd01f534883eb3d018c35b0f6d6f9d005c62a0ab6f612:8316955 peer=16Uiu2HAmBuVpfZwoRodETmKQPiiE7awhs53vGaBzJCuZnSuU2zyb txs=1
2024-11-11 23:05:01 t=2024-11-11T22:05:01+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0xa4bcb8feafb55669d10bd01f534883eb3d018c35b0f6d6f9d005c62a0ab6f612:8316955
2024-11-11 23:05:04 t=2024-11-11T22:05:04+0000 lvl=info msg="Received signed execution payload from p2p" id=0xb002b9adc0d752d7f51a31f433e4a91cdbf54ea51c214355828b387b94825db5:8316956 peer=16Uiu2HAmBuVpfZwoRodETmKQPiiE7awhs53vGaBzJCuZnSuU2zyb txs=1
2024-11-11 23:05:04 t=2024-11-11T22:05:04+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0xb002b9adc0d752d7f51a31f433e4a91cdbf54ea51c214355828b387b94825db5:8316956

Yes, I have noticed those messages recently.
We could try using the new OP Stack v1.9.5 version to see if these messages continue to appear.

[matjazv]

I ran the node multiple times and following warnings always recur in the op-node logs. Did you encounter this? These don't occur on the main branch though.

2024-11-11 23:04:59 t=2024-11-11T22:04:59+0000 lvl=info msg="Received signed execution payload from p2p" id=0xd4b1980ff702a65acef01e1be18af2406dae04be11ba9efea6f0658d149bb186:8316954 peer=16Uiu2HAmBuVpfZwoRodETmKQPiiE7awhs53vGaBzJCuZnSuU2zyb txs=1
2024-11-11 23:04:59 t=2024-11-11T22:04:59+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0xd4b1980ff702a65acef01e1be18af2406dae04be11ba9efea6f0658d149bb186:8316954
2024-11-11 23:05:01 t=2024-11-11T22:05:01+0000 lvl=warn msg="Failed to get payload" payload_id=0x036cceadd1e96b2d payload_id=0x036cceadd1e96b2d err="Unknown payload"
2024-11-11 23:05:01 t=2024-11-11T22:05:01+0000 lvl=warn msg="Cannot seal block, payload ID is unknown" payloadID=0x036cceadd1e96b2d payload_time=1714728793 started_time=2024-11-11T22:05:01+0000
2024-11-11 23:05:01 t=2024-11-11T22:05:01+0000 lvl=warn msg="Block sealing job of derived attributes expired, job will be re-attempted." build_id=0x036cceadd1e96b2d timestamp=1714728793 err="failed to seal execution payload (ID: 0x036cceadd1e96b2d): input error -38001: Unknown payload"
2024-11-11 23:05:01 t=2024-11-11T22:05:01+0000 lvl=info msg="Received signed execution payload from p2p" id=0xa4bcb8feafb55669d10bd01f534883eb3d018c35b0f6d6f9d005c62a0ab6f612:8316955 peer=16Uiu2HAmBuVpfZwoRodETmKQPiiE7awhs53vGaBzJCuZnSuU2zyb txs=1
2024-11-11 23:05:01 t=2024-11-11T22:05:01+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0xa4bcb8feafb55669d10bd01f534883eb3d018c35b0f6d6f9d005c62a0ab6f612:8316955
2024-11-11 23:05:04 t=2024-11-11T22:05:04+0000 lvl=info msg="Received signed execution payload from p2p" id=0xb002b9adc0d752d7f51a31f433e4a91cdbf54ea51c214355828b387b94825db5:8316956 peer=16Uiu2HAmBuVpfZwoRodETmKQPiiE7awhs53vGaBzJCuZnSuU2zyb txs=1
2024-11-11 23:05:04 t=2024-11-11T22:05:04+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0xb002b9adc0d752d7f51a31f433e4a91cdbf54ea51c214355828b387b94825db5:8316956

Related issues:

• Unable to sync Lisk Mainnet with the latest version (v1.1.1)
• Node can no longer synchronize with latest versions of op-node and op-reth (paradigmxyz/reth)
• Node can no longer synchronize with latest versions of op-node and op-reth (ethereum-optimism/optimism)

[matjazv]

Response from Reth team:

somehow we never Hit this on our infra...
sorry about this, expediting new release with fix https://github.com/paradigmxyz/reth/pull/12520 in the meantime please use 1.1.0
expect 1.1.2 monday

So on Monday we should get a new Reth version with a fixed issue.

[sameersubudhi]

Skipping reth upgrade to v1.1.1 based on this comment from the reth dev team. Closing the issue.

thanks for flagging,
somehow we never Hit this on our infra...
sorry about this, expediting new release with fix paradigmxyz/reth#12520 in the meantime please use 1.1.0