Everything EOS EOS Leap Upgrade Group, 24 Aug 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: EOS Leap Weekly Meeting #29 (Aug 24th 2022)

Description

This week the Leap launch group updates the community with progress on software releases, communication strategy, jungle testing, Kylin and more!

00:00:03 This weeks recap and topics by Daniel
00:02:02 Software release update by Stephen
00:04:40 Communication strategy by Daniel, Stephen
00:10:35 Testing on Jungle 4 by Michael, Bucky
00:15:39 Kylin update by Daniel, Denis
00:20:50 Platform support by Daniel, Stephen
00:21:26 wrapping it up with Survey update by Stephen, Daniel

Leap v3.1.0 Release Notes
https://github.com/AntelopeIO/leap/releases/tag/v3.1.0

Summary
🟢 In progress action items are on track:
Leap software development #41
Leap 3.1 Final Release is now available
DUNE 1.0 RC2 was released on August 18
DUNE RC3 and CDT RC3 is expected within the next week or so
Communicate upgrade plan broadly #50
The Leap 3.1 Upgrade Guide has been updated with the new Antelope branding.
EOS Support has shared the guide with exchanges and developers. 140 contacts have already responded to acknowledge the upgrade and none have indicated any concerns with the September 21 activation date.
We'll update the upgrade guide with links to the final release and continue to promote the September 21 upgrade and resources heavily this week.
Test Mandel on Jungle 4 #44
BPs on Jungle are asked to upgrade to Leap 3.1 final release.
We'll deploy EOS system contracts RC2 on Jungle this week
Testnet strategy #40
Kylin Testnet update 🚀
✅ PowerUp configured
✅ All protocol features activated (including 3.1.0 Crypto primitives)
✅ Latest system contract v3.1.0-rc2 deployed
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
EOS Nation has already updated all of our EOS nodes to Leap 3.1 final release, except for 1 SHIP node + dfuse, which stil need to be updated.
Participants (20)
Host: Daniel Keyes | EOS Nation
EOSUSA Michael
Max_Cho :: KOREOS Owner-South Korea
Corvin - cmadh | liquiid.io (Corvin Meyer auf der Heide)
Bucky Kittinger
Jeff Werner
Matt Witherspoon
Stephen Diesel
Patrick - Aloha EOS (Patrick Burns)
Genie Kim - EOSeoul# NEOPLY
Virginia Glass
Denis Carriere
Vlad
junhank | NodeONE
Kevin Heifner
Randall Roland
Ted Cahall
cc32d9
Yves La Rose
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

All right welcome everybody. It's august 24th. This is week. 29 of our weekly leap upgrade calls um let's uh quickly check in on the the outcome of last meeting and and we can check in on our progress. uh So last week we talked about starting to really push out the the mass communications we we've got. Our upgrade guide, all rebranded for antelope and leap and eos support team has been engaging with their list of of contacts exchanges dapps, so we can get a check in on how that's going.

A

At the same time, we've been on our side. Our team has been individually connecting with top 21, as well as a few of the standbys making sure they're all in the loop and ready um so again, I'll get can give updates there.

A

um Last time we checked in the 3.1 rc4 was out uh or was about, was on the brink of being released that day, and that was the case it was released. We can check in on how we're doing on the final release looks like last. I checked looks like that was tagged.

A

um Testing on jungle, ongoing dps were asked to upgrade to leap rc4. We can have a look at how that's going um and we had progress on pylin last week. M6 were up to configure power-ups just deploy system contracts. Activate protocol features again lots lots of progress there to report and um we had shared some news. Some feedback on dune and rc2 was scheduled to be released on thursday, with fixes for windows 10., um so anyways yeah, let's get let's get into it, um maybe actually start with software release.

A

How are we looking with the final release? Steven, maybe can, uh can you give us an update.

B

Yeah, absolutely so, I guess probably 14 15 hours ago, we we did bump the version to uh our final, stable release for leap. I can drop a link to those release, notes here, great and in in terms of some of the other code bases. We do anticipate an rc for cdt in dune, but this doesn't block our timeline for giving ourselves about that month. Runway that we want on the stable release of leap to move forward, so I'm ready to upgrade jungle to that version whenever it's really just the version bump.

B

So no significant changes there and I think, probably over the next week or so those rc3s for dune and cdt will make their way out um just a few things that we want to clean up before we go live.

A

A

Link to that in our issue here.

A

So it's official final race is out and release notes have been updated too.

B

Yep and uh with our final release, it's the aggregation of all of those rc's together. There may be a few updates just as we're tidying things up um but everything's in there, it's more about just tone-in structure, so feel free to. Let us know if you have any questions or feedback.

A

Great and you are dune rc2, that's due- is that right or.

B

This would be an rc3 and then uh cdt will also be in.

A

Rc3 right and sorry, where was there a timeline for that or just it's coming at some time.

B

I think that it will be within the next week quite honestly, but I don't think we've made any sort of uh explicit commitment. um Okay did some refinement around some of those issues. Yesterday.

A

Great excellent anything else to report on the software side of things.

B

I think that's about it um just kudos to everyone. That's helped support us getting this far. This is a really exciting step for us.

A

Yeah awesome. Thank you. Thank you steven. um So on now that that is out one thing that we can do on the communication strategy. Side of things is, I guess, there's still there's some new updates. We can add to the upgrade guide. um You know just indicating, for example, file releases out in lincoln there. I think right now here we're linking to rc4 um so we'll work with with you guys to get that updated to all the latest links.

A

um In the meantime, though, we've already been like, I said communicating this- I got an update from randall um this morning on the progress sounds like looking pretty good um randall mentioned that just like pull up here that um they they've received uh uh from all the emails they sent. 104 have actually responded um and are directly engaged with the eos support team, acknowledging that this is coming and nobody has indicated any concern with the september 21st date, there's no one raising any red flags that they're not going to be able to hit that date.

A

um At the same time, like I said we're, our team has been directly um engaging with the block producers.

A

Everyone has acknowledged they're either you know getting ready to upgrade already or just waiting for that final release. Last we checked in so now we can. Let them know that that final release is there and and we'll continue tracking as we go. um Eos nation is already upgrading, we've upgraded everything except we just have one ship node and our diffuse node to update to final release, but otherwise everything's already been updated.

A

So looking good on the communication plan, I don't know randall. If you have anything, you want to add.

C

Yeah so yeah you're on track, um so basically we sent 345 emails and 104 answered. 241 has not um have not have not answered yet. um We've been able to um talk to some of the major players.

C

We've established that direct communication and some of them are actually um prepping for uh new upgrades, and um I think so far so good. We don't have any um red flags at the moment, but um each um um stakeholder or project manager that we've uh encountered has assured us that if they have problems they will reach out to us. So so far, so good.

B

Great good question- and um I I just wanted to know if there's been much like discussion or feedback around the deprecated state history and whether that's kind of come up as any concern from any of the respondents.

C

Yeah so so far we have not had any um question come.

D

C

Yet so that's something that we are going to be looking out for.

A

I think we have on the on the bp side of things we had heard. There is at least one bp who was just running it, but again they haven't indicated any they're aware of the timelines. They haven't indicated that that's going to be a problem.

D

A

Were a few that came.

D

In the channel saying the p1 deprecation was the trigger, but I don't think in the last week or so I've seen many, but there.

E

Have been a few just to add to this daniel uh apologies, I I need to go again, but I wanted to to drop this. While I was getting the emails that you guys were updating this particular part of github.

E

What I recommend is before september 21st, uh perhaps a few days before you start holding, go no go votes as we used to do before that way, more so specifically to the top 21 to ensure that uh all of the top 21 basically give a go uh or as close to the 21 as possible, give it go uh before actually activating on september 21st, and then those could be uh yeah.

E

Those could be leading up to the 21st and then that way, if it's not the 21st, for whatever reason um the community is surprised at that, and basically these calls are public, as we did before. Maybe 1300 utc, 0-100, utc type of thing.

A

Yeah 100 so in the background, we're going to continue engaging them, one-on-one and then leading up to it. I agree so we've got including today, five calls remaining before september.

A

The fifth one is on september 21st, so we've got um you know exactly four more meetings after after this one um for the 1.8 upgrade, we started getting eps joining the calls, I think in the last couple weeks, so we'll aim to do the same this time, but in the meantime, keeping our tracker updated and- uh and I agree I think, it'll- be good to get as many of the top 21 on this call as we lead up and and participating, go no go.

E

Yeah, I think randall. If you want to mute yourself. uh Thank you very much daniel and I have to go again cheers guys. Thank you.

A

Thank you eve. Take care uh all right, any any other anything else to add on the communication strategy.

A

Awesome and I'll I'll keep connected in the background with with randall, um and maybe we can get some tracking going as well similar to what we got for the bps.

A

um We can identify kind of the the critical ones we really want to make sure we get updates from and get a status for each of those as well.

A

So I can touch base with you offline on that randall um testing on jungle, four, let's have a look and see what our trusty validator is saying.

A

So we've got um here: we go folks on leap, um anyone to report anything anyone have anything to report. So far on how testing's been going.

D

Seems to be going fine on jungle; they don't really change much. I guess we'll wait on the new system contracts and try to push those as soon as they're out.

A

Cool, I don't think we've so we rc 2 has been released. I don't believe those have been deployed. Is there value in doing an m sig for rc2 on jungle or waiting for rc3.

A

Not sure if anyone has an opinion there.

D

From the hurting of cats, I'd say wait on rc3, but I don't, I don't think, there's any benefit from deploying one version and then laying another person right on top of it. But I don't know.

A

A

Yeah, are you guys looking for any feedback on rc2 right now, I think on jungle, yeah rc, one version of the system contracts has been deployed.

B

um I I think honestly, operating with the most up-to-date version would be beneficial.

B

um I don't think that there's any big changes that we're of course concerned about or anything, but um if it's not too much pain, I'd advocate for it, but I don't know if I have full perspective of just the level of effort to make that happen.

D

I mean if it's coming out in the next week or so you know we could hold off, but I know you'd said no definitive timelines or whatever, but.

B

Maybe we should clarify, I might have misunderstood, we'll have an rc for cdt in dune, um I'm not anticipating any uh changes to the eos system contracts.

A

Okay, in that case, let's go ahead. That's what it was right in that case, that's good, good clarification. Thank you. um So we'll we'll ask crypto lines to put it up an m sig then, for the is, I guess that needs to be used right, michael.

D

uh June and cdt those are just developer tools and stuff, like that, I mean they'll start compiling contract, maybe with the new stuff, but but.

A

For the system right.

D

Yeah well y'all, haven't rc1 is the latest version.

A

I believe I saw rc2 came out um in the.

B

Middle last week I can actually get a link for that too I'll grab it for you guys.

D

Rc2 push jungle and kylan, probably.

A

Yeah, so we can, we can work on that this week. uh I posted that link to that in the jungle uh group, but no, there was no kind of action item to deploy it so now that we all agree that that would be valuable. Let's uh we can get that moving.

A

uh Excellent and I see we've got thank you. Steven for sharing the link to system contract rc2.

A

What's the right terminology here deploy system contracts.

D

Yeah 310 rc 2. and I guess we'll need to do that on jungle and thailand. Yeah.

D

And no, it's even no major foreseen issues or rc3 on the contracts. At this point right reserved to change your mind.

B

Yeah there's there should be no real issues. um I I'm like 99 confident that the only changes here were just any accommodations to really observe this as eos system contracts, so the the renaming process, basically um so nothing crazy inside of it.

F

Yeah, the only the only thing that we did there was sort of the rename and use leap and cdt from the antelope repositories and get rid of some other naming things that were in there and then fix a bug where or use the ricardian contracts that were available from the thinking deals nation. um But that was really pretty much it right.

D

There so yeah probably push those through finalize them up, run them for a week or two should be fine.

A

Yeah cool anything else on testing on jungle, in particular.

A

All right, let's move on, then we can uh share some updates on kylin. um Thank you, denny and michael for all the work you guys have been doing to get kylan in good shape. So now we've got power up configured.

A

uh All the protocol features have been activated activated, including 3.1, crypto primitives uh and the latest system contract. Actually rc2 is already depleted.

A

So that's what we're running on kyling. We just need to do the same on jungle.

D

A

And I can confirm.

D

It forks out any old 2.0 nodes forgot that my snapshot node was on that and I think it actually forked out some other other nodes as well that we saw but, as expected, you know when we activated it if you weren't upgraded so um but chain kept moving and we're at least 10 times closer to functional.

A

Excellent yeah thank.

D

You I gotta say it's all danny danny's doing all the work.

A

Well, thanks for uh keeping engaged michael and signing those m, zigs too, we need we need uh yeah. We need an engaged uh bpm get those m6 signed. uh Denny. Do you have anything to add on that.

G

Yeah um yeah, so all the the protocol features are going to be the what we're going to be proposing for eos mainnet so right now, this is essentially the exact word plate for what will be deployed on mainnet.

G

It's essentially, you know activate all the protocol features so for mainnet when we do the upgrade it's going to take the list of all the protocol features, do one big m sig to activate all and then uh whatever version that we're at for the system contract. Whether rc2 is the exact you know, is the final release or maybe there's a future one um to deploy the system contract. So that's the only two things. Of course eos mainnet already has power up configured, but uh those two are exactly what we're going to be doing for mainnet.

G

So everything seems to be working on kaileen. It's um yeah right now, we're just ready for the upgrade. If, if the system contract does not change, but I think if, uh if everything is pretty stable right now, everything's deployed and uh yeah, I think we're ready for uh for the upgrade.

A

Yeah, thank you for the update, denny uh and, and we haven't seen any everything's stable from what we can see on on kyla no stable.

G

Enough, I think I think there is you know you know, people that need to upgrade that's more of a self. You know uh infrastructure issues where oh, I forgot to upgrade this or I forgot to you know my snapshot or I forgot defuse or whatnot so, but I think it's now like the chain itself is good. It's just making sure that you know everybody has those updated nodes within their infrastructure, um but um as far as the the system contract the chain itself, uh all the protocol activation.

G

Those all seem to check out now. It's just personal infrastructure, tidying up and stuff on behalf of all the vps.

A

Excellent, thank you, and I see patrick from aloha, saying apologies, the aloha monitoring being down on on kylin uh no problem. Thank you for for joining. I guess. Do you guys have any any plans to update the aloha monitoring on kylin and.

H

Beauty yeah. Definitely um you should have it fixed today. That's the goal anyway. Okay, just.

D

H

Yeah, basically,.

A

Yeah awesome great all right, so look looking positive um testing all around.

G

Oh just one more thing I wanted to add um so in every previous system contract that we've done, because we were using block one's repo. Previously, it did not include ricardian contracts like all of everything that has to do with eos mainnet. So thankfully, in this release, bps can actually point directly to the eos network foundation, eos system, contract uh repo, and that includes all of the mainnet recording contracts.

G

So people can build directly with that repo and not a custom repo that we had to do before, where we kind of had to fork block one's uscio system contract and then include those those recording contract like reg produce and uh and the other ones. So now everything is bundled in in the same repo that we're going to be using. So that's really great um people can just directly use that repo and not uh our forked version of the system. Contract.

A

Right without everything you need in the official eos nightmare.

G

A

Repo, as opposed to the eos nation, forked repo yeah, exactly that's great, that's great good update. Thank you. Denny um platform support. I don't know. If there's anything, uh I guess dune rc2 was uh scheduled to come. I believe that did happen. Is that right.

B

Yeah, that's right and, um as mentioned earlier, we'll likely have an rc3 on that, just some small things that we want to tidy up, but not anything that impacts our timeline. Great.

A

Okay, um that's all I have on the agenda. Is there anything else anyone wanted to raise while we're all here.

A

Okay, well um so yeah we'll see you guys in the test net chats we'll we'll get jungle updated to the latest system contracts, we'll keep testing we'll keep coordinating with eps and- uh and you can find our you know- our tracking is all up open on github here. So we'll keep updating this as we go and uh we'll have another update on our progress next week.

B

I actually had one other quick question, which was just update around any of uh the interviews that we were doing, or I'm sorry surveys around uh the way that chain base is being consumed by some people as well, as um I think that we were just interested in a little bit more feedback around um like the hole punching for the block log splitting we were doing.

A

Yeah, so we were we held off on sending that because we didn't want to disrupt the main we wanted to get everyone really engaged on the uh upgrade guide this week. Right now that that's out, I think, maybe that's something actually good that you brought it up. um Perhaps now is it now that that is out and we've started engaging in people. It seems that people are aware um we can. We can probably send that out this week, um so the the block log one was the priority. If I recall correctly, that's.

B

Right yeah, so we'll start with that.

A

And we already have the the question drafted ready to go so I'll, just work with uh with randall to get it sent out in a survey excellent.

B

Thanks so much.

A

Awesome. Thank you. um Unless there's anything else, we can end it there. Thank you. Everybody have a good day.

H

Thank you. Thank you.