Everything EOS Antelope Coalition, 13 Apr 2023

Previous Meeting Next Meeting

⏯

youtube image

►

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

Description

Join us as we explore the progress and updates on the IBC Protocol, aimed at building a bridge between EOS ecosystems for interoperability and cross-chain communication. We discuss collaboration with other chains, encouraging developers to build on IBC, and seeking more developers to test and work with the protocol. We also cover core updates including feature activation, smart contract edits and integration, new keys, aggregate signatures, and optimization. Plus, hear about the positive feedback from developers using the SDK, upcoming polished UI release, and Antler CDT new release. Don't miss our discussion on the upcoming meeting with Ledger representative and integration plans.

#web3 EOS #IBCProtocol #Interoperability #Blockchain"

00:00:00 Intro
00:00:04 This week's topics and updates
00:00:13 P2P Optimized Transaction Propagation and RAM limitation fixes
00:00:33 P2P Peer Discovery
00:24:00 IBC and Instan Finality
00:28:05 Wallet SDK
00:38:06 Antler CDT
00:40:17 End

IBC Protocol
Progress on building a bridge between EOS and Cosmos ecosystems
Interoperability and cross-chain communication
Collaboration with other chains
Encouraging developers to build on IBC and explore use cases
Seeking more developers to test and work with the protocol

Core Updates
Feature activation mechanism implementation
Smart contract edits and integration
New type of private-public keys
Aggregate signatures and new intrinsics
Optimization and improvements

SDK Progress
Positive feedback from developers using the session kit
UI improvements and bug fixes
Upcoming polished UI release
Development of contract and account kits
Lowering the barrier for development with easier interaction with contracts and tables

Antler CDT
New release coming out soon
No additional updates during the meeting

Ledger App Integration
Upcoming meeting with Ledger representative
Gathering logos and content from each of the chains
Identifying web pages for content updates
Discussion on whether Ledger will create a page for each chain or if the individual chains will handle the content

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 so cloudy not a lot on the menu today, um but there are a couple things: uh we should talk about. um First, two items: the P2P optimized transaction propagation and the ram limitation fixes.

A

um As we've said, these are still paused but will soon be open, as enf is getting ready for the next uh release. Coming up um the next one P2P peer discovering uh now I did want to ask uh Yeoman Lucas about the status of the last Milestone.

A

um It's like the miles. The pr was posted on March 22nd and it's still kind of pending. um So is there a timeline on this? Is this something that there's a blocker that we can get resolution on? Or did they miss the mark and there's a lot of uh issues that they need to recover like kind of? What's the status on that? So we can close this out so.

B

From my uh perspective, it's a little bit of of all of that where um on one end- um and there were uh so so there's there's a few PR's um and I'm, not sure. First of all, that kind of I, don't I, don't really know where to start. The first first thing I guess is. uh It would be very helpful if we had um or if I had, because I I didn't couldn't find it.

B

But I don't know if it's available anywhere or wow, but I'm I'm, not uh aware of exactly what the terms of these Milestones are. Is it just to fulfill the requirements tr1234 uh or is it? Is there more to it because I mean in the case of what I've been uh what we've been doing with sentinelity at IBC, for example, there was a pretty clear, not clear enough to my liking, but there was still a pretty clear definition of what needed to be done. That's not like a deliverable and not just a requirement.

B

So it's kind of it's difficult to say. Are we meeting the requirement or not? If it's, if there's no deliverable I mean like these are PR's that are supposed to be merged? In the code base, but the adult lead to any functional product or functional, uh you know like I, guess, I guess like um features just yet, but I'm I'm kind of at a loss in terms of what should be done next as if it was if I was a you know like a maintainer of that of that goal days.

B

I would not accept these PRS because they don't they're. Basically, like you, know like uh bunch of loose and loose strings that are not leading to any completion of any features. It doesn't doesn't get us anywhere. It's just additional code that gets added without having any uh clear purpose, is to um get what I mean uh so I'm not I'm, not quite sure how the Milestones were defined, and uh if, if this is the appropriate way, it's gonna go about. It.

B

There's also other things uh that I'd like to point out, but maybe start and start with this one has um any additional information on that front. Maybe just a few if you have uh get more insole here,.

A

Yeah sure, so, first of all um this that sounds like an issue. We need to coordinate back with fumin. um The Milestones are defined. That was in the um uh the the RFP response, and fumin should have that now how the pr the specific PR matches with a specific Milestone again I, don't have that in front of me, but that would be where the information is right and if there is some sort of lack of clarity um between the two.

A

um So that's a different issue than was escalated to me, which is fine right, let's, let's kind of get to the bottom of this.

A

um So if that's the case, what we can do is I will see like let's pick a time where uh we can also assume it involved, and then you and uh Lucas or Lucas, your representative, um get on a call and walk through that and make sure that we all understand what the target is that they're attempting to hit right now right.

B

Okay, so that's that's number one um which, which definitely will help um number two on that list.

B

uh It's it's a bit I mean I, mean there's, there's probably more discussion to be had uh with the team regarding that, but uh there were also, um you know like uh clear misses in my opinion, uh in terms of what was uh done versus what was expected like the uh for example, what are these PRS added a uh a configuration element that should not have been a configuration element and should have been instead, a kind of I guess like a resource that should be part of the the uh of the the code base and uh it's gonna.

B

It's gonna, like feels feels to me like that. The requirement was not well understood there, uh so that one I mean has been addressed. We've fixed it, but it kind of It kind of raised additional questions as to the understanding of what is required uh versus what is being delivered, because if, if it's kind of it's kind of you know like you're, asking someone to pay the the fans blue and they they end up cutting the fence in two instead like it's, it doesn't really they'll like bring you to the the end.

B

C

One there's one problem: if, if there's a misunderstanding that leads to one you know that happens once it's a whole different level. If you start recognizing that they're just going to be ongoing communication challenges- and um not just you know in in various terms, so right.

B

And to be fair, they've addressed it I brought it up; they they they understood it, and after after uh just a little bit of back and forth, they fixed that. So that was that was solved, but uh I'm I'm yeah, like I I, just want to make sure that I understand exactly what they've been tasked with and uh how they're opposing to uh address that. So that way, I can I can I can review it, but.

C

I'm dealing with something very similar trying to hire a reasonably large number of developers, and- um and um that is something that that we're facing and so all I all I would say you know, would suggest- would be try to assess, try to make a good assessment of whether these are going to be ongoing problems or whether these are sort of one-off problems that once once fixed won't be because to me, that's the that's!

C

That's going to be the con, that's going to be the limiting factor, that's gonna, of how well this will work so a year and well, that's just my.

B

Opinion- and there was another kind of like similar issue- I guess, uh which which also raised additional question, and then we really know a lot about this. But while at some points there was someone else, uh CRT lab roads was part of the zero bass team. I believe uh it was also been reviewing. uh Prs I think they're doing it as they just just voluntary uh work.

B

I asked their their team lead and said they were encouraging their developers basically to look at outstanding BRS and provide problems there, uh and uh the guy essentially suggested that they Benchmark uh various.

B

You know like um ways of doing things essentially like dealing with uh uh mutex objects to kind of control, um tread slow and that kind of stuff, but to go to details, and uh so so uh he suggested that The Benchmark performance of various uh attempts at doing so and- and they came up with some sort of a test where they said- oh, like we're spawning a thousand threads and we're running like 30 000 in iteration years of performance. But it's not.

B

This is not the proper test like there's nobody's running 10, 000 threads so on these machines, like you, might might want it best. You know with five or ten or something but yeah I know like they're.

C

Testing they're testing a situation that never actually exists in real life, so I can then buy like two orders of magnitude. So what's the value of it and.

B

That that raises it because I mean I mean uh if you were with multi-trading. You also know that this is going to cause additional issue like there's. There's basically, like uh you know, context, switching costs basically like moving from one thread to the other, and what that and so they're not measuring at all with what it's right right, yeah.

C

Those problems, grow, non-linearly and, and so and and it suggests, if I'm, if I'm hearing you right to me, it suggests a lack of fundamental understanding of what it not that has nothing to do with language or anything else that it just has to do with.

C

um Is there a clear understanding of what our actual goals here are, and you know or or is this or are people just trying to like create a volume of of work that you know that, may not, you know, actually contribute much value. You know to me exactly and.

B

This is, this is exactly it because I mean at the end of the day. At the end of the day, you know like uh looking at the actual requirements. Actual Milestones um is is very important, determining whether or not they're making progress towards these goals, and uh my concern so far is that seeing the way that they've looked they've been handling it, it requires. It would require a lot of micromanagement to basically get them to produce code.

B

That has a chance to be eventually merged into this, because, if I mean like the way, the way it's going so far, I'm a bit a bit, you know like yeah worry I can just give my perspective. Guys I mean working with uh teams in South, America and Asia uh I mean a. It is a very a touch heavy process. I mean I, spend most of my days on calls daily with each team, and then each project requires detailed technical specifications and kickoff, where you actually walk through in detail.

B

What needs to be done and then you have to require them to pair it back next day. In writing.

B

You know what it is that you understood that needs to be done with when the actual you know, technical milestones and goals and and this process repeats daily right like unless you cannot have a team in Asia that speaks different language and and have different cultural understandings or whatever differences and and just let them be for a couple weeks and and expect to get what you want right like this has to be it's a very high touch process and I. Don't know if we do that today.

B

uh If we don't, then then they're not going to be successful right.

C

Now management, research that would that would presuppose a certain amount of of project management resources that we don't have even close to right. We so.

A

We're very important it's more than that, because they've been raising questions and fumin has been bringing those questions back, but then sometimes not every time sometimes like days. Maybe even weeks would go by on this just in this project, with no response so like we need a better escalation path right to say: hey, there's an open issue and we have to have resources with the engineering capability to be able to respond now. I get the fact that the escalation part that's definitively on fumin and I'll work with him to say.

A

Look if there's an open item. You need to pound the drum every single day, but you got to understand that she can't answer the technical questions right, and so we need those people to be involved right. You to address that.

B

I think it's a good experiment. Right I mean if, if this process through this particular project does not work, then we know that we do not have capability to effectively engage teams in in other regions, and that's that I mean that's. That's going to give us an answer whether, but at least can participate. Sorry if I don't go ahead, no no I was just saying I. Think I, think what you said before to me is it's very insightful and I I agree.

B

It probably is is the right way to go, um uh can I you know like whenever we we ask something uh make sure that they reformulate it in their own words, so that we can know that they understood what the the requirement was. uh I think I think it will. It will definitely help uh if we, if we start adopting that approach, uh especially dealing with with teams that don't necessarily um speak much English and and whatnot and uh at the same time, there's there's also um I I.

B

Think I think when we my expectation when, when I started and what I agreed to review this and to basically be there and doing that work, I was expecting that you know like uh I would receive something that was more or less feature. Complete and I could test that and could verify that it was meeting objective, criterias and whatnot, and here I'm basically like it. It really feels like a you know, like a uh someone who's been submitting like a homework for their computer science class.

B

You know, like yeah sure, like they've, been they've, been naming things right, they've been writing code and everything, but it doesn't really compile it doesn't really work. It doesn't really show.

A

You I think your expectation was correct, though, like feedback from.

B

Aaron, so so this is, this is like, like our expectation, was that there would be kind of like a final PR. That's already right feature complete, and then this is just like a final review, not yeah. We are like we should. We should not be reviewing, like uh you know, daily commits for like small little changes. That's that's not. Why we're here yeah.

C

I was saying it well, I think you had your end. Your understanding of what was being asked is is certainly how I understood it, and, and what's what you're actually being you know uh led to perform, is, is 10 or more times the work that you signed on for all right, independent versus you know the third party yeah.

B

That's, that's! That's for sure. That's my expectation, I was was expecting to have. You know like something that was kind of you know more or less ready, maybe a few little bugs have there to iron out little optimizations here and there, but really it's basically like. Oh here, I wrote 20 lines of code.

B

uh Let me know if that that's okay and I'm like well, you know like it, doesn't really show much like it's got a you know like you're you're, showing me something that doesn't really work that doesn't really get us anywhere to uh we're final release or anything like that, and it's kind of that's kind of yeah. You need to get to get much further along before you.

B

You ask uh reviewers to look at that stuff if I think, for example, same process that we're doing with uh Eric and Matt regarding instant formality, I mean we're like were, were we've got, we've got code that runs that works, that's ready to be reviewed and yeah sure there's a little like few discussion items here and there uh to be uh to be Ira Dell, but it is, it is kind of quote, feature complete and has to uh I'm not going to bug them until I have something meaningful to show that you know so.

B

It's gonna, it's gonna, like maybe maybe I misunderstood what was expected in terms of the review process, or maybe uh the door. Okay, okay,.

A

You did not no that's what I'm trying to say like we I, don't need I, don't think we need to believe with this that you should have had a delivered solution that Mets the expectations and requirements defined in the Milestone details. So I've asked Fu man like he's, obviously in different time zone, so he'll get this in a number of hours, but the first thing we need to do is: he needs to meet well and I'll, be on the call, as well with you and Aaron at minimum, to discuss the scope of the requirements right.

A

You should be validating just to make sure there's Clarity there. um The other thing- and this is I- talked to fumin a couple weeks ago about this, but I forgot off the top of my head. I've got it written down somewhere, but they were supposed to submit some sort of design or architectural documents um to some level to start the conversation, because one thing we all knew going into this was that was going to be a big component. uh Does anybody recall seeing that or reviewing any sort of document that said?

A

Okay, here is going to be the structure of our approach.

B

Well, I haven't personally I haven't seen anything like that.

A

Okay, because I think I, so I'll follow up with that, but I think that is also part of like we can't have experimental code. I totally agree with that. It's like your comment that it's like you're grading homework is kind of interesting, but if we had a good architectural document that could be something worth taking the time to review and then their code should fill out the picture and there would be less concerned about uh some of the low-level items.

A

So I will follow up on that as well to see what is going on there uh again. I think this was a good discussion, because my understanding that, as where the issues were, was different than what you're uh sending back so we'll have an offline discussion kind of get these things lined up. uh You know and we'll just try to get this back on track in a way that is not pulling so much time from uh any of our resources here.

A

B

And I just want to add also like this says. This may not be an entirely their fault. There might have been additional confusion in the in the process that led to the state of things, maybe understood something different. So it would be probably a good idea to kind of fear the air make sure that we're on the same page and that would start by yeah just making sure that we, uh what we're reviewing that we understand the Milestones that are being uh requested, also review and that we can properly assess like yeah.

B

So far, I've been only going by the TR requirements and I mean the gr requirements are important, determine uh weapons to be built. But it's not enough, like any can't really say like oh, like yeah I built something that meets requirement one, but if it doesn't also meet two or three and four five and six I mean it's not the feature completed. Yep.

A

Perfect yeah done listen, some NAB.

C

uh Yeah so, first of all, I think this is a great conversation and I and I appreciate you, you bringing it to us I'm, hearing two issues here and in the plan to address it. I'm hearing mainly uh an approach on the first issue, so the first, the first issue I hear is the ad is: is the ad hoc issue of uh of and I'll explain? So so there's we are trying to ad hoc.

C

You know, find a solution for this one situation, but I'm always going to encourage us to to develop methodologies instead, so that we don't keep having the same ad hoc issues. So the ad hoc issue is that this was not. There are various reasons why this this issue is not.

C

um uh You know going well and that's fine, because it's the first time we've really gone with an outside group, um but I'm I would like to encourage us, and this means starts with you Jeff, please, as we address these. Let's always be thinking and in terms of developing a methodologies methodologies to make sure this doesn't happen. This doesn't continuously happen.

C

um A couple ad hoc things don't hurt us, but but not, but failing to provide our own methodologies that that reduce or eliminate these things will hurt us a lot as as a Development Group. So I really like to always I like to propose that we always think in that mind mindset and then one of the things at in doing so it you know, I, think it's been a good. It is a good experiment to say: hey, let's open this up to outside groups, but one of the things I'm realizing.

C

Is this group everyone here at whatever by whatever chain, it's self? It's a self-selected group of of incredibly entrepreneurial people. um You know High function, thinkers, um people who, who are very good at working with minimal resources. I mean you know even even EOS has has has minimal Resources by by comparison and all the others do, of course. So so we have so we have self-selected self-trained to be extremely capable under such working conditions and as I work with other groups um outside of this I see.

C

That is not at all normal and we should set our experience. So we should set our expectations that, as we go outside of our of our known, Workforce I, don't think it's I, don't think it's realistic to expect you know any level of of uh entrepreneurial ship or the ability to discern the real, valuable issues, and things like that um that that I think are just inherent in that I would think getting what anyone in this group be able to boil those things down.

C

These are we're hearing about problems that I, don't think any of us would have, because none of us would like assign those kinds of testing things to something like like. That's that's sounds like make work to me, and none of us here are make work people, because, because you know we're not trying to get an A we're trying to make happen so um I just encourage you defensive food, Dan.

A

C

Don't think I'm, not it's not about Canada is home anyway, by the way, I want to be really clear. It's not about any one thing. It's about our own process. We can only control our own processes, but yeah. Please.

A

Right but I don't think this characterization is quite as accurate because we made it clear to them up front that they were walking into a complicated environment and we've been telling that adult.

A

We don't want you to sprint out ahead and find out you've been going in the wrong direction, and so to me it sounds like they're over compensating in the other direction and saying hey, here's Snippets of code, and so we need to strike the happy balance like they're like trying to push forward faster than uh um I, wouldn't say, faster, I, think you're, right and you're gonna check in at each.

C

Wait absolutely so in that hole in the whole development of the methodology um approach to this we should. We should first and foremost, look at our own Communications. What we're asking people to do and if it's so I'm I I, don't care where the personally, it's not important to me, where the their the um blame I, don't even think of the concept of blame. But you know where, where the fixes land on this, only that we look at these fixes and say you know not hey.

C

Let's never do this one thing again, but let's, let's look at, are we communicating the right things? Are we you know like on a larger scale anyway, I've said I've said my my peace ticket for what you will and thank you for listening.

A

All right any more comments on uh Peter Pete, peer discovery.

A

All right again want to give an update on instant finality and IBC. You can kind of run them together.

D

B

So um for IBC, the uh M6 are up for uh yes and what uh yes and the Telos to complete the integration with wax I believe uh we have I, don't know Jesse if you know like I, haven't checked the m6 for uh Telos, but it was pretty close. I think we had 12 out of 15 last time, I checked and uh on yes, I think we had eight out of 15 that might have changed in the last day or two, but that's about where it was um so um so so yeah.

B

It's basically at this point. It's just uh giving the BPS a nudge to make sure they uh they complete that and then once they end Sig uh go through then um the last step is basically to turn over control of the contracts to uh essentially the governance of the chain.

B

So, like we've done for the other chains will uh basically do the same for wax and at that point, you're good to go so um happy to keep you in the loop Lucas like uh just I'll, keep an eye on this and whenever it's complete, uh I'll ping, you and then, uh if you need anything like a transaction tests or uh uh any yeah links to the GitHub repos and things like that. Just let them know I've got all of this for you. So it's cool, I'll.

D

B

Play it the way you see fit and a happy to also uh help you craft any uh press release messaging that you'd like very exciting indeed. Indeed, there's a lot of people that are have been waiting for the the wax IDC for a long time, so yeah.

B

um So on that front uh that that basically takes care of uh the IDC side, instant finality is still on a hold um like somewhat on hold until tomorrow, because uh on the prior work commitments from the same same team, that is reviewing it, but I got assurances from.

D

B

The various people at the enf that uh starting next week, things will uh basically accelerate a lot or when it comes to reviews and discussions of the last few items to complete the core uh functionality. We're pretty much there like there's just just like I, said, like a few, a few discussion items uh to finalize and then uh then there's more work to be done in terms of integration in terms of uh essentially like connecting all the plumbing so that it works across the boards.

B

There's a number of things like there's, smart contracts to be uh edited and to be kind of changed a little bit like the feature. Activation mechanism has to be implemented and uh additional stuff, like the utility used to deal with uh these new type of private public keys that we're dealing with. But this is all kind of you know relatively uh straightforward stuff. uh The core has been uh pretty much built and uh it's looking pretty good. There's going to be probably some optimization as well, but that's that's that's part of it.

B

So um so we're quite quite excited about that and uh We've also got some very interesting benchmarks when it comes to uh the aggregate signatures. uh The new intrinsics that we're adding to um to the envelope code base- uh so that's uh that's also very exciting, I- think I think uh it will open the door to a lot of new um possibilities that that will be uh didn't really think were even possible, if you, uh let's say that last year. So that's uh that's quite exciting stuff.

B

There's going to be a lot one back and left to discuss discussion materials for quite a few, uh a few butt guests in my opinion. So uh we can talk about that at one point. Otherwise, uh I think that's pretty much. It um we're looking to uh get back to steam ahead in that direction. uh After the logic DM.

B

Looking forward to your last Sprint.

A

Awesome any questions.

A

All right, Aaron, you want to take it away on us to get.

D

Yeah sure um kind of a repeat of last week, but we are engaging with a lot of developers right now and we're getting some great feedback um on how the session kit Works.

D

um We have a number of apps at this point that are integrating this early access version and the overall it's just been a really positive feedback um with it, allowing them to do things that they haven't been able to do before in apps, without building themselves and really just helping them build their applications better and the feedback like I, think I started with this, but it they're coming up with situations that we hadn't anticipated that were able to make tweaks for and accommodate for and so far uh just positive I think it's the best word to describe it.

D

So um in that vein, we're kind of uh like I, said we're making adjustments based on the feedback coming in from the developers who are deeply engaging in the session kit and we're compiling that into the documentation that we're all working on right now. um The developers we have right now are the ones who you know.

D

They've built these apps before they know what they're doing, whether it's directly with wallet sdks or, if they're, using ual or whatever they may be using these days um so they're, giving this this great perspective, but then we're able to weave into the documentation into the website into the guides that are going to help the developers that don't have that past experience.

D

So when all is said and done with the educational materials and stuff like that, we should be able to craft a really great um onboarding experience for new developers, they're looking to build web applications in this space um from a development perspective uh like we're doing those sorts of book fixes and adjustments on the session kit, the UI is really starting to come together. At this point, um we have some of the UI stuff merged up into our Master Branch, but we haven't done a release of it. Yet uh we're still doing some bug fixes.

D

There are some kind of uh really annoying bugs that we wouldn't want to release uh like the close button being triggered inadvertently and just closing out the processes.

D

um But in the near future we should have a polished, UI release, which will then complete uh the next Milestone, that is on The Chopping Block. It's a little bit uh behind schedule right now because of the UI, and just because of the way that we didn't anticipate this individual Milestone needing to be done sequentially rather than in parallel, um and the Milestone after that, like I mentioned last week, is just kind of waiting on a technical document based on that user interface.

D

So the Gantt or like the water Folly, looking Gantt chart whatever it is, doesn't like it shows us behind a little bit, but we feel pretty confident in where we're at, and we have now started diverting some of our resources back onto the contract and account kits, which we haven't talked about a whole lot back in February, we decided to de-prioritize those to focus in on the session kit, since that is one effectively replaced, ual and Transit and the other libraries people use today and these new kits the contract kit and also the account kit they're going to provide functionality that we've never had.

D

That just adds an additional layer of ease for the developers.

D

um Not everybody will be super familiar with this, but just to kind of give a sense of what I mean um right now, when you're working with anything Antelope related and you're, interacting with the table or a smart contract, you need to go out and you need to find how to interact with that table or that smart contract like by exploring the blockchain and finding that data. The contract kit is kind of an evolution of that it's going to be Discover. It does the discovery for you, while you're writing your code.

D

So that way, it makes it easier to interact with contracts, whether you're, reading or writing. um So I'm excited to see people get their hands on that. It should lower the barrier, a lot for development purposes and hopefully, I think the milestone for that is mid to late June. So before then, we should have some kind of preview, technical preview of that and be able to show that off a little bit um but yeah.

D

That's where the team's at the website's coming along nicely and uh really excited to be engaging with the developers in this community to push this forward and get those reactions and help them build these apps better.

B

I'd like to add just uh to that, like a shack from our team, has been being a close eye on what you guys are doing and he's quite excited. Like he's, uh he's been working, witchy whale and uh yes transit for a long time. It's been a core contributor to these uh protocols as well, and uh he qualified your stuff as a definite Game Changer. So I'm really excited to see it.

D

See it come to life, that's awesome, he's been one of the developers we've been working with and talking with regularly, um and his feedback has also just been invaluable in this process. You know when you're working on something so hard, you kind of end up in your own bubble and you might not see all of the possible uses of the thing and having people like Shaq coming and dropping this kind of feedback with that outside perspective is so so valuable.

C

Foreign, do you need more? uh Do you need more um testing I I think back to when um you were releasing the the Android wallet and um we had the chance to work really closely with you on on um decide, boater and and it it occurred to me that, like the the better, the the better, the the sort of in-depth the use use case testing, you know like real development, that's going on around something, the the better you can find uh uh problems and I I'm.

C

Just I myself have like I've kind of avoided, jumping in because I didn't know exactly where we were there, but I actually think we have some projects that could be closed. Are you looking for that or or is or do you have what you need.

D

There yeah I mean we're actively seeking that, and we also are open to that kind of collaboration.

D

uh There's a pull request on the open block, Explorer right now that I started, maybe a month ago or whatever that integrates what we have today to kind of kick start that process we're going to probably do that with things like hifa and a couple other projects as well, just to kick start that and start that engagement like us, proactively, kickstarting that, but if you guys have projects that you want us to be involved in the integration of like migrating away from ual or direct sdks integration.

D

uh Yeah reach out we're happy to do that kind of stuff.

C

uh That's great, thank you. um uh We will and actually uh yo same question is. Is that a place where you're, at with the uh with the uh um IBC uh pieces? Are you looking for for um real case studies to come in and sort of you know get ahead of the development or or oh yeah yeah.

B

I think at this point at this point this is uh this is uh for IBC, like we've got, we've got like all the Tooling in place. uh Now it's about. uh You know like the ideas and the use cases where we can basically like make a try to I I got a lot of people uh asking me. You know like uh how to go about certain things, but not many developers that are able to uh Implement such things.

B

So I'd like to also uh uh explore that transfer of knowledge verify how we can uh share that information with more developers on board more developers like uh basically like show them how the protocol works and all of that we have a uh uh till the best year in CI. That is currently writing.

B

An article I can give an article about the IBC protocol. That's also an internal uh memo that the Distributing Apple CID, so it's very, very uh interesting uh music collaboration like to uh also uh uh explore shorter with everyone else system. Anyone that has something in mind that uh could leverage IBC uh hit me up at me to uh discuss with you and I mean anyone who wants to build something on top of IBC. They might not necessarily know what just yet uh I'm happy to also like uh introduce them match developers and uh I.

B

Guess, like idea, generators and see what comes out of that.

C

So so my so thank you, I appreciate that I'm actually really glad to hear that um uh I think we have a small audience of people who actually reach who actually watched this whole thing and would and would to whom this would be surfaced just by watching um I'd like to I think this is a specific area where, where we should um look at how to how to uh surface this, these types of things for people are these very important area and the probably the fastest we could accelerate the growth would be by making it clear to people.

C

So if anyone wants to get, you know talk with me offline about ways we could do it. Obviously we have the the show is one way, but there's some other ways we could. We could try to do that as well. I think it'd be really valuable, so and I'm open to spending time on on figuring out how to do that, because that's this is the kind of thing where the difference between people, a large number of people, seeing it and interacting with it early on or not um has a you know, is something looking back.

C

You will see um you know a large, a large um difference in how quickly these new technologies are being taken up.

D

Agreed totally.

A

All right any more comments, questions on sdkit foreign next, one antler CDT. uh This is a quick summary. It's in the release that is coming out. So nothing new to add there uh final one on The Ledger app, uh there are a. There is going to be another meeting with The Ledger uh rep Thomas.

A

While we have logos and some content from each of the chains, there are actual web pages on the site. That currently, you know, are all about EOS and you know, let's start price and a little history and their support um so there's at least three pages that we've identified so far. So we're going to meet with Thomas to get an explicit finite list to make sure we don't miss anything and then once we have that uh each of the chains can expect Adam to reach back out, um possibly for more content.

A

The one thing we're not sure yet is whether Ledger is essentially going to take the same page, because some of it looks a little canned in the structure and if they're going to create a page for each chain or if they expect, um you know each chain to do that work. So we'll get those answers um again we're just talking about web content at this point, so it's critical it's important, but it shouldn't be a big lift.

A

Once we know the exact pieces of information we need to get and things we need to accomplish any last comments on that.

A

All right, uh we are through the status today. Anything else. People would like to add in the last 13 minutes.

A

All right, everybody have a great Thursday.

B

Thanks thanks, everybody.

C

And reach out, if anyone wants to talk to me offline about any of those topics, I will.

B

I'll, pin you Douglas all right cheers.