hmmm.... after almost 2 days of being only connected to the 3 main nodes, no listening etc., i happen to have another fork somewhere around 3 hours ago... happend with the wallet I'm solomining for said almost 2 days straight.
now, after performing a rollback (and retrieving a new ip from my isp as the wallet of course became banned), it synced just fine.
yet, I wonder how the fork could happen in the first place while being only connected to the reference nodes...
Same just happen here... !!
I'm investigating this kind of * too. Staking, solomining. Last transactions 17:37 GMT (solomine 0.50 AMBER) and 19:27 GMT (stake). There was no 3-party connections (very often checked by getpeerinfo too), only the 3 mooo-s:
--ambercoin.conf--
server=1
listen=0
addnode=ambercoin01.mooo.com
addnode=ambercoin02.mooo.com
addnode=ambercoin03.mooo.com
--/ambercoin.conf--
It can be big help if wallet logs instead of "disconnected" something like "disconnected. banned for forking/old wallet/[something] mismatch/etc." Or even "disconnected. banned (for xx hours)." can be very big help - walletowner can see that "problem with me", not the infrastructure.
Second wallet, staking, not solomining, stays online and staking.
So, solomining can make forking? Antho281 you solomining too?
I have seen big rate of rejected blocks while solomining, different miners: 16%, 32%, 7% etc. My solomine wallet with solomining 280x has 1-core AMD Sempron (other miners connect here). Other miners and even local machine miner say often something like "...not providing work fast enough". Present fork may be some timing issue? BTW I have seen this kind of message always while solomining BTQ (quark) too.