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 2.0 Developer Revealed the Potential ETH 2.0 Launch Date
In the recent episode of Into The Ether podcast by EthHub.Io, Paul Hauner, who is contributing to the LightHouse ETH2 client written in Rust, discussed the future design of Ethereum 2.0 network as well as the prospects of its launch.
Ethereum 2.0: More Decentralized, More Secure, More Speedy
Mr. Hauner revealed that libp2p will be the main technological stack for Ethereum 2.0 instead of devp2p. Despite being very young, libp2p is one of the cutting-edge toolkits for decentralized systems like Polkadot, Substrate or IPFS-based projects.
A new Into the Ether is live!
— eric.eth (@econoar) January 8, 2020
This week I talk with @paulhauner who is helping build the eth2 client Lighthouse at @sigp_io. We discuss eth2, their 16,000 validator testnet, hardware requirements for stakers, staking UX and what's left before launch.https://t.co/047yTtIYK6
With respect to the security, Mr. Hauner explained the concept of an 'attestation'. Acting as certificates of system status in a particular moment, such attestations will be included into blocks of the new Ethereum. It will upgrade the attack-resistance of the whole system and reduce the ability of malicious validators to corrupt the consensus.
Speaking on the progress of ETH2 public testnet, Mr. Hauner revealed that 16 000 users are validating its transactions now. The overall speed of the new system will allow it to add one block to Ethereum orders of magnitude faster than now when it takes 10-12 secs.
When PoS?
Typically, developers avoid sharing the detailed time frameworks of the products under development. For Ethereum 2.0 such a disclosure has already caused heated debates in Ethereum Foundation.
Nevertheless, Mr. Hauner told the audience that this week the new version of specifications (network rules) will be published. After that, the developers will spend 3-4 weeks preparing the multi-client testnet. So, Mr. Hauner concluded:
In terms of when can we expect to see mainnet, (...), perhaps like a five or six months, maybe seven. A kind of mid-year range.
With that said, we should get prepared for the mainnet launch of Ethereum 2.0 by the start of Q3, 2020.
Do you belive that EF can achieve such a milestine in time? Tell us your opinion in Comments!