Everything EOS EOS Leap Upgrade Group, 21 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Leap Meeting #36 (Oct 19th) 2022

Description

This week the Leap working group updates the community on software development, EOS Support Survey, and Blocks.log files.

** Encourage BPs and node operators to join the call next week for the discussion on the blocks.log survey.

00:00:00 Start
00:00:03 Recap and this weeks topics
00:00:38 Loftware releases
00:05:54 Blocks.log files
00:11:00 End

Summary
🟢 In progress action items are on track:
#41
Expecting Leap 3.2 RC2 with some bug fixes by the end of this week or early next week
CDT release 3.1 by end of this week or early next week
EOS System contracts and reference contracts to be updated shortly after to make it more user friendly
ENF is still working towards a possible March/April timeline for next consensus upgrade to Leap 4.0
The survey seeking feedback on the usage of blocks.log files has been shared with BPs, but no new responses have come in since last week.
Early Survey Results (9 responses)
On the agenda for next week's call: a technical discussion on this topic. We encourage BPs and node operators to join the call for the discussion.

Participants (10)
Dario | EOSsupport.io
EOSUSA Michael
Jeff Werner
Ross (EOSphere)
Stephen Diesel
Ted Cahall
Yves La Rose
Max_Cho :: KOREOS Owner-South Korea
Kevin Heifner
Daniel Keyes | EOS Nation

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.eosnetwork.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 19th. This is week four post English Independence Day. um Last week we checked in on how we're going on the software development side of things. uh Leap, 3.2, rc2, rc1 is out um CDT release. 3.1 was expected in the week. We can get a check in on see how that how that's going um so we talked about system contracts and we talked about the EOS support survey um and we probably I think maybe we have some news there. Let's we'll have a look.

A

um So, let's start from the top uh with the. How are we doing with the uh CBT release and eosystem contract release.

B

Yeah sure thing so uh top to bottom. When it comes to uh potential rc2 for 3.2, we will have a release, um there's just a few items that are still awaiting review for the most part. uh Nothing too critical, main things that are going in. There are just a couple simple bug fixes, as well as uh just a few enhancements to LEAP util, which is a new feature. We've introduced with 3.2.

B

So that's kind of the first update with respect to leap.

A

And that's leap: 3.2 right.

B

Yeah it'll be 3.2 rc2, that's correct!.

A

Any um timelines for that.

B

Yeah so I think I'd love to get some movement before the end of this week, but it may be early next week um and that's kind of the same update as it pertains to CDT.

B

um You know: we've got a couple of bugs that we still need to discuss and um in terms of what we were trying to get in. The main thing is uh just the remainder of the crypto extensions, uh just in support of some different Matthew stuff and we've just got somebody who's a little bit newer, cranking on it.

B

uh So it's just taking just a little bit longer than expected, but uh that's kind of our update is that we'll have uh an initial release of what I guess is uh CDT 3.1 on I guess around the same timeline.

A

Same same timelines, cool.

B

Yeah and then right, the last real update here, uh just related to EO system contracts. We finally had some discussion. um There's been some questions. The last couple weeks in this meeting about some discrepancies related to msig uh there. There was just a little bit of a gap there and we have somebody that's working on that.

B

We do anticipate a release and it may be around the same timeline as this, maybe maybe a week or so longer, but um we'd anticipate releasing that out in the eosystem contracts and, of course, uh we'll look to make that update inside of the reference contracts as well.

B

A

Also, roughly the same timelines, You're Expecting.

B

It may be a little bit longer like maybe a week longer. We've got some uh significant competing priorities so um yeah. It may just be a little bit longer and.

A

You said that's mostly to address the msig discrepancies like there are some I guess, gaps from the reality of their m6 and what was in the repo is that right, yeah.

B

There was just a a little bit of a a gap when we performed the migration over I. Don't think that uh it's is critically impacted anybody, but um these are just some updates that we need to get in uh to clean up the release and make it user friendly for anybody. That's trying to operate on the latest version of contracts.

C

And it was really needed for that time. Lock: contract, that's what kind of triggered the Rabbit Hole to go down was you need to be updated to the latest version and not everybody had, but it in itself kind of has some inherent whatever, but then there was that eight different repositories that yeah it's not like: they'd Chase it. So thanks thanks for knocking that out there there's a lot of change. That'll that'll be happy and yeah no major rush, because they're kind of waiting and seeing how we over here on EOS or blazing the trails.

B

Yeah no, um but it's definitely on our radar and thanks for uh reinforcing that priority for us uh glad we could get that tackled for you.

C

Love having Direct Communications with the people that get get stuff done now, it's been years happy.

B

A

And um are we still I'm just reminding myself the way we had some potential timelines for uh March April was kind of what we a couple weeks ago, were talking about for a potential leap 4.0 which would be a consensus upgrade and but I know, there's some uncertainty there, whether or not that will be a breaking change or not, depending on the capacity on the team. Is there any more certainty there at this point or still pretty uncertain, yeah.

B

I think that there remains a high level of confidence that there will be breaking changes in what we release there I think that it's pretty well safe to say that 4.0 in that timeline makes sense. What's what's really what we'll be working on. Communicating more clearly to this team is just the actual scope of what fits in there I've mentioned previously. We've had a couple of competing priorities uh with some of our very talented engineers and as a result of that, we're working on really pulling together.

B

What we'd like to confidently announce we'll all be inside of 4.0.

A

Great excuse me I'm, looking forward to that all right anything else to add on the software development side of things.

B

I think that that's it um yeah.

A

Great uh on the blocks log survey front, I'm, not sure if we got any more results in but I have uh circulated the survey kind of directly with the top 21 block producers. I know that's kind of a Target, an audience we really wanted to Target. uh Do we got Randall on the call did any have? Have you seen any movement there or maybe Dario can can speak to that? Yes, it did not get any more responses.

A

um Okay, so we'll I'll follow up there. Then, with the block producer see what I can do about get getting some more uh some more engagement there. um So.

C

Nothing about nuisance, we talk about it here. Sure.

A

Yeah, let's hear it.

C

I'm also curious, as you know, I mean I know. This is related to the EOS upgrade, but I mean it's a great opportunity for a lot of the tech people, the the VPS, as we kind of refer to them, um to come in and discuss and collaborate or even hear about what all you know, maybe currently on the plate.

C

um I was curious. If there was a you know, do we do we kind of tag them? Maybe two together that way, you can, you know, tag the upgrade at the beginning check on how that's going all the non-nerds break away and then the BPS or nerds geek speak. You know kind of expanding the meeting out as as a scheduled, live platform to really get together to talk about things like this. Damn.

B

C

Really had a hell of a time finding that correct hash. Well, that's why, um but that, then, that would give you a platform to, instead of blindly shooting out an email, resp and expecting responses from the BPS who don't I, don't check my email.

C

um You know offering some of them a platform. um You know Corvin coming in here and discussing some of his technical platform discussions more so than just the EOS Network upgrade itself, because it's a great team anyway, some I've been meaning to ask, as we kind of wide down the duration of these upgrades yeah.

A

It's a good point and we had a good. There was a good conversation a few weeks ago and you know we kind of had wrapped up the call and- and you know you Ross and uh Kevin kind of talking through some of the pain that uh that BPS feel.

C

And I think if you offer a platform scheduled, you know, like we see on a bunch of chains, you can get a lot of people showing up. Some people are the ones that never shut up like me, and then some people are the Next Generation that just sit there and listen and they learn. You know what I mean so anyway, something to think about I, just try not to hijack too much of the calls. Ross loves it when I talk so.

A

We we could try experimenting with that. um Is there a topic? You know with this block.logs question be uh perhaps a first topic we could. We could try.

C

I think so today, with.

A

The folks that are here, but then we could, you know actually make that an agenda item for the next week's call put out a call to action to everyone, including the BPS, invite them to join. um We can get Matthew to join uh I. Know he's probably already shared his thoughts on that topic, but you know maybe some discussion maybe would draw out some more insights, I.

C

A

Be great I like talking okay,.

A

um Okay well and any talk any comments on that topic for today, or do we want to save them for next week, when we put out a form I'll uh put that into the formal agenda.

C

From the technical side, yeah I mean it's more hypothetical and brings in some of the other things, and maybe focusing on that that Hot Topic list I forget what y'all call it the the all those not working groups or whatever the enf has you know it's like a list of 40 of them or whatever, but some of them whatever are the most Hot Topics. We can discuss that. Y'all are working on.

A

Cool so we'll we'll see how it goes uh we'll put out we'll make the the topic next week, block.logs files will I'll share the invite, with uh with all the BPS, we'll see how many we can get. We may need to get some translation help, but we can do that too, and, uh or at least we'll get. You know, I think definitely wouldn't be a problem getting Matthew on here and and uh some more of that other technical, nerds, um okay cool anything else for today. In the meantime,.

A

All right so well, uh we can wrap it up then, and we'll uh we'll see you next week and I'll share the summary and that uh that call to action for next week.