Quote from: SatoNatomato on June 13, 2017, 10:28:22 AM

He has no "potential attack", he is not a " white hat hacker". His "attack" would be him paying bytes to make transactions or store mp3s as messages in Byteball. What he plans to do is using Byteball and expecting it to break. Oh wow, such a hack.

Judging by general tone of your message you are about to agree with my assumption that once Byteball gets world-wide adoption and GB price rises we'll see most of people caring about fees and hence publishing mostly high-entropy data. Which in turn will lead to very low copression ratio of Byteball DB. I think we can omit this testing scenario if you post that you agree.

Quote from: SatoNatomato on June 13, 2017, 10:28:22 AM

When in reality he cant even find source-code of an open source project

I believe I could find it, just wanted to save my time, this is why I asked you for help.

Quote from: SatoNatomato on June 13, 2017, 10:28:22 AM

Further, there is no way to say after his attempted attack that it failed, he would just say he has to try harder or send more or think of more FUD. He would never admit he is wrong, you can see that in this thread when increase means decrease for him.

This is a valid point, but it can be solved easily. All we need is the devs to come here and say what max TPS Byteball can process without "breaking". I will either agree on that number or test it in practice. Let's wait for the dev's reply. If they don't give it then I'll be gradually increasing TPS and reporting progress here and on the slack. I'll stop when I run out of GBs.