The first activity of the national roadshow themed on "EOS and its Friends" was successfully convened in Hangzhou, China on August 4. Around 200 participants attended this meetup held by HelloEOS and its EOS community partners.
Zicen from HelloEOS expressed that the series of meetups of "EOS and its Friends" will provide a open stage for EOS partners to show themselves. This meetup invited the Yangtze Delta Region Institute of Tsinghua University, Zhejiang to hold cooperatively and gathered EOS fellows including Starteos, EOSAsia, AntPool, imToken, lMEOS, EOSPark, Chiance, SuperONE to share on the meeting.
The national roadshow will tour other major cities across China, including Beijing, Shanghai, Guangzhou, Shenzhen, Chengdu and Xiamen.
On the evening of August 3 (Beijing time), HelloEOS took part in the daily zoom meeting held by EOS Mandarin Arbitration Community (EMAC), along with other global nodes, such as EOS NewYork and EOS Canada. The meeting focused on the responsibilities that should be taken by EMAC and publicized the details of the EOS token recovery processed by the EMAC 911 team.
Daniel Larimer suggested to introduce a new resource token named REX for the use of resource renting trade, as well as a trade pair, EOS/SEOS by applying Bancor Mechanism and a service fee charge of 0.5%. SEOS stands for Staked EOS.
Due to the fact that there were no particular issues to be discussed and presented to the agenda, BPs agreed to cancel the regular weekly meeting since last week. They also agreed on the proposal to organize a meeting once an important event emerged. Any important agenda would be posted on the Telegram mainnet group.
On August 1, the proposal of EOS Token contract upgrade was approved, so that the RAM required for EOS transfer was reduced. Because two voting nodes were not qualified as the super nodes during the voting period, the proposal was finally accepted by 17 votes, and HelloEOS voted in favor.
The 360 Vulcan team reported that a loophole, which can cause an overflow risk in numerical calculations, exists in the "asset class" of the base layer of EOS smart contract. It's related to the root cause that leads to the overflow attack of the EOS Fomo3D Werewolves game. On July 25, the SlowMist security team forewarned this attack. The security team of SlowMist and the 360 Vulcan team have audited the source code of the contract and found that the asset calculation have an overflow vulnerability.
If this asset class is used in your EOS smart contract, it is recommended that you update the corresponding code and recompile your contract after the official patch is released to eliminate security risks. The 360 Vulcan team has already reported the loophole to the EOS official vulnerability platform.
Demux draws inspiration from Facebook's Flux Architecture pattern and Redux, creating a back-end infrastructure pattern for sourcing blockchain events in order to deterministically update queryable databases for applications built on the EOSIO blockchain.
Block.one has set up a developer portal that introduces EOSIO features and a series of DApp-developed tutorials and tools for developers such as C/C++ function introduction, contract deployment, command line operations, tool indexing, random numbers generating and so on.
Following the Block.one CEO Brendan Blumer, Daniel Larimer also clearly stated in the EOS Telegram group that he believes EOS' 4% inflation incentive should be cancelled, mainly because he worries that the 4% inflation incentive will be abusedly used. He will also draft an article to explain the reasons in detail. Previously, on July 30, BB issued a proposal to cancel the 4% inflation incentives that flowed into the WPS (Worker Proposal System) and distribute it to EOS voters as online transaction fees. It will not only offset the inflation costs of running the network, but also introduce more services.
A week ago, Meito Blockchain Lab identified and officially informed EOSIO of a security loophole where EOS malicious contracts can misappropriate users' RAM. The Lab has discussed into detail with the official team on this loophole. After a week of communication, the official team has fully understood the hazard of the loophole and replied: "Code has not yet been written and there is no schedule. Watch future release notes."
In order to avoid malicious attacking during this waiting period, Meitu Blockchain Lab decided to publish the details of the loophole for further community research so as to facilitate self-examination and defense. EOS contracts can trigger other contracts through the require_recipient code. The design of such a mechanism provides great convenience for contract developers, but it also brings new problems. When a user makes a transfer to a contract, it's probable that the contract can consume the user's RAM without the user's knowledge.
=END=
Block Producer Account Name：helloeoscnbp
Location: China
HelloEOS Community
HelloEOS BP
HelloEOS Weibo
HelloEOS Wechat：hello-eos
HelloEOS Twitter
HelloEOS Telegram
