Thank you. I am particularly worried about disappointing the host and everyone, because I don’t want to talk about too hard-core things. I was in Shanghai for the past week, which is the very well-known Shanghai Blockchain Week in Shanghai. There are many people and many activities. . So I talked to a lot of people in the past few days, so the voice condition is particularly poor today, but the things we talk about are very important. The important thing is what we think about open source and openness. So what I want to share today is the multi-chain concurrent Web3.0 world.
A brief introduction again, I am a veteran of the blockchain industry. I joined the blockchain industry and have done a lot of things: exchanges, and now I am doing public chains.
The definition we give to Web3.0, in my heart it creates a new decentralized Internet, today is the Web3 conference, if I discuss with you what is the definition of Web3.0 and what is the definition of an open Internet at this time, there is no need. So in my heart, creating a new decentralized Internet world is what we want to do. We made Nervos under this framework, and we are very happy to receive the invitation from the Web3 Organizing Committee to share it with you here. At that time, I discussed with Dr. Jia, and I said, what would be more appropriate for me to come here to talk about something? I will say what you think is appropriate for me to say. Dr. Jia said, you also use the Rust programming language for development, can you talk about Rust? I said yes, I will definitely speak Rust.
First of all, the Rust programming language is not something in the world of the blockchain. The blockchain was born, it is the world outside the blockchain, and it is something at the level of a larger technical world. The most important infrastructure of our industry is all cast through the Rust language, which is very, very important. I would like to say that the highlight moment of the Rust language in the blockchain industry was really established in this venue about 4 years ago, which is the Hyatt Hotel and this venue where everyone is today. What happened 4 years ago? In mid-September 4 years ago, the Ethereum conference was held in Shanghai, and it was at this venue. About a few hours before the opening of the venue that day, the Ethereum network experienced the most serious Dos attack in history at that time, and that attack was the most severe attack encountered by the Ethereum community. That is to say, hackers organized and premeditated at this conference in Shanghai, when all the core developers of Ethereum gathered in Shanghai, a general attack on the network took place.
I still have a deep memory of that attack, because I was the founder of imtoken at that time, and we had put the 1.0 Alpha was released. I held a mobile wallet and I was going to demonstrate it to many people. I wanted to demonstrate the world's first mobile wallet at that time, and demonstrate the transfer of Ethereum on the spot. As a result, after the network crashed, my transfer became difficult to demonstrate and unable to operate. I was very anxious, so I was very angry to see when the network would recover. Some people may know what happened after that. In the lounge next to the venue, there is a photo of Ethereum core technology developers gathered in that small conference room. Some of you knelt on the ground, some Sitting on the sofa, holding a computer and anxiously solving problems.
How was this problem solved? The client that survived at that time was written in the Rust language, and the name of that client was Parity at the time. This team is in the same line as the Substrate team and the Polkadot team we know now. This is the back story. At that time, the Parity team implemented an efficient Ethereum client in the Rust language, which can be said to have saved the network. At that time, if not all the mining pools quickly switched the high-level language client to the Rust Parity client, if the network was beaten to the ground, there would be a fork, or it would never run again No, there is no such result as today's Ethereum, and there is no such thing as the industry has developed to today. So as a blockchain developer, we are grateful for the client implemented in the Rust language at that time, we are grateful for the Rust language in this world, and we are also grateful for everything that the blockchain has brought us. So thank you open source community.
In order to give back to the contribution of the Rust language, as a blockchain community, we are also We have participated in many Rust conferences in China, and we have also combined Rust language with blockchain, and held many offline activities around the world. Including that we held the first Asia Rust technology conference in Beijing last year, because there is no preparation for this year's epidemic situation, but if there is no epidemic situation next year, we hope to continue, and we hope that we can continue to hold this conference together.
The second sharing, the future blockchain world must be a multi-chain interconnected world.
Here I want to introduce a concept called interoperability 2.0. What is interoperability 2.0? We don’t actually have a definition of 1.0. I want to give you a very simple explanation. What is 1.0? Just imagine, some time ago our hottest project in the blockchain was DeFi, and the hottest project in DeFi was liquidity mining. For the first time, liquidity mining puts a model in front of everyone, an innovation called nesting dolls. That is, you can put your assets into one project, and you can also pledge the liquidity token of this asset to another project to get TokenB, and then superimpose TokenB on TokenC. Eat three fish. The community calls this model the nesting doll model, which is the mixability and interoperability between smart contracts on a chain. We call this combination of a virtual machine on a chain and a smart contract platform Interoperability 1.0. When it comes to 2.0, can we realize the interoperability between blockchain chains and chains, that is, nesting dolls between chains, and now we can actually do it.
When it comes to interoperability 2.0, I would like to review the pain points brought about by the current interoperability ,what is the problem.
First of all, from the perspective of customers, what users contact with the blockchain is the wallet, and each chain has its own Exclusive wallets, some wallets can support many chains, but in multi-chain wallets, users have different accounts and addresses for different wallets, and users have to learn and understand this on each chain. How to do the operation on the chain. If we want to cross this chain with each other, do we have to make a new wallet for users to learn again? We don't want users to learn. Can users use their familiar wallets without changing their habits, so that they can easily enjoy multi-chain connectivity and the benefits of cross-linking. This is from a user perspective.
From the perspective of a developer, if the developer wants to serve all users, he will find that the users of the blockchain are It is divided into different chains. I want to serve users of Ethereum and users of US. He needs to re-do its application on each chain. This cost is very high. Can it be done? Can one application run on all chains? Or allow all users on the chain to become its users? How can it be done only once? In the early days, we had iPhones, and later we had Androids. Developers had to make applications on Android and Apple IoS. These development teams are doing the same function on both sides at the same time. In fact, the cost is very high. Finally, we have WeChat, and WeChat has a small program. You only need to do it once in the small program, and both sides can take it all. Therefore, the number of users of Mini Programs is growing very fast. Now we no longer want to make cross-platform applications. We want to build Mini Program applications. One platform serves all users, which is what developers want.
As for assets, the cross-chain technology of assets is very mature, and it has been well researched by people. To be honest, the biggest problem is that efficiency and security are always irreconcilable things. When you focus on efficiency, you can choose centralized cross-chain, witness cross-chain, and multi-signature cross-chain. When you need security, you need two chains to have each other’s SPV nodes to verify each other’s light nodes, and the efficiency will become very slow and complicated. However, the compromise between efficiency and security is different in different scenarios. Can the user be so simple that in different scenarios, someone and infrastructure can help him to complete the cross-chain, and he does not need to make any choices. Woolen cloth? With these pain points together, we are wondering if we can do it through technical means?
So we leveraged the capabilities of the underlying platform to deliver Interoperability 2.0. Interoperability 2.0 depends on a very unique feature on the Nervos platform, and we have made a very vivid analogy for it. The Nervos chain has a very special ability, that is, it is very good at learning foreign languages. Each chain has its own protocol, and each protocol is a foreign language to the protocol of another chain. The two chains can interoperate and cross each other, that is, the third party you want to find can speak the language of the two chains, and then translate the language of one of the two chains to the other chain. But if there is a person who is gifted, he is naturally smart enough to learn 8 languages, and can easily learn more new languages. Then he can naturally help people from different countries to communicate better, and he will do centralized translation between all people. If you have this ability, can you simulate the protocols of other chains at the bottom layer? This is the core capability of Nervos. Based on this capability, we can easily transfer the assets of all chains. On the upper layer, developers do not need to make additional new applications. You can directly connect to it without changing the protocol. When Nervos comes up, after connecting it, other assets can be crossed over and assets on other chains can be operated at the same time. We only need to develop once, and he can develop on whatever platform he likes, and all platforms can be supported by compatibility.
We have not gone out of the circle here, the real blockchain world is going to help all users solve problems, the district The largest world outside the blockchain is called the Internet. The Internet already has many protocols and standards, and there are many users behind each protocol and standard. If our blockchain understands Internet protocols, speaks the language of the Internet, and is compatible with Internet standards, we can quickly and conveniently provide all Internet users with an opportunity to access and use services. All Internet users have mobile phone numbers, and almost all Internet users have email addresses. With mobile phone numbers and email addresses, you have access and opportunities. We can easily turn Internet users into blockchain users. It's a bigger opportunity, a scenario that we want to do. This is what we want to do with Internet Interoperability 2.0.
Finally share a public account, here we have now achieved support for the Ethereum ecosystem, we can already With the ecology of Ethereum, the wallet of Ethereum, and the application of Ethereum, it can be directly supported. There will be more in the next step. If you are interested, you can follow our official account and continue to follow us. Thank you all again.
Welcome to join the official BlockBeats community:
Telegram Subscription Group: https://t.me/theblockbeats
Telegram Discussion Group: https://t.me/BlockBeats_App
Official Twitter Account: https://twitter.com/BlockBeatsAsia