Indeed, one can look at Lamport clocks or Vector clocks or simply the block height. However a miner might decide to trigger a race condition by transaction withholding. Setting safe boundaries for timeouts seems like a practical issue to consider
Yes. The short term reward is indeed the individualistic gains aspect.
I’ve been playing in my head with the following:
We’re in the age of AI for the commons: it becomes a public utility and hence drives down the marginal cost as the market opens.
Interesting. So you’re trying to split state from function. I hope more people will adopt that strategy when designing smart contract platforms :). It makes sense to make the state recording IO bound and the compute consensus process bound and async.