Home
Contribute Contact Us Browse all meetings
Home Contribute Contact Us Browse all meetings
Hummingbot / Community / 5 Apr 2023
Hummingbot / Community / 5 Apr 2023
Previous Meeting Next Meeting
⏯
Add meeting Rate page Subscribe
youtube image
►
From YouTube: Hummingbot Community Call | April 2023

Description

* v1.14.0 Release Highlights
* Vote in Epoch 4 Polls!
* Botcamp Update
* Gateway Demo: installing using Docker Compose https://github.com/hummingbot/deploy-examples

A

Okay, okay, great um so, okay, now we can finally start the call uh sorry for being late. uh So today uh we're gonna. Do a few things we'll go over the uh the release highlights in the last release, 1.14.0, which just came out last week.

A

um We also just launched the epoch for polls uh which gives Community a voice in determining which exchange, connectors and strategies uh should be in the code base and also allows Community to prioritize what issues we address in um the following month. Then I'll give an update on how botcamp our our Dev boot camp is going. uh We just started the fourth cohort um and finally, I'll give a demo of the new installation process for Gateway. uh We recently uh gateways our Dex connector module.

A

um You know, users have historically had a lot of problems, getting it installed and compatible with hummingbot, so we recently moved it out into it's a separate repo, and now we have a new process that I'll show you for linking the two together and should be much simpler than uh the the prior version and finally, uh we'll do an AMA. So hopefully uh this uh this is. You know this. This video experience with full HD color will be better than just doing it uh on audio.

A

So, let's get started, oh wow I think it's the first time. Some of you guys are seeing me on camera. um uh I I guess, uh look down more down to earth. Thank you. Well, I. Think, that's! uh You know it's probably a result of having getting gotten beaten down by all the turbulence, the crypto markets over the past few months. You know it's a less more humbled and excited to just code and build stuff, as opposed to you know, trying to deal with FTX and all that craziness out there.

A

Okay, let's let's get started so um first, let's go over the release, highlights for version 1.14, um so uh there uh I would say I'll just go over these release. Docs, because I think um these uh kind of really go like prevent, provide the the best explanation of all the new stuff in a certain release.

A

So uh the what's new here- and this is a new transition- is now since we separated hummingbot into hummingbot uh and I'm like Gateway, two separate repositories, uh we offer you the ability to install both using Docker or GitHub, and the pathways for both are intentionally very similar. So if you know how to install hummingbot, you should also know how to install Gateway with either Gateway, uh whether with a Docker or GitHub, but but I, think the recommended way that we think you should install hummingbot, especially for Docker.

A

If you're going to do something more complex is with this new deploy examples repo and later on, I'll show you how you can easily use this repo to um basically install uh hummingbot plus Gateway instances together in one single step.

A

um The other big thing we launched uh is the quick start guide. So um this is because honeybot when we first started, it was just really a simple Market making tool, but um over the years as we've added uh more functionality, it's really turned into much more of a framework where people can build any type of custom, Quant trading strategy, so because of that, we've kind of really shifted our focus in terms of who the user is to a more technical archetype. And so this new quick start guide.

A

It shows you how to um basically, uh you know, start with just a simple hello world type script that prints the the Bitcoin price to the log um and then and then um and then the next step, you'll build a a simple Market making strategy, basically replicating uh the pmm strategy as a script um and the third exercise, we teach you how to uh launch a custom format status where you can. Basically, you know display any type of variable. You want in the status function uh in the fourth exercise.

A

This is where you're going to start a really, uh you know explore the power of scripts, because you can uh essentially just add any type of logic. You want into your Market making strategy, for instance, this is a very simple price ceiling price floor that that limits um the price range where your Bot is active and, finally, in the fifth exercise, the quick start guide. Teaches you how to make this a lot more Dynamic. uh It uses a new candles feed feature.

A

We added in the last release to um dynamically calculate uh the Bollinger Bands and and use that to inform how the price ceiling up in price floor are being Set. uh So so, overall, we think this quick start guide really gives it really teaches you how to use hummingbot in a more custom uh in a in a more sophisticated way and uh based on you know, kind of the feedback from the community.

A

We've had it's really the folks who've been able to customize their their Bots that have had uh enduring success running hummingbot, so uh that was probably the biggest thing that came out in one point, one four, um some of the other stuff we added. uh We also uh changed the installation section using the the new deploy examples, repo um and a bunch of other new documentation Pages uh as well like the candles feed docks.

A

uh The orchestration module docs and the smart this these new smart components that we added recently um overall documentation is going to be a big Focus for us in the coming months, because honeybot's becoming a more um you know, more professional, uh more complex code base and- and we think documentation is the best way to allow the community to use it with confidence.

A

um So the the community team, uh clippanagi and holy Roger, who are working on an orchestration module, uh have now shipped phase two so phase two, um you know, provides more interfaces for subscribing to topics and listening to messages um and um and I think you know this is this: module is going to get more and more sophisticated in the next few months and uh we're really excited to see um the the interface that uh the the the team's working on that's going to stitch everything together and um I.

A

Think it's going to really showcase what the orchestration module is capable of. So look out for that in the next couple months. uh We also added the the kucoin uh Perpetual connector in this last release, uh which, uh since cool coin, is a silver one of our silver connectors. Where we want to. You know support them and continue adding new new features, and so I think this.

A

This connector, um which is still in beta testing, we're still ironing out some Kinks to this connector, uh should uh be something really useful for the community and on the Gateway side uh we added a few a couple new connectors in this release.

A

uh One was the x-swap Dex on the xdc Chain, as well as dexilot, uh one of our first Club Dex connectors, uh which is an order book uh desk connector on the Avalanche blockchain, so um and- and you can there's also some other updates so overall, this was a really jam-packed release and I'm really proud of the team for both pushing out new features as well.

A

As you know, merging in um updates from the community um overall I think you know we're starting to get more efficient, uh with updates as you're, seeing um and I think it's a result of kind of like some of the process, improvements that we've had a chance to make.

A

um Now that our focus is more on improving the top uh gold and silver uh connectors and less on trying to maintain every single change. Every single connector in the code base. So so I think that's why I think the governance process, uh even though it's still pretty new uh we're we're. You know we're very motivated to to continue flushing that out, because I think that um you know by allowing the community to prioritize. You know where we spend our time. It does allow us to. Hopefully really you know, improve the code base.

A

um You know on as opposed to spending lots of time, maintaining it uh great. So let's go back if there's any more questions and let's please leave them in the in the chat about this particular release. Otherwise, I'm gonna, move on and um and and do the next uh step in the agenda, which is to vote in the uh in the epoch for polls. So um just as a recap uh polls are the process we use to tell the community or to have the community tell us how we should allocate our time.

A

uh So we have four types of polls. Currently, uh the um the the issues pull uh basically tells us. You know how to prioritize our issues, so uh that one is, is uh this over here this issues poll, uh so the issues pull um I'll I'll vote on this one first. Actually so, each of these, what I try to do on the community call is just to vote myself using my own.

A

uh You know fatality.eth wallet, just to kind of show you guys, um you know how I perceive it as a personal member of the community. um Just as a caveat, this is not. You know. This is not promotion of any exchange or strategy. This is really just myself.

A

um You know acting on my own personal behalf as an h-bot holder, uh trying to show you guys uh how you know how how I would vote basically, so this issue this poll, this issues poll, is designed to basically tell us of all the 300 plus issues in the hummingbird code base. Currently that are open, which ones should we actively work on resolving so work on resolving means. We either fix it ourselves, we either or we investigate it and close it.

A

If we determine it's not a real bug or we might assign the bounty to a developer, we actually track the status of these issues in our um in our hummingbot uh project. I. Think, there's a project that tracks this.

A

So if you go to uh the the I mean the hummingbot repository here and I think projects uh you'll see you'll, see a project um that that tracks, the uh the I think the the priority issues here.

A

So this project issues uh board here uh tells you kind of the status of of these, of the issues that have uh been you know prioritized in the prior months and how we have been resolving them so over here, um yeah, so I would say: I've looked at some of these uh issues already beforehand and so um I'm gonna I'm definitely gonna nominate this one here. uh This is this is the one that um you know, I'm sure many hung out.

A

Users have seen where, if you, uh if you kind of load, a hummingbot and some some connectors, not you know working uh it's gonna flag, it's gonna, throw an error because it can't retrieve the trading pairs from that connector. So uh this is a legacy connector that I think it just um you know, should be removed from the code base, so I think we should uh kind of yeah remove. You know anything related to just errors like this that are related to unworking, connectors, um I, think also kucoin.

A

Perp uh is you know to me: I think this is an important. um You know these, uh because we're trying to really address some of the these issues with uh kucoin, so so I I think anything related to coin or coupon. Perp I think we should try to fix um and and I say, I also think um uh it's a I think installation should also be important, so I, I, overall I I, see lots of great issues.

A

That I think should be fixed this time, but I think just um I'll, say uh yeah, I, I guess like because uh I guess I can vote for more. But in my opinion these five will be the ones that I would try to prioritize um in. In this release.

A

So uh what this does I should mention one change that we're making uh in this whole process from the last time, which is that um we used to use a quadratic method to allocate the votes, uh and it was done because we thought it would make it fairer, but we found that it was actually hard to determine. You know how my my votes were allocated, uh because the numbers here would shift, depending on some quadratic calculation, uh so this time around uh We've made it simpler.

A

So what that means is um you know, however, many h-bot you have in your wallet is going to be equal to how many votes you you distribute, um and so, if you basically do like this, it will just evenly spread them out across these five issues.

A

um Okay, so now let's go to the other polls, uh so the other three polls um are uh the ones we do only on a quarterly basis. uh So the the sex poll tells us how much you know, uh which of the gold and silver um sex connectors and uh and for the bronze ones. uh Anyone any connector that receives at least 100K plus hbot is kept in the code base as a bronze connector.

A

So the difference here is that um the the the the um the gold concealer connectors are the ones that we uh as a foundation actually maintain ourselves. uh So that's why, in the last quarter, we added uh because binance was gold condenser. We um we added the the candles feed uh feature for the for finance and balanced perpetuals, which now lets people. uh You know, collect historical data and create ta indicators uh on binance and binance pairs um in the next quarter.

A

We're going to crib bounties to add similar candles, uh feed features for the silver connectors, kucoin gate uh in a sentence, or you know, depending on what this country might be in the next quarter uh by voting uh and we'll also look to improve the gold connector as well. By supporting more order types like Market orders, uh you know staking or deposit and withdrawal, so so basically um we're really going to concentrate our engineering and kind of bounty efforts on these gold and Silvers connectors in order to make sure that we're continually improving them.

A

um So uh there's no requirement for you know the for the improvements to be added to the bronze connectors uh and for the bronze countries. We're actually not really going to take any responsibility for uh it's really up to the community to submit them in, um as, as you know, into the process and maintain them and so forth.

A

So in the last um quarter we actually saw BTC markets as a community maintained connector that was submitted uh successfully got into the code base uh and and I think it's a good example of something where you know it's. It's a small exchange. It's only available to Australian residents, but there's really no reason why some of the community can't maintain that connector use it um and make it available to everyone else. So we look forward to working with other. You know maintainers to kind of get their connectors and code base.

A

um You know, but, but we as a foundation will focus our efforts on the gold and silver ones in order to keep on advancing them and make sure they're they're good, so so yeah. So let me do the votes. um So to me uh you know I'm, gonna really try to focus on who I think the the exchanges that are working best and are you know, are safe uh and are available to the community.

A

So uh I'm gonna, uh you know, I, think binance, kucoin um and and gate are are definitely three exchanges that are uh working well. Also, these three exchanges are also the ones that are um are providing the the largest amount of fees. uh You know shared with us on a monthly basis, so uh I'll pick those um and so I. I also think that I don't think we should.

A

We should try to support um coinbase and Kraken more because we are seeing some consolidation in the industry uh and and I think you know what we um we should. We should try to. You know up level. The number of topics changes uh there uh I'm also going to vote for okx because um you know, especially with binance getting um investigated by the cfdc I. Think that it would help the industry to have more exchange diversity out there in okx.

A

um You know they've always been one of the top exchanges. It's still you know one of the like the most active ones and I think um you know they seem to be. uh You know in a good position to take away some of binance market share.

A

If Finance does um even more people are moving Capital off of binance and then finally, uh you know I I always like to support some of the small exchanges in the code base, so I'm also going to vote for BTC markets and and also in all markets, uh because I know that they're uh they're they're being maintained by long-term members of the community who um who I personally want to support uh so yeah, so I'll just kind of vote for this and um and then uh um and that's the the the the sex poll.

A

All right so um that's a sexual, and then the Dex poll works very. Similarly, uh these are all the um the the um the the Dex connectors uh in our code base. uh So this includes uh basically both the Gateway connectors um as well as as um as some of the uh um kind of like the the um the the the dydx and and other ones and loop rank uh as well in the code base. So on on the deck side, um so uh yeah I think it's the same. It works the same way.

A

uh You know it's, um it's uh the the top. Connector is gold. The next three are silver and those four exchanges connectors are maintained by us and we will try to improve them on a continued basis um and whereas the bronze ones are maintained by the community, so um as I'm I'm kind of the one working on uh Gateway a lot so so to me, I think we should um you know: I I, do think uni swap uh to me actually I, think uni swap in my payment, and um we still need a core functionality.

A

Work on Gateway, so uh I'm actually going to limit how many exchanges I vote for here, because I think the the there needs to be more work done on the kind of the core experience um focusing on a few uh top exchanges before you know we go too broad and I think that uh with Gateway you know historically, we've always tried to you know bite off more than we could actually chew, and- um and so we're still in the process of trying to get back to basics, deliver a really a good experience that allows someone to do something basic on a DEX.

A

So that's why I think I'm really going to try to vote? For you know the maybe just the four current ones. um You know to try to limit what the experience is going to be.

A

uh Okay, uh I think someone's saying that my my voice is not okay, uh okay, anyway, uh so yeah uh we'll try to fix any audio issues in the next time. But um Let me.

A

Let me do finish off the voting with the strategies poll, so the strategies poll this one is designed to basically select the course strategies and the way that this impacts the user base is because these are the three strategies we um our QA team tends to run the most so whenever, let's say a nuke, we're running long-term testing Bots and we kind of focus on testing these three strategies uh with the um the various connectors.

A

So uh it's it's not a guaranteed, but I think um the core strategies, the the the the the code base, the users select, will likely work better and being better maintained than the other ones, so um I I think I would say we're actually kind of we're moving away from strategies as a whole, because uh we want to encourage people and encourage customization with scripts. But I do think it's important for just as for maintain a few.

A

You know base basic strategies to help people who don't know how to code um interact with hummingbot, so uh I'm gonna I'm, actually going to pick I'm, actually gonna pick oblongata frankly, because I think um mm Arbitrage I feel like it's actually better as a script. uh You know on the Gateway side, people have like you fundamentally have a lot of things. You need to control so uh I plan on recreating a sample script that basically does exactly what this AMF arbitrage strategy work works and it makes it better.

A

So, in my opinion, I think we're better served by having a strategy like avanada, be um one of the one of the top ones or maybe even one of the other Perpetual strategies, because I feel, like um they'll, be easier for users to interact with um so I. Actually, you know, I would actually probably pick something like uh yeah, probably maybe Arbitrage actually as a third strategy, because I feel like people, people should be doing something with perpetuals and and I think um yeah.

A

Maybe if one of the core strategies was Perpetual related, uh you know we would. You know kind of like have the bandwidth to spend more time there.

A

Yeah, okay! Well, uh that's it! So no I think I finished all four votes, um and so we're doing this because we think uh you know obviously voting's not a uh it's. It's not a fun process, you know, but, uh but we think that by doing it, this way, hopefully we're making easier for you guys to vote, is really every four months. Every three months is really when it's important, uh but I think um we also want to make sure that you, you know that your votes really do have impact.

A

uh You know what what exchanges do you vote for uh and what strategies go for what issues are for? Is you know how we respond and where we actually spend our time in the subsequent uh three months.

A

All right so uh so now, um uh I wanted to just give a quick update on how botcamp our new death boot camp is going and then um and then we'll get into the gateway demo uh to wrap up the call um okay. So so uh we just started cohort four, uh so cohort four has 22 students um and uh and because we're trying to make sure we can serve every student properly and improve every cohort. uh We're gonna move to a quarterly cohort model after this.

A

So so far over 80 students have gone through bot camp and we're pretty comfortable. You know with. We think we have something really good here, because um overall, you know the students, a lot of students have built really. um You know interesting scripts of their own. uh They, you know I love them actually using these in production and and we think we can actually teach people, uh basically the art and the science of Quant trading in a six-week period and deliver a really fun experience.

A

People, uh in addition, I think uh I'm, really Amazed by kind of what some of the students have done afterwards. You know they've paired up with other people in the course um because it's like an ongoing program, they're joining the new events, we're doing like we're doing kind of like ongoing events for all cohorts and um there's a real sense of community, that's forming in among the bach Camp participants, both the mentors and the students.

A

So um that's why we're not as a huge to grow it to grow it, um because we want to make sure that the quality of a community and the quality of the student experience is there, uh but I do want to you know kind of like publicize it here, because we did just open up applications for cohort five uh I think we're in a cap cohort five at 30 students.

A

um It's not going to start until probably um probably late June, uh but uh but yeah it's open already. So if you're interested or you know any questions, please let us know, uh because uh overall, we um I think I think I think that this cohort based learning kind of process we can do can we can actually expand dramatically once we get the program in place, you know even better, but right now we're really focused on delivering a high quality experience for everyone. That's going through bot camp okay.

A

Well, finally, um I wanted to show you some of the uh changes we made to the installation process for hummingbot Gateway, uh which I think is going to make it a lot easier. So, uh um okay, so um so yeah. So, let's go through um and I'm gonna show you the new, deploy examples of repository and walk through how I would use that to install hummingbot uh and hummingbot Gateway together, uh so as I know.

A

uh So this is the deploy examples repository here, uh so this you can find this on your github.com hummingbot slash, deploy examples, um as you know, we're still working on uh getting the the docs in place. So uh currently the development branch has uh more documentation from the main branch, so I'm going to follow. What's on the hummingbot Gateway compose folder, uh so this folder has instructions for deploying hummingbot and Gateway together uh as a single.

A

You know in a single step, using uh Docker compose so uh to explain: what's really happening here, you know we, um a lot of the trouble people have had with Gateway in the past has been uh kind of like making sure that both the client, hummingbot and Gateway can talk to each other, and this was by Design, because we wanted to allow multiple hummingbot clients to connect to a single instance of Gateway, uh but we also wanted that to be secure.

A

So uh we there's a SSL certificate process where a Gateway has to know the passphrase used to generate the certificates as to be able to access these certificates in order for hummingbot to communicate to it. So uh because, there's some complexity in setting this up, uh you know we've always had to try to.

A

You know help and handhold users a lot um to do this, but I think it's a lot easier for users to install this with Docker compose now uh compose is a tool for running multi-container Docker applications and we've also found that it scales very well to more complex deployments.

A

For example, once you understand you can deploy one instance, if I Can Bot using compose you can deploy uh how about instance link to a Gateway instance uh you can deploy. You know three harmonic instances connected to a single Gateway instance and in the future, with the new uh Brokers orchestration repo uh you'll be able to deploy even more complex deployments, like you know, 100 hummingbot instances uh controlled by a single Master instance, or something like that.

A

So that's why we think compose is a good framework to build on top of, and we want to try to get everyone. You know who's using Docker with hummingbot to install using compose like this. So that's what I'll show you here?

A

uh Okay, so um so first um I would say you should have cloned this repository, so um here I'm just on the uh uh yeah I'm, just on the on the dev Branch here and and all I've done is uh here.

A

Let me let me just look at my containers, a second uh okay, um so uh I'm actually gonna go and delete my containers, uh so I can kind of show you uh how actually you know what I won't do that, because I'll, probably I'll, probably just make the the pulling and downloading process time faster or longer uh and increase the time of this demo. So so just uh just know that um yeah like, if you may want to just you're, probably starting with a fresh container or an image.

A

You know set collection, uh so you might have a slightly different experience than what I'll show you here, uh but the steps should be basically the same. So first uh you want to make sure that you can access Docker compose uh from the command line here, so um so one second okay. So uh basically, uh if you can actually start and compose and see, uh you know this message here. That means that you can. You have access to the tool, if not uh the easiest way to access.

A

This compose tool is to install Docker desktop, which is a application that helps. You manage all your containers, it's also GUI, so you can also manage your containers, your images more easily and after you install Docker desktop, you should have uh access to the compose command um in the in in the in the command line.

A

So um so so then, then after you do this, uh the the first thing you'll do is we'll need to generate the certificates that Gateway needs, so the um so to do that. First, you go into this um this this folder, so every folder has a deploy. Examples: I'm, sorry, a Docker compose yaml file that you'll use to um Define the docker compose configuration. So so what that means is, uh if you look under this this compose directory, you see that there's a compose Docker compose yaml file here so uh because um so yeah.

A

So the first thing we'll do we'll have to edit this file, but but don't worry yet it'll be very simple. The first thing we'll do is we'll just run this Docker compose up command over here, and this will create the initial uh container, so it creates actually two containers, one for hummingbot clients, which is hummingbot, Gateway, compose bot, one and then another for the Gateway part, which is hunbot compose yeah. This is Gateway One uh bot here, okay, so now um now we want to uh now we want to basically attach to the hummingbot version.

A

So that's that's this one here so I'll attach to it and then um and you'll probably have to recreate your password. This is starting an instance I created previously, so I'll just enter my old password here um and after this step, um you will now generate the Gateway certs. So that is this step here. uh So, let's see uh so after you generate the search. uh This is when you're prompted to enter passphrase.

A

This can be the same as your coming up password or it can be something different, uh so I will uh use Gators for mine um and uh and and but I also remember this, because I'll need this later on. So mine was Gators. I wrote that down g-a-t-o-r-s.

A

um And uh and so now I can I can exit or I can stop or actually this should be exit exit. The clients.

A

Okay, so so now, um I'm back here and um and now I've generated the clients, but I need to I need to uh take the network down because we're going to recreate the network uh after afterwards. uh So I'll take the network down and now um I'm gonna edit, that Docker compose yaml file and include the passphrase that I just used to generate uh the certs.

A

So uh remember that we have this Docker compose file here, so I'll go and edit using um you know. uh Well, actually you know what I I uh since I I'll use VSC, since uh you guys probably have VSC and not them so VSC, yeah BSC, so uh so yeah. So the the see.

A

So it's this this Doc and compose file here and and what we want to do is we want to uh change these two lines here so I'm going to uncomment them and I'll change this passphrase to um the passphrase I just used to create the Gateway, the the certs, the certificates for Gateway, so edit it now I can save the file and uh and now um now, uh okay, uh now after I save the file, I can recreate the container uh by launching dark composed up again.

A

And so now um now Dr compose has recreated the network using the new configuration file. I just put there, and if I did everything correctly uh and hopefully uh I can I can pray to the demo gods that this works I should be able to see Gateway attached and online when I log into uh this instance.

A

Yep and there you go so so now it says Gateway is online and the reason is because uh now uh I added the the trading pair properly and now I can run um uh some of the sample scripts. uh So I can say, start script.

A

uh Let's see.

A

Yeah, we don't have a interesting. We don't have autocomplete on here interesting. um Oh, that's, right, I! Think it's because there are no sample scripts. That's right! Okay!

A

um Yes, um if we, if we had some sample scripts in our scripts directory, uh then we can run some but right now, because I saw using Docker I actually don't have any sample scripts, uh but uh uh yeah I could actually easily pull some. You know into from the um uh from just from the scripts folder in the hummingbot directory.

A

Yeah, so if I did want to run some scripts, all I have to do is uh is just exit. This is it this this client um and then and then, um and then basically add you know ads, add scripts to the scripts folder here in the I'm, not files, one uh and yeah.

A

If I add some files, scripts here and I go back and I I attached the the client again, um you know, and it should actually uh run it run again, so so um I I hope that was a just a very simple example of just like the new Gateway installation experience um I think that, overall, um if you follow uh right now, if you follow the instructions in the deploy examples repository the development Branch, um this should be you know very up to date and we're in the process of moving this information into the the actual uh docs right now um and uh and I.

A

Think I think this is just like. You know one step toward getting Gateway. You know fully functional and usable by people, um but that the longer process- that's probably a longer process, they'll take uh the remainder this year, but hopefully by making the installation part better. We can solve one of the biggest bottlenecks that people have and and get at least people. um You know able to use Gateway going forward.

A

um Okay, so um yeah, so so I think um I'll stop there. I think this is a good time to end the call for today, uh but uh if um I'll I'll keep the keep up for another few minutes um and uh just uh just to see what people are talking about in the chat, I'll actually pull the chat over here.

A

uh So we can see the the community call the chat here and uh if you have any questions, please um you know add them here uh and I can basically do an AMA for the last uh few minutes. So Emmett! Yes, here we go. um uh Let's see. So uh let me let's look at these questions here. A couple of comments, um so yeah uh I I think uh it's good to see actually 17 people in the audience, uh because you know when we're doing these calls.

A

um Last year we had like 30 plus people I think on Discord, uh when we moved over to YouTube um it was falling down to like 10 people. You know per per stream and plus, like we just weren't, getting much comments because, like you know, because that's it's YouTube, not Discord, so I'm really I'm happy to see that uh there's more commentary. uh It feels like a warmer environment on Discord, honestly and I think this is a just better home for Community College, going forward.

A

um uh Let's see uh just looking for some of the questions: um uh yeah yeah, we are adding also the injective uh connector as well. uh It's another order book, Decks that we're excited about um and uh and there's there's both a Spock connector and a Perpetual connector. It's actually kind of a hybrid because it uses kind of like a uh the uh the python SDK on the client side, but it also has Gateway because um it's it uses the nonsense, manager aspect of Gateway. uh So it's it's a it's, but it's I think.

A

Overall, it's a good high quality uh exchange and and connector on Cosmos. So I think it should be a good one to add uh to the list.

A

um All right: well thanks. Everyone for joining this call, um I, think I'm, recording it so we'll probably publish this on YouTube in the next few uh days as well uh and, uh as always uh I um hope to see you next time we're actually going to do another. What we're actually doing we're doing a how-to call. uh You know in two weeks the fade will be running here and then I'll see you back here for the monthly call again at the beginning of April thanks. Everyone bye, bye.