Quote from: Big Naturals on March 29, 2018, 03:36:25 AM

Quote from: Zebra# on March 29, 2018, 03:15:07 AM

Quote from: Big Naturals on March 29, 2018, 02:33:08 AM

Quote from: Zebra# on March 29, 2018, 02:27:33 AM

Quote from: ComputerGenie on March 29, 2018, 12:47:34 AM

Quote from: Bittzy78 on March 28, 2018, 09:42:42 PM

We gonna hustle baby!

Even if it means stealing currency from those that rightfully ~~own~~ stole it. Undecided

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

"Komodo Bug Found: How We Defeated An Attack

MARCH 13, 2017

Komodo has just gone through a small emergency caused by an attacker trying to exploit a bug he found. The attacker didnt cause any real damage as our team responded quickly.

The attack started during the weekend and lasted about 30 hours before one of our notary nodes detected it. We quickly pushed a fix that was going to go into effect at Komodo block # 236000. At this point, the attacker had only been creating few coins to avoid detection, and the damage caused was minimal.

The attacker went into overdrive after he saw that a fix was coming. He started to generate as many coins as he possibly could, and that led us to take further action. We publicly announced that we would roll back few hours, and advised everyone not to do KMD transactions until the rollback was done. Heres how jl777 described the situation:

I announced the block that will be rolled back to, pretty much in real time, so it is more like stopping the chain at 235300 rather than rolling back. Of course, a few hundred blocks were generated during the time to make the fix, so yes, technically it is a rollback of a few hours.

Without the rollback, KMD coin supply would have expanded about 10 % as the attacker would have been able to create over 10 million KMD. We managed to avoid all this by just rolling back a few hours.

These recent events have a lot of similarities with Bitcoins early days. Heres what happened on 6th of August, 2010:

A major vulnerability in the bitcoin protocol was spotted. Transactions werent properly verified before they were included in the transaction log or blockchain, which let users bypass bitcoins economic restrictions and create an indefinite number of bitcoins. On 15 August, the vulnerability was exploited; over 184 billion bitcoins were generated in a transaction and sent to two addresses on the network. Within hours, the transaction was spotted and erased from the transaction log after the bug was fixed and the network forked to an updated version of the bitcoin protocol. This was the only major security flaw found and exploited in bitcoins history.

The difference is that bitcoin knew about it for over a week, while we found out about it when the attack was already under way. This attack is not comparable with a typical hack where an exchange loses funds. In our situation, the bug was in Komodo code and considering its implications a rollback was the logical thing to do to avoid damage.

Komodo is still a young project and has a lot of new code built on top of it. The quicker these bugs are found, the less effect they will have. The longer Komodo blockchain keeps running, the less likely that further such bugs are found in the future.

We continue to closely follow our network and promise to quickly respond in a similar manner to any possible future incident."

KMD notaries mining Safe coin wasn't an attack, if it was they would not have stopped and offered to help you fix the problem , and donate the coins they mined back to your community. Trying to compare that to a real attack like KMD experienced is like comparing a parent smacking a naughty toddlers bum with à violent rape. You posting jl777's explanation proves the point exactly, he's describing an attack, not an inadvertent outcome of Safe coin devs leaving hard coded kmd notaries in your coin source code.

Big Naturals Grin

That's a bit of a stretch Grin

I know you chuckled when you typed that Grin

I don't believe you can let someone off the hook for unethical behavior based on how much mercy they had for the victim.

Now, I acknowledge that you don't see it as an unethical act or attack. I respect your opinion and passion, but as I said before, I strongly disagree.

Yes, we disagree, I do admit I know nothing of the safecoin devs background, so I don't know if he will end up producing anything useful from here on. With jl777 however, I have watched and researched his projects for a good while, and to my knowledge he has demonstrated on numerous occaissions that he has all 5 qualities that make a super dev in this space:

1. high skill as a coder
2. high level experience in finance industry
3. superior communication skills, patience, humour, ability to explain & inspire
4. work ethic, the guy Is online working everyday, 7 days a week +12 hours going on 5 years now
5. demonstrably honest, every project he has started migrated to KMD, has done 2 ICO's, one for Supernet which OWNS millions in crypto funds (I.e jl777 did not receive funds personally but used to create a crypto fund), and the second for KMD which pays for notarisation fees. I have not seen one credible case of jl777 ever scamming anyone, but countless cases of his generosity

Five years of good reputation in the crypto field should not, and will not be tarnished by Safe coin, so you guys would do well to consider thanking jl777 for using his code, and apologising for the slurs against his character.

Maybe we are beginning to understand each other Grin

It's clear that you and your team have a lot of respect and admiration for your dev.

I hope you can also see that we have a lot of respect and admiration for ours.

There's a good reason we are standing up for our project and our developer. Just like there is a good reason you are standing up for yours. We'll never agree on all the details in-between but that doesn't mean we can't move forward.

Hey, I know our dev does not have the track record in crypto yet but he shares so many of those great qualities you just described. I assure you that the first ever fork of Komodo is in very good hands. Give him some time.

We've always been thankful to JL777 and the Komodo team for the work they've done.