EOS is a blockchain protocol for building scalable decentralized applications.
Blockchains can only have two of these three properties: Decentralization, Scalability, Security
You’ll want all of your public blockchains to be secure, so you have to pick one of the other two options: Decentralization or Scalability. It is important for the market to test out both pathways.
EOS is an experimental blockchain with lower decentralization and higher scalability.
There have been countless blog posts, tweets, videos and talks about how EOS isn’t decentralized at all. I won’t be touching upon that subject since it’s been debated to death.
Here is some content if you’re not aware of the discussions:
The accounts heifner, brianjohnson5972 and pmesnier are Object Computing employees. The account bytemaster is owned by EOS CTO Daniel Larimer. The other 2 accounts are developers who were contributors to Steem & Bitshares (Both were previous projects of Daniel).
If you go down a little further down their contributors page we can find that there are also 3 more developers from Object Computing: cj-oci, PaulCalabrese and mitza-oci.
These are only the obvious accounts, which have this information available on their Github account. I suspect there are other OCI employees that have not made this information available public on Github. [2]
So, what is Object Computing, Inc?
It’s a software consulting company founded in 1993 in St. Louis, MO that now has 70+ employees. They work on projects from wide variety of industries like defense, energy, finance, healthcare, manufacturing, commerce and telecommunications.
If you are building any kind of mission critical software that has few predecessors, you need full time all star developers in your team, working for your project without other professional involvements or you’re not going to be able to build it [3]. This statement gets more significance when building any kind of hard tech, like EOS is attempting to do.
No serious technical innovation has been made by saying “I have this great idea, now build it for me, here’s some cash.”.
Take a look at a list of all the top tech companies. Which one of them outsourced the development of critical components of their product? [4]
Why does the most prematurely funded company in the history of humanity, Block.one, not have a dedicated developer team and instead uses a consultancy service for their critical development activities? Surely they can hire a battalion of full-time in house engineers to work on the product with the money they raised.
Hiring a Q&A team? No.
Trying to hire Research Scientists in Times Square?
Creating a VC fund, because why else would developers build here?
Block.one did not have a hiring/career page on their website until March 2018. And after February 2018 they actually hired a few engineers, so there is progress. But why specifically at February-March, what happened then? Leave a comment if you know.
I’m just throwing out some ideas, roles and numbers without thinking much about it to prove a point.
Hire the top 3 people in the world from each these areas:
Hire the top 5 people in the world from each these areas:
Hire the top 5 people in the world from each these areas:
That’s 73 people in total. Since there is a high demand for these talents, let’s go way over the market price and give them each a $1M yearly salary. The cost of building this team would be $73M yearly. $730M in 10 years. With a whooping $3.3B left for operations and marketing. Wouldn’t this a better way to spend investor money?
EOS is either going to be the most spectacular winner in the history that changed every rule in the industry like Facebook, or the most spectacular loser in the history like pets.com.
Which do you think it will be? Share your thoughts in the comments.
[2] Another thing to consider which I haven’t is diving deep into the code, look at key core files and figure out who wrote it via blame view. I checked out the EOS Launcher main.cpp real quick and 80% + of it was written by by OCI employees. Also, almost no documentation in an open source application?? Not even going to mention issues with software design patterns in the code.