EOS BlockSmith - roadmap (eos.go checkmark #7)

The primary role of any Block Producer is to build and support infrastructure. Our roadmap is built to scale our infrastructure first and foremost. Upgrades include, but are not limited to, the following:

1. Increased RAM. There will likely be a high demand for RAM and we are making all preparations. With the potential for speculative RAM trading, it is important to have plenty, and be prepared to add more quickly. As we are self-funded, we cannot throw hundreds of thousands of dollars at RAM just yet, but it is the first thing on our roadmap for a reason. When we need it, we’ll have it.

2. Increased Cores. It is unclear if or when eos.io will incorporate multi-threading, since side-chains now give us unbounded scale potential but include increases in RAM as well. If multiprocessing goes back into development, we will prepare our processors and be ready.

3. Increased Bandwidth. Initially we are running 1Gbps, but this may need to increase. All of our datacenters are capable of providing additional bandwidth when necessary.

4. Increased Redundancy. At launch we will have full production-capable nodes in 2 cities. Post launch we will add our 3rd node outside the US.

Those of you familiar with the BlockSmith model know that we intend to burn our excess block rewards. In this way, we add that value back into the ecosystem by increasing the value of all tokens in EOS. The deflationary force created by burning tokens is the same mechanism used by Block.1 to return the RAM trading tax to the system. It’s completely fair, totally equitable, impartial, and unbiased.

The purpose of the token burn is to ensure that we are completely free of conflicts of interest, capable of doing full financial disclosures, and the work we do fits with our skillset as a team. However our commitment to financial independence does not preclude us from developing systems on or off chain which are profit-free and benefit the community as a whole.

One of our team’s core skill sets, beyond technical expertise, is education. Everyone on our team has a resume dotted with teaching, consulting, instruction, charity, and finding ways to give back to their communities and help others find success. From soup kitchens to free surgeries in Africa, to university-level instruction, to professional consulting, we cover the gambit. It’s part of who we are as people, and so it will be part of BlockSmith.

If we are successful we have some great ideas for ways we can build EOS Education into our model with conventions, conferences, hackathons, meetups, and an online educational portal. We have a meetup on May 23 in SF focusing on preparing the public for main net launch and teaching people how to register their tokens. We’ll also be at the Tulip conference in early June with many other EOS community members. Beyond that it’s heads-down working to prepare for launch. After launch, we will roll out plans for a major education initiative.

We have a plethora of ideas for how we can harness our skills in education and community outreach, but the time to formalize them and begin to act on them is not now. Now is the time to prepare to produce blocks and to be a leading BP in preparation. June is fast approaching, all hands on deck!