Everything EOS EOS Leap Upgrade Group, 23 Feb 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: EOS MANDEL Meeting #3 (Feb 23rd 2022)

Description

[UNCUT] EOS MANDEL Meeting #3 (Feb 23rd 2022) - https://youtu.be/PkkILy10J5M
All EOS Mandel Meetings : https://github.com/EOS-Nation/mandel/issues/37

#eos #mandel

Meeting Summary
ENF is on track to confirm that the upgrade path will be directly to Mandel 3.1.
Mandel 3.1 will include transaction lifecycle improvements identified in the API+ blue paper and implemented by OCI.
Mandel 3.1 final release is projected for end of June, with a testable release by late May.
Acceptance criteria for the transaction lifecycle improvements is in the process of being published publicly.
CryptoLions have started Jungle 4 testnet with B1's EOSIO 2.0.
BPs are asked to join Jungle 4 ahead of testing the upgrade to Mandel 3.0.
Jungle 3 will remain active for the short term.
cc32d9 has identified bug fixes in B1's public repository that can be merged into Mandel and is in the process of documenting them.
EOS Support and EOS Nation are on track with documenting points of contact for EOS developers and exchanges so they can be informed of the Mandel upgrade.
EOS USA has deployed Hyperion to Kylin testnet.
EOS Nation and EOS Asia are coordinating to condition Kylin testnet for Mandel upgrade testing.
Mandel will officially support Ubuntu 18.04 and Ubuntu 20.04. There will be documentation for running it in Docker for Mac and Windows.

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://eosn.foundation
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosn.foundation
#EOS #EOSIO #ENF

A

All right, thank you, everybody for joining today. This is our third check-in call with the mandel upgrade working group. We will start with eve if you have anything to share on progress towards determining our path forward between either 3.1 for everyone or 2.3 and 3.0. It.

B

Seems dan has maybe already skipped 2.3 and is already working towards 3.1. I haven't gotten confirmation at that, but that seems to be the case right now and there's nothing else that I can share at this time. Other than that we are in the process.

B

On the other side of things, though, we are in the process of signing, we should be signing a an agreement with oci today, we've kind of pinned down the scope of work or the api transaction life cycles that should align roughly with the timing, so they need roughly 15 to 16 weeks from start and start with the next week or early march. So that would bring us till you know, beginning of june, to start getting releases and end of june have kind of the end of the releases.

B

We will be sharing through a blog post and through other information, we'll be sharing kind of what that entails, especially for developers what that means. So matthew, darwin and aaron cox have been helping me out, leading that that file. It's part of the api plus blue paper, which isn't out yet, uh but it will be out by the end of the week. So essentially it's a it's an item that we saw that was uh kind of a quick win, fast, trackable item that we could add on to this.

B

That would give value to developers in this particular release right.

A

You said what was the date you said there that we're.

B

Tracking, towards was there which, for the eight.

A

Year, transaction life cycle.

B

Yeah they're, saying roughly, let's say 15 to 16 weeks from beginning of march, which would put us at the end of june, but they end of june, would be where we have kind of a final release, so we would be getting released prior to that. Let's say uh end of may beginning in june. We'll start getting the the first releases do some back and forth some bug fixing okay, so.

A

This is still accurate, ready to start testing in late may. Is it hasn't changed.

B

It might even be a little bit sooner than that for the release candidate, one but yeah you can input. That seems fine and, like I said in terms of actual details, which we will be able to include in this at some point or we'll put through a blog post or something more formal kind of the breakdown of what that entails. And if you want to put those notes, it's the acceptance criteria so we'll be sharing the acceptance criteria widely so that basically developers can understand the technical details of what's being implemented.

B

We should be signing the agreement today, so we've been doing the back and forth for about uh two weeks now and I think we've we're done and we're good with the scope of work, that's being presented so once that's signed, then we'll transform that section, which is already essentially written. So it's just a question of copy pasting in a format but they'll be suitable to share so maybe a week or so. Wait wait before it's needed. Essentially.

A

Done I see you have some updates to share.

C

Yesterday evening we started jungle 4, as you mentioned before, it's on the 2-0 version and smart contracts are 191 1192.

C

The last one was the configured power-up system and it should like be similar like on eos here in the chat in the zoom uh chat. I shared information about access to the jungle for the monitoring. You get information with the genesis file and please feel free to use that if you will have any questions, we'll be happy to answer great.

A

So everything we need to know to connect to jungle and and use it is, is in here is that right, yep, that's right! So what are next steps for jungle? Probably.

C

We need two more block producer to be registered and then we will do upgrade when we will have already like the centralized chain right now. The the old proprietor on our side, yeah.

A

We need to get more bps to register. Do we have a threshold? In particular, we want to shoot for and and what are right now, it's just. Is it just you guys? We started.

C

On our blog producers, but uh when the new block producer will register we'll just what and bring them in the top 21. and.

A

I guess we need a minimum.

C

A

21 that we'd want to participate in this.

C

A

C

The best one we can cover the difference if we will have less, but if more that centralize the chain will be then better. That's.

D

The result we will have it looks like it's 2013, so just spin it up like a normal node and then we'll upgrade it from there another one. We are drawing that yeah.

C

Only not those should be on the two zero third inversion, the last one from the two zero. We will also announce in the jungle test that group uh there will also, probably the zombies, might join.

D

C

D

We're just letting kind of dwindle off into la la land as we relaunch jungle. Four right no need to put any effort into three. I.

A

Think the idea is we want to keep both for the time being. Is that right, yeah.

C

I recommend to keep during like six months the jungle tree, so everyone is able to to migrate to the new chain and, as I know, we will probably arrested this jungle for during some periods, so maybe better to keep still jungle tree to allow other development testing yeah.

A

If you're able to continue running both that's ideal dan, uh you mentioned you're dialing in from the car. It sounds like I'm not sure. If you're able to speak, I saw that you gave an update in the chat about reviewing the changes in 3.0, rc and and you've gone through some of those pr's that kevin mentioned I've. I've added that in the comment here anything to address.

E

I I'm driving right now. I can't really add much more, but.

F

Okay, it's working.

E

Progress there's a.

F

E

Of stuff that that is useful and- and I think we need to move it into mundo, there are some improvements and bug fixes also for usa, commerce, there's some network conditions that michael is experiencing, and there are some bad fixes to that. Yeah.

D

Please get my the eos usa coma bug fix into the code; they they fixed it and it's gonna get dropped out.

A

Okay, so if I understand correct, these are different changes in this release that are being considered to be added into 3.1. Is that correct? That's.

E

Right, yes, there's a list of fixes that block one is doing polish is doing, uh have done right now in public repository. We don't have them yet in in mondo okay, so we need to have a plan for them to merge.

A

And I see kevin is on the line. Is there anything that that you can add on this topic.

F

Sure the mandel was cut from a tag version 2013. I believe. Since then, there's been a number of fixes that are under release 2.2.0.x branch. They didn't pick up because you know they they cut it before. Then those are valid and they would be in a 2-0-14 if a thing like that would happen to ever exist. However, they're not right now and so yeah, I think those should be uh brought in, including one that's actually not even merged.

F

Yet I realized that there was one fix that would that's in two one and two two and develop box that uh hadn't made it into 2-0. So I pushed up a pr for that that has not been merged. It'll, probably be merged relatively soon.

F

I'm waiting for one of our guys who's on vacation to review it so yeah, and then I was planning on and I hadn't gotten around to it, going through all the changes in develop box and developed in two three and two two and two one, which is a lot to try to indicate what I think of those ought to be in a mandel. And I just haven't had the chance to do all that. That's quite a bit of work. So.

A

It sounds like between between you and stan that we're documenting the additional updates that are available and we'll have to decide if we're able or willing to merge them into what. What I guess we're working on for mandela is that right, yeah.

E

That would yeah some bug. Fixes are quite easy. I mean this. This bug fix.

A

I'm guessing yes.

E

I think I think it's just good. It should go to three to zero if it is because right now we have released candidates, so this bug fix would be perfect, for the release is.

A

Anyone from the frackley team able to speak to that, whether that's feasible or what you would need to to have in order to make a decision there and just.

B

To confirm, stan uh and or kevin, you guys are putting that as you've put in the issues right uh under the current repo, so that the fractal team is actually aware and can see. I.

E

Will I will I just went through the list this uh today.

B

A few hours ago, steven watanabe is here if uh from franklin, if he can address, I'm not sure if he can.

G

At the moment, I don't have plans to integrate those into the uh 3o rc1, I'm currently working on recording features into 3-1. I.

A

Guess once we have this, you know stan is in the process of documenting all this stuff. Is there an opportunity to revisit that once we have that documented, possibly.

G

I'd prefer not to.

H

Import things more than once, though, we haven't agreed to purchase 3.1 yet so we do have the 3.0 release candidate and it would make sense that we're asking to have these fixes put into that's. Why it's a release candidate and not the 3.0 finals.

H

It sounds like we need to have some clarity on the scene. All.

G

Right agreed, I am not confident to negotiate.

H

Can I ask kevin heffner a question, please kevin? Who is making these changes in the 2.0 release that you feel that should be included? I mean we trust you're right about they should be included. Are these oci people making these, or are these some remnant block one developers still making some some fixes bug fixes who are? Who are the people that are making these yeah? They were all done.

F

Under block one's dime, if that's what you're asking? Are they months old or are they semi-recent? uh Well, some of them are months old. One of them hasn't even been merged, yet that that one I pushed up yesterday or the day before you know they they're all stuff. That's since the 2.013 release, which I'd have to go, look when that was you know, they're all in what would have been in 2.014.

F

If such a thing would ever happen, I see thank you. I.

A

Had a call with uh randall this weekend we discussed: we've got a pretty large database of dap developers and exchanges and making good progress on getting contact information for each of them. So yeah, randall myself and a couple members of my team are working on populating all of the all the contact information. So that way, when we're ready with all of our materials, we can email, basically, all of them individually we're trying to get uh the official support email.

A

You know to open a ticket with as many of the exchanges as we can and then we can track the progress of those tickets and make sure that they've actually been acknowledged by the exchanges and they're ready to go. I saw that we've got hyperion now up. Thank you, michael. I see that you've got it up now. I see we've got another update here from nat some info from the chat from syed, and we were also, I think, igor, was working on some something for hyperion on thailand as well. How are we doing there? Yeah?

A

I think, that's just like general hyperion updates. I don't know if he's here or not, but I don't think.

D

It was anything.

A

Immediately yeah, so we had you signed up for the short-term fix and igor for the long-term fix, but it sounds like what you've. What you've provided now is is sufficient for our testing needs in the short term. Hopefully,.

F

A

Thank you, we're still, I'm still working, I'm coordinating with the with the folks on kailin to get power up updated. We have to do some work on basically come. What's the list of tasks that need to be done in order to, I think, there's like a number of contracts and things that are behind on kylin, not much progress to share there at this time, unfortunately, but still uh we're coordinating in the background to get that done and for the record.

D

I mean kylan infrastructure block producer-wise. You know, I mean it's, it's a test net. So not everybody pays attention, but there's miss blocks, there's forks all the time I mean it may be a great test for uh examples of what eos could be like. I guess, but I don't know if we want to focus on trying to at least at some point in time kind of getting that back. Yeah yeah.

A

That's part of that's going to be part of that coordination effort getting everyone on there, who's on there engaged and not missing blocks and getting you know, signing the m6 to deploy the contracts and activate power up all that sort of thing.