Cleetus Feetus

> > > > > @kissing009 it depends on the hardware you use and quality of your peers. Most likely you need faster hardware. > > I do not think...

> Hi @xer0de , does this still happen? It could be because your peers are rebooting Yes, it still happens. Currently I get sync failed error with a peer and...

`t=2022-10-17T21:48:50+0000 lvl=warn msg="Ancestor below allowance" peer=f7535fd4 number=0 hash=0x0d21840abff46b96c84b2ac9e10e4f5cdaeb5693cb665db62a2f3b02d2d57b5b allowance=22,175,188 t=2022-10-17T21:48:50+0000 lvl=warn msg="Synchronisation failed, dropping peer" peer=f7535fd487f82d65e212512e6b8adcde6f485d44e8f0624a773bee28095a270d err="retrieved ancestor is invalid" t=2022-10-17T21:48:50+0000 lvl=warn msg="Synchronisation failed, retrying" err="peer is unknown or unhealthy"...

Yes it happens a lot, resynced with the snapshot provided as well. Same issue persists and is happening many times an hour.

> Try with the latest official binance snapshot, I just worked for me. Also, what flags do you provide? That is the one it is running on, flags are in...

@j75689 Can we please get this looked into when possible? It appears that when we connect to peers that have state pre hard fork we get massive desyncs.

> After replacing StaticNodes, the problem is disappeared > > First time, StaticNodes were taken from https://api.binance.org/v1/discovery/peers Second time I filled StaticNodes from another working machine and problem is disappeared...