Recently, EOS, a public-chain project developed by BM, has encountered unprecedented troubles. Its main network has been blocked into dogs due to the new air-drop project EIDOS, which was founded by Aiden Pearce, the former founder of ANU, and a large number of users have been Forced to wait.
According to data provided by DAppTotal.com, the number of transactions per day for the EOS main network was 19.38 million, and the number of transactions for a single DApp of EIDOS reached 18.76 million, accounting for 96% of the total transaction volume.
To this end, the digital asset exchange Coinbase also issued a reminder , and even media reports that "EOS is dead."
- How will the public chain break the game in 2020? The project party answered these 3 questions
- 2019 blockchain trend report: The industrial blockchain valuation model is announced, and the traditional fund giants have entered the market.
- Bitcoin Investment God: How to quickly filter out 1% of valuable tokens
- From quantum computing to blockchain: frontiers, trends, and challenges
- Babbitt Column | Neglected Blockchain Node Operations: The Hidden Value of Mining
- Research Report | The Innovative Path for Institutional Investors - How to Participate and Invest in Blockchain Assets
(Image courtesy of pexels.com)
It can be seen that the "DoS" attack designed by Aiden Pearce is very successful, and it has been very effective against the EOS network.
To this end, the EOS community is also very helpless, and Tal Muskal, chief technology officer from LiquidApps, has proposed a very interesting solution, which he believes can effectively solve the dilemma faced by EOS.
It is reported that this program is called "EOS resource market immune system using rest proof".
To put it simply, it is to use "airdrops" against "airdrops."
The following is a specific explanation of the program:
In the past few weeks, the EOS community has witnessed a new token “mining” mechanism that has caused the EOS main network to be blocked.
The user transfers the EOS token to an EIDOS smart contract, and then gets the EOS token while getting the EOS token back.
Currently, EIDOS tokens have been traded on multiple exchanges, and those participants have provided “fuels” and prompted more EOS tokens to be transferred to EIDOS smart contracts.
This surge in activity has led to extremely tight CPU resources for EOS, and "regular" transactions require a large amount of EOS to be executed.
This EIDOS token is a good example of a "wasted value" token. Although it has no real value, the support of exchange users has provided more "firepower" for this congested war. We believe this is a bubble, someone must fuel its existence (even if they don't realize it themselves), and because of the negative value of the bubble (network congestion), it cannot be sustained for a long time.
The "immune system" of the EOS resource market, using bubbles to fight against bubbles
This "wasted value" token strengthens the behavior of users wasting valuable resources. In the case of EIDOS, it will cause CPU resources to be wasted. The community asked us to design a solution. To this end, we came up with a solution: the way to fight this bubble is to create a confrontational bubble that will become the “immune system” of the EOS resource market.
Compared to EIDOS, which relies on CPU usage for mining, this immune system will have its own token, which will compensate those who do not use its available CPU. If you wish, you can call it a proof of rest (Proof- of-Rest).
If users can prove that they own the CPU and do not choose to waste, they will receive "immunity tokens" as a reward. In other words, the user will be rewarded for their free CPU.
This "immunity token" will have the opposite effect of "wasting value" tokens (EIDOS in our case), eventually reversing the negative consequences of "wasting value" tokens. In addition, this new token has a positive sum value that is used to maintain the health of the chain and balance CPU requirements.
How to achieve technically?
This solution does not require changes to the underlying layer of EOS and does not require BP's cooperation.
We envision the operation of the “immune token” smart contract as follows:
Each time an EOS token is sent to this contract, it will call LiquidOracles to check the number of CPUs that the user has not used since the last transmission/claim (LiquidOracle DSP will aggregate this data using its local EOS node).
The contract will send the EOS along with the new "immunity token" to the sender, which is proportional to the total amount of CPU unused in the sender's account.
And to break the current EIDOS bubble, this "immunity token" also needs an active liquidity market, and its price and liquidity depth will rival that of EIDOS (at least for the time being).
It is reported that this program has been supported by some people, but whether it will be implemented, it also needs to see whether EIDOS can continue DoS attacks, and the recent EIDOS attacks will undoubtedly reveal the existence of EOS design. Some questions.