>that doesn't mean Eth as a whole is broken That's true in the sense that it's not why ETH is broken. ETH as a whole is broken because it's cryptocurrency. The

>that doesn't mean Eth as a whole is broken That's true in the sense that it's not why ETH is broken. ETH as a whole is broken because it's cryptocurrency. The whole idea of smart contracts is never going to work as advertised, it's impossible to make a more complex contract without running into any number of these flaws and spending an inordinate amount of your time and energy trying to mitigate and workaround them. But at the same time these are the types of contracts that drive developers to ETH. It's a lose-lose situation, at best it's equivalent to a payment API that's extremely unpredictable and insecure and will never have those issues fixed because they're part of the design. These flaws aren't inherent in making online transactions, they only pop up when you insist on using blockchains for everything, when there's no real reason to do that. >Also, trading ought to be done in Layer 2s. It's really baffling to me how L2 chains have become a serious thing. If you ask me those are just workarounds for flaws in the design of the L1 chains, nobody actually wants to use L2 chains but they're forced to because ETH (and other L1 chains) are so poorly designed that it can't accommodate most things people actually want to do. >They're programs with a low ceiling on the number of steps and possible codepaths. They barely even have loops half the time. Estimating isn't that hard in practice. Ok but why should anybody have to estimate in the first place? There's no reason for it with a trivial transaction, requiring this is just bad design.