Hummingbot Weekly Developer, 14 Sep 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Hummingbot Weekly Developer Call 008 | 14 September 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: September 14, 2022 : 10:00 AM EST / 2:00 PM UTC / 10:00 PM HKT
- Duration: 60 minutes
- Location: Hummingbot Discord https://discord.gg/hummingbot, in the community-call-chat at https://discord.com/channels/530578568154054663/996769563054186536

Agenda:
- Bounties Board Review
- On-Going PRs
- Tick Size Improvement
- Community QA

#hummingbot #developer #algotrading #cryptotrading #liquiditymining #marketmaker #trading #bottrade

A

Okay, excellent, so well, we are eight. Probably we can wait, one more minute until the other folks showing and then we can sort.

A

Well, I think that we can start so well. The first topic of the agenda for today I think the carlito posted the ascendant there is the bounties board review, so we are very happy. The this process is running very good. I will paste the link for the ones I already know don't know, which is a bounties board, as you can see, we started.

A

I think that three weeks ago, this process and a lot of developers are starting to contribute with hummingbird starting to solve being issues, um and we are. We are very happy about that, because we can improve the gold base so mainly the biggest the we have. Only three bags opened right now, that is, the search of the gateway b2, their cross exchange market, making radioactive conversion and the rate limits on coin. Those are the ones are open, and if anyone wants to start working on those, it will be very good.

A

So well, those are the the open open box. We have a three bucks assigned already and we have eight submissions and we are working with qa to to to review them review.

A

The prs uh emerge immerse the emerge them so now I don't know if anyone has a question about the about this board, um how is it working how the process is just to make a quick recap: the the processes you have to check the issues that are open and if you want to get a sign in one issue that is open you should you just comment on the issue and you will say hey.

A

I would like to work on this and then we are going to assign you to the issue and you have to start working and create your pr. So anyone has a question about the about the bounties board or about the process of the bounties.

A

Okay, perfect so well. The next topic for today is the ongoing prs, so I'll paste also the link to the ongoing pr's that we have right now, as you can see, we are reviewing. There are seven pr's out under review, mainly I will describe quickly, which are the problems. The first one is the information that we are retrieving from the minor platform about the snapshots about the campaigns. Well, all those things. The second one is uh the gate. Io is a has.

A

An issue has a bug that is not providing uh updates using the websocket channel. When you have changes on your orders, it's only providing the messages when you have a field. So that's why the available balance was wrong and you can not get the updated balance.

A

So we made a refactor and now is using just the rest endpoint to get the balance on the events to compute the available balance. There is another bug uh there that the total balance. Now it has a problem, but the important one for the bot is the available balance. But probably we are going to create a prp to improve this dynamic too.

A

So the then we have the cross change market, making the auto complete for the taker market in the configuration the other one is uh we have when you want to how to start a strategy that has the the new configuration of pythag. It was fading, for example, if you want to start pure market making was working, but if you want to start available it wasn't working so that pr try intends to solve that. Then we have the binance perpetual cancer order. That issue was related to that.

A

The bot gets stuck when it's trying to cancel an order. We are in testing right now, probably two days just to make sure that we have more issues, then the other. The next one is to iterate to a blank password, because if you use a blank password with a client, then the gateway won't work. So that was the issue that was erased and the spi is trying to solve that, and then they hit vtc or the book failure. It wasn't working the other book of hit btc so well.

A

Those are the pr's that we are working on and they are on the review. Now. Anyone has a question about this.

A

Okay, well, the next topic that we're going to discuss is the tick size improvement. In this case, uh this this pi is already merged in the in the code base in the development branch. So, if you clone the latest development branch, you will find that you can configure the tick size so how you can use it.

A

You can change the value on the conf client jumbo and also you can run the command config size and it will change the tick size. Where is this tick size used where or which is which? What is the tick size? The strategy gets executes, the anti all all the objects. There are time. Iterators.

A

The strategy is a subclass of time iterator. So all these objects has a method called c underscore tick and that method is called every tick size so, for example, the normality size. What was one second, that means that the tick method will be executed every one. Second, this pr lets you tweak that text size and execute a strategy, for example every 0.5 seconds.

A

So what are the tick size that you that you want to to use? So what that that pr is already merged, you can try it on on the development branch um well and that's all about the tick size. Anyone has a question about the size improvement uh like.

B

Yeah yeah yeah, when it comes to just maybe just discuss this uh uh this um this improvement bit uh because it's in the code base now- uh and I think uh uh there was some discussion about this in the community- called chat channel. So I just want to maybe just flag those issues and maybe ask if you have seen those issues that maybe a memento murray brought up.

B

So I think he asked about kind of like what values are are possible for fixed size and if there are any values that are not possible or like or wouldn't work, um you know like, for instance, like how low can you go like like what are the bounds for how users can change it?.

A

Okay, yeah, uh for that I just limit the mint tick size to 0.1. If you miss one thick size, it will recover the logic on the next size, but by default I put like the minimum on 0.1. Probably we you can use it. I think that normal will be like 7.2 0.3, but I put 0.1 base that based on the binance, since the websocket messages are uh with a delay of 100 milliseconds so lower than that doesn't make sense.

A

So that's why I put 0.1 as a minimum tick size, but we can put like 01.3 if you want, but well that I know.

B

Yeah yeah, I think, just just kind of getting that um yeah kind of like documented in some way, I think, would be good, so I would say one thing: I think we should try to start doing is like when we make changes like this and it's in development. uh We should have a plan for actually also making sure that you know we're updating the dots in time to add the parameter. You know that about the the tick parameter, defining what users can send, what they can set uh for that parameter.

A

Yeah in the in the pr I explained that minimum, but well, if you want to know exactly it will depend on the exchange. Probably there are some exchanges that sends updates with a delay of 300 milliseconds.

A

A lower tick size will have the same information of the elastic side, so it's it will be the same. So I think that it's an experimental.

A

Thing that at minimum we we put that the minimum 0.1, but each user will have to research about his exchange, about which are the the logic sites that he can. He can use, for example, but well we can make some investigations.

A

I know that memento likes to to make the make the the test of the speed of all the providing of the code. So we can. We can do something like that, so well, yeah, every every everything has the same thick size, memento you. You are asking that, because how hummingbird works?

A

You have a clock and that block has a list of children. There are time iterators, so every tick the clock notifies his children's by calling the c underscore check.

A

So all the all the the components are using the the same tick size, but the main things that you were the the connectors and the the connectors, for example, are time iterators, but they won't do anything, because the only thing that is running on the tick size is a event to let to let the.

A

The status pulling loop run so well. That's that's why it's not so so complicated. All the things has to be based on the timestamp, so you don't have to be based on the tick. uh Well, anyone has another question about we about the text size improvement.

A

If anyone found a finds a bag, we can fix it by default. If you use, one will be the same as using him before I try with different text sizes and it was working good, but well, if you want, you can use it exciting as you want, I would recommend you if you want to do some things that needs more computation or well you you want to do something more accurate.

A

Instead of reducing the tick size, I think that is better to code, a synchronous task that will be checking your condition and if you have one condition, for example, in balance in your day book, you can trigger an event based on that. That would be for me a better approach than reducing the tick size or everything, but well, it depends on what you want to do.

A

Well, the next topic that is not in the agenda for for today, but we want to include it because we think that is very important is that we are in the in the foundation. We are going to promote the the refactoring of the connectors, the certified connectors that we have to the latest standards.

A

This means that they have to be a subclass of exchange by base and we are going to start a we always with the certified connectors and then once we have all the certified connectors in the latest standards. We plan to move this task, or also include in this task, add the perpetual connectors that are for certified exchanges too.

A

For example, add the kucoin a perpetuals connector, so once uh we we are going to, we are working on a list or which are the connectors that we want to start with, and once we have, though, that is ready. Probably today or tomorrow we are going to publish uh this course thread mentioned in this uh this initiative.

A

Who will be the the person that wants to work on this and then we're going to create the hip to to pay bounties for the people that is refactoring the connectors?

A

So well, I don't know if anyone has a question about this. The main thing is that when you are, when you are.

A

Coding when you are coding a strategy or you want to use a connector, you want to trust in the code of the connector, and there are some connectors that are. The code is like very old.

A

We don't know if they are fully updated to the data standard, so the best way of making make sure that we are using the a good quality connector is to make it some class of exchange by base. That has a lot of tests and a lot of things already automated and then, if we have any valve it will be much more easy to detect it. So that's why we are promoting this initiative uh and it will be better for all the harmful users.

B

This is this is related to our exchange certification program that we started uh a couple months ago. uh You know right now. Hummingbird has, I believe, more than 40 hectares to both centralize, the decentralized exchanges in our code base. So I think you know for us, and especially on the centralized side, there has been kind of an evolving standard there, so currently, what we're calling kind of the gold standard we're going to rename as b2.

B

So the first step is to label like what exchanges in the codebase are are actually meeting the new v2 standard and which ones are not, and then, after that, we will create bounties for the certified exchanges uh where the connectors are not. You know yet on that standard, uh and that will allow people in the community to earn h5 tokens for upgrading them uh to to the new standard um so um and that- and this is kind of like- and that combined with the the bug bounties we've created for these certified exchanges.

B

We believe this will help essentially allow the community to ensure that these certified exchange connectors at least are high quality uh and that will hopefully, you know, really allow people to really gain more use in their flowing plan, because now, when they run a bot, as I mentioned, they can trust that the connector is working properly. um That also means that, in the future, when we have- let's say a new standard, you know the the platinum standard so to speak.

B

uh We should really be calling that v3 uh and then then subsequently creating downloads to help um you know to allow the community to upgrade any. You know non-v3 connectors to that new v3 standard. So, as you can see overall we're trying to standardize uh how hummingbit works um and essentially create a process that allows the community to uh basically maintain the code base in a decentralized way.

A

Yeah yeah sure, and also we also want to promote that on the perpetual connectors, because we know that there are a lot of people that is that that wants to trade, also in perpetuals uh right now we only have binance dydx and by bit so probably adding a coin.

A

Well, all the certified changes, ftx ftx is very important. We want to add it soon too. It will be very, very good for the for the community, so mainly uh just to mention which are the the benefits of of using the of being or maybe making the connectors a subclass of exchange by base. They have also uh on like a stand like a generic class of tests that are running in the exchange class. So now the work of building a connector, a spot connector is much more easy than before.

A

Because of this, these tests dictionary text class and also you have a lot of implementations already in exchange by base. So I think that the best way, the best thing that we can do with the 35 connectors, is to make migrate demo to to this class to the to visa as a class of exchange by base. So.

A

B

Used so so, just you know, there should be, I think, around probably about um at least like five five to six bounties that we'll be creating. Initially, uh you know it's a combination of refactoring. You know connectors a new standard, uh possibly building you know uh professional, connectors or refactor professional bankers new standard as well. um So I think what one sense we wanted to. We, we didn't want to come out and maybe um kind of like get a sense for uh how much you know hbot.

B

uh You know uh we should give to developers who are doing this work so um so the way that we were thinking about it is that uh spot connectors. You know, probably in our belief, take about uh probably two or three weeks of time to build well, uh whereas petrol connectors because they are more complex um but because there's also more testing involved um may actually take like four to six weeks to uh to build.

B

Well, so, uh in terms of the h spot, you know kind of, like uh you know, amounts uh we were thinking proposing something around um like five hundred thousand uh h-bot for spot, connector, uh refactor or rebuild and um and 750 000 h spots for a a perpetual connector. You know rebuild uh or refactor, so um maybe um yeah, maybe maybe we can do a quick poll in the community called chat and see if you know how people feel about uh these, these embers.

B

um Let me let me uh create a poll there and then maybe we can just do a vote and see um if people feel like those these. These numbers are kind of, like you know too high, too low or or just right, so um yeah. Let me keep going and I'll create a poll in the chat.

B

A

So well, the last topic of today is a an open discussion about which are the bugs that you think that we have in the code base that are not included in the bounties board. uh We mentioned in the first part of the of the meeting. We have uh bounties board that you can. The link is in the in the community called chat, and now we have all like 4 8 11, like 15 bucks, are in treatment.

A

If you have one bug in the source code, you know you are experienced above you, you already create the issue, and this is a time that you can post that in the community called chat. um Oh well, obviously,.

A

Obviously, we are trying to include include them in the bounties board. This is mainly because we are prioritizing the bugs as we as we think uh that are the most important bugs, but if you are, if you are, if you, if you think that we are missing somebody, please now create a post out by in the in the chat.

A

Well, I think that there is no bugs or you or you are comfortable with the bugs that we have in the boxes for right now.

A

My bot is an experienced bug at the moment.

B

B

I created, I created the poll, uh so I think if it is up, I think it means it's too high. I guess his down. Arrow is too low, I guess, and uh the plus arrow is, is uh it's just right.

B

B

B

The thumbs down- okay, yeah yeah, the thumbs down, is like basically people want that change in some way so yeah. So the the the up arrow is means that you think the numbers too high, the down arrow is too low uh and then yeah the plus. So it.

A

Seems like nothing.

B

I would say I think, just uh you know, I would say it seems like if.

B

It seems like most people feel like that the master proposed are decent, so let's just go with these and then you know we'll see how how people's uh experiences and we can adjust them. um You know, based on how much time these devs are actually taking so so yeah. Let's um yeah, I think, let's go with 500 and 750 and we'll we'll get those bounties created in the next week or so.

A

Okay, well now I barely say in the in the group the the thing that probably a connector shouldn't take no more than three days, but that would depend obviously on the on the api docks. These sd5 connectors obviously has a better api docs than another random connectors.

A

But it's true that now with the generic test and the exchange paybase, the work is much more simpler than than before. So I don't know if three days, uh probably abel, can do it in two days or three days, but I don't know, may probably a developer that has a sideshow or is not fully dedicated to. This can take like one week one week and a half early.

A

But or is not so familiar with the with the with the connectors but well, I think that the discussion is is good, yeah well um and the one that the generic class of tests was a bell. So thank you all for for that huge contribution.

B

Yeah yeah, yeah, yeah, yeah and, and just just everyone knows like. I think that the uh you know like the foundation philosophy for hp tokens. So so uh you know for the dev bounties we do want to make sure we can. You know reward developers for the time they invest into uh helping maintain the code base. um You know with hvac tokens, uh you know right now, uh yeah other than governance is really the only thing there's not really much out there.

B

uh They don't really listen anywhere, uh but so that's why it's kind of the only reward that we can give right now, um but so with the amounts, we're just really trying to make sure that you know some people. um You know for the folks that really believe in long-term agenda for hbot. um You know they they're getting some type of governance value for um for making changes uh in the future. uh If the exchange share that we're getting from these certified exchanges, you know like it's sufficient.

B

uh We do, you know, uh intend on paying bounties in stablecoin or other tokens down the road as well. uh But, of course you know that's why this effort is designed to improve the um the connectors only for those sort of exchanges, so that in the future the foundation as a whole is earning more money from the fee share and which allows us to share more uh with the devs in our community. uh But for now um you know, because of the uh you know, exchange volumes are down. um You know right now.

B

It's uh it's really just uh beachbot is only kind of like token we can get out, uh but you know we do feel like h5.

B

So um so with that, I think the next step for us is to um basically, uh you know: label which exchanges in the code base or v2 versus v1 um create bounties to refactor the certified exchanges where they need to be upgraded to v2 um and then and then basically add them to the bounties board and get them assigned to devs that want to take on the work.

B

um So yeah, so if any questions about about the process, please uh please post them now uh or or once you actually kind of see the bounties uh feel free to you know like bring our team. If you need help uh in terms of documentation, we actually do have quite a lot of docs now uh in terms of building connectors, uh there's a there's, a template, there's no template! That shows you how to do it um there's a lot of stuff in the docs we've added in the last uh few few months.

B

So hopefully uh you know you know and there's also many examples as well that people can copy and code base. So hopefully uh it's a good chance for people to contribute to code base, while also learning how the exchange character, architecture and that works.

A

Okay, that's perfect.

B

Oh um yeah, I say question for momentum: mary uh yeah, you submitted a pr for the sites. um Yeah. Thank you for that. uh I think um yeah we'll make sure.

B

um Oh yeah, I think actually um it looks like the the pr well memento. um The pair you did was for the uh the separate buy, sell, hang orders um yeah, we haven't coming out yeah uh so with that pr uh was.

B

That um was that um wasn't that, due to what was that feature actually merged in uh because I thought that pr wasn't approved yet or hadn't actually been submitted, um but basically the the rule for the the uh the docs is that, basically, when, when the um when the fix is burst into the moment, then the docks are also adjusted and in the future. Actually we should. We should probably also create bounties for uh improving the docks as well.

B

So, for example, we are going to add a page to the docs, reflecting the new tick size parameter that faded added. uh Perhaps you know it's probably going to be very basic to begin with, and so I think in the future we probably will start adding more documentation boundaries as well for people to help um uh yeah. If I'm cutting out yeah. Just um please let me know, and uh I can try to move to a more uh better internet location.

B

Got it oh yeah, so so momento, oh yeah, so um I think uh uh the the the um yes it was submitted. um I think this. This is a bit of a process that we haven't like fully ironed out yet, but but I think that um yeah, if you, if you're it's very for review, um let us know- and I think was this- was this already approved prp, because I think that our team is looking for the prp to kind of to understand when to start reviewing.

B

That's why it's possible you're, paying orders pr might have gotten lost in the shuffle. So I think um because this is related to community bounty. I think we probably need to establish some rules around this, but but overall I would say we should. We should start reviewing this um in this period. So if you haven't made, if you haven't made a prp yet I was just just making a therapy now and then uh but yeah.

B

It was ready to review and we should be reviewing it and try to hopefully yeah basically some feedback and try to get it into the next release.

B

um But but yeah so the the, but I think your question was updated. The the doc site is basically, I think that um I would say just so. Many pr's is the right way to uh update the doc site, uh and um so I think that, right now we don't quite have a process for connecting the doc site to the code base, but um I think generally, it should be like any time the code base is is uh is changed and some pr is merging developments where it's going to change some documentation. Changes are needed.

B

That's when uh you know either the developer or something from community should make a change into the docs um in the future. We should probably ask the developer themselves to actually make the docs change alongside their code change, so that it's like one single step, uh but uh at least for now right now, it's it's kind of like a doc that is just kind of updated. Alongside of the codebase.

A

B

Yeah, the the for the dot strings um yeah, I think you're, referring to the the dot strings, are in the code base uh yeah, so the the dot strings actually should be updated. I think, if you're actually changing the the function or the component of the class that that that's in the code base, so I would say I think this is actually where I'm not sure how much, how many of the components and actually have are used in dot strings, but I think a lot of new ones are so um yeah.

B

I was, I think, it's kind of like um your question is: do your recommendation or repository of code uh documentation um yeah, I'm not sure exactly what you mean by that.

B

Repo is the official documentation site, uh but that's intended to be more of like the uh the user documentation and like the guys and those kind of things um I think the encode, the inline like doc strength is, I think, the the the the more I kind of like the standard that I think we're trying to evolve to now, for, I guess, like documentation that lives inside the code.

B

Okay, yeah yeah yeah, exactly yeah, the uh I think actually- and this is actually one thing I discussed in the future- is like you know how to kind of like complete how to take the documentation that exists um in in in the um you know, in the dot strings, and I actually kind of can auto generate a docs like from them or something like that. So they'll.

B

Actually I I talked about this a few months ago, but basically because a lot of the newer components have um like you know, inline documentation for every function, um there should be a way to kind of generate kind of swagger-like docs uh for for, like basically those those functions, and I will then watch something like I said, like runs my internal documentation server alongside human body, so people can, you know, develop that access.

A

Okay, I will ask that.

A

Well, I think that we cover all the topics for for today. I don't know if anyone has another question that wants to or another or a bag that founds in the code base that that is now in the bounty sport.

B

Okay, uh well yeah, thanks for watching about this new bounties based process that we started recently, um I think now we have something like we tried, something like probably at least uh more than 10 issues that we've already solved using this new process with like at least like five or six devs, the community to fix bugs already um and- and we feel like this seems like a really you know- kind of like a good process to invest into, uh because uh you know we're improving the quality of connectors, uh growing, the developer community and really kind of like trying to use this.

B

um You know set of incentives in the governance system that we've created to reward people who are uh helping to maintain a code base, so I think we'll try to get the um the connector boundaries created in the next uh week or so um and uh and in the future.

B

I think we'll probably also start studying this to you know um you know other bugs that people find and feature maybe other subject, documentation or or content, or you know other ways that we can involve community in helping to um you know, improve the code base and grow this.

A

B

A

Memento says ftx recent bugs are no on the bounty. They seem to do a websocket disconnect that is not registered.

B

um Which actually is basically a lot of communities like? Can I help us identify which bugs they think are important and should be on the board, so yeah memento? If you have, if you yeah, you have a ticket for that bug, uh just posted in the call channel in the chat channel, and then um I think this is a good time for uh our team to to kind of get feedback, the community in terms of which bugs should be on the board and get them posted so that people.

B

Okay, cool yeah, yeah thanks, yeah yeah. I think that one yeah we actually just talked about this bug uh during our internal drive call today and yeah. I do think we'll probably add this one on the uh the downdies board pretty soon momento.

A

Okay, yeah: I will talk about this today,.

B

B

A

Yeah yeah, we should focus on the bounty sport right now um and once we have a better better standard of the connectors and a lot of issues that we have on the occurring strategy solved. Let's focus on improvements, but this time I think that the best way is to focus only on solving bugs oh well, well, community.

A

I don't have any more topics for today. If anyone has another issue, just posted here, um let's see, let's see us on the next week in this community called.

A

Okay, well, bye-bye have a nice week.

A