Everything EOS Antelope Coalition, 20 Apr 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Antelope Coalition - April 20th, 2023 Meeting | EOS, TELOS, WAX, UX Network

Description

In this Antelope Coalition call, the team discusses various updates on ongoing projects and plans for future developments. Topics covered include the Antelope Go-to-Market, Cross-Chain Marketing Group, P2P Peer Discovery, RFPs repository, and more. The team also shares updates on the Wallet SDK, Antler CDT, Ledger App, and Instant Finality projects. Watch the call to stay informed about the latest developments in the EOS ecosystem.

00:04 Antelope Go-to-Market Cross Chain Marketing Group Update
00:45 Coalition RFPs Repository
01:26 In Progress Column
02:22 P2P Peer Discovery
08:42 Instant Finality
12:01 Wallet SDK
14:42 Antler CDT
15:00 Ledger app support

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.eosnetwork.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 #Web3

A

All right. um, so first for the new agenda, items.

A

Um, funny enough,, the first one, the antelope go to market, cross chain.

A

Marketing group update that was requested by lucas,, but lucas had,.

A

Um, last minute reason for not coming.

A

So if nobody else has insight to this,, we can pause this.

A

Till next week, when lucas, is.

A

uh, so throw that out., does anybody have anything to add to this topic?.

B

Uh,, not me., not me.,.

A

Okay, good. on the second new agenda item,. This is just informative.

A

The old rfps were being published in the e n, f github repository.

A

There, of course, is an antelope one.. We have created a coalition hyphen rfps repo, and we have copied all of them. Over.

A

And going forward, we're gonna put all of the coalition rfps into the.

A

Coalition github home, uh, for reference.

A

I mean, you should,. Everybody should be able to find it when you go into gith.

A

I'll pop this up on the video,. So if anybody wants to see.

A

This,, you can go directly there.

A

All right. so I'll close that out.

A

all right. moving into the in progress column.

A

So the first two again, uh,, we'll start up after the release of currently the, uh,.

A

Rc three has been out for about two weeks.

A

there's been. major rumblings about it., so tentatively, uh,. It might go into production on the 25th.

A

Again,, I'm hoodie at asterisks with that, because everybody's been through the release process, before.

A

um,, but things are looking good.. The reason why I bring that up here is because of course, as we've.

A

Been saying for weeks, that will open up capabilities for some of.

A

The e n f resources to be able.

A

start documenting the desired requirements for both of those two items.

A

Uh,. The third item is the p2p peer discovery.

A

Now, earlier this week, y, you had a meeting with sudan, um, and I will.

A

Actually, turn it over to you to kind of give an update on some of.

A

The discussion, particularly around how they set up the milestones.

C

So, um, so yeah, so there, there was, um, uh, some issues, with, uh,, the way.

C

That the, the, the milestones were set and, uh,, I guess,, I guess by, um, uh,. You.

C

Know,, like the,, the consequence of that is that we might want to,, um,, um, kind of.

C

Review our process as well to make sure that, uh, when we do, um,, when we take on.

C

Rfps like this one that touch the core code.

C

uh,, we ensure that the milestones are, and probably any, any rfp that.

C

We, that we take on actually, uh, we,, we wanna ensure that milestones are.

C

Correct and can be, um, uh, verified independently and, and objectively.

C

The issue here was that they,, they just went with the technical requirements.

C

As the milestones, and that's not,, that's not really appropriate. After.

C

Tell that in the, um, telegram channel..

C

So following that, um, discussion that we had on tuesday morning, um,, we agreed.

C

That, uh, the food and team, with the help of fuman, would be, um, revisiting.

C

The milestones, essentially coming up with a new calendar of milestones.

C

The remaining three or four milestones of the rfp,, and these would follow,.

C

Uh, the template that I suggested,, which is essentially, uh,. You.

C

Know,, like defining unit tests and integration tests, are required.

C

Then coming up with, uh, a code implementation that meets these,, uh,, requirements.

C

and then, uh, successful pr to the code base as well as deployment to, uh, test.

C

Net, main net and, uh, so on and so forth.

C

so, of course, like this is,. This is a bit kind of maybe.

C

I think, like something: like, um, 40% of the project, was, uh,, the.

C

Milestones were already awarded then., so we, uh, gonna convince the new, um, template into the last remaining three.

C

But that should put back the, the project on track. And, uh, make.

C

It, make it verifiable after that., so we're expecting to get these updated. Milestones, uh, over the next few days.

C

So, probably on the next call next week, uh,, we should be able to take a vote.

C

On the updated milestones and then, uh, get back on track with the project.

C

Any questions or any comments?.

B

No,, I guess this just highlights kind of like what you had put in your messaging that, um,. We need to, as,, as we do out more rfps,.

B

We really need to position them.

B

uh,. We talked about this on multiple occasions,, but to have a mechanism.

B

To be able to validate the work.

B

um,, but I'm not sure we'll be able to move away from this specific example.

B

Because it's broken down and if I understand it- correctly, different technical, components, great. that component's done., but there's no way to verify if it works,, because as a standalone, it's not.

B

Anything, it,, it requires them to be done.

B

Exactly. um,, so I don't, I mean it's, and maybe I missed it,, but I'm not.

B

Sure how we'll close that gap., it's still,, it's still doable because,. I mean, uh, uh,. If we look at the, the.

C

Template that I suggested, uh, this,, this kind of gives you a way to, um, to,, to.

C

Approach just about any, uh,, any kind of component or any, any project, uh, any.

C

Kind of more or less standardized fashion..

C

The problem here is the,. The milestones were literally the technical requirements.

C

So we had like, you know, uh,, something like 10 technical requirements for the, uh, for the rfp., and these are kind of characteristics that the final solution must have.

C

But they, they don't,, they don't,, they don't represent, um, anything tangible,.

C

Uh,, taking an isolation by themselves., yeah,, exactly., exactly., so,, um,, but, uh,, you know, lesson: learned, uh, for the next ones, we'll make.

C

We have these objectively verifiable, um, kind of checkpoints, and, um, and uh, yeah,.

C

The template that I suggested,, I think,, I think, works for the majority of the cases.

C

A

Any, any questions on that?.

A

All right, perfect. so again,, hopefully we will.

A

yet that the new proposed milestone schedule, again,. It was also made clear to.

A

Them that this should not change the cost., and just like we've done on several other projects, uh,, you know,, sometimes the.

A

Schedule changes will bring it back here..

A

You guys will vote. If you are voting in the affirmative,, then we'll go.

A

Back to them, and, uh, re-baseline, the remainder of the project.

A

What is their, just before we move on from that one,? What is their position on that?.

B

I mean, is their pushback, is it,, are they understanding,? Do they understand.

B

Kind of the challenge that we're facing?

B

just just to get a sense.

C

Yeah. no, they were, uh,. They were very, uh, understanding,. I think,. I think,.

C

I think it's kind, of, it's,, uh, the,, the mistake kind of came from them.

C

I mean, we didn't,, we didn't catch it,, but uh,. They are the ones who suggested these miles. so,. I mean,. Obviously they, uh, they, they,. They recognize that, uh,. They.

C

Might, they,, they should have been clearer and they should have, uh, spent.

C

A bit more time defining these and, and they understood the, the,, the challenge.

C

And I mean, uh, bear in mind. I wanted to make sure also that, um, uh,.

C

You know, like this,. This resulted in a high quality code, submission.

C

So I, I was,, I was,. I was a bit..

C

You know, uh,, tough on them as well. and,, and,, uh, I,. I didn't want to approve something, uh, before we, uh,. I had a.

C

Very good, uh, you know,, like confidence, and, and, and the quality of the code.

C

So, uh,, so I I I, I,, I told them and they were,. They were understanding.

C

And I think, I think,, I think they, they,. They will produce good code.

C

Um, uh, as well.. They also requested a little bit more, uh, kind of guidance,, but that's,. That's.

C

Gonna, that, uh, I'll be happy to provide them. With, with, with that guidance.

B

Awesome. thank you.. Thank you for that.

A

A

so, uh, guil,. Why don't you flow into, uh, in instant finale.

A

I believe I b c is kind of paused unless you have an update on that as well.

A

Uh, the only thing on I b c is, uh,, the last time I checked there was.

C

Still, I think, two or three signature, uh, is missing on the, uh, s and six.

C

So maybe jesse, if., if you don't mind, uh,, taking a look at that and, uh, and see if.

C

This, um, uh,: this can be completed.

C

that'd, be great.. That's for the wax, uh, configuration.

C

and then, uh,. Once that's done,, lucas, requested, um,, basically, that we pause,.

C

Um, that we, we,, we leave it in, uh, uh, disabled state until early may.

C

I think they add, uh, some, some,, some marketing, uh, material.

C

That they wanna produce to, uh,, align with the official launch.

C

So, but otherwise, otherwise, like,. I think that's the only thing that's left to do, uh, on your side., the yes. was approve the thing last week, so,, or only this week.

C

So, uh, it's,, it is just, uh,. Just tell us left.

A

Was there, was there,? Is this the second mc, ellos?.

B

Did wa the did? Did one of them?.

B

Uh, yeah. redone?.

C

No. so, so, so,, yeah. the,, so the, the,, yeah, the,, the first one I, uh, I, uh, made a mistake.

C

I essentially set the, uh, authorization request to e sio o active instead.

C

Of, uh,, the actual contract,, which is I b c,, proof, active, and cleos re.

C

Uh, cleos allows you to kind of map these, uh, air emissions,.

C

But then say, contract doesn't., I'm sure we, I,. I know I've done that fast, so, yeah.

B

Okay., I just wanted to make sure, because I knew that one had done, I,. I knew that one had.

B

Gone, had been executed, but, uh, okay.

B

make sense? uh, we'll push the, the rest of the people.

C

Get those done. thank you very much., uh, and uh,. That's it for I b c.

C

no, uh, no additional.

C

um, uh, with regards to in instant finality, last week was the.

C

End of the, of the evm sprint., so essentially this week, uh, yf is, uh,, basically,, um, uh,, back to,, uh,.

C

Uh, in a position where it can, uh, review the work that has been done.

C

So there's, uh, still a bit of, like,, quite a bit of catch up to do..

C

It's been probably like something like two or three months, uh, of work.

C

Uh, much, uh, review from the nf engineers.

C

So this is what is taking place. uh, this week, we're expecting that, uh,, maybe next week or the week after that,.

C

We'll be back basically in cruising speed.

C

uh, they'll, be, uh,, caught up with the progress that we've made.

C

Uh, uh,, we have,. We have one pr that will, uh, go, um,. That will be.

C

Presented, probably over the weekend. um, and, uh,. Hopefully we gonna get at the end of the two or three week,.

C

Uh, period,, we should be able to.

C

uh,. I complete three of the milestones of I b c and, uh,. That would put.

C

Us in a position where we would be preparing for a public, uh, test, net.

C

Um, for the public test net milestone.

D

Uh, that would come probably, um, early june.

C

That's my estimate., hopefully if,. If all those look,.

C

Any questions on, uh, intentionality.

C

All right., so that's it.,.

A

Moving on. uh, aaron want to give us an update on sdk?.

D

Yeah, sure. uh,. Today we will have, uh, everything released in kind of an o four state,.

D

Which is kind of the next major bump up in terms of, uh,, our early.

D

Releases that are going on right, now., um,, a lot of the.

D

Milestones are now completed., with this release coming out, today, we'll also be pushing the next.

D

Milestone into the review phase.

D

um,, we have about 95% of the next milestone done as well,, which is, um, part.

D

Of all these releases that are coming out., it's hard because there's so many individual components to this to.

D

Talk about it at a high level. um,, but this release itself will provide a pretty stable interface for.

D

Web application developers to drop wharf into existing applications and.

D

Use the wallet adapters that we have available, as well as do all the session.

D

Management and everything they need to do.

D

um,. So in terms of development, uh,, the session kit itself is, entering.

D

Kind of a stable phase and we're gonna continue to improve it as.

D

Well, as continue to improve the uis., but this is a good base level. We feel.

D

Um, development,, I think I mentioned this last week,- is shifting towards.

D

The contract kit,, which is the next kind of big development, milestone, and.

D

That'll be probably ready in june, if not.

D

Um, we have a lot of website progress happening with documentation. That's.

D

Going to explain how all of this works.

D

um, and we're just continuing to engage with new developers every week, as,.

D

Um, you know,, new people are trying it out, finding how it fits into their.

D

Applications and maybe where it doesn't, and then kind of taking that feedback and.

D

Trying to apply it back to the session kit and how we can improve that.

D

Experience for those types of situations., so all in all, uh,, we will have, like I said, the submission.

D

Of the next milestone, today.

D

uh, we'll have the progress report coming out this week, and then.

D

I'm going to be personally missing for the next, maybe two weeks, or.

D

Um,, the team's gonna continue to be working..

D

I will have them monitoring kind of telegram or whatever,, but being.

D

Kind of the public voice of all of this, uh,, my voice will just.

D

Be not as loud as it has been., so it's about where we're at.

A

Thank you for that. any questions. For,.

A

All right. moving on. uh, antler c d.

A

as previously mentioned, uh, the work is done,. It's tied to the release and.

A

I mentioned earlier, um,, the tentative date or that release is, uh,, the 25th.

A

So, hopefully, by this time next week, knock on when we will.

A

Have a different status on this.

A

uh,, the last one ledger: app, uh,. We are reaching out to them to get.

A

Those spinal details on the webpages., as I mentioned last time.

A

um, other than that,, there's no update on this.

A

Uh, any other questions about any of the topics today and or.

A

Are there other topics we want to cover in the remaining 42 minutes?.

A

See what I did there?, I pointed out. We had 42 minutes to get back and an encouraged volume you.

A

To not say this is wonderful.

A

all right. um,. If that's it, um, everybody have a great day, great weekend.

A

Talk to some of you possibly monday.

B

Sounds a good one, guys. sounds good,. Everybody. enjoy your weekend. bye-bye. bye-bye.