Quote from: Bittzy78 on March 26, 2018, 02:31:00 PM

Quote from: xrobesx on March 26, 2018, 02:13:00 PM

I've gotta say... These SAFE guys don't know what they're talking about.

I'm all for forking, go ahead fork KMD.

BUT... you better know what you're doing.

Have a competent developer who knows how to code, and maybe how to read code.

Anyone that is familiar with Komodo knows that there are 64 elected Notary Nodes, all of which get EASY DIFF MINING.

Now if you're going to fork Komodo, and not remove the pubkey's of the Elected KMD Notary Nodes, then guess what???

EASY DIFF MINING STILL EXISTS for KMD Notary Nodes.

No attack by KMD community or jl777.

All we have here are some smart people (elected kmd notaries with key's for the specified pub keys), and some dumb people (safe devs who left in pub keys in the code).

If the devs were competent enough to understand the coin they were forking, and to read the actual code, and know that the Elected Notaries have EASY DIFF MINING, then they could have either removed the KMD Notary Node pubkey's, or they could expect to have these individuals mine very easily.

Nothing here was an attack as Jl777 clearly pointed out.

If the SAFE community wants to learn anything at all.... its not to trust the SAFE DEVS with shit.

And don't trust any crypto coin doing a ROLLBACK!

Thanks, xrobesx.

http://vote.xrobesx.co to vote for me as a KMD Notary Node.

Ok...

https://komodoplatform.com/komodo-bug-found-how-we-defeated-an-attack/

So you are saying these are the same?
Wow. It is hard to believe the level of your misunderstanding.

A blackhat attacker does not stop the attack 0.0001% of the way in, does not go into discord/slack and explain what happened and how to fix it, does not undo the high diff that was created and make it so the chain does not have to be forked and all can be updated with a minimum impact.

When you see what a real attack is like, you can learn the difference between what happened and a real attack.