Hummingbot Weekly Developer, 26 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Hummingbot Weekly Developer Call 013 | 26 October 2022

Description

The Hummingbot Weekly Developer Call is a technical and general discussion intended to gather active community developers who contribute to making the Hummingbot codebase better through Hummingbot Improvement Proposals (HIPs) and Bug Fixes.

Meeting Info:
- Schedule: October 26, 2022 : 10:00 AM EST / 2:00 PM UTC / 10:00 PM HKT
- Duration: 60 minutes
- Location: Hummingbot Discord (https://discord.gg/hummingbot)

Agenda:
-Gateway v2
-Review Bugs Pending
-Community Q&A

A

Hello, everyone thank you for coming to the.

A

Start so hello again, everyone thank you for uh coming to the weekly developer call uh today today we're going to be talking about the uh like the agenda. As usual, we have the we have Gateway V2 uh dates: okay, um Pinto, the audio issues. Just give me a secondary I switch.

A

A

Okay, uh I think that on your side, Mike and okay, nope no problem so I've been talking about the agenda right now, we'll be talking about the Gateway V2 updates. uh We have the serum team who have been working hard on uh on, like updates to the serum, connector and, and this example for a script. Then they have a ripple decks proposal which is a currently in in voting process. We will also be reviewing uh bugs the Box pending and in the end we will have the QA so uh for the Gateway V2 updates.

A

A

um We have some updates coming to Gateway V2 user experience over the last two or three weeks, I've been working together with entirely with Mike. Here we have been trying to like Envision how to improve the Gateway developer experience both when installing from source and doing installing from docker. So we we came up with the with a few updates. The the first one is was with the certificates. We had issues with the certificates before the users didn't know how to handle the certificates.

A

There was a lot of steps in order for a developer to installing from Source. In order for them to uh to have the Gateway working properly and for them to connect it to the client, they had to run generate conf on the Gateway end then go on the client and then run generate search then take the path from the the generated search on the client copy it in in the SSL file in the um in the Gateway conf. So it it's.

A

Basically, it wasn't an ideal uh process, so we sat down together with with Mike and with the with other suggestions from other developers and from uh from other team members, and we came up with a an improved process that is coming in the next, hopefully in the next release.

A

So the change the first change was the to the certificate. So now, once you uh want to install Gateway from Source, you are going to run, generate con from the Gateway end and then run generate search on the client and and everything will be updated automatically.

A

The second, um the that is the first part which will allow you to connect directly to the um to the Gateway without having having to do like nine steps for the gateway to connect. That is the first update. The second update is to make the path for the certificates configurable on the client end.

A

This will allow users, many users have been asking about whether you can like connect multiple clients to one Gateway. This update will allow you to do just that. So, once you run generate search, you take that path, and you put it in as many clients as you want, and those clients will be connected to to a single Gateway. That is um like uh the first, the first purpose of the uh making the the certificates path. Configurable, the the third update is the um is it changes to the location of the configuration and the logs.

A

uh Currently the logs and the configuration for the docker installation of Gateway are uh are saved in the folder in a hidden folder called dot, hummingbot Gateway um right now we will be changing that to um to be the like in the same location as the client configuration from the docker installed, so everything will be under one folder and accessible, and the user can check for the logs and and the configuration of the Gateway in the same place.

A

If there's any questions uh feel free to stop me and post them in the Community chat um or leave them until the end with the QA, so the that is another update.

A

The the last update that that has been like a lot of annoying warnings when, when running the status command, especially when you're running um when you're running a Gateway, AMR or any other Gateway related strategies, there's been a lot of warnings and we decided to remove those warnings, as they already exist in the logger side of the client, and they also exist in the logs files, so we're removing the warnings from the status command.

A

uh The last update is we are reformatting the the error messages from the Gateway. We have noticed that the error messages right now are are a lot clumped and they are not clear and they display a lot of um like um useless text so right now we're only keeping the status code, the message and the endpoint so uh that those were the main gateway veto um user experience, improvements coming in the next release. We are also working on a Gateway script example, which will be coming in the uh just after the user.

A

Experience updates, so this is the um the updates that we've been working on for uh user experience on the Gateway. Hopefully, this will improve the the uh the experience for the users installing from source and also for for developers and selling from Source, also for uh users who are installing the Gateway from Doc.

A

Yeah, so this is, um that is the first part of the update, my guys posted something yeah. So there is a feature uh there is a feature branch that, uh where the these user experience improvements are located right now it's called Uh feed, uh Slash, configurable search path, Mike posted it in the in the chat right now. Thank you Mike for posting it uh so we're we're, hopefully, um that that Branch will have all of the user experience updates and will hopefully be coming in the next release or or the one.

A

So that is the uh these are the updates that are coming to Gateway V2. So we uh in the agenda. After this, we have the Solana serum Dex update I'm, going to invite uh deep fit.

B

B

Can you hear me.

B

Hi, uh can you hear me or is it not good right now.

B

Okay, audio is clear: uh yeah. Thank you, fawzi for uh giving us the rundown on the ux improvements, uh something that we also benefited and uh yeah I'm gonna, give you a small update, or maybe like a bigger update uh on what uh on hot. What on on our progress of this Lana and serum decks, connectors and uh yeah, maybe uh first off, we were able to successfully launch a production Market making strategy uh on the serum decks with it.

B

So we were have been working on it for over a month already for a customer who wanted to make uh provide liquidity on several markets. For his newly launched token, and as you can see here, uh the market is live. The bot does basically what it should do all with the help of hummingbot. We're really happy that we made this happen and we plan to build out functionality for this on the in the coming months.

B

So we had a lot of learnings a lot of improvements on the Gateway side, but also on the client side, which we found basically by really using the connector to to its full extent, and we plan to now move parts of the code into the hummingbot Repository.

B

um Which Danilo or garudan is uh currently preparing he's also here in the call and we uh yeah and so so that, basically, what we did right now uh in the scripts um will be available in a new and improved version of the server Market making script.

B

And later this year, we plan to also release the uh the upgrade to full script functionality and uh sorry full strategy functionality, which will mean that you will be able to use any strategy which requires a central limit order, book exchange or centralized exchange to be usable with the serum decks. So we would be very excited to work on that.

B

um There will also be a bigger upgrade like that that it might be that there will be a bigger upgrade to the Gateway necessary to make this happen, though, because uh what we have been talking um about was that we might actually integrate websockets um into Gateway so that it makes so that it is possible to get live trade data as a feed into the client similar like uh similar to other centralized exchanges, and this would basically be the gold standard of integrating new Central limit order. Book exchanges, which are decentralized with Gateway um I.

B

Guess this will require some more discussion um and also planning uh with also with you fuzzy, um as as you're taking care of the Gateway improvements. I think other projects and chains will also benefit if we have a clear plan and a clear architecture on how to integrate web sockets into Gateway and yeah. And if that's, if.

A

It's done, we can have a key for the key architecture exchange, integrate websockets.

B

Yeah experience that you're so accustomed to with hummingbot, but on a decentralized exchange, of course, uh yeah I think maybe uh Mike wanted to uh break it to you guys, but we will be have we'll we'll be having a uh kind of secret or non-secret uh Meetup in Lisbon coming week um there is going to be the Solana breakpoint conference um and also the hacker house and uh I. Think Mike is writing.

B

um We will be meeting there somewhere, yeah, okay, cool um and I. Think I think Mike can provide more information about that now or later, but we will be also then presenting our Bots and that we will be also there for a q a and if you need support integrating others. Solana exchanges we'd be also happy to to meet you there. If you guys, will be in Lisbon and uh yeah and see how we could help you out with that um yeah. uh Otherwise, uh questions.

A

Mike I think I didn't want to shave until the like the event until the date and Vineyard confirmed, but the if you are in Lisbon next week, then you're mostly welcome we'll be sharing all of the details in the uh in the announcement. Channel and you're mostly welcome to come to the inside event of uh Solana break from right awesome. uh Thank you for also sharing the updates on the serum I.

A

I want to also extend the person thanks for the effect and garudan was also in the call who have been doing uh great work with the with the script and with the serum connector, and they also have another upcoming project which I think we're going to be talking about is going to be talking about right now. If you have any other question um any other questions for him, you can leave them here or discuss them in the developer. Chat, um David you're going to be talking next about the Ripple decks proposal.

B

Sure all right, thank you, Father um yeah, so this was something uh quite spontaneous, I would say, but um I we got messaged by a guy who asked us asked us if we were able to build a Gateway connector for him uh for the Ripple decentralized exchange. Up until this point, I didn't even know that there was a decentralized exchange on Ripple already so I was looking up. Looking it up, I found it to be, like I, found a documentation to be technically appealing, um pretty easy to understand how it should work.

B

So so I figured uh well.

B

Why not and I told him yeah we're gonna do this and um yeah and we're gonna try to provide a um like a very minimum, valuable implementation uh somewhere in November, mid, mid November, mid to late November, and we are going to work on this together with community members, vojak and Mooney Mike, who basically followed my call for Gateway developers or typescript developers, which I was looking at the time, because we're still so um so busy with the Solana connector and those two will be working on this also I'll be advising them on how to continue and and how and what you know like basically, operations, wise and uh yeah, and we hope that this will be a big, an important addition to the hummingbots code base.

B

um I haven't traded on Ripple. Yet, to be honest, um I also do not own a ripple wallet yet, um but I would be very excited to see what comes out of a potential collaboration with ripple Labs As I understood the request comes from someone who is about to join Ripple labs and uh as a quantitative Trader will be also in charge of Market. Making four Ripple Labs on the decentralized exchange and also as I heard of by Mike, was that Ripple Labs actually and hummingbot Foundation have some past.

B

um You know past history, so so they definitely have a interest in the hummingbird code base and um I think if we are able to provide them with what they need, it could turn out to be very beneficial for hummingbot, as laid out in the proposal, not only in terms of more exposure to and more features, but also in more exposure to institutional investors.

B

um You know big shops, which want to trade large volumes through hummingbot and yeah, and potentially we could secure further funding if we could help them to onboard to Hummingbird. So that's why I think this proposal is a good idea and I hope that you see that the same too, and if you do then please follow the hip on Snapshot and vote for it and yeah. So if there's questions we can also reach me anytime and also on the Forum thread that I created and yeah. We can discuss it there.

B

A

Thank you. Thank you. David I posted the link to the Snapchat uh HIV proposal that DPA was referring to uh feel free to vote for the and, yes thank you. Carlito Carlito posted the Forum thread you can discuss on the on this course. There you can discuss the um uh the Ripple decks, Gateway connector suggested by defeat, and you can also vote for the proposal in the um I posted on Snapshot um yeah. So uh thank you David for the updates. Thank you for uh your contributions.

A

Also, uh definitely is one of the most valuable uh I think uh personal opinion, I think is one of the most valuable uh contributors in the community and I've been doing great work with the serum and now upcoming work with. uh So thank you well,.

B

Thank you for Aussie and thank you also hummingbot for contributing a very valuable couple place to work on.

A

But all right, uh so the the next point of the agenda is we're going to review the bug. Spending I think the uh bonus Board of the same box from the last week is I'm, inviting everyone in the community to um like to take a look at the uh bonuses board and like look for uh volunteers that they can pick up.

A

uh Many members of the many members have been contributing uh the have been resolving bugs now over the last few weeks since the start of the program and I would invite you as well to uh uh to pick up uh like a connector. For example, there is a bounty for the snx syntax uh spot to upgraded to V2.

A

uh You can pick up any of those bounties by requesting them on the volunteers board on on the code base, I think, uh since we have the same boundaries from last week, I think we can move to the Community Q a.

A

uh If you have any questions you can post them in the in the channel here in the community chat in the community called chat.

A

I remember saying someone seems to have requested this index already I've seen it in the open. uh um If you go to the one this board, it's in the open uh issues so just check if it has been requested, I'm sure it's not, it has not been assigned yet.

A

Oh yes, I only seen it is now. Someone seems to have requested the uh uh the bond so we'll uh we'll check with the ferry as well on on this and see if it can be assigned as soon as possible.

A

Any other questions I will be happy to answer them right now regarding uh what regarding the Gateway V2 updates or regarding the serum connector, the Ripple, the X connector or the open issues or any questions in general.

A

A

No yeah, if it can answer that in the chat I think it like a manto is asking if the Ripple connector is built, don't think it is yet yes, I just started organ on it.

A

Mike during the stage I'm like, if you have anything to add, feel free.

A

I I can't hear I can hear you my if you're saying.

A

A

So my uh Mike is saying that his audio is not working properly, but he's suggesting a potential Improvement to the to these weekly calls, uh perhaps providing like as part of the agenda, providing um a mini lesson uh about some aspect of the uh of the hummingbot code base. It can be, for example, uh the balance command.

A

It can be the status command or like how the start command is working to start the strategies or the scripts different aspects of the having bot code base code base, so each week will be suggesting that we have uh he's suggesting that we have and like. We choose an aspect together like a the community votes for an aspect of the code base that that they want to learn more about, and we can discuss it in the in this call.

A

uh Examples given here are like, for example, how the right Oracle Works to convert like assets to uh to whatever base value you want like, for example, to usdt or the telegram integration that the that is available within hummingbot to send, updates and configure the bot through telegram through telegram both or, for example. One of the strategies choose one of the strategies to talk about foreign.

A

Think it's a it's a it's a great idea that uh I think developers would appreciate learning more about um like different aspects of the code base, uh guys you can give your opinion in the in the chat here. If, if that is something that would interest, you.

A

A

Like some interest, this being shown in the chat here for these many lessons, so I think we will.

A

um We should consider them in the in the in the upcoming calls to, and we can also create a vote for like what the topic the community wants uh like uh um or which one which one of the aspects is, is the community more uh like to would like to more discuss on the uh on the next polls?.

A

Moment is asking mementus asking if we have a solution for uh integrating the Gateway tests, or is that open to be proposed right now? We will remove like the only reason that the Gateway tests have been removed is to check if it is the one causing the the workflow, the GitHub workflow, to fail. I think they will come back but feel free. If you want to propose a solution, feel free to create a PR or I'd recommend that you discuss it with the um with Federico with fediology.

A

We discuss it with him first before proposing it, so that you don't have to um like do a lot of work. If there is already a solution cup.

A

So, as my as the fact that you might say uh seems like there is, some support for the meaningless in ideas will be creating a forum thread so that people can suggest the topics there and uh we can add them to future calls. That's actually great I think I'm, looking forward to seeing these uh uh many lessons and probably leading a few of them as well.

A

All right any other questions regarding any of the topics we discussed today. Already other topics related to the having what code base or the Gateway or any other aspect.

A

I went to the right typing.

A

A

Version so I think we we should consider this, but this all should be tested over time with the like compatibility issues and with all of the packages that we're using. So that is not something that is not something that we can do hastily. We have to consider all of these different ramifications and probably the changes that need to come with the updating, the node version of the good.

A

Now that is also the reason that we haven't like we haven't, get the version up to date, with every release of note, because there is uh dependencies of uh some of the packages used by the some of the models used by the Gateway, and that is probably will um will need the like uh rigorous testing. Before uh pushing the update to the to the um like to the code base.

A

Yes, we try to keep uh the environment up to date, but it's it's not going to be like uh with the latest uh release all of the time because, as I said, there is changes that need to uh um like that need to be taken into account before updating the version in the in the release.

A

Yes, exactly, as you said, you wanted to change to say from 3.0.

A

uh Updating to newer versions. Probably can cause braking like can have breaking changes and can cause issues with the um with the current code base, if not done carefully. That is why we always try to um like make sure that uh we take a careful like measures before we. We push an update.

A

I I wouldn't say this is there is no higher level devs here. If, uh if you have done the work for the updates, you can push it in APR and it will be reviewed, and this is a community-based project. So there is no higher level depth or lower level depths.

B

A

To the question of updating uh modules, saying that there is, there should be a good reason to update any core dependency, since anything that uses the that library is impacted.

A

Qi effort is needed to ensure that it doesn't break. That is thank you for the Insight I think we should hold. Please take careful measures and do rigorous testing before updating uh updating any of the dependents any of the dependents because of the. If we have, if we do main like maintain it to the latest release, we will be, uh we will have like endless work for the QA team to to be doing with every list of every dependence is hundreds and thousands of dependencies being used by hummingbot.

A

So it's not realistic to keep like to keep it up to date with all of the latest uh versions, but we try to make sure that we keep it as much up to date as possible.

A

Is there any any other questions we.

A

'd like to answer in this call.

A

If there's no further questions, then we can go ahead and end the call.

A

Okay, thanks: okay, thank you. Everyone for coming to the weekly developer call appreciate your uh your presence, and uh hopefully we will see you in the next course looking forward to it. Thank you.