Stefan Pingel

Hi @emclab, we have had a look at that problem and we are planning to fix that issue as part of some work in the p2p area in the near...

@mbaxter This should get fixed with the changes that I'm doing. The main map holding the peers in EthPeers will use the peerId instead of the connection as the key....

This is the EIP describing the fork ID message: https://eips.ethereum.org/EIPS/eip-2124

@Gabriel-Trintinalia and I looked at the log file (Log03.txt) and found the following: Block #14,965,607 with block hash 0xe27481970fc2c069ce84d9be9561d21ac87d699fd814e388a5eea24d587cfb51 is imported, but checking on a block explorer we can see...

The latest experiment on mainnet with 3 nodes with changes and 3 nodes without resulted in the 3 nodes without the changes to the defaults to finish syncing earlier than...

All nodes, except for one with the changed defaults, were able to hold on to peers very well: 

I have the original log file available, but it is 11GB in size.

Disconnects with reason TIMEOUT from full log file: `2022-07-28 04:47:42.502+00:00 | EthScheduler-Timer-0 | DEBUG | AbstractPeerConnection | Disconnecting connection 685122028, reason 0x0b TIMEOUT 2022-07-28 06:07:55.932+00:00 | nioEventLoopGroup-3-5 | DEBUG |...

[https://app.zenhub.com/files/206414745/c4c7dae8-c7e2-4b14-8bfb-8d8845c262d3/download](https://app.zenhub.com/files/206414745/c4c7dae8-c7e2-4b14-8bfb-8d8845c262d3/download)

Clients not sending the ForkID: - Nethermind v1.14 - bor/v1.10.9 (Matic network) - Geth/v1.10.25 (must be configurable?) - Geth/v1.1.16 (old version, most geth clients are sending the fork id) -...