EOS Store Block Producer Report

in roadmap •  6 months ago

1. Public website URL and at least one social media account (all social media links offered by candidate will be shared in report)

2. Links to the following ID information

  • Official block producer candidate: EOS Store
  • Location of company headquarters: Beijing, China
  • Expected location of servers: Tokyo, Taiwan
  • Type of servers: Cloud


Lu Haifeng  (CEO of EOS Store)

Mr. Lu, graduating from School of Economics and Management of Tsinghua University with finance MBA as his major, invested EOS token in its early stages. He is one of the first entrepreneurs based in Garage Cafe, an enthusiast of block chain technology and EOS believer holding over 7-digit  EOS token.

Simon ( CTO of EOS Store)

Simon has full participation in the R&D and architecture of BP level storage systems, cloud computing platforms and e-commerce system during his 9 years of experience in Internet area. He has dedicated himself to micro service, container clusters and CI/CD for a long time. Proficient in 5 more programming languages, Simon has built a micro e-commerce system by himself. Besides, he also has done more research on artificial intelligence.Now, Simon devotes himself into the blockchain technology and the subversive revolution it will bring about.

JJ   (COO of EOS Store)

As an early supporter of EOS, JJ worked in investment & Internet areas for 5 years. She was the Chinese representative of a EB5 project responsible for the recruitment of its second phase in mainland China. As a senior marketing consultant of MLN Singapore, JJ once successfully helped dozens of entrepreneurs find perfect resource match. Besides, she also worked for Red Castle as its CMO, promoting the communication between China’s startup teams and startupers from such six countries as the UK, the US and Chile.

3. Estimate of technical specifications and total expenditure for resources by June 3, 2018

As a blockchain system supporting very high TPS, EOS nodes require strong hardware and network bandwidth, and need to ensure that services are highly available; In order to prevent hackers from malicious attacks, nodes need strict security protection; In addition, high-level monitoring systems as well as operation and maintenance teams are required to ensure the stable operation of the system. As the whole network traffic of EOS increases gradually, the node hardware and related configurations need to be upgraded smoothly. As EOS BPC, we will provide the main-network node and test-network node. 
As a whole, we provide “one active plus two standbys” deployment mode and divide the hardware configuration into multiple phases. When the EOS network traffic reaches 70% of the capacity of the master node in the first phase, we will migrate to the second phase, and then the third and the fourth phase accordingly.

The first phase
Master node (AWS x1e.16xlarge) vCPU:64  Memory:1Tb   Bandwidth:10Gb  Storage:AWS EFS 100Tb  Location:Japan
Two standby nodes(AWS x1e.16xlarge) vCPU:64  Memory:1Tb   Bandwidth:10Gb  Storage:AWS EFS 100Tb  Location:Japan, Singapore
The second phase
Master node (AWS x1e.32xlarge) vCPU:128  Memory:2Tb   Bandwidth:25Gb  Storage:AWS EFS 200Tb  Location:Japan
Two standby nodes(AWS x1e.32xlarge) vCPU:128  Memory:2Tb   Bandwidth:25Gb  Storage:AWS EFS 200Tb  Location:Japan, Singapore
The configuration of test node  vCPU:16  Memory:128G Bandwidth:1Gb  Storage:AWS EFS 10Tb  Location:Japan
Monitoring, Operating and maintaining
Use AWS's monitoring service and set alarm thresholds. If there is any abnormality,the operation and maintenance teams will be notified to perform maintenance via the social system; In addition, automatic processing mechanism for service fault is required to be developed, thus to promising the high availability of the service.
Network Security Select strict safety precautions,such as using DDoS attack protection, WAF, traffic cleaning, key management, risk control, penetration testing;The most stringent security measures are adopted at the operating system level and the cloud gateway level.
Total budget
About 600k$ per year.

4. Estimated scaling plan for hardware after June 3, 2018

As mentioned above,the hardware configuration takes multiple phases. Each phase has a master node and two standby nodes.From the previous phase to the next phase,we will start three new nodes at first. When these nodes have synchronized all the data and can run stably, they will become the working nodes. At this time, the three nodes in the previous phase will be deleted and the smooth migration will be completed. 

5. Community benefit project outline, only for projects expected to be public by June 3, 2018

Every member of Eos. EosStore community is EOS holder. To provide these community members with better services, we share EOS-related information and hold EOS events regularly. Meanwhile, to better serve app developers, we have set up EOS college to provide technical training and exchange. EOS holders now can access the community by voting for us and receive some exclusive benefits such as votig, technical development training and project investment in the community.  
Surrounding the community, store and fund, the future development of EOS ecosystem is determined by each community member based on consensus, and we believe that EOS ecosystem will become better based on the shared vision and consensus.  

6. Listing of Telegram and node names for community testnet participation.

Node name: eos.store Telegram: https://t.me/StoreEos Textnet: node add is, http port is 8888, p2p port is 9876 

7. Block Producer Candidate Roadmap on values, community project timeline, finances, transparency, or any other topic the candidate deems important. Please show the direction and future of your candidacy in a Steem post for the community. Any roadmap labeled as such by the block producer candidate will earn a check mark - community gauges the effort.  

EosStore has made a variety of technology preparation and joined EOS Force testnet before building its testnet on AWS cloud host and performing DDoS test. A high availability proposal and daemons have been written before a stress test. Meanwhile, EosStore has formulate its operation and maintenance plan to ensure safely stable operation of BP. Besides, we participated in such activities as 2018 Global Graphene Developer Conference and built EosStore community. 2 Q&M and 4 R&D have been configured to set up system respectively and to implement various kinds of tests. Next, EosStore will develop DApp and some development auxiliary tools, making it easier for developers to develop DApp. Activities for developers will be organized to make the EOS ecosystem grow. 2 O&M and 6 R&D will be configured, developing DApp and its auxiliary tools respectively. Then 2 O&M and 8 R&D will be configured, responsible for the development of underling source code, DApp and its auxiliary tools.

8. Position on Dividends (The sharing of Block Producer inflation rewards with unaffiliated voters, AKA "vote buying.”) Please describe the block producer candidate's stance on sharing inflation rewards and/or paying dividends to EOS token holders. Will the organization offer payment to EOS token voters for any reason, including BP elections AND worker proposals? Does the organization have a written policy of no-payment for votes? If so, please provide a link.  

EosStore will neither promise any types of dividend nor enter into an alliance with some voters. We strongly object to introducing the idea of dividend in the EOS community. Vote-buying should be prohibited absolutely, as a massive vote-buying may lead to the collapse of EOS economic mode. In terms of how to attract more votes, the three key elements is determined.(a) we will establish and expand our at the node of maintenance and the development of EOS technology advantage.(b), we establish a high quality professional community for developers to develop technical training (c) we will assume the role of incubator, cultivate excellent EOS Dapp project and contribute to the EOS ecosystem.We believe that voters real, meaningful returns is a long-term vision, given the greater the overall interests of EOS community and focuses on how to use the actual strategy to extend the EOS ecosystem.
We will be completely independent of the voters.We have neither any dividend commitment, no association with voters.This is our bottom line.In showing us the independence of the voters, we will not make any intentional announcement.Our strategy is to establish and maintain a highly transparent with public relations.We warmly welcome the community to public scrutiny. 

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!