Hyperledger Foundation Hyperledger Global Forum 2021, 11 Jun 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Fabric-IBC, Besu-IBC Combined with IRITA - Bringing... - Zhiwei Hu, Shanghai Bianjie & Ryo Sato

Description

Fabric-IBC, Besu-IBC Combined with IRITA - Bringing Interoperability on Enterprise Blockchain - Zhiwei (Jeffrey) Hu, Shanghai Bianjie AI Co., Ltd. & Ryo Sato, Datachain, Inc.

IBC (Inter-Blockchain Communication) protocol is for communication between heterogeneous blockchains that does not require a trusted-third party. In this presentation, Jeffrey Hu from Shanghai Bianjie AI Co., Ltd., and Ryo Sato from Datachain Inc. will jointly give a presentation of an introduction about the IBC protocol, its design, IBC in public chain, IBC protocol implementation architecture in Hyperledger Fabric, Hypderledger Besu, and use case of international trade and IRITA Hub for interoperability with many other different blockchains as well as legacy systems in BSN environment.
Sessions Details & Slides (if available)- https://sched.co/j3cz
Access All Sessions: https://events.linuxfoundation.org/hyperledger-global-forum/program/schedule/

----
Hyperledger – Open Source Blockchain Technologies

Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use

Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory

Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter

Follow-us on Twitter @Hyperledger

Learn about Hyperledger Membership: https://www.hyperledger.org/about/join

#Hyperledger #HyperledgerGlobalForum2021 #Blockchain

A

Okay, so thank you for joining us. uh Originally, we have a plan to introduce ibc at first by jeffrey and then I'll, introduce our current product base, fbc or fabricabc, of course, but you know.

A

Video for jeffrey now, so I want to start our session.

A

A

Okay, so now I skip an explanation for overview of ibc portal. Sorry, but it's a jeffrey part. So I start my session about our product about ibc so based on, obviously fabrication cross framework or our hyper hi.

A

Sorry for existing convenience.

A

So uh before my presentation, uh let me introduce myself: uh I'm will sato a senior blockchain architect at data chain. Data change is a tech startup working on interoperability, solutions for blockchains and I'm working on open source products. We have such as fabric ipc and also these several interpreted projects.

A

So I'm going to talk about the design of ibc modules such as base ibc and fabric ivc. Then I will show you an overview of our cross framework, which provides a question population like academic swap on top of ipc.

A

Finally, I'd like to introduce our current work on hyperledger loss- okay, oh sorry, okay, so ibc, utilize, cross authentication for verification, which means lecture-wise on-chain, like client, verifies a header on the state in the jx.

A

Also, there is a relayer that fetches and relays outpoint packets between later x and y, as well as block headers of each blockchain. A packet consists of a payload from one blockchain to another and verifiable proof for it.

A

There are two important functions to achieve cross-authentication, namely verify membership and check header. These function names are actually a bit longer, but we are simplifying them here in the receiver chain. Measure y on this line check header is keeping a header of leisure x and updates current state on leisure y also verify membership is giving a key value pair and its proof then verifies physics appear exists in the leisure based on the proof.

A

This function should make use of underlying ledger structure, so we design and develop such functions for the hypothetical basu and hypothetical fabric.

A

So I'd like first to explain the concept of base ibc for hyperledger basin. The grant works in a similar way as the background of ethereum works in basic. A block header contains a root hash above macro3, consisting of all account stretches.

A

Each contract's account range is also a marker tree and proofs for a keyboard pair on each stretch can be obtained from base nodes. As such client state maintains a root hash of a specific contact account and updates it on receiving a new header.

A

A specific key variant pair can be verified with its markup path and the root rash. So refine membership verifies a key value pair with its market path and the root cause.

A

So ibfd2 base consensus algorithm features a dynamic var data set, so we also need to verify it in base ivc. A veritas set is verified in check header in furnace case. Verification of such a dynamic set is easy, as you can verify a newly elected operator by checking the approval of the last five data sets. However, this is not the case for inter-blockchain communication.

A

Tactically typically, not all block headers are presented. We think it is not realistic to relay all the block headers between two ledgers, so we introduce a trusting period inspired by tendermint and cosmos. Here we have four variations: a b c and d for a valid duplicator. Then another block header with pareto, a b d f, is received.

A

If the interval between these two blocks is within the trusting period, we can say a b and d are trusted, thus skipping verifications of these three parameters. I think this is a reasonable assumption and convenient for lightweight verification.

A

Please refer to our documentation for more details.

A

Okay, so, let's just move on to fabrication.

A

Hyperledger fabric manages a world state differently from hyperledger basin, since a fabric does not provide inclusion proof for h3 structure, we need to come up with a different idea for verifying each state fabric, ibc utilize proposal, response or read, write set for verification.

A

B

A

Is that if you query a change code, you will get a read, write set for corresponding key value pairs with an endorsement signature. We use this signature as membership proof in fabric ibc, here in leisure x, a relayer invokes a chain code to query specific given pairs to its world state and returned proposal. Responses from endorsers that satisfy an endorsement policy mega packets to be relayed, then in leisure y the packet is verified using verified membership with an endorsement policy for ibc.

A

Here united states uses andersen signatures for verification.

A

So speaking of endorsement policy for idc high biology fabric does not support on-chain functionality of synchronization upon the endorsement policy with other lectures. Moreover, an endorsement policy can be dynamic. On runtime.

A

As such, we designed to provide a policy as a property for cloud in rajawi, namely, you can call create client to set an ipc policy and call update client to verify a new one with the old one and then update it.

A

This policy should be designed to be compliant with the original region x, endorsement policies, the cloud integer y checks and those signatures according to the ibc policy for verification.

A

Oh sorry, geoffrey hi.

A

We change podcasts, holder, okay,.

B

Yeah yeah, please continue please deeply sorry, for I met a terrible, never problem. Okay,.

A

A

Okay, so next we would also like to mention how we make use of these ibc modules for cross chain operations. We have developed a cross framework which enables developers to implement a cross chain. Smart contract on top of ibc cross framework mainly consists of two modules. The first one is a transaction coordinator.

A

This coordinates a request to execute multiple contracts among blockchains it authenticates each contract call within the request, inbox them and manage their results.

A

The second one is a state store, and this is a wrapper for the contract state store with a locking mechanism for enabling cross-chain transactional operation, such as two-phase connect with this mechanism. You can first lock a key before updating, then after checking everything's even right, so we commit the new value to it.

A

Cross framework supports an atomic commit among blockchains, for example, suppose we have two lectures x and y with two contract transactions a and b respectively that we want to execute atomically.

A

If contract transaction a fails on measure x, the result of contact transaction b will not be reflected in chain y. We believe that cross framework will further expand the application scenario of blockchain interoperability.

A

So, as a practical use case, we conducted a proof of concept using ibc modules and cross framework for delivery versus payment dvd settlement, the ethnic swap between asset and payment token for global trade operation.

A

In this project, we teamed up with ntt data, a company that has a blockchain-based trade platform here. The asset, of course, is maintained in hyperledger fabric as a trade platform, and the payment token is maintained in scandamid network as a payment platform with cross framework, we can achieve a cross-chain atomic operation between two networks, thus mitigating the need for a trusted third party, such as an escrow account also with cross-framework.

A

We can reduce user interactions in comparison with another trustless method hdlc. It requires both an exporter and importer to monitor the other party's transaction and respond to it appropriately, which results in a complicated use. Interaction during a trade.

A

We believe the scheme that cross framework provides reduce the burden of trans settlement. We continue working to commercialize this technology on threat platform. We also seek opportunities, try it in other application areas.

A

So, lastly, in my and I'd like to talk about our current work on hyperledger, we have released a hybrid lab called the ue as an integrable solution for the for the hyperledger family, and it includes related products such as fabric ibc, a base idc and holder ibc.

A

We are expanding this lab to add a framework for cross chain applications like cross framework, as well as tools like explorer for question transactions.

A

And they were initially developed and are mainly maintained by data chain. For now, however, bianchi ai is also supporting and contributing to the ue lab. So please refer to the love page for more details.

A

Okay, so my part is over and.

B

Okay, can you hear us see my screen right now? So uh yeah? Okay, let me start with my my part of the presentation um yeah. So uh actually, uh for this session with uh I and the leo sum for the edition team, uh we'll talk about the ivc particle, how this kind of the ibc particle can be integrated with permissioned enterprise blockchains can bring this kind of interoperabilities.

B

So um actually it is uh deeply uh sorry for that uh late for the presentation, so I will just make a short, very short introduction for myself and also the the binge here.

B

I am the research director of the bingo team right now, heads for the strategy and also the technical research right now also the ecosystem system, development of png also and actually binge is a high-tech enterprise in china, and we are also called that team of the a public blockchain project called the airstat, and we are also the kodak team for contributing to the bsn wing, chun open permission, blockchain and also a permission also a blockchain project called irita hub, which is focused on the interoperabilities so uh and and the little song you you give, uh or you already give a self introduction before, or maybe you want to?

B

Okay, okay, I will move to the next page, so um I believe, with the little nilsson have already uh introduced a lot of about the base of ibc fabric ipc, it's kind of the module based on the ibc particle, so I, for my part, I will focus on the ibc particle this introduction and also the differences and how this kind of the ibc can be applied in the infrastructure level. We practiced in the iota hub how we combine the ibc and the eye service, which is called the industry service.

B

So what is ibc particle? It is short for the inter blockchain communication particles, which is proposed by the cosmos project, and it's a focus down the heterogeneous blockchain's communications. Also, it assumes uh no topologies between this kind of network how they are connected, so it is also follow a design idea quite similar to the tcp ip. So it is abstracted how the like the the ledgers, how this connection works and how this data pack can be transmitted between the different networks.

B

So here are also um a picture that can show this kind of ability at the red corner of this uh slide, so each dot you can see here it. Actually it is a blockchain network, so um each network can be connected with each other freely and trustlessly that can almost even it can become a circle that's connected with each other, so it assumed not a hard spoke topology between this net kind of network. So it's really like a tcp which can be fully leveraged in this kind of question abilities and for more information.

B

You can also refer to this website, so what is ibc is, and what is it is about. Actually, there are many kinds of misunderstanding about ibc and also the cosmos project. Well, the ibc particle is actually is not only about the application layer.

B

Particles like some people may argue that it only handles the asset causing chance the production. Actually, it is not because ibc is really handles. The data transport.

B

B

Actually, it's a quite on the communication layer so.

B

Can be verified trustlessly by another blockchain and it's not all another job and.

B

Also, our no root chains in this kind of networks, so it is also another layer. Two particles like we can see uh many solutions in the example right now, uh according to this kind of architectures, so ibc, uh this kind of module actually has some core uh concept in the whole particles. So the first one is uh for sure is the ledger, or we can call this distribute the ledgers it's abstracted like. um We can see that the ledger.

B

It is a state machine and also it stores a key value in this kind of a letter. So um and if we could go deeper into this kind of ledger, we can see the uh this uh the module here, which is the stop component of our ledger. It handles the state transition between a state machine, and also um we can see like many kind of smart contract, can be seen as a module on uh like on blockchains.

B

So um it is also a special module called ibc module, which is specifically handles the question transaction into a ledger. So this is called the ibc module, which it can uh condense. Also, another kind of uh components like the client, which is a verify another uh which is a litecoin to verify another uh blockchain's transactions. Also, there are connections to maintain the state consensus date and also the channels to uh for the message, delivery ordering and also the uh like the authentications and here is also another very important concept.

B

I also mentioned uh also notice that already questions in the in the session. What is your layer? Actually, the layer is off-chain like land process that can just focus down the uh message uh transmit, uh so uh the actually uh the both the ledger, a or letter b do not. Try do not need to trust the layer, because uh these two blockchains verify each uh each other's transactions respectively.

B

So relay just translates kind of a message to between these ibc modules and the client inside of this ipc module will verify the message from another blockchain so that I also so both ledger. Don't need to trust this relay, so it is not a gateway or third-party risk in inside of the layer. So if there is at least one relay is working, the whole question works.

B

So here is also a flow for this kind of transaction because of the time time problem I may go, and I may do not have enough time to go deeper into this, but from this kind of flow you can see that it's quite like the tcp ip flow, because the message will go from the top level uh go deeper into like the connection and also go to the consensus, and this kind of message will be transmitted to a relayer, a biore layer to a chain b, and the transactions will be handled through this kind of consensus on the chain b and also go back to the go, go up to the application layer to uh on chain b.

B

So this is basically a transaction flow of this uh whole ibc process, so there. Actually, there are many kinds of differences between the ic and other particles, like we also mentioned, compare all compared with the polar dot and the customers are maybe idc. Actually it is not the same, because uh the whole ibc particle is uh the bottom up.

B

Well, the pokedex is more like a sharding particle, so this is a root chain, but when we see ibc, there's no kind of misreaches in the enterprise blockchain and we can also see there are many question projects like characters and vividly hyperelectric right now, but ibc actually is not assumed that can connect with only information blockchain but can also connect with the permission, links, blockchain like or even centralize the system with using the protocol. That's been proposed by the dnca team.

B

So here are two examples, though. Actually, uh I believe nelson had already mentioned about the data change, integration with fabric ibc and other modules, and another example I will I would like to share- is the irita hub. It can leverage the ipc and also the iservice, to connect with different blockchains like the public, blockchain and consortium blockchain, and also the legacy systems.

B

So it levels mainly about two techniques. So if another blockchain that can already implemented the whole abc particles, it can like, like the fabric ipc, uh it can uh directly connect it on the aerial hub we developed and also there are also many kinds of blockchain that haven't been implemented in the ipc part right now. So we also can leverage the iservice on the iota hub and for this kind of module we also uh used.

B

Another uh tools called we called it for the moment is called the smart relay because it needs to um to know about the application. Semantics of the message is transmitted compared with the relayer transitional layer. I just don't know about the message. What is what it's about so you can you can uh here? You can find more information about this every hub on the bsn environment.

B

So this is the whole process of the how ie service can work between the different networks, so the server exp provider can register their abilities and their functions as a service on the iota hub and with this relayers, which we call the iservice over the ibc, because ibc is a communication layer and I serve is more about the application layer. So the this kind of service definition can be transmitted to another, which we call the app another blockchain and the client.

B

Our user can request this kind of service on the app chains to obvious, uh with the service fee that we that he can call this kind of service, and this kind of service will be uh information will be transmitted by the relayer to back to the hub and service provider. Listen to this kind of information and transactions. I will give back to the response and this uh response and the result will give back uh to the client on the app chain. So this basically is a whole process of the I service.

B

So with kind of with this kind of uh abilities, uh we are right right now developing on a bsn network. Right now, the idler hub can connect with the fabric uh using the module uh and it can be connected about the layer on the other hub, which we believe will be realized later this year and with the smarter layer. We can also connect with different kind of information blockchain like physical, because superchain and other construction blockchains.

B

uh The users uh need to know about the service definitions through the smart layer, but also can uh acquire it like many kinds of the like the data from uh training, also many kind of service on different public blockchains. So it's quite useful and we also we are also implementing other kind of the application layer uh particles.

B

Besides the functional token transfer, we are also uh implementing a question nft right now so later on, you may see some applications about the empty questions uh like between the permission, blockchain and also permissionless blockchains connected by the id hub on the bsn environment.

B

So this is because, basically, the contents I want to share for today and at the last of our presentation uh we also there are some contacted information about our two teams, benji and the data chain. You can always find me here. Thank you.

A

So much also in a deep.

A

B

So is there any other questions besides the relayer.

A

No question no questions.

B

Yeah, I saw the question there about the layer. It really actually is not need to trust it. Any futures.

A

Okay, so thank you for joining us and yeah. If you have any questions, please contact us.

B

Yes, thank you.

A

B