nice design, great work dev!

I'm glad you have a mobile wallet in the roadmap, introducing mobile integration is  great since it can lead to mass adoption.

I had no experience with the purse, I'm a noob. whether it is possible to recover the wallet? there's not a lot of coins, but all I would like to get them back to your new wallet.

if you know what your seed is (the 25 word mnemonic), you can recover your wallet with the following command and paste/type in your seed when prompted.

The attacker remained a bit longer this time and mined at high difficulty. But once he noticed he couldn't drive it higher, he left.
The chain is now mined by 60kH/s and blocks will be very slow for quite some time.

The last such large attack happened 24h ago. I am not counting the many smaller attacks within the last 24h.
Yesterday the attacker left around block 35300 when the difficulty was around 50M. However the difficulty adjustment
behaved very badly because even though hashrate was low after the attack and blocks were coming in at only
one per hour, it increased the difficulty without any sense until 160M and the chain became stuck for several hours.

We know that the network hashrate is derived from the difficulty and it does not reflect the real hashrate at any moment.
The pool hashrate however is accurate since it is derived from the real shares submitted by the workers.

I suggest therefore that the dev and the pool operator of superpools go over the pool's logs to see exactly
when the attacker entered and when he left and how the difficulty adjustment reacted or rather how it should react better.

Clearly it makes no sense whatsoever to increase the difficulty when the last block was an hour ago, no matter how fast the blocks
were coming previously. There must be a long window and a short window to monitor, as well as the time between the last very few blocks.
Depending on how the measured average block times in each of these windows match or rather not match, priority must be given to the one closer to present time.

The difficulty adjustment works well now when the hashrate is skyrocketing. It is too slow however to re-adjust when the hashrate suddenly drops, like from 1.1MH/s to 55kH/s.
This happened right now when the latest attack stopped at block 36086 with the difficulty at 131M. The next block was found only after exactly one hour.
You would expect the difficulty to drop significantly, but it went up to 144M.

The pools are actually the ones who see what is really happening since they do directly measure the actual hashrate the miners contribute to the network through them in every single second.
I could imagine a re-target method where the pools are communicating the actual hashrate that is pointing at them. This way the adjustment could be done as hashrate joins or leaves.
The current systems in use only react after the fact by looking at the timestamps of previous blocks, which is always too late and inaccurate anyway.
Already because faster or slower blocks due to natural variance will emulate a higher or lower hashrate, which means the adjustment will be fooled by hashrate increase or decrease which simply doesn't exist.
Of course that would open up also many attack vectors and it might be not viable at all.

If the adjustment back down worked so fast how do you regulate the amount of blocks found per 24 hour period? Should be 720 Blocks per day right? When some idiot uses nicehash and runs difficulty up they hit blocks well to fast and once they stop the network needs to change difficulty. In Theory  If some one nice hashed in a few hours all 720 blocks then the network should not produce more blocks for next 20 hours or so. If it does readjust in like 2 hours then you would produce more than 720 blocks per day?

The network needs to and does change difficulty much earlier than "once he stops". He therefore can't mine 720 blocks within a few hours. Especially not since the V2 fork which implemented a more aggressive difficulty adjustment. If we would wait until "he stops", he would never stop and mine all 18.5M coins in no time.

The attacker is gone again, leaving the difficulty at 350M. Superpools has around 30kH/s, masaripool around 60kH/s and ms-pool has around 5kH/s.
Good luck to the remaining permanent miners. It will probably take 5-10 hours this time until the difficulty is again down to a level which reflects their hashrate, at which point they will start to earn some coins again. This is unless the attacker won't return just then, get 99% of all block rewards again and rinse repeat.

The operator of superpools can see in his backend where the hashrate is coming from. He has recently added a port specifically for Nicehash mining. As far as I remember this cryptonote universal pool has ways to block miners if they are considered to be malevolent, e.g. by detecting things like low diff attacks and then blocking their IP.

^ that all depends on when an exchange picks it up