Yeah. I am a total idiot - I was in the wrong session and searched the wrong debug log! Ignore the data above.
THIS looks more like something that should not normally happen:
10/08/17 16:55:50 received block 9aee7c6ab0d18367742a
10/08/17 16:55:50 REORGANIZE
10/08/17 16:55:50 REORGANIZE: Disconnect 55 blocks; fec9f399ecd8a7a816b1..a91bdde8e30c0b6fc48a
10/08/17 16:55:50 REORGANIZE: Connect 168 blocks; fec9f399ecd8a7a816b1..9aee7c6ab0d18367742a
10/08/17 16:55:51 REORGANIZE: done
55 blocks were invalidated by a longer chain which added 168 blocks. If any of those 55 blocks contained transactions AND they were manually removed from the wallet right after the reorg (to prevent the client detecting the tx had 0 confirms and rebroadcasting it) then you have a double spend.
That's as far as my logs go back. If something happened on the 17th of August - why did Cryptopia take 3 1/2 months to announce the attack and delisting?
Transactions were halted on the 18th and a notice was put that they were investigating a 51% attack. Now why they took this much longer to announce delisting I don't know....
Hello,
I believe the attacks occurred before 17 August.
I noticed that the currency that was traded at 200 litoshis and a single order dropped to 100 litoshis, with many LTC in the transactions.
I do not know if it's related ...