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)
EOS Users Concerned About Potential RAM Collapse
Participants in the EOS community expressed their concerns about the new airdrop. Its organizers ask EOSians to "mine" their token by sending some EOS to their contract. However, the thing about this token is that each coin occupies 1KB of RAM of the sender's EOS account. Therefore, the project attempts to tokenize the EOS RAM in a similar manner to the one that was recently tried with the CPU.
Yuri MolchanSimple but Shady Scheme
The scheme looks quite ingenious. Those who are interested in the airdrop send some fractals of EOS to the project's "mining address". This address then sends the participants some project tokens that occupy 1 KB of RAM of the sender's account. The organizers warn the following:
Make sure you have enough memory on your account,
Advertisement
One account can participate up to 100 times, or just let the project lend 0.1 MB.
In the next stage of the scheme, the EOS account holder sends tokens to the project's address in numerous iterations. During this process, new tokens are to be mined, in which some of them will be destroyed to bootstrap this process. In short, boosting the RAM price by rapid demand growth is the economic basis of the model.
Could the Consequences be Disastrous?
Despite the fact that the interest in this airdrop is not there, some EOS users and analysts warn of the possible formidable effects on the network. The following was said:
One of the most common things to do in EOS is to airdop tokens. (...) But if the price of RAM were to go up dramatically, this will make airdrops prohibitively expensive. Users would have have to fork out EOS to purchase additional RAM.
Half a year ago, the EOS community managed to address the issue of RAM manipulations very quickly. During the recent and infamous CPU congestion, some users suggested dumping the price of the airdropped token in order to undermine its tokenomics.
At the time, the documentation of new "RAM-speculation" project contains only one GitHub repository developed by one contributor with a newbie account. The token is only traded on the EOS-based DEX with statistics unknown to CoinMarketCap.
Have your ever participated in airdrops? What is your maximum ROI? Tell your story on Twitter!
Related articles
Yuri Molchan
Tomiwabold Olajide
Dan Burgin