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)
Litecoin’s Implementation of MimbleWimble: Details Disclosed by Dev
Shortly after the hot discussion on the MimbleWimble (MW) protocol vulnerability, David Burkett, the lead developer of Grin (native blockchain behind MW), disclosed some amazing details that brings MimbleWimble to Litecoin.
From Funding to Implementation
Recently, the developer announced that the Litecoin Foundation decided to fund his efforts at implementing the MW extension block. Thus, we can conclude that Litecoin's protocol governance is focused on implementing its new privacy protocol.
I'll be posting monthly status updates detailing progress on the LTC MW EB (YAY acronyms). This is geared toward those interested in LTC development, but will also talk a lot about Grin++ changes, so it may be interesting to Grinners as well. https://t.co/hTpUbWSPI6
— David Burkett ツ (@DavidBurkett38) December 1, 2019
Widely criticized for the lack of anonymity in MimbleWimble, the developers have now made their technology work with TOR. MW requires interacting with the receiver in order to finalize a transaction collaboratively. By using TOR for that interaction, the protocol can use familiar-looking addresses, a simpler set-up, and improved privacy.
Yuri MolchanCoinJoin: Single Exchange Point for Speed and Privacy
Mr. Burkett also reconsidered some aspects of the transactions broadcasting in Litecoin's mainnet. In order to increase speed without sacrificing privacy, every MimbleWimble transaction can now be pre-broadcasted to the CoinJoin server. As a result, users in some cases can avoid latency and transaction denials.
As one more step to its release, Mr. Burkett re-designed the Grin++ codebase in a way that allows LTC to reuse Grin++ with minimal modifications. Therefore, the implementation of MW into Litecoin will have a barely seamless design.
MimbleWimble protocol is a kind of side-chain extension that can be used for the unmatched level of privacy in some major blockchains.
What do you think? Will the release of MimbleWimble in Litecoin somehow affect the price of this asset? Share your opinion on Twitter.
Related articles
Godfrey Benjamin
Gamza Khanzadaev
Dan Burgin