Everything EOS Antelope Coalition, 4 May 2023

Previous Meeting Next Meeting

⏯

youtube image

►

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

Description

In this conversation, Antelope Coalition stakeholders dive into various aspects of Antelope development, focusing on P2P milestones, documentation improvements, issues with snapshot file extraction, and potential solutions. Join them as they discuss practical use cases and share valuable feedback on enhancing the Antelope ecosystem.

00:00 - Introduction
01:15 - P2P Peer Discovery
02:55 - Update on EVM and Web3.js Support
05:36 - Antler CDT
07:10 - Marketing and Communications
13:53 - Upgrading Chains and Interoperability
27:54 - Status Updates: ENF, P2P Optimized Transaction Propagation, RAM Limitation Fixes
28:19 - Antler CDT Release
28:32 - Instant Finality and IBC
31:45 - SDK Update
32:07 - Ledger App Progress

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 #Antelope #NodeAntelope #Diffuse #BlockchainDevelopment #SnapshotExtraction #AntelopeTalk

A

All right, so, uh,, I'm gonna, kick off today.

A

we've got, um,, the p2p projects, uh, revised schedule that yon worked with them.

A

Uh, the team about, uh,- you can see this on the screen.

A

Let me explain what you're looking at. at the top. here are the five milestones in the contract..

A

You can see that they've mapped to these.

A

requirements, and here's the date, and the first two are already done.

A

But as ome explained, uh, last week, and we don't have to go through all of the details to go, watch it,, but it was difficult, uh, validating these individual requirements.

A

So, uh, working with the team,, they came up with sort of breaking things, down.

A

And this middle part was suggestion by gion, but then,. They reconfigured that into this bottom part.

A

So, essentially we're looking at revised states here you can see the previous description. Is, uh,, there's a correlation,, but it's not exact.

A

And so what we're saying is the next milestone? Three would ha would be producing standalone code that passes unit test.

A

Et cetera., you guys could read this.. I don't need to read it all: out. um, and then the, the one after that, milestone four and then the final one, uh,, the milestone five.

A

Does anybody, like, the last time we've done? This, I,. I think this group sort of entrusted the working team to get into the, the nitty gritty of which, you know, and yo. Clearly did.

A

Does anybody have any questions on this, or do you think we should just go ahead and formally vote and say, yep, we're? Okay, with this schedule?.

A

Uh, either way is fine. you guys. Let me know what you want to do.

B

Uh,, just before we, um,, we take a decision on that.

B

Um, there's also just a,. I think it needs to be rewarded,, but as to, uh, to be understood.

B

Um,, the deployment of solution to main net is more of a,. You know, like,, when they re,, when when we agree that the solution is ready to be deployed.

B

To main net., that's when that milestone is, um, is, is due and understood.

B

Uh, and then the,, the chains can decide when they update, uh, to main net.

B

We're not, we're essentially like we've done for other similar things.

B

We're not forcing the, the, the, the, the, the chains to update at on any sort of schedule.

B

Uh,, but we're not trying to hold back the milestone payment on something that's completely outside of the control of the, um, of the team.

B

So typically, this is,. This is handled more by the end of sla and bug. Fixes, period.

B

So we, we would normally also allocate a larger part, uh, portion of the, the milestone payment to that one,, because, obviously that's the one that, um, we're,.

B

We're,, we release them of their obligations once we, we,. We reach that milestone.

B

Uh,, so we wanna make sure they still have something at stake.

B

They'll just run away after delivering, uh, code that doesn't work.

B

So that part was outside of my mandate.. I was not, uh, privy to the financial discussion about the payments.

B

Um,, so I don't know what, what size of payments are,, but essentially like the,, the,, that, that,. That's how I would.

B

I,, I would invite you to kind of,, um,, consider the, the,, the decision, uh,. This deployment solution command net is a, uh,, let's say a workable, uh, version of the code.

B

And, uh,, it is to be deployed on each chain's, uh, own schedules and independent of paying the contractor.

C

That wouldn't normally be the case, right?, that's what we did for I b c as well..

C

It's not I well correct., there's present not really on van. yeah,. It's not really on van to ensure that we deploy.

C

that's really on us., so they did the work. Regardless of whether or not we deploy,. I think what we, uh, agreed on for I b c anyways is, um, deploy.

C

Or I guess what I would suggest for this, if that's not the case, deploy what they have on jungle.

C

So we have one location where we deploy.

C

everybody: agrees, okay, it works, it's good..

C

We've got what we need. then, uh,. We make the payments and then as long schedule on each chain. That is completely separate.

C

Exactly., do you agree with the, the sla so that we keep, though the sla bug period fixes?.

C

That would be separate. plus. That would also be,. I guess, maintenance, just generally.

C

Each of our chains are slightly different., so if there's some kind things to adjust,, I would imagine that that would be, uh, found in milestone five as well.

C

D

Yeah. I have a related question to that,, which is, um, uh,. Well, first, I'm curious.

D

I'm curious, uh, if,, if this,, if we are,, if this is on track, um, per this schedule, uh, for, for the.

D

The july 20th step. and then, um, along the lines of what, uh, of what eve was talking about,. What is the, is the end of,. I assume that the end of the sla is actually triggered.

D

By how,, by being a month after the, after the, um, deployment to main net.,.

D

Uh,, but I want to verify that and, and I'm curious about what the process,, what the understood process is. For.

D

The bug fix period. is that a year? is that,. Does everything have to come through antelope or can, can the, any of the coalition chains, um, yeah, I mean, uh,. I think it's a very good question.

B

And, um, there's also another thing to be, um, kind. Of, I guess, factored in is the, uh, planned release cycles of the, of the envelope cordez.

B

So essentially like the, um, um,, this has been maybe discussed a little bit on previous calls,, but just so that, um,. Everyone is aware, and, and feel.

B

Free to correct me, uh,, maybe dead or jeff. If you have,, uh, if, if, if.,.

B

Yes, sir., I'm not exactly right about the details, but, uh,. The general idea is to have a, uh, release cycle where there's a major release in march and a major release in.

B

September, and then, uh, releases where, um, uh,, there's a break in consensus.

B

These are set to happen more in september, like hard, forks and soft forks that don't require necessarily breaking consensus are set to happen. Normally.

B

In the march release. uh,, this one here is not a, a change. That, uh, would break consensus.

B

It's only a, uh, configuration that, uh, operators would be, uh, enabling.

B

Um, the,, this being said,, I mean it, uh,, a non breaking consensus. Change can be added to the release cycle. Of, uh,, uh, of september.

B

It doesn't, there's, uh, cause any issues., but the other, the, the,, the opposite is not true.

B

like the, uh,. If you are breaking consensus,, then we try to keep them on the september. Release.

B

Um, so here, one way or another,. It seems like for this to make its way into an official version,. That would be the september release.

B

Uh, so there might be some, um,. I guess, uh, issue with having a, uh, an end of sla fixed that comes before that release.

B

Because that woodman, uh,, you know, that doesn't really leave any one, much chance to experiment, uh, with, with real world conditions, as opposed to, um, to testnet conditions.

B

So, I,, I don't know how guys feel about that: if, uh, if,. If you're, okay, with, um,, it's a,, it's a relatively simple, um,, you know, like,, uh, uh,. I guess like, um, feature that gets added. That.

B

Doesn't really impact, uh, the, the, the, the core code and can be disabled if there's any issue.

B

Uh,, so I don't think the stakes are too high..

B

I don't,, I don't personally mind not having, uh, the, the,, the sla um, you know, extending past the, the release of that version.

B

It can be tested, um,, on, on,, on a testnet.

B

And I think, we'll, we'll have all the information that we need to have,, but we just want,, I think we,. I would still mention it, uh, just so that you guys are aware.

B

If you feel a bit more reluctant, um,, there might be a good reason to push that, uh, end of a silly date to say october or november,, where it has a.

B

Good chance of being deployed in the wild, in real production, environment.

B

And, um, uh, sexual,. If the team is okay, with, uh, with,, with waiting for their final payment, um,, delaying that by a couple months,, it might be worth it for the guian consider.

E

C

Go for it, douglas.

D

Okay, thank you. you,. You anticipated a couple of my follow up questions,, so thank you.

D

Um,, I guess the only thing that's unclear to me: is, uh,, you know,. We do need to figure out how to co how these would be coordinated. With,, um,, with,, uh,, core releases and the core release schedule.

D

I don't understand how deployment of a solution to main net can be done in july.

D

If we aren't,, if we aren't, including this in the.,.

D

Into, into the core code: until,, you know, until september though,, correct.

B

That was the, uh,, yeah, cuz uh,. What I was saying, um, the deployment of a solution to main net,. That really means more like the,. The solution is ready to be deployed to main net, uh,.

B

By a chain, for example, that would want to run the, the, the,, let's say like the dirty build.

B

That is not a, an official release,, but it's still works., it's still there. it's just not been, has not been packaged into an official release.

D

Nobody's gonna do that.

D

None,, none of our chains will deploy to our main, to the main net,. I don't think.

D

No, I,, I wouldn't, I mean,, I mean, I mean,. I would not, no,, but we would remove deployment from main net as a condition for payment.

B

Right, right. or yeah.

C

Yeah., that's why,! That's because they can't control that., neither can we.. So the main net deployment component,. I mean, you could just delete that and the rest remains the same.

C

Um,, what we would need to check,, I think, is in the language for the milestone, five.

C

Is it one month after deployment to testnet or is it after a period of time after deployment to main net?.

C

Uh,, we also can't just withhold funds for an extended period of time, because we are not ready to deploy a solution. That's not,, uh,, fair for them. Either.

C

I agree. agreed., I agree.

B

Uh, the, the, the indication that I have, uh, from, from the court devs and from the vps. I've talked to and like, kind of kinda like driven by.

B

Precedent,, like typically, um,, it,, these,, these, uh, releases are adopted.

B

Yes. mean that a month, give or take after they're released.

B

Uh,, so that's kind of the general, uh, like, seems to be the general time that takes consensus.

B

That building exercise takes one month and then, uh,. They are adopted.

B

So,, so that gives us, if, if that would probably be something like october and then, uh, uh,, you know, like a, a one month period after that would put us in november.

B

So that's still a few months, uh, further.

B

um, for the,, the final payment.

B

uh, for me,, like I said,, I'm very comfortable with, uh, deployment testnet and against douglas point.

B

Uh, I ux would not mind deploying a version that is not an official release if there was a, an advantage of doing that.

B

So, so, uh, maybe,, maybe you guys don't wanna do it, but from, from my end, that,. That's totally fine if, uh,! If I didn't mean this being you or anybody else,, my own, so might help personally.

B

Right. but, uh,, this being said,, I would still,, I would still say, uh,, I would still say, like the,. The safer, safer route would be to wait. For.

B

Uh, a main net, probably yes,, uh, uh,, as they usually do, to, to deploy it and to wait until it's been tested by the bps on yes.

B

Before, uh, ending the sla because, obviously, if we end the sla in august, um,, we might find bugs when we deploy to, uh, ya, made that a few.

B

Months later and then, uh, they're no longer obligated to, to fix them.

B

So my have to either contract them again. Or, uh, fire, uh, find someone else, to, uh, to fix them.

C

Right. uh, two questions on that yam.. So in solution that would be deployed,. Can you confirm, cuz? We talked about breaking changes earlier,. Is it a consensus,, uh, level change, or is it a breaking change because those are different?.

C

Neither, neither.

B

Because this, this release is only, um,, essentially it, it, it,. It has its own protocol version.

B

So any node that is not,, uh,, uh, upgraded will still be able to work with a node that has been upgraded.

B

And,, and that is a toggle on change.

C

B

So, exactly. and it's just configuration by individual node operators.

B

Do they want to enable that feature? they can. if they don't, no big deal., um, it, uh, they,, there's no requirement to, uh, enable it.

C

Jeff, uh, just,, you might not have the answer: off, uh, on the hand,, but that milestone five right, now, jeff, uh,. What is the total sum, uh,, the actual funding amount,? Do you know?.

C

Roughly., it doesn't need to be exact., maybe. yeah. and the reason why I'm asking is, I would also be comfortable in saying, um,, that we could split that milestone five and two milestones and give the majority of that after a month, or, or whatever's.

C

Written currently after deployment to testnet, cuz, that's where we'll catch the majority anyways.

C

Then we withhold a very small portion,, which is less so about, uh, bug fixes.

C

It's really just extending that sla period if they're comfortable.

C

But I don't know what that, that total amount is.

A

I almost have an,, let's see here.

C

And then I guess the total amount, the, the mouse five percentage of it.

C

Is it of the total funding?.

A

Yeah. milestone, five is $7,650.

A

It's like,, so it's a joke.

C

Yeah,, which is nothing. so I,, I would even be, yeah,, basically there's no,, even if they decide we're not supporting you, we're not giving you sla, we're, not fixing your bugs,. We've got no leverage.

C

Um,, so I would even be comfortable in just saying this sla will end a month after the test net, and if we need to reengage them,, we have to bear those costs. Anyways.

C

Because that $7,000 in, uh,, how much are we paying out of the $200,000, is a minimal percentage.

C

It's irrelevant.

B

Yeah. for, uh, for comparison. for comparison,. We put 600,000 for the end of the sla for at centrality.

D

I,, I think, at the time it was just to have something hanging out there for it. To, to, um, ensure against non-performance.

D

Um, well,, it's also a non breaking change.

C

It's a very small upgrade that people can do on their own.

C

D

I think we had talked about that. This was low, risk.

C

I think we did this because, and the, the, the low dollar, uh, value indicates,. I think it's,, it's just because, like when.

D

You no longer have payments, you,, you no longer have any leverage.

D

And we have,, we would have the very small $7,000 worth of leverage to make, to, to keep them, to keep them interested and engaged..

D

Um, as a, you know, though,, we would hope that would always happen. By, by good business, ethics.

D

Um,, I think it was,, I think this, that,, that's what that reflects. Is, is I, because the amount is so low,. We could also go back to them and ask them if they're comfortable in waiting till august.

C

I mean that $7,000 is likely not making their payroll, um, any, any different.

C

They might just say they're good, and if they say they're, not good,, then we would respect the current contract.

C

And either way, it's so minimal,. It doesn't really change. Anything.

D

I think I would suggest that we should.

D

Ask ourselves,: do we feel that that is a, uh, suitable amount of a suitable length of sla?.

D

And, um,, we should determine, you know, hey,, you know what,, maybe this is,. This is fine.

D

We, we've had, well,, we'll have, have had enough, uh, or maybe we should say, you know, we, we,. It might be really nice to have them, uh, on,. You.

D

Know, on speed, dial, for, uh,, you know, for another two months or something.

D

And if.- and I don't know if the appropriate time to do that, is immediately or when the test net is deployed,, but, um,, it might be worth going to them and saying, hey,. What would, you know,.

D

Just,, just so, we have this under the understanding ahead of time,. What would it be? Worth?.

D

What would it,, what do you think it would cost for additional three months: of, of, um,, sla, time?.

D

Extension and then we'd, know,, um, and then we'd, you know, we,. We wouldn't commit to that.

D

We would just have that option and we'd have the price set up.

D

um,. I think that would,, that's how I would approach it.

C

Works for me. yeah, that works for me.. We can't,, I mean, we,. We should respect the contract we have with them regardless,, so we can offer that extension.

C

And we can choose to exercise or not that option, uh, in time, if needed.

D

Yeah. and this could negotiate that as opposed to waiting, waiting.

B

I,, I agree with that. and I would also add though, um,. We should probably think, uh, for future rfps.

B

Uh, to, um, to keep a larger proportion of the total, uh, payment for the end of the sla.

B

It seems to me like, um, that would be 7,000 here is too low.

B

Like, uh, should,, but I think it also depends like what is the risk of the,. I mean sure.

C

Let's,, let's say it's a,: we could standardize it's a 10, 15% or something like that,, but it also depends like something like faster finale.

C

Sure. and instant finale or idc, the.

C

Sin in particular,, the,, the breaking component or the risk, is much higher than this.

C

Oh yeah., it's this.. We could just choose not to enable.

B

Yeah., a a, absolutely, for sure., but it's still,, it's still, cuz to me: it, it kinda, it kinda,. As we experience now,. It basically tells us that there's no leverage,, so we can't yes.

C

Can. the, the percentages, anything? yeah, exactly.. I think it was a conscious decision at the time.

D

Right. so reflected that this is not,, not a consensus protocol level, thing.

D

I mean,, I think at some point somebody signed off on 7,000 and I don't remember the, the date,, but I think that's why well, we all did.

C

Yeah, exactly. right. right., but I,. I really don't see this as being an issue right now, because again, the,, the nature of the function itself, is very low..

C

Um, yeah, I,, I like your, the approach that you suggested, douglas.

C

I think it's good to proceed that way.

A

All right., so in terms of these milestones, then it seems like,. So the one thing to call out,, I renamed heart of milestone, four to just solution, ready.

A

To be deployed on main net and taking the actual deployment out.

A

Other than that, uh, for these milestones, are we ready to vote?.

A

Do I have everything up, updated?.

C

And just to confirm, jeff,. What are we voting on on that? Change?.

C

Yes,, because right now are we voting on milestone three on that list?.

A

On, on the list., so we are going from these milestones at the top, which are in the contract to now these milestones down at the bottom, with these.

A

The new description, these, uh, deliverables for each of those milestones and prior to voting to confirm,. Are they in agreement with these milestones?.

A

Yes. in fact, uh, they were working with ome.

A

Uh, yes. they're, they're fine, with these, uh, milestones.

A

they that, in fact,. They asked me to bring it up for vote.

D

A

All right,, let's call a vote.

A

so, start with you.

A

E

Uh, waxed,, that's yes.,.

E

A

A

well do make assumptions.

B

A

A

okay, good., so I will get that back to you., who will a coordinate with them and the next milestone. Is, uh, I'll tell you when we get closer.

A

All right. uh, next thing for new items, uh, antelope, go to market, cross chain, marketing.

A

Ver uh, lucas,: this was something you asked.

A

To be put on the agenda., would you like to take a moment to talk about it?.

A

I'm sorry,, which item?

A

antelope go to market. cross chain. Marketing. Group.-.

E

Oh yeah. so that, that was actually put in, uh, a while back.

E

Um,- and it was just an update regarding the fact that we are regularly meeting now.

E

There's a cadence to these calls.

E

um, and, um,, you know, the latest one we're just discussing, uh,; essentially, alignment on antelope bo,, um,, uh,, press releases, and,, uh, and then, um,.

E

Any sort of articles, uh, across different chains as we are upgrading.

E

So I think that's a, um,, it's a pretty good initiative. And, uh,, you know,, at least from our side of wax, uh,, you know,. It helps us kind of coordinate all these different pieces.

E

Across, uh, different social media platforms.

A

Okay. is there any questions?, I just, that was just coming with,.

A

All right. uh,, the last new item, uh,, the timing of this call.

A

So, uh,, it's been noted that this call tends to be a lot of just routine status reports. Now, uh,, and it has been suggested that this call happens once a month on the first thursday of each mud..

A

So I will pause there and open up for what could possibly be a lot of good discussion.

C

That's a great summary. uh,, and so I would suggest that we, we proceed with that. Until, uh,, further notice.

C

So I mean, we've got no issues in, in having ad hoc meetings. If necessary.

C

That's how a lot of these meetings started., but I think at this point we've got a few items that are essentially now outroing in not maintenance mode,. But in development.

C

And so a lot of these calls are somewhat repetitive, and so I would support moving.

C

Or dropping these calls, uh, to once a month, uh, un until we decide that that's no longer, uh, suitable.

D

My, my, my take is that this is, this would be reflective of how much progress we've made.

D

Um,, this group was begun, uh, as a, in an emergency basis.

D

There was a lot of technical debt that we had, um, and development of the antelope protocol and a number of, a number of other things,.

D

Branding, identity, uh, community building that needed to happen.

D

Um, and so the previous schedule made a lot of sense, but most coalitions don't meet weekly.

D

Right. um, and I think,, I think, monthly- feels like a good cadence.

D

Uh, at this, at this point in our,, uh, development and existence.

D

So I,, I would support that.

E

Same, same thing from wax. I,, I think we needed the, this cadence at the very beginning.

E

Um, and I'm sure we will have to, we'll need it again. Once we go through another round of prioritizations and projects kick off.

E

But, but right now, we're, we're more in like a maintenance, mode.

E

So,, once a month is perfect.

D

Yeah. the thing I'd add, oh,, I'm sorry.

B

No, no, no. I was just gonna say, uh,. It makes perfect sense to me as well.

B

we're,. It's been almost a year, so, uh,, so like there's, uh,, quite a lot that has been done: already, so normal that,, uh, organizations, evolve, uh, past their initial setup, phase.

B

Now they enter, they're more, uh,. I guess like bruising speeds, phase.

B

D

The I, I agree. uh,, the only thing I would add, is that this is our primary form of transparency into our combined, uh, uh, communities.

D

And I think that's extremely important. uh, as,, as I've said on almost every call,. What if we meet, make a mistake?.

D

Let's air on the side of more transparency., um, and so let's,. That is something that I will be conscious of, and I think we should all be watchful for as we, as if there are a lot of meetings that are, that are, um,. That.

D

Come up, uh,, where we're deciding things, uh,, as opposed to just dealing with minutia.

D

Um, of those, of those breakout, meetings, uh,, that might be a reason to, to have a, an additional,. You know,, an additional, um, call just to, just to surface all of that to.

D

Our community,, which is, I think, one of the primary, um, uh, objectives of this coalition.

C

And, and just to confirm, jeff,, the gi dupo that you're currently showcasing on screen is open, correct?.

A

That's perfect.

C

So, um,, although for those listening,, although we might not have a video once per week,, if any changes are apparent, that regardless of, of we meet.

C

Or not,, as douglas just mentioned,, all of this is transparent, regardless.

D

A absolutely. but, um,, while much of our audience, is very familiar with github, um,. There are also many people who find it extremely intimidating.

D

Um,, I don't know why,, but it's just sort of a, a,, a mental block, and, and they,. They don't know how to navigate it and they wouldn't, it's not as accessible to them as a video would be.

D

D

Anyway, I think, we'll,, I think we'll strike a good balance.

D

uh,. I just wanted to sort of be on record with that, and so that we're, we're mindful of our responsibility to our cons, constituents,.

D

Which I think we always have been, and we will continue to be.

A

All right. any final comments on this?.

A

All right,, so, let's take a vote to set first thursday of each month.

A

E

Wax? Yes, as well.

E

A

A

B

Yes. or ux.

D

Oh, wow. expecting one of the canadian guys to do what?

D

yes, please., I wouldn't have, or yes, sorry.

A

So I will update the in height.

A

um,. I guess not.

A

A

All right. um, oops.- this is done.

E

A

All right. kind of going through the status. uh, couple of these will be quick. Again.

A

uh, we're, uh, same update with some of these that the, uh, e n f is going to start getting into, uh, some of these, uh, requirements, uh, that we've talked about.

A

Um,, the p2p optimized transaction propagation and the ram limitation fixes.

A

Uh,, we already did an update on the p2p peer discovery.

A

That was the new timeline that we voted on earlier of I'll, actually move antler, c d, t up cuz, that's pretty easy as well: that, uh,, that is about to be released.

A

Uh, and once it is,, of course, everybody will get an update at that point.

A

Uh,, let's see. flowing into, into finality in I b c gil.

B

So we've had a, uh, discussion, uh, with adam and with eric and matt, um, yesterday.

B

So essentially, uh, it was mostly about, um,. The e nf updating us on their, uh, planned calendar, for, uh,, the next few months.

B

So, um,, they are definitely making, uh, a lot more room now in the schedule. For, uh, reviewing and, uh,, finalizing the instant finality parts of things.

B

So, uh, we're hoping to, uh,, see that come to fruition over next, uh,, two weeks.

B

They still have, uh, some back backlog to process before, uh, they can, um,. They can engage to the degree, to the extent that they want to engage.

B

But they, they reassured me that they wanted to make this a, uh, their, their main priority. For, uh, this upcoming september release, their,, their largest, um, uh, priority essentially.

B

So, uh,, it would appear that, uh,. We will be in, in good hands, for, uh,, the final part of that project.

B

And, uh, we're very, very much excited,, looking forward to, um, to the involvement of the amazing engineers of the e n, f, um, and seeing ality come.

B

To, uh, and through reality,, I can confirm what you just mentioned in ym.

C

If,, if at any point, uh,, you require more, uh, support of some sort, uh,, please don't hesitate to reach out,, obviously to bart, uh, or to myself directly.

C

Much appreciated. much appreciated.

C

uh,, so yes,. We do aim to have instant finality out, uh, in our september release.

C

That would be great., I don't know if it's possible,, but that would be great.

B

I think it is, that's what we were, uh, assessing, um, yesterday.

B

And, uh, we're, we're definitely optimistic. It can be done.

B

And, uh, if, um, yeah,. If the e n f uh, is there, like we're, we're, we're ready,, we're, uh, willing, and, uh, if, um,, if you guys are able to,, uh, to, uh, participate in the.

B

Degree that, um, I've been assured you would,, then I think it's,, it's gonna, be I in there.

B

Did you change the, uh, the meeting for that?.

B

No, he's just going yesterday., it's better than it said you were on another meeting.

B

uh, no,, it's true. and that, uh, yesterday,. I apologize.. I had to deal with, uh, with some, uh, some, uh,, further things, but, uh,. That was my skills.

A

B

No,- and it only happened- like, uh, uh,- to be fair at this, this meeting,, I think only.

B

Happened two or three times over the last two months, because, uh,, essentially like most,, most people, uh, from the nf, were not available,.

B

Uh, due to the, the,, the release of e v m, few other agenda, items.

B

So it's not,, it's not,! It's not you, it's, uh,! It's us.

B

Like as a, as a group., we haven't been meeting, uh, much at all.

B

now,, but now that this is gonna be, uh,. This is gonna change and it's gonna start being a regular, uh, occasion, and there might actually be more than one.

B

Meeting a week, now, uh, uh, as we enter that, that, that, uh, last space, awesome.

D

That's what I assumed and I was happy to have the time.

D

A

Uh, aaron is not here: today. um, provide a more in, in-depth update on sdk.

A

Uh, but I knew the, I do know the project is moving along as, uh,, as it has been.

A

Um, and then the last thing is on the ledger: app.

A

uh,, some of the resources, uh,, started to become available. Again, uh, recently.

A

So, uh,, I believe, there's some movement on that,, but I still don't have a date yet on when.

A

I will be knocking these, some of these things. Down.

A

Um,, hopefully, in the next um, e n s health report that we put out,, we'll have, uh,, more concrete dates on that, and that should be next week..

A

Are there any other items that we wanna talk about, today?.

A

Are there buddy? uh,? We will see you guys in a month.

C

Awesome.. Thank you. Everybody. thanks. Everyone. have a good one. good one.

B

Take care. bye-bye.