**A** (0:00):
Hello. I in fact will not be talking about Mesh Security. I'll be talking about some other stuff, but it'll show off a little bit at the end. I think I've just been sending Mesh Security as the title for all the talks that I haven't come up with a talk for yet. And you know, they just, they're like, oh yeah, that sounds good. No, but I'm gonna be. Thank you guys for coming. My name is Sunny, I work on, I'm one of the co founders of a project called Osmosis. And we're gonna be talking a little bit about how, how Osmosis will be interacting with the modular ecosystem. So a little bit of background for anyone who's not familiar with what Osmosis is. Oh yeah, that's better. Anyone who's not familiar with what Osmosis is. We are a DEX built on the Cosmos SDK. We have all sorts of, you know, we just launched, we just launched, you know, we have liquidity swapping ability. We launched a contrary to liquidity very recently. You can do all sorts of have assets from over 50 different blockchains. On the Osmosis blockchain. We have over $100 million in liquidity. We have all sorts of pro trading tools, basically the most advanced developed decks in the Cosmos ecosystem. And yeah, liquidity from all different places, both from within Cosmos and outside of Cosmos. Out of all of the assets, you know, like four out of five biggest pools are from non cosmos native chains, right? And along with just the DEX itself, we have this ecosystem of applications really meant to build this like full unified DEFI experience on top. So you know, beyond just your basic spot trading, you have your margin trading, you have your perps, you have your launch pads, you have your fiat on ramps, you have lending protocol. So basically a full integrated DEFI experience, everything. You know, the goal here is you go to binance.com, you have all these trading tools, you have all this like things in one unified experience. Osmosis is going to provide that in a decentralized way. So, and you know, as by being this like liquidity center for the Cosmos ecosystem, we are sort of the center of IBC traffic today. So if you look at, you know, on any metric by users or by IBC traffic by volume, Osmosis is sort of the center of that and has found itself as this like IBC hub and liquidity hub of the Cosmos ecosystem. And so now very soon, hopefully we will have a new entrant to the Cosmos ecosystem, right? The Celestia Blockchain will be launching. And as part of the Celestia blockchain launch, the goal of the Celestial blockchain node implementation is to be as simple as possible, right? Like, you know, obviously we need this thing to, you know, sorry. You know, with Celestia, we're going to have like this beginning of all sorts of like new modular chains and roll ups, building on top of the Cosmos ecosystem. And you know, there seems to be this like, thing about like, oh, app chains versus modular. And like, I think this is like some weird dichotomy because really the whole point of app chains is this idea of modularity, right? It's saying like, hey, we don't need to put everything into one blockchain. We can, you know, break out what you need, you know, osmosis. We're trying to be a Dex. We can like say like, hey, we don't want to deal with bridging. We are going to completely outsource that. We are. That's not our, not our problem. We're going to go find someone else to work with. We're going to go work with the Axelar team or, or the Wormhole team, right? We're gonna go outsource bridging completely. This is part of the modular idea, right? Or if it comes to things like data availability or like, you know, if we need to base money, it's like, okay, we're not building that, we're gonna outsource this. This is all, it's all modular. So what I was saying was. Yeah, so, you know, the goal of the Celestial Blockchain is to act as this app chain and to be as simple as possible. Cause obviously, you know, we gotta run it on our Kindles and we're gonna keep the, keep the nodes as, as light as possible. And because of that, the Celestia code base is actually like very, very minimalistic. You'll see that it actually imports very few modules. You know, Ishmael just talked about how like, you know, what, how can we avoid adding a general purpose VM or anything to this chain? So the one module that it does have, though, one of the few, one of the few modules that it does have obviously is the IBC module, which is great, right? And so this is this decentralized, this permissionless bridging protocol that allows you to send tokens, data assets, anything between any IBC enabled blockchain. And so IBC is growing. It is, you know, built on the Cosmos SDK. There's other chains as well. Now, now we finally have it on Polkadot, we have it on the Penumbra and Anoma stack. So, you know, IBC is slowly growing, but with Celestia now and this ecosystem, the modular ecosystem that's being built on top, we have a whole bunch of new frameworks being built, right? You have like the OP stack now, right? You have RollKit, you have the Sovereign S, you have Eclipse. And it's like it is going to take us time to go and build out IBC for every single one of these. Because the goal of IBC is to really like build in your bridging protocol at the same security level as your consensus system. It uses like client proofs and it'll take time for us to get there. Obviously the goal is we want IBC everywhere and there are people working on this, right? Like Polymer is working on adding ibc, zk, IBC to all of these sort of different stacks. But it'll take us some time to get there. And so right now, how do we do this? We're gonna have to rely on other bridges, right? And so this is kind of where. So the question is, how will all these rollups and, you know, chains and sovereign rollups and everything on all these different stacks access liquidity, especially TIA liquidity, right? Cause they need that TIA to pay for their data availability. How are they gonna get that TIA to there? Well, this is where Osmosis comes in. So Osmosis is, you know, really expanding on its bridging support. So obviously we support IBC today. We work very closely with the Axelar team. Wormhole just announced yesterday at OSMOCON that they're launching Worm chain, which is gonna be a Cosmos SDK based chain. And then the important one here is Hyperlane, right? So Hyperlane seems poised to be the, you know, bridging the first bridge that's available to a lot of these different stacks because of the way that it's been designed as this, you know, very OP modular bridging system where you can have, you can choose what kind of security system you want. And so we are working on adding Hyperlane to the Osmosis chain. And you know, because of its app defined security model, we can write it as a Cosmos contract. And with this we're gonna be able to use Osmosis as the connector between Hyperlane and ibc. So now you have this flow where finally you can say, hey, how do you get TIA from Selesia onto something like Eclipse or onto an Eclipse based rollup? Well, you can IBC from Celestia to Osmosis and then Hyperlane from Osmosis to Eclipse and, and you know, this will be, and the idea here is that we're going to use Hyperlane to connect to all of these sort of different rollups and get TIA onto them now. Well, what do you do when you're at the center point of you know, know transportation routes, right? Well you build a trading center, right? You build, you, you build Constantinople, right? You're, you're at the crossroads. You build, you build a training center there. That's what, that's what we're building, building with Osmosis. So we, we want to be the place where we build up as much TL liquidity and liquidity for the entire modular ecosystem and provide these services and like product that we've been building for the Cosmos ecosystem, but expand just beyond that. And so one of the things that I'm really interested in is like protocol owned TIA because you know, if anyone remembers a couple months ago like the Arbitrum chain basically came to a halt because like some dev account didn't have enough ETH in it to pay. Its like data availability and stuff, right? So we should be moving to a world where no, you shouldn't be relying on some like foundation or some dev team to be like paying for your submission proofs to your DA to Celestia, right? You should be actually moving towards a system of protocol owned tl. And so you know, there's a bunch of different ways that we can do this. So one, we have this protocol called Stream Swap which is basically a auction system built on top of the Osmosis chain. And I think a lot of the new projects that are launching should, can do to, can do these Stream Swaps. You know, it gives you this initial distribution but you can do it for tia. So that way you have this initial distribution of your token. But now your protocol owns TIA in its community pool or treasury and it can pay for its own DA without directly from itself. We also have built this thing for the Cosmos ecosystem called fee abstraction. And what fee abstraction is, it's meant for transaction fees. So what you can do is you can take a chain like Stargaze, right? Stargaze is an NFT platform built on Cosmos. People can start paying their transaction fees in stars, but they can also pay their transaction fees in any token. They can pay in usdc, they can pay in osmo, they can pay in Bitcoin. And what we've done with this fee abstraction module is Stargaze can accept these fees and all these different tokens. But what the chain will do by itself is it'll send all the tokens to Osmosis, swap them to its own native token, and then send them back to the stargaze chain. So that way they can be distributed as fees or burnt or whatever they want to do. So this module is available, it's available on our GitHub. You can go to GitHub.com osmosislabs feeabstraction, you can import it into your Cosmos chain today and any Cosmos chain can start accepting fees and any token. Okay, what's the next step? The next thing that we're gonna build with this is DA fee abstraction. How do you let all of these rollups pay? You know, let's say they don't want their own protocol owned TIA in their treasury, but what you can instead do is say, hey, a chain like Manta can say, oh, we are going to hold our own native token Manta, but we need to pay our da. They can send it to hyperlanet to Osmosis. It will automatically swap it to TIA and send it to the Celestia chain in order to pay for the da. And so we have, we are working with some teams to actually build this out in production. Now, another way that, you know, beyond just for fee abstraction with, you know, this whole modular idea, a lot of these chain, you know, we work very closely with the ARGUS team. You know, we, we can build this idea of outposts where they don't have to build their own DEX infrastructure for their own chain. They can actually provide things like swaps and everything over ibc. So let's see if this works. This is a demo that we built of the Cosmos swap, which is basically, this is a swap on the Juno chain. You're swapping Juno, sorry, osmo, Juno. For osmo, you make a single transaction on the Juno chain. But what it's doing is it's actually sending the tokens to Osmosis, swapping them to OSMO and then sending them back to the Juno chain. So basically Juno doesn't need its own native Dex. Let's say you have a DAO on Juno or whatever you're trying to do. You can tap into Osmosis far deeper liquidity. And so the EVMOS team has also built a similar version, the same, similar concept for the evm. The Skip team has, you know, you saw them present a couple like an hour ago about ibc. Fun. You can basically swap from any chain to any, any chain on any token, on any chain, to any token on any other chain over ibc. And we'll be working on like integrating hyperlane into the system as well. Yeah, all through osmosis anyways. So these are some of the ways that osmosis is like, you know, planning on integrating more deeply into the whole modular ecosystem. One of the other things I'm actually really interested in is, you know, I will obviously I do have to talk about mesh security and how we want to incorporate data availability into mesh security. So, you know, the con. The premise of Cosmos and I think a lot of the module, like the thesis and a lot of the modular ecosystem is this idea that every chain is the L1 for its own internal state and an L2 for its foreign state. Right. This is sort of the whole idea behind these sovereign rollups. And so, you know, osmosis is the settlement for, you know, the OSMO token. But it acts like an execution environment for any axle that is bridged IBC'd to osmosis. And so as part of IBC today, you know, we do these sort of light client proofs where like two chains are going along and you send an IBC packet that includes some sort of light client proof. But what we wanna do is eventually make IBC or you know, the security model between these chains better than just like client proofs. We wanna start to incorporate things like fraud proofs. And finally now, thanks to things like RollKit, we actually have fraud proofs for the Cosmos SDK. Now the thing is, fraud proofs have this huge time delay to them. Right? Right. You have to wait the entire challenge period. And the UX that people have come to expect in Cosmos is like very fast bridging. Right. You can IBC between two chains in a matter of seconds. And that's sort of one of the things that people really love about it. And so we don't want to build in this, you know, fraud proof window into the IBC bridging protocol. Cause it'll just massively deteriorate the ux. But how we can use fraud proofs is in mesh security. So mesh security is this idea of restaking where you can say like, hey, validators are going to give certain guarantees about, you know, they're gonna be restaking their OSMO to. Yeah, okay, so, and as part of this, what we've done is, you know, the, the initial version of mesh security is mostly about tendermint fraud proofs. So it'll be able to detect, hey, okay, this validator does something malicious in like the consensus protocol, we're gonna slash them. But the way mesh security is implemented is Actually, as it has this interface called a slasher contract. And you can write arbitrary slasher contracts, Right. You can do it for things like, oh, we're gonna do mesh security restaking for an Oracle protocol. And if you're, if one validates Oracle price is too far away from everyone else. That is a valid slashing condition. What we can also do is build rollkit fraud proofs as a slashing condition. Right? And so I think that eventually every Cosmos chain will start to use rollkit style fraud proofs. Right? And so that's great, but then how do you make sure that you have these fraud proofs? The idea is that like, okay, we're not gonna block IBC bridging on it, but if a Byzantine state machine sends an invalid packet and in the future they will be slashable for it. But to make them slashable for it, we need to make sure there's data availability. So this is what we can block for. We can at least block on data availability before accepting IBC packets. So let's say chain one or say chain two wants to send some assets to chain one. What it can do is generate a transaction. It will post the data onto something like Celestia or any DA system. And the validators of chain one will be running a data availability sampling like clients of Celestia. So in the validator software we should be having this DOS like light client built into the software. And then what they will do is when IBC data is sent from chain 2 to chain 1, the validators will basically use a vote extension to approve whether or not that they actually got the. They'll validate that the data is available. So they're not gonna actually validate the fraud proof itself, they're just gonna validate the data is available to so that someone in the future can submit a fraud proof to the Mesh security slasher contract if needed. Anyway, so thank you guys so much for listening and I hope you learned a little bit about osmosis and mesh security and what we're building. Thank you.