While it may be true that using multiple pushdatas can insert a lot of data into a single UTXO (just like a building has no virtual height limit), there are still limits. 1. Ownership limit. My data is not your data, and with 6-10 billion people on the planet by 2040 there’s some restriction. 2. Complexity limit. Mixing white rice with black rice is reversible, but the task of separating becomes worse with small scoops of scale. 3. Unknown limit. Since no one has really gotten to play with the PUSHDATA very much due to continuing unfurling of hard cap limits (similar to dust limit not yet breaking double digits) we don’t have any experience yet with large size on coin, particularly breaking the 4 GB limit as it pertains to how Nodes treat it on a technical Performance basis. This could be akin to # of transistors on microchips. Remember, saying we can scale and scaling are two different things— one brings back memories of Joe Namath and another can bring back memories of the Titanic. But also we can think about building height “limit” not being an actual limit but a technical hurdle. 4 speed limit. That which is small can be fast. Speed of information has value. If my dictionary is slower than yours, my dictionary may suffer competitively. 5. Economic limit. When the seed of the New York city was young there was room enough on Manhattan for a few multi-acre farms and even some hunting/game land up where Columbia University stands. When price is cheap we can be liberal with our asset. But once all the UTXOs are used for simpleton purposes we will find a beautiful discovery of economics driving innovation and efficiency. When all the open shoe racks of your closet fill up you will need to dispose of the pair you dislike most to add a new pair of shoes you just bought and love. Forced efficiency and improvement. This is why Manhattan is so wonderful— it’s the geographic constraint of the River which is costly to traverse. There may be others but I gotta get to work.