1. You fail to understand how Byteball works and especially the witnessing. People have tried to explain, a few pages back. Not our problem you have a weak mind.
Right, I don't understand everything, but it can be a sign of a conceptual flaw, not of my "weak mind".
2) Addressed in the whitepaper, compression works well today, price of data to store is price payed in bytes.
So what is the solution to the problem explained here:
So what? With a fee of 50$ someone can make DAG twice as big overnight? With a fee 500$ can make it 10 gb more? There is people who can do this just for fun. Is there some prunning mechanism what will allow to cut old transactions from database?
There isn't. I'm pointing this out for a long time but nobody is listening. Byteball has the same scalability problem like any other blockchain with adjustable blocksize limit. Database grows indefinitely and hardware and bandwith are the limiting factors. Moreover if somebody wants to attack byteball by sending huge data to the database it''s pretty easy and cheap at the current price. 8 years old Bitcoin blockchain nears 100 GB and you can make byteball database that big in 1 day for just $6700.
3) Quantum-proof is non-issue for hash-based signatures, when Bitcoin breaks, Byteball may break, the code supports different signature curve to be used even today, Whitepaper especially mentions NRU for this reason.
I know, I'd like to know how the conversion of old addresses will be done.
4) Whitepaper mentions the defined constants, 1 of which sets this limit, which is 100 I believe.
Thx, I'll check that part.
5) Organically, like is mentioned in the whitepaper and by many people in this thread.
What will happen during the transition? The network can't function in normal mode if several witnesses differ between transacting nodes.