There was an attack on the network and it caused a fork on the blockchain a few days ago. You might be on the wrong chain...
I was on the wrong chain for a couple days myself. Luckily I always have a copy of my data folder just two or three weeks old so it's easy for me to get back on track.
If everything else fails, just start syncing from the beginning with the latest wallet. And then, as soon as you're done, close the wallet and make a backup of your data folder!
I was on the wrong chain for a couple days myself. Luckily I always have a copy of my data folder just two or three weeks old so it's easy for me to get back on track.
If everything else fails, just start syncing from the beginning with the latest wallet. And then, as soon as you're done, close the wallet and make a backup of your data folder!
What kind of attack?
Details?
Thanks.
The attack brought him nothing but creating problems to synchronize wallets (decrease the number of connections for those who have not the necessary settings in the file diamond.conf).
As a result, some wallets were on the wrong chain.
But this is easily eliminated by removing the old blockchain and syncing from scratch using the backup archive.
So are you saying , it was a sybil attack that was isolating some nodes which allow
the attackers to utilize their own nodes to withhold blocks and/or headers, reject blocks and/or headers, purposefully fail to relay block’s and/or headers
and so on to cause the fork.
Were the necessary settings in the conf file , using addnode= to trusted nodes to block the attacks?
or
Was it something else?
Thanks.
The main method of protecting has been the addition of recording bantime and addnode.
But it is much less felt the attack for wallets using an additional connection to the .onion nodes.
These records have been repeatedly cited here.
You can find them by scrolling this section a couple of pages back.
