 Hello everybody, it's my great honor to be here to speak in the HyperLider Global Forum. My name is Yi Zhang, I come from Huawei Cloud, I came from China, so it's glad to be here to share with you guys about the trusted cross-chain system, how different governmental data transfer with high efficiency. So why this topic come up? Because there is real scenarios in China that we help the government offices to solve the issues that they have the blockchain data silos. So we use a trusted cross-chain system to help them build the transfer from different blockchain systems and help them to reduce the cost to build their system. So here is the agenda. So I split this session into three sections. The first one is background and current status. So I will start to introduce why. Why it goes to this status, why they will need such system to break the data silo for the different blockchain systems, so how to stimulate them to use different kinds of blockchain systems in their systems to build their applications. The second section is what we do, what is our solution to help them, what are the tools we use, the architecture we use and how we use the cross-chain system to help them to solve this kind of issue. So the third section is we worked with the characters team. So we do some contributing to the characters team. So we build the connection from one interoperability system to connect to another interoperability system. So in that situation, we help to improve the connectivity. That helps the customer to build a wild connection in the cross-chain system. So from the trend we see that in recent days or recent years, we see the Web3.0 is very popular. So we see many news that different government has started to investigate the Web3.0, they investigate to different technology. So here I just use MacKenzie's words, I quote his word, blockchain technology is considered to be the core technology of the next generation of disruptive technologies after steam engine, power under the internet. So we all know that after steam engine, it frees people's productivity. After the electricity, it solves people's basic living need. So after the internet, it changes the way information is delivered. So we see is the trend is so obvious. So we see after the blockchain, it is a construction machine of trust to change the way value transfers in the whole human society. So as we see the trend, it's a necessary happen since so different countries have published policies to support the government blockchain systems to happen. So in the US, in the Europe, in Japan, in India, in South Korea, Southeast Asia, so they all encourage the blockchain system to develop. They have published many policies for them. Also in China, it is said to be the nation strategy. So now it's avoiding the virtual reality, it's focused on developing the blockchain system. So here we see the policies in China, published. So China actively promulgating policies to incentivize the blockchain industrial application. So in different province, like in Beijing, Shandong, Xi'an, Jiangsu, Wuhan, et cetera. So in China, different government offices have published policies to support blockchain to develop. So different offices has started many applications in different offices. And here is current status for the government fair application in China. So here I just caught a government blockchain project bidding sensor report in 2021. So it increased to 72 projects in production in 2020. So as a trend and the policies from the government push, so the applications just blooming, and we have the CIACT report that in 2020, all around the world, the government application percentage is 32%. So it's really a big value. So different government offices try to explore the usage in the nowadays life, so such as data sharing, digital identity, and optimizing that their government fair services improving their government efficiencies. So here we see the two tables. It's for the, the application of blockchain in government affairs attracts the international attention. So in different years, in different countries, they have down different government related applications. So we see the trend here. So in China, it makes the application blooming and the application supervision faces new challenges. So they say different offices. They made their own different government fair applications based on the blockchain. But as a policy admitted, and in China, these years, it also has more than 50 blockchain systems started. So we see a lot of blockchain systems and the different offices choose different blockchain systems to do their applications. So you'll see they have more and more blockchain applications, more and more blockchain data, and more and more smart contracts. But it falls new data silos when they use different blockchain because their blockchain systems cannot connect to each other. Their blockchain systems has different agriculture, have different architecture, have different data structure. So it's so blooming and it causes a several data silos. So it cannot be developed in the future trends that as several companies and the blockchain system is not maintained. So the applications, the data of the application cannot be read and the data will cause several issues for the government office. So to help solving this kind of problem, so we just see several key bottlenecks and the pinpoints for this kind of situation in four aspects. So from the technical aspects, so we see there is no standards and specifications, it's not unified. And the infrastructure is not perfect. So it's sad, it's lack of the high level design for the whole system. And it lacks the standard for the data and the API. And due to different blockchain system has different, you know, the stability, the security and they have different data structure, have different security mechanism. So they cannot talk to each other, they cannot share their data. So they cannot transfer the data. So the data from the different offices cannot connect to each other, they are not floating. So in another aspect from the cost. So it's difficult to share information because they are not using the same, you know, the hardware resources and the same software resources. They just build their blockchain application use their own hardware and software resources. So they cannot be repeated reused. So it's repeated construction. It causes a lot of waste on the infrastructure. So in the security level, we know the logic of the government of fair applications is very complex. And if the government of fair application use a separate blockchain system, maybe it has a lower security level. So even if they build the connection from different blockchain system and this blockchain system have a lower security level, it will be the security issues for the whole system. It will cause the information leak for the whole system. So from the economist, there is a shortage of blockchain professionals and the cost of operation and maintenance management is very high. So to face with these key botnets and the pinpoints, so we really think we need to reduce the technical difficulties and to help them quickly and efficiently construct of the blockchain system. And reduce the technical difficulties and the cost of internet connection to help them build a connection with the whole system. So to reduce the cost and to make the blockchain resources reusable and easy to expand. So it finally comes to the solution that it has a basic blockchain platform plus unified management and operation system with the ecological support service to support the up-level blockchain application. Thus, we will see how our solution is to using the tools and the infrastructure of the tools and how we use the cross-chain system to combine together to build the solution. So this is what we propose to like unified blockchain management infrastructure. This is a simple structure here. It's based on the cloud infrastructure. So it has a support the bus level. The bus is called blockchain service. It's used to manage different blockchain system to fast lead to build a blockchain system and to manage it. So upon the bus level, it has a unified blockchain management infrastructure. It supports the blockchain application and the services. So the customer could call the unified blockchain management infrastructure. It has a set where unified standards for different chains or different ledgers, different bus platforms to register. So it has a unified government affairs standards, resource allocation and governance standards, unified identity and authentication standards and operation supervision standards and ecological collaboration standards. So using the unified blockchain management infrastructure, it helps to reuse the resources. It can monitor all the hardware and the software together. People will know how to build the system. They use the system as a builder for the government. They actually need a builder for that. They control all the resources. They buy the resources, help them to build the chain. But actually when you are using blockchain, you have your separate key. It's also decentralized. So for the building process, we need such tool or such infrastructure to help them to build the whole solution. So after building the solution, they would monitor all the node status. Even if they have already built their blockchain application, they could register the blockchain application to the system. It also can monitor this. So how to support such infrastructure we need a bus level. So the Huawei Cloud's bus level looks like this. It's our capability per panorama. So it has the infrastructure with the Huawei Cloud, Hyper Cloud and Edge Cloud. So we use two blockchain islands. One is fabric, one is the Huawei Cloud ledger. So here I'm mainly to focus on the basic capabilities. If you need to support the app level management, you need to, in the bus level, to support the alliance management, node management, user management, operation, monitoring, alarm log, and several contract management. Because in the total management portal, you need to call the bus level to management for the blockchain area. And with better support for the applications in the government usage, we need to do some enhanced capabilities like the trusted sharing. So we just say in the background that there are several scenarios happening in the whole world, like trusted sharing and multi-part computation. So we also support the computing sandbox. So in different countries that page, we have several DID scenarios. So we also support the distributed identities. It follows the W3C standard. So in order to help to do the cross-chain services, so we have the enhanced ability of cross-chain services. So this is the architecture for the blockchain management platform. So in the architecture, you could say the underlying blockchain, it has a bottom layer blockchain platform and the other underlying blockchain platform. It's support to do the blockchain management and operation and maintenance management. In the bottom layer blockchain platform, it has a blockchain underlying technologies to support to use different blockchain abilities. So in the bottom layer blockchain management interface, this is a key point. So when we do the management platform, you need to make several standards. So how to let others know your standards? You just publish several interfaces. So they register their platform, they use a platform, they need to follow your interface standards. So this here, it has a unified security, unified operation, unified resources, unified cross-chain, unified supervision. So they register their platform, follow this standard. So the whole platform could work in all the standards. So the security in the system to build the whole chain network could follow the same security level. It will not have a shortage. So the hack or something will not to attack the shortage. So the upper level, it could do some management about the alliance management, node management. And for the yellow part, it's pluggable. So because in different government customers, they need to use their own identity system. They need to use their own process management system. So it's pluggable, they could just use their own system. And for better usage, we have also support several blockchain common components. Like digital identity, VC, very favorable credentials, trusted exchanges. So we also have the smart contracts warehouse. It has supplied several contracts of templates. They could directly use the contract template to deploy their contract and to develop their government application. So for the blockchain application repository, they have the government collaboration and the directory management and the digital archiving application as a sample application. They could just modify the application and directly use it to build their application and the solution very fast. So this is a basic business process to how to use this just the management portal. So I just use the three simple ones to just let you understand how it works. So the first process is creating a tenant and the user. So the tenant submit a request to the portal that he would create a tenant user. So the management will get the request and he will approve the tenant creation. So you would wonder why there is a management. So here the management is like the DAW, the decentralized anonymous organization. It could be a DAW because it's a builder. It will help the government to build in all the infrastructures for the blockchain system. So the builder would pay the money to pay the resources. It's just like a cloud. If you use a cloud, you need to use the cloud to buy the resources, buy the virtual machine, buy the Docker container. So it looks like this. So it's like a DAW or the admin who pays the money for the construction. So in the back technical aspect, so there is a resource delivered and the service deployment. So the end user will say, oh, the user is created and the permission is a standard. Then he could do creating and joining a chain. Then the management would do the approve and prepare the resources. So in the background, it's a resource allocation and the chain member update. So the last step is smart contract usage. So the tenant will develop and submit to the smart contract. So the manager would approve and archive and distribute to the contract. So in the background, it's running the contract. So to the user is installing the smart contract. So that is a simple process. So here is the complex process of the smart contract usage. So we have the contract template warehouse. So in the first step, the generally the analyst leader is responsible for the contract. So he would occur in the contracts templates and develop a contract based on the template. Then he will submit the contract to all the analyst participant for collecting the review. Just collecting the votes. Does the union approve we install such template, a such contract, smart contract? If they all agreed, so he get all the agreement. So he would just follow the process that send it to the administrator. Administrator is not, it depends. It's not only one administrator. Maybe it's many administrator just like a doll, you know? So the administrator group who may vote or just approve the smart contract and submit and record this information, then it will, if it agrees, so it will trigger the different, you know, different nodes to install the smart contract to help them build the whole solution. So this helps solve the issue. We just recognize in the pain points for the reduce the difficulties for the solution. But if they have built such chain and many chains exist. So how we could break the data silo and use the tracety-crossing system helps the data transfer from different blockchain. So let's see. So here, this page is here is to say using the system. It's like building the chain network. So we have the requirement that using this system, you are curious. So how the system would build for the government because if you use a system for the city or for a province and many enterprises would like to join on the chain network. So he could build such a primary chain for some offices and side chains for several offices with several enterprises. It forms like, you know, the chain network. So maybe use a system. It could include hundreds of nodes in this chain network to form a big chain network. And with, you know, I just draw a supply chain there. It's like when you have an existing chain and it would like to talks to the chain network. So how we could talk to the chain network. We will see that in the following page. So here I will say that the advantages of using the whole deployment management system, it will full stack cloud service. So it can dynamically scales in and out. It's intensive construction, low cost and high efficiency because the constructor can know how many resources is used. They can know the workflow. They can know what's the chain network looks like. Yes, because you build this chain network. If you don't know what it looks like, it's something wrong would happen. So your system would broken. It will influence some business. So actually it's really decentralized permission because each participant manages and controls their own blockchain nodes and the cloud resources. So only the constructor could help them to build but they have their own private key and public key. They could control their own node. So to support such kind of chain network, so the traditional network management doesn't cannot work on this situation. So we have done some hierarchical network management to support the outer large scale node networks. So in traditional networks, we use gossip to synchronize data but gossip has many redundant messages. So the network performance deteriorates rapidly with the increase of the node number. So we see the curve, it goes down very fast. So we just figure out so we use the hierarchical management to manage the federation chain network. So the data synchronize from the core to the edge and reducing the redundant messages and reducing the impact of the performance. So in large scale network, we also use a set kind of consensus algorithm for them, like in traditional PBFT algorithm. There are several processes like pre-repair, pre-submit, et cetera. So each step, each node will send messages to each other. So the message complexity is very big. It's all in square. So we use a wrapped consensus but we consider the security. So we combine with the T, it's trusted execution environment. So we leverage the T to execute the consensus, call logic, convert to the BFT issue into CFT issue. So in the meantime, we retain the BFT consensus security and improve the efficiency. We see the graph that the messages go to different nodes only once. So it greatly reduce the message complexity into the ON. So it's more suitable for the large scale network. So the large scale network is from here. So we build such hundreds of node large scale network. But how do we make the connection from side chain A to go to call side chain B or really go to the supply chain? So here we need to use our own cross-chain method. So it's a consortium cross-chain method. So we use a relay method for building the cross-chain method. So we see the several pages before that the chain network. There is a primary chain you remember. So we build the cross-chain solution and cross-chain middleware on different node. So it forms that each circle in the chain network could be a relay. They could transfer data with transfer. So I just say introduce a process. So if people want to separately use a cross-chain solution, they need to register their chain to the transfer relay and the relay know the chain and they need to authorize what data the chain A could access. Like we have several authorizations like the several contracts. You could read the contracts or you could write the contracts or you could read the letter. It's in different authorization level because if you read the letter, you could read the local contracts. You'll read more data. So we make it very specific. So the process is that if you send a cross-chain transaction, it will generate proof. That's to prove that it's from your chain and the proof will put the hash code of the proof and hash code of the cross-chain transaction to the relay and send the message directly to another cross-chain component. Another cross-chain component gets this information and verify from the relay. They know, okay, it's from you and the message from you and he will get the message and he will write the cross-chain information to the blockchain B. And this is our first phase. So we use a two-phase commitment and he will get the response and the response proof back to the submeter. So the submeter will also verify the proof and the result to written in the blockchain B. If it's all success, the lock will be released and the data will really written to the blockchain to keep the atomicity and the finality. So in this process, it's only for the both right solution. If you use a read solution, it's more easier and not so complex. So in order to optimize such a process because this process is two-phase and you need to lock the data to help protect the atomicity. So we have made some improvement for this. So the cross-chain relay would transfer the chain proof keeping the transaction trustworthy. So the traditional consulting platform have different underlying technologies and make some data silos as I mentioned before that the government use a different blockchain system to make their different applications. So if we use such cross-chain interaction system, if you don't generate the proof, it will cause a data tampering, many in the middle attack and the data loss and insufficient privacy protection. So if we use a proof generator, so in the blockchain A, you just submit to pre-commit proof and the acceptor and pre-commit the proof. So at last, if they all verified and the submitor commit to the proof and the acceptor commit to the proof. So when we finish the two-phase process, it will finally write the data to both chain and in the process, each step will cause a rollback for the whole process. We use a chain code level counterlocking and a complete rollback mechanism to ensure the atomicity. So here we see that from the relay, we have some cross-chain component to make the data transfer. So if you use a single-point component, if it will cause a single-point failure and it will cause a single-point failure, the process will not continue and the atomicity need to be insured. And if the account is locked and can't be unlocked in this scenario if the component is broken. So we make the horizontal expansion for expanding many cross-chain components to support when a cross-chain component is down. The other component will take over your process, take over your transactions and to go on the process. So how to achieve that 100,000, more than transaction per second with a high concurrency? So we use a linear network mode when cross-chain traffic is heavy so it will become the bottleneck and cause a service congestion. So if we use support to the horizontal capacity expansion networking, we could expand for the release service to build different cross-chain channels. It will make it support high throughput transactions in different channels and it will not influence each other. So as I introduced before, so we use a fine-grained permission control for the cross-chain contract access. So the overall authorization solution would expose the contracts other than the smart contracts on the blockchain. Bring in risks of privacy disclosure and authorize the tampering. So we use a fine-grained authorization for specific contracts read and write or for the leather read. So it will make the cross-chain more comfortable and secure. So we integrated the DID to the cross-chain system. So in this system, we will help to build influence, we will help to build a unified identity system because in different blockchain system, they have their own ID system, identity system. So if you build the authorization for several identity, if you have more identities or you have the off-chain identity, it cannot be recognized and it may cause the identity forgery. So we use a DID to just map an ID group for such kind of authorization. So this group can only read several contracts. This group can only read, write the contract. So different ID systems could map to this ID. They use this ID, they could just improve the efficiency and reduce the risk of identity forgery. So here we have did some, use some of their knowledge techniques to help prevent the information anonymization to strengthen the privacy protection because here scenario that if you are the user in blockchain you want to ask some proof in the blockchain B. So they will ask you to show your identity through the process, your identity will be exposed, your privacy will be leaked. So if we support several contracts integrated with the ZK knowledge proof, so you just show the proof that you get several, you get several value is verified. What is a verification? It's an equation that you satisfy the equation. So you show that to another chain and another chain to take the equation verification proof to the related test and verify, it will help to satisfy the situation to protect the user privacy in the cross-chain situation scenario. So also to satisfy Chinese standards for the cross-chain system to build such kind of chain network, we need to satisfy the national standard and international standard. So we need to build such solution for different systems, we need to support a different kind of deployment. So this is our solution to build the chain network and that makes a different node in chain network to talk to each other, use the techniques and use the cross-chain systems. So the cross-chain system is integrated to the chain management system. The user could just call the interface to build the connection. If they could register their chain to the system and the cross-chain system would help them to build the connection and they just send the cross-chain transactions it would work. So it will solve the problem of reduce the technical difficulties for the interconnection. So the last part is we did some contribution to the characters to improve the connectivity. So we contributed to the plug-ins. So we have our TCS, it's Trusted Cross-Chain Service. We just made some plug-ins for connecting to characters. Characters is also a HyperLider project. It is for the cross-chain services. So this is a first cross-chain service interoperability system to connect to another interoperability system. They could expand different connections because if you use the interoperability system to connect to a chain, you need to develop such SDK or develop such interfaces to face different chains. So if we connect together, so they could use what we developed and they could use what the characters already have in the ladder. So it's a Boothman solution. So it's a flow for characters to connect to the TCS. So the characters is a component used to connect to, the agent characters is a component to TCS to connect to the characters and it implements the interface of I plug-in ledger for them to connect. So also if characters is written in TypeScript, so our TCS is written in Go. So we need to use an open API to generate the Go interface, to generate the interface, TypeScript interface and the validator TCS can register the verifier and act like a normal validator. So the characters species is logical, can send the transaction and monitor the ledger of the TCS. It's actually not monitor the ledger of TCS, it monitors the chain connected to the TCS. So this is a stream from the TCS to characters. So the process is that agent characters will connect directly to the verifier and call the transaction to get the proof and the verifier can access the blockchain through the validator to get the info. So we both need to accomplish the interface for the TCS. So that is what we have done and that's all for the sharing, it's what we have done to use, to what we recognize the pain points and how we did our solution to solve the issues and to expand the connection, we just work with the TCS. So that's all for today. Thank you so much for coming.