Hummingbot Weekly Developer, 19 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Hummingbot Weekly Developer Call 012 | 19 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 19, 2022 : 10:00 AM EST / 2:00 PM UTC / 10:00 PM HKT
- Duration: 60 minutes
- Location: Hummingbot Discord (https://discord.gg/hummingbot)

Agenda:
-Review Exchange Revamp Status
-Sifchain DEX Connector
-Review Bugs Pending
-Community Q&A

A

uh Welcome to the uh the this week's weekly death call for coming by uh payday should be here pretty soon, uh but in the meantime I'll get us started. um So uh so we have the agenda uh as always: I'll post the agenda in the community called chat channel. uh If anyone has questions, please please uh you know kind of like that. Listen there as well, um so we have um today we're going to talk about a few items.

A

uh So uh first uh we have uh the uh we're gonna review um kind of basically some of the the stats of the ongoing exchange revamp uh that we have uh there's payday um and then and then basically, we've assigned a bunch of connectors to be built as bounties by the community. So we'll give you an update on that. Next, we'll have a web of presentation from the team from sip chain who has added, uh um who submitted a proquest to add the cosmos.

A

Basically, your integration I think they also plan to submit additional PR's later on, to integrate sip chain and have the bot as well and then finally, we're going to review the pending bugs and then uh and then also uh raise.

A

B

A

But uh yeah I, just uh I, just kicked out the agenda so I'll hand it over to you.

B

Okay, perfect: well, uh we are going to start with the status of the The Exchange, revamp that we are working on well. The good news is that we are getting into a very good point in terms of the quality of the connectors Aisha's review, the first submissions that was from a yakom that is here. It was a very good connector, a quality. Will he followed the standards of the of the guides that we have, and it was very, very easy to to read the code and that's why we are doing this now.

B

If you are going to check the different connectors, you will find a similar structure and it will be very easy for you to check if there is any issue there. So that's why the main purpose of working on this upgrade So. Currently we have that submission of the gate, IO perpetuos to the code base and we have assigned the FTX Perpetual the Google in perpetuals, the upgrades for hit BTC spot by this spot Huawei spots and the upgrade for binance Perpetual. All those connectors are assigned and they are developers working on them and we have.

B

We have remaining one that is to the upgrade of the ascendants connector to the version 2.1. uh Well, if anyone is interested in working on that one uh just comment on that issue, but well right now, I'm very happy that this initiative has a lot of a lot of support from the community.

B

um Well, that's all about the The Exchange connectors, real amps I, don't know if anyone has a a question yeah that BR Dot is the one that I am referring to. If you want to check the code check the code, you will see that it's very similar to the code of the Bible connector and that's the main idea. You know so well, I, don't know. If anyone has a question about this initiative of the exchange revamp.

B

A

Before we move on I think after this batch of kind of connectors are done, um I think we'll probably create more issues as well uh that community members can work on related uh to these connectors. For example, uh we may create issues to add various connectors as a rate Oracle sources, so that people can use them. um You know at other places and another one.

B

A

I think that another area we can prove is probably uh you know, adding different order types and making sure that all the server by connectors support you know um kind of order, types like Market orders or stop limits.

A

You can do that that give users more more options when when using that connection, so overall, what we're really trying to do is you know, really make sure the certified exchanges uh or we're focusing like development efforts and trying to make sure those vendors are at really high quality and then using the voting process in order to kind of, like you know, kind of like have those exchanges kind of you know basically themselves.

A

I'm certified so so that's kind of like the the model that we have. That's. Why I think that? um Obviously the token is not you know it's. It's not a lot of use, it's right for right now, but we do think that if we really differentiate kind of like certified exchanges from the non-certified exchange of the code base, uh then then that is um and then one one note in the future.

A

We we also might do something, that's very similar with strategies as well, uh because right now, uh there's probably about 14 strategies in the code base, uh but we we're seeing a lot of a lot of more people who want to submit their own strategies into the code base, and we want to encourage that. However, um the same problem is going to happen with the connectors and that it's you know the the the the the maintenance efforts um you know can't doesn't scale it was going to try and handle every single strategy.

A

It's most likely, we'll we'll ask the community to help us select like the top. You know five or six core strategies uh that the foundation then puts efforts into creating downsheets for maintaining, while uh the other strategy that code base are uh so so that's kind of, like the the general plan for you're, trying to make sure that you know we're leveraging Community containers um to improve the code base, while also uh kind of using the token voting process to help us decide which connectors and which strategies.

B

Yeah so yeah I agree a lot and I like I love the idea of creating some tickets to do some similar stuff, like adding rhetoricals or or, for example, at the support for different order types. Those things I think that are will be very, very good and all you see is much more better if we start with the same the same base and a standardization of how the connector should be coded so I'll well, and that's all for this The Exchange revamp initiative.

B

So now we are going to invite the sieve chain devs Arrow Calito, if they are already here.

B

Oh, they are racing.

C

Okay, hey how's it going.

D

C

Guys, how are you um so? We are actually pecunia Finance we're a Dao working independently to connect hummingbot and exchanges, and our first project is with sift chain.

C

um As most of you are probably already aware, um our project lead to Nicolo or pecunico or paku. Nino is uh often in these calls and and active in the in the Discord, but essentially um we originally wanted simply to add a sift chain connector. But as as development progressed, we realized that we could create also a essentially a cosmos abstraction layer that would allow yeah many different uh cosmos-based uh exchanges built on the cosmos SDK to much easier connect to uh or build on onto huntingbot.

C

So that is the first of our pull requests, which is active right now um and then the following pull requests. Indeed, uh we have planned to integrate a sift chain connector as well, and uh that is not all. We also intend to continue uh developing. So we want to. uh We want to be recognized and and known members in the hummingbot development community, so we're going to keep looking for opportunities to uh to connect.

A

Good thanks a lot Nick yeah and uh thank you very much for contributing uh I.

B

Know that you guys.

A

Have spent a lot of time on the on the cosmos, one so change one, so so yeah I think we should we'll try to help you kind of navigate the governance process.

A

um One thing I actually note is that I do think, there's quite a lot of value in having a cosmos bass, clear integration uh into Gateway, uh informing but um I I. Think there's, um there's a few I think there's still about 1.3 million tokens in the Gateway B2 uh kind of governance proposal.

A

um You know allocation, so um so you could probably submit um a I guess we would call it the hip. They help me buy an approval proposal uh to kind of like allocate bounties from that allocation um for the cosmos. Integration uh generally I think I think the community will likely support the cosmos, basically allocating H5 tokens for the base. Later integration, I I feel like they would likely.

A

um You know, vote for that, whereas uh I think the sift chain integration made kind of that may just need to be before class, because I'm not sure if the community will. You know like how much they would value uh kind of like the shifting integration versus like a generalized Cosmos. One but.

B

I do I definitely think the cosmos integration.

A

uh Deserves you know some tokens and I think um I think if you need help submitting HIV for that, we can probably help.

C

Awesome, thank you very much yeah. We, um we were actually thinking along similar lines um and our planning um an hip um and would definitely like to uh to collaborate on that to see what what is a an appropriate and fair amount to ask and yeah.

A

How much the value.

C

A

So actually I think I would say um the because coin Alpha, you know our parent company they're actually planning to submit a uh hip for I, believe uh Kronos and near Integrations in the next. um You know a week or so so I think that once.

B

A

Those you can probably just copy the template and do the same thing.

C

Amazing, okay, yeah.

A

um Maybe if I can ask a few questions about the what you've already submitted uh Nick.

C

Yeah sorry go ahead, uh any any questions you might have.

A

um Yes, so so it seems like what you submitted is the the cosmos um the base chain. uh You know proquest, can you can you talk a bit about more about, like kind of you know, maybe uh since you're online like what what what what the current proquest does and maybe your plans for future ones.

C

uh So the current one is essentially the components that are used in every Cosmos related protocol, um so I mean essentially just creating a a global foundation for Cosmos based applications that um yeah Will Allow whenever somebody is, is building on on or wanting to connect to a hummingbot to a cosmos based uh exchange that they will not have to do. The added development of integrating those those variables which are common throughout all Cosmos SDK based applications.

A

So the the chain basically allows kind of people to select Cosmos chains. um Did you also add like the the different networks in as well like the um and and and um like like, for instance like so right now it sounds like the current one adds Cosmos basic chain support, but it doesn't add any any dexes.

C

Yeah, that's correct so that we have three following uh pull requests planned.

C

um We originally planned just two, but in cooperation with uh fawzi, um we found that it was, or rather uh our our project, lead, Nicolo and and fousey decided that it would be better to break it up a little bit more. So the actual exchange elements are coming in the following: pull: requests: okay,.

A

Got it got it got it and and I think you mentioned earlier, um you you had to create some changes in order to get um like uh get it working with chain, because.

D

A

Because I I think that um I guess like so um because right now we're trying to do a Gateway is kind of have like very standardized exchange types. But you know like a uni file, B2 amm, use of V3, a man and then and those can then be used by kind of like these specific files on the countryside. uh Like you.

B

Know and so so my question would be like I guess, like Are, there specific features.

A

Of chain that you had to you know kind of, like um kind of like you know like what are some of the changes you had to make in order to make it work uh with.

C

um There is definitely I mean because of the way Cosmos based exchanges, work, um they're, not they're, not built, like uh yeah I'm, doing a bad job of explaining this. Maybe uh Nicolo. Are you uh available to he's listening in I? Don't know if he has uh time to get into details.

D

Yeah I think if we could invite pecanino also, he he's in.

C

D

Call yeah he's in the column, but just on stage yeah I think he would benefit hey.

E

Guys, thanks for inviting um so the main issue, we uh Civ is also an mm uh basically, uh but they use a different kind of uh uh translation of the coins so because they have an EBC uh so inter blockchain component.

E

So when uh reviewing results with fousey, uh we understand that was not possible to use the the actual uh endpoints that the Gateway provides and- uh and so we we will need to create our own endpoints. For uh for for the webto itself. uh That then will be consumed by the client.

A

What in what why um why.

D

A

It not possible to use the currents uh like you know: the classes. Okay. What about the IBC? uh You know the aspect um is kind of like.

E

Just introduced.

E

E

um As far as I know, they don't use the same. uh The same logic. That unit swap provide, for example, and um yeah. We we we develop a on a different basic uh and uh we are creating our own endpoints, like uh you know, like Solana, did for a club, so we have created our own name endpoint, for the wallet so and uh in the future we are creating our own endpoints for the network as well.

A

Yeah yeah so so yeah, so the the yeah.

D

A

D

A

Say um there's a lot of guys. uh You know we are kind of allowing them to create their own classes, but it's also more because it's that class is designed for like order book yeah order. Book Exchange is like serum and so forth, so so the the part that I I think that um I would say overall we're not opposed to adding kind of like more accommodations for new types of exchanges uh in that connector class. uh I. Just want to point out that.

E

The way that it was designed.

A

Was that um these, like kind of Gateway, connector classes and client, are supposed to be abstracted to exchange types so, for example, uh Club connectors, amm, connectors or you know, amm concentrating liquidity connectors. So that's why it's like. So that's why? What I'm trying to ask is more like on the cosmic side, it sounds like the change is not specific to an exchange, because it's still an amen, so it was still named them. Then um then, what is the kind of the additional complexity that that does not allow to use existing amm.

E

O because you sort of like a mix between mm and or order book, so this is related to shifting. uh um What we have created for Cosmos uh is like uh some some kind of classes. That then, would be irritated from for all the taxes that are built on top of the their SDK okay.

E

So but, for example, for for shift chain, uh we have to create our own inputs, but uh I'm I'm, open and happy to to discuss more with uh the functional lead and the review if there are possibility to to reuse your own endpoint. So this would be helpful also for us.

A

Go go okay, so so that means that if someone Builds an osmosis, connector yeah so once this connector could use, could build on top of your Cosmos base chain.

E

Exactly but use.

A

The regular, uh uh but because if chain has characteristics, both the Border Book Exchange and an amm, that's why I need to separate protect that.

E

Correct yeah, yeah, okay,.

A

Got it thanks thanks for clarification? No, no! No so overall I would say: yeah I think I think that um we're not opposed to it, but I always say that I think any yeah kind of any additional complexity. We would need to kind of review that to make sure that we're not going to like you know.

B

A

The complexity, I would say generally I, would say we're open to increasing common code base. It was absolutely necessary, uh however. uh Obviously we're trying to standardize.

E

Okay, uh that makes sense and um yeah I'm happy to review it and step step back and if to align with the uh with the logic that we have created for the code base. So no no problem on this okay.

A

Okay, but but overall, it's on a high level. uh I do want to thank you, for you know, contributing and especially because I I think they're, adding the cosmos the base layer. Integration is a very you know, important, a valuable contribution, so so I do want to think we'll try to work with you to support such.

E

C

Awesome. Thank you very much.

C

uh Does anyone else from the community have uh any questions.

C

Cool well, we are also available in our Discord. um We are providing as much documentation as we can also on our own docs page um and yeah, trying to do as much promotion as possible as well. So um you'll probably see us around, uh and uh thanks for inviting us.

A

Maybe can you post any uh documentation or anything yeah you want to kind of like highlight about you, know either petunia or for sub chain in the community called chat so that people.

C

D

Yeah, maybe we want to mention something about the bounties as well. Nick.

C

uh Yeah, we do also have open bounties for uh any community members who are looking for additional um development works. So uh um if you're interested in building, uh primarily in Cosmos, but also in uh in relation to other protocols um and in relation to connectors, um we are yeah putting together an infrastructure to facilitate that.

D

Awesome awesome thanks for inviting us guys to to the call.

B

Okay, thank you very much for me here, of course, playing which are you trying to do so, I, don't know if.

B

The performance thread, so thank you Carlita too so well.

B

We can continue now with the rest of the meeting. We have now to check the box pending and then q, a so for the Box pending. We are going to open the boundaries board. If you don't have the link. Is this one.

B

So important we have eight by eight bounties, open yeah, so one is to upgrade the San Diego spot connector from the initiative that we talked at the beginning of the of the meeting, and then we have mostly the same issues of last uh last week.

B

So I think that some of them that are important uh to check and to finalize are the ftx1. We have to take a decision, probably or close the issue or I, don't know check if someone has a check to really that the problem is not caused by what uh um well. The other features are more like cosmetics.

B

um Well, the minus one also is a little bit important, but at the same time there is one guy working on the revamp of the of the Linus perpetuos to the latest standards. So probably that will solve that issue too. So I I probably would like to remove that issue from there on this world.

B

So well as we mentioned every week, if you want to work on some of these just comment in that issue. Saying Hey I want to work in this issue and we are going to assign that to you. So so well, I don't know if anyone has a question on that or.

B

Something related uh one thing that we discussed today on our internal call we want to this is for all devs that are working on on different PRS or different bounties.

B

We want to that that you help us sticking to the rules and what I mean by sticking to the rules is like. If the contribution guidance says that rpr has to address and solve an issue, your PR has to solve the bug that is mentioned in the in the card. You don't have to make changes in all different files, adding typos or improving reliability or adding the types of the variables in different files, because that's not the goal of that PR.

B

If you want to do that, that I think that is very good, because it will help other depths to find a easy, which kind of viable is the one that you want, or you are going to fix, typos or something like that.

B

You can create another PR with that information or without change with those changes, and then we are going to review it, and why is this important and why you should stick to the rules because for the client side, I'm the only engineer reviewing them from the QA standpoint, we are only three guys that are reviewing all the PRS, so every time that you make a change in some part of the code, that is that can change or can have problems later on with the functionalities of that part needs to be tested.

B

So if, if in one PR that has to address some issue, we may change this in all different files. The q18 will have to test that and we are going to lose the focus that our focus is to change to to only fix the bugs of the code base or the bugs that are in the bounties board. So that's uh what I would like to say now uh uh um and it's easy. She just has to stick to the to the rules of the contribution guidelines so well.

B

I mentioned that uh well, Memento says it will be nice to have visibility on on when the bounty board is updated.

B

um Probably we can you mean like having some some information in the in the in the Discord or what do you mean about that?.

B

When they are boundaries, reviewed and updated, yeah I, don't think I I, don't know if the QA team can saying that every time that there is a bounty added or or open, but probably we can make like on a weekly or daily Snapchat. The thing is that they want this public and if you have any adapt you can go to that website and check the the bounties. There are different views, so you can check that in the different views, but well we we.

A

Yeah yeah yeah: this is a I think right now, right now, I would just check the board, but uh in future, what we might be doing that uh maybe use like the GitHub API and create like a Discord bot that, like you, know, updates every single time. Someone like you know like yeah, any kind of like a bounty card changes from one state to another. uh You can probably post uh like a message.

A

But I do think that yeah I think I think there's a.

B

A

To kind of get notified when something happens like that, so so I think the future yeah. If a lot once we have more developers working on.

B

Yeah I I also I also think that, but that part of the workflow is already automatic, because if you are working in a PR, GitHub already sends the emails to your account. If you are involved on that PR well, for in my side, every time that I'm involved in one PR, all the changes or the the updates I receive an email with updates.

B

But I don't know if you want to check the updates of all the different bugs or all the different PRS from different persons are working on that.

B

Before that you can go to the website. If you see rpr, you are going to receive an email or a notification in in GitHub and regarding to the the times the the how long the answer will take. That will depend that will depend on the PRS that we are reviewing in that moment and also it will depend on the availability of the reviewer and the complexity of the code, because, probably I don't know there are some PRS that I asked the review three times and every time that I have to review.

B

There is another code that you have to recheck. The code download all the things so well, normally in a weekly basis on Monday we find, which are the PRS, that we are going to work on uh uh on review, and we we put our reviews on that week. So in a weekly basis, we clean all the PRS that at least they have one review in a weekly basis. But, as I mentioned at the beginning, yesterday I had to review like seven br's, so I I am only one if you are working in one PR.

B

It's easy for you to know which are what are you changing and that's why I also asked at the beginning that only made the changes related to that VR. Just an example, the director of years, I use a mid Memento was very good in in the task of adding the rhetorical, but you added uh some a lot of unrelated changes without PR. That makes the work of the QA team harder because they have to test a lot of things.

B

So that's why I mentioned at the beginning that we should stick only to the to the solution to make the solution to that PR and then, if you want to submit another one, do another one. But that's how we are working on Monday we defined aprs to work on and on Friday. We finish the PRS so.

B

um And also in this in this meeting, every every Wednesday, we we told you, which are the PRS that we added into the world I. If there is another one the that you can take for now, they are eight years open. So well, if you want to work, you have like aprs to work on them. Also you you weren't in the meeting, but we mentioned the beginning.

B

That will be good to add more tickets, to create more great oracles because recycled feature to add a rate Oracle of another Exchange in your code and it's very straightforward to be the rhetorical. So probably we can add them. We can add some tickets to to add the the reviews.

A

Yeah yeah yeah the the process which we first serve the HTTP. Actually there I do think well, actually one thing that we're going to start doing is to try to formalize like the governance and maintenance process. More uh so that, um basically um you know when it's more visible to the community. You know how much h-bond has been allocated uh to tokens have been allocated to which you know initiatives and then once initiative is allocated now you can kind of, like you know, kind of create. uh You know boundaries from that.

A

So basically, that's why we've already um I think there's one that was uh uh the Snapchat currently for the uh the connect the sex connectors. So basically I think this is most of the process in terms of like process, what we should have done was created HTTP 25 of the sex connector revamp program. First, um you know gun gun this uh snapshot approved and then afterwards, then we create the bounties for the various.

A

um You know, exchange connectors.

B

A

Once someone actually has has actually created a connector, then what they should do is significant hip, or we help them to make the hip that allows the community to actually allocate this downtown.

A

So so that's kind of the process of work we're trying to kind of move toward, but overall it's something that I think um yeah. We're so excited make sure that, but um so so in terms of the the the right Oracle, we do think the radar equal, creating more bounties and developers get an ad vertible sources.

A

We should uh I think this time, each other. We should start the process. uh You know the right way by basically identifying like like how much bounties we should you know put for the uh you know, propose something for greater goals, create the hcp and get the allocation.

B

Improved uh yeah, yeah I will do it um and also for the I think the Memento is asking for the bounties board to assign Developers for that process. Probably we can invite next week to share me that is our community manager.

B

uh He can explain the process as he is following to assign developers to the shops, how we work the QA team, uploads the bugs to the to the bounties board, or we add some bugs that you want in this call. For example, if you say, hey, I think that this bug is important and it's not in the boundaries board. We can add that to once the the bound is using the period board in the bonus board. You can comment and that those comments will be reviewed by by our community manager.

B

That will be sharing me I share me, who said you are assigned to this PR or not. So probably we can ask Jeremy next week to have a five minutes. uh Call five minutes uh talk about the the process. uh What we can improve- and you can give him some feedback too about how we can improve that too.

B

B

Well, um probably now it's time to to some uh shame is here: okay, he's raising a hank a leader. Can you help him to the call I thought that you were sick, Jeremy.

D

uh um Hello guys yeah I am I, am sick, but I I saw the chat um so about this board I I.

D

We do check that every day me and QA, because we do need to wait to work on for the for the whole week, but at the same time, um I've been trying to limit like how many, how many issues can one developer get because as far as I'm as far as I'm, seeing like for the for the Improvement bounties for the connectors, like one developer, wanted to work on four and I, don't think that's optimal, because um it's better to distribute the work instead of one developer, working on four four different PRS for div for connectors right.

D

So that's not very productive. It's it's going to be as much as counterproductive for everyone, because we're on our side we're going to wait for them to to finish the pr for PRS and as far as far as depending on the bounties board date now, depending on the.

D

You're one of the one of the most active members of the community, um I I, always assign most of the issues to you, mostly within the day, because I'm working days in Asia time, so mostly maybe, if you're in U.S. It will be your night time and it's going to be my morning. um It's always updated every day, but if I do need some advice from a developer, I do have a meeting first with Federico before we assign anyone to the bounty.

D

B

A

Overall and um I think that you know the developers out there like I, think you should understand that you know we're we're trying to kind of make sure that everyone's a chance to pick up developer pick up bounties. So so, if we sign bounties to one developer, that means that other developers can't you know we can't assign that to other developers at the same time. So so overall I think this should be like.

A

Let's say for like bug, fixes like I, think developers should no developers should not be assigned more than like three at a time. I think because you know, if you should finish the ones you're working on currently before you get um similarly I think for connectors, connectors I think I feel like we should only sign one. You know to any any outstanding developer, because you know it the country's a pretty big projects that take multiple weeks, so um I think the developer has one assigned to them.

A

They shouldn't have another connector assigned until they finish that.

A

Does that make sense? It's yeah, because I feel like I, think this is just I I I yeah. We can try to formalize this, but I think a lot of things like it's a lot of times like it's better to just have a norm rather than explosive, Rule and I think this is one of those like Norms, that I think the shot established as a community. That kind of gives a chance to everyone else. You know so that.

B

A

Hopefully, increase dispersion of issues available.

D

D

Mostly, if it issues don't have comments, it means that no one is taking the bounty so yeah you, you can take it, but but uh mostly I think you have. We have like five PR's, mostly at the same time, so I think, oh, what whatever works for everyone, but at the same time we do want other developers to work on the bounties on the bounty board as well.

D

A

uh What's up, I think that yeah, if any, more there's more questions, please put them in the chat um you know and uh but I think that uh I think that we we should probably wrap up soon. Yeah.

B

Okay, well, I think that that's all because we cover all the topics for today so for the next week, I will probably have the proposal already to add more rate oracles to the to the to the to create the initiative of the to add more right oracles. uh Well, hopefully, we get more back solved and we can continue with this cycle every week. uh Well, thank you very much for all of you that are contributing with hummingbot I may I'm solving I'm fixing bugs so well, I think that's all.

A

Thanks everyone bye.