Defending the attack... one way to do so....
-
i think last valid block is http://explorer.feathercoin.com/block/c4bc5ef468c02f61e0ca6c77e1348a6809d9ee3538a4ad0aad790527c5ab1e8b
so i tried to fork the chain from that point, seems to work…
if enough people are willing to mine on the clean(er) chain, i would start it on my pool again.I think it should be clear that we cannot let any attacker just inject blocks making the legit blocks all invalid just get away with that. we should *fork* them out and proof to the world feathercoin cares about security of investments. Letting the chain beein played like it happed would be proven insecurity, not a very good point for a crypto coin from my point of view.
you can obtain a version with a custom checkpoint added by myself which sets this block above as checkpoint under github.
https://github.com/hynodeva/FeatherCoinIf you start it with -addnode=hynodeva.eu you should be able to retrieve this chain.
hynodeva dev
The major Pools would need to take part of this…
-
There were issues before that block.
-
I have checked my client logs, this is the heighest block which has been reordered with a large amount of blocks.