All right, everyone. We will get started in a minute. One more minute go by. Get a few more people in here. Today's order is going to be suddenly providing some updates, talking about what's been going on. And then we will have some members from the OSL hop on and tell us what they've been up to.
Hey everyone, can you hear me fine? Yep, cool. Yeah, let's see if you're seeing everyone again. So we can I guess go ahead and jump in while we
We wait for a few more people to join. We've been a bit spoiled. We had our co-hosted spaces with Polygon and Avalanche in the past two weeks. I think those might have been our most listened to spaces ever. I think there was close to 2,000 listeners on
I think it was like 1.5K and then 1.7K or something. Listeners on those two spaces. So we got a step up our game with the normal updates from the labs I guess. But no, yeah, I think that was not really well. Also, I guess the Mars space actually had quite a few listeners
as well, I think, close to 1,000. So, you know, I guess, you know, we can start from there, start right there where obviously I guess the biggest news of the past two weeks is the Mars launch went pretty smoothly, I would say, with, you know, maybe I think maybe the biggest hiccup
that the deposit caps are way too low initially but those have now been raised. But yeah, so you can go check out Mars.Osmosis.zone. You can start to deposit and borrow the three initial assets right now or Adam, Osmo and USDC.
I believe the Adam and USDC deposit caps have already been re-hit, but Osmo, their collateral deposit caps are for Osmo are much higher. So the Osmo caps haven't been hit yet, so if you have some liquid Osmo, you can go ahead and deposit it into
to the Mars lending protocol. Beyond that, there were some other interesting ecosystem launches this week. One of them is cellar tone. This is maybe a little
more developer focus, but if you go to cellatone.osmosis.zone, it's a new contract explorer that was built for interacting with Cosmosom contract on osmosis and eventually other Cosmosom enabled changes.
And, you know, while, you know, minskan is obviously, you know, probably one of the best explorers in all of crypto, but, you know, it's not really well designed right now for interacting with contracts in a way that like if you go on ether scan, right, like on you can actually interact with contracts.
contracts directly from either scans website that you can query the state of contracts much more easily. So, so, so, cell phone is sort of like that packaged with a way of actually deploying contracts. So, you know, today we have with with beaker, like,
It allows you to deploy contracts from the CLI, but this will just provide a much easier user interface. One of the tools that was very popular early on in Ethereum development, and still today it was called Remix, and it was sort of this web UI for deploying contracts.
having that on, you know, yeah, you can treat cellatone as sort of like a combination of remix plus a contract explorer for osmosis. So hopefully it'll just make it a lot easier for people to interact with than developers to like test and query their contracts. The other big launch that happened
or integration is a layer swap. So, layer swap is maybe a little bit of a lesser known product, but like, so layer swap is a, it's by this team called Brandsburg. And so, what it allows you to do is deposit assets directly from centralized
changes to other chains. So what I mean by that is, so if you go to layerswap.io, what it allows you to do is, you know, let's say you have USDC on Coinbase and you want to
basically authorize them to withdraw a certain amount from your Coinbase account and they will automatically basically withdraw from your Coinbase account and deposit USDC into your osmosis account directly. And so you can sort of bypass axelar bridging fees by using this
as well as a few less clicks. So if you go to layerswap, you can, you know, their integration for coinbase is actually very seamless right now for some of the other centralized exchanges, not so much, but, you know, I've used it and it's actually a very convenient way to move USDC
between coinbase and osmosis and you don't have to pay any sort of Ethereum transaction fees while doing that. So very, no Ethereum transaction fees or Axelar bridging fees. So question for you there, Sunny. Are there any security issues with that?
If you're opting in and pretty much connecting with LayerSwap with your centralized exchange and then your wallet as well. What happens is you authorize them to withdraw a specific amount. Let's say I'm like
I want to transfer a thousand USDC from Coinbase onto Osmosis. What happens is when it opens up the login with Coinbase sort of UI and when you do that you actually have to tell Coinbase I'm authorizing this
service provider to withdraw a maximum of 1000 USDC from my account. So, you know, they won't have the ability to withdraw. And you have to like, manual, if you go through the layer swap like UX, it'll show you, you actually have to manually type in to the coinbase OAuth system.
like how much you're authorizing. And so this kind of like, you know, you won't get into a situation. It's almost similar to like, you know, in the Ethereum world, EVM world, how you do like token approvals, right? When you want to give a, if you want to contract to be able to pull the ERC 20s from your account,
You first have to approve saying hey that you're allowed to withdraw up to this much from my account and so it works It's kind of like a bit that's a good analogy actually The other thing is that layer swap is Trusted in during the period of the transfer. It's almost like
sort of like a similar to like a how a fiat on ramp works, right? Like when you when you work with when you use transact or kato on us Moses, right? You are trusting them for that brief period of the transfer where you know, you first you send them fiat and then, you know,
They confirm that and then they send you USDC or Osmo. So it's a similar thing here where you are first sending the Brands for a team, the team behind Lyosov, you're first sending them the USDC on Coinbase. And the thing is it's using Coinbase.
So it's using Coinbase's internal transfer system rather than on-chain transactions. So that's why you don't have to pay any e-thcast fees. But yeah, so it's using Coinbase's internal transfer system. They get the USDC and then they send you USDC on our devices.
has a very similar trust model to like any fiat on Ramp that you might be already interacting with. So yeah, so that's a good point. Yeah, it's worth noting those two like security considerations when deciding to use Lara Swapper not. Gotcha. Good information.
Yeah, so we will ask the, I think maybe we can ask the OSL or someone to put together like a little demo of how to, like a video walkthrough of how to use layer swap that could be probably helpful for a lot of people.
But yeah, so I think those are some of the big launches that I guess happened in the last two weeks. Some upcoming ones that are looking forward for autonomy is working on their limit and stop orders system. I think they are going to be putting that up
for governance proposal pretty soon. The stream swap and IBCX contracts are currently under audit by OEC security. So once the audit results come back from that, I think they're going to be ready to put those up for governance proposal as well.
Mars will be launching their fields of Mars, which is like their sort of leverage yield farming protocol that they built along with Apollo. So, you know, I think they were planning on trying to launch that by the end of the month, or at least get the, yeah, put that up by the end of the month.
with them. I think they were waiting, I think the Apollo team ran into some issues with deploying their contracts, so they might affect the timelines a little bit, but after within the couple of weeks. >> Sunny, I have a question back on autonomy. So with autonomy, they're building
limit order is how is that going to differentiate with the ones that the team will be building? Yeah, that's a great question. So I think maybe we'll try to get the autonomy team on for a update from the lab soon where they can talk about how they're building it. But the difference is that autonomy's limit orders and stop orders are not our
not in the AMM, but rather they are intense that you declare. So how do you, how do you, how do you, how do you, how do you, how do you, how do you, how do you, how do you, how do you, how do you, how do you, how do you, how do you, how do you, how do you, how do you, how do you, how do you, how do you,#
I want to sell this Osmo for $1.50. What they do is they have off-chain watchers. The reason the project is called autonomy is because it's like an autonomous
So they have these off-chain actors that are watching the pool price of Osmo and they they see that oh if they if it hits a dollar 50 that's when they can call the contract and and trigger the
sell of Osmo for $1.50. And basically contract will only execute if it actually successfully executes for $1.50 if not the contract just gets revered. So you don't have to worry about autonomy.
successfully or not getting you the getting your worst price than your limit order. The only difference is you do that. You have less guarantee of execution as you would in the on chain limit orders because how on chain limit orders work is that they will
You'll limit order will have to clear before the price can go above $1.50. Because it will hit the limit orders and then go start executing against other liquidity. So yeah, there's this tradeoff that you make when using an economy that you
There's a chance that the price actually jumps up to $1.51, but then autonomy didn't have time to trigger it. Their bots couldn't get to it fast enough, and the price drops down below $1.50 again. It's possible that your
trade doesn't execute. So that's the one trade off when you use autonomy. So obviously I think that like on-chain limit orders will be better for this use case than the autonomy one. But the drawback is on-chain limit orders can only exist
or like pools that exist, right? Like you can't, let's say there's an Osmo U.S. DC pool, yeah, you can place limit orders on that. But if, let's say you wanted to make a limit order for a selling Juno to buy Somalia
It's very unlikely that there's going to be a deep liquid order book for like Psalm Juneau. In that case, it might just make sense to use an autonomy limit order instead. Good information. So with that explanation, thinking back to how Mars was
not natively integrated into the front end. How will autonomy be in the same sense where it's going to be like an external website and users need to go over there to place that limit order? Yeah, so they actually have a, it's really nice actually where they have a conversion of the
It looks very similar to the OS website just with like living and stop order functionality added in. And so for now to start off with, you know, you're going to have to go to a different website until, you know, we want to let autonomy like
be proven out before we like presented to all users on like the osmosis main site. So, but you know, you know, you will probably like link to it by, by, to like autonomy.osmosis on zone or something like that. Give, give people that easy access. One of the things we're actually working on right now is they
So it seems like the trend with a lot of these
things that are getting integrated on chain but aren't getting integrated on the native front end. Are they all going to roll out like this word? None of them are going to be on the front end or will they eventually potentially be integrated like the idea of Mars being or the lending platform being
integrated? Yeah, so the goal is that we want these things to eventually get fully integrated into the OSOS front end, similar to how we did with Axelar, right? So Axelar, you know, if people remember a couple of few months ago, like in the first few months, you actually had to, we just would link out to satellite as
the way of like depositing to axelar. But then once we were like had the time to integrate it properly, according to like the UX we want, you know, now you have this like more native integration of axelar into the osmosis front end. And so that's sort of like the, I think the
We're going through a lot of design changes on the osmosis front end. Once that's done, we want to see which process we're going to do.
products have the most traction and do users want to see on so we can do prioritization of what to start adding to the front end and what order. >> What about something like Babylon that doesn't necessarily have something for a user to go interact with but it's going to be integrated natively.
And also speaking of Babylon with their security summit coming up, can you talk on the first question I asked and like what's going to what's going on with Babylon and and maybe like what this whole security summit's about? Yeah, so yeah Babylon isn't something that's super
The closest thing that maybe is a little bit user-facing is wallets. Wallets might want to be plugged into Babylon, but even that should be something that's happening pretty behind the scenes in the internals of Babylon.
of the wallet. So I think that's sort of the stuff we don't want to really put into the like, you know, there's not really a way of integrating that into the osmosis front end, per se, right? There's nothing to show users there other than maybe like, I don't know, yeah. And same
We have an awesome ecosystem page which shows all sorts of things, developer tools, explorers, all sorts of stuff that you want to do. But the in front end app store is really meant to be more user-faces.
thing like, "Hey, here's like things you can actually go interact with." So that's what I don't imagine Babylon sort of being part of that. But yeah, you mentioned this shared security summit that this is happening next week, Thursday, so part of the
Denver fiddle week. And yeah, so it's a shared security summit co-hosted by Babylon and Eigenlayer where they're going to be talking about, you know, all sorts of different models for shared security. And so we'll be talking a little bit about, you know, I'll be giving you a talk.
there about mesh security as well. And yeah, so if anyone's in Denver for East Denver week, come check that out. Have you perfected your mesh security talk? There's definitely been improvements. I think there were some, I think like one of the big
Flaws in the Cosmoverse version of the talk is I think that it was a little bit unclear I think a lot of people think that Mest security relies on validator set overlap which it does not that was like It was sort of like a way I was building towards like I was using this like oh there's one way Mest security work could work
but here's the problem with it. This is how it actually works. But I think I just didn't explain it as well during the Cosmiverse talking a lot of even to show today I think a lot there's a misconception that like Mestricity relies on validator set overlap. When in fact it's a design explicit design goal of our Mestricity design to not rely
on validator set overlap because that will lead to massive validator centralization. Hopefully I'll be able to explain that a little bit better this time in this version. The goal of this is actually more to, I think everyone in Cosmos land is very aware of mesh security right now.
But the idea is to share this very exciting idea beyond just the cost of community. There's a lot of inspiration actually in the mesh security design from EigenLayer. And in the same way, there's a lot of inspiration to EigenLayer from the cost
So it's a good opportunity to share mesh security with the larger crypto ecosystem. >> Speaking of mesh security, what were some of the key takeaways from the debate that was hosted by cryptocito with Nick White from Celeste?
Yeah, so I actually feel like we didn't talk as much about mesh security as much as I would have liked or thought. I feel like I still didn't get an exact explanation from Nick on what his biggest concerns with mesh security are.
Other than that, he said that most faults can't be proven, but I think I'd be resolved that. I think we ended up spending a lot more time talking about data availability systems more so than anything else. I think the result of that was like, yeah, we kind of came to agreement that like, hey, data
is useful. I guess there's a little bit of a question. I think it might take away on the whole data availability thing. Data availability is useful for like cross-chain communication. Will it be something that all cost those chains
internalize versus outsource. There's different parts of building. It would probably likely be a combination. If you look at Bridges as an example, some cosmos chains decided to fully internalize their own bridge. I think injective runs their own version
of the gravity bridge, you know, door chain built all their own bridge, internal bridges. While Osmosis took a more like outsourced this approach, right? Like we're like, okay, bridges are actually very hard and this is not something that I would rather work with a team that is like, you know, full-time
focused on the bridge and making sure it's secure and functional and stuff rather than have it be like a side project of like the osmosis development team right and so I don't know where mesh secure where where data availability lies on it in my my take is that it honestly just seems to be something that
If it's a simple enough module that every chain just adds to their own blockchain, it seems like... I don't know. So, yeah, it's almost like the question was this idea of mesh data availability versus like hub and spoke version of data availability, right?
So, we'll see how that plays out.
Okay, last question of mesh security. Are you able or is mesh security at a place where you're able to give an update on timeline and how it's going to unfold? So I'll stay tuned for our talk like shared security summit will you know have some announcements
around like some of the development and like how you know, basically there's a you know a number of cause-nose ecosystem projects are like contributing funding towards like towards this and so we'll talk a little bit more we'll share and announce the initiative there okay
Awesome, you heard that guys just stay tuned for the US Security Summit. Speaking of the Security Summit, what is going on with the Axelar Interop Summit and speaking of events, can you tell us about Osmacon 2023 yet? Is an official date able to be shared yet? Or are we still waiting?
Yeah, so, sorry, did you say US security summit? I don't think so. Did I say that? Someone tell me if I said that please. I swear I said axelar. No, I think I said share security dinner. Okay, okay. Yeah, this is definitely
not a US security summit. Awesome. It's not a US security. Someone DM me if I said that. Yeah, so interop summit. That's like a also in Denver hosted by the Axler folks. Yeah, it looks like it's shaping up to be a pretty cool event.
a lot of people, not just like causes ecosystem people, they have a lot of great speakers from like a bunch of different ecosystems. I'll be on a couple of panels there. So yeah, come check that out. Awesome, Khan. Yeah, so the date with like 99%
percent certainty right now is going to be July 21st on 2023 in Paris, where we are nailing down just the venue right now, but it will be in Paris on July 21st. That's the day right after ETCC. So ETCC
see is July 17th through the 20th. And so, yeah, this is going to be the day right after. You know, goal is, you know, we're trying to get as many Ethereum ecosystem people to attend and learn about osmosis and the Cosmos ecosystem by attending OsmoCon. So, yeah, if you're interested in coming,
book the dates. Yep, and it's also one day before the Nebula hackathon and two days before the Nebula conference and one month after the Gateway conference in Prague if anyone wants updates on events. Yeah, so there'll be some cool Cosmos. There'll be a lot of cool Cosmos stuff happening in Paris that week, so double
I've been seeing a lot of feedback requests on Twitter lately from all the accounts pretty much. Can you tell us about what these are asking for? What are the ecosystem ideas you've been reaching out to Twitter community for?
Yeah, so we have you know doing a lot like I mentioned just a little bit ago like you know working on re
Just improving the osmosis product and we're trying to figure out, you know, just get feedback from the community, what are the ways that we can do that, what are the biggest pain points that people find, what are the things that we can improve.
We've mentioned high PRs are fun and all, but they're not the product of osmosis. They're a bootstrapping system, especially with concentrated liquidity around the corner. We should be expecting those to go down.
And so what we're really trying to do is figure out like okay, how do we like Make sure to design the osmosis front end and product to be What are the what are the use cases that people you know the goal is to get people trading on on osmosis, right and how can we imagine?
to improve the trading experience on osmosis. That's what we're trying to focus in on. What are the features and things that you want that users will want on osmosis. It doesn't have to be trading, but it
What are things that people want to be able to do from the osmosis front end? Do people want to be able to stake from the osmosis front end? Do people want to be able to deposit into Mars directly from the
supposed to run into people want to have like fiat on ramps built into the osmosis front end. So you know what what I was talking about like hey there's all these integrations that we can do and it's by talking to users is how we'll sort of figure out a prioritization schedule for them.
Awesome. Were there any other updates that we skipped over when we started diving into all the Babylon and extra stuff? Yeah, so I guess a couple of other updates.
on the two main couple things. One is we talked about outposts of lunch last time and the cross-chain swaps. The actual code side is basically like the chain side code is basically complete. The squid team is working on
integration right now, but also the OSMOs' grants program will be given a grant to a team called NABLA to start building the OSMOs' the UI for these outposts. And so that way we can start deploying them on
more chains and having a way for people to interact with them. So, so, Noble was the team that built Sinfonia. Sinfonia for, you know, anyone who's not aware is like sort of the bit song, fan token focused version of the osmosis front end. So if you go to Sinfonia.app.app.app.app.app.app.app.app.app.app.app.app.app.#
It's like an osmosis front end, but almost like an app specific osmosis front end, right? And that's kind of very similar to what Outpost UIs are meant to be as well. So yeah, we'll be working with them. I think our target is to have
The first outpost be deployed on Neutron. Neutron is a, you know, the Cosm wasm chain that's being deployed as part of ICS deployment. And so, you know, it's a brand new fresh Cosm wasm chain. And I think it's a good opportunity for osmosis to
common, you know, planets flagging the ground and be like, hey, look, you know, cool, like osmosis can be like this osmosis outpost can be the biggest and like primary decks for the neutron ecosystem. So yeah, that's something we're pretty excited for. So for those, for those that
may not know, can you explain what Squid is concisely and then explain like are these outputs all needing Squid or can it be done without it? No, Squid is separate. So the outposts are something that we build. Squid is they are working with
They are allowing cross-chain swaps to be triggered by a axelar general message passing protocol. So the cross-chain swaps implementation that we've built, it allows you to trigger cross-chain swaps using, you know, the cross-chain
So I think the same swaps are basically an IBC meta protocol. But then it's how do you trigger them? There's like different ways of triggering, you know, generating the necessary IBC packet to do a crossing swap. One is you could just do it from a front end, right? And you can just have the front end JavaScript code generate the necessary
So that's how the outposts UIs are going to work. Then there's also the outpost contracts which is a Cosm-Wasim contract. What that does is it allows other Cosm-Wasim contracts on a chain to do cross-chain swaps.
The outpost of UIs are almost like independent of the outpost contracts. The contracts are for other cause and wasn't contract, the UIs for users to interact with it. Squid is allowing a third way of interacting with cross-chain
swap, which is via Axelar, GMP, general message passing. And this is going to eventually be used to enable cross-chain swaps from EVM chains. One of the things that is going to be used for is going to be to do bridging between
like allowing people to move between, you know, swapmatic on polygon for abax on avalanche, right? So what they'll do is they'll break the bridge thematic, use the cross chain swap on all surfaces to switch it to abax and then use axel out to bridge it to
So they'll be working on that. Another use case for the squid router is that for dy/dx, what they're doing is that like making it so people can deposit their USDC, swap it to Cosmos USDC and then forward it to
to the dydx chain. So yeah, so you know, it's basically a way of plugging Axelar messages coming from EVM chains to also be able to use cross-chain Swaps as well. So that's sort of what Squid is working on. >> So it's a correct to say that anything that involves Squid has to run through Axelar.
Yes. Gotcha. Cool. You just talked about dy/dx. Can you share anything further about dy/dx as far as what their timeline is? Are they moving along sooner than later?
I don't know how much I can, I'll let them share their own timelines, I guess. But yeah, they're definitely moving along.
We had integration to deposit USDC into dydx via osmosis is coming along quite well. So yeah, excited for that. Awesome. Anything else?
Yeah, so two other things. One is obviously with the BUSD news. I think it is prudent to or probably just necessary to wind down the BUSD tools on osmosis that includes the BUSD Osmo pool that was incentivized. I think the
audio proposal up for that. But also, you know, the three pool, the current incentivized three pool on osmosis is USDC, Tether and BUSD. And so it probably makes sense to remove it, to slowly pull incentives from that and move it to other
pools. One of the ones I would suggest that we're proposing is actually we should create a three pool with just different types of USDC. So whether it's like USDC from Ethereum, USDC from Polygon, USDC from Avowance, this will make it easier for people to deposit USDC from any of these chains and this has
three biggest? Those are the three biggest ones right now. The ones that have Axlar integration right now. I think Solanas might be like one of the biggest, but that's not supported by Axlar yet. Yeah, and then
Otherwise, I think we'll leave it up to governance to decide other stable swaps that are worth incentivizing. I'm still a little bit of a tether-apologist maybe, or in the sense that I think people often discount how much value most crypto
volumes go through tether and if you look at even after the BUSD winding down tether supply has been actually increasing and the USDC has been decreasing so most of the volumes that were in volumes and supply that were in BUSD have been converting to tether rather than USDC.
it's important to not over centralize on one stablecoin and make sure we still have like stablecoin diversity within cosmos. That's one. And then the last thing I wanted to mention was with constant liquidity
How, you know, we're just starting to think about, okay, you know, code wise is. Close to done. The actual core code is done now. We're now sort of in internal audits at this point. There's so just a little bit of work left on like incentives and front end, but the core code is basically.
basically under is in the view phase now. And so we're starting to think about how do we actually do the migration and one of the things that the current suggestion to governance right from us is that we should do this as a sort of slower rollout process where we start to move
Like a couple pools at a time so instead of you know betting the whole stable on like you know migrating everything to concentrate of liquidity and like one fell swoop Let's start with a smaller with like a medium-sized pool first let that run for a couple of weeks see
see how incentive, let's shift the incentive, see how the market reacts, uses React, LPs React, and then let the code prove itself on live chain and then we move more over time. Our suggestion was to probably start with the Osmo
I pool as the first pool just because it you know it is actually you know one of the I think it's like the fifth or sixth biggest pool but you know it gives and it's nice because it's a little bit easier for a market for like people to try concentrating liquidity on because you really only have you only have to worry about market making one asset rather than
two volatile assets because you know dies a stable coin. So yeah, you know, that what we'll be putting up like a sort of a more formal proposal on commonwealth for like how we should go about this, you know, this will probably be one of the biggest like ships in like osmosis.
until today, right? And so yeah, I want to make sure it's done in a thought out and, you know, conservative way. So yeah, look, so just a heads up for how we're thinking about going about it. All right, awesome. Anything else?
I saw this cool stack from token terminal that apparently osmosis has more daily active addresses than uniswap. So that's pretty cool.
there's a little bit of a bias there because that osmosis is a chain that has many things so that could include transactions that are like staking or doing stuff like that rather than necessarily interacting with the DEX.
It's still a pretty cool metric nonetheless. Awesome. Awesome. Well, I'm going to invite some of the members from the OSL to start speaking then. And thank you for the updates from the lab. Thank you.
All right, Robo, I'm inviting you. I don't know if you're on a laptop or something, but it seems like you're not getting the invite maybe.
and call Chaita, I've invited you to speak.
No problem. Cody, can you also pop a request? Because the invite seems to be bugged out.
So Rova, do you look like the photo of your profile picture? Or is that just a bad kid? Yeah, not at all. I just really, really liked this bad kid. So I scooped it out. Gotcha. Because Larry's profile looks like him. Sonny's profile looks like him. Emperor Osmo's profile looks like him. So I was just wondering if that trend was going.
Now I've yet to find a bad kid that looks like me. I thought about maybe picking up one of the robot ones, but they're a little expensive. All right. Did you say--
- For Osmo looks like a llama. - I think you finally caught the joke. (laughing) - So that took me a second. (laughing) - That's a complete joke, by the way. (laughing) - That's a complete joke, by the way. (laughing) - Jame Dipper Osmo does not look like a llama.
All right, Robo, tell us about what's been happening since the last prop, what changed from the last prop. Yeah, just go into it.
Yeah, so it might be helpful to give a little bit of background on this first for anyone that doesn't know. The Osmosis support lab is a community-led initiative that kind of supports all aspects of Osmosis users and users that touch Osmosis and it essentially in any way.
This could include obviously like osmosis end users, but also extends to entities like osmosis validators, node operators, and even other contributors. We assist the osmosis developers and the
the osmosis grants program and things like that. We do this on effectively all of osmosis's social channels, be that discord, Reddit, Telegram, as well as the osmosis support website at support.osmosis.com.
as of this most recent proposal. We've kind of expanded our operations a bit, you know, for a couple of different reasons, but we've kind of branched out more into like helping with community building opportunities.
and like a lot of public goods and osmosis tooling the ladder of which I can kind of like coldly speak to but just to kind of quickly touch on some of the community items we we run and operate the
Osmosis Community Updates blog and the Osmosis Community Updates Twitter which is here in the space as well. These are initiatives that were originally run by the Osmosis Ministry of Marketing and when
When the osmosis ministry of marketing dissolved, we thought that these were like extremely valuable educational resources for the community. So we wanted to make sure that we didn't let those kind of die out. And the blog has been really
really effective resource we we publish articles on you know various aspects of support just informational things on like new listings major osmosis chain upgrades and new features things like that we
also just recently expanded into kind of giving like an overview article of the various osmosis governance proposals that are on chain. I know that governance fatigue is very much a thing, so we wanted to get people, you know, like short and concise summaries of what a proposal means.
and what a yes voter a no vote might do and some arguments in favor and against for each. We also run the Osmosis Crew 3 initiative, which is like a community gamification platform.
And that helps a lot with engagement and just getting people more involved, which is more important than ever in a bear market. We also, as of this quarter, started the Interchain Lab, which is a kind of like discord's version of updates from the lab.
Just trying to make sure that people that may not prefer Twitter You know get to have access to a show that Educates people on like osmosis ecosystem things. We had we had Larry come up with with Mars protocol and we've had people like strut
and skip protocol come up to chat with us as well. We have another episode of that airing this Friday and that the OSL is also going to be on that one as well and I'm kind of hoping we can do more like interactive tutorials of some of the tooling that we're going to speak about here today.
And I think with that, I'll kind of kick it over. We have more to talk about, but I want to get cold-eated to talk about some of the tooling infrastructure, because I think that's a lot of like the meat and potatoes of what we've been working on this quarter, and it's some pretty exciting stuff.
Sure, coldy hop on. Hi guys. So for those of you who don't know me, I've been with the OSL since the beginning really, since the first proposal that passed on Shane. I also
I run a osmosis validator as well as validators for a bunch of other chains in my living room. So that's what I do for a living basically these days.
Now on the OSL we've been
evolving in our mission internally to moving beyond a simple presence on the social media and the chat support to really try
trying to create solutions for users' problems. Now one good example of that is we've started relaying IBC packets on some of the
most popular channels between Osmosis and other chains. So for example, on the SmartStake dashboard, which is really great, we're registered on there. And I think at this moment we have made
over 14,000 transactions since we started, I think less than 30 days ago, or at least since we started keeping track. And one thing that's interesting there is I think that we are one of, if not the
only organization that's not a validator or like a core team that is actually running relays in the Cosmos ecosystem. So I think that's pretty cool. Another initiative that we've been working on is we're actually
running our PC API node for people to access the Osmos blockchain. I have some stats on that that I was just looking at today since we started keeping record about 10 days ago. We've had
1886 unique users for a total of about 12 and a half million requests over the past 10 days. So it's a lot of data that's being moved there.
So these are just kind of examples of stuff that we've been working on that's kind of beyond simple support stuff and it is more kind of trying to, as Robo said, create like public goods for the community. And as a further example of that, we have
a little tool that we made and just put up a beta version of it today. What it is is it's a tool that allows a user, anyone really, to clear and congested the IBC channel by themselves by simply clicking a button. If you want to
check it out. It's not really great for public demonstrations because it kind of runs in series. So each request runs one after the other. But it's at oc.osl.zone. It's basically just a little selector where you can select a channel and request to clear the
packet and it'll just tell you if you cleared it or not. I've been like spamming some lightly spamming some packets on the Iris channel because it seems like there's nobody else re-laying it now. So if you click clear on Iris you might be able to clear a packet. And I think that's something that
I wish I had thought of a long time ago because it's something that's so easy.
that will be impactful for helping user experience. In the past, we've had to reach out to the relayer team or whatever validator or organization is relaying a specific channel.
it's jammed up and wait for their response. Sometimes that could take like minutes, hours, days even. If it's on the weekend, for example. So I'm pretty proud of that one, honestly. That's awesome. These are pretty cool updates.
So it seems like, you guys are kind of like shifting into a lot more technical things and better public goods related. What kind of spurred this shift and why are you guys working on these things now instead of a few months ago? So this is kind of something we've always been working on in the background at least
like internally, we've been creating tools that are helping our own personnel to better access and understand the osmosis blockchain and better understand technical stuff in general.
So it's kind of like an extension of that. I see it as like an evolution and extension of our mission. It's kind of like continuing to provide support and education, but in a different way. And it definitely
I see it as like a natural progression. And we have noticed that like the need for like 24/7 support or like having
So many people across all channels may be diminishing with the market conditions and external factors. But there's definitely a lot more that we can provide as an organization of
value to Osmosis and to the community. And just like these, I don't know, quick examples are even things that are like pretty impactful in my opinion, because
You know, they're basically core functions of osmosis. You know, osmosis needs IBC to function. Osmosis needs access to good nodes to function and we're helping with that.
Yeah, just to give a little more color on that, for anyone that's sort of been around since Osmos has launched, there used to be bigger issues with IBC and relaying transactions, on big channels like Cosmos Hub to Osmosis might go down for an eight hour period and then basically all
everything would grind to a screeching halt. Relay or infrastructure has improved significantly since then. I can't even think of the last time we had a downtime on that channel in particular, but the smaller assets that may not have like the like the financial wear with all
or even the technical wear with all to support consistent uptime on their IBC Relayers. We still see down times for those assets all the time. And so that's one of the areas where we kind of, you know, as people that are helping with support, we're kind of like the first line of defense that we get the
reports and it's just easier to say, okay, well instead of trying to go hunt down, you know, whoever's relaying on this channel, if anybody, why not just clear it ourselves? And so that turns up potentially eight-hour process or multi-day process, as Colby said, into a, you know, five-minute process or less.
So it really helps with these are experience in that sense. So with what Kony kind of said is how like the live chat support isn't really as in demand and how you guys are kind of shifting into these technical public goods, you know, needs. How is that, is that transition happening like this coming prop? Are you guys, you know, going to focus
focus on even more causes or potentially like, there's this idea of, you know, dev rel is a pretty valuable effort, but at the same time, like, you know, what if there's community dev rel? And it seems like you guys are gaining these abilities and learning and having this ability to be community dev rel in a sense.
Yeah, I mean, I honestly would like to see us do a lot more of stuff like that. Just another thing that I think is worth mentioning. We've been working pretty closely with the the osmosis front end team these past while
the whole time really, but these past few months we've been pretty close with them now, and we're getting issues solved, identified and solved more efficiently than ever. I think it is really
dev route sort of an organization in a way that is how we've been acting and I would like to see more of that for sure. Yeah, I've also noticed a lot of these communications between the OSL and the front end team and like
getting all these bugs cleared out. I think it's quite incredible how fast and how frequent you guys can spot these things and get them addressed and send them over to the front end team. I know like crypto assassin sends these a lot. I see you call chain a lot as well. So I think that's pretty awesome.
Yeah, thank you for recognizing that. That's cool. Recognize.
Yeah, well, what other updates do you guys have for us, Reba?
Yeah, so we have a couple of things in the works. I'm not fully sure, you know, concrete timelines, but one of the things that we want to do is start like giving back to the community in ways that are, you know, significant and can help.
just, you know, ensure that the Osmosis community continues to thrive. And I'm in Siberia and Arquants me to shill ledger. So I'm going to do that. But we've been working with like members of other communities to try and foster like cross community building relationships.
A good example of this is we've been contacted by some of the mods from the ledger Reddit and they want to do like, you know, joint AMAs and just kind of like better security education, you know, collaboration. So a lot of
things like that. I've been speaking with -- Will this include a free new ledger? One of those fancy ones? I probably not, but you know, you never know. Maybe for you, Aaron. Awesome. You know, I've been talking with teams like the
stride team, like the quasar team about potentially doing other kinds of community collabs through things like crew three, you know, been helping the the auto team, you know, with some things like that. So really like, and actually we just did a collab last night with interchain at
and rock effects put on an event in the Osmosis Discord. So more community building, you know, events, more collaborations. I think the one of the great things about Osmosis is that it's sort of, you know, obviously the hub for economic activity in the
ecosystem and I think that you know just sort of naturally it's become kind of the hub for community activity as well and I see part of our mandate you know in addition to all of the technical tooling. Devoral stuff is to help foster and and build the osmosis community from from the ground up.
Awesome. Well, I think it's exciting this kind of shift that you guys are working on. Obviously after like over a year of existence, you guys are kind of finding this stride and kind of seeing where the OSL really needs to exist in. And I think that's pretty valuable.
Yeah, so I think we're good to end it here. We're right on the top one hour in Robo Coltie. I think we can end it here. Just really quick.
Quick way out. You know, I want to thank you. Thank you guys for having me up and just let everybody know that we have. We're planning on putting our next funding proposal on Commonwealth towards the end of this month.
really, really want to make sure that we get everyone to be back because, you know, the community is the reason we're here and I really want to make sure that we're incorporating everyone's feedback into that.
Sounds like sunny just unmuted to type a few things on his keyboard. I think that's the end. All right, thanks everyone. Thanks. Thanks everybody.