Advertisement
AD

Main navigation

Advertisement
AD

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’s Vitalik Buterin Wants to Create Annual “Rent” Fees

Advertisement
Tue, 27/03/2018 - 17:05
Ethereum’s Vitalik Buterin Wants to Create Annual “Rent” Fees
Cover image via U.Today
Read U.TODAY on
Google News

Ethereum co-founder Vitalik Buterin has made a controversial proposal to create a new fee for storing data on the Blockchain. Buterin’s proposal would require users to pay not only transaction fees, but would also require them to pay “rent” to preserve their data. Such a payment would ensure the network doesn’t get too clogged, making it expensive or even impossible to run a full node.

Advertisement

More fees?

For years, debate has raged in Bitcoin’s community over having too many fees. With limited block space available, users had to pay higher and higher fees to have their transactions included in a block. Many of Bitcoin’s proposed scaling solutions have focused on ultimately reducing those fees to a more reasonable level.

Ethereum’s Blockchain has been growing even more rapidly than Bitcoin’s, and Ethereum’s node operators are required to store a great deal of “state data” in RAM. State refers to data about each contract’s state, including user balances, that needs to be stored on each full node. Right now, running a full Ethereum node requires at least 5 GB of RAM to store state data. Buterin wants to add fees to the storage of such data in order to limit the size of Ethereum’s state to 500 GB.

Not much, but volatile

Buterin’s proposed rent fee is quite small. The average user would pay about 15 cents per year in storage fees, while contract owners would pay about $15 per year. Further advances in Ethereum’s technology, such as the possible implementation of sharding down the road, would reduce those fees by two orders of magnitude.

One concern that Buterin specifically addresses is the volatility inherent in such fees, which would actually be paid in Ether. Depending on the price of Ether at the time, fees could conceivably vary by thousands of percent during boom or bust cycles. Nonetheless, Buterin argues that such volatility would be less than is seen with transaction fees:

“One natural objection is: but won’t fixing the storage fees in ETH lead to unacceptable fees if ETH rises or falls too much? The answer is: this is quite possible, but transaction fees are not expected to be any less volatile.”

A
A
A

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