On November 29th, the Nebulas Technical Committee held another meeting with the intention of reviewing optimization opportunities for the Nebulas core.

I. The Nebulas mainnet optimization meeting was divided into three sections:

1. Performance Improvement: Improving TPS (transactions per second). 2. Storage Optimization: reducing storage overhead and improving thequery efficiency of data. 3. Stability Enhancement: avoiding invalid functionality, such as crash and synchronization issues.

II. Why and how to improve:

1. TPS

(1) Reason: In addition sustaining stable performance, the Nebulas mainnet team will be working to further improve TPS.

(2) Method: We’ll make careful decisions according to the development direction and cost of Nebulas technical vision. The optimizations include transaction data cache, storage data serialization, parallel packaging, parallel verification, V8 instance reuse, so as to improve the efficiency of smart contract execution and data compression. Other concerns include reduction of transaction verification time.

(3) Consideration:

A. The importance of TPS is not the core point of Nebulas technical vision. Our focus is to prevent TPS from becoming the bottleneck of Nebulas. The improvement of TPS can also be combined with feedback received in the process of technology output.

B. We also hope community members can participate in this part and submit their proposals to further improve Nebulas’ TPS. Nebulas will also consider planning a bounty program for this optimization.

2. Storage optimization:

1) Reason: Currently, the transaction data size is huge and keeps growing. This significantly consumes a lot of storage space, affects synchronization, and also affect the efficiency of data operations.

2) Method: Transaction data compression, KV database structure optimization, distributed storage, light nodes, etc.

3. Stability enhancement:

1) Reason: Avoid function failure in smart contracts

2) Method: The V8 engine which powers smart contracts performs logical separation, update and reconstruct the existing modules.

III. The roadmap of the Nebulas core development team for optimization is to comprehensively consider the importance, urgency, development difficulty and other priorities.

IV. During the process for promoting and optimizing, the Nebulas Technical Committee will create a summary of the experience and technical achievements in the work of optimizing, such as data compression, database optimization, etc.

The experience summary will be announced and the applications will be promoting the Public Chain Technology Alliance. In addition, it will continue to explore optimization and other advanced technologies in the industry for the future.

V. Nebulas Technical Committee will seek a breakthrough in the underlying technology.

In the process of Nebulas operation and NR execution, we perceive a limit brought by data-store structure and technology. To a certain extent, the current data-store structure has an unfriendly impact on the application of blockchain technology. The Nebulas Research Institute will seek innovation and breakthroughs in data-store structure while optimizing the existing technical framework.

VI. Super nodes: The Nebulas Technical Committee believes that supernodes may be a call to action to the community and promote decentralization.

As we continue to develop the PoD consensus mechanism, we will give advanced preparation to technology and governance plans according to the Nebulas NOVA technical points and feedback.