 Tracy, we're at 10. All right, thanks, Sean. And I think I'll go ahead and get us started. So welcome, everybody, to the August 11 hyperledger technical student committee call. As you are all aware, two things that we must abide by on this call. The first is the antitrust policy notice that is currently being displayed on the screen. And the second is our code of conduct, which is linked in the agenda. For announcements today, we have the standard depletely developer newsletter that goes out each Friday. If you have something you want to include in that newsletter, please leave a comment for consideration on that wiki page that is linked in our agenda. If there, I guess, is there any other announcements that anybody would like to make? All right, I will take that as a Bobby. I just wanted to remind people that the survey is still in the chat from last week. If you didn't get a chance to take it, it's only two minutes. And the documentation effort would appreciate it. All right, thanks, Bobby. Any other announcements? All right, so we do have two quarterly reports that came in last week. Hyperledger Aries and Hyperledger Indy. I know I saw that Aries one has, I think, about three people who've had a chance to review that. I haven't taken a look at the Indy one, but I'm sure it's probably about the same. So if you haven't had an opportunity to take a look at those, please do. There's some really good stuff happening in both of those projects. Any questions on those two reports for those who have had a chance to look at it? We do have the Aroha one that is due today, so hopefully we'll see that one coming in. And then the Bevel one that is due next week. So we'll be looking forward to seeing those. As far as discussion items, I don't know of any specific TSE discussion items that we have today. But if anybody has anything now, it's the time to bring it up so that we can talk through that before we move to the Task Force discussion. OK, so, Dano, I think it is over to you for the Task Force discussion. All right, let me get my screen ready. So a few weeks ago, we went over the recommendations take one. I spent most of the time sharing the details of it. And we didn't get much of an opportunity to get participatory feedback from a lot of the people who are on the call or who may have seen it for the first time. So I first would like to open the floor if there's anybody that has any comments on it. And then if there is no general comments, we could talk about review the LABS projects and review if there's any other scoping limitations we want to put on the themes. And other than that, I don't think there's a whole lot more to do with this Task Force because as our goals are to identify areas, identify the LABS projects and other sources, and those are the main tasks. So we're basically there. So open the floor. Any general comments about the findings that were presented a few weeks ago? I know that in, let me find my discord. There is one question from Arun. Did the Task Force consider any projects in the metaverse space? Maybe have examples demonstrating? Have interoperative solutions work together to tie in virtual worlds to the real world? Anyone have comments on that question from Arun? Or does Reem want to speak to it? Sure. So this came up as one of the questions. So two weeks ago, I don't probably last to last week on a weekend, I got a chance to attend a blockchain event in Bangalore. It was a hard call where I could meet some of the people. It was a different meeting for me, different kind of setup where it was more from a public blockchain ecosystem, not from enterprise world. But I had some familiar faces there in that event where many of them were talking about this particular topic. So I introduced myself, and then I say that I'm working within the hyperledger ecosystem. But then the very first question that pops up is how relevant would hyperledger move towards in the web-tree space when everybody moves towards, let's say metaverse? In that kind of an area, right? So I think there is two ways I could have responded. There's one way is to just answer, be technical, be objective to the question, or other way could be OK. Let's understand what's happening there. So I tended towards that approach where I tried to understand what's happening there and understand what's that ecosystem moving towards. So most of the problem statements that they brought up are already solved. It's not like a problem that's not solved under any of the project under hyperledger. It's just that there is no such example. And unless we have people who can think the same way, it's very hard to communicate these things out. And that's when, I mean, when you posted that question, it reminded me of this discussion and I had to write it down. So that's the background of why this came up and how it came up. Yeah, because when I look at the metaversal stuff, I tend to agree that a lot of the technology is there to support it. We just, the three rendering libraries are probably out of scope of hyperledger. But the tools to link an NFT to the system should be something that could be done with it. With hyperledger tools, it should be a library that should be there to support. I mean, a demo application that, yeah, that's something that I didn't initially think about, that we might or may not want to do. That sounds more like something like a project level might want to put their demo together, but it's a tough call, especially when we're talking about something like the metaversal thing where it's all aggregates of multiple projects, an aggregate demo. Kamalash? So adding to Arun's point, so six months back, I met one company who was building a metaverse platform on hyperledger fabric. So I think there are such projects are going on. But like Arun mentioned, there is no kind of people out talking about and sharing in the community what they are doing with the hyperledger. Another thing like last to last week, Julian Gordon, the VP, SFSF, like I sponsored, came to India. And Julian and I met with the Polygon Vice President. So, and they have kind of shown interest to be kind of collaborate with hyperledger or like how they can maybe create the plugins for the cactus even I think, something I mentioned in the, this wiki page, like, so how we can involve the other communities or whether create some collaboration or maybe also talk the language of like how the people are talking about the web three in the public blockchain space. So I think, yeah. And I think it's like, when like some, if someone is building on the tokenization, so always the, if like, for example, if the technology person consulting them, so it's very hard to convince someone to create a token, tokenomics on a hyperledger, best projects instead of on the, any public blockchain. So like recently, one of my customers is building some kind of agriculture, tokenomics to an NFT platform kind of thing, like kind of farm land tokenize and then what are the crops is from, produce on the farm is attached to that token. So this kind of thing and he's considering to use the hyperledger fabric, but now suppose when we are consulting those kinds of customer, so if you don't have such kind of stories or some kind of like, for example, like wallet, for example, like in the fabric or any kind of hyperledger project, you need to create the custom wallet instead of like a public blockchain provide the kind of consolidated wallet like MetaMass. So in what projects gaps in the particular hyper community, we should have kind of such kind of project is kind of simplify the implementation execution of the blockchain projects. Okay. Yeah, that I think, yeah, it's those are good points. It's hard to distill that into a project that we need, but I think those are all some high level things we need to think about as we, as we produce our projects and get the demos out. Okay. Anyone else have anything they want to share on this before we move on to reviewing the labs projects? So if we go to the labs, the labs websites, let's go back down to the lab section. We'd initially identified Solane, Perrin, Business Partner Agent Orion, there's a couple of fabric things that are probably going to get absorbed into fabric. Did anyone else have any favorite labs projects that they think should be on this list that we should consider approaching and discussing with them? I think fabric operator, sorry, I didn't raise my hand. Go ahead. Yeah. So fabric operator or HLF operator, I think is a good to be considered. I think operators already mentioned here. So I think there's a two operator. I think there's one HLF operator, there's another fabric operator. I think there's two different labs. Fabric operator, fabric operations, that's what it is. So I can speak to these two. So what we're trying to do with these in the fabric ecosystem is see if we can get traction. Like you said, there's two fabric operators in the labs and then there's also a bunch of other fabric deployment solutions for Kubernetes. We're trying to see if one of these gets traction as kind of the operator that most of the community uses. And if so, these would probably get absorbed into the fabric as fabric sub projects, like Dana mentioned. So we're trying to gauge the interest of seeing if we can coalesce the ecosystem into, you know, one of these operators along with the operations console. And we'll be talking about this also in the global forum. Okay. So going from the top here, how about so like, does anyone use your, let's do hands first. Tracy. Yeah, sorry. So I did, I think after our last call went through and did some kind of ranking based on like number of PR done, the participants number of releases, that sort of thing. I think the other one that jumped to the top that isn't listed yet is the blockchain carbon accounting, which is close to the top 10 in most of these categories. It definitely is in the peer account and the participant account. And then it's just outside the top 10 for the release account. So that's another one that we might want to think about as we go through and talk about the different labs that are out there. Okay. Quick run through. They don't have maintainers. So first thing they need to do is get it up to, where does it read me? The list of maintainers. Yeah, if you check your, the bugs, I filed over a hundred issues on GitHub repos for no maintainer file. So like right there at the top. So it's very common. Okay. I think the labs don't have the same level. I mean, that's part of the process of bringing a lab into an incubation is to get them up to the standards. Okay. Kamalash, is this about the carbon or should it be? So that's the time on the carbon before we go to your question. Yes, I think this carbon accounting lab is really good because I'm initially contributor and user of this lab. And in the last two years has been significantly. And like how the grid project is for the supply chain, it could be the carbon accounting or tokenization. And best thing I think it uses all the different blockchains like fabric is there, like the reserve. Beisu and currently we are mentoring some projects, some projects in the mentors projects and bevel and cactus integration two years. So. Okay. So this is a nice example. It deploys on both chains at least. Yeah, right. That's a really good example. And even there is multiple blockchains not just the like one, there is a gorilla, there is a men net, there is a other kind of public blockchains is all the supported and that we tried. Okay. So there's one thing. And also I was talking about this fabric token SDK is also another life, which could be kind of sub-project in a fabric, I believe. Token SDK. Got many tanners, magic numbers done to those three organizations. That's good. No, no, it's all IBM, it's all IBM. It's all IBM? Okay. Still it's more than three warm bodies maintaining it, which is the critical standard for incubation. So whenever I see like a fabric only project, the critical question here is, is there a reason why this shouldn't just be absorbed by fabric? I guess that'd be my first question and it doesn't have to be, it could be independent of fabric, but is there a reason this shouldn't be maintained as part of fabric? And that might be a part of the rationale for why it's a separate top-level project. I'll let Andrew speak more, but my first comment would be unlike the, what we just talked about, fabric operator and fabric operations console. Those are definitely tied to fabric and would likely come under as fabric sub-projects at some point. The token SDK can work with other blockchains and so that might be a reason not to do that yet, but I'll let Angelo speak to that more. Yeah, indeed. So it started as something for fabric, but now, for example, we integrate already with Orion, with Hyperledger Orion, which is a centralized blockchain system, which is another lab, by the way, that can be very interesting. And technically we can interface other blockchains as well. So yeah, it was born as a fabric thing, but definitely it can deliver zero-knowledge tokens to multiple blockchains. And for instance, we already use these in multiple CDBC experimentations with central banks. Okay, so that's, I mean, that's the sort of rationale I'm looking for. There's a reason that it's above the protocol layer and that works with Orion. That's awesome. Cool. So let's go back to the top of the list and go through some of these and see if anyone's had a chance to get familiar with it. Solane, has anyone done much, looked at Solane much, worked with it, familiar with it at all? Jim? Yeah. Yeah. I haven't used that hands-on, but I think it's an interesting project. I think WASM is a new programming model. Self-share uses it for customized runtimes. It's pretty useful to have that as a project in general. Okay, so Jim sees it. Because one of the things I think some of these projects is time to start getting them to move up and to get feedback like this, I think would help some of them go through the process because as we've learned in previous examples, going through the incubation process can be, it's very easy or very hard. So positive feedback to this would help for some of these projects. Tracy, I think you have your hand up. Yeah, so I think I brought this up the last time that we talked as a lab project that would be useful. And in that time, I had reached out to Sean and asked him to put together a project proposal, which he did, but he's a little shy of submitting it without kind of some feedback from the TSC as far as whether or not it looks like something that he, that would be useful to bring in as a top-level project. I think he had potentially a poor experience the last time he attempted to bring this as an incubation project in the past. And so I think it's any sort of feedback or thoughts that we can give on this particular lab becoming a project would probably be a useful sort of thing. I do think that it has gone through a lot of changes since the last time that Sean brought it to incubation. I think that there's, you can see, like just the number of conversations that are happening in the SoLing Discord channel. It's one of the, as I go through and kind of take a look at different channels it's one of the more busy channels that exist out there. I do think that there is the increase of kind of people who are working on it, people who are using it. I see that from the proposal, there was a lot of really interesting thoughts about bringing different languages or even using it for different sorts of projects. And so to me, it seems like it is definitely worthwhile to bring this forward. And so anything that we can do to help encourage Sean in that regard, I think would be great. I realized from that that there's a, I was looking to see whether it's a slot into and I think it would fit into applications support and libraries. I don't know if it would be a top level or underneath it, but I'm gonna put it on our application support and libraries. Cool. Kamalash? So I not use the Solang, but I think when we see that this roadmap and usability, so I think it will attract the consolidated developers from the public blockchain community. And if Solang has the roadmap to support the other hyper-ledged projects like maybe like Indie or maybe Sartu or Fabrik in the future, then it could help to get the other consolidated developer in the hyper-ledged ecosystem. So I think I support to be in this project as a maybe main-level project in the future. Okay. Would a project have to support hyper-ledger DLT for to be included? Is that a question we should be asking them or just being interviewed? I think it's not necessary to support the hyper-ledger, but at least I suppose is a kind of Solang solidarity compiler which could be used by any other projects outside the ecosystem is also the hyper-ledger projects only. But I think it will fill the gap and maybe attract the quality developer outside there or maybe solve the issues in the currently solidarity language. Okay. Okay, that makes sense. Peter, you raised your hand. Yeah. So I just wanted to express support for it as well. I am a fan of the technology stack that uses specifically LLVM and Rust. And I'm also a big proponent of WebAssembly in general and also building other technologies on top of it. So yeah, I definitely support it. Jim, your hand came back up. Yeah. So I was thinking about this project. It intrigues me the level of interest where we are with the adoption interest from the enterprise side. I feel like this is a genuine contribution to hyper-ledger from a natively born project in the WebStreet space. And it wasn't, it's certainly more adopted there rather than the enterprise at the moment. And Jim, your question wasn't. Wasn't, okay. And to a question whether a project, top level project should support at least one DLT, I don't feel like that should be a requirement. A lot of the things may be that a project is already adopted in WebStreet in general, but hasn't been by any of the DLTs in hyper-ledger. But that's a point in time thing. I feel like Wazem might be one of these. I remember Besu made an attempt to support that, but walked away from it. I think maybe out of performance issues, but so there's certainly interest, but at the moment, none of the DLTs are interested in having a support for Wazem, but not me changing the future. Okay, so to get some context on the Besu E-Wazem, there's two variants of Wazem that's being discussed about for Ethereum. General Wazem and E-Wazem, and there's issues with the gas calculations and making sure that it's EVM compatible. They're trying to do some changes to E-Wazem. Early prototypes showed that interpreting EVM was actually faster than what they had built for E-Wazem, which was a layer above the Wazem. They're doing some very Ethereum-specific things such as compiling EVM to Wazem and the gas calculations. And it was really the 256-bit math doing it in Wazem that really got them. And those aren't, you know, that's why Ethereum specifically went away, but if you do things, you make smarter choices about what you're doing in your language, such as allowing native register with multiplication rather than requiring 256-bit, the performance goes up significantly. And if your blockchain doesn't have the gas calculation regime, it's a lot easier to handle. So I think, you know, we shouldn't view the failures of E-Wazem to reflect necessarily on Wazem because what Ethereum was doing was very specialized and imposed some very, very severe constraints on what Wazem was capable of for that. So, yeah, basically did Dablin, the Ethereum community at Dablin had basically never implemented it. And it's generally speaking not happening in the Ethereum community right now, but Wazem in general, like Substrate and Cosmos, it's very strong in that particular sub ecosystem. Cool. Anything else that anybody wants to see on Solange or should we move on to Perrin? Angelo. Yeah, there is always this aspect that bothers me or troubles me. That's why one in the for enterprise applications, you usually desire privacy. So privacy is a concern and also performance is a concern. So you usually tend to not have or to have as less possible execution on chain. And if you have, if you execute anything on chain, it's usually for verification of zero knowledge proofs. So I understand that for the public blockchains where everything is public, you are not concerned about privacy. This is a project that might be very, very be absolutely interesting there. But for the enterprise application, what's the benefit? I'm not completely sure. Maybe just assuming that enterprise application are not using a lot of on chain computation. If you're talking about stuff like big secrecy acts, then yeah, that the secrecy is basically required. But I think there's a lot of public uses. We're doing everything in public to be seen as a valuable item. Hart. Yeah, I was just going to agree. I think there's a lot of enterprise interest in using the public blockchain for certain things. And I totally agree with Angelo that things that need to have privacy properties are very, very difficult to do on the public blockchain and often require some of the solutions that Angelo just described. But we are seeing enterprises use public blockchain stuff. And whether you agree with that or not, this is sort of a case of the customer being right, at least I think. Oh, that's authorized. They won't do that. That's authorized then. Because one solution, I think we touched on it last week when we were finishing this of the H1. Would be to use, and this is something that I've seen in the past few weeks, trolling around the ecosystem is the use of roll-ups to get your privacy. It's basically had to use zero knowledge proofs except instead of a zero knowledge proof, you would have an off-chain roll-up. Those are called, one variance called plasma, which is a variant of the old Lightning network. But there's also layer two proofs where the data availability is not kept on the main chain, but I'm on private people, between the people who only care about it. So I'll go ahead and put that because I've heard solutions that beat around the bush on that to get kind of around it, but I think it seems to be pulled out that I think a roll-up solution would be an excellent project at Hyperledger, one we should probably solicit for. I don't have any specific ones in mind. All the ones I know are very theory-specific, but there's also layer one blockchains that are enshrining their roll-up solution into it. So I think this is valuable to make a sub-ledger that acres into another ledger as a use case that we should consider that might be one to keep an eye out for. Har. Yeah, I agree with that. I think as a K-roll-up project would be amazing and I have been actively agitating people to try to build one. I don't think it's worked, but we'll see you in the future. Okay. Jim. Yeah, I don't know if UI is represented on Hyperledger, but they've been working on Nightfall, which is interesting roll-up. It's optimistic roll-up with ZK payload. Just feel like it, from its lineage, it fits in the Hyperledger space, but I don't know if anybody has made an attempt to work with them. That's what I particularly always have a look at. I was, I know they were disappointed when Ethereum didn't adopt the BLS-12 pre-compiles and I tried to get some information from them as to what specific set of these curves they needed, that the Japan DevCon never got ahold of them. There was so much going on, but I agree, they have some amazing demos and some of the amazing stories. And just the one I saw the other day on Carbon Accounting, it was all Ethereum. So that really interested me. I think, is that all you had it, Jim? Yep, Angelo? I was wondering, can we invite companies to join the Hyperledger? Because for example, in this space of the roll-ups that is Starkware was doing really, really beautiful work and with very good theoretical background. And they have also a language called Kyro for privacy-preserving computation. That to me seems very relevant, more than other options to be honest. Even though this works mostly in the account models, so they come also with limits and they will be a bit problematic for CDBC, but definitely Starkware is doing a lot of good work. Yeah, I mean, that's how Consensus and Basis came on board, to be honest. Hart? Yeah, I was gonna say, if you know people or projects that you think would make good members or projects, like absolutely, please introduce them, please socialize them with them. I'm happy to talk to them. I think most of the staff are happy to talk to them. So yeah, please talk to people. Remember that Hyperledger is about open development. So projects that make sense are things that companies are willing to open up to outside development and have a truly open development process. But yes, please socialize it and talk to people. And if you think something is appropriate, tell them and ask them. Cool. Kamalash? Yeah, so in this JK role of I think recently, Polygon from India actually met there one of the technology open source. So maybe collaboration with them or ask them to come under the Apache 2.0 license because they recently made the open source as JK role of technology. Okay. All right, so let me get those thoughts organized a little bit. Because there's some suggestions for members to join on board. Okay. Angelo, your hands back up. Yes, just for a clarification. So ZK relapse is not that they are private. They are not private. So it's true that they are using zero knowledge proofs to compress essentially operations, but they are not private. They will reveal what's happening. So they will reveal the content of the account and so on and so forth. So actually the one that are private are called the Z-squared roll up. Then you can just for clarification that ZK doesn't mean necessarily. Unfortunately in the notation doesn't mean always private. ZK squared, sorry, ZK squared. To clarify, Angelo, you mean privacy in that whoever is conducting the transactions is still revealed, but the payload, the content of the transactions is still private, right? No, not even the content of transaction is private. So sorry, for the ZK roll up, if you take ZK roll up, they are just everything is public. It's only the aggregation that is proved so that this entity, this mediator, aggregated all the transactions in a proper way. So it's more, it's this kind of, you actually don't need, for this, you don't need actually the zero knowledge proof. If you really want to hide also the content of the transaction, who did what? Then it's much more complex, the operation and usually it's called the ZK squared roll up. So you apply two times to ZK. But it's unfortunate than the terminology because if you talk about zero knowledge, you are implicitly saying that it's also private. But for what I read the literature, it's not the case with simple ZK roll up. Probably worth a different time for discussions. My understanding is the entity that conducts the roll ups are not protected unless you apply any anonymity like Tom Lee, for example, but the content itself should be a private. But this is probably not the right form to discuss this. Yep. I think there should probably be a table on one of our discussion days in the hyper-logical forum on roll ups. I don't know who's got that part of the program community together. In past years, they've had at the lunch area, some days they set up specific tables for specific topics. So I think this would be an excellent one. Okay. So we've kind of taken a segue to non-labs projects that might not be on the labs list that would fill in project themes. Before we go back to the labs, are there any other project ideas that people think that would be good for Hyperledger that we don't have in labs right now? That we should specifically solicit for. We have the themes that fit into the themes, so that there's any specific from a theme that we are in more needed than anyone else. Okay. So I think we were at Perron. I hope I'm pronouncing that right. Anyone familiar with this lab? Antelope. I don't know. Then I wanted to mention another project that I think comes from consensus. It's, I think it would be a nice extension to HRSA because it's a general purpose zero knowledge proof system. It's called the GNARC. It's a very powerful library. GNARC, G-N-A-R-K. ARC. Oh, GNARC. Yeah. Yeah. It's a very poor part from consensus, I think. It's a very, very powerful library for the general purpose zero knowledge proof system. So I think it would be very complimentary to HRSA. Very, very good library. Okay. Grace is here. Grace here is that. Grace will talk to with that, see if that's appropriate. So we don't have to go too far to ask anything else. So Perron, anyone familiar with Perron? Anyone used it? It looks like mostly a two-member project right now. The occasional third. Yeah. So Perron is like a recursive lightning network. If that makes sense, that's probably the fastest way to describe it. Okay. Way to do secure channels and use the blockchain to prove it, but you don't keep it on chain, you only keep it between the two partners. That'll make sense. Well, the idea is that, you know, sort of if you can bootstrap on the trust of other people. It's a very nice concept. It has like a formal academic paper and everything. That is interesting. Okay. It does have semi-regular. Yeah, that's pretty regular commitment for the number of people there. But it's interesting that no one on, except for Hart on the TSC is terribly familiar with it. I wonder if we should ask them to do a presentation to the TSC, if that would, maybe that's one option we could do. Angelo? Yeah, I'm also familiar. I spoke also with the, I not only read the paper, the literature, but also I spoke with the guys behind Perron and also suggesting recommending them to push more for becoming a project. I also find very interesting. I like a lot the concept of virtual channels. Yeah, very nice. If they can get also an implementation on Fabric, that would be super cool. Okay. So I think probably the best thing there is if we need to get Perron, let me write this down, have Perron do a presentation so we can get more familiar with it. That might be a prod they need to decide to become an incubating project. Okay, this is partner agent. Again, oh, just quickly. I can reach out on the, I think they have a Discord channel. I can reach out on Perron to see if they would like to set up some time with the TSC to schedule a presentation. Okay, I was writing it down, but if you're gonna take the action item, definitely. Sure, I'll take it. Cool. I'm just writing on my notepad instead of on the screen, so that's why I didn't see anything. Aries, cloud agents. Anyone worked with business partner agents? That's not named Hart? So I haven't worked with it per se, but I do think it has some interesting ideas around it. I think there is this idea around organizational type wallets and how we deal with credentials that are issued to wallets or from wallets, I'm sorry, to organizations or from organizations. I will say that I also, I don't know if it was in the chat. I think it was in the Discord chat. The British Columbia government also has a source base called traction, which I believe they're thinking about taking and bringing to Aries, and I think it is similar to business partner agent, and I would love to see those two communities work together. My guess is that at some point, this might be something that comes into Aries as a kind of sub-project, if you will. I think Aries is made up of many different types of projects, and so I think this could be something that we look at from that perspective, but I think it really requires the connection between the communities that are working on the same sort of thing. Okay, and I think we're reaching diminishing returns, but let's just finish off with Orion. Has anyone finished, has anyone worked with Orion with maybe a good candidate to get proposed to either present to the TSC or propose a project? Because I think that also leads to another question, is how often should we ask the labs to say, hey, you've done cool stuff, do you wanna share it publicly? So I think that could be a good step to encourage them to continue growing, to show what they've built and get encouragement feedback from TSC members or other projects. So anyone work with Orion? Okay. They did do, I mean, I'm thinking of sharing when they were publicly, Orion did do a meetup recently, I can share, I can get the recording of that and drop it in the TSC channel, but I mean, there is interest from labs in presenting some of their work. So I've reached out to some in the past, and Orion was one who was gonna raise their hand and say, yeah, I'll share what we're doing. Angela? Yeah, just to say that obviously I worked with Orion, it's very simple, the nice thing is very simple to set up, very simple, whereas compared to other blockchains, it's super fast, super fast. Kamash? So my work about the Orion, I think there are many such use cases where we don't need the decentralization, but the kind of distributed nature is required. I think Orion is filling that gap. So especially in the government sector, quickly I had to call with sometime back with the Orion mentor, Orion mentor and contributor and how Orion could be the good use project for the use cases in the, especially in the, where we need the, we don't need the decentralization technically. Okay, all right. So with 10 minutes left, I guess the ask here is, are there any things you need to revise before we push a final publish on the projects and themes or any labs or a non-labs projects we want to solicit? And do you think the task force, I guess this is a request, does anyone think that there is more for the task force to do or can we call it a completion? Is there more work that needs to be done? Okay. Angelo? Could it make sense to have, I don't know, a final feedback now that there is the Habitology Global Forum to take the chance there to ask the community about feedbacks and... That's an excellent place to do it. Yeah. Get feedback on recommendations, project. Projects that they would like to see or something that they found useful or something that we missed as well. Okay. So I'll take that as the next step for the task force to make it available for Hyperledge of foreign people. And then depending upon the feedback we get there, possibly putting it up and putting a lid on it. I don't think we need to wait for the forum itself. I think that outreach could happen today or this week. Yeah. So would that be an all members email? Would that be the message and discord? What would that look like, Ryan? I'll have to huddle. I feel like that would be an email but we might be bombarding people with too many emails. It might get attached to another email. Let me huddle with David and Karen and see what the best way forward is. I wonder if we should... Yeah, I think that is the dilemma because I think email may be better because not everyone's on Discord and Discord's tend to be projects skewed rather than participants who don't have a project that think it might be a gap that they're not in. Yeah. We do have a Discord channel or group for people that have signed up for Global Forum but there aren't that many people there because I haven't taken the task to make sure that every single person who's signed up has the right tag. Yeah. Okay. All right, so get back to me on what you think the action might be on that. I can draft email. I don't think I have access to send on those lists which is probably a good thing. You wanna control that? Cool. Well, if there's no other discussion items, give people seven minutes back. Thank you. Thanks, David. Bye-bye. Bye-bye.