The One Question bounty closes Thursday 10 December.

Join in
We Them Media logo We Them Media Support us

Interchain applications Cosmos and the IBC - Peter Anyaogu

The picture loads from YouTube. The player loads only when you press Play. Turn on captions in the player if you need them.

A speaker introduces the Cosmos ecosystem, a network of application-specific blockchains. They cover hubs and zones, the Cosmos SDK and its modules, and the IBC protocol that moves data and assets between chains. They also compare Cosmos with Ethereum on consensus, accounts and address generation, before the session is cut short.

Not by We Them Media Channel: Web3Bridge. Published Friday 4 October 2024.

Titles are the owner’s. It plays from their channel.

Transcript

This transcript may contain errors. This video belongs to Web3Bridge. Letters mark each change of speaker.

These are the speakers’ own words. We have not checked their claims.

0:07 A: My name is Peter. So today I'll be taking you on a topic that we mostly don't hear about whenever we are in a Web3 event. And today I'll be talking about Cosmos ecosystem. I'll basically be looking at the interchain. I'll discuss more about Cosmos ecosystem and the IBC. We'll talk about interoperability, we'll talk about appchains, we'll talk a lot about the Cosmos ecosystem. And most of you must have heard of the Interchain, the internet of blockchains. So first of all, I'll go through the basics of Interchain and its tech. Then I'll look at how IBC works, some similarities and differences with Ethereum, and then the use cases and real-world examples. And exactly why am I speaking about Interchain applications today? So this is the slide in case you want to follow through with your mobile phones. You can scan it and then you can see it from there. Okay, so if you scan it, you can also give it to your neighbor to scan from there. So we can see the Interchain, or we can think of it as a galaxy. All right, in the Interchain, there- it is a network of interconnected blockchains, each implemented with specific properties. We can say that appchains that are developed in the Interchain are application-specific. They are purpose-built, and that is the main component of Of the interchain. Nah, nah, nah, nah, nah, nah, nah, nah, nah, nah. It's not this slide. So the concept of hubs and zones were one of the initial concepts of the interchain. But although this is not particularly what we have, but we can think of the hub as an interoperability layer. A hub is a blockchain just like an Ethereum. All right. And a zone is also a blockchain. In the app chain context, in the interchain context. But then the hubs are regarded as bridges. Think of it as bridges that facilitate communication between zones. These zones are specific app chains, and these zones are purpose-built and app-specific. So these hubs allow interoperability. They allow these zones, as you can see here, this is a zone and this is a hub. The Cosmos Hub is the first hub or the first blockchain in the interchain, and the Cosmos Hub allows or facilitates transactions and communications between interconnected zones. And then one of the most important things about the interchain is the IBC, the Inter-Blockchain Communication Protocol. This helps, or this is one of the key enablers of interoperability between these app-specific chains in the internet. How do these chains communicate, effect, or communicate, transfer assets and data with each other? It is via the IBC protocol. And you can say that appchains in Cosmos are built with the Cosmos SDK. So I like to think of this as the interplanetary stuff, right? We have a galaxy, and in the galaxy we have systems, right? We are currently in the solar system, and the star of the solar system is the sun. and revolving around the sun are planets. All right, so we can think of the Interchain as being a galaxy that has several AppChains, and then each of these AppChains contains or is being built to- is being built with the Cosmos SDK. And this Cosmos SDK has several modules. These modules each have specific functionalities that they offer for the AppChain. So, for example, if you're building an app-specific chain, you can add some of these models: the bank, the auth, the stake, gov params, mint, OTC, and more of them. There are several models. Or as a developer, you can also develop your own custom model for this blockchain. So let me go deeper into models. When you're building an application with the Cosmos SDK, Models are like the most important thing, and transactions are routed to a specific model to handle it. This is a simple message or a message sent as a normal transfer of tokens in, in a Cosmos chain. And then the way this happens is that you encode a message as a transaction and you send it to an app chain. In this message, there is a type URL. This, all right, this defines the interface. All right. on which exact model in the AppChain that this encoded message will be routed to. This model has keepers and multi-store, and this keeper manages accounts and states in the model. So if you are sending this message to a Cosmos Chain, all right, you are basically sending it as a transaction, and then the type URL is defining the interface or defining the type of where the model will be, the transaction, the encoded message will be executed inside the model. And if there is state in the model, the keeper manages access to it. And the multi-store is like a key-value storage that holds the state in a Cosmos model. I know this might be a lot, but let's go on. So let's talk about the IBC protocol. I briefly mentioned that it is what powers interoperability in the Cosmos chain. So basically what the IPC is, is it is the HTTP. Think of it as HTTP of the interchain. It's basically the protocol that handles the transport of data between appchains in the interchain. And then TL;DR, too long to read, IPC powers cross-chain communication. So we look at how IPC works in the next slides. There are clients, connection channels, and ports, and there is another thing called packets. A client- a Tendermint client is basically a client that helps to keep track of the consensus states of several appchains. All right, if it keeps the consensus state of an appchain, and then when you create a connection between 2 endpoints, that's between an appchain and appchain, the client can be able to verify it with something known as proof spec. Now the channel can be bound to any port, and these ports are like, you know, normal ports. Like if you are developing on localhost, there's a port. So these ports are like, um, a port that is being bound on an end, and then when you open up a channel, you can be able to transfer assets between 2 appchains. And basically this is how the IBC works. It has clients, which is basically to verify the state and using something known as proof spec. And then there are connections between these 2 appchains, and then there is a channel that you can open up between this. You can open up in this channel and bound the channel to a port. And what you can, what you can send between these 2 appchains is known as packets. So one of the differences with the Cosmos and EVM is usually the consensus, but basically they are both proof of stake. But then Cosmos has the Tendermint consensus. Ignore this Tendermint or BFT. BFT, Comet BFT, is more like, um, a rebranded version of Tendermint. And then there is Intermint, which is a fork of Tendermint to introduce a model, an EVM model, in the Cosmos consensus, which would allow you to have EVM compatibility for your app chains. So it's basically adding a drop of EVM. So normally in Cosmos, you have the Cosmos EVM, and then if you want to add- if you want to make your app compatible with EVM, you use the Etamine consensus client. Basically, the consensus client in Cosmos it has the ABCI and the engine. So the engine is like the consensus engine, and then the ABCI is the application binary interface that helps the consensus to interact with your application. The ABCI is more like a language independent, like it is not particularly tied to any language. That way it can be able to talk to your application directly. So those are the 2 main components of the Tendermint consensus. It has the engine and and the application binary interface, ABCI. Okay, so I'll quickly talk about the accounts in normal, um, Ethereum environments. Yeah, okay, basically in Cosmos the same account model is being used, the same public key cryptography, but what happened- what is different is the hashing algorithms and the algorithms that have been used. So in order to generate the address of a Cosmos chain, you can- you have to use the RIPEMD-160, which is a 160-bit hashing algorithm compared to the EVM, which uses a 256-bit hashing algorithm. So it has a prefix. This prefix is a chain. For example, Noble. Noble is a blockchain. All right. Osmosis is also another chain. Zooming. Okay, let me- so basically in the Cosmos account, you still use the same public key cryptography. You can make use of SEP-256K1, R1, or Edwards curve for accounts there, but mostly the most popular one is the Cobalt curve. And then this is how the account is generated. And basically this is all part of the account object. An account object contains the base account, which contains the address, public key, and sequence. I won't talk about that now.

10:41 B: Oh, amazing. Awesome.

10:45 A: I was going to talk about examples, but-

10:48 B: Thank you very much for that awesome session. Thank you so much.

10:53 A: All right, so this is my social. If there is any-

10:58 B: Thank you so much, Peter. Please, a round of applause for Peter.

More from this hub

Something wrong, or a video you want off this page? Write to wethem.xyz@gmail.com and it is fixed or taken down within 48 hours.