Sirlibz
Infura, Ethereum infrastructure provider is currently facing a service disruption which has led to different exchanges shutting down Ethereum deport and withdrawal along with ERC-20 tokens. The disruption of service caused delay in price feeds of ether (ETH) and it’s ERC-20 based tokens.
“We are currently experiencing a service outage for our Ethereum Mainnet API. Our on-call team is investigating and working to restore service functionality,” the Infura status page reads. The issue started today at 08:12 UTC.
Exchanges such as Bithumb and Binance have had to disable Eth and ERC-20 tokens on their platforms because of the service outrage.
CZ added that that are also investigating a possible Ethereum chain split at block 11234873
“Etherscan and Blockchair are showing two different chains and data after this block. We’re resolving now but have temporarily closed withdrawals,” said CZ.
Lead developer at Blockchair, Nikita Zhavoronkov gave an explanation to the chain spilt in a twitter thread. He clearly pointed out that Ethereum developers introduced a change in the code that led to the chain split starting from block 11234873 and since some service providers did not upgrade, they got stuck on a minority Chain.
Technically, that was an unannounced hard fork,” said Zhavoronkov. “Something similar happened to #Bitcoin 7 years ago when there was a database upgrade…Fix: upgrade geth and run debug.setHead(11234872).” Geth is a tool used to run a full Ethereum node on the system.
Infura has pointed out that it has identified the root cause and is fully ready to restore the service functionality back after bringing in more hands to help them.
Affected components include the Ethereum mainnet archive data, Mainnet filters, Mainnet logs, Mainnet Web socket JSON-RPC API and mainnet HTTPS JSON-RPC API. More work is currently going on and so far Infura said that the root cause was traced to several components within its infrastructure, these components were locked to an older version, a stable version of the Go-Ethereum client that encountered ” a critical consensus bug at block 11234873″.
