Everything EOS EOS Leap Upgrade Group, 29 Sep 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Leap Weekly Meeting #33 (Sept 28th) 2022

Description

This week the Leap huddle group updates the community with the Leap 3.1 consensus upgrade status, software and patch updates, Token 2049 and more!

00:00:00 Start
00:00:02 Recap and this weeks topics
00:00:40 Leap 3.1 upgrade status
00:05:37 Software and patch updates
00:09:49 Block logs splitting survey update
00:13:20 The next consensus upgrade
00:17:13 Token 2049 update
00:22:45 Patch testing and recommendations
00:00:00 End

Summary
🟢 In progress action items are on track:
#36
The September 21 Leap upgrade was a success! Some top-tier exchanges had to pause deposits and withdrawals following the upgrade, but based on analysis from members of the working group on the call and EOS Support, deposits and withdrawals have resumed on all top-tier exchanges we've tested.
#41
ENF has released the following patch releases this week:
Leap: https://github.com/AntelopeIO/leap/releases/tag/v3.1.1
CDT: https://github.com/AntelopeIO/cdt/releases/tag/v3.0.1
EOS System Contracts: https://github.com/eosnetworkfoundation/eos-system-contracts/releases/tag/v3.1.1
Software development progress:
Work in progress on 3.2.0 RC1 and leap-util
We should have a target release date to report by next week's call.
ENF is working towards a possible March/April timeline for next consensus upgrade to Leap 4.0
EOS Support is preparing to send out a survey seeking feedback on the usage of blocks.log files to help guide development for future software versions.
Token 2049
Ross provided an update from the ground at Token 2049. The conference is huge and EOS is getting people's attention.
Participants (11)
Kevin Heifner
EOSUSA Michael
Max_Cho :: KOREOS Owner-South Korea
Vadym | Everstake
Daniel Keyes | EOS Nation
Stephen Diesel
Randall Roland
Ross (EOSphere)
Jeff Werner
Alysha Mims
Denis Carriere

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's September 28th! This is now our first week of meeting since the leap upgrade um and whether the goal now is to start planning for the next upgrade, which might be as soon as six months away um another another potential consensus upgrade on the horizon that we can start preparing for um before we jump into that.

A

Maybe we can just quickly um get a read in the room on how things are going now that we're upgraded to LEAP um the day after we had a a quick catch up to check how things are going, and we did uh note that there's a few exchanges that had uh some of the big ones that that had uh paused deposits and withdrawals as they were getting some other infrastructure upgraded, updated um some, some of them still using the old depreciated V1 history.

A

um As far as I know, the the two big ones that we were discussing, finance and bitfinex seem to now be back uh back in business from what I can tell Finance for sure. We've been testing that ourselves and um it's as far as you know, bitfinex as well, I'm, not sure. If anyone else out, there has been in touch with anyone or experienced any downtime or anything else to report coming out of the upgrade.

B

um Also bittrex is up and running. um We were able to get confirmation from them um and Big Goal I was able to get confirmation from them as well that they are up and running as well, um so I think so far. So good um and I think coinbase is working right if I'm not mistaken, coinbase.

A

Was working from the from the yeah they were ready, uh destroys. You know like instantly.

B

Yeah so yeah so I think um the major major ones are okay and working um I confirmed with the big go. um They said that they actually help with um bullish. So if they wanna um um how great they can be able to help them, but they didn't go too much into um details, but pretty much. They said the developers there said that they they work with them as well.

B

um Hot coin, um updated um um c e x that I also updated they're now working on um possibly um listing um usdt.

B

um It's something that I was able to talk to one of the owners about um they said within one or two weeks, but you know I can't promise anything, but that's something that they also working on. um Let me see um okx.

B

Let me see what okay said: um uh okay, they said that they were upgrading, but they didn't give me 100 confirmation, but some of them once they are okay, they don't um um you know, talk back what, because they feel confident that everything is fine, so so far, I think that one is um okay.

B

uh Let me see uh I mean I. Think those are like. Oh big get big get is okay, um they are they updated. They also gave me um um confirmation, so that's good um yeah, so so far some of them are okay, um the ones that are um we're asking a lot of questions they they're able to agree sexually, but um as always, if I'm any Community member is having problems or like being able to withdraw or Deposit they can.

B

Let us know so that at least we can focus a lot more on that exchange and try to give them help.

C

Thank you excellent.

A

All right anyone else to anything to report on before we even I see we have some uh some software related news uh from the enf we can move to next, um but before we do that, any other comments on how the upgrade went, uh I think I think it went like all things considered. I think it went very smoothly. Obviously you know there was yeah a few exchanges that that had to pause service, um but given the complexity of this upgrade there, it was you know, forking from an old version of eosio.

A

You know if you're running, 2.1 you're going to have a bad time got to go from 2.0 depreciating of the V1 history solution and a Rebrand all happening at the same time. So, despite all that complexity, I think I think it went very smoothly. Yeah I, agree, I, agree with you, yeah.

C

A

Yeah and uh perhaps an opportunity we can maybe do a retrospective or and put a little kind of um post-mortem, we'll write about something like I'm working with the team to make sure we're even better prepared for the next one, um but the next one, I I, the conditions are alone are vastly different, should be a simpler upgrade, um so yeah I would just say congrats to everyone. Thank you, everyone for for your engagement and um let's, let's get ready for the next one.

C

A

Let's, uh let's move on then to Stephen uh sounds like there's some some news on the software side. We've got a a patch out. Can you speak to that? A bit.

D

Yeah, so just a little bit of cleanup for the most part, honestly a couple of silly bugs here and there, um but just did a wave of patch releases over the last week, uh leap went out last week and then we got CDT in the EO system contracts released yesterday, um I I, don't think that there's anything too critical um to really touch on just would of course, recommend using the most up-to-date versions, um I think maybe with CDT.

D

The inconsistency and the Avi generated for map is the the one main reason I think we would want people to update um and it I I can't speak to the exact details of it. But I think that it was just uh some sort of inconsistency uh with the abis being generated by a previous version, so just recommended that we upgrade to the latest version, um but that's about it from us.

D

The only other thing that I'll make mention of that I, don't think, needs too much discussion today, but we are planning the release of a version 3.2 and the RC. One of that I would assume we're probably going to be looking at as soon as late next week or the week thereafter after I.

D

Don't think that this of course requires nearly as much uh hand holding and coordination, but a lot of that release is just going to be centered around a lot of the back Port work that oci has been helping us out with, and then we are going to be releasing a little bit more uh Tooling in the form of a new thing that our teammate vlad's been working on called leap util, and it's really just meant to help manage all of uh the the various commands across a number of the different Services being used.

D

I can drop a link to kind of the the scope of that as well if anyone's interested. But that's all we've got going on on technology side.

C

D

C

A

So I've uh I'm putting the the links to the updates here, the patches in the notes here that we can share more broadly um yeah and any info on the so two point. Sorry, three 3.2 is that right so.

D

What you guys are working on now, so it would be 3.2.0, rc1 and I would assume over the next couple of weeks. There's a few bugs that we're just working on trying to squeeze in at this point and then um we're just doing a little bit of discussion around like the scope of uh what all leaputo will do as the MVP um there's, basically a snapshot which snapshotting related feature that we're either trying to get in or just release without for V1.

A

Great any um and timelines uh any any timelines around that or not at this time.

D

In terms of the decision there, uh we we had discussed yesterday that we're just going to touch base tomorrow and um our refinement session and just kind of see how uh everything's kind of lining up with both uh leap, util and then there's again. One bug that we had discussed yesterday afternoon and just trying to see the timeline and actual scope of that bug.

D

um It may be just a couple of places where we need to do a fix, but uh Kevin right now is looking into just the the full breadth of that I I think we'll have some clarity by end of day tomorrow around when we'd be shooting for that first rc.

D

um But again it's it's probably going to be late next week or the week thereafter.

A

Cool and that's just a simple upgrade: anyone can do whenever they please there's no, no consensus impacts. Anything like that. It's uh that's correct standard standards, update cool any questions or comments on that topic.

A

uh Maybe Randall you can give an update on the the survey you guys are preparing on the Block logs splitting.

A

Might not be much much to share there, but I know that you're about to, if not already have um sent out a new survey to catch some feedback from the enf.

A

Maybe Randall can't speak right now. That's fine! um So yeah we you can expect. If you're on the EO support mailing list, um there's going to be a survey going out if it hasn't already I, don't think it has, but it should be going out very soon. Yeah.

B

um But yeah Daniel, sorry about that. That's all right yeah! So we are working on blogs.log survey um which uh will will possibly send out. Maybe today or tomorrow, um I was waiting for translation. um So the goal is to um give the survey to um developers so that they can. Let us know um what project they are working on if they they need um chunk blast that that log files um or if they have other ways that they want those um um um files um to be um developed right.

B

So we are trying to get updates on that, so that we can share with uh um the enf and um the core team developers so that they can come up with better ways to to help them with their development of um their project and how they store um files.

B

So I'm going to be doing that, hopefully, today or tomorrow, everything is done just we're here for a last translation and then we will send them out.

A

Is the English version in a state that is ready to share like? Is there value, maybe in sharing it with this group here? If there's anyone on this call, who maybe can provide feedback, you can get start get that feedback rolling.

B

Yeah I think um I think it would be great. um Do you have the you? Have the link or you're going to.

A

Do I've got the link that you shared me so I can I'll drop it in the chat here. um So all that before you're, all you're waiting for to send the emails is the translated version of this. But in the meantime the English one is good to go. Is that right.

B

That's correct: okay,.

A

So I'm dropping the link to that survey. Here, um make sure you check the there's additional. Maybe I'll drop you a link to the article to which is linked in the survey they both link to each other.

A

Some more background in this second link: I, just posted in the chat I'll, make sure that's included in the summary, as well um and yeah feedback looking for basically any node operators and and block producers. So in addition to sharing it uh through the EOS, uh you a support newsletter. While we can pass it around to the the top 21 BPS, as we did with the you know, as we were getting their status same same kind of deal.

A

um So there we go any uh comments on that topic.

A

All right and then otherwise we can I, don't know if we're out of state, yet we're we're ready to start talking about the next consensus. Upgrade I, don't know if uh Steven has any insight into timelines or anything like that on what the plan is for the next consensus upgrade and and what we need to be lining up for that.

D

Yeah so I I guess the the bit of light I can shed on it right now is that um what we've been discussing to date is kind of a March April timeline, um the scope of which is still being negotiated. uh Part of what's come into play there, which has been shared on this call in the past, is that some of our resources have been directed over towards closing out the trust evm project.

D

So as a result of that I I, don't think that we've got too many details to fill in just yet, um but I think quite frankly, over the next I'd say three or so weeks. We're gonna have a lot more clarity on um what all will be able to prioritize inside of that there's a number of large initiatives that we've broken ground on, but in terms of committing to an official timeline or anything, we've not we've not done that. Yet. Okay,.

A

The ballpark was perhaps looking in March April for and that's going to be, 4.0.

D

The Assumption at this time is that there will absolutely be at least one breaking change: pushing us into 4.0 land um I'll, just disclaim uh just to cya here that if there's any chance that there's not a breaking change, there's an entire possibility that we may just go with the 3.3 um I see. That is highly highly unlikely, though.

A

Okay, cool good to know, uh but yeah at least we have a rough timeline to work towards um and I guess this won't be called leap. Is that right did I? Guess we're getting a little ahead of ourselves on talking about the name and stuff like that, but.

D

I I will let marketing defer to that I think that I mean the repo is always going to be called leap: um okay, whether it's Antelope leap, something or Antelope, something the repo is always going to be elite. So, okay.

A

So we can still refer to it as a leap upgrade good uh okay, so the the.

B

I have a quick question. So um leap is basically the C plus plus um implementation of uh of the code right because I think that's what I was getting and I want to make sure that I'm not giving people the wrong um impression here. Yeah.

D

So it's just it's the implementation of the the node software that they're going to be running and it's the C plus implementation just like how there can be multiple other implementations of it and it's the implementation of the antelope protocol. Okay,.

B

Okay, so for us to change the name, we have to have something like uh a different program like let's say we have rust, then that can be a different name, pretty much.

D

um Yeah again, this is kind of a place where we'll work to give clarity about the naming of future releases coming out of this C plus implementation, um but, quite frankly, I think. If anyone else were to implement another uh node software implementation of this protocol, they would probably name it what whatever they wanted to name it, because it would be kind of their baby. If that makes sense,.

B

I got it okay! Thank you. So much.

A

C

A

E

Sorry, I just I'm a token 2049, so I was going to give you guys an update if you're interested.

A

Yeah, no, let's, let's hear it.

E

Yeah so token 2049 it's in Singapore this week, uh just oh it's two days this week and it aligns with uh Singapore blockchain week. So there's 101, like Eventbrite smaller event. Type thing is going on around the city and today was the end of day one of the um EOS Network Foundation sponsored with trust, evm, sponsored uh token 2049 event. So we've got a stand and there's a trust. Evm stage uh this morning we had Eve give the run through about how we broke away from block. One was actually quite a good.

E

um It was it. It was um like a fireside chat, but it was pretty much Eve, just kind of giving everybody the 101 of how far we've come over the year, and you know where we're going to go. It was quite positive. um The conference is really big here, I think. As far as crypto conferences go, this is the biggest that I've seen uh they reckon seven thousand attendees and there's got to be a couple of hundred exhibition uh like stands and stuff. It really is a lot.

E

I've got two bags of Swag I've got so much like you would love it, um but the the stand.

E

It's kind of shared yesterday foundation and the trust evm guys the trustee VM guys um I actually can't remember their names, but um they seem to be getting a lot of questions and then Eve, Zach and um Petty are in the standard and I've been there with Diego from uh from Rio we've kind of just been helping answering questions, but everybody's got the same. Everybody's got the same. Ask of us like, what's going on with EOS, you know, isn't it dead? You know everything that we all heard um and I think I think we've.

E

Definitely as far as people at this conference. A lot of them have left thinking. Oh no, yes, is definitely doing something. um We've got some nice statistics to share with them when they come past. The stand on the the speed of you know, 800 swaps, per second, that we expected on The, Trusted, UVM, overlay and um I. Think overall, it's a very positive conference. So far you know, um I was very surprised how many other layer ones they are out.

E

There I can't even remember their names, man, the ones that are in like development that are launching, but not they're, not even based on anything that you know they just got their own plans, there's so many of them. um But it's it's like a trade. It's like a trade show for blockchain protocols, it's pretty much and and exchanges.

E

You know so. There's just there's tons of people here um and you know: we've got, we've got a nice spot and getting a lot of traffic and definitely a lot of uh interest in EOS and where we're going.

A

E

E

Yeah yeah, it's pretty good um yeah Eve was saying much bigger than the Soul conference that just came from, but yeah like so many people and and of course it's the Formula One going on at the moment. So um the city has got all the streets closed off. It's like a nightmare to get from point A to point B, and this is so many people in the city. It's uh it's bubbling here.

A

That's cool! That's cool thanks for uh for sharing your your! Are you.

D

E

You're not in the.

A

Conference right now are you or you're.

E

You know the whole the whole clothes that like hop us five um and then um you know it took me so long to get back to my hotel, because I had to take a Subway and everything was closed um and I'm just tired from standing. So it's going to be early night for me tonight and we got dinner with all the all the guys from the stand tomorrow. Night, so that'll be nice and we can connect some more on there.

E

But but yeah we've definitely had some amazing conversations and it's great to see some old face.

A

Awesome well make sure you uh say hi to the whole gang for us and uh and enjoy the rest of the conference there. Thanks for the for the report, yeah.

E

A

um Okay, so we've got, we've got a rough date. We've got a good report from the 2029. We've got a packed release. We've got um the blocks.log survey going out now.

A

um And maybe I'm just kind of spitballing here, I think what we're going to do. Speaking of maybe doing a post post-mortem on this upgrade um I'll work with the team to prepare. Perhaps a little survey on how did the upgrade go circulated around? Maybe we'll give it a little time for this block. Log survey get some traction, but would love to get feedback from the folks here as well.

A

As you know, whoever else from the community who either participated or were impacted, how the upgrade went- and maybe we can gain some insights on ways to improve for the next one.

A

Otherwise are there any any other topics we wanted to go over today.

A

What this patch release is there any anything in particular, we need to be looking out for anything. We should be testing on the test. Nets I I wouldn't be surprised if we were already Matthew's already upgraded us on mainnet.

D

Yeah I I think that the the main thing that uh we would have been interested in some results around were in the patch release that came out last week. I think that Kevin had made that change that some people had already made an upgrade to with, like their own version of a release related to the subjective billing and um its use of a different like integer representation value.

D

Uh Kevin is: is there anything that comes to mind for you that across these patch releases that people would be interested in or want to test uh nothing huge come into mind? For me,.

F

N32, um where you mentioned in a couple weeks here, uh it does have the um subjective uh three strike rule applied to speculative nodes, which is a a difference in behavior that uh certainly would be looking for for feedback on uh that can be, of course, enabled or disabled according to the whether you have subjective billing enabled on your node uh but I know, at least in my testing on uh wax. It made a huge difference on my speculative mode, CPU usage.

D

Right and I guess just looking at the like the patch releases that are out right now that that's where I was speaking to there being maybe some notable difference as well. But is there anything else that comes to mind for you that people would want to look out for a test? I I! Don't think that there's any big take-homes that jump out at me.

F

Yeah I I, don't think so I mean we do think that we've got Tacomas taken care of for uh for Michael. But uh you know if you run across one of those. Certainly let us know.

C

I hadn't seen them recently, but I, don't know everything's 3-1, but the even the old two old nodes haven't had a lot of Comas, but yeah I mean at least so far. So good.

A

And I'm, looking at the uh the validator Matthews validator, it does look like the nation is already upgraded on mainnet to 3.1.1 and as far as I know, everything's running smoothly. So.

C

Yeah, we haven't gone all the way up. We had across the board, but I know on a lot of different chains for a lot of different operators, they've already kind of rolled to 3-1-1, um maybe I'll install a TCP patch. Soon uh only the old Fergus will get there.

D

Yeah I guess um one other thing that I'll mention just since it is a discussion item yesterday for us is uh whether we were going to do any sort of patch release for Dune. um Historically, in these meetings, you may recall that we had to bump the version when we bumped the version of the other repos that had dependencies on we're just going to be waiting until we get out this 3.2 RC. Before we do any bumps there, uh people should be able to manage just fine, but just I guess covering bases there.

D

You should not expect a patch release at this time for dude.

A

Okay, all right, unless there's anything else, that's all I have on my side for today.

A

Thank you. Everyone have a great day and we'll see you in a week.

E