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)
BCH Hash War Descends to Dirty Tactics, Clashing with Nakamoto’s True Vision
Since the 15th of November, an intense hashwar has been raging between two sides of the Bitcoin Cash blockchain following its hard fork. On one side is a man who has claimed to be the creator of Bitcoin — Satoshi Nakamoto — Craig Wright, and the other is a man who calls himself Bitcoin Jesus, Roger Ver.
The hash war has degenerated to a point where some dirty tactics have been used and have come to light. But most concerning is the hypocrisy of the BCH proponents who have enacted the tactics — and the hard fork in general — as it is clear this mess would never have been the intention of Nakamoto when he created Bitcoin 10 years ago.
Bitcoin Cash ABC had a hash burst straight after the fork, but it has emerged via Jimmy Nguyen, the CEO of nChain, that the burst was actually rented or subsidized from the BTC network.
These tactics are clearly not for the benefit of the cryptocurrency ecosystem, with the total market cap tanking soon after this petty hash war kicked off. Furthermore, Bitcoin Cash was hard forked off of the original Bitcoin chain under the guise of maintaining Nakamoto’s vision of a electronic peer-to-peer cash system — yet this latest feud is far from that.
The exposed hash burst
Taking a look at the graph showing the competing networks that forked off the BCH network, it is clear that BCH AC spiked earlier and harder. This hash burst has since been exposed, though.
This hash burst was actually rented — subsidised — by the BTC network “in order to artificially boost the support for Bitcoin Cash ABC far higher than it had ever been in the days and weeks leading up to the hard fork,” according to Nguyen.
This is clearly a subversive tactic in a war of hash for this chain, and is neither ethical or the right way in which to win this battle. It is also not conducive to what Nakamoto envisioned for blockchain and Bitcoin — something that is supposedly very important to the BCH believers.
Nguyen says it is hypocrisy to move hash for a day or two from the rival network that most of the community do not like and use that to claim victory.
“The whole reason that such hash was available on the BTC network to move onto BCH is because the people who should have fought Bitcoin Core did not, and splintered off to create the Bitcoin Cash network, and allowed BTC to continue on. That’s perfectly fine. But now they’re borrowing hash, renting it, subsidizing it from the very network they so vehemently oppose many of them to try and claim a victory on the BCH network.”
Testing the Nakamoto Consensus
In Bitcoin’s white paper, it states that the cryptocurrency should be a cash-like system, which is a fact the BCH believers hold onto, but the Nakamoto Consensus also states there was supposed to be only one Bitcoin network.
Nguyen adds: “Satoshi Nakamoto could not have envisioned, at the time the white paper was written, that there was going to be some splintered-off network using the same hash algorithm. And with the idea of one CPU equals one vote, or miner hash power equals the vote, it was designed.”
“I’m sure most logical people can agree with it to recognize that the people who have an ongoing continuous invested interest in the network are the ones that should vote on a rule set.”
A philosophical war
While this hard fork started out as a scheduled maintenance, it quickly degraded into a battle between big personalities within a blockchain that was already controversial and hostile. The decisions to go separate ways at this juncture cannot be too surprising, but the outcome of this war will probably not be positive or conducive to a betterment of the cryptocurrency space.
Related articles
Godfrey Benjamin
Arman Shirinyan
Vladislav Sopov
Dan Burgin