Based on different governance concepts, the EOSC community has optimized the EOSIO election mechanism, launched the EOSC mainnet at Genesis Height 1, and continued to iteratively upgrade the EOSC mainnet, making EOSC move towards a decentralized high The direction of the performance smart contract platform continues to evolve, laying the foundation for the large-scale popularization of the encrypted economy.

Background

The encryption economy has ushered in a critical stage from social experimentation to large-scale commercial use.
Large-scale commercial use means huge transaction pressure. In order for a blockchain system to efficiently carry a huge amount of transaction demands, it must first provide sufficiently strong performance. To achieve this, higher requirements are required for full nodes, such as better configured hardware machines, larger storage capacity, more stable network, faster bandwidth, lower latency, and so on. Obviously, too high a threshold for full nodes will lead to a reduction in the number of block producing nodes that can operate stably. If the POS mechanism is adopted in such a blockchain system, the system will quickly converge to a centralized situation. To strike a balance between high performance and decentralization, the DPOS consensus algorithm is undoubtedly the best choice at present, and it is also the best feasible solution for managing a small number of nodes.
EOSIO based on the DPOS consensus algorithm came into being, and the community saw the dawn of large-scale commercial use of the encryption economy for the first time. Whether the election mechanism is fully effective is the key to the survival of the DPOS consensus mechanism, and it is also related to whether the DPOS consensus mechanism can succeed POW and lead the next generation of encryption.
In order to accelerate the arrival of the era of large-scale commercial use of the encryption economy, the EOSC community has optimized the EOSIO election mechanism, launched the EOSC mainnet at Genesis 1, and continued to iteratively upgrade the EOSC mainnet, making EOSC move towards The direction of a decentralized high-performance smart contract platform continues to evolve.

Consensus mechanism

EOSC follows the consensus mechanism of EOSIO, that is, DPOS BFT Pipeline Consensus. Unlike EOSIO, EOSC does not adopt EOSIO's model of one block every 0.5 seconds, and one node connects 6 blocks. In EOSC, one block every 3 seconds , Nodes will not continuously produce blocks, although continuous block production by nodes can reduce the waiting time for unpacked transactions, but because the current network environment is often not very ideal, rapid block production will affect the stability of the chain, resulting in a large number of micro forks.
The current consensus mechanism of EOSIO is not perfect, but as a DAPP platform, the block confirmation time is not the first optimization priority of the chain. For EOSC, the consensus mechanism must be considered in a high-load environment. In the current parallel computing mechanism If it is not perfect, rushing to improve the pipelined confirmation mechanism will cause big problems.
The future consensus mechanism of EOSC will evolve in parallel from two directions
1. Compatible with EOSIO development and update its consensus algorithm, we judge according to the current development progress of EOSIO, when EOSIO completes the parallel improvement, the consensus algorithm will be upgraded, Achieve faster block confirmation time.
2. It will adapt to other consensus mechanisms based on confirmation numbers, as a supplement to the existing DPOS consensus, on the one hand, it will realize the interaction between the embedded Layer 2 chain consensus and the main chain . On the other hand, it can realize a more decentralized cross-chain mechanism with chains of other consensus mechanisms.

EOSC Technology Improvement

Resource model based on service fee
Although the payment model of EOSIO's CPU and NET resources is a good design in technology, it is too complicated for users and cannot promote DAPP Developers optimize their contracts. On the other hand, the purchase method of EOSIO’s RAM will lead to certain hoarding behaviors, which is not conducive to the development of DAPP ecology. For this reason, EOSC innovatively designed a new set of resource models. Through optimization in practice , explore resource models based on service fees in a complex smart contract environment, and thoroughly solve the resource problems that plague the EOS ecology.
First of all, EOSC pays the user's CPU and NET resource consumption in the fee mode. For the Action defined by the developer in the DAPP, the DAPP developer can set the required fee for the Action, and the system controls the resource usage of the Action based on this , On the one hand, it is easy for users to understand the consumption of resources, on the other hand, it also strongly promotes DAPP developers to optimize the use of contract resources, so that the entire ecology develops benignly.
EOSC uses a method similar to renting cloud hosts to allocate RAM resources. Users can use voting dividends to pay for renting RAM resources. In this way, users do not need to worry about paying rent, and the problem of rent arrears is also eliminated. Through the method of "renting and selling", EOSC can effectively avoid speculation on RAM resources, so that the development of DAPP does not need to be disturbed by the price of RAM, and effectively promotes the ecological construction of DAPP.
While boldly innovating and exploring new resource models, EOSC is also exploring mechanisms to be compatible with EOSIO's resource models. For CPU and NET resources, users can pay fees based on dividend ticket age to achieve a similar EOSIO mortgage to obtain CPU And the effect of NET resources, for RAM, users can achieve the effect of EOSIO based on the market purchase through the form of mortgage voting swap, so that DAPP developers can quickly cut into EOSC from other EOSIO chains, and smoothly switch to the EOSC resource model.
Smooth update mechanism
EOSC's election mechanism encourages super nodes to actively participate in promoting technology upgrades. Unlike the split of EOSIO community node versions, EOSC actively promotes technology upgrades and renew.
In order to achieve a smoother incompatible upgrade process, EOSC has added an update mechanism based on the effective block height. The community can confirm the effective block height of a function through multi-signature, so as to complete the smooth upgrade in a decentralized manner process, different from EOSIO’s recently proposed labeling scheme based on block expansion data, EOSC’s update mechanism is more friendly and easy to understand. EOSC was the first to practice the decentralized “soft fork” update process in the EOSIO-based chain, which It is the basic guarantee for the continuous evolution of EOSC to solve various mechanism problems.
On the other hand, the function of setting chain attributes based on multi-signature can provide the community with a set of decentralized chain configuration and on-chain solutions. Various parameters and configurations can be modified in a decentralized manner according to actual development, making better community development.
Node heartbeat mechanism and stable block interval
In order to promote the stability of the main network, EOSC has strengthened the construction of candidate nodes from the perspective of economic model. At the same time, EOSC has added chain The heartbeat mechanism of the node on the network is used to promote the strengthening of the node to improve its stability and promote the stability of the entire main network.
On the basis of the heartbeat mechanism, EOSC can confirm the operation of the nodes, so that the faulty nodes can be punished based on the chain, so as to further supervise the construction of nodes and prevent the inaction of nodes from causing the instability of the entire main network.
Increase the block interval time at the beginning of the launch, so as to avoid occasional soft forks on the main network when the current network infrastructure is not yet perfect. EOSIO designed a half-second block interval and a Although the mechanism of nodes producing six blocks in a row can improve the availability of the chain in the future, it is not applicable in the current network environment. In a pragmatic manner, the interval between block production should be increased first, and then changed to rapid block production when the conditions are ripe in the future. This can effectively reduce soft forks, and at the same time, the reduction in the number of blocks can greatly increase the synchronization rate of full nodes, so that there can be more full nodes, thereby enhancing the availability of the entire network.
More contract layer APIs
In order to make it easier for DAPP developers to develop contracts, some APIs have been added, and some specific adjustments have been made to the system contracts.
First of all, an API for obtaining the block height is added. Developers can easily and efficiently obtain the current block height. Based on this API, the contract can effectively avoid blocking block attacks and other retry-based attacks. Second, add In order to obtain the API of chain configuration information, developers can adapt various parameter corrections and chain upgrades of the chain at the contract layer, so that the contract can also smoothly follow the chain upgrade function. Finally, in order to avoid counterfeit currency attacks, before the chain starts , an independent core token contract is used, so that users can clearly distinguish counterfeit currency attacks.
Adaptation to cross-chain services
At the beginning of the launch, the Force team foresaw that the support for cross-chains in the future will be the basic function of the public chain, so the Force team started the Codex project Development, establish the Codex.Relay relay chain to provide relay services for each chain, so as to realize the cross-chain mechanism between each chain, can provide more perfect support for Codex.Relay, and interoperate through the super nodes of the two chains , can achieve a "complete" cross-chain mechanism, that is, the degree of decentralization of any chain will not be reduced during the cross-chain process.
Through the cross-chain mechanism, great scalability can be obtained. Based on the relay service, Layer 2 sub-chains can be added. Some services and DAPPs that consume large resources can be run on the basis of sub-chains. Through the relay service, the The calculation results or the core state are synchronized to , so that special sub-chains such as storage, calculation, DAPP, and random numbers can be added in the future to expand functions.
Highly customizable EOSIO blockchain development framework
Based on relay services, Layer 2 sub-chains can be added, and various sub-chains will play a role in the EOSIO ecology in the future It has a great effect, but it should be noted that the current development of a blockchain project with customized functions based on EOSIO still has a high threshold. For this reason, the Force team has launched the Codex.io project, which is a highly customizable The EOSIO blockchain development framework lowers the threshold for sub-chain development and provides developers with a more economical and friendly sub-chain development experience.
The Force team has accumulated a lot of experience in developing blockchains based on EOSIO during the development process, and hopes to maximize the value of these experiences. Codex.io is an "out-of-the-box" EOSIO block Chain development framework, developers can quickly start their own chain based on Codex.io, after simple configuration, they can customize various symbols, freely choose economic system and resource model, on this basis, developers only need to pay attention to the chain The problem to be solved by itself can be implemented based on the contract or the native layer of the chain. Codex.io can facilitate developers to expand in the native layer of the chain, so as to solve some performance problems, and can also greatly expand the chain. Function.
Codex.io integrates the expansion functions proposed by most of the current EOSIO chains. With an inclusive attitude, Codex.io allows developers to freely combine functions on the chain: including subsistence allowance system, account system, various black and white list mechanisms , common governance mechanisms and voting mechanisms, and various plug-ins.
Through Codex.io, a large number of Layer 2 sub-chains will be integrated in the future, which will provide unlimited scalability.