Everything EOS EOS Leap Upgrade Group, 20 Apr 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: EOS MANDEL Meeting #11 (April 20th 2022)

Description

All EOS Mandel Meetings : https://github.com/EOS-Nation/mandel/issues
#eos #mandel

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.

Summary
In progress action items are on track:

#55
Pomelo team is working on a survey to Grant applicants to gauge impact of dropping official Mac support in Mandel.

#41
2 more engineers have joined ENF to work on Mandel, for a total of 4.
A process has been established to prioritize scope for 3.1 and 3.2 and items are being sorted.

#48
@cc32d9 has presented a draft set of questions to include in the survey. Feedback from the working group was to consider adding a question asking if subjective billing is enabled.
EOS Support has prepared the survey to send to exchanges and developers.

#44
@eosusa has upgraded BP nodes to Mandel and is beginning testing
the working group is happy with the number of BPs that are now registered on Jungle 4

Participants (21)
Host: Daniel Keyes | EOS Nation
Matt Witherspoon
Yves La Rose
Jannis (WAX) (Giiaaannis)
Nils Littmann
EOSUSA Michael
Patrick - Aloha EOS (Patrick Burns)
Genie Kim - EOSeoul# NEOPLY
Zack Gall
Max_Cho EdenOnEOS Member-South Korea
Ted Cahall
Rob Genereos
Randall Roland’s iPhone
Corvin (cmadh - liquiid.io) (Corvin Meyer auf der Heide)
junhank | NodeONE
Jeff Werner
swatanabe
ben
Denis Carriere
Henrik - Sw/eden
Brian Johnson | OCI

// EOS Network Foundation //
https://eosn.foundation
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-...
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosn.foundation
#EOS #EOSIO #ENF

A

All right welcome everybody. It's april 20th. This is our 11th time meeting. We talked about platform support how the there's a, I guess- appetite to gay the impact of dropping mac support, so the pomelo team is looking at sending a survey to our group of devs who participated in the mello to gauge their sentiment with a survey and give an update on how we're doing there. We had two new engineers join last week and, if I'm not mistaken and the third one joining today is that right or on.

B

Monday this monday bucky joined, I'm not sure. If he's on the call right now and bresnikov also joined this week, so yeah so we're inside the enf now and we're always looking.

A

B

More in case, you know, people and you'd like to make a recommendation.

A

And we see sam started a list, we were talking about having a priority list of what's in and what's out from 3.1 and what'll be prioritized for 3.2. I understand there was a meeting to discuss that, so we can get an update on that and we can give an update and.

C

That's the account is the one that was non-encrypted. Whoever is the phone number. It's the alert that we're getting from zoom. Okay,.

A

I can't see an option to mute anyone who's gone, but that's okay, they're gone okay, tess mandel, don't know if anyone has any updates there, but yeah we. Last week we reported that all of the rest of our nodes, except our defused nodes, have been upgraded, so we can check in on anything else there so yeah. I can I'll start I'll give my update on the platform support, so it just so happens.

A

One of our new hires, the eos nation, on the pamela team, our project manager, we just hired miranda in a previous life, was a professional survey. Sender. So she's been tasked with looking and diving more into this objective, and there was some initial feedback from the melo team that perhaps the audience will be not quite what we're we might not get the responses we're expecting. We don't have a narrowly segmented like only send to smart contract developers, for example.

A

We could send it to all everyone who created a grant, which is you know, a lot of content creators, a lot of maybe devs who aren't actually running nodes. It's actually a pretty small portion of that audience. That would be actually smart contract developers so we're thinking about what the best approach will be, and so that's something miranda's working on. I should have her recommendations to to bring back by the next call. Maybe we.

B

Can make a few questions in one of them? Do you run a note at all? What type node do you run et cetera so that we can you know what is your primary job description content creator? Yes, contract developer, front-end developer back-end developer. Then we can segment the results. The way we want saying out of these types of smart contract developers or back-end developers. This is what they want, because you know you're going to find most content. Creators are going to say: oh yeah. I want macs and yet they're, not of course, yeah.

A

So yeah, that's the idea, we're also already planning on doing a survey to kind of mellow participants, so one of the approaches might be, including, as part of that survey miranda is going to dive into the objective, make sure we we get what we need mandel code strategy. I added a note in here from matt that he shared in the telegram chat. That's part of mandel 3.1 plans. It's been previously discussed that blocks.log splitting feature is a necessary requirement for the release to be acceptable to the community.

A

Recently, a question arose as to what is the actual requirements necessary for 3.1 related to this feature in matthew and a bunch of other devs views, keep all the blocks dot log in a single file as per nodeos, 2.1 or 2.0. No change which starts from the beginning or based on a snapshot. Number two keeps some recent blocks in one file or optionally, more files at the discretion of developers and removable blocks. With the configured number of blocks passes.

A

This is less features than in 2.1 where it can be split files, move them to archive directory and other things for three. Don't store any blocks at all. This is a new feature, not in 2.1, so if anyone has any opinions, one way or another, there's a couple. Github issues open that you can leave them feel free to share your thoughts. Now, if you have any too.

B

Daniel we're going to hold another meeting at one o'clock next tuesday to continue to kind of parse through these lists and stuff. Would you feel you'd like to join that we maybe there's an oversight, not inviting you we're trying to track all these issues in the eos network foundation manual repository and if you have time at that time, it might be good for you to just join and be directly involved sure wednesday. What time did you say next wednesday or.

A

Tuesday, okay yep, I can do that. Okay, all right. We can move on then, unless anyone has any feedback at this time. I'll take that as a no. Where did we go here, yeah, any any updates you guys can give on so far and on what's been discussed, and I I understand again, the team's already met and has done some prioritizing. If I'm not mistaken, is there anything to report yet or should we save that, for, as you know, after we continue, I think we at.

B

Least agreed that we were going to start by um matt witherspoon querying the github via api and creating a spreadsheet of all of the pull requests that had been issues, possibly that had gone into anything, that's not in 2.0, past 2.0 and then we'd start to categorize those and eventually remove the crop from the list stuff that we know we got that we never will want we'll just kind of mark it as dead and then slowly as we see things that we want we'll start bringing them into the issues list in the mandrel repo and then we'll start.

B

You know, we've started to create some labels in the manual repo for whether it's targeted for 3.1, which will be very few things other than you know, block log splitting whether we want it in uh you know as a 3.2 target, etc. So we've started a process. I think you'd be great to add to that process. I give a lot more experience than say me for that, but it's we're starting with a kind of a breath.

B

First, approach of gathering everything out of you know the original repo to see what are potential candidates for 3132, etc and matt will have that by next week's meeting, so we're starting we're also kind of hanging off the wiki in the mandel repo, some links to things kevin hefner had a file of some pr's and stuff. He thought should be looked at and reviewed, so we're kind of collecting lists of lists right now and then we'll start distilling it down and eventually start tagging them into milestones and different releases etc. Looking forward.

A

To joining next tuesday, okay, what else do we have anything else on this topic? Yes, this is the list where we started from right, stan's list and we're adding to it and yeah great testing mandel. I don't have anything to report from eos nation's perspective that we still haven't done any upgrades to defuse still doing the work on that needs to be done to enable that, I'm not sure if anyone else has anything to report in terms of testing mandel on jungle. I.

D

Just flipped our bp over to it so assuming it's not missing blocks right now, we should be on 305 and I'll start looking at upgrading the ship nodes and then trying out hyperion, but I think cryptolines has already shifted over so, but I don't know what feeds it, but our apis got abused, so you might not be testing them, but they're there, okay, I'll, look it open and back up somebody decided to smash 15 000 requests a second to the jungle mode like a day after I launched them. So who knows murphy's.

A

D

Who even knew they were there but whatever, but.

A

We got well, we got evm now on on jungle for right. I think.

D

It might have been before that, but yeah yeah, okay.

A

D

A

There anything.

D

Needed I mean: are there any worker nodes, or you know like I know, there's some hyperion history for some of the other evm solutions, but I I hadn't dug much into the current evm system. Is there anything usa can run and break? I'm sure, there's things you can break. I can't break anything kevin the test of that, but I I don't know, I think eve- maybe knew a little bit about that or zach.

D

I don't remember which one I saw talking about it, but anyway we're here to run some stuff if correct the new evm and getting it up on jungle. I know it just kind of went, live and everything, but anyway we're here. Yes,.

A

I know that matthew's planning assistant- I don't know- if there's anything related to mandel that needs to be like. Is there any mandela compatibility evm? You know.

B

Now it's going.

A

To be a new environment with evm, really it's just a smart contract shouldn't, be uh I'm guessing uh two separate things in my mind, but maybe someone else is it's: when they're.

D

Not separate that it burns you and I'll circle around more on that, but we will be ready to spin that up, I don't know. Are we ready to try, maybe breaking some things on 305 or do we want to wait until some further updates, like double signing and things like that, just to see how it is because that's what we do on jungle.

A

Yeah, I would say: yeah put it through its paces. It might, in my view, I.

C

Would just put caution like if you know something's not in has a fix, don't just break it to break it, because you know it's not there. So yes break it. If you don't know, what's coming as a fix, but if you know it's already coming as a fix then kind of pointless you're, not bringing new information, I guess.

D

I yeah I'm not even looking I'm looking at things that we know that have broken in the past. You know the I don't know, I'm like double signing like.

C

Yeah, no, that's doesn't it but yeah, so just things that you know weren't included in 3.05 which are being included in 3.1, which you know you'll break. Don't if you do that.

B

Because there is maintenance required.

C

For other people to do so, but yes, it should be fixed, yeah for sure or still working from before. That's.

D

More, what I'm thinking of how, of course, yes yeah exactly so. Yes, that was what I was thinking, but I don't know if the forks or we're trying to avoid, or I mean are we really ready to try to kick things a little harder or are we waiting on like a three one or three.

C

Two before we really run it through some, oh no there's, no three, two! It's three one! That's going to be deployed, so you know, so you want to break it beforehand. Yes,.

A

Are we happy with the number of bps we have on here, or should we still be trying to chase to get more? Did costa rica end up joining? I.

C

Think it's pretty good, because we have a few that are running a few, which is actually better because then it makes upgrading a little bit faster to decentralize a little bit hard for the testing yeah.

A

Okay, so let's call this one, and now it's just a matter of getting bps upgrading and testing great. What else is there anything else that we need to check in on either new items or follow up on some? I guess we're still. I guess not 100 decided on whether mac support is in or out the I know there. You guys had somebody on your team joining that. We.

C

Were going to transform? Did you work on on the questionnaire for the pomelo applicants that were approved so the 145.

A

So I don't know, I guess I don't know if you missed that update at the beginning, yeah someone on our team who's working on that she's, actually professional survey. Sender is what she was previously doing. The audience that we have is not targeted right now to, for example, smart contract developers, so if we just send it to all grant owners, it's going to be mixed results, so we're getting more tailored exploring. How might we respond more more valuable feedback, so it'll probably be a multi-question survey.

A

So that's something that she's working on a recommendation for us right now on how to proceed and make sure that we don't get just junk answers that aren't actually valuable. I'm expecting to get her recommendations today. Actually don't have anything on this call, but I can share what I got in a mandel chat when I have something worth ready to share.

A

Okay, anything else to add to the agenda today: oh yeah, sorry, is there still value in assembling the documentation for docker on mac, while we're waiting for that answer- and I know that we have pushed that out to april 27th because we just had- uh I think.

B

We want uh docker instructions for both mac and windows, and I think it's even okay to make it for linux as well bucky's having internet problems today. So he and I've asked him to join this call each week. He is the person that will do that. I kind of forewarned him that it might come up on the call today and surprise he had internet connection, I'm sure, they're unrelated, but so yeah. I think we're still going to do that.

B

He is saying he will take care of that and normally he'd be on this call to talk about it himself. Great.

A

We also had stan made some progress on, so we've been planning from the start. To do a survey to you know the wider eos developer community, just like we did for the 1.8 upgrade stan, has proposed the list of questions which are essentially just modified versions of the same questions we sent for 1.8, so yeah. So I asked is: would this be maybe an appropriate place to ask that question about mac support, so I see stan stan thinks probably not.

A

This is really targeted to the node operators, whereas our mac question is more smart contract developers. Unless anyone has any conflicting thoughts, I think we can yeah. We can keep those as separate. I would encourage you guys to have a look. Maybe we can look it over quickly here. Are these all useful questions to us and is there anything else we want to be asking, so you know pretty basic: what's your adapt describe, how eos apis are using your project? Do you host your own eos node? What types of api do you require?

A

What public apis are you currently using, which node versions are you using in your own infrastructure? I know 2.1 and mandela are the options.

C

It's silly but relevant right now, when you talk about apis- and I don't know if a few is on the call, no I'm adding whether or not they've enabled subjective buildings, because we know that's an issue and I think that maybe that's the issue with coinbase right now. Anybody who hasn't applied subjective billing right now is still having the issues, so it might be worthwhile, maybe just double check with matthew if he thinks it's worthwhile adding for 3.05. I did ask matthew.

B

About that he was not concerned about 3.05. He was more concerned about the version that was going into 2.0 and he wasn't saying, don't add it to 3.05. That's not what he was concerned about.

C

Yeah, I mean more so when the people answer this, if they say no, they haven't turned on subjective billing. Then we know, and we could do a one by one just to see. Are you having issues? Are your nodes performing properly? Oh, maybe you want to turn this on more so for that, but then.

B

A tuber will still be validation in.

C

3.1, in the same way that it is right now, so it's more so just for potentially resolving issues that currently exist or that they might be seeing okay.

A

I'll run that question by matthew see what he thinks if it's relevant for this stan. Are you on the call? I know you had. These are your questions and you had some feedback on my previous suggestion, because he's not here but I'll, so I'll check with stan to make sure that makes sense. From his perspective, randall has already created in their eos support system. They've created a survey with these questions, they're just waiting for us to give them a thumbs up, they've already collected contacts.

A

I think over 200, something like almost 300 exchanges that they can shoot this survey over to and we can start getting that feedback. I'd like to them. Yeah yeah. I know you guys had fun with that last time. The good news is they've already got email addresses they've already did the chasing people in telegram part that that exercise is behind them. So, okay, that's those are what I had today on the agenda. Anything else all right in that case have a great day. Everybody thanks for joining.

A