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...
--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.
I'm solomining with 3 GPU on a Wallet and Owning a pool (amber.thecryptoworld.org:8080) where I'm mining with about 12 GPU at the moment.
The third wallet forked.. there's no mining on it
What about your internet connection Jayfek?
Sometimes, solomining ask a quicker connection than pool mining
There must be something, not just code Or...
EDIT: This ban to me seems come from all 3 mooo-s
I never solo mined and had the same issues with the same conf above (without server=1). Got also banned by the server. After getting on the right chain I deleted the conf and started it again. Since 12h is seems to work fine (previously I got every 2-3 hours to another fork and need to resync from the backup).
MAC OS.