That's what happens when you decide to write your smart contract language in what is basically javascript and your smart contracts are interpreted in a stack ba

That's what happens when you decide to write your smart contract language in what is basically javascript and your smart contracts are interpreted in a stack based VM. Doubly so when your contract execution is entirely determined by the order in which Tx happen to get accepted. It's actually sane when your contract is written in a non-turing-complete language with strong typing and the smart contract system has deterministic execution (i.e. you know the result when you submit the Tx and if the result would be different, the tx fails, preferably without charging you). I'm convinced that one of the main issues with most smart contracts is that they have such weak guarantees and the guarantees they do have are brittle and hidden behind complex, opaque proofs & constraint systems.