Mina Protocol Node Working Group Community, 22 Mar 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Mina Community Node Working Group Meeting | 3.22.22

Description

The weekly Node Working Group session serves as a platform for the community, ecosystem partners, and the Mina Foundation to interact.

This meeting is a time to discuss the latest core protocol releases and for members to propose suggestions, raise issues, and provide and get feedback.

If any community members have questions or feedback on the latest 1.3.0 beta 5 release, please visit the #mainnet-block-producers channel on the Mina Discord: https://bit.ly/MinaDiscord

The issues discussed can be found on GitHub: https://bit.ly/NWG-issues

Chapters

0:00 — Intro & Preamble
1:37 — O(1) Labs - GitHub issues updates and overview
5:25 — Mina Foundation Developer Relations - Iryna - Introduction
8:50 —Q&A / Discussion
- New uptime leaderboard backend
- Delegation Program community suggestions
- QA Testnet
- Other topic request

Mina Protocol – the world's lightest blockchain

A

All right, everyone hi, thank you for coming today. uh Welcome to the note working group sessions, uh we'll start off with a preamble and then we'll go through the agenda and there's not a lot on there. So um if anyone has anything else, they'd like to talk to, you can add it there or just uh just shout it out as we go through the meeting here.

A

So here's the preamble now the noteworking group session is a time when members come together to discuss and collaborate with ecosystem partners in the mena foundation, topics discussed generally include latest releases, node operations and other technical matters related to the protocol. Although this is the discretion of the node working group, uh my name is john robinson and I'm the community operation manager at the meena foundation and I'm here to support everyone and facilitate these sessions. So just let me know if there's anything, I'm forgetting to do or anything I can do to help out.

A

uh If anyone has any questions, uh please raise your hand with a button or shout it out. uh Also, you can drop it into the agenda and we can get to it. That way. Also, this meeting will be recorded and posted to youtube um in an effort to increase transparency and get the information that we're discussing here out to the broader community.

A

So thanks, I see some stuff's being added to the agenda now. So that's great. um Let's start off with the updates, and for that we'll go to our ecosystem partner owen labs, um andrew.

B

uh Hello: everyone, um the update today, will be about uh 1.3.1, where we're in the process of uh putting together the first alpha release, which should go out today or tomorrow, with a fairly small chain, set we're going to try and keep these releases coming faster than we have in the past.

B

Because yeah we're making more good small incremental changes, so we want to get them into your hands, and that includes a bunch of new metrics around um where the daemon is spending. It's like cpu time, which I think will be really useful in making sure that we don't introduce major performance bugs again in the future.

C

B

And I also want to just solicit out into the group here if there's any uh issues that you've experienced with 1.3.0, that we should look at uh trying to resolve for the future release, please please share it as soon as you can, either here or in the new working group channel and discord.

B

That's it for me.

D

So I guess I can go next. um I was out uh on pto last week, so um you know I'll be meeting with the networking team tomorrow morning and get a better sense of how things are progressing, but quickly by looking at our network stability board. um You know: we've made some uh progress on those timing, metrics and other things that hopefully will give us more information.

D

um One of the main things is: you know that the community has also asked us to look at regarding the snark work. Inclusion, that's still scheduled and we're going to be looking at that as we get some more time. But I beyond that, I don't really have clear visibility. Since I was out last week.

A

Thanks a lot prithvi yeah and um for anyone else watching the recording later on too, as andrew said, if you have any feedback or uh comments on the latest releases, you can post them in either mainnet block producer's channel and discord or the devnet channel, and if you ping, um one of the team members there, maybe linus chrome or um chris f, or something like that, we can have a look and get back to you with that.

A

So thanks bri um last last week there was a a request to actually go through the github uh board that I put a link up to in the agenda there. um Would it be all right to go through that really quickly.

D

Yeah definitely so.

A

I'll just share my screen here and get that up so.

A

Let me see here- oh I'm, sorry, I'm gonna have to readjust this a little bit here.

A

All right, I'm just gonna, have to resize this.

A

Does that come through all right, or would you like me to make it a bit smaller.

A

You guys still see that.

A

Great, if you would, if you could just give a quick rundown through it, if there's anything particular quickly, I can just scroll through it, for you.

D

The first one on the high priority column that uh that was added to our um last sprint uh as part of the networking team. So georgia was working on this one. um I think this work has is being done as a part of an integration test, so um we were thinking about actually working.

E

D

The priority and then scheduling uh different different stuff, so I I don't have the latest update on this, because I haven't got a chance to speak to george, yet so I can try to provide an update next week. The the next one, the node, restarts an issue after 30 minutes.

D

I believe this one actually can be closed now, because this issue ontab, was seeing this issue and we can close it because we arrive at a solution that was recommended to them and they found that it. It works. However, I'm not 100 sure if it's just localized um to that party or if other users are seeing it. I haven't really seen um other people harp about this one as much, maybe other folks have. So let me know if you think this is appropriate for closing.

D

All right great, thank you.

A

Prithee, does anyone have any questions about the updates.

A

All right, that's that's good, then we'll move on to um we can move on to the next one there on the agenda and what we have up next I'll just readjust my screen here, but um we have an introduction. Today we have uh irina here who is the uh developer relation for the mina foundation and she's been meeting with a few people. I believe she's met quite a few people in the noteworking group and she's introduced herself in the discord channels, like that. So what it'll do I'll just stop the share here and uh irina?

A

Would you like to introduce yourself.

E

Hi everyone- I am irino, I'm the first person in the developer relations team at mina foundation, so we'll be responsible to provide education, support and engagement for them for their technical community. So please reach me out if you have any comments or recommendations and uh yeah or if you just want to meet or yeah or anything else yeah, I will be here to help you anything. I can thanks.

A

Thanks serena and erina um she's already had a kind of open call that she publicized in the main network producers channel and that so very easy to reach out to on discord or um through other means too.

A

um Okay, everybody. We have uh another thing up on the agenda here uh and the third one it says: can you share more about the issues encountered with the new uptime leaderboard back end? um I might be able to I like that. Andrew that looks good. um I I might be able to share something on that too.

A

um There hasn't been really a problem with the back end that I'm aware of um there was an issue with the uplink for the url we're using for getting the data from the nodes into the backend, and I don't have the details on the technical side of that, um but it has been worked out over the last.

A

I I got a message about it a couple hours ago, um so we will be able to put that out we'll put out some announcements in the near future and what we'll be doing is requesting that people move over to the new uptime system, while keeping the sidecar running. At the same time, there will be detailed instructions on this. um These instructions are quite simple, they're, basically the same as andrew posted in their release, notes on um quite a while back now, and so what we'll be doing?

A

There will introduce a bit of information on the scoring system and how we'll do that for the next um the cycle, so there is quite a bit of information coming up um really happy that was resolved.

A

I was told by a few people that should be something easy to solve, but it certainly was not um judging by the efforts that went into fixing this up um now now that it's up and as we get the other things moving along, um getting some communications out and explaining more. What we'd, like people to do to upgrade um to the new system and with a new scoring system, also try and get some more technical details for everyone, who's interested in that on actually what the problem was.

A

So I'm not sure if andrew do you know anything about that, is there anything you can say about that yeah yeah! I can.

B

Speak to it, we're largely we're trying to make sure that the same sort of uptime back end that we've been using for a while now can actually scale to the amount of people who have been using the sidecar and the amount of people who are going to keep using it um and to make sure that we can maintain it. So we introduced a load balancer and we're trying to verify the correctness of everything and the you know success rate of requests um and yeah.

B

I think I think we're in much better shape now, there's a new url that will come out in the announcement and yeah and it should be more reliable. That's what we're that's! What we're aiming for.

B

Go ahead, lamps.

C

Am thanks for the updates, so I just want to check out on the on the new update uptime system. Does it have a limitation on you know how many loads you run? I mean um the official recommendation is three but uh but I suspect that many many people are running more than that, which I think is adding extra note to the network. Is it thanks.

B

um The new system is not explicitly limiting it to three or anything like that, but there is a rate limit to how many requests you can make so there's for sure, diminishing returns on running more nodes like in ways that was not true of the previous sidecar, so that that should help, but also we can adjust that, and you know I think I think that's that's sort of um you know this same system can be applied.

B

We can apply more and more checks on the on the back end side, as we, you know, continue these technical discussions as a group, uh and you know we can sort of improve this stuff going.

C

Okay, thanks um yeah. I just think probably on that regard, john um some guidance on on those and also maybe anti-cheating um measures and how many nodes you run would be useful.

A

Yes, thanks lance and that that comes back to also some of the um suggestions that were made by people on the spreadsheet viewer you created for us which yeah thanks for that um and some some there will be some announcements with uh information on that coming out shortly too. Now.

A

Some of these things do take quite a lot of time, um partly because there's quite a few things going on, but also because there's quite a process involved in that and well some of these things were we were doing for the first time and as we've done it, we've found the processes improved quite a bit, and we found quite a few areas where we can streamline things so yeah. This is this is really um by introducing that and collecting feedback in that way. That was really great.

A

um So that's something that will definitely work on improving and using more like that, a little bit more information coming out on that. um One thing too, I will say, um and it'll it'll be quite clearly laid out in the instructions or that for upgrading and how things will work as we transition to the new system.

A

um People will be uh requested or, if well, you'll need to basically run both sidecar and the new append system on the same node, probably, but both systems will be used um during the transition period until we move to the uptime system, um the new uptime system. So please bear that in mind. um You'll hear that many times don't stop sidecar.

A

Does anyone have any questions about that.

A

All right, great um there's, another thing: anyone has anything else, I'd like to speak about today.

D

Oh appreciate hi, so I'd be very interested to uh know if um any of you guys got some time to participate in the keyboard network. um I know uh john, you and jonathan were interested in participating as well we're trying to be a little bit more aggressive with you know, trying to get the most testing that we can in the next two to three weeks and so I'd love to hear you know what your experiences have been in this.

A

um I I wasn't able to get anything set up. It was um yes, I've been running a little a bit low on time and a bit low on sleep these days. um I I believe jonathan was similar in that way too, but.

D

Yeah less about time and sleep and more about doing the beautiful weather in mexico. I didn't.

B

Get it running.

A

Jonathan, don't say that I'm so jealous.

D

No, no, no worries at all.

A

D

So I'm I'm basically gonna try to activate the community as best I can, and um you know our hopes is that we have a lot of people. You know playing around with it, and so, let's see uh you know lamps, do you know if, uh if you might get some time in the next two three weeks to participate a little bit or have you all ready.

C

I haven't sorry um yeah, probably this weekend I can. I can do a bit of testing.

A

That's what I said last weekend.

D

A

D

It totally makes sense because this is kind of like a volunteer basis right. um So, as you guys accommodate with your schedule, um you know we're just we're. Just really grateful to have your support and.

E

D

You can you know, since uh post some messages in the qa channel, just so that other users who are not as actively engaged see that you know hey some other folks are planning on you know getting around to this, so it can even be like hey I'm going to do it this weekend or or something like that. We'd really appreciate that.

D

um Are you looking for.

A

Quite a few people in there now is that right.

D

uh As many as as many as we can yeah, okay, okay, great.

A

Well, that's something for people watching the recording. Also, um if anyone is not in the qa task force channel, um it is a it's an old channel that we're using for this and it's a private channel but anyone's pretty much welcome to contact um chris f. That's me, chris f, in discord, uh just ping me- and I can add you to that channel.

A

So, if someone's out there wants to do some testing and get an idea of what the newer releases are looking like, um yeah, please ping chris f in discord and ask anyone here and if anyone hears anything about um someone wanting to join or someone who might be good to join that channel, please let me know it's not it's a it's a private channel, but basically anyone's welcome to join it. Just give me a ping.

D

Cool and I'll share the link with some common test scenarios that we want people to run uh here in the chat. So, if you're watching this recording later and you'd like to participate and run these steps, you know just uh message, john, on discord and we'll get you we'll get you added.

A

And that's probably something we should post in. um We can post that also in the qa net channel and um it might be worth posting um a message asking for people if anyone else is interested in mainnet block producers or the devnet channel as well. um So like, I said that that's a fairly old channel, the qa task force channel, and um they did some quite good testing back uh well, just just over a year ago now and uh but yeah, anyone can pretty much join.

A

um Yvonne are you here today, I can't see on my screen here.

A

um Last week after after we finished uh yvonne, had a suggestion that, um as things are going quite well now with uh node stability and there's been some fairly big, improvements uh already made that we could um make a section here for discussing other issues related to other topics as well, and so what I've done um I'll just share my screen again here, but down the bottom of the agenda.

A

I posted a little place where people can add other topics. um It's on the parking lot, one there's a link, an item number six there. So if anyone else has anything else, they would like to discuss um it's something that we can certainly do so, please feel free to add topics down the bottom there as well on some suggestions even had were related to snaps and things like that and some of the things we might not have uh people able to answer here now.

A

But if we have some notice of these questions coming up, what what we'll be able to do is try and find people who will be able to help out with those specific questions so yeah, please feel free to add there or bring up other topics as well, and I got that link here and it just goes down down to the bottom here.

A

So if there's anything, anyone would like to discuss just drop it in.

A

Alright, everyone uh anything else you would like to discuss.

A

We still have about five minutes or, if not I'll, stop the recording and I'll hang out till about half past and have a chat with anyone.

A

All right, well, a big welcome to you irina. Thank you very much, and I think was that you that was taking notes. Regina.

A

No sorry, I didn't take any notes. Oh it's jonathan jonathan! Thank you. So much appreciate it. Thank.

E

A

Yeah all right, everyone will. You have a great week out there and um yeah look forward to seeing you hopefully tomorrow um at the celebration, all right. Thanks a lot. Everybody.