We’re developing Email to scale: Getting to real-world usage for aeternity and as recommended are running our own node for that.
As far as I understand from the posts here, and the Telegram group, there was a 51% attack a few weeks ago (Notice regarding the recent attack) and the attacker used the proceeds from this attack (https://t.me/aeternity/234378) to fund another 51% attack yesterday.
In response, aeternity Anstalt has been working with the mining pools to roll back the chain and re-start mining with higher hash power in order to win the mining battle against the attacker.
As a result, our service has been having issues for around 24 hours writing transactions and we’re concerned our node may still be on the attackers branch.
Are there any instructions for how to recover our node from this state?
Starting a new node from scratch took ~2 days last time, and we would really prefer not to have that kind of backlog for our transactions. So any advice on how to proceed would be much appreciated.
What do we need to do in order to get our node onto the correct chain?
Thank you so much for any help you might be able to provide and all your hard work!