Hey everybody, we'll give it a few minutes, let some more people pour in before we get rolling. Hello, hello. Hey, good morning, good morning.
And John's gonna hop in as well and a little bit to talk about hack waslam as well. I'm gonna ping him the drawing.
Alright, well, I think we can get going here today. October 5th, Wednesday, finally back on updates from the lab. It's been a while, but it's been a busy few weeks. Today we're going to have sunny, going over some general osmosis updates upgrade, Prop 337 chain halt stuff.
developments on the features coming soon and better recently out. Maybe a little bit about mesh security. Then we'll get into Columbia. Talk about Cosmiverse, some thoughts on that. Water Spinner is here from the OSL admin team. He's going to talk about the booth, the attendees and his experience, and then
John is going to join us. He's not here yet, I don't believe, but he's going to talk about HackWazim for us. And yeah, so Sunny, why don't you kick it off with General updates? Hey, oh yeah, right now, I think almost a month since the last one, so, and, right a month.
So some general larger updates include we do the V12 upgrade went through pretty smoothly where so the V12 upgrade was basically
It added a couple of things like T-Wop as well as some it reenabled Stargate queries which allows you know a lot of the gaps to be able to actually interact with the state machine. That caused a lot of contract to be able to interact with the state machine properly and it finally reenabled and can account correctly.
So, it's gonna count as was something that's been, you know, it's supposed to be added in the last upgrade back in like June or whatever, but like it wasn't activated correctly and so now we did it correctly finally and so now people can, you know, that allows people like craze are and stride and stuff and people who are trying to use it and trying to counter it to react with us those
to be able to do that pretty easily. So yeah, those things, you know, that those upgrade went through that happened last Friday, so that went actually pretty smoothly. And then, you know, we had a little bit of a hiccup yesterday or yesterday? Yeah, wow. No, two days ago. How about yesterday?
Wow, I'm flies. No, I was three days ago. That be on Monday, where there was a slight bug that caused downtime on the chain. This bug actually had nothing to do with the V12 upgrade. This bug has actually been like latent there in the chain for a little while actually.
actually, but it got triggered because of a governance proposal to increase the validator set size. A high level overview of what, what, why that happened was the, you know, there was a,
people might know we have this concept in the Causes SDK called End blockers, which is basically code that runs automatically at the end of every block. But now we have many Causes SDK modules have their own end blockers. They all want to try to run certain code at the end of every block and what happened
was we had a little bit of non-determinism where it was not deterministic of which end blockers run before which ones. And it normally never mattered until this proposal came up because what happened was the validators that were running their governance end blocker before the Staking One, they processed the proposal
And then ran the stating and blocker which increased the validator set size. Validator set ran in the other direction. They ran the stating and blocker first. There was no validator set change. Then they ran the governance and blocker which then increased the validator set size. And if that validator set size would have been
to execute in the next block. And so because of this non-determinism, that's caused some of the nodes to end up on one side of the fork, some of the nodes to end up on the other side of the fork. This was, you know, how this non-determinism got into there. In the first place was, you know, it was a mistake on our part. We actually
did try to sort the array properly, but then we passed in the wrong version of the array. So it was kind of a bug that, you know, this, like I said, this bug actually got in. It's been there for a while. It was actually before our previous, you know, it was there since before the,
the June exploits. So my hope is that the new testing processes that we've been going through recently would have caught this kind of thing, but that shows that we do have to go all these new testing processes that we've been putting in place ever since the June exploit. We have to go make sure we also do the same process on it.
stuff on our existing code from before that as well. So yeah, that's kind of the status on it. But you know, the it was able to have resolved pretty quickly, you know, last halt, which was five days, the time was just five hours, maybe next time it'll be less than five minutes. But yeah, so basically we, you know, the value that is we able
to like help coordinate it pretty quickly, we were able to find it and it was pretty easy to resolve. So, you know, there was never any user funds or anything at risk at all. It was mostly finding the bug and then figuring out how to like safely restart the chain again. So yeah, that went by
pretty well without a hitch actually. So I can tell people this is sort of what Tenderman is designed to do, right? Like if you want there to be like, let's just have to halt in case in a situation like this. Like otherwise you would have all these crazy forks, something like that actually happened on Ethereum like, you know, last year or whatever.
where there was some non-determinism and then there was like someone triggered it and then there's all this like forking that was happening and they had to like, you know, cut off one of the forks basically and I don't know, the tenement safety overliveness approach I think is like, you know, working in practice here where it's like, oh, as soon as something goes a little bit wrong, you just, it should automatically#
I said the breaker to give people time to figure out what goes what went wrong instead of allowing the errors to magnify. >> Sonny, do you think this is a type of bug that would also exist on a lot of the other projects like Juno and Satch, or is it just like such an overlooked one line of code that is unlikely to be there?
This bug was in our code because well, so you know other chains also, okay One of the big problems and no big annoying things about go in and which is a language that the cause of case written in is they there's a data structure called a map and then it
go the map data structure is non-deterministic by default. If you want to iterate over the keys of a map, it is non-deterministic. It gets run in a random order, which is, you know, it kind of like what maps are supposed to do. But it would be way, you know, so actually there were past bugs. I think, you know, there have been
to a three pass halts on Juno as well, right? And I'm pretty sure one of them was actually caused by a similar thing, which was like, hey, there's non-determinism when catering over a map. So I think, you know, the solution to this is go recently added this thing called "Gimerix," which is long story story, we get, it'll give us a way of
like making a new type of map that will be deterministic. So that way, you know, we, we, that will cut out a large cause of the bugs here. So yeah, that was, that was sort of the, so I think that, that's something because of SDK team is definitely working on right now. So that will definitely help cut these
out. The specific bug itself that was in this situation, it wouldn't be on Juno and stuff because we had the way that people were supposed to order the end lockers in the normal cause of this. You have to take every single module's end locker and order it in a certain way and we thought that was like a
really bad developer UX and so we kind of like modified that process to make it simpler and there was just that one line bug with the code that when we wrote that. So, but no, I don't believe anyone else is using this same code. So I don't think the same bug is on any other chain right now.
How would let's say in the future when whenever met security gets implemented? How would this sort of a scenario play out when met security is in effect? We wouldn't really have much effect. I mean, that's sort of the whole point of like saying no dissentlement layers.
no single settlement layers. Like, you know, in the Ethereum model of like, rollups and stuff, if the Ethereum chain ever had a halt, then all of the rollups must also basically halt at the same time because they all rely on one chain as the settlement and if that if transactions aren't being posted to the main chain,
It's the security that's being shared, not the liveness properties that are being shared. So, I don't know, this is like the point of something like mesh security is to avoid this sort of situation. Avoid one chain going down having ripple effects on everything else.
Good, that's what we like to hear. Speaking of mesh security, what can you talk about with the developments that happen at hack wasm with mesh security? Anything exciting that we can share yet? Yeah, so, you know, I gave my...
talk on mesh security at Cosmoverse. The TLDR mesh security is this idea that mesh, you know, interchange security
Well, that'll I think we missed about the past 10 15 seconds. Oh, sorry, what I was saying was, you know, inner chain security shouldn't be a hub and spoke system nor should it be a multi-hub and spoke system where, you know, there's multiple hubs by security, everything else. It should be a
a mesh where all chains are providing security to other chains. Security is going bidirectionally. So for example, the causes hub can provide security to us Moses while us Moses provide security to the cause of the hub. I gave this talk at cause of worse and then
Jake, Hartnell from Juno and Ethan Fry from Confield, they were just like so hyped about this idea. They were like, man, we gotta implement this weekend at the hackathon. And so they actually started doing that. And so you know, three of us sort of spent some time
I don't know if I wrote a single line of code, I helped with the architecture and the read me, but Jake and Ethan Fry are just like cause and wasm gods and they just like, you know, smashed out a like proof of concept at the hackathon. Obviously,
It's not, it's no, it's no, we're close to production, and it's not, it does like some of the functionalities of what needs to be done. It does a lot of the IVC related functionalities. And which is kind of cool because it shows that like, Cosm wasm is like such a so fast to like prototype things in Cosm wasm as opposed to the SVK.
And so, you know, and then a lot of stuff. One thing that we realize while architecting it is how similar the super fluid stuff is to actually how similar the the cross-sticking stuff is to house the super fluid module and our supposed
And so what we realized is like hey, you know, so we built a lot of the cross IBC stuff at the hackathon and cosmopolism and then you know at some point our team can help take a lot of the stuff that we've already written for the super fluid module and Adapt that to like working for crossmaking and so once we combine this with the stuff that we were going to have
I think that it's very plausible to get some sort of like MVP of yeah, we went from before the hackathon it was literally just an idea now at that point we have like some sort of like prototype proof or even a proof of concept more
than a prototype. Then, you know, with a couple more work of like adding some of the super fluid stuff, adding some of the stuff that Goudau team has already worked on, I think we'll be able to get it to like, you know, some sort of prototype for MVP, like within a couple months. Very good.
Guys, with that team of 3U, Jake and Ethan, what were some of the maybe struggles or difficulties or hurdles you guys were kind of hitting? And I know you guys maybe had a little a few breakthroughs and architecture and ideas. Can you talk about that? And over those 48 hours.
Yeah, I mean a lot of it was sort of this arched, like we had to iterate a couple different ways of like how, you know, how do you know, the engineering is all about designing the right abstractions and so, you know, we have to go through a couple of iterations on how to correctly abstract things.
But to be honest, I mean, I don't think we actually ran into too much struggles. I mean, like I said, fry and drink are to the best cause of awesome depths ever. So they like, you know, they were able to like hack it out pretty quickly. We getting like some of the, you know,
What was really cool about this hackathon in general was I think so many of the projects were actually making use of IBC cause and bars of interactions. In the last hackathon in Seoul, there was not as much actual people, people all the apps were building this thing on June or on Christmas.
Like the winner at at the hack was like they were building an ETF protocol I think that then like uses IBC to like rebalance on us Moses and like I think one of the other winners they were like doing like Oracle prices over
over IBC. It was really cool to actually see this was the first hack was them with a majority of the projects were actually doing stuff over IBC. New custom protocols more than just token transfers. So I think that's, and so my security was just another one of those.
I think that was the most exciting breakthrough of like wow we're actually starting to see people actually hack on like new IBC protocols other than just token transfers. Got it. With you know you interchange security coming out and the USDC announcements that took
plays that Cosmiverse and mesh security. How do you think the pathways are kind of going to unfold given those three things coming out? Yeah, so you know the much anticipated Adam 2.0 was finally unbealed and yeah so you know there's a lot of
And stuff going on there with like some new features like the inter-integration security and The scheduler as well as like tokenomics changes Yeah, so you know, I think inter-change so you know people keep like I think like forcing like inter-integration security as like a and
And the goal of the security is to figure out how we can get all these options to start securing each other and be competitive with any L1.
In a chain security is more targeted at the small app chain that's just launching. You know, most of the security is really kind of assuming that chains have their own validator sets already and they're trying to share security with each other. In a chain security is more for like, "Hey, here's a brand new chain.
literally has no desire of coming up with its own validator set or something and it just wants to like you know be a call any of the of some larger change which are benefits to write and so you know I think these things are gonna like have to play out in parallel
And I think what's going to end up happening is chains that like, you know, maybe they start with like the hubs in a chain security will graduate to being like sovereign chains and using less security. Or maybe they start off with less security with like multiple chains providing them security. I don't know. We'll kind of like see how it plays out. Um, yeah, then, you know, I guess
I guess like there was an announcement of a couple of chains that were going to be the first doctors of interchange security. And I think one of the, you know, first ones, you know, our team was helping, it has been helping out quite a bit with helping them get to come over to Cosmos was USDC. So, you know, there's going to be a general asset issuance chain.
So it's not going to be like, oh, this is the USDC chain. It's going to be like, hey, this is going to be used for issuing other coins as well. But yeah, so USDC is going to have some sort of native version that's going to be secured on its own chain, secured by the Cosmos hub. But then it's going to be able to flow via IP.
you see to all the cause of shame. So, you know, this will be pretty exciting because we'll have more definitely more trustless stablecoins on us most than relying on like axlar, like also bridge risk and stuff. So, yeah, I think I think exciting that like, you know, stablecoin, you know, centralized stablecoins are
coming to COSMOS, I'm sure more central stablecoins are going to come as well, and then there's also going to be a bunch of decentralized stablecoins coming as well. So there's IST and from McGorrick, there's USK for Pachira, IOU from the ION Dow. So there's going to be a lot of cool stuff.
coming and you know our goal here is like you know more stablecoins the better we're we're launching stable swaps by the end of the month and so you know the more stablecoins are the more the stable swap liquidity is for us most it's just great as far as a stable swaps go on a lot of these new stablecoins that are going to be
deploying or coming over to Osmosis. A lot of the stablecoin liquidity is tied to the AxelR/USDC. Are there any plans or thoughts on spreading that out? Yeah, so I think a lot of the teams that are bringing over new types of stable
are going to be providing incentives. So like for example, like IST will provide, uh, Oracle providing incentives for IST liquidity. And so, you know, I think once we see more incentives start to come, come out, we'll see like, you know, a huge, you know, more diversification of stablecoins throughout the throughout our stores.
And then what we're working on a module called like a contract I guess called a transmitter which will basically be a way for people to like allow for one to one swaps between like conversion of Between the point so like one way conversion. So let's imagine that like
you know, a gorych wanted to help people convert Axler USDC into IST. They could like preload this transmitter with a lot of IST and allow people to like just come swap to it with no swap for you, no slippage. Basically, they would be taking on the risk of like any deepag or something because they're the ones.
promising the one-to-one swap, but it's a tool that will be available for many stablecoins providers to be able to help. Let's call it vampire liquidity from other stablecoins. What about all the liquidity that's bonded and tied up in liquidity pools? Oh yeah, that's a good point as well.
You know, I think maybe as some of these more other stable points come in, maybe our, we, our slowest governance would want to allow for like, you know, we can, we can build some system where like people can like break locks similar to how we did on the USD situation where people could break locks, but maybe we can do it where like people can break locks as long as
it's for the purpose of diversifying stablecoin. So it's like let's imagine we had like you know a lot of Osmo USDC liquidity maybe governance and say like hey you can break that Osmo USDC bond as long as it's in an atomic transaction of moving that into an Osmo IOU
bonding period for the LP shares could, it's something that could work. But obviously that's something that would have to go through governance because that would require like special casing some of these things and building them into protocol. Yeah, two questions on that. One, how hard is that to implement in code and two, are we just going
have a ton of Osmo different stablecoin pools or is it possible to have like an Osmo general stablecoin pool that's kind of meshed in. I think if we learned something from the whole UST debacle it's that we should be a little bit more diversified on
stablecoins that we use rather than like putting all of our eggs in one basket again. So I think what will happen is we'll probably end up like I think right now in the early stages we'll let the market play out have multiple multiple stablecoin pools and let the market play out which one they prefer and then
Maybe over time we can have some sort of consolidation of like okay look These few stablecoins are definitely like getting the most traction. Let's put more liquidity there or like there can be like aggregators right like you know there's a number of people building like ETF style protocols now, right? And so we can use like hey, let's put an ETF
of different stable points together and use that as a popular pair. This is what they have this thing where they use the 3-pool LP here. The 3-pool and the IRB is like the USDC tether die liquidity pool. They use that 3-pool LP share as
as a popular asset in other liquidity pools. So we could do something similar to that where like, hey, if there's a popular three pool that emerges, right, we could use that as a asset in and of itself in many liquidity shares, liquidity pools. And that could like,
that that will maybe improve some of the UX there but you know I think that I think those ideas will come farther down the road I think right now we should like just aim for like resiliency and supporting multiple stable points. Got it. What do you think the tie-frame would be not on like the initial release of all these but the full ecosystem?
system of stable coins centralized and decentralized on osmosis. So, you know, IST will be launching pretty soon. The USTC, I mean, unfortunately, it's going to take a little bit longer than we were hoping. You know, we were hoping for something by this
But like it looks like it's going to be locked on like whenever the launch of interchain security from the hub comes. So, you know, at Cosmiverse they are telling us that it will be January. So fingers crossed, but I'm sure that there's other stablecoin providers that are also like, you know,
rushing to move as fast as possible as well. So probably within the next, at least three months, I'm sure we'll see the first for some stable coins launching on us, whether it's centralized providers or decentralized ones like ISD or IOU.
Do you think there will be any sort of like stable coin war on us, Moses, where they're all competing to be, you know, the first runners? And is that good for us, Moses? I think there's definitely going to be like, I think there's definitely value in being first, right? And so I'm sure that those people are racing to do that. And yeah,
I don't know, maybe we'll end up seeing something similar to the B-curve wars in Curve, right? The B-curve wars were like sort of this big game that was happening over the course of last year to like see which stablecoins are going to get the most liquidity on Curve and like, you know,
And it was like a way of like, oh, okay, you know, by owning curve and locking it up, you can choose which pool is incentive. So, you know, maybe we'll see something like that happening between the stablecoins as well, where like, you know, our models that we use in our sources are kind of different, right? Like we don't do like, you know, we try to avoid these old bribery.
systems because, you know, it's generally bad for the long-term health of systems. But, you know, also, this does these external incentive matchings and stuff. So, I think what we'll see is a lot of these protocols like, you know, fighting to throw external incentives into these pools, so to like bring, you know, try to
build up the most liquidity. So, you know, I think that's just going to be good for awesome holders all together, because I say as this fight you get more and grow more incentives at the points. If you're allowed to say which do you think will be the big three, and if you're allowed to say further, which do you think will probably be the losers?
I mean realistically, I think the USDC and Tether are inevitably going to be big on osmosis, right? Like a big on every ecosystem. And I think that like,
So if you look at it on curve, right, those like the big pool, the three pool is USDC tether and die. And so I think maybe it makes sense to have like USDC tether and some decentralized paper coin. The question is like which decentralized table coin and I don't know to be honest, I think like there
interesting it's a little bit unclear how so the history of die is like very interesting where like it came on a theorem at a time when like there was no native stablecoins right there was no there's no USDC on a theorem there's no tether on it theorem
die was sort of the only stablecoin there. And so it kind of got quite a bit of traction that way. And then on top of that, once the whole curve war started, you know, because die happened to be part of that like base three pool that was in everyone else's pools, it kind of just like built up so much liquidity and kind of
It's unclear whether that's going to be a very weird path dependent thing or if that's going to be reproducible again. One thing people remember the problem, one of the challenges with maker style systems is the growth of the supply is very
much tapped by the demand for leverage. Unless you do a diet, which was say, "Oh, the demand for leverage can't keep up with the demand for diet self." So they had to build this whole system where it becomes backed by USDC.
Now, somewhat kind of reduces the interest, like, you know, the whole point of the, you know, decentralized stablecoin a little bit. But so, you know, we'll see which one, which one of these play out. I mean, I think the, I think the IST team is like doing a good job. I think, you know, I'm excited for it.
You know the IOU stuff I think it's an interesting way of doing it of like instead of choosing one asset or like You know into the one causes asset to like be the primary collateral It's like hey, let's choose a basket of all the causes assets So it's like you know, so a little bit more risk-never-safried as well as it's like
I think that's a really cool approach. I think the USK, for example, it seems very much like pretty isolated on the Codira platform right now. I think multiple people have been asking them to drain over to other chains as well, like make it as smooth as something.
And so, but you know they haven't really done that kind of stuff. So I don't know if their goal is to try to build a cross-chain stablecoin or really just like have something more internal to procure itself. Yeah, so I know we'll see how the decentralized stablecoin game plays out in.
Honestly, even the centralized stablecoin game as well, like, you know, people saw like orders like three weeks ago or something, Binance decided all of a sudden like, hey, if you have UFDC on Binance, you suddenly have VUSD instead. It's like not even an opt-in thing. It's like, you have this now.
So like, BSD is like, okay, playing this game to try to become, you know, compete with USDC and Tether for their positions as well. So I don't know, I think we're gonna see generally a very like, vulcanizing of stable coins in the coming months.
So speaking of the Binance route, what were to happen if, when these stable coins and the ecosystem get so prevalent, and then maybe someone wants to go on governance and propose
that osmosis takes the route of finance and to leverage osmosis in a more powerful position. How do you think that would unfold? - Can you say that one more time? What do you mean?
If someone goes on governance, let's say nine months from now and they propose to take the same path that Binance took, but on Osmosis, so Osmosis leverages maybe like Ion stablecoin to be the default and then all the stable coins get converted to that. Yeah, I find that to be somewhat pretty unethical.
You know, the point of luck is to avoid like, you know, you can't not just going into someone's account and taking, you know, taking away their assets and replacing them with a different asset. I think what we do need is some, but I think what we'll have, what can happen is like something more, something like using the transmitter. So let's say, also, this governance says like, hey, you know, we see that there's#
benefits on everyone having one stablecoin. We're going to put up a transmitter that allows people to opt in to swapping all their one stablecoin to another one, right, without any slippage or fees or anything like that. So it's still an opt-in model, but it's just like, you know, you shouldn't be able to
I think it's pretty wrong to go into people's accounts and like swap it without their consent. Right, but I imagine with you know the ecosystem unfolding in these you know this coming year. You know a lot of these chains and stable coins can incentivize people to use that transmitter for their agendas and that'll be the whole game that might be played out.
Like the curve wars, the stable coins that are going to be launching on us Moses, they can use these incentives to kind of lure people into adopting their stable coin with these transmitter abilities and such. And that'll be like the game that gets played. Yeah, that's fun.
I think so. Yeah, it's like it'll be really interesting to see it play out how like different stable. Yeah. Yeah, it does feel like, you know, like I said, like guy got its like start at this time before USDC and Tether came on.
to Ethereum. I mean, right now, I mean, we kind of do have USDCR already on us, but it's the bridge version by Axler, but I don't know, maybe there's still an opportunity for a decentralized stablecoin to like still like cement its ground before like native USDC together come over.
Yeah, I think we are good to go on the USDC and the stablecoin discussions. Maybe we should shift to Columbia, Medellin and talk about your thoughts on Cosmiverse, maybe not as awesome as a specific. And then, you know, what are you excited about? What are the projects that you learned about that, you know, brought some exciting news.
and the overall vibes that you got from Cosmoverst study first and then we'll shift to water spinner after that. Well yeah so you know it's a lot of fun I think I lost my voice by the end of it but it's a little bit raspy still but yeah it was
I was, you know, had a lot of, so I gave my mesh security talk. I think that was definitely a lot of excitement. A lot of people excited. A lot of interest around the concept, you know, as demonstrated by Jake wanting to, like, get it done by the weekend.
the Adam 2.0 stuff was interesting. I hosted a panel on MEB with mechatech and skip and so I think that was, I had multiple people say that was a David panel because it got a little bit spicy like I think that you know panels are fun when there's a little bit of arguing going on and so I definitely recommend checking out that panel.
And I'm not sure if they put it up yet or it's on commonwealth. I don't know if it's on chain yet, but they put up a proposal for building in a lot of these MEB auction systems and the good MEB internalization systems on inter-
the osmosis protocol itself. And so, you know, if you want to let, you know, the whole idea of like bad M.E.V. versus good M.E.V. I definitely recommend checking out the M.E.V. panel from Cosmoverse. I think we go like really deep into a lot of these like distinctions and like, you know, and I think what one of the things I was very clear
is like hey if we don't know it's important to bring these things in protocol so they can be like used to maximize social good rather than like let them happen off-chain via like validator cartels so yeah definitely check out that that panel for sure I guess other things that happened no it was really nice
We got to spend a lot of time with the Mars team because Mars is going to be launching very soon on our devices. There's a lot of cool products that we're like sort of co-building here and like building this like leverage trading platform and this like de-platform together.
of our teams were very remote and so getting spent a lot of time together with them was really cool and like planning things out of how we're going to build the greatest step ever. The, yeah, and then you know another project I was pretty excited about like being announced was like, oh you know I'm known about it for a little while but
like the kind of came out more publicly now was Babylon, which is like a way of leveraging Bitcoin security to help secure the IBC network and making it more, making it so that if channels expire, we can auto-bootstrap them because everything is being check-pointed into Bitcoin. And so I guess it's a good timing as well because
I'm just switched to proof of state recently. So it's like, okay, there's only one real proof of work chain left. It makes sense to use, and it's not going to stop being proof of work for, you know, the foreseeable future. So it makes sense to like use its proof of work security to augment, uh, cause most proof of state for little to no cost basically. So, um,
Yeah, I'm going to use some of the things that I've been pretty excited about. In regards to Babylon, is that something that has to be done by a project in a chain itself or cannot not be built into osmosis without Babylon? It could be built in without Babylon. It's Babylon access. They like service.
The point is that the way it's architected it should be fully trustless like where it doesn't depend on trusting Babylon It's more just like hey Babylon can take the headers from all of the chains and then like Merkleize them and then checkpoint them into Bitcoin so it'll just it's a way of making it cheaper to do it, but it's not necessary
It's necessary to use Babylon to do this. Awesome. Water spinner. Why don't you hop on, tell us about your experience at the booth. You definitely put in a lot of work and the OSL and the foundation saw you repinosmosis fantastically.
Hey, thanks guys. So yeah, Cosmoverse 2022 was absolutely amazing. The first Cosmoverse was something like 100 people or something like that. And this year was I think around like 1500 people in person. So it was just amazing.
having everyone there being able to talk at Cosmos with the community like that, medying itself was just an amazing place to be, amazing atmosphere. The town was great, the people were great, so definitely huge shout out to Ceto for putting that on. But yeah, being at the booth was, it was really cool to
to hear some first-hand experiences from people coming up and talking about how Osmosis was this red pill into IBC and the Cosmos Network where they might not have even realized what they just performed, doing an IBC transaction in the sense that
I was talking with one person specifically that their friend had told them about some stargaze NFTs. So they wanted to get their hands on some stars and then transfer them out to stargaze and get some NFTs there. And you know, unknowingly they deposited some atom onto
Osmosis traded that atom for Stargaze, took that star's transitive back to Stargaze, bought some NFTs and now I'm NFT in their wallet and they did that in the course of 10 minutes in a seamless easy transaction whereas we're coming, we just have things with the Ethereum and things like
that we're bridging and wrapping kind of used to be this long process where now these guys are just coming in and talking about the joys of IBC that are happening right in front of them and the user experience that they get without even fully noticing it which hearing that is kind of just like a a reinforcing
that some of the things that are going on are definitely moving in the right direction. And another thing that I really noticed was the Latin American community was just super, super excited about getting decentralized finance into Latin America. A lot of people
that you know, cosmos has kind of a way of, you know, the way of government is working with it is really appealing to them. The exchanges that we offer are very appealing to them. So it was just like everyone was just really good time of bringing everyone together here and everyone out.
Yeah, that's good feedback on Cosmiverse. Given that most or a lot of Cosmiverse was people that are already in the space,
At the booth, what did you feel was the ratio of people that knew about osmosis or had at least interacted with osmosis versus people that really had never utilized osmosis or had any idea about it?
comparing to previous conventions like permission lists or consensus, this was definitely a pleasing atmosphere where there was a lot of people, the majority of people that came up either used osmosis or knew
about it in the sense that it was a large exchange within cosmos so that it was cool to kind of like read. It gave me the opportunity to lead conversations into a little bit more media-type kind of topics where you know with security within IBC and finding out some
some more ideas of what they had with thoughts on the exchange and things like that. There was definitely a very good vibe and feel of osmosis and cosmos, cosmos, de-fi being kind of the future and, you know, depth-specific chains.
very, very playing out and being like this very big realized future was definitely a huge feel and vibe that I was getting while I was there.
and the attendees that came to you at the booth, what do you think they were most excited about? Onosmosis and for the cosmos ecosystem in general.
For us Moses, I definitely can say a lot of people
When order book was a lot of questions that you have something like that and I definitely think you know those are things like that are in the works A lot of people were excited with things like stable swap coming in stuff like that and You're kind of going into what happens
And on Monday, I had a couple people that were brought up, the bug and the health in June. And they really, really were extremely pleased with how well the community reacted and how developers and validators all came together pretty quickly.
found this solution. There was a lot of sentiment of people being extremely pleased with how as most is moving forward and excited for the future with the mess security talk that Sunny gave. A lot of people were coming up and extremely excited about that, just hearing that
Osmosis is not doing anything but building right now, right? Like we have no, we have no thoughts of just saying that, yep, what we're at right now is pretty good. I think this is all right. Everyone really knew that Osmosis is here to keep updating and keep upgrading and building and that, you know, we're not stagnant. We're done.
I think that was the general consensus. And for Cosmos ecosystem in general, it really showed that people are very bullish and excited on this interchain thesis, given that we're in a pretty heavy
So John is one of the lead devs on the front end for Osmosis. He was a mentor at Hackwasm and I think he should talk about a lot of the developments that we saw at Hackwasm and maybe a little bit about the challenges the entrance faced and some of the projects that were built.
Yeah, hey, can you hear me?
Yes, beautiful for you boys. Thank you. Thanks for the intro. So yeah.
I was at Cosm versus well, and then I was also put on as a mentor for mostly front-end people at Cosm or HackWasm as well. Overall, it was like a really good experience. It was really nice kind of moving from
like high level concepts at Cosmoverse to more like development kind of getting down in the weeds with developers at HackWasm. I was also really pleased to see a lot of local Colombians there working and hacking on on Cosmoose technology.
I talked to a lot of them afterwards and they said that they want to continue to learn about Cosmos and Osmosis and continue to invest in the space which was cool to hear.
For me personally though, I didn't do as much Cosmos and development. I was kind of going around like people would flag me down when they're like, "Hey, we need a front end for our smart contract." And everyone would point to me and then I would basically use
Create Cosmos app and a lot of the tools that Dan Lynch has been working on. So like the day before the hackathon, we spent all day setting up Dan Lynch and I sat together all day in a wee work.
to set up the clients to support V12 upgrade for osmosis, but also to create a template for making it really easy to create a front end for your smart contract as well. And we kind of like worked all day and got that working just before the hackathon. So it kind of made my life really easy.
And also people who are trying to build front-ends really easy because when you finish building your contracts, people would come up to me and I was basically able to help them just run a handful of commands and create a really good looking front-end in literally five minutes, which is insane.
The tools that Dan Litch has been working on over at Cosmology has been or they're like totally invaluable for People creating front-ends in the cosmos. It made my life super easy at a hack-lasm and then it saved tons of time for people there but also
While we were there like during the hackathon we were like discovering problems with Create Cosmos app and the clients and stuff and so we were like pushing bug fixes like during the hackathon and telling everyone to update their mpm packages So I was kind of cool, but yeah, there's a lot of value that came out of the hack wasm
How do you feel about the abilities of the competitors were a lot of them well-versed in the CW or was it you know people having to learn from scratch? How was that? What do you mean by competitors? Like the entrance the teams that were competing for all right?
Yeah, maybe that's not the right phrasing. Yeah, I'd say the more challenging part was probably like the rust specific stuff. I don't have tons of cosmos and experience, but during the hackathon I did like work with a team to like help do some of the initial development.
on their contract. So, Rust can be hard to learn, but for Cosmism, it's like the easiest use of Rust. You kind of just like get a message, do a simple kind of state change, and then send a response. So there's like a lot of the advanced concepts in Rust.
So I found generally people were able to, like the developers are able to kind of get their proof of concept down on Rust and then we were able to generate a front end all the way like it literally read the Rust code, created JSON files and we generate the front end from there.
So I found like a lot of people are actually able to get some proof of concept work done.
which is pretty amazing. So it really shows the productivity that's enabled with the tools we have.
Yeah, um, can you talk on the winning team equilibrium? I remember these guys that are huddled up in the corner by the front and I walked over to them and I said, Hey, you guys crushing it or what? And this guy the tall one he looks back at me is like, yeah, we're kind of crushing it and then it went
Can you talk about what they built more and what their plans were and how they went into that and why they ended up winning? Yeah, so they were actually had a feeling that when I met them that they were going to be at least a very
strong team. So I will say they didn't need my help very much, so I don't actually know much about the details of their project, but I know that they did take really great advantage of like the entertain features of Cosmossum, because that was like not only a big focus at Cosmossumverse,
as Sunny said, but at Cosmopolism, or at the Hack wasm, we kind of like encouraged everyone, even though Osmosis was a sponsor, Stargaze was a sponsor at Juno, we encouraged everyone to build apps that interact across these chains. And I think they did an excellent job.
using like leveraging IBC to create really valuable functionality. As far as the specifics, I feel like Sony would probably be able to chime in more. But yeah, they're really impressive team. Hopefully we can see more of their work in the future.
Sunni you're about to talk about the specifics on their team anymore any further Yeah, I mean they were able to work on what they worked on there was like doing that ETF repalms. No Yeah, ETF rebounds because they were able to use like the swap router contract that we had built and like doing
Transactions over cross-chain swaps over IBC basically which is something our team has actually been working on as well So that's actually something we mentioned at Cosmo for us was we're gonna be working on cross-chain swaps on these like outposts model for us Moses where you know Dap on other
We'll be able to really easily do trades and stuff on osmosis, right? Instead of having to have a deck on every single chain, like Juno and our tray and neutron and Stargaze and everything, right? It's like, okay, well, we can just, you know, have every, every cosmosom enabled chain just plug into our
osmosis liquidity. So what they built was sort of like a version of that, right? It wasn't using our version of cross-chain swaps, but they were, it's not live yet, but they kind of like very impressive team were able to just like sort of pack together their own version of cross-chain swaps at the hackathon. So that's quite cool.
Yeah, we'll make a comment on the swap router because I did see some details on how that was implemented. I know there's a big opportunity. I think there are people working on it, but for actually system background, the swap router that was used during the hackathon was kind of
The routes are kind of like hard coded pools. Like you have, like if there's no route that you hard coded, then it's not really able to do the routing. But as we do on the front end, we, I think it's a big opportunity to create optimized kind of automated
routing where it'll look through pools and actually find the best path based on the current weights. That still is something we need. That's like a cosmoslemic population.
I'm hanging out with Nikita right now from Hazard and he's working on that actually right now as well. The more dynamic router. Yeah, definitely interested in using that even on the front end. So yeah.
So we've got Jacob here as a speaker. I think he should speak so that we can also get the timeliness of this Hopefully around this hour to end so Jacob take it Hey, thanks. I'm actually right now on the airport. Then just wanted to throw my to send
So, as a last-month contract mentor, a lot of issues with people came to me, there were simply things that are undocumented or not very well accessible, for example, start with using proper
the libraries start about using use sites and some people spend really hours trying to solve issues when building those products. So it definitely brings great force my beliefs
where the biggest work right now, for example, so from Comfield shoot, you should focus. And my boarding just started, so that's what I wanted to add and the director. Yeah, thanks. Have a good day.
good flight home. You know, some of the things you mentioned, I do think we have room for improvement at the next hackathon. So we'll, you know, try and document that and get things smoother for the entrance so that they can focus on what they're building instead of focusing on getting to what they're building. With that said, I think we should
wrap it up. It's almost it's almost on the hour here so you know thanks everyone for tuning in thanks sunny John water spinner and Jacob for speaking and that's about it for today. Thank you very much. All right see you later everyone.