Good sir did you find it ? <| sep |> While we may be free to express our opinions , you will edit them to how ever you see fit . You ' re such a fucking hypocrite . <| sep |> I answered the criticism most of it boiled down to WAAAAAAAHHHHHH I DON ' T LIKE THE FORMAT , which , when pressed , people were unable to defend as anything more than that . I took a look at Day 2 Top 32 , but didn ' t put the numbers together I will say that if you put the numbers together , it will strengthen my post , not weaken it . You ' re more than welcome to do so , I have no good way to scrape the data quickly . <| sep |> Agree on all points <| sep |> Do they want us to make fun of them ? <| sep |> It ' ll come back . In 2019 after Star Wars Land opens . <| sep |> The point I ' m trying to make is that if the common sense expected behaviour opcoderesulting changes don ' t have an effect on trie state if the tx hits OOG was ignored by the node leading to unexpected state , a service that is build on top of Eth that implements some internal accounting of its own for whatever reason speed , implementation concerns , etc then a bug like this could lead the service to deviate from the eth network ' s state , causing issues of lost money resources conflicts for offchain data . For a trivial example relevant to here , say you ' ve created your own account tracking according to the spec because you need to send transactions to many addresses and then clean them up after you ' re done , for whatever reason . Assuming your tracking doesn ' t update your own service ' s target account state if the TX goes OOG then if you don ' t catch this you would be left with an internal accounting error at the end of your execution , because you would attempt the transactions twice that errored , causing different gas costs because now those addresses are empty . You could run out of funds before completing your task because of it and perhaps if this is some time sensitive event , cause further problems around supporting infrastructure . To me and I assume most devs , if I was creating an automated system OOG means retry same , with more gas in this case this would lead to unexpected results . If this is done by some automated service , it can cause trouble if it ' s part of a larger running chain of processes . Do you see what I ' m getting at ?