A valid signature does not necessarily guarantee the outcome a user intended.
Ethereum is now exploring native transaction assertions as a layer beyond clear signing. The idea is to let users specify or verify expected state changes and reject transactions when the actual
Ethereum is changing how blocks travel across the network.
Large execution payloads are becoming a networking problem: with whole message propagation, a node must receive the entire payload before it can start forwarding it.
EIP 8411 explores splitting payloads into
Ethereum is exploring shorter slots with EIP-8198, initially targeting a move from 12 seconds to 10 seconds.
But reducing slot time also leaves less time for block propagation, execution and consensus duties.
For Ethereum developers, where should the protocol draw the line?