EOS is usable again, thank god.

EOS developers finnally get the CPU jamming problem resolved by activating proposal below:

https://github.com/eosrio/proposals/blob/master/updateparams.md

Since the mainnet launch the global blockchain parameters were left as default, and now with a recent increase of the usage, the users noticed that the system contract is triggering the CPU congestion mode too early. As soon as a block hits 10% of the total 200ms of CPU time allowed per block, the CPU allocation algorithm switches to the congestion mode and every user is left with his share of the remaining allocation based on their stake in proportion to the whole network stake. What ended up happening is that while the actual CPU usage of the validators is very low, the CPU price became higher.

It seems like the sudden surge of network usage has triggered the self-protection mechanism too early and we can very much relate this phenomena to the rising stars, Betdice and EOSBet, the biggest twin dapps in EOS network.

Interestingly, the solution in the proposal was very alike with our Steem's RC disaster:

This proposal aims to change the current value for target_block_cpu_usage_pct from 1000 (10%) to 2000 (20%)

Not enough RC? Multiply the RC! Not enough CPU? Double the CPU! Problem solving has never been this easy.

Not bad as a stress test

While the hot gambling dapps get so popular that the crazy trading volume paralyzed the whole network for a few days, this is actually healthy for the long term stability.

Take a look at the difference of CPU price before and after the CPU congestion incident:

Screenshots from EOS Resoource Planner

$2.733/ms/day then vs $0.014/ms/day now. EOS network back in business with silkly smooth transaction once again. Good job devs!

---

Posted from my blog with SteemPress : https://fr3eze.vornix.blog/eos-is-usable-again-thank-god/

---