I agree that common sense isn ' t very objective here I am mostly going off of my view that OOG means all except gas cost is reverted which is something that is stressed in the protocol description , tutorials , etc , and so that ' s the perspective I assume that most devs would reach , as well . Of course I could be wrong and we wouldn ' t know what common sense is and I stress common here , as in majority sense , not good sense until we have 910 services disagree with the node on something . Then you could make the case that either the node got it wrong or the spec is really confusingly written ! Any time the spec is ambiguous , it should be made less so . I agree , and I think this is something that needs to be worked on in the space either way . All that said , I appreciate the team and foundation ' s work on geth and I understand how difficult implementing these systems is . This wasn ' t an attack on you or the team EF at all , just my two cents on how I would have expected the proper implementation to behave !