But the way he structured the transaction fees really made me think he isn't thinking holistically enough about design and long-term. But I am not omniscient and I can't keep up with every design change that every project does. So it would be crazy for me to tell people not to be intrigued by Byteball. I am. So much so, that I dedicated the last chapter (major section) of my whitepaper to Byteball's DAG stability point consensus algorithm.
Do you think the transaction fees should be scaled? Instead of bytes per byte of data stored/used-by-database, it would be bytes per byte up to a limit of say 1000, then 2 bytes fee for each byte stored, then if the transaction or data to store is above 10 000 bytes, you would require to pay 3 bytes for each above that level? What is that kind of scale called?
That would discourage to use the Byteball network and database as a personal storage if the price of each byte is very low.