Different configurations of the besu client lead to inconsistent genesis blocks and inability to synchronize

[1033309821]

If the besu client is started using network-configs/besu.json and other clients are started using network-configs/genesis.json, they will not sync correctly due to some minor differences in the configuration files.

besu.json

The modified besu.json file is provided below.

[1033309821]

In addition, the chainspec.json configuration required by nethermind is slightly different. The values ​​in genesis.json are:

"pragueTime": 40139930634,
"osakaTime": 40139931018

But the values ​​in chainspec.json are:

"eip2537TransitionTimestamp": "0x958821e21",
"eip2935TransitionTimestamp": "0x958821e21",
"eip6110TransitionTimestamp": "0x958821e21",
"eip7002TransitionTimestamp": "0x958821e21",
"eip7251TransitionTimestamp": "0x958821e21",
"eip7702TransitionTimestamp": "0x958821e21",
"eip7623TransitionTimestamp": "0x958821e21",
"eip7692TransitionTimestamp": "0x958821fa1"

The mismatch between them will cause 'chain.ForkID()' to fail.