@markm
i suggest following addnode entries
#all lines with a # in front are optional settings and inactive as long as u leave the #
##################
logtimestamps=1
listen=1
noirc=1
addnode=213.136.80.93
addnode=37.187.176.193
addnode=167.114.184.20
addnode=213.136.86.202
addnode=213.136.86.205
addnode=213.136.86.207
addnode=84.39.96.180
bantime=3600
maxconnections=50
#changeaddress=youraddressforchange
# to disable PoS
#reservebalance=9999999
# for more logging
#debug=1
#printcoinage=1
#printcreation=1
#printpriority=1
#printstakemodifier=1
#printcoinstake=1
#printfee=1
#printjunk=1
############################
we will update first page of this thread to the same soon
as u can see here some wallets still not updated towards 2.1.0.4 which increase the chance they end on a fork
if u didnt do already make sure u run the actual wallet
https://github.com/DMDcoin/Diamond/releasesDiamond v2.1.0.4
DMDcoin released this on 7 Jul
and today
so nothing changed in the network situation
there is the mainnet with all explorer and exchanges and 170+ active nodes most of them already on wallet 2.1.0.4
and there is since some time a fork with like 30 wallets that didnt update to 2.1.0.4 with no explorer and no exchanges
if u update wallet to 2.1.0.4 and u use the addnode as suggested above there is absolute no risc u land on a wrong chain
the reason this happend is because we did release wallet 2.1.0.4 as a non mandatory wallet and did not block the old 2.1.0.3
but in fact it is mandatory because 2.1.0.3 wallets are very likely to fork if the not run 24/7
the reason is one time check inside is done in a way that use a actual time instead of blocktime when he check blocks he sync
this is no issue if blocktime and actual time is basical the same (for a 24/7 node) but if u go with ur wallet just online from time to time or u suffer some poweroutage and have to sync a few history block there is
always a chance that without wallet 2.1.0.4 u lose connection to the mainnet
we could release a 2.1.0.5 to finally block all comunication with the forked 2.1.0.3 wallets but that would mean we also lose the "good" 24/7 active 2.1.0.3 wallets which are still with the mainnet now
we did decide to not release a 2.1.0.5 and instead remember again and again people to please update to 2.1.0.4
this issue fix itself as more and more of the users will update to 2.1.0.4