HelloEOS' Update

Node Upgrading

On July 11, EOSIO v1.0.9 was released. The technical team of HelloEOS updated the EOS node version to the mainnet 1.0.9. The EOSIO v1.0.9 has been introduced a very strict HTTP Host: header validation.

On July 13, EOSIO v1.0.10 was released. The technical team of HelloEOS updated the EOS node version to the mainnet 1.0.10. The latest version relaxed the host header validation based on the previous version and introduce the http-alias services for Docker.

Participation in the BPs Zoom Meeting

On July 12, the technical team of HelloEOS participated in the periodic BPs Zoom meeting. The main issues discussed in accordance with the agenda are as follows:

• Unmapped Token Resolution Step: Smart Contract is ready;
• BP treatments that violate the EOS Constitution;
• Zoom Conference link distribution method;
• Emergency response and disaster recovery;
• The smart contract update of the referendum.

Zicen, the Founder of HelloEOS, Attended the High-level Annual Meeting of China Internet Conference

On July 11, the CEO of Youzi Technology, Zicen was invited as a round-table guest to the periodic annual meeting of China Internet Conference, held in the China National Convention Center. Following the theme of "How the blockchain will reshape the value of the Internet", he discussed with colleagues working in the classical Internet on the future of the value Internet and how the blockchain can promote the development of traditional enterprises.

Weekly Hotspots & Major Events

The Community Should Take the Security of EOS Account Seriously

Last week, there were still a large number of users who reported their EOS were stolen. There are three main reasons:

• The private keys are generated by weak seeds, resulting in "rainbow" attacks.
• Some holders are unfamiliar with the EOS account mechanism. The hackers pretend to help the users register an EOS account so as to obtain their account permissions.
• The use of non-standard third-party account registration tools.
  Part of these stolen assets have been recovered with the help of the EOS Mandarin Arbitration Community (EMAC), third-party security agencies and wallet agencies.

On July 9, EMAC released the Classification of EOS Lost Property Cases and A Guide to Risk Prevention:

• For EOS holders whose private key is lost for undefined reasons, EMAC recommends that EOS holders should raise their awareness of private keys security. They must not give the private keys to other people or send their keys through social networks. The recommended way is to write them down on paper and save properly.
• For stolen cases which are caused by the modification of authority especially when a public key corresponds to multiple accounts, it is recommended that the victim must first call the police and promptly explains the reasons why the theft happens. Secondly, the victim should ask for help from the power of the media and the community to make good use of the pressure of public opinion; however, please note that do not blame anyone or any party when the case is inconclusive. At last, EMAC911 will cooperate with the holders who suffered such a currency loss incident and use the EOS transfer postscript and the OTCBTC mailbox to warn the hackers who stolen the EOS and notify them of their illegality to create pressure.
• For the cases of forgetting keys, losing keys and transfer mistakes, the EMAC911 team believe that these incidents are not included in the scope of arbitration. As to cases caused by transfer mistakes, it can be resolved through negotiation. As to cases of losing keys, it's recommended that holders should strengthen their awareness of accounts security to nip the risk in the bud.

On July 12, the blockchain security company Peckshield published a forewarning to some high-risk EOS accounts. They found that certain EOS accounts are readily vulnerable to being compromised and the corresponding digital assets are seriously under the risk of being stolen. The essence of the risk is caused by an improper use of third-party EOS key-pair generation tools. With user-provided seeds, these tools greatly facilitate users to generate their EOS key pairs. Unfortunately, if a simple seed is chosen (by the user) and allowed (by the tool), the generated keys might be exposed and exploited by launching the rainbow table attack (or dictionary attack)
Peckshield's security staff has been customized a set of crisis solutions for this:

• It's planned to reveal the details of the cases that the assets have been stolen because of weak seed phrases. The EOS community users are suggested to strengthen security awareness and avoid using blank or weak seed pairs.
• Peckshield has launched a public service dubbed EOSRescuer (peckshield.com/eosrescuer). Every EOS holder is encouraged to check whether her account is in danger or not by one-click access.
• To rescue these high-risk EOS accounts that are vulnerable to rainbow attacks, Peckshield created a secure EOS account, and made a makeshift arrangement by choosing to transfer the EOS balances from vulnerable accounts to this secure one. They will return transferred EOS balances back to original users (after verifying their authentic account ownerships) in a transparent and verifiable way. They also claimed that the entire process is transparent and free, and is subject to third-party media inquiry or audit.

In addition, the EOS wallet TokenPocket also published an alert, they cooperated with the White Mozi Security Labs (security technology supporter of the TP wallet) to analyze these stolen incidents and found that multiple EOS accounts were in a high-risk. TokenPocket made an urgent decision to change the authority of these accounts with weak seeds. At present, this batch of accounts has been transferred to an account with a secure private key. The holders of these accounts can contact TokenPocket to reclaim their property. The users must provide necessary proof of ownership of the EOS account, such as transaction records.

HelloEOS hereby remind all the EOS holders that:
Before registering and using the EOS account, please figure out the working mechanism of the EOS account, strenghthen security awareness and skills, and save properly the key words, seed phrases and other important information.

The Discussion on RAM Is Continuing

Last week, the price of EOS RAM kept falling back, but the discussion related to RAM is continuing.

On July 9, BM mentioned in the Telegram group that RAM will incrementally increase, but it is not good to straightly increase by only one time. He said that DRAM is to fix the RAM trade craziness and absorb some speculation demand. He mentioned that allowing shorting RAM will lower speculative peeks.

On July 11 at 8:06, BM quit the Telegram group "EOS Ram" where he recently discussed the topic on RAM with EOS users. The last sentence he said is, "Goodbye all. So much tolerance for fraud, lies and misrepresentation in this chat."

On July 12, BM appeared in the group consisting of EOS BPs and discussed the release ratio of RAM dilation. He indicated that:
When the community decide to increase RAM or change the RAM release ratio, they need to balance between the two factors：

• If it is sustainable in technology.
• If it is sustainable in economic development for users.

Some BPs believed that the decision was too subjective. BM replied, things that can't be measured by code cannot make up an objective future. Other BPs proposed to stop waiting for any program or feature update of Block.one and implement community voting.

On July 12, BM released a new article:

• He suggested the BPs immediately starting growing the RAM at the rate of 64GB per year (1 KB per block). If prices remain too high and/or testing reveals that the RAM can sustain a faster growth rate, then this number can be adjusted as-needed by the community.
• The minimum RAM requirement of account creation will be reduced. This update will be ready by July 31st.
• Block.one will be able to offer a free EOS account to users of their iOS wallet.

In addition, due to the increase in the EOS RAM transaction volume, the transaction fee has caused EOS to enter into a deflationary situation. According to the data of EOS Cafe's statistics, as of July 9, there are 4.58 million EOS in the eosio.ram account. The fee rate of buying and selling is only 0.5% respectively. But there are nearly 1.33 million EOS in the eosio.ramfee account, which is twice as high as the reward of 658,000 EOS issued to the BPs.

Because of the rising price of EOS RAM, the account registration threshold has risen. Many wallets now promote a flash account registration for free. Except for the previous cooperation between HelloEOS and Cobo Wallet to provide 1,500 free registration account, HelloEOS will once again, along with EOS LIVE APP, in the coming days to send out free registration quota. Please following on HelloEOS' WeChat public account and Knowledge Planet for the update.

BM Denied Any Attack Against the Ethereum Network

On July 15, the researcher Justo of Ethereum accused EOS of suspiciously manipulating the "attack" against the Ethereum network: creating congestion in Ethereum network by spamming passes.

At present, the transaction fee of Ethereum is as high as US$1. At the end of last year, even the extreme congestion of the Ethereum network caused by CryptoKitties did not cause the transaction fee to reach the current peak. There are no obvious issuers behind these passes, or there is no website to support them. Even if there exists a website, the passes are shoddily done in just a few hours. He pointed out that this is not just his personal opinion. Many other famous Ethereum developers also have this suspicion. BM then responded in the Telegram group and denied the accusation. He said that Block.one would not be so stupid to abuse its resources to attack Ethereum, because "only a CryptoKitties game can make Ethereum congest." He mentioned that this move is unwise. There are "smarter, cheaper and more efficient ways to break Ethereum network."

EOS Fixes 42 Bugs within 5 Weeks and Rewards the Hackers with about US$35 Million

Last week, DailyHodl reported that 42 EOS network vulnerabilities have been fixed since EOS announced the Bugs Reward Program in early June. Hackers have received $348,000 in rewards. The rewards range of the major vulnerabilities provided by EOS is from $5,000 to $10,000.

The Starteos Team Bid for the Third Short Account Name "io" in EOS Eco

On July 9 at 17:58:57, the Starteos team successfully bid for the short account name "io" in EOS Eco with 90,088 EOS. Prior to this, they had successfully shot two short account names "EOS" and "com" at 50,000 and 150,000 EOS prices respectively.

However, it was also found last week that some speculators attempted to defraud the users of their EOS by pretending to be able to register the ".eos" and ".com" account names. In response to this, Starteos claimed that the registration of account names ending in ".eos" and ".com" has not been open yet, and they never charged any users the registration fees.
HelloEOS reminds the community users that in the early phase of the EOS mainnet, the community information is in a great mess. Everyone should be vigilant and obtain EOS-related information from trusted channels.

Everipedia Completed the Airdrop

The Everipedia token is called IQ, with the aim to build a web encyclopedia on EOS. The IQ Token completed its airdrop last week. The Chaince and Bitfinex exchanges opened the IQ/EOS trading pair.

Sam Kazemian, president and co-founder of Everipedia, mentioned in the interview with IMEOS that:

• There is always a way to deal with potential politically sensitive issues when entering the Chinese market.
• At the system level, RAM should be designed to serve the real use, not for crazy speculation.
• By learning from Steem and other pioneers, they will eventually design a system which is decentralized.
• Everipedia wants to be a source of truth in the chain and a knowledge basement that Dapps can rely on.

=End=

HelloEOS Community
HelloEOS BP
HelloEOS Weibo
HelloEOS Wechat：hello-eos
HelloEOS Twitter
HelloEOS Telegram