Block.one has officially release EOS 1.0.1.
There have been a few Test Nets taking place.
There has been no user acceptance testing that took place.
There is no available Wallet solution.
How voting for Block Producers will work hasn't been identified.
How Governance will work hasn't been identified.
How Arbitration will work hasn't been identified.
How to ensure an entity doesn't own or has interest in 15+1 Block Producers hasn't been identified.
How to ensure a Block Producer doesn't have interest in another Block Producer hasn't been identified.
If this was a software release in an Enterprise environment, It would have received a "No Go" status to deploy.
I have been a Software Developer and System Architect for past 15+ years and EOS software release should not be exempted from following a Software Development Lifecycle (SDLC). I have worked for many Fortune 500 companies including Accenture, Verizon, AT&T, Citizens Bank and more. The SDLC identifies specific activities to ensure a successful implementation.
- Requirements
- Design
- Development
- System Test (Test Net)
- User Acceptance Test (Community Test)
- Deployment (Main Net)
#1 - #5 is an iterative process in order to allow for identification of bugs and assign it to the developers to get fixed. It is much cheaper to get these potential issues fixed prior to the deployment (launch of the Main Net).
#1, #2 and #3 has been completed by Block.one when they officially release version 1.0
#4 is equivalent to Block Producers launching a Test Net (such as Jungle Test Net, Superhero Test Net, Scholar Test Net, etc..). This is where Block Producers test the functionalities being delivered by Dan Larimer & team. Block Producers also work together in this phase to streamline the operation and optimally configure the software to run like a welled oiled machine. Once they're happy with the results then they should release the Test Net to the Community to test drive the system and the network. There may be many of these Test Nets running simultaneously in order to allow all of the Block Producer Candidates to participate.
#5 I believe is crucial. With the snapshot of the EOS-Contribution contract and the creation of the Genesis block, it means that EOS owners are a huge population block who can do some real world testing. The Community can provide the load needed to test the SLA of .5s blocks. This will put a huge number of transaction in the transaction pool and allow for the following types of testing:
- Performance Testing
- Stress Testing
Block Producers who's equipment can't keep up with the demand will be quickly and clearly identified. This allows them to make changes to their hardware and infrastructure.
Then we get to #6 once the Block Producers and the Users have given consensus that the Blockchain is truly ready to be launched. This can be done by collecting user input on some portal (can be a simple survey) once there is an acceptable number of transactions/blocks processed by the Test Nets. The Block Producers can then certify the EOS Blockchain Test Nets and identify a launch date.
To me, this would be an ideal process but so far the process seems to be in disarray. Questions are being asked in many different forums but proper answers are not being given. There are still so many unknowns but Block Producers seems to be ready to launch a Main Net without proper certification of the Test Net. Before we trust these people with our investments, we need to make sure that the Main Net will not be launched, stopped, relaunched, stopped, relaunched, stopped and relaunched.
There is a lot of money on the line and Block Producers will want to launch the Main Net quick fast and in a hurry but what's the big hurry? I believe as long as the Community is given an opportunity to test drive the Blockchain, they will understand the wait.
I haven't mentioned all of the other issues with Wallet, Voting, Governance, Arbitration. The effort to clearly identify what those solutions are will need to take place in parallel and it is happening as far as I can see. But why the Main Net launch if those activities aren't completed. For example:
- As a DApp developer, how do I deploy my DApp?
- As an EOS owner, How do I recover my account?
- As an EOS owner, How do I take a dispute to arbitration?
What everyone needs to know is that EOS is not like the other Blockchains that has come before it and many after it. It's not simply a chain to speculate on a currency nor is a chain to simply deploy DApps on. It has many more next level functionalities and I believe this why it's more challenging to coordinate and launch such a Blockchain. This is the more reason why we as a Community need to ensure it is done properly or else all of the Naysayers will have the last laugh and all us investors will hear the infamous "I told you so".
Update 6/5: EOSCANADA has released a very detailed timeline for the launch and it does specifically call out for the Block Producers and the Community to verify the contents of the chain, voice any concerns or issues, workout solutions and finally validate the chain. That's what I'm talking about! I have to commend everyone on the outstanding effort being put forth. I think a lot of people all around the world are going to be very very happy with the results. So far, the Block Producers have proven themselves to be professional, competent, great team players and collaborators. I think once launched, EOS will be in good hands. Keep up the good work!!
The Launch Timeline can be found here: https://www.eoscanada.com/en/block.one-releases-eosio-v1.0-eos-launch-live-update
