D · R · E · P are the four released versions of the DREP Chain test network, representing the four key nodes in the development of the DREP public chain.
Today, we launched the third version of the test network, Euler (Euler), dedicated to helping companies deploy blockchain and reduce the barriers to entry for enterprise technology. The released version will be launched on the 31st of this month.
Test network 3.0 basic situation
-
Cluster structure : 7 main chain nodes, 128 sub-chains
7 nodes in each chain, the main chain node verifies all transactions, and the sub-chain nodes process their respective transactions and blocks
-
Total number of network nodes : 903 = 7 + 128 * 7
-
Node deployment : United States, Canada, Japan, China, South Korea, Singapore, United Kingdom and other countries
-
Peak TPS : 14000
new features
Address alias function
Aliases are easy for users to identify and remember; aliases correspond to addresses one by one. Aliases are unique in the chain, and support updating and deleting aliases; various address-based operations of users can be achieved through aliases.
To achieve mainstream use of blockchain, it is imperative to lower the threshold for companies and individuals to use the technology. Ordinary users must be more accustomed to using simple account registration systems like WeChat and Alipay to operate. The one-to-one alias system can restore the experience of this operation to a greater extent, greatly reducing the barriers for new users to use blockchain.
Optimization function
① P2P module optimization
The P2P module adds the function of trusting nodes. Under the BFT consensus mechanism, block nodes are added as trusted nodes, and they enjoy the highest priority in building a p2p network, making the network fast and stable. By providing hooks (method mode) through P2P, the p2p module is uncoupled from the upper-layer modules of the blockchain protocol; each upper-layer module can independently define its own message type and message processing method.
This optimization improves the stability and efficiency of the block generation nodes of the network, and better provides the necessary security guarantee for the entire network
② Optimize the query of historical data such as transactions / data blocks
Introduce mongoDB to achieve distributed and highly concurrent reading and writing of data in nodes. From 10 transactions per second to 10,000 transactions per second
③ Optimize the transaction signature verification process to achieve a substantial increase in the main chain TPS
Previously, the single main chain was 1000TPS, but now it can reach 6000TPS.
Under the premise of this throughput, DAPP developers and various service providers can build more high-frequency and smoother blockchain application projects in the DREP network.
④ Add the executable client of the go language version to communicate with the server using http
Provide more options for joint debugging and official use with the exchange; at the same time, it is also convenient for third-party developers to use the DREP source code environment to build
⑤ Trading pool optimization
The read-write separation method is adopted, that is, one queue is used to write data to the transaction pool, and another queue is used to read data from the transaction pool. After the read-write separation, the speed of receiving data in the transaction pool is not subject to any restrictions. Only when the amount of data in the transaction is large enough and exceeds the size of the pre-allocated space for the system will the transaction pool receive data fail.
⑥ Optimization of data synchronization between nodes
The implementation of the previous version: the new node only synchronizes data to a full node. Optimized synchronization process: the new node obtains the hash of all blocks to be synchronized from a full node, and then selectively synchronizes the block body to other nodes according to the node's network status. The current approach is to send blocks to other 3 nodes Body request. In this way, synchronization to a single node can be avoided, and the failure of the other party leads to unsuccessful synchronization. And simultaneous service to multiple nodes can also improve synchronization efficiency.
Advancing forward and fulfilling expectations
In this update, the technical team has further lowered the threshold for enterprise partners to use blockchain technology, helping partners to easily start their own blockchain services on the DREP platform, and targeted services to specific goals Groups can also feed back the development of the entire DREP encryption ecosystem.
In order to better promote this vision, the following are the areas where DREP focuses on deep cultivation:
① Develop DREP SDK components to incubate super chain games
We will focus on the development of DREP SDK, which is a set of developer tool components that can support various DAPP on-chain. The DAPP R & D team will be able to publish a multi-public chain asset-supported version with one click, built-in wallets and asset trading platforms, and obtain multi-public chain users based on the shared DREP ID. The R & D of the version is to open up all digital assets through the DREP SDK, so that users in the entire blockchain industry can make payments, transactions, and mortgages without any threshold.
② Open up digital assets and reduce transaction friction
Based on the needs and expectations of an ecological expansion, we study the multi-asset integration function. At the beginning, it will be a simple version of SWAP based on DREP's internal system, which supports the exchange of DREP and various tokens in the system; and later it will be expanded to two-to-one exchange between tokens and tokens in the system.
③ Build a cross-chain account system, build a value network
At the protocol level, DREP will create and coordinate protocol specifications, which will define the construction / deployment of various projects, to facilitate our continued research and establishment of cross-chain networks, and to breakthroughly relate important personal identities such as reputation (credit / loyalty) Behavioral data is also synchronized and migrated across the link, eventually forming a seamless value exchange between DREP's internal ecology and other chains.
