Everything EOS EOS Leap Upgrade Group, 14 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Leap Meeting #35 (Oct 12th) 2022

Description

This week the Leap Upgrade Working Group updates the community on the release of Leap 3.2 RC1, the forthcoming CDT 3.1 release, EOS Support Survey, and more!

Here are this weeks notes: https://github.com/EOS-Nation/leap/issues/102

They can be found in the issues tab after the call each week.
https://github.com/EOS-Nation/leap/issues

00:00:00 Start
00:00:03 Last weeks recap
00:00:53 Software development
00:03:54 Blocks.log survey feedback
00:07:04 Software testing
00:11:00 End

Summary
🟢 In progress action items are on track: #41
Software development progress:
Leap 3.2 RC1 is out
This should include all the best of 2.1 plus some improvements in particular for performance issues experienced on WAX
CDT release 3.1 by end of this week or early next week
Possibility we'll get EOS system contract release in the next 1-2 weeks
EOS Support has sent out a survey seeking feedback on the usage of blocks.log files to help guide development for future software versions.
Early Survey Results (9 responses)

Participants (12)
Kevin Heifner
Jeff Werner
Max_Cho :: KOREOS Owner-South Korea
Denis Carriere
EOSUSA Michael
Daniel Keyes | EOS Nation
Alysha Mims
Stephen Diesel
Randall Roland
Ross (EOSphere)
Lovejoy
Ted Cahall

The EOS Network Foundation coordinates financial and non-financial support to encourage the growth and development of the EOS Network. We’re harnessing the power of decentralization to chart a coordinated future for the EOS Network as a force for positive global change.

// EOS Network Foundation //
https://www.eosnetework.com
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosnetwork.com
#EOS #EOSIO #ENF

A

All right welcome everybody. It is October 12th. This is if I'm not mistaken week, three post continuous Independence um last week, we quickly got a check in there was a patch release out 3.1.2 that was expected by the end of the week. We can get an update on on how that went.

A

um Work in progress on 3.2, rc1 and leak util also was expected by the end of the week.

A

um Enf was working towards can check in on March April timeline for the next for leap 4.0, and we talked about the blocks.log file survey that EOS support has been sending around and that, as of last week, we had eight responses. We can check in and see if there's anything more um so from the top uh Stephen. Maybe you can give us an update on these items here. How did that expected release? Go yeah.

B

So the patch release uh went out about mid-week to late week last week and then um end of week. We got that rc1 for 3.2 out, um there's absolutely a possibility that we have an rc2 follow-up on there. Just because we've had a few small inconsistencies. We want to tidy up, but so far so good from everything else that we've seen other things that we anticipate in terms of releases.

B

We will have a CDT release either by the end of this week or early next week, we're just incorporating a little bit more of the follow-on work related to crypto extensions.

B

um So just some of the C plus wrapper work there I'm just adding in the final gaps- and there is a little bit of discussion around in in eosystem contracts release, but it pins further internal discussion before we officially make that call I know there was some brief discussion last week about some stuff that had been discussed in telegram previously, and we were supposed to chat about it yesterday, but the meeting that we had dedicated to that actually got other priorities slipped in front of it.

B

Unfortunately, so the CDT release, just since I, see you've typed it there it'll, be I, believe a 3.1 release. If that helps for context. um But that's kind of our update 3.2 for leap is out. We anticipate 3.1, probably by end of week for CDT and then there's a possibility that we have an eosystem contracts released across the next couple of weeks.

A

A

And this is RC one.

A

With the possibility, it would be also getting an rc2 at some point.

B

Yeah I think that uh there's a decent likelihood of that.

A

All right and do you have the link handy for that.

B

I did have it open. um Let me see if I can grab it right, quick there. We are.

A

Beauty I'll add that to the notes.

A

All right anything else on the software Dev side of things.

B

No I think that that covers it for us great.

A

uh um Do we have Randall on the line, looks like we do? Are you able to speak yup.

C

A

How's it going Randall I need anything new to report on the uh block slog file survey.

C

um I think there was only one new person who filled it out um so pretty much. um It's not like a great um amount of numbers, but those who filled it out. um um You know people are saying that there's no need to um there's no need for chunked blocks that log file um as it was implemented in use, IO version 2.1 um six developers said no need for that and uh for developers said that um they would like it, but it seemed like um majority, um really don't care for it.

D

um Do you mean block producers, because it's developers don't care about this? It's going to be exchanges or block producers that care about this. Who did you pull.

C

Pretty much I'm just sent it to um exchanges and we sent it to um blood producers, um but I didn't really look to see um if the person was answering. The question was a block producer or it's an exchange, but we sent it to um exchanges and block producers specifically got it thanks.

A

And one thing I still haven't done, that I said I would is um you know. I know you've sent this to your newsletter group.

A

um Maybe we can do some if, if we're not satisfied with the number of responses we have at this point, we can kind of do a little bit of door-to-door with the block producers that we have contact with um we'll reach out on WeChat and try to get at least the kind of the top 21 in good good majority of them to fill out. The survey that.

D

Would be great, that's that's really what we're looking for.

A

Okay, we'll do that we'll work on that this week. Thank you um all right. Anything else on that topic.

C

um For now, I think, maybe we just wait and see if we can get more um blood produces, especially the blood producers in the top 21 um if they want to fill it out. So that leaves there's more um right.

A

Yeah you've got translated versions of these two if I'm not mistaken. Right, yes, already.

C

A

Already translated in 30 languages, English, Chinese and Korean great so I'll uh I'll circulate English and Chinese and Korean to those who need it.

C

A

All right so we'll check back in on that next week.

A

um That's all we really have um discussed last week and like as far as I know, there's no nothing really new to discuss unless anyone else has any agenda items to add for things to look forward to for either the next consensus upgrade or other kind of smaller updates. We have coming along the way.

A

Stephen is there anything in particular, we should be watching out for with these. This latest release things that, um if you're looking for feedback on or testing in particular.

B

Yeah, so I I, don't think that there's anything too big that uh we should be concerned about testing uh the one area where I think that there may be interesting. Curiosity, it's just that uh three strike rule related to um I, guess how CPU is being managed. I I understand that, specifically for wax that there were some uh performance hiccups, and this was something that really helped alleviate. That um Kevin has some great details on that.

B

If anyone has some further questions since he's the guy who did the work, but otherwise a lot of it is just backupported work from the 2.1 release historically, um so it it would just be interesting to see if we've kind of fulfilled the things that you were looking for in terms of getting the best of that release into uh what is now leap since, of course, uh that was after when we had forked from.

E

Cool and Stephen I was going to ask last week I had mentioned. There was some confusion about the I. Don't know the branch of the m-sig contract you had mentioned there might be some contract updates, I think coming up quick, you know, always you know do whatever, but I know at least the last week there was still some confusion trying to get the right hash, although I do think they finally chased it down, but did y'all get a bearing and plan on kind of rolling. All that back in.

B

um I actually think I asked you to follow up with me if you had any more details to share, uh but I do know that we plan to have a discussion around us. Eosystem contracts, 3.2 release, and it may be related to that um again. The discussion was scheduled for uh yesterday, but it didn't end up taking place since that meeting had another priority slip in front of it. The.

E

Most detail, I had I, think I sent you a telegram, link and I. Think I saw you join in there, so yeah I assume it was just basically figuring out the right contract that was ultimately deployed on EOS, which everybody kind of says.

E

Well, it's working fine over there and tends to be what's on the others, but as we push a lot of these other chains because a lot of them are going to be deprecating, you know uh deferred transactions and stuff like that, as they go through all this so I know one chain ran into it and worked their way through it, but if it gets rolled in I think that was just the one confusing piece and the time lock feature is working pretty well thanks. Danny.

B

You're welcome gotcha, sorry about that. I I must have missed uh that you connected the dots there. So that's.

E

Fine main thing is y'all are aware of it and like say put it on a bullet point on the system contract, but there was just some confusion, but I do think. Eric had the right, Branch hatch and uh they got it to match. But of course that's a you know, needle in a haystack using the right CDT in the right version. But um so if you need some more details about which one I think Eric probably knows more about it than me, but I could probably Chase it down in some of the channels but main.

B

Thing is right and um just for context: he is the person who's looking to bring the 3.2 discussion into the fold. um We've just not made it happen yet so um I I'll look to maybe comment uh by end of day on this thread just to give people an update. Sorry for the delay there guys foreign.

A

Cool, thank you um anything else to add today or new items. To add great in that case, I think we can wrap things up for for the day, um so we'll we'll close it up. I'll put out the summary and the recording and we'll see you all in a week thanks everybody.

C

Cheers everyone bye thanks, bye.