Everything EOS EOS Leap Upgrade Group, 1 Sep 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Leap Weekly Meeting #30 (Aug 31st) 2022)

Description

This week the Leap working group updates the community with progress on Leap software testing, DUNE and CDT updates, and Testing on Jungle 4

00:00:02 Recap and this weeks topics by Daniel
00:01:23 DUNE and CDT updates by Stephen
00:03:07 Communicate upgrade plan by Daniel, Ted, Michael
00:11:17 Exchange and Dapps survey update by Randall
00:13:36 Testing on Jungle 4 by Daniel, Stephen
00:16:41 Kylin update by Daniel, Michael
00:18:47 DUNE update correction by Stephen
00:20:24 End

Summary
🟢 In progress action items are on track:
Leap software development #41
CDT RC3 was released yesterday
The current release of DUNE is not compatible with CDT RC3 and will require a minor update.
Communicate upgrade plan broadly #50
EOS Support has shared the The Leap 3.1 Upgrade Guide with exchanges and developers and is continuing to engage with them.
Many have acknowledged the upgrade and none have raised any concerns about the September 21 activation timeline.
EOS Support will prepare a public status report indicating which exchanges and developers have acknowledged the upgrade, their current status, and which stakeholders haven't responded.
We've not received any responses to the survey. We'll request responses to the survey as we continue to engage.
Test Mandel on Jungle 4 #44
Most BPs on Jungle have upgrade to Leap 3.1 final release.
CryptoLions is preparing to update EOS system contracts RC2 on Jungle but is reporting that they're getting the same hashes for RC2 as RC1. ENF is looking into it.
Testnet strategy #40
A number of BPs are now running Leap 3.1 final release on Kylin.
Upgrade Block Producer nodes #1
All top 26 block producers have been engaged 1 on 1 and have acknowledged they're preparing to upgrade in time for the September 21 upgrade. We're continuing to engage regularly and keeping track of the upgrade status.
ENF has proposed daily go/no-go standup starting ~September 10
We can propose the MSIG to activate features at the same time we begin the dailies.
We'll need to monitor signatures daily to make sure we don't activate early.
Participants (17)
Host: Daniel Keyes | EOS Nation
Stephen Diesel
Matt Witherspoon
Virginia Glass
EOSUSA Michael
Max_Cho :: KOREOS Owner-South Korea
Alysha Mims
Ross (EOSphere)
Randall Roland
Genie Kim - EOSeoul# NEOPLY
Ovi
Kevin Heifner
Andrii Cryptolions (Andriu Bobrovych)
junhank | NodeONE
Ted Cahall
Jeff Werner
Vlad

Everything EOS is the official media channel of the EOS Network Foundation (ENF). 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

Playing Welcome everybody, it is August 31st. This is our 30th week meeting uh quick recap. Last time we met a week ago. um The final race was already out uh so was June rc2 uh we're. We were waiting for rc3 of Dune and of CDT, so we can check in on how that's going um we've been making a big push on the communication strategy, both one-on-one with BPS and, more broadly, with all the DAP developers and exchanges. So we can check in on how that's going um testing on Jungle is ongoing.

A

I'm, not sure we can. If we've uh deployed rc2 contracts we can check in on that and kylan is also was all updated with power up protocol features activated, so that's fully upgraded on kailan. Now we're just been testing now uh and we can check in on how it's going with block producer. Upgrade I don't have much new to provide there, but everything seems on track um so from the top. How are we doing with uh Dune and CBT.

B

Yeah so update there is that we did release rc3 of CDT yesterday evening in terms of Dune. Everything that we've identified I think is kind of a nice to have so we're not planning an RC. At this time um we won't go stable with Dune until we've gone stable with CDT, but um that's kind of where we've landed right now is that CDT rc3 is out. There may be no other releases other than going stable, but uh we'll keep this group posted.

C

D

So Stephen Dune, that's currently out, will work with cdt3 right.

B

Yes, that that should be the case. um I will verify, but I have no reason to believe that it should be a problem.

D

And those will both go stable simultaneously, if, if, when we stable CDT, then right, that's correct thanks. Thank you.

A

All right so we'll get we're pretty confident about. This should I just say that it is and then, if you, if it's not let us know and I'll update that I.

B

Think that we should just go ahead and say that it is and I'll get you to update. That's fine cool.

A

uh Okay, anything else to add on this topic.

A

All right moving right along uh communication, um like I, said we have we're continuing one-on-one with with BPS all the BPS. Have. A knowledge are aware, are either in progress or um planning to update imminently to the final release.

A

um Don't have much more to provide other than that we'll uh we'll get them to start joining. Definitely go no go call on on the 21st uh we can talk about if, if we want to get more of them on perhaps next week in the following week,.

D

I think Eve was even asking if we could start a go, no go call I, don't know if it would just be internally with us, or um you know broader for, like a week to 10 days before September, so that every day 9 A.M whatever it is, go, no go. So we you know find you know, are these? Are people getting along and uh you know upgrading and then we know.

D

Okay, this exchange is saying: they're not going to make it and so they're just not going to be able to do transfers until they get there and we can start to. You know be clear about you know: okay, we've got, you know enough of the 21 we're good there, but we've gotta. You know the important part will be.

D

Do we have a few exchanges that that are not going to make it and that's going to be the critical part, uh because then you're going to get people that can't transfer on and off of their Exchange right, and so you you can feel free to check with Eve on that. But that is what I remember him saying in a previous one-on-one that he wanted me to let you know on this call that sure you should start to.

A

Go and the idea is do daily, uh perhaps not necessarily on a call each day we'll we could do it asynchronously or um you.

D

Know if there was a kind of a stand-up like just literally you know whether it's nine eight nine thirty whatever and just for 10 15 minutes like who else has has now completed, who has completed what issues have been found, and we start you know somewhere in early. You know maybe around September, 10th or 11th and do that every day and you know definitely should be. Checking in it'd be good to have some type of dashboard as to yeah.

D

That's what you got right here, maybe uh of of um checking off who is already running it and- uh and you know again, it's going to be important for things like binance bitfinex and anyone that's an exchange. If they don't upgrade, then transfers don't work.

A

C

I can also give you an update, we're actually 24, so we're not too far away from active and we're upgraded. So if somebody didn't on the BP side, it didn't help exchanges, but if at least I could unrag, we might be able to step in and at least not be broken.

A

Cool yeah we gotta, we got a couple of standbys not far out from from Top 21, who are highly engaged. It's helpful uh daily go no go stand up, starting around September 10th. We can start um trying to coordinate that uh we'll see how how much and again we can do a call and and try for those who are not able to join. We can continue getting their their status. Asynchronously.

D

um At least we would then be able to you know quickly. You know ascertain so the few of us that will join the call Eve probably would even try to join the call I think we, you know, for the asynchronous news that came in you'd be able to show those of us on the call exactly and right and you'd be able to decide. Eve might decide to start. You know making 2 A.M phone calls and things like that, based on how things are moving.

A

Okay in terms of the upgrade path- maybe that's something we should talk a little bit about too.

A

um Obviously, if we want to activate the feature upgrade on September 21st, there's going to take some time for us to collect the signatures on the MC, so we probably is there a date that we should Target proposing the MC and is there any measures we need to take to make sure it doesn't get executed early.

C

I think they're, not good Michael I, would say ma'am most of the time you need at least a week. You know to kind of circle the wagons you know um as for preventing execution I, that's about the only you know best way we've had is you can stack up enough and then back off some right, I'm engaged to have a.

A

Few of us hold yeah. Some of the engagement is not sign ready to sign when we're ready. Yes, uh alternative I, don't know if there's a way to like set a minimum execution time or something like that in an M6. Is that a set of thing.

C

um I mean you might be able to pack something up for it, but it's.

A

Probably easier just to yeah just have a few of us hold off on on the signatures.

C

Yeah they're designed to be fired at will once once they're approved, they're, fair game, so sounds.

D

Like a okay, a feature upgrade is asking for an msig no earlier than date, and then that way you know we could set a timing. You could have all the signatures ready, but it doesn't execute earlier than the no earlier date right. Even if you want to note that we can maybe look into that. Obviously this will be coming up in the future as well and it would be good to get the signatures ready, but not accidentally, you know, implement the chain upgrade before you know the time we're saying it's going.

C

To happen yeah, we fought that for many many years, even even small things. You know that you want the developer to be able to execute and watch it like on a console. It yeah. It's always been a delicate dance.

A

Yeah, hopefully, that no one notices this M6 up and doesn't exit because anyone can execute it. Doesn't they don't even have to be on the MC so well.

C

You spend days pushing everybody because Sonic on Sonic or sonic or panic, and then all the stragglers start coming in and keep bumping it back above the threshold. So you fight this. This ebb and flow.

A

Yeah uh cool, uh so that's what so, maybe this is a whatever date we decide to start doing. The go no-go is maybe perhaps kind of the same time. This is hey. Mc is up. Let's start, let's start really pushing for signatures, checking in on people's status.

C

Ready at nine o'clock yeah that nine o'clock meeting check the status of it, see if you need to pull any signatures so yeah that they at least could go inside, probably a good idea.

C

A

Okay and uh yeah I do have a you know, started tracking the for the BPS the status on here. uh Nation actually is you could consider us essentially done the only we have.

A

We have a ship node that we haven't updated and that's strictly just so that we have snapshots available for the old pre-leep upgrade and are still doing some work on diffuse, uh going through some test cases, but our all our BP nodes are actually upgraded ready to go on mainnet and, uh like I said, we are checking in one on one, and everyone has acknowledged on the exchange in-depth side of things. Randall.

A

Are you able to provide any um any uh status updates on on the responses you've been receiving and have we received any responses on the survey.

E

um On this, server-wise um I've not received anything yet, um but uh I've been able to have communication with binance and bittrex, um and my students working with coinbase um so far so good. um There is um no um problems as of yet. um They said that they are working on it and they're gonna upgrade their notes. So we just won't stand by just um uh waiting for anyone to reach out to us if they have any problems. But so far all the exchanges said that everything is fine and.

A

You have a record on your side on, like which exchanges have kind of given a thumbs up which have not responded which have, and so far no one has raised any not going to be able to meet. This upgrade is that right.

E

Yes, so far, that's the case and um yeah I have a um stats on that yeah.

A

D

Would be good if we could get that list of who has actually responded and acknowledged the message that would be great.

A

Yes, yeah I was just gonna say the same. We could maybe we can uh either I, don't know if you have a spreadsheet, where you're tracking that we could make public or we could create something similar to uh to this one here, there's probably maybe too many, but just this I guess a spreadsheet with the yes acknowledge, not acknowledged.

A

You know, issues upgraded, upgraded, yeah, yeah, uh so maybe Randall you and I. uh We can work offline, have a look at the data. You've got and put it in a a format. That's shareable publicly um on the next call, or even ahead of that we can even yeah, even even before that would be even better yeah. We can share it in our in our chat.

E

All right, we will discuss.

A

Going on jungle, we were looking to update the system contracts actually I'm, not familiar to anyone. Aware of the status on that did we did that msig go up. uh I saw that Boudin acknowledged last I checked that.

A

Looks like Okay.

A

The I don't see the msig has been proposed yet, but go down looks like Odin is acknowledging is he said he was receiving the same hashes as an rc1 for all system contracts when he was looking at the rc2 system contracts.

A

Does anyone know why that might be I'm guessing that's not supposed to be the case.

B

I I don't think that there were any meaningful changes to the code base other than some of the the renaming that took place to accommodate the migration into the antelope organization. So I think the system contracts uh shouldn't have any big changes to it. Between rc1 and rc2.

A

Okay, so we they selected that could be.

C

Out differently, even a single change, though right, that's.

A

Yeah I would think so either. Is it possible bodens looking at the doing something wrong or that the rc2 doesn't contain the changes somehow.

A

We may need someone more technical to um yes,.

B

Excuse me I'll, take that action, item offline um and and try and get some support from the team on that.

A

A

C

It helps I do think. Rc2 was deployed on Thailand, so you know we could probably check against that hash.

A

C

What Benny did.

A

A

A

So yeah we'll follow up with bodon on that. Otherwise, everything from our side from testing looks fine. Don't we haven't seen him run into any issues? I, don't know if anyone else has anything to report on testing.

A

A

I think that's again not much new to report on kylan either. There were um we've been also in addition to following up one-on-one with BPS on on EOS, we're making sure folks are updated on common, make sure it's stable, um so we've been tracking that too and pretty much everybody is, is updated and we've got the features activated. Things are so far looking good and we are on rc2 of the system, contracts.

C

And I don't know if it's kind of rolled into this whole bigger thing, but I do think that Danny got that savings, contract deployed and tested. We got it pushed through on kylan I, don't know, I think it's kind of part of the whole new update right through some something along the line. Anyway, it worked pretty cool, awesome piece of code.

A

Do you have a smart contractor to uh yeah for savings redirection.

A

um Cool anything else, uh so offline, like I, said, will me and Randall would will touch base and get a status update. That's publicly shareable and we'll share it in the uh in the chat and I will start planning for I'll get some BPS and, as Whoever has many, you know, impacted people as possible. You know maybe we'll get some exchanges beyond the top 21 and staff developers to join those dailies as well or at least provide their status and Report those back and um so we'll start now.

A

I'll, maybe I'll get that going on the calendar this time. Probably this is a good time. I think we'll keep it at this same time of the day.

A

um So we can look. Look forward to calendar invites for that anything else.

B

Just one minor correction from my end, um it does sound like there's one place where we need to do a version bump inside of Dune to ensure that it's compatible with the latest release of CDT. So we will keep you guys updated about when we get that out.

A

A

So this current release of Dune is not compatible. Is that right.

B

Yeah, that's correct. It's a hard-coded value associated with the latest, the previous RC.

A

Okay, so there will be: is this going to be another RC of Dune? Then.

B

I I'll discuss it with the team, but it makes the most sense, in my opinion, to release it as an RC just so that we have a functional stack to work with and then uh probably going stable after that, okay.

B

Should be a very minor change, though, as far as I understand.

A

A

uh Anything else.

A

C

A

You everybody have a great day.

C

Thanks everyone cheers. Thank you. Everyone thanks.

E

Daniel cheers bye.

B