PeerCleaning and optimization

[kristjank]

Hi @sharkdev-j @sharkdev-a ,

only one seed peer is usually not a good idea. I know there has been lately an issue with a lot of them. Please take a look at the clean healthy SEED peer list - and include them from here:
https://github.com/kristjank/ark-go/blob/master/core/arkenv.go#L206

After you randomly select one SEED peer... you must build up the ACTIVE healthy peer list to work with, meaning:

connect to randomly selected SEED peer from the SEED list
call peer/list from that peer
clean the received peer/list by (version= 1.0.1 - mainnet, status=OK, and find the max height peer, and then select just the ones (let's say 10 blocks smaller than max height peer)
save filtered the peer list globaly so it can be used on the API for later on (multi broadcasts and switch peer, etc)...
--I use this in arkgo now - and I usually clean the list from 150 to 70/60 healthy peers to work with...