The problem is if, say, a proposer maliciously proposes a block where the first transaction deletes a nameTx, then a second transaction updates that name. Not sure if this is actually a problem or not, but state/execution seems to panic in this case, and I'm not sure what catches it.

We should catch panics during block execution and return an error.