On Jan 18, 2019, the core developers of (ETH) announced, once again, to postpone the activation of the Constantinople upgrade via network hard fork. This is the third time that the upgrade has been postponed. The developers announced they are planning to ‘try again’ in late February – with the new upgrade block height set at 7,280,000.
The industry has noticed that the ability to upgrade the network seems to be one of the biggest challenges to a distributed system and has now become a key point that hinders further development of the entire world.
Most projects, including , are inflicted by this challenge, basically due to the fact that communities are separated into three unique groups with different agendas. These groups include: developers, hardware miners/node operators and holders. For instance, the governance model and ultimate control of under the current PoW consensus comes down to the nodes who choose to implement the upgrade or not, and the direction of the upgrade is mainly affected by the small group of developers. This leads to an inefficient and enclosed system where the ‘voices of the few’ control the entire project.
It’s an expensive and time-consuming process for the new software version to go live. Even after core developers have agreed on a proposal, completed the required software and prepared to release the update. software updates are very complex; requiring all network nodes to upgrade their software prior to a specific time so the new update can come into effect. This type of update is commonly known in the world as a hard fork. In the past, hard forks have led to network slow downs, community separation and major issues for all who utilize the network.
The decision of the developers could in one respect adversely affect the miner/node operators while on the other hand being beneficial to other parties on the network. In return, the miner/node operators can make the choice not to integrate the latest update, and consequently, pressure the development team into altering their decision and to rewrite the code altogether. All the while, holders have almost no say about the future of the project. Overall, one can say it’s not a fair and trustworthy system for anyone involved.
This is a significant problem in the industry and has been putting a lot of attention and research into this difficult issue. Nebulas’ vision is to let everyone get values from decentralized collaboration fairly. To achieve this, it’s important to have a system where communities can work together equally, and as a result, the system should autonomously evolve through common decisions.
Pertaining to the issue of system upgrades, Nebulas believes that “the decision makers of a upgrade should not be centralized. It belongs to every participant in the community. Every user of Nebulas has the right to participate in and choose the future direction of Nebulas.”
One of the many new features that Nebulas NOVA will include is the Nebulas Runtime Environment (NBRE) and is the first version of Nebulas Force as stated in Nebulas’ whitepaper. NBRE is the execution environment for the Nebulas core protocols and algorithms; based on the JIT (Just In Time) LLVM (Low Level Virtual Machine) compiler, making it possible to manage, execute and submit LLVM Intermediate Representation (IR) to the Nebulas .
In Nebulas NOVA, the algorithms and parameters of key features are stored on the in the form of LLVM IR. NBRE will execute the algorithms when acted upon by external requests (such as a API call) and export the corresponding execution results.
Due to the fact that NBRE can manage and the LLVM IR on the , these protocols can be upgraded automatically. As a result, an assembled community of developers, holders, and nodes operators will form a consensus for system upgrades and the network will be automatically upgraded without the need of node intervention.
In return, the expense of upgrades is significantly reduced. Having the ability to upgrade the core software without the centralized power of nodes and through on-chain governance leads to an autonomous network that always supports the newest features, bug fixes, and consensus protocol updates. In this way, with this new power, Nebulas NOVA becomes a powerful tool for Nebulas to implement its community governance.
To create a more democratic network, Nebulas is currently developing governance where developers, nodes operators and holders all have an equal voice, thereby promoting the co-creation of a fair and open ecosystem!
- – February 22, 2019
- – February 22, 2019
- – February 12, 2019
- – February 12, 2019
- – February 8, 2019
- – February 8, 2019
- – February 6, 2019
- – February 6, 2019
- – January 31, 2019
- – January 31, 2019
- – January 30, 2019
- – January 24, 2019
- – January 24, 2019
- – January 23, 2019
- – January 21, 2019
- – January 18, 2019
- – January 17, 2019
- – January 10, 2019
- – December 17, 2018
- – December 15, 2018
Published at Fri, 22 Feb 2019 16:53:20 +0000
