From 3be98149f0b7c0188eacf57fcc4571d360d7ed2e Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 23 Jul 2024 17:56:23 +0000 Subject: [PATCH 1/4] Create meeting notes for Sig-economics #18 (#630) * Create meeting notes for Sig-economics #18 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 018-2024-07-03.md added transcript chore: add recording link Signed-off-by: Drinkwater * Update 018-2024-07-03.md add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-economics/meetings/018-2024-07-03.md | 217 +++++++++++++++++++++++ 1 file changed, 217 insertions(+) create mode 100644 sig-economics/meetings/018-2024-07-03.md diff --git a/sig-economics/meetings/018-2024-07-03.md b/sig-economics/meetings/018-2024-07-03.md new file mode 100644 index 00000000..8856adcc --- /dev/null +++ b/sig-economics/meetings/018-2024-07-03.md @@ -0,0 +1,217 @@ +# Akash Network - Economics Special Interest Group (SIG) - Meeting #18 + +## Agenda +- Discussion on Inflation and Staking APR (Cheng Wang) +- Community Pool Liquidity on Shade Protocol +- Proposals Update +- Transparency Reports for Community Pool Funding +- Dashboard for Provider Incentives + +## Meeting Details +- Date: Wednesday, July 03, 2024 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://gtkqa2srpm2ve37fgnzh4bvk2ajdzxzdh5owwd3vaqvtg5pncdaa.arweave.net/NNUAalF7NVJv5TNyfgaq0BI83yM_XWsPdQQrM3XtEMA) +- [Transcript](#transcript) + +## Participants +- Cheng Wang +- Julius Haus +- Maxime Beauchamp +- Poroburu +- Scott Hewitson +- Tolguy Ture +- Tyler Wright +- Zach Horn + +## Meeting Notes +- **Welcome and Overview:** +- **Scott Hewitson** + - The last meeting was rescheduled to a couple of weeks ago, leading to fewer updates this month. + - Scott Hewitson introduced the agenda and mentioned that Cheng Wang had topics to discuss. + - Previous meeting had discussions on inflation and the current staking APR being over 20%. + - Concerns were raised about the high APR, and Cheng Wang was asked to discuss it further. + - Previous chatter about using the community pool as liquidity on Shade Protocol was mentioned. + - The Shade Protocol presentation was noted, though Scott was not present for it. + - The deployment from GitHub/GitLab to Akash Network on Console was discussed. + - This proposal had been through many talks in special interest groups and steering committees and has now passed. + +- **Proposals Update:** + - Since the last call, several proposals have gone up, including Q3 events and community support. + - Dashboards showing the status of these proposals are available. + +- **Transparency Reports for Community Pool Funding:** + - A new [repository](https://github.com/akash-network/community/tree/main/community-pool-spend-reporting) in the community allows anyone receiving community pool funding to add transparency reports. + - Scott mentioned adding Overclock’s 2024 reports and plans to add more historical data. + +- **Dashboard for Provider Incentives:** + - Scott mentioned creating a dashboard for provider incentives, with a direct link to be provided later. + - Details about the amount of AKT off-ramped, liquidated, committed, and expended are tracked. + +- **Further Discussion by Cheng Wang:** + - Emphasized the importance of accountability and transparency for every unit of AKT spent. + - Mentioned plans to formalize the core team and engineering contributions, with more details to come in the next quarter. + - Discussed the inflation issue, proposing to lower inflation and increase the community pool tax from 40% to 50%. + - Suggested reducing the inflation max parameters from 20% to 15% and the min from 13% to 10%. + - Emphasized the need for provider incentives and the formalization of these programs. + - Discussed the timeline for circulating the proposal and gathering community feedback. + - Addressed future considerations for the community pool tax rate, with potential adjustments based on network needs and AKT value. + - Mentioned that APR projections will be circulated for community review before submitting the proposal. + +- **Community Pool Size Context:** + - Scott provided context on the current sizes of other community pools: 52 million ATOMs, 37 million OSMO, and 26 million AKT. + - Highlighted the importance of funding the community pool for future Akash network needs and incentives. + +- **Provider Incentives and Verified Compute:** + - Discussed the importance of provider incentives and the upcoming proposal for verified compute. + - Encouraged community members to review and provide feedback on the GitHub discussion regarding [verified compute](https://github.com/orgs/akash-network/discussions/614). + +- **Open Floor for Questions and Comments:** + - Maxime Beauchamp asked about the long-term plan for the community pool tax rate. + - Cheng Wang explained that while 50% is the target for the foreseeable future, the rate could be adjusted based on network needs and AKT value. + - Maxime also inquired about the projection of APR, to which Cheng confirmed that projections will be circulated for community review. + +- **Closing Remarks:** + - Scott thanked everyone for joining and encouraged them to participate in discussions on Discord and GitHub. + - Cheng wished everyone a happy Fourth of July and signed off. + +## Action Items +1. **Scott Hewitson:** + - Provide the correct link to the dashboard for provider incentives. + - Continue updating Overclock’s transparency reports and add historical data. + - Post meeting notes on GitHub and monitor for any further discussion in the community channels. + - Follow up on the community pool liquidity usage on Shade Protocol and provide updates. + +2. **Cheng Wang:** + - Discuss the inflation and staking APR concerns in more detail in the next meeting. + - Circulate the proposal on GitHub and gather community feedback before submitting the governance proposal. + +3. **All Attendees:** + - Review the new repository for transparency reports and add any relevant reports. + - Check the dashboards for the status of ongoing proposals and provider incentives. + - Provide feedback on the verified compute proposal on GitHub. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Scott Hewitson: All right, m everybody. Welcome to this month's installment of Sig economics economics and the last month was rescheduled. So it was only a couple weeks ago. So there may not be a ton of updates, but I know Cheng has a few things he'd like to talk about as So let's start with last time. We had some questions about there's some chatter about inflation, current staking APR is over 20% Some people are concerned that that's too high and I think change, discuss that a little bit as well because we put some thought into it as well. + +Scott Hewitson: And then I know last time there's some chatter about using some of the community pool as liquidity on shade protocol. I know they presented at steering committee actually wasn't present for it, but we'll see how that goes. Then from The Proposal side, so we since the last call couple proposals. had gone up the Q3 events and Community Support, those are ongoing programs. There's just the quarterly requests and we have a dashboards that kind of show the status of all those Actually, I'm on that point here is a link to we created a little repo and community that is just an area for anyone who receives. + +Scott Hewitson: Community pool funding basically you can do a PR and add, if any transparency reports anything you want to report from the money side. I went ahead and added some stuff from overclock side for 2024 probably add a few more things going back further, but just to get it kicked off a little bit. So anyone who's receiving funding and wants to report on Feel free to add that there. + +Scott Hewitson: and then what else passed so there was the deployment from GitHub gitlab that bucket to caution Network on Console. I know that one passed as well and that one had been in many talks in Special interest groups working groups and went to the steering committee. So that one passed. And I don't think there's any other major things since the last call. Yeah, I think that's about it. So I'm gonna kick it over to Cheng. I'd like to first talk about quick recap on pit because we have a dashboard off for that and then the inflation discussion and then anything else you'd like to touch on chain. + +Cheng Wang: Yeah, did you want me to touch on the PIP stuff first or sorry, I wasn't clear. + +Scott Hewitson: I'll just give a quick synopsis. So the past call I said I would be making a dashboard for provider incentives on That page I sent earlier as well. But here's the direct link to it. no, that's the wrong one. + +Scott Hewitson: I'll get that truck then but basically, there's a certain amount of akt that have been off ramps liquidated. there's certain amount that's been committed and expended. So it's just going to be tracked there. And you can take a look at it yourself and have any questions feel free to Cheng go ahead. You can go ahead with the other stuff I'll get the correct link for the dashboard. Yes. + +Cheng Wang: Sounds good. Yeah, so just a quickly reiterate there the reporting Link in the + +Cheng Wang: Akash Network repo there just to kind of put in front of everyone and I want to I think celebrate this really big I think not really miles somebody we said we would obviously the core team and this is the standard that we want to uphold right for the open network and just be responsible accountable for every unit of akt that comes out of the pool should be reported because it is a public good fun and essentially right and so it should be reported as such and we kind of want to lead and we do rather want to lead in this effort and show that this is the sander we want to adhere to in a standard we want to set and all the protocols out there, we can name them everywhere and there's a little lot of fun coming out of a big protocol that we all know, I think last yesterday or regarding Community spend and all that kind of stuff. So it's important to highlight especially now like accountability and ensuring that we are spending and a very responsible way and manners that directly or indirectly. + +00:05:00 + +Cheng Wang: Benefit the network in the most obviously responsible fashion possible. And of course reporting against that + +Cheng Wang: So if there are any thoughts questions, please comment here or in any single working group that you feel is appropriate the other thing like dovetailing from this is as we kind of move forward and as the scope of what everything we're working on continues to expand and build we will be formalizing the core team in concert, of course with the community contributors a little bit more as far as engineering contributions, right? I think Julius on the call Max obviously part of the core team now formally, directly part the community came in this way is from lasting a lot of the engineering and product contributions there for as far as they reporting against the community pool and drawing from the community pool to continue to fund development. So we're going to formalize that a bit more going forward probably in the next quarter. I want to thank you for but definitely rolling into 2025 something really front and center. + +Cheng Wang: to really + +Cheng Wang: put structure look forward to details around that so that's for community pool spend as far as engineering resources specifically to look forward to the second item is as far as the inflation that Huey touched on Wright currently the market though is doing well / sideways at some points in time. We definitely understand. The inflation rate is a little bit high. So We put together quite a bit of thought on already and we'll of course circulate the spreadsheets that we've historically have circulated modeling out what ultimate look like, but will probably look somewhere in the vein to fold two kind of components. Right one is lowering inflation is increasing community pool to the desired level of 50% So currently that parameter sits at so 40% and inflation and currently goes to the community pool and I think every bit of money that's been spent out of + +Cheng Wang: That has been extremely successful. I would say we're all relative to what their goals were right from events to Community Support to development of different features capabilities and just the cloudnos team Predator team Acquisitions all that kind of stuff. + +Cheng Wang: So we're gonna propose increasing community pool tax from 40% up to 50% That's one and then two is going to be changing the inflation max parameters. I think currently men sits at 13% and Max it's at 20% And what we'd like to do is probably reduce Min down from 13 to 10% and then Max from 20 to something like 15% And so that should bring down inflation. Just the notch. We don't want to obviously over Justin do something too crazy, So that's the I think initial proposal here and hopefully there's a good amount of support I think to support is already there as far as contributors that have chimed in the last economics, which I wasn't able to make but yeah, that's as far as inflation as well as community pool goes and I think funding the community pool, of course. + +Scott Hewitson: This put it up. Obviously. We'll throw. The tax code. Yeah, that's Max's question tax. Go to 50% Cheng. + +Cheng Wang: Yeah, that's right. + +Scott Hewitson: Is there a reason why 40% versus 50% or what's the rational there? + +00:10:00 + +Cheng Wang: Yeah, so the reason for 50% that's the marker we think we want to get to and then we talked about in Greg's talked about it and I forget we in which calls I probably a Syrian committee here or there to get it to 50% and that'll be the ongoing rate going forward to well. + +Cheng Wang: Kind of answers itself, We've been finding the pool for a little bit and… + +Cheng Wang: It does a couple things one continues to ensure the pool as well funded for all the issues. + +Cheng Wang: everything we've done has been through the public eye in a lot of people… + +Cheng Wang: We've done plus additional ones that are going that will be pushed in a future that we can't even in Envision now,… + +Cheng Wang: who I think push and human HQ, right submitting proposals on their own to get funded for various initiatives. + +Cheng Wang: right? So one of the biggest things that I forgot to mention is provided incentives programs comes out of this right and… + +Cheng Wang: So the community pool I think is doing an outstanding job and… + +Cheng Wang: then 10 and… + +Cheng Wang: it's currently quite well funded at this point in time. + +Cheng Wang: incentives that's not something we've yet put forward. + +Cheng Wang: So we want to definitely continue to build that I know there was a little bit of hand ringing when we did some marketing initiatives with coinbase that the pool would deplete… + +Cheng Wang: Yeah, we've done little scattered things here and there but we want to formalize that a lot more of course going forward. That's one bit. So the … + +Cheng Wang: but as we noted historically that wouldn't come close to the pleading and… + +Cheng Wang: so 50% is the marker we want to hit. I think that's kind of a good point to be at a 50/50 split between inflation emissions to stakers. simply by virtue of emissions as well as the increased Slash validators, of course and then 50% to the community pool to continue to fund that effort. + +Cheng Wang: + +Cheng Wang: and in terms of sorry timeline wise I think probably next couple of weeks. We'll circulate of course as is the discussion on GitHub and then have that circulate for maybe a week or so gather Community feedback and then ultimately submit the governance proposal incorporating feedback from the community. + +Scott Hewitson: Yeah, go ahead next. + +Maxime Beauchamp: Thanks for the explanation and I guess Is the plan to stay at 50% forever or is there a plan to eventually drop it or make it? higher + +Cheng Wang: That's a good question. The short answer here is we don't know what the future holds I think 50% in the foreseeable future. Let's just say call it the next year or so, right and don't hold my feet to the fire. There is probably somewhere we want to be of course. These are all governors parameters that can be changed if let's just say the community pool gets funded to akt goes to 100 bucks. I'm sure everyone love that and the community pools like a billion dollars or something like that. I'm sure we could bring that right down a little bit right especially if the use cases for the community pool aren't necessarily eating into the balance in any significant way. Obviously, we all of us right not just the core team but every single Akash token holder and then definitely stake her has a literal, stake and say in this doesn't want the pool to just sit there idle without generating some sort of return. + +Cheng Wang: To the network ultimately, So I think it's ultimately going to be a bit of a balance and we'll have to see how the community pool is used going forward. Obviously all that stuff will be super public and undergo the same level of scrutiny. it's always been on there and relative to what a lot of factors. I'm sorry to kind of give you a cop on answer, but I'll say for the year. Probably stay at that rate going forward between emissions between what the macro is doing between what the micro needs specifically of the network are other things that we can't really forecast. these things are presents for reason and it can be adjusted as such. + +Maxime Beauchamp: Yeah makes sense. And do you have a projection of the APR? That would go. + +Cheng Wang: Yeah, we're putting that together. it'll be circulated Huey or Scott and… + +Maxime Beauchamp: Okay. + +Cheng Wang: I are putting that together and that'll be circulating. So yeah, don't worry. It's not like we're discuss it here and then we'll put The Proposal on chain. + +Maxime Beauchamp: I know you did that in the past you put a proposal it would projection and stuff. So. I will. Thanks. + +Cheng Wang: Exactly. It'll all be there 100% good questions. + +Scott Hewitson: And I dropped in the messages just to give people a rough idea of community pool sides of silly atoms right now is worth 52 million Osmos were set 37 million. We're done at 26 million. So I think at some point. We probably don't need to keep filling it. But yeah, those are just like cops in the space to give people an idea. + +Cheng Wang: yeah, and then just to + +Cheng Wang: Put it into a little bit of person. Thank you for that here. That's extremely helpful and in additional bit of context as we look forward is the rate at which we were requesting or the core team and the community at large has been requesting funds through a caution Network. It's hard to say that's going to be the status quo. Let's just say for 2025 and 2026. Let's just say right because as the network continues to grow as it attains further adoption further notoriety and as tool sets expand right there will be additional needs to expand that and of course that's just gonna require more funding from the network, right and provider incentives. That's not forget. This is literally two phase three hadn't yet been rolled out for various different reasons of technical capabilities right verified compute stuff like that by the way went on GitHub discussions. I think was it? last week Wednesday, and we're looking to + +00:15:00 + +Cheng Wang: Push that on chain sometime today right here. Correct me if I'm wrong there. So there are a lot of things. + +Scott Hewitson: Yeah the next day. + +Cheng Wang: Yeah, a lot of things coming down the pike that the community pool will be required to ask to fund and provide an incentives especially as we kind of in this phase one right is really an initiative to help us learn. what chipsets are in demand which providers and kind of start to chip away at that and we've gained a lot of know-how and an education quite frankly around how that process work. So we'll be in phase but phase two pit zero three going forward. Those will obviously require additional resource from the community pool to build up the resources available in the network. + +Scott Hewitson: awesome Thank you for all that flavor and color on all things. Yeah, I was gonna say I was gonna ask about the verifiable compute. I dropped it in. Here's a discussion 614 and since coming from Surah from University of Texas. So it feel free to put in any notes comments. It's been up for a little over a week, I believe and they spoke it steering committee. But yeah, if you have anything you'd like to add to it, please please do. Let's see. I think that's all I had from my side on items that I'd like to touch on or for you to touch on chains. Right? Do you have anything else you'd like to add? in general + +Cheng Wang: Yeah, I mean any questions that anyone has regarding the GitHub discussion on verified compute, this is a good place to ask any initiatives that you think might be on the horizon or not, or if you have any ideas right for the community pool for everyone here and also anyone reading or listening to this afterwards because I know it's just the lot of us here. Please chime in let us know make your voices heard. + +Scott Hewitson: We don't have Andrew G here to ask my token question, All Okay, so I anything I think we can probably cut things short. I'll give one more chance if anyone wants to bring up anything at all. Stay it now or wait till next month. + +Scott Hewitson: All thank you everyone who joined in today and those that'll be watching this at a later time. I'll make sure to have notes up on GitHub and let us know in the meantime between calls and see economics and Discord if we can got anything that pops up or you don't feel comfortable talking about it Alrighty with that. I'm going to end the call or in the recording and we'll see everyone later. + +Cheng Wang: All right, see everyone in the metaverse. Enjoy your fourth of July for everyone. + +Meeting ended after 00:18:48 👋 + + From 548297e7c15dbde128281ad54e57d012cba10464 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Wed, 24 Jul 2024 16:34:57 +0000 Subject: [PATCH 2/4] Create meeting notes for sig -providers #18 (#635) * Create meeting notes for sig -providers #18 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 018-2024-06-26.md added transcript chore: add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-providers/meetings/018-2024-06-26.md | 204 +++++++++++++++++++++++ 1 file changed, 204 insertions(+) create mode 100644 sig-providers/meetings/018-2024-06-26.md diff --git a/sig-providers/meetings/018-2024-06-26.md b/sig-providers/meetings/018-2024-06-26.md new file mode 100644 index 00000000..ce247a82 --- /dev/null +++ b/sig-providers/meetings/018-2024-06-26.md @@ -0,0 +1,204 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #18 + +## Agenda +- Welcome and Introductions +- Follow-up on Praetor Acquisition and Integration with Akash Console +- Provider Builds and Upgrades +- Damir Simpovic's Presentation + ## Meeting Details +- Date: Wednesday, June 26, 2024 +- Time: 08:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + +## Participants +- Andrew Mello +- Andrey Arapov +- B S +- Damir Simpovic +- Deval Patel +- Jigar Patel +- Rodri R +- Scott Carruthers +- Tyler Wright + +## Meeting notes +- **Welcome and Introductions** + - Tyler Wright opened the meeting and welcomed attendees. + - Recap of last month's discussions on the Praetor acquisition and next steps for integration with Akash Console. + +- **Follow-up on Praetor Acquisition and Integration** + - Tyler Wright discussed ongoing work and next steps involving Jigar Patel and Deval Patel around console 2.0. + - Encouraged attendees to watch the detailed video from the SIG clients meeting for more information. + +- **Provider Builds and Upgrades** + - Tyler Wright mentioned Scott Carruthers' major changes to provider builds and the ongoing testing involving community and core team members. + - Andrey's testing contributions were highlighted. + - Action items related to provider build upgrades and specific testing were noted. + +- **Console 2.0 Updates** + - Encouragement to review the SIG clients video for detailed insights into console 2.0 and its short-term focus areas. + +- **Damir Simpovic's Presentation** + - Damir Simpovic shared progress on deploying Prometheus and Grafana using Helm charts on the Akash provider. + - Demonstrated the current functionality of the dashboards and monitoring tools. + - Discussed the overutilization of memory by some Akash services. + - Mentioned plans to clean up unnecessary features and improve deployment. + - Invited community contributions and offered to start a GitHub repository for collaboration. + +- **Feedback on Damir's Presentation** + - Andrew Mello provided feedback emphasizing the importance of having both internal and external monitoring solutions. + - Highlighted the need for external checks to ensure cluster accessibility even during outages. + +- **Additional Updates and Discussions** + - Andrew Mello discussed the Akash mining project and the deployment queue, which has been finalized and finished. + - Mentioned that some providers might experience full CPU utilization as part of the testing and deployment process. + - Encouraged providers to participate in GitHub discussions to voice their thoughts and feedback. + +- **Open Floor for Discussion** + - Damir Simpovic mentioned that the user facing issues is learning Kubernetes and is receiving step-by-step help from the community. + - Tyler Wright discussed ongoing updates to documentation for clarity on provider audits and support. + - Encouraged attendees to look forward to upcoming working group meetings for the Akash website and documentation, as well as the steering committee meeting. + +## Action Items: +- Track provider build upgrades and ongoing testing via the product and engineering project board. +- Attendees to review detailed updates from the SIG clients meeting. +- Damir to create a GitHub repository for the Prometheus and Grafana deployment project. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to providers monthly meeting number 18. It is June 26 2024 During the special interest group for providers the Akash Community discusses anything related to the provider on Akash, at the last month's meeting there was a discussion following up on all things happening with the Predator acquisition and next steps as an integrate with console. + +Tyler Wright: There was some follow-up discussion around the work on that. Jigarette and Deval are doing around console 2.0 during sick clients yesterday. So again, there was much detail that went into next steps and how Prater is going to be involved there. I'll give some time to the Prater team to talk a little bit about it here. But again, I urge anybody that wants to go into the details to watch the video that will be available shortly from sick clients just yesterday. After that damir had something that he wanted to share and then I wanted to open it up to any other discussions that anybody wanted to have. + +Tyler Wright: But again, I'll just get it started Digger if there's anything that you wanted to mention in terms of how things are going greater as it stands today and some of the next steps, or Deval feel free to chime in. + +Tyler Wright: Thank I'm gonna drop in the issue that's been created as of tracking around. Some of the provider builds upgrades have been happening. I know that again Scott made some major changes to how providers are built and has connected members of the community as well as members of the core team to test these things out. There's also again, I'll drop in the chat. + +Tyler Wright: A number of items. I've been put together by Andre over a little while in terms of testing that is now underway and this testing that jigar just mentioned. So feel free to continue to track a number of items in the product and engineering project board related to this. I think there's one in testing around the provider build upgrades and then again there's a company issue that lays out all the specific testing that's going on related to that issue. + +Tyler Wright: Cool again, I would urge anybody that wants to dive deep because Jigar, the ball the Maxes spent some time yesterday during sick clients. I'm going through what's going on next in a little bit more detail and more detail around console 2.0 and some of the five main areas of focus in the short term. + +Tyler Wright: Cool, if there's no questions there then we'll continue on with the agenda. I know damir had mentioned wanting to spend some time to discuss something. So I will hand the floor over to damir to talk a little bit about something that he's been working on. + +Damir Simpovic: All right. Thanks y So share my not screen, but just say + +Damir Simpovic: just the window. + +00:05:00 + +Damir Simpovic: can you guys see my window all… + +Tyler Wright: Yes. + +Damir Simpovic: so I just started working on it maybe a few days ago. So basically what I found was that there's a Prometheus and grafana Community film charts already available for deployment on the kubernetes cluster. And I toyed around with it and managed to deploy it on your cash provider. so not everything is working yet I just basically started working on it, but most of the features do work, so if you want to + +Damir Simpovic: Actually, let me show you grafana dots Euro. - ai.net so basically yeah, it's running on my test provider Euro ai.net. And the dashboards are already created basically, so they have been pulled by Helm charts and they've been automatically installed. + +Damir Simpovic: Yeah, I will work on cleaning this up a bit because we don't need all of them. But yeah. most of the stuff already works + +Damir Simpovic: it's super simple and Yeah. For instance I don't know the networking. Stuff already works you can sort by. + +Damir Simpovic: by namespace and see which pods actually Consumes what amount of traffic is being consumed but by which pod I don't know. Some stuff doesn't work some of these dashboards doesn't work yet. But yeah, I will clean this up. So yeah, if you want to test it I made you can go to this URL. I will leave it running. And I created the test user which is username and Both are test user. So you can see for yourself. So yeah, there you go. + +Damir Simpovic: Yeah, if anybody has any desire to help. And contribute. Yeah, please do. I think it would be. A very efficient way of Basic monitoring tools for providers. There's also the alert manager here. It's also automatically installed basically can be configured to send alerts about provider. basically whatever we configure it to ert. So yeah on Discord on email. wherever So yeah, there you go. Not much to show yet. But yeah, it does. + +Damir Simpovic: It does work. So yeah, there you go. Thank you. + +Damir Simpovic: it's actually very good that you brought this up… + +Andrey Arapov: Thank you. + +Damir Simpovic: because I didn't know this until I actually tested this but some of the Akash Services provided pods are actually over utilizing the memory. So basically let me see where they find that. + +Damir Simpovic: memory utilization 1800 percent so basically some of the ports are basically over utilizing the memory. So yeah. I think it's a Akash node. That's all utilizing. So yeah. + +Andrey Arapov: It's interesting and interesting coach something definitely dig into and we could install it in more providers perhaps just to compare, the behavioral and it's also good to track it whenever we released a newer version of node software kind of compared with previous traffic instrument that previously we had the issue open by Andrew Mello and he's in the goal accident Thanks for opening it up that he noticed, the traffic Spike. So it's definitely good thing to have things. + +00:10:00 + +Damir Simpovic: Yeah, I'll start a GitHub repo for this so. Basically on my own GitHub if anyone wants to take a look or whatever. feel free + +Andrey Arapov: Yeah, cool. I think I'll just take some provider probably try to deploy there. + +Damir Simpovic: I'll deploy first on your plots. Basically, I'll test on this provider on this which it's production but nobody's using it intentionally. or the first Production really? Let's call it version room. I'll test it on europods and go from there. + +Andrey Arapov: Yeah, in the end of the day, it's just in all the metric so it's easy to kill it because I think it's been deployed this whole chart namespace you can just destroy it anytime, right? + +Damir Simpovic: Yes, exactly. The helm charts is actually being maintained by the Prometheus community. And they're open source. You can just take them and modify them. we like but they work as they are. I only change a few things. I added the English controller. And yeah not a lot of work has been done from on my part yet, but + +Andrew Mello: Hi guys, and hi damir. Thanks for taking a look at that. I have a little bit of feedback just from some experience with this. It's a question of really what is the problem the dashboards are looking to solve if you're looking to make a public dashboard for the cluster that's going to be available on a domain name. That is a good solve for it. However, if the cluster goes down, right or there's no network connectivity, then it doesn't really solve the problem for the user checking the status of the cluster. Right so you can look at that as a partial solve for kind of uptime and status but it still is really important to have an external public check basically of your accessibility on your ports and your endpoints for your cluster as So doing that against eight four four three, for example from an external check it's + +Andrew Mello: Really important and that's something you should still definitely think about and kind of think through here as you're thinking through the solution because the dashboard you have worked great when the Clusters alive, but if the cluster is not accessible or there's an outage or the power goes out or the internet goes down. Then that is not gonna really do much or help from the outside perspective of… + +Damir Simpovic: There are no absolutely I agree. + +Andrew Mello: what your provider looks like. So I was just sharing this… + +Damir Simpovic: Totally I think there is no dual be all solution,… + +Andrew Mello: because again on my clusters, for example,… + +Damir Simpovic: honestly, so this part would actually be Just a part of a providers monitoring. + +Andrew Mello: there's always public dashboard. And then also again there are solutions for that kind of more local dashboard that would show if the cluster is up and running that is a nice to have… + +Damir Simpovic: Let's call it the stack. + +Andrew Mello: but you can't always rely on it basically and… + +Damir Simpovic: And it will be completely optional,… + +Andrew Mello: you can always rely on the external check. + +Damir Simpovic: . + +Andrew Mello: So just something for you to think through as you continue to develop that Sure. Yep. Got some feedback. + +00:15:00 + +Damir Simpovic: I mean, yeah. Thank you. + +Andrew Mello: Just some thoughts. Yeah again great great job. + +Damir Simpovic: Thank you. Definitely. I agree with everything he said. + +Tyler Wright: Excellent. + +Tyler Wright: Yeah, our message in the chat. Thank you for that. Damir. Are there any other questions or comments and Andrew? Thanks for that feedback. + +Tyler Wright: All I wanted to see if there's anything else on the provider side that anybody want to discuss or share again. We got an update in depth yesterday in Sig clients about console 2.0 and some of the work that will be involved from prador in that console 2.0 work and then we got again another update from jigar today damir gave a demo on some work that he's been doing around cluster monitoring, but I want to see if there's anything else that anybody wanted to discuss on the provider side. Go ahead Andrew. + +Andrew Mello: Yeah, hi guys. So since we all last spoke or you heard from me one of the things that would affect basically everybody on this call and you may have noticed that a couple weeks ago, but a cost mining is well underway, and in the process of building that I have finalized and finished the deployment queue and what that means is some of your providers you may have noticed at one time or another were becoming completely full topped off and that's one of the actual effects and benefits of the queue is that it can size and right-size deployments to the available resources on a given provider. So again, some of you may have noticed every CPU getting full, that was by Design in the testing of the queue. So again, just a heads up to the providers that + +Andrew Mello: when that Q runs you can expect a lot of deployments usage and leases basically coming from it. So I just a heads up there and normal activity from my end. + +Tyler Wright: Excellent. Does anyone have any questions on that from Andrew? + +Tyler Wright: All there's no active discussions that I see that affects providers again. I would ask that anybody that wants to get involved in discussions on GitHub do so to make your thoughts heard, but there's nothing that I can generally see it seems like everything is fairly business as usual on the provider side. I have seen this one user and MF having some real issues, but getting some support from the community and members the Insiders. Go ahead damir. + +Damir Simpovic: Yeah about this user. He's basically learning kubernetes. So yeah, don't take it too seriously. + +Tyler Wright: Yeah. Yeah. No, I know that documentation. Can you get reference? I think he's just getting literally step by step help hand holding from the community. So again, I do appreciate that. I did want to see if there's anything else on the provider side that anybody wants to discuss. We did talk a little bit on the six support call about updating documentation to make it very clear in terms of where some of the provider audits should go. That's something that is continuing to be handled. Again. There's another way that'll pass through soon. But again, we talked about that already during Sig supports a lookout for just some documentation updates as well as those that are insiders at the next meeting. We'll just do some clarification to make sure that it's very clear on where to send people for various things. + +Tyler Wright: Outside of those topics. Is there anything else that anybody wants to just discuss? Otherwise again, I'll let you all go and we have the working group for the cash website in docs to look forward to tomorrow as well as the steering committee, but Anything else anybody wants to discuss before I let y'all go. + +Tyler Wright: Terrific. again much appreciate the updates from Jigger Deval damier Andrew appreciate everyone's time on this call today. yeah take some time back and I'll drop in the notes here shortly, but please feel free to join in providers or the providers Discord channels if you have any questions between meetings, Much appreciate everyone's time today. Hope everyone has a great rest of the day. Thank you. + +00:20:00 + +Andrey Arapov: They go. + +Andrew Mello: Yeah. + +Rodri R: you guys + +Jigar Patel: Thanks guys. + +Andrey Arapov: right + +Meeting ended after 00:20:26 👋 + + From 0d698541eabd24cb89db3d440f57639bac7621f7 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 24 Jul 2024 13:36:20 -0400 Subject: [PATCH 3/4] Update steering committee README.md added video recording link for June 2024 meeting to table. Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index b721509c..0a38d85b 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -30,7 +30,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, March 28, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md#transcript)|[Link](https://4wprt5kys3oxjr7ihtu2jgx6mshwts7gzsiv2pfr4qypgrp2xywa.arweave.net/5Z8Z9ViW3XTH6DzppJr-ZI9py-bMkV08seQw80X6viw) | Thursday, May 02, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md#transcript) |[Link](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) | Thursday, June 06, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md#transcript) |[Link](https://capv32vqn7vrb5u3qvsjn3n6y6swnjkba32ukvydflmqqhrxbswa.arweave.net/EB9d6rBv6xD2m4Vklu2-x6VmpUEG9UVXAyrZCB43DKw) -| Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | |[Link](https://upv27tytyope2fseqvgnnre2au6nmmo65bs2c2fvuxtohsr5bpjq.arweave.net/o-uvzxPDnk0WRIVM1sSaBTzWMd7oZaFotaXm48o9C9M) | Thursday, July 25, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, August 29, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, September 26, 2024 11:00 AM PT (Pacific Time) | | | From fa22fe6a404aaa27c10214db01fa4816128fd606 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 25 Jul 2024 12:51:02 -0400 Subject: [PATCH 4/4] steering committee Create 017-2024-06-27.md (#643) * steering committee Create 017-2024-06-27.md chore: add notes and action items Signed-off-by: Drinkwater * Update 017-2024-06-27.md added meeting notes. Signed-off-by: Drinkwater --------- Signed-off-by: Drinkwater --- committee-steering/meetings/017-2024-06-27.md | 276 ++++++++++++++++++ 1 file changed, 276 insertions(+) create mode 100644 committee-steering/meetings/017-2024-06-27.md diff --git a/committee-steering/meetings/017-2024-06-27.md b/committee-steering/meetings/017-2024-06-27.md new file mode 100644 index 00000000..3cc1548b --- /dev/null +++ b/committee-steering/meetings/017-2024-06-27.md @@ -0,0 +1,276 @@ +# Akash Network - Steering Committee - Meeting #17 + +## Agenda + +- Review / discuss / address any community feedback, grievances, or conflicts. +- Review [projects list](../projects-list/README.md), prioritize / add / remove if necessary. +- A look at open discussions in [Github Discussions](https://github.com/orgs/akash-network/discussions). +- Open up to any other questions from the community. + +## Meeting Details + +- Date: Thursday, June 27th, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://upv27tytyope2fseqvgnnre2au6nmmo65bs2c2fvuxtohsr5bpjq.arweave.net/o-uvzxPDnk0WRIVM1sSaBTzWMd7oZaFotaXm48o9C9M) +- [Transcript](#transcript) + +## Committee + +- Anil Murty, Overclock Labs +- Artur Troian, Overclock Labs +- Greg Osuri, Overclock Labs +- Scott Caruthers, Overclock Labs + +## Participants + +- Adam Bozanich +- Allwyn Dk +- Amanda Keay +- Andrew Gnatyuk +- Anil Murty +- Artur Troian +- B S +- Cheng Wang +- Damir Simpovic +- Denis Lelic +- Deval Patel +- Greg Osuri +- Jeremy Schipper +- Jigar Patel +- Joao Luna +- Joe D +- Maxime Beauchamp +- Poroburu +- Rodri R +- Samson Thomas +- Scott Carruthers +- Sriram Vishwanath +- Tyler Wright +- Zach Horn + + +# Meeting Notes: + +* Tyler talked about the change in schedule for the Steering Committee over the next months +* Tyler went through the agenda for the meetings. The agenda can be found on the Steering Committee readme. + + +### [Product and Engineering Board / Community + Marketing Board](https://github.com/orgs/akash-network/projects) + +- Tyler mentioned that there was a lot of detailed discussion about Console 2.0 and the roadmap during the sig-clients bi monthly meeting. Tyler urged the community to take a look a the recording, as well as look a the product + engineering roadmap for additional updates on the product side. +- Since the last Steering Committee meeting there has been a network upgrade to Mainnet 12. The upgrade was a success. Thank you to all of the Akash Validators. +- Artur reiterated that the upgrade was smooth, and +- Tyler talked about the work from the Mystic Labs team. There is a cosmoskit bug that is a blocker right now, but Mystic Labs team is working to rectify. +- Tyler also briefly talked about the provider build upgrade. This was covered in sig-providers. Testing continues. +- Anil shared some notes in the chat around all of the work around Console 2.0: " I summarized few of the near term console initiatives publicly, here as well https://twitter.com/_Anil_Murty_/status/1804616363769819185 --- all these are tracked in individual tasks on the board Tyler is presenting here." +- Anil mentioned there are 5 themes for the next 2-3 months for Console 2.0. Themes include user experience for onboarding new users (including a custody layer to attract non crypto users); a provider console; and beyond. +- Hooman HQ team will contribute to Console 2.0. The proposal passed on chain. The work can be tracked [here](https://github.com/orgs/akash-network/projects/5?pane=issue&itemId=66078743). +- Tyler touched on Cosmos SDK 47 which is a major upgrade. Look out for announcements in sig-chain. +- Tyler opened it up to questions from the community. + + + +#### [Community and Marketing](https://github.com/orgs/akash-network/projects/6): + +- Tyler talked about ETHCC and all the events happening in Brussels. +- Amanda mentioned that Akash has a full slate of events from July 5th, 2024 +- Akash sponsored 15 different events. Greg and Anil have over 15 speaking engagements between them. +- Many of the events are AI and DePin focused. +- Tyler asked if there were any questions related to Marketing + Community Project Board. +- Zach talked about the Akash Chat API. There will be a permissionsless version available to the public soon. +- Anil mentioned that Akash and Flock.io are doing a hackathon leading up to EthCC. +- Tyler mentioned the Flock.io blog found [here](https://akash.network/blog/decentralized-ai-model-training-on-akash-with-flockio/) +- Amanda mentioned that the first DePin Summer Series kicks off tonight in NYC. It is a 4 part series, with the finale during Messari Mainnet 2024. + + +### Github Discussions: + +- Tyler asked the Akash Community to get involved in discussions and make their voices heard. +- Jeremy talked about his discussion: https://github.com/orgs/akash-network/discussions/543 +- Shade protocol wants to expand DEX liquidity for projects. +- AKT token can be acquired privately via secret. Discussions in sig-economics have been around 50K - 75k tokens. +- Greg asked some questions to Jeremy about how the pool works. The logistics are a challenge. +- Greg mentioned that historically the community pool hasnt been used for liquidity needs. + +- Next discussion from Sriram was brought up. Greg provided context on Sriram, a professor at U of Texas. Sriram spoke at Akash Accelerate 2024. +- Greg also talked about the problem around [verifiable compute](https://github.com/orgs/akash-network/discussions/614). +- Sriram mentioned that the goal is to hardward and software verifiable compute. Software verifiable compute is more challenging. +- The proposal is to use a dongle. +- Sriram went through the discussion with people on the call. +- The plan will be a 2 semester plan (4 quarters). +- Sriram and his team are looking forward to working with the Akash Community. + +- Tyler asked if there were any other discussions to talk about live today? + +### Open Discussion + +- There was no open discussion. + +### Action Items: + +- Brussels Events coming up July 5th, 2024 - July 13th, 2024 +- Please look at the calendar for future sigs and working groups found [here](https://akash.network/development/welcome/#calendar) +- Sig - design has seem a lot of participation from graphic designers that want to help with marketing materials and swag. Give feedback on designs. +- Wg-website and docs is a biweekly meeting for those that want to help with the open source website and the docs. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the Akash steering committee. This is a 17th edition of the Akash monthly steering committee meeting during the steering committee. The group goes over many of the things that happen across the various six and working groups. There's a typical agenda that we go through starting with again reviewing discussion an addressing any Community feedback from there your View Community. We review some of the project boards, including the product and Engineering board as well as a community and marketing board following that we'll review any new GitHub discussions. Usually we try to focus on discussion from folks out to be there. Come to a previous meeting or are here here today to the discussion a little bit more detail. + +Tyler Wright: After that, we'll open up the floor to any other questions. So if anybody has any questions that they want or any topics, they want to discuss today. Feel free to drop in the chat. I'll add them to the agenda during the open discussion portion and then we'll wrap up with just a look ahead at some of the special interest groups and working groups for the upcoming month. we recently had a steering committee at the top of this month because of all the action that happened around the cost accelerate and consensus 2024. So again, this is the second time we're meeting in June but there's certainly been a lot that's been going on this past month. Again, I'll start with the typical agenda. I want to see if there's anything on the community side relates to six working groups or just a committee instruction in general that anybody wants to get feedback on or talk about in more detail. + +Tyler Wright: All If not, then we can move on to the second item on the agenda, which is around the project boards again previously last year. We were using project We've done a lot of the work around those projects lists, and now have these boards that get updated in Fairly real time again, you can track what's going on in terms of what's been released. What's in testing progress again, what's on the roadmap and Beyond both for the product and Engineering side of the org as well as what's going on in the community and marketing front as well. + +Tyler Wright: couple things that I wanted to talk about, we'll start off with the product and Engineering roadmap. We can talk about this at a high level because there were a number of cigs and working groups that have happened over the last week during the Sig clients monthly meeting a Neil did a great job with the Maxes and some of the folks Jigger Deval to talk about all the stuff that's happening in console 2.0 and Neil gave a short presentation on some of the bigger efforts that are happening over the next couple of months. So again, I'll give Anil some time to talk about it if you want to later, but I would urge anybody when the notes are available in next day or so for sick clients to take a look there because again, it was a great meeting. + +Tyler Wright: One of the big items that has happened since the last steering committee was the mainnet twelve upgrade. It was a success and happened very quickly much appreciate to all the validators that were online and again helps with the node upgrade Artur. Is there anything that you wanted to mention in terms of the upgrade here today? Don't feel a blast. + +Tyler Wright: Absolutely. + +Tyler Wright: All right, continuing to move along there's a couple of items that are in testing right now one is around and we talked about this at the last hearing committee monthly meetings Around The Meta mask work from the Mystic Labs team. Thank you to the Maxes who have been working to incorporate cosmokid into console for getting on a call with the Mystic Labs team. I believe the error that there's an issue a bug right now. That's a Cosmo kid bug that the Mystic Labs team is working through and again the product and engineering team is continuing to monitor that so we can get this Mystic Labs met a mask work over the line and get this into released. So again, there will be some more information over the next day or so, but just do want to shout out Max C and Max B for taking the time to connect with the Mystic Labs team get them everything that they needed in terms of environment set up. And again the Mystic Labs team should be delivering and solution. + +Tyler Wright: On the metamask cosmo kit integration very very soon. + +00:05:00 + +Tyler Wright: When other item that I won't go into too much detail on is updated provider build we talked about this at length yesterday during the Sig providers meeting Jigger and Deval talked about some of the testing that they're going to do. If anybody has any questions about this issue again, you can look inside the notes. You can find out where the instructions are. If anybody from the community wants to continue to test you can track where some of the testing is going on and where that currently stands at this point. But again, this is something that in regards to just general providers stability and Improvement of the provider build process is something that Scott Carruthers has been working on with the rest of the engineering team and the product team to again do some testing and this as discussed in sick providers yesterday. We'll continue to be tested and then we'll look to be integrated into the work that the prey to our team is doing around. + +Tyler Wright: So 2.0. So again, if anybody wants to go into more detail about the provider build improvements, feel free to comment on these specific issues or listen to the sick providers monthly meeting call the recording look at the notes and feel free to join as a future sick providers call if you so desire. + +Tyler Wright: All right, covering both the stuff in testing and in release again during the Sig clients call yesterday and you'll gave an update on all the work that kind of see here related to consult 2.0. He just dropped an additional note that gives more clarity inside of the chat. So again, shout out to the product team that's been working diligently and being transparent about all the things that are being worked on where they stand Etc. And I know that more members of the just general Akash Community are getting involved and… + +Anil Murty: Yeah, not a whole lot to act or… + +Tyler Wright: supporting developing some of these features and… + +Anil Murty: what we talked about in three clients yesterday, but just to summarize things there's kind of five initiators that we're pursuing in the near term under basically the console 2.0 umbrella and… + +Tyler Wright: getting engaged with the products core team so major shout out there Anil or anybody else. Is there anything that you wanted to discuss in more detail that was discussed in Sid clients yesterday,… + +Anil Murty: keep in mind that these are just for the next, two to three months and… + +Tyler Wright: go ahead and deal. + +Anil Murty: there's a lot longer roadmap for console beyond that as well that we presented it accelerate Greg talk to a lot of that as well. But I dropped the link to four of those those are primarily focused around improving developer experience for people getting started with Akash, whether it's people coming from public clouds like AWS or people coming from platform as a service products like versaille or nicholify all of those types of users are going to be supported in much better within our caution within console. And then separately we're also going to work on a custodial experience for people that are not crypto native. So those are kind of the main things in terms of the developer experience and improving adoption of forecast site and then separate from all that. We are working on a provider console. So this will be a console for people that want to set up a provider. + +Tyler Wright: Thank you very much I think Anil also touched a touch on it and it was covered a lot during a classic accelerate but + +00:10:00 + +Tyler Wright: there was a proposal around some work that the human HQ team will do to contribute to again console. Thank you to all those that contributed in discussions again human HQ team gave discussions at Sid clients. They had discussions on GitHub a pre-draft discussion to Gage interest from the community that seem to be interest. They then continue to connect with members of the core product team and say clients and other meetings to get more feedback on the best approach went through a number of cases. And then again when it made sense, they put a proposal on chain which pass so thank you to all the validators at voter all the proposal and then again, they'll start to integrate their work into all that's going on with console under again Neil's guide and so again much appreciate to all those that participated in any part of that process. And again, we'll provide more updates on all their work in future steering committee. + +Tyler Wright: All right continuing to move along again. I know that during Sig chain as well as in the last steering committee Archer went into great detail about all the work that's happening on the engineering side regarding the upgrade to Cosmos 47. I know artur's been working with the rest of the engineering team on Next Step strategy roadmap for what again that upgrade will look like because it is a major event. The timeline is pending testing is scheduled for end of summer early fall, but please look out for future announcements whether it be through Sig chain or another special interest group. We're working group for folks that want to get involved in testing get involved and understanding the process how it will affect other parts of the Akashi ecosystem. So again, please take a listen. + +Tyler Wright: to Sig chain the last steering committee to go in depth on all the stuff that Archer covered with related to the cosmos 47 upgrade and then again, look out for announcements whether it be on the website or in Discord about next steps there for those that want to get involved. There's an item on this board where you can also track what's going on there. + +Tyler Wright: Does anyone have any questions on anything on the product and Engineering roadmap again, we discussed this in great detail a number of special interest group and working groups as of recently, but I do want to see if there's anything else that anybody on this call wants to discuss in more detail before we move on. + +Tyler Wright: All right. If not, then again next up is the community and marking initiatives one of the big things that I'll hand over the mic to Amanda Zach is around East CC there's a number of events going on in Brussels. So I want to hand over to Amanda who wasn't able to join the last year and committee, but I know that they're getting ready for all the events happening in Brussels. Amanda Zach do you want to spend a minute or so talking about what's coming up in Brussels and Beyond? + +Tyler Wright: Thank you nda. Again as the Akash team touches down in Brussels, insiders members of the core team alike. I'm sure there will be a lot of content that gets created and shared out of that to look out for, updates there from folks. That'll be on the ground. + +00:15:00 + +Tyler Wright: I know there's a number of other initiatives that are going on the community and marketing side. I wanted to see if there's anything that anybody wanted to discuss or had more questions regarding any Community or marketing initiatives. + +Tyler Wright: Go ahead. + +Tyler Wright: Thank you very much Zach. And Neil I saw your hand up and I saw you drop a message in the chat. Do you want to speak to it? Or I know people can read. + +Tyler Wright: And thank you very much while we're on the topic of flock. I will shamelessly plug a Blog written by Zach and a member of the flock team Matt Burke. That was just recently released So for anybody that has not seen that yet and wants to take a read again. Feel free. + +Tyler Wright: Cool, is there anything else on the community or marketing projects board that anybody wants to discuss? + +Tyler Wright: Go ahead Amanda. + +Tyler Wright: Thank you Amanda for that update. Anything else that anybody wants to discuss related to community or marketing initiatives or any of the project boards before we continue on with the agenda? + +Tyler Wright: cool + +Tyler Wright: All right. If not, then next up on the agenda is discussions. Again. There's a number of discussions that are happening. I would ask anybody that here. I know there's a number of people and I talk about this all the time, please look to get involved in discussions when you can. I know there's a number of people that reach out to me and talk about their opinions on discussions. I would ask that you make those public so that folks can hear your opinions get involved give feedback Etc. So again, thank you to all those I get involved in this discussions. There's a couple that I want to touch on. I know that there's a new discussion that went in there and we will discuss that I believe the person that put that forth is here today, but quickly before we do that there was one prior discuss + +Tyler Wright: And that participant has come to Sig economics a number of times and is just looking to connect and get some feedback from The Wider Community looking for that discussion right now. Pardon me. Perfect. But is Jeremy here? believe + +Tyler Wright: cool Excellent Jeremy. + +Jeremy Schipper: Yes, I am. + +Tyler Wright: I know that you have come to sick economics on number of occasions and put this discussion forth. I believe April 10th. Do you want to take a minute to just go over the discussion and look for again called action from the community to give feedback? + +00:20:00 + +Jeremy Schipper: Yeah, for Thank you Hi everyone. My name is Jeremy schipper. I'm coming over from shade protocol over on secret Network. Hope you're all doing well. I put up a proposal a while ago shade right now is going around to different really high quality Cosmos projects and seeing which community pools want to work with us. If any of you have read it essentially the entire idea is we would ask for proposal from your community pool and ours and we paired up on liquidity on our decks. Essentially we want to be able to expand a lot of people's specs liquidity for a lot of different teams. The biggest thing for Akash that we have seen based on feedback and a lot of the stuff that we do on secret network is the fact that all the transactions are private on secret Network. So essentially would allow for people to have + +Jeremy Schipper: entire setups and acquire their Akito a KT tokens highly privately because of secret networks decc privacy technology. And we're very open to doing this essentially whenever and whatever size a lot of people have suggested 50 to $75,000 worth and we're just looking for more feedback essentially on that. So happy to discuss it with anyone. + +Tyler Wright: Excellent again, if anybody has any specific questions or comments, I urge folks to get involved in discussions. But does anyone have any thing that they want to ask of Jeremy was here live with us today? + +Greg Osuri: So this also means you got acquired shd tokens. + +Jeremy Schipper: No, we would on Shd tokens from our community pool. And then you would do yours and then repair them against each other. So we would be on the other side of that and we're open to doing any sort of liquidity holding custody that you guys would suggest whether you have a liquidity Council trusted actors or just setting up a multi-date on speaker network, but we would be the other side of that pool. + +Greg Osuri: We got to figure out the logistics of this is interesting to the community. I don't have any particular comments generally speaking. historically we haven't used Community for liquidity needs. there is challenges of that approach from a legal standpoint from decent relation or not. And also because it's purely liquidity. It's not really enhancing the value of the product per se they're challenges as well as to how to handle this, logistically. Those would be my concerns. I don't really have any other further or the comments on it. + +Greg Osuri: Thank you. + +Tyler Wright: But again, there's been consistent conversation happening in the Sig economics Discord Channel as well as in sick economics monthly meeting. So I believe the next one is in a couple weeks, but I asked that if anybody has any other questions concerns or what wants to move forward with this idea and discuss it more feel free to drop those opinions and thoughts inside the discussion, please thank you very much Jeremy. + +Tyler Wright: Right continuing to move along again. I know that there is another discussion that is just submitted in the person that create that discussion is here. I wanted to see if sriram you want to talk a little bit about Russian in more detail. + +Sriram Vishwanath: Yes. Yes, thank you for the opportunity. Hello everybody. + +Greg Osuri: Before Shri Ramos. I want to give a little context for this proposal. So sriram is a professor at University, Texas. is a very well known and very much loved professor and he give a talk at accelerate which we just received very well by the community. And we also doing quite a lot of work and one of the big challenges for Akash to enable incentives is verification of compute. We all know what happens when you don't know how many of them paid attention to what's happening with several other networks where some networks took a very naive approach of not verifying actual compute the proviron and given incentive. So you guys civil attack, right? So verification is foundationally + +Greg Osuri: Important aspect for giving out incentives especially in permissionless or trust minimized environment and we couldn't find a better person to work on than someone and sriramically is he's gonna incredible experience and his resume speaks So for himself, and we're really honored at Shri decided to make a proposal to work on this very high level computer for So great. + +00:25:00 + +Sriram Vishwanath: Thank you Greg for that. It's very kind introduction. So folks. It's my pleasure to be here after having the opportunity to meet Greg in Anil in Cheng. I'm a big fan of not just that harsh but just the culture that you have. I think you have an amazing culture so very welcoming and open and I think how do I put this? I'm naturally very drawn to collaborating and working with you. So + +Sriram Vishwanath: Quickly on this. I think the goal ultimately is to do both hardware and software verifiable Computing software is a longer course. especially real-time I think is a substantial effort. But I think the good news is on the hardware front we can get started right away. The proposal here is to use an external what's called a secular enclave and a dongle. So standard USB interface a or c to be able to build verifiable hardware provisioning and essentially manage both identification and secure provisioning. To quickly summarize the approach here through a secure Enclave which has something called a physically and clonable function or path. You must have seen this in a ledger wallet or any Slim. It's the same concept. + +Sriram Vishwanath: you can actually both identify and check on the provisioning of particular a set of Hardware looking beautiful on one downloads enough for the whole cluster. We first plant to Select a set of Tes that would be compatible with the whole variety of operating systems and then to be able to build the mechanism and mechanism itself will be a pseudo random way of essentially making sure that the GPU is Benchmark correctly. So we'd give it a benchmarking task and if it matches the Benchmark for example RTX, 40 90 or similar, then it's currently identified as that particular type of hardware. + +Sriram Vishwanath: And then this certification is then securely signed within the te. And then provided to the Akash Network. So that's the plan we plan to do this at the university project. So I'm the professor, but they'll be graduate students and some undergraduates as well. But mainly led by graduate students. In the plan is to kick the surface AP. So that's the good news is that we'll get to hopefully not just excited bunch of young minds that hopefully involve them at much deeper level within our Network. + +Sriram Vishwanath: So the university is prepared a budget for it, which is also linked and the plan we'd like to do this as aggressively as possible. But we put down a two semester which is roughly for quarters plan here, but you'll see in terms of deliverables. We should be able to provide both the specification and a prototype pretty quickly and then hopefully, after sufficient testing we can handle this over to the a team perfect. So that's it in a nutshell. It's a very interesting project for me because both from a similar attack. And ultimately from a overall network security perspective, I think. It enables us to contribute to our cash Network, which makes me feel really good. So I'm looking forward to doing that. + +Tyler Wright: Thank you very much for putting together this very thorough Proposal with again deliverables budget team how you're looking to solve the problem. Does anybody have any initial questions that they want to talk to you about right now while we're all live. + +Tyler Wright: If not again, I know this proposal just went up but I would ask that everybody continue to read through the entire proposal. They have any follow-up questions that can drop those in as comments in the proposal and then I'm sure we'll get back and forth using the proposal using this as a way to go back and forth on next steps from there. + +00:30:00 + +Sriram Vishwanath: Perfect. thank you. for having me + +Tyler Wright: And please thank you. + +Tyler Wright: All right, if there's no questions on that proposal then again, we can go back to General discussions. I wanted to see if there's any other discussions from anybody that's here today that they want to talk about live. + +Tyler Wright: All then we'll continue to move along again. I would ask that everybody here and all insiders vanguards can continue to get involved in discussions or ask those that are looking to contribute to a class to get involved in some of these discussions and make their voices All right continuing to move along. Next portion is around open discussion. I don't see anybody that dropped anything in chat, but I want to see if there's anybody that has anything that they wanted to discuss with the group here today live. + +Tyler Wright: All right, I will take that as a no. All right, last portion is again the look forward. + +Tyler Wright: As previously mentioned there will be some continued changes to the schedule for the cigs and the working groups coming soon. But as previously mentioned the Sig economics working Sega economics is going to be happening July 3rd, next Wednesday following that there's a couple of other that'll be happening the following week sick chain and sick Community again as mentioned there might be some changes to the structure of Sig chain the formation of potential another Sig that we talked about in six support which will involve more members of the core engineering team. So look out for updates on Discord and then again continue to use his calendar on the Akash website as your source of Truth for all future things and working group meetings couple other things to call out are Sig design. There's a couple of folks that have been getting more involved in I sharing designs for swag. + +Tyler Wright: During designs for other marketing materials and some folks have been coming to the meeting some more graphic designers and visual communicators. Again, if anybody from the community knows anybody that's looking to get involved in Akash and is a designer have them again. Feel free to join the Sig design. And again, there's some folks that are either dropping in designs or have already dropped in designs to Sig design Discord Channel. Feel free to give your feedback on those designs so that we can either Look to add them to the store or have them for future events or give feedback for some of these newer community members are looking to contribute. + +Tyler Wright: Again, the cost website working group is continuing to move along. There's a number of contributions that happen there on a monthly basis or me on a biweekly basis. So again, if anybody wants to get involved in supporting the website or documentation, which is under the website feel free to get involved in that weekly working group. And then again, you can check out the rest of the addenda. + +Tyler Wright: Sid clients will most likely be removed because that is a monthly meeting and we just most recently met with a change of schedule just yesterday. But again, if anybody has any questions about console again, we talked about those things and steering committee or you can feel free to get involved in Sid clients Luna who was also very active with corsage his team and does a number of Open Source efforts with Akash also gave a demo of some work that he's been doing with his team for some time. So again, feel free to take a look at the state clients or recording in the notes which will be available in the next day or so to see a demo from corsage and then see all the work that again the console 2.0 the console team is working on for latest to console 2.0. + +Tyler Wright: There any other questions about anything that anybody wants to discuss related to Akash? + +00:35:00 + +Tyler Wright: If not, then again, I know this is a quicker steering committee than usual. But again, we just had one maybe 20 days ago appreciate everybody's time and effort today. Appreciate everybody that's been joining the Sig clients to enjoying a number of these cigs and getting involved again damir gave a presentation a demo of some work that he's been doing around grafana and Prometheus in sick providers just yesterday and also in the Akash insiders office hours today. So if anybody wants to get involved there, please take a look at the demo that he gave in sick providers and then reach out to him in the providers Channel or… + +Anil Murty: Thanks everybody. + +Tyler Wright: the sick providers Channel about next steps. + +Tyler Wright: But again much appreciative on time and effort today. Thank you to all though all that pitch their discussions. Please get involved in the discussions and we'll continue to connect online and look forward to all the events going on in Brussels and safe travels all those that are attending but I'll see you all in the Midwest. Have a great day everybody. All right. Bye. + +Meeting ended after 00:47:08 👋