Karl Knutsson

I run into the same problem with FreeBSD 10.3 amd64, both with ghc 7.10.2 and ghc 8.0.2.

At the moment Cardano is running in a federated setting and is not utilizing Kademlia . New network related work for Cardano's decentralized release is going on over at https://github.com/input-output-hk/ouroboros-network...

Yes, the document at https://cardanodocs.com/technical/protocols/p2p/ is out dated. The peer discovery method hasn't been made public yet.

I will make a post here when it is pushed.

My node had a block from the future around the time of the https://github.com/input-output-hk/cardano-node/issues/4720 issue . An SPO shared logs with @gufmar regarding another TraceDidntAdoptBlock at 2023-01-02T05:13:57.03 . This also...

> > May I ask though for the rationale in adding the complexity to try to save blocks from the future? Why not keep it simple and just discard them...

The complete fix would mean that cardano-ping can do some parsing of unknown versions.

> simply refuse to transition from TooOld to YoungEnough while it only has local peers For relays this is exactly what we want. For nodes with some trusted local peers...