i've spent enough time on deso's documentation and code to conclude the following:

1) @nader is exaggerating by omission, and your initial analysis of 30 tps is fair.
2) what deso has to offer is far beyond code optimizations that can be addressed when the load justifies it

just to be clear, the current processing power of deso is more than enough to power things through. we're really talking about hypotheticals of incredible widespread global adoption here.

we have time to figure those things out