Chromia Mainnet Clarified

Chromia Mainnet Clarified

Many of you have asked for updates on the Chromia Mainnet, in this article we’ll clarify our mainnet roadmap and describe our progress.

First, let’s clarify what we mean by a “mainnet”. For us, “mainnet” is not a particular milestone, but a process of a continuous refinement on a path towards maturity and mass adoption. Many projects get ossified once they reach a “mainnet” status, after that stage only minor modifications are allowed. This often gets in a way to the adoption, as initial design does not meet the needs of real applications. We would like to avoid that, and grow our “mainnet” gradually.

Our first step in this process was in January of this year, when we launched the network we call “mainnet” and the first application running on it,  the Green Assets Wallet (GAW).

The definition of what many people refer to as "mainnet" is a fully autonomous decentralized network which, in case of a dapp platform like Chromia, should be able to run any application. This is certainly the goal for us, but we don’t want to rush towards that milestone; instead, we see much more value in continuing that work while simultaneously focusing on applications' needs. Our current goal is to put more applications on the mainnet incrementally. A mainnet with actual serious and useful projects running on it is way more valuable than rushing to a universal one.

Next in line for deployment on the mainnet is Hedget. We want to do everything that we can to make sure that Hedget can successfully and safely run on Chromia, and at the same time, integrate well with Ethereum. If we prove that this works well, we believe that it will inspire other developers to work with Chromia.

We are also working on onboarding more providers to mainnet as well as launching staking program in October.

At the same time, we continue working on core features which would allow the network to work in a more autonomous fashion. We have significant progress on application containerization and dynamic resource provisioning, but given that these features are state-of-the-art, it is hard to predict when exactly they will reach full maturity. Since no application actually requires dynamic resource provisioning at this point, we do not want to put pressure on developers to release something at a certain date: instead, the developers should focus on making sure features work in optimal and reliable fashion.