First. It was no statement but an assumption within a question.
And Second. In my statement (see post #1270) I was quoting "aiwe" (see post #1261) in which he corrected the statement of "Andretti83" (see post #1258) with the words: "In fact Karbo was patched
BEFORE the disclosure [of Bytecoin, own note]" because "Andretti83" in turn was answering on my question from post #1257 in his post #1258 with:
So, if the statement "Karbo was patched
BEFORE the disclosure" should not be true, what I am doubting because "aiwe" belongs to the dev-team and I believe him for reasons I do not know, I for one did not state this.
And KRB team twittered 2 hours and 11 minutes later than Monero team at 18 May 2017, 5:39 AM that "#karbowanec is patched and safe". They did not inform about the fact
WHEN it was patched.
I was solely wondering why a bug should have been patched before a disclosure. At first glance it sounds a little bit absurd. Thats why I
asked in my post #1270:
I dont want to be distrustful but if Karbo team patched its coin BEFORE the disclosure it could have theoretically been able to exploit this insider knowledge, issnt it?
I was originally referring to this news from 28/05/2017:
https://www.cryptocoinsnews.com/cryptonote-currency-bug-allowed-creation-unlimited-number-coins/ in which was statet:
After a complete network update, Moneros team notified all affected CryptoNote-based cryptocurrencies that they had until mid-May to patch the vulnerability. These include Boolberry, Bytecoin, DigitalNote, and DashCoin. (note that DashCoin and Dash are different currencies).
At the time of the initial disclosure, Monero, Aeon, Forknote and Boolberry had already patched the bug. DashCoin, DigitalNote and Bytecoin had not, although now that the vulnerability was made public the developers of these currencies have reportedly fixed the problem.
In any case I did not want to accuse KRB-team to exploit a bug. On the one hand I was surprised that such a heavy weighting bug could be possible and on the other hand I was surprised that the bug was already fixed by the teams of the Bytecoin forked coins like Monero, Karbowanec etc. see
https://upload.wikimedia.org/wikipedia/commons/7/7a/Forks-tree-fixed.pngwhile in contrast to them the team of Bytecoin which is the parent coin of several coins was not able to fix the bug instantly.
Regards
