Hyperledger Foundation Hyperledger Global Forum 2022, 6 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Demo: Interoperability with Hyperledger Lab YUI - Koji Matsumiya, Datachain

Description

Demo: Interoperability with Hyperledger Lab YUI - Koji Matsumiya, Datachain

This session covers the basic idea of YUI and how to use YUI to achieve cross-chain transactions (interoperability) between different blockchains. YUI is a lab to achieve trustless interoperability between multiple heterogenous ledgers using Cosmos' IBC protocol. As YUI supports permissioned blockchains such as Hyperledger Fabric, Hyperledger Besu, Hyperledger Iroha and Corda, enterprise companies such as NTT DATA, JCB and HITACHI have conducted proof-of-concept using YUI. The session will explain how to implement YUI modules to enable interoperability in those use cases above.

Sessions Details & Slides (if available): https://sched.co/176nS
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

Discord: https://discord.gg/rVCn4j7UFd
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 #Blockchain
License
Creative Commons Attribution license (reuse allowed)

A

Hello: everyone, I'm coach, maximir I'm, a software engineer at the data chain in Japan, welcome home joining me in this session, I'm going to talk about hyperleader levels, UE that enables interoperability between multiple different blockchains.

A

The main purpose of this session is to show you what hypolitical level U is through the demonstration.

A

First of all, I'd have to describe what you is as I mentioned earlier. You is a hyperleader lab project to facilitate into availability between multiple heterogeneous blockchains, as shown in this figure of several modules and tools, particularly important components as the ABC module and the layer.

A

This will be explained later and then you have the closed framework for more complex to execute distributed transactions.

A

We have already released close framework on GitHub, but we have not yet integrated into the UI. So I'll skip the details of cross framework.

A

There are severely important aspects of UAE. I have picked out three there. First, you it doesn't require additional trust by unchain verification.

A

In short, it means that even when using UI you can only rely on the security model or the blockchain you are connecting to next, you suppose arbitrary date transfer and computation.

A

This means that you can execute arbitrary, smart contracts with each other. Third, you provides abstracted communication methods. Developers just need to design application that do not depend on the counterparty blockchain. Therefore, it allows us to develop change Independence.

A

If you need more details, we publish a document named on named UI, Docs and hyperledger levels on GitHub.

A

So, let's move on to the next app in IBC is an implementation of the inter blockchain communication protocol called ICS by interchange, Foundation NBC is a layered protocol, as shown in this figure in IBC, we Implement modules for each of each load and combine them to achieve interoperability.

A

For example, the loading module is required to link the application to the IBC. The current module behaves as a right client to verify, broker head turrets on the other side and the connection module provides a bitter connection. Module provides the ability to safely establish a connection between two blockchains and so on.

A

Besides I show the dependencies between each module in this figure, but it this doesn't matter in this session.

A

The next trait is just an example of sending a datagram by UI. You enables into availability with the IVC based light, Grant method, light clients core component to trace and verify counterparty States at local.

A

In order to communicate with new chains. We need a new light grant for new chains.

A

One more important component is a layer. The layer has a load in the physical connection of IBC, Elena detects and transmit packets from one to the other, and the layer has two important properties, permissionless and trustless.

A

The layer works of chain on any third particular can operate it. In spite of this, the layer remains trustless because of using the light Grant.

A

Even if layers in the force information, the blockchain to which a packet is sent from the layer, can detect the connect, detect the correctness By. The Light current now I'll show you a sequence of sending a packet between two blockchains I assume to connect Cosmos and hyperledger fabric. As an example, I want to go into details of Cosmos.

A

One key point is that Cosmos has a tendermint for its consensus. Algorithm ETrade client is included in IBC gold Repository fabric, as many you know, is a permission distributed Ledger. We call this right ground to the fabric Grant.

A

Our client is included in UI fabric IVC Laboratory, and it provides a layer as a UI layer.

A

Now let me explain the sequence: the cosmos in the packet to hyperledger fabric in Step, One, a fender, creates a packet to be sent to public to send to public in Cosmos next until step, 5 that your layer detects the packet and gets the latest hitter from Cosmos and submits it before sending a packet to fabric, because public site needs to know the latest states of Cosmos, stupid, Fire pocket and then you layer sends a packet to fabric and fabric verifies, verifies 8 by 10 Diamond ground.

A

You have packet is verified how to call the function according to your packet.

A

This is a part of sequence for sending pocket using UI. Originally more steps are required, but some committees for Simplicity.

A

There are various methods to achieve interoperability, but let me jump to the conclusion due to lack of time. The right grant method is more secure, but it has low extensibility and high verification costs.

A

Now this is a time to show your demonstration over here. This demo is a twinkle transfer using ics20 between public and Cosmos. The ics20 is a standard used for the token transfer, but let me skip the details.

A

You can try this demo by accessing the fabric. Cosmos IBC demo, Repository, the main components are used layer, UE, fabric IVC and IBC. Go so I'll describe a demo scenario.

A

It's assumed that token will be sent from Cosmos to fabric at first. The sender initiates token transfer on Cosmos side and then the existing token is locked. Next, the U layer, laser packet to the fabric side.

A

Let's keep updating the right ground at this time for Simplicity if I receive. If a receiver receives a packet on the public side, new token is minted equivalent to your lockdown.

A

Finally, a receiver responder acknowledgment packet on the sender accept it on the cosmos side.

A

Here is a directory structure for Cosmos IBC demo. The chain code and code chain code and contract directory include include on the IBC application that references transfer, module for fabric and Cosmos.

A

The networks includes environment for both chains. The layer directory refers to your layer. The test directory has a script and utility for the scenario.

A

Sorry next, let me skip this slide and I'm also skipping this right.

A

A

I've explained an overview of the demonstration. Now, let's begin in the first step, we have to build a project by running Mac, build the make file in the loot on this refers to subdirectories.

A

This build IBS applications for Cosmos and fabric and the make file in the layer result CRI for the layer, and so all the artifacts shown in the lower light.

A

Next, we have to launch networks and initialize by make setup, so the setup script kicks in three more Scripts, the stat fabric start Cosmos and the prepare the start Fabric and start Cosmos. Now, each Network as a Docker container and to prepare ensures the more both Networks, create both right clients with initial States and initiate opening handshake, as described by IBC.

A

Each blockchain checks if initial states are correct after we learn setup script, the following scripts following results are obtained.

A

We established channels and connections and we'll see that containers are running.

A

So this is final step. We'll learn a demo use demo using the make transfer the make transfer kicks a text test. Tx script, which has a demo scenario like I said in the. In this scenario we transfer the token transfer from Cosmos to fabric this script, will print current state and then learn the layer text transfer command his arguments, ib601 IBC, 0 IBC, one amount of token and recipient address after execution. The token is locked on the cosmos side.

A

Next, this script executes the linear text. Delay commands to transmit the packet from Cosmos to fabric, and we get the token on the public side.

A

Then the script executes the layer takes X command to reply to Cosmos. As a result, we'll see that demonstration was successful.

A

So finally, I'll quickly show you only current work. Now we're developing the LCP, which stands for right client is light current proxy, the CPU solves the issues of the right grant method such as low extensibility and high verification cost sap. Using the t, e e t e e is a trusted execution environment.

A

And T secure area or main processors such as Intel, sdx and amateur Zone, more information is available on GitHub and our medium post. So that's all my presentation. Thank you for listening.