BSN Livestream Reviews: Chain33-based Dedicated Node Services Introduction
FUZAMEI always insists on the technical guideline of domestic production, independence, controllability, and innovation.
As the core product of FUZAMEI, the Chain33 blockchain bottom architecture system was officially open-source at the end of 2018 after 5 years of development. It has always maintained efficient technical iterations and functional updates. Open-source address: https://chain.33.cn/
A few days ago, blockchain service platform BSN added the Chain33 dedicated node services, and Hailei Yuan, the bottom architecture R&D engineer of the Chain33 blockchain, was invited to offer a training course on the topic of “BSN Dedicated Node Services Chain33 Introduction and Use Demonstration”. In the live broadcast course, Hailei Yuan explained the Chain33 bottom architecture and the use demonstration of Chain33 dedicated nodes to BSN users, which attracted the attention and questions of many BSN users and blockchain developers.
Trainer Profile
Hailei Yuan, Blockchain Bottom Architecture R&D Engineer, Hangzhou FUZAMEI Technology Co., Ltd.
He is a former Oracle senior engineer, started to research blockchain in 2014, participated in the development of multiple bottom architecture technologies of Chain33 blockchain, and has an in-depth understanding of blockchain and blockchain-based applications. In 2019, he was invited to China’s Microsoft headquarters (Beijing), and the 2019 Blockchain Developers Conference held by CSDN to share the topic of blockchain innovation architecture.
Livestream Highlights:
The live course is mainly about sharing a technical introduction of the Chain33 consortium chain and how to use the Chain33 consortium chain on the BSN. The live is divided into 4 parts, the first part is about the Chain33 architecture introduction, and the second is some functional components of Chain33. The third one is some blockchain applications built on the Chain33. Finally, he introduced the process of using Chain33 on BSN and how to integrate applications with blockchain technology.
Part1: Introduction and advantages of Chain33
Hailei Yuan:
Hello everyone, let me introduce the overall architecture of Chain33. The bottom layer of the chain system is the bottom architecture of Chain33. It contains all the functions of the blockchain, such as smart contract modules, consensus mechanisms (it also supports pluggable functions), network layer (P2P network), and as for the data layer, it is the format of data storage with the support of storage formats, like Merkle tree, MPT tree, etc.. For the passwords and security, it supports international algorithms, state encryption algorithms, privacy protection, and other capabilities.
These capabilities are the core power of the entire platform. However, due to the blockchain distributed multi-node deployment method and the threshold of use, there will be a certain threshold for deployment, operation, maintenance, and application access.
Therefore, on the blockchain bottom architecture, we provide a blockchain management service platform. Through it, we can achieve capabilities such as the management of blockchain nodes. For example, we can create consortium chains and parachains with one click, and execute node management by adding or deleting nodes. Then the platform has capabilities, such as order billing, security certification, and other management tools. At the same time, it will execute load monitoring to the nodes, including blockchain performance monitoring, and synchronization status monitoring.
In addition, we can support the ability of an application center, that is, developers can quickly deploy smart contracts, some blockchain tools, and SaaS applications on the platform. Developers can quickly access the blockchain through our API interface.
Then, on the basis of this platform, companies can encapsulate a variety of rich application scenarios, for example, companies can do a number of business applications, such as commodity digitization, bid contract management, electronic files, and so on.
Part 2: Practicing the implementation of the blockchain, and realizing data on the chain through the deposit service
Hailei Yuan:
This is a flow chart of the electronic file deposit application, which uses the deposit service to send data on the chain. In reality, there are many users who do not have much time to study the technical practice of the bottom architecture. For those users, they just want to send some hash values of electronic files and the file attachments to the blockchain without doing extra things.
Therefore, we have packaged the deposit service in the middle.
The OA system and the foreign affairs system will create this kind of compressed package in the process of forming this document. And then each forms an electronic document. Each electronic document has its metadata information with an attachment. It will edit one of its metadata into a JSON string, and the hash of the attachment was sent to the deposit service.
After that, the deposit service will call the on-chain interface of the blockchain, and while storing the data on the blockchain, it will return a transaction hash to the OA system and the foreign affairs system in real-time. This transaction hash is the only proof of this deposit on the chain, which is called the unique key value. After the OA and foreign affairs system form an archive, it will push the electronic document and the original data to the electronic archive system, then the electronic archive system will confirm the filing, complete OFD conversion, data encapsulation, long-term preservation, archive utilization, and file identification. In these processes, it will call the interface on the data to save the data on the blockchain.
In the process from top to bottom, identifying the uniqueness of the entire file is the hash returned in the first step. The first step is to access the hash and application layer database records. After the completion of the on-chain, we also provide a client for traceability verification. Then the function of the client is it can implement traceability of electronic attachments without OA or electronic file systems when the entire blockchain platform exists. For example, I generate a hash of an electronic file attachment on the chain, through the traceability client, the deposit service gets the entire attachment, how the electronic file attachment is generated from, and how it is used in the file system (For example, who initiates the action, who approves it, who confirms it, etc.), these processes are traced back to the source, which is equivalent to an H5 page.
You can check the complete life cycle of the electronic file on this page. Unlike traditional databases, whether it is MySQL or Oracle, as long as you want to change the data and do an update in the background, you can change the data, then you don’t know what the historical data is like. But with blockchain, it can record your step-by-step process, and even if your application system does not exist, you can still check the entire life cycle of the electronic attachment from the blockchain.
This is an example of an application on the chain through the deposit service.
Interactive Q&A Part1：What are the advantages of Chain33’s bottom architecture technology over ETH?
Hailei Yuan:
In fact, Chain33 that I have introduced just now belongs to the category of consortium chains, while ETH is actually a public chain, therefore, the two chains are in different forms. The difference between them is the consensus protocol, in which we have done some optimization on the consensus protocol supported by PBFT. However, we are not satisfied with this traditional consensus, and we have done some deeper customization based on the traditional model. We support continuous block generation and aggregated signature technology. We have also optimized the parallel execution of transactions and data storage to maximize the TPS of Chain33.
Interactive Q&A Part2：How do developers learn the Chain33 technology?
Moderator:
One more question, can you share the code of Chain33, and is there any open-source code for developers to learn from?
Hailei Yuan:
OK. We already have open-source code on GitHub, which is 33cn/chain33.
What I have just described is a plug-in architecture. Chain33 is the core capability. It achieves functions like a ledger, consensus, memory cache pool. P2P is the most basic and core thing, which is relatively simple and stable. We will control the amount of code to ensure that the chain can run well. Other capabilities are in Plugin. we support both DPOS and PBFT consensus mechanisms. For QBFT (Quickly BFT), it’s our capability that we optimize. Programming two things together in the form of a plug-in. Through the configuration file, if developers want to load the QBFT plugin, then it runs QBFT consensus. All the codes and SDK can be found on chain.33.cn.
Website: 33.cn
Github: https://github.com/33cn/chain33
E-mail Contact: 33fuzamei@gmail.com
WeChat Official Account: 复杂美（mandarin）
