Main navigation

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: Increased Block Size for Unmatched Speed

Advertisement
Fri, 1/11/2019 - 14:43
Ethereum 2.0: Increased Block Size for Unmatched Speed
Cover image via www.123rf.com
Read U.TODAY on
Google News

While it's still unclear whether Ethereum 2.0 will be delivered, developers keep leaking some aspects of the future blockchain architecture. Danny Ryan, one of the most well-known advocates of next-generation Ethereum, shared the last work-in-progress proposal.

Block Size Increased Drastically

From the early days of blockchain technology, the size of one block seemed to be the "Holy Grail" of blockchain scalability. Arguments about the block size resulted in several of hard and soft forks (Bitcoin Cash, Bitcoin Classic, SegWit, etc.). With Ethereum 1.0, the size of block could vary depending on the network activity.

With Ethereum 2.0, every shard (part of blockchain) has a target block size. According to the new proposal, the speed will be 128k instead of the planned 16k. The will result not only in high speed and scalability (today one block size is 23.9 kB), but also compatibility with cutting-edge, side-project scalability solutions. Recent tests on the existing Ethereum network showed a significant increase of 1 MB/s capacity with unmatched TPS.

Rescheduled Shards Design

To guarantee this speed without sacrificing safety and decentralization, all of the shards at each slot will be cross-linked. This will simplify communication between the shards and result in a much better and simpler developer/user experience.

 

Article image
Image by: https://blog.ethereum.org/2019/10/31/eth2-quick-update-no-2/

To make this scheme work, the total shard quantity has to be reduced from 1024 to 64, with the intent of scaling up the number of shards over time (approximately 10 years).

Ethereum 2.0 is an update of the Ethereum network that is focused on speed and scalability. It will include the concept of sharding (full network will be divided into autonomous parts) and switch from Proof-of-Work to a Proof-of-Stake consensus.

What do you think? Is there any possibility that this scheme will result in a severe over-centralization? Don't hesitate to share your opinion with us!

Related articles

Advertisement
TopCryptoNewsinYourMailbox
TopCryptoNewsinYourMailbox
Advertisement
Advertisement

Recommended articles

Latest Press Releases

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

Popular articles

Advertisement
AD