email: [email protected]
This post tries to answer the questions outlined by @eosgo in: https://busy.org/@eosgo/announcement-grading-criteria-for-eos-block-producers-in-march-7-report
Public website URL and at least one social media account (all social media links offered by candidate will be shared in report)
Links to the following ID information
Official block producer candidate: eos.store
Location of company: headquarters Beijing, China
Expected location of servers: Hongkong, Tokyo
Type of servers: Master(model: AWS x1e.32xlarge) Slave(model: AWS x1e.16xlarge)
Estimate of technical specifications and total expenditure for resources by June 3, 2018
we provide Master-Slave structure of node. There are two stages in total. We will step in the second stage once the workload reached the 70% of capacity.
Master(model: AWS x1e.16xlarge)
Slave(model: AWS x1e.8xlarge)
Master(model: AWS x1e.32xlarge)
Slave(model: AWS x1e.16xlarge)
Storage: 10Tb, AWS EFS
Location: Hong Kong
Total Expenditure: The budget is sufficient, we have other income from various investment.
Estimated scaling plan for hardware after June 3, 2018
There are two stages of upgrade plan. Every stage has both master and slave node. First, we will setup a new node which is the master node of second stage. Once this node synced over and work well, it will become the new master node. Second, the old master node become the new slave node. Finally, remove the old slave node. The migration is completed smoothly.
Community benefit project outline, only for projects expected to be public by June 3, 2018
Create a co-governed prosperous community. Each user can have the equal, transparent and open environment as well as the opportunities for dominating the EOS Store Community Development Orientation.
Listing of Telegram and node names for community testnet participation.
Node name: eos.store