EOS Silicon Valley - Block Producer Candidacy

in #eos6 years ago (edited)

EOS Silicon Valley - BP Candidate Introduction



announcement_image_b1.png

Contents:

  1. Vision
  2. Strength
  3. Technical Details
  4. Team
  5. Community Benefits Plan
  6. Contact

1. Vision

Hello World!

This is EOS Silicon Valley. We are a team of EOS enthusiasts based in Silicon Valley with deep expertise in technology, product, marketing and operation.

With the awesomeness we have in technical talents and community resources & influence, we want be one of the 21 Block Producers to help launch EOS in mainnet and make decentralization applications universally accessible and useful.

2. Strength

Why us? Here are the 3 main reasons:

  1. Technical capability - we are top engineers and visionaries from silicon valley community
  2. Community influence - we have resources and willingnesses to promote EOS ecosystem to next level for digital world
  3. High Integrity - with our expertise and experience, we stick to the goods to make EOS community better

3. Technical Details

Expected location of servers

Oregon, USA
Virginia, USA

Type of servers

Cloud servers before reaching to a certain scale (e.g. 10k+ nodes) or a tipping point where we have to gain extra security, control and/or customization than cloud offerings on the market.

Tech Specs

Here at EOS Silicon Valley tech team, we are a group of engineers having deep expertise on scale industry leading infrastructure to tens of thousands of nodes. We prefer to start with Amazon Web Service (AWS) given our expertise and the fact of its low entry barrier, high scalability, enterprise level security and customer support.

Currently, we have 4 m5.4xlarge EC2 instances up and running for our own EOS pacific rim testnet, as well as EOS Jungle testnet. Those instances are located within 2 Availability Zones (AZs) of AWS Oregon region, and secured by Amazon Virtual Private Cloud (VPC). In addition, we set up Elastic Load Balancer (ELB) for load balancing and Route 53 for traffic routing.

Specs for each of our m5.4xlarge instances are listed as below:

  • Up to 10GB network bandwidth
  • 16 vCPUs
  • 64G RAMs
  • 512G SSD storage

In the next few weeks before June 3, 2018, we will scale up our infrastructure to be fully production ready. We don’t have a precise prediction about the exact scale we will have to be at this point, but we will continue to engage with the EOS community to figure it out. However, we do plan to run a stress testing for our infrastructure to be at least ready to scale to 500 m5.4xlarge instances (or equivalents) in less than half an hour time. In total, this would be equivalent to:

  • 8,000 vCPUs
  • 32T RAMs
  • 256T SSD Storage

For expenditure, given it will be a gradual scaling up between now and June 3, 2018, It is estimated that we will run around 10 m5.4xlarge instances on an average day.

The following math is based on a 30-day window:
Rough EC2 cost = 10 /day * 30 day * $0.768/hour * 24 hour = $5,530
Rough EBS cost = 10 / month * 512 GB * 0.1 /GB / month = $512
Rough total expenditure = $5,530 + $512 = $6,042

Scaling Plan

Quickly after June 3, 2018, once we stabilize our BP infrastructure together with EOS community, in short-mid term, we will be focusing on the following:

  • Quick incident response - monitoring, detection, recovery and prevention
  • Enhanced security protection - Anti DDoS and Firewall
  • Cost efficiency - reserved instance, spot instance, shared lower cost S3 storage.
  • Multiple Regions - disaster recovery, failover, lower latency for US east coast traffic
  • Auto Scaling up and down - intelligent scale up / down based on traffic prediction

We currently envision the following infra architecture:

In mid-long term, we will re-evaluate our overall infrastructure based on stability, cost, control, security and customization etc. We envision the possible strategy would be one of the followings:

  • Hybrid cloud (leveraging AWS, Google Cloud and/or Microsoft Azure)
  • On-premise + Cloud, e.g. on-premise data center for average capacity, while leveraging AWS for traffic spike)

Testnet

To get us hands dirty, we started with joining EOS Jungle Testnet with one BP node named as “pelican”.


Our Initiative: EOS Pacific Rim Testnet

Furthermore, we committed to build a self-managed Testnet: EOS Pacific Rim Testnet(https://github.com/lucas556/EOS-Pacific-Rim), together with EOS Beijing, EOS Asia etc. So far we get 4 BP nodes up and running well.

We are working on getting more participation and feedback from broader EOS BP community. Welcome to join our telegram group to share your ideas! https://t.me/eospacificrimtestnet

4. Team

bo_image@2x.png

Bo Yu - Co-founder
Senior Product Manager @ Instamotor; former PM & Engineer@ Oracle. Participated in "traditional" Enterprise Operating System - Solaris
MS @ Carnegie Mellon University
hugo_image@2x.png

Hugo Yang - Co-founder
Engineering Manager @ Lyft; former Tech Lead & Staff Engineer @ Walmart Labs
MS @ Carnegie Mellon University
glen_image@2x.png

Glen Zhang - Blockchain Engineer
Software Engineer - Big Data @ Apple
MS @ Carnegie Mellon University
xialin_image@2x.png

Xialin Zhu- Blockchain Engineer
Staff Software Engineer - Infrastructure @ Linkedin
MS @ Carnegie Mellon University
maggie_image@2x.png

Maggie Zhang - Operation
Program Manager @ Alchemist Accelerator; former Digital Marketing @ Cinemood
MA @ Stanford University
null_image@2x.png

Issac - Blockchain Engineer
Software Engineer @ Google
Extensive blockchain development and investment experience
MS @ Carnegie Mellon University

5. Community Benefits Plan

Develop community beneficial tool/tutorial

As a team with strong technical background and influence, EOS Silicon Valley plan to develop tools/tutorials to make DApp dev's life easy [more to come]

Discover, help and invest in great DApps on EOS

We are product builders ourselves and we know the ins and outs on how to build great products. Furthermore, we have extensive connections with top accelerators and VCs in Sillicon Valley.

We will discover, help and invest in great DApps with top ventures to fuel more growth in EOS - which is fundamental to the future success of EOS ecosystem.

Host local meet-ups/conference in greater Silicon Valley areas

We are planning to cooperate with partners to host EOS events to promote brand awareness in silicon valley community, to attract more talents into the ecosystem. More details will follow.

6. Contact

Telegram: https://t.me/eossv
Steemit: https://steemit.com/@eossv
Twitter: https://twitter.com/EOS_SV
Medium: https://medium.com/@eossiliconvalley
Email: [email protected]

Sort:  

Congratulations @eossv! You have completed some achievement on Steemit and have been rewarded with new badge(s) :

Award for the number of upvotes

Click on any badge to view your own Board of Honor on SteemitBoard.
For more information about SteemitBoard, click here

If you no longer want to receive notifications, reply to this comment with the word STOP

Upvote this notification to help all Steemit users. Learn why here!

Coin Marketplace

STEEM 0.19
TRX 0.14
JST 0.030
BTC 60787.79
ETH 3242.30
USDT 1.00
SBD 2.46