<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>erwan</author><text>Ethereum has different client software, they must all use the same consensus rules: produce&amp;#x2F;gossip&amp;#x2F;accept transactions and blocks that follow a certain format and respect certain invariants. When that specification is updated, a hard-fork occurs. It&amp;#x27;s not a problem if all clients meet the new spec perfectly but sometimes bug happens and different clients disagree on what constitutes the canon chain. This is what happened here: the OpenEthereum client (11% of the network) has had a bug following the Berlin hard-fork (network upgrade). Nodes runnning this client are stalling at a certain block because they don&amp;#x27;t recognize the new &amp;quot;post-Berlin&amp;quot; blocks as legitimate because of a bug in the implementation.</text><parent_chain><item><author>axiosgunnar</author><text>Can somebody explain the significance?&lt;p&gt;Is this related to the conflict between devs and miners where devs want to reduce the mining fees and miners responded by creating a fork?</text></item></parent_chain></comment><story><title>Ethereum Fork Fails on OpenEthereum</title><url>https://github.com/openethereum/openethereum/issues/353</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>yulaow</author><text>Reading the comments seems more like a technical problem on the consensus protocol of some implementation of eth nodes (in particular openethereum and geth)</text><parent_chain><item><author>axiosgunnar</author><text>Can somebody explain the significance?&lt;p&gt;Is this related to the conflict between devs and miners where devs want to reduce the mining fees and miners responded by creating a fork?</text></item></parent_chain></comment><story><title>Ethereum Fork Fails on OpenEthereum</title><url>https://github.com/openethereum/openethereum/issues/353</url></story>