{"id":31611,"date":"2020-11-11T16:40:16","date_gmt":"2020-11-11T14:40:16","guid":{"rendered":"https:\/\/forklog.com\/en\/?p=31611"},"modified":"2025-08-28T04:34:36","modified_gmt":"2025-08-28T01:34:36","slug":"infura-outage-explained-as-an-unannounced-hard-fork-of-ethereum","status":"publish","type":"post","link":"https:\/\/forklog.com\/en\/infura-outage-explained-as-an-unannounced-hard-fork-of-ethereum\/","title":{"rendered":"Infura outage explained as an &#8216;unannounced hard fork&#8217; of Ethereum"},"content":{"rendered":"<p>Outages at Infura, the leading provider of infrastructure solutions for the Ethereum network, are linked to consensus errors in older versions of the Geth client. Because part of the network had not updated to the latest version, Ethereum split into two chains at block 11234873.<!--more--><\/p>\n<blockquote>\n<p>&#8220;At some point Ethereum developers implemented changes to the code that led to today&#8217;s split at block 11234873 (07:08 UTC). Those who did not upgrade (Blockchair, Infura, some miners and many others) were stuck for two hours on the shorter chain (~30 blocks),&#8221; wrote Blockchair developer Nikita Zhavoronkov.<\/p>\n<\/blockquote>\n<p>According to him, &#8220;technically this was an unannounced hard fork.&#8221;<\/p>\n<blockquote class=\"twitter-tweet\">\n<p dir=\"ltr\" lang=\"en\">(1\/2) Ok, so what happened today on <a href=\"https:\/\/twitter.com\/hashtag\/Ethereum?src=hash&#038;ref_src=twsrc%5Etfw\">#Ethereum<\/a>\ud83e\udd84:<\/p>\n<p>1. At some point Ethereum developers introduced a change in the code that led today to a chain split starting from block 11234873 (07:08 UTC)<\/p>\n<p>2. Those who haven\u2019t upgraded (<a href=\"https:\/\/twitter.com\/Blockchair?ref_src=twsrc%5Etfw\">@Blockchair<\/a>, <a href=\"https:\/\/twitter.com\/infura_io?ref_src=twsrc%5Etfw\">@infura_io<\/a>, some miners, and many others)\u2026 <a href=\"https:\/\/t.co\/mbRYFU5tgn\">pic.twitter.com\/mbRYFU5tgn<\/a><\/p>\n<p>\u2014 Nikita Zhavoronkov (@nikzh) <a href=\"https:\/\/twitter.com\/nikzh\/status\/1326465592841351168?ref_src=twsrc%5Etfw\">November 11, 2020<\/a><\/p>\n<\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>Nikita Zhavoronkov contends that something similar happened in the Bitcoin network seven years ago when there was a database upgrade.<\/p>\n<blockquote>\n<p>&#8220;The solution: update Geth and run debug.setHead(11234872)&#8221;, he added.<\/p>\n<\/blockquote>\n<p>Even with a remedy, Zhavoronkov stresses that what happened should not be underestimated and should be considered one of the most serious issues Ethereum has faced since the The DAO incident four years ago.<\/p>\n<blockquote class=\"twitter-tweet\" data-conversation=\"none\">\n<p dir=\"ltr\" lang=\"en\">In my opinion, today\u2019s consensus failure in <a href=\"https:\/\/twitter.com\/hashtag\/Ethereum?src=hash&#038;ref_src=twsrc%5Etfw\">#Ethereum<\/a>\ud83e\udd84 shouldn\u2019t be underestimated and should be considered as the most serious issue Ethereum has faced since the DAO debacle 4 years ago. An investigation is in order.<\/p>\n<p>\u2014 Nikita Zhavoronkov (@nikzh) <a href=\"https:\/\/twitter.com\/nikzh\/status\/1326497038964502528?ref_src=twsrc%5Etfw\">November 11, 2020<\/a><\/p>\n<\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>A former Monero maintainer, Riccardo Spagni, confirms the rationale behind such actions.<\/p>\n<blockquote>\n<p>&#8220;We have secretly fixed bugs in Monero several times, fearing they could be exploited if disclosed. For example, that is how we acted in 2017,&#8221; Spagni commented, recalling the successful fix of a bug that could have allowed unlimited XMR coins.<\/p>\n<\/blockquote>\n<p>Geth developer Martin Holst Svende explained that older client versions contained consensus bugs.<\/p>\n<blockquote>\n<p>&#8220;The change introduced was actually targeted at fixing those problems. This is a reminder that node software must be kept up to date,&#8221; he wrote.<\/p>\n<\/blockquote>\n<blockquote class=\"twitter-tweet\">\n<p dir=\"ltr\" lang=\"en\">Older geth-versions contained consensus-flaw(s) which were hit today on mainnet. The &#8220;change introduced&#8221; was actually fixing those issue(s). This is a reminder to keep your node(s) up to date! <a href=\"https:\/\/t.co\/oZatRUgENS\">https:\/\/t.co\/oZatRUgENS<\/a><\/p>\n<p>\u2014 M H (((Swende))) (@mhswende) <a href=\"https:\/\/twitter.com\/mhswende\/status\/1326474816736677888?ref_src=twsrc%5Etfw\">November 11, 2020<\/a><\/p>\n<\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script>\n<\/p>\n<p>Analyst Larry Chermak of The Block, however, does not understand how such a situation became possible.<\/p>\n<blockquote>\n<p>&#8220;If this is the case, things are much worse than I thought. How can it be that the largest infrastructure provider did not know about a code change that could have led to a chain split? It\u2019s almost unbelievable.&#8221;<\/p>\n<\/blockquote>\n<p>Earlier on Wednesday, November 11, it was announced that Infura and other services <a href=\"https:\/\/forklog.com\/en\/news\/infura-a-leading-ethereum-infrastructure-provider-suffers-outages\">encountered<\/a> outages. This caused delays in ETH and ERC-20 token quote feeds, and some exchanges halted withdrawals.<\/p>\n<p>At the time of publication, developers were continuing to restore service functionality. By 15:00 UTC, the work had been completed.<\/p>\n<p>Subscribe to ForkLog news on Telegram: <a href=\"https:\/\/t.me\/forkloglive\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">ForkLog FEED<\/a> \u2014 the full news feed, <a href=\"https:\/\/telegram.me\/forklog\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">ForkLog<\/a> \u2014 the most important news and polls.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Outages at Infura, the leading provider of infrastructure solutions for the Ethereum network, are linked to consensus errors in older versions of the Geth client. Because part of the network had not updated to the latest version, Ethereum split into two chains at block 11234873.<\/p>\n","protected":false},"author":1,"featured_media":31612,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"select":"1","news_style_id":"","cryptorium_level":"","_short_excerpt_text":"","creation_source":"","_metatest_mainpost_news_update":false,"footnotes":""},"categories":[3],"tags":[46,1749,2022],"class_list":["post-31611","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news-and-analysis","tag-ethereum","tag-geth-go-ethereum-client","tag-infura"],"aioseo_notices":[],"amp_enabled":true,"views":"30","promo_type":"1","layout_type":"","short_excerpt":"","is_update":"","_links":{"self":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/31611","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/comments?post=31611"}],"version-history":[{"count":1,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/31611\/revisions"}],"predecessor-version":[{"id":31613,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/31611\/revisions\/31613"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media\/31612"}],"wp:attachment":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media?parent=31611"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/categories?post=31611"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/tags?post=31611"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}