Main navigation

Advertisement

Error message

Warning: Undefined array key 0 in amp_entity_view_alter() (line 156 of modules/contrib/amp/amp.module).
amp_entity_view_alter(Array, Object, Object) (Line: 545)
Drupal\Core\Extension\ModuleHandler->alter('node_view', Array, Object, Object) (Line: 304)
Drupal\Core\Entity\EntityViewBuilder->buildMultiple(Array) (Line: 238)
Drupal\Core\Entity\EntityViewBuilder->build(Array)
call_user_func_array(Array, Array) (Line: 111)
Drupal\Core\Render\Renderer->doTrustedCallback(Array, Array, 'Render #pre_render callbacks must be methods of a class that implements \Drupal\Core\Security\TrustedCallbackInterface or be an anonymous function. The callback was %s. See https://www.drupal.org/node/2966725', 'exception', 'Drupal\Core\Render\Element\RenderCallbackInterface') (Line: 788)
Drupal\Core\Render\Renderer->doCallback('#pre_render', Array, Array) (Line: 377)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array, ) (Line: 238)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 583)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 239)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare(Array, Object, Object) (Line: 128)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse(Array, Object, Object) (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray(Object, 'kernel.view', Object)
call_user_func(Array, Object, 'kernel.view', Object) (Line: 111)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object, 'kernel.view') (Line: 187)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 191)
Drupal\page_cache\StackMiddleware\PageCache->fetch(Object, 1, 1) (Line: 128)
Drupal\page_cache\StackMiddleware\PageCache->lookup(Object, 1, 1) (Line: 82)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object, 1, 1) (Line: 704)
Drupal\Core\DrupalKernel->handle(Object) (Line: 18)

Ethereum Users Should Update Their Nodes for New Hard Fork

Mon, 23/12/2019 - 14:57
Shortly after the Ethereum Istanbul Hard Fork was implemented on the mainnet, node operators should be prepared for the Muir Glacier, which will occur on January 1!
Advertisement
Ethereum Users Should Update Their Nodes for New Hard Fork
Cover image via 123rf.com
Read U.TODAY on
Google News
Advertisement

Hudson Jameson, Core Developer at the Ethereum Foundation, published today instructions for Ethereum node operators to make preparations for the Muir Glacier update.

Micro Hard Fork?

This hard fork is unusual. Unlike Istanbul or Constantinople, which were system-wide upgrades, this hard fork consists of only one change to the blockchain consensus. The Muir Glacier hard fork will be implemented on January 1, 2020 for block number 9200000.

You Might Also Like

The upcoming update is required to customize the block time (the time it takes for one block to be validated by the whole network). In turn, this is needed to prevent the inevitable degradation in the usability of Ethereum due to wait times for confirming transactions and decentralized applications.

Advertisement

It's not the first time that such an update was implemented as two previous updates - one was activated in 2017 and in the other was during the early days of 2019. This customization delay lead to transaction congestion on the Ethereum network, or Ice Age, for approximately 611 days.

You Might Also Like

What Should We Do?

Like with any previous update, owners holding onto Ethereum coins (ETH, Ethers) in their wallets, exchanges, or ledgers do not need to do anything unless informed to take additional steps by their respective exchange or wallet service.

Node operators should upgrade their software (clients) to the latest version. The full list of Parity, Geth, and some minor implementations have been published by the Ethereum Foundation. It should be mentioned that Ethereum's Java client will not be supported anymore, so Besu is the only active Ethereum implementation written in Java.

Even those who missed the Istanbul Hard Fork can upgrade their nodes to Muir Glacier directly.

Have you ever operated on an Ethereum node? Describe your experience in the Comments Section below.

Advertisement
Advertisement
Subscribe to daily newsletter

Recommended articles

Latest Press Releases

Our social media
There's a lot to see there, too

Popular articles