diff --git a/committee-steering/meetings/021-2024-10-31.md b/committee-steering/meetings/021-2024-10-31.md new file mode 100644 index 00000000..6bebc808 --- /dev/null +++ b/committee-steering/meetings/021-2024-10-31.md @@ -0,0 +1,424 @@ +# Akash Network - Steering Committee - Meeting #21 + +## Agenda +- Address community feedback and grievances. +- Review updates to project boards. +- Share updates on recent and upcoming events. +- Discuss progress on developer onboarding initiatives and YouTube content. +- Provide updates on the Cosmos SDK 47 upgrade and related technical developments. +- Review and discuss active governance proposals. +- Open floor for additional topics or feedback. + +## Meeting Details + +- Date: Thursday, October 31st, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://h5r73bah365pqfr4x62x5sdut5px4wpprsnd6lu2hcej3x42jkxa.arweave.net/P2P9hAffuvgWPL-1fsh0n19-We-Mmj8umjiInd-aSq4) +- [Transcript](#transcript) + +## Committee + +- Anil Murty, Overclock Labs +- Artur Troian, Overclock Labs +- Greg Osuri, Overclock Labs +- Scott Caruthers, Overclock Labs + +## Participants +- Tyler Wright +- Adam Wozney +- Amanda Keay +- Andrew Gnatyuk +- Anil Murty +- Artur Troian +- Cheng Wang +- Damir Simpovic +- Ed Prado +- Fico Calderon +- Garrett Minks +- Joao Luna +- Juan Pablo Arce +- Robert Del Rey +- Rodri R +- Scott Carruthers +- Scott Hewitson +- Zach Horn +- Zeke Ezagui + +## Meeting Notes + +### Community Feedback +- Tyler Wright opened the floor for feedback and grievances from the community. +- Participants were reminded to share their input during meetings or reach out to core team members or insiders between sessions. +- Focus on making SIG operations and community contributions more transparent and accessible. + +### Project Boards Review +- Tyler emphasized the importance of the public-facing project boards. +- Boards track initiatives across product engineering and marketing, offering a transparent view of Akash’s ongoing efforts. +- Team members traveling for events have been contributing to updates despite logistical challenges. + +### Event Updates +- Amanda Keay provided updates on recent and upcoming events: + - **Permissionless Conference** in Salt Lake City: + - Akash team had speaking engagements and hosted a successful booth. + - Generated high-quality leads, particularly from AI developers, comparable to engagement levels at Token2049. + - **Cosmoverse in Dubai**: + - Akash led the AI track, hosted an AI-focused afterparty with over 300 attendees, and secured prominent branding. + - Team members participated in panels, discussions, and networking activities. + - **NeurIPS 2024** in Vancouver: + - Plans include a booth, speaking engagements, and workshops at a nearby venue, focusing on Akash's AI positioning. + - Attendees will have access to Akash Compute credits and networking opportunities. + - **ETH Denver 2025** preparations are underway, with plans to continue building Akash’s presence in the Web3 space. + +### Developer Onboarding and YouTube Content +- **Zealy Campaign**: + - Sprint 3 of the second campaign completed, with rewards distribution scheduled. + - A new onboarding process is being developed, focusing on guiding developers through a structured user journey from basic engagement to advanced contributions. + - Best campaign submissions, including guides and designs, will be compiled and shared. +- **YouTube Content**: + - Steering Committee meeting recordings are being prepared for upload. + - Upcoming focus will be on creating technical tutorials for deployments, Akash Console features, and GitHub contributions. + +### Cosmos SDK 47 Upgrade and Technical Updates +- Artur Troian provided updates on technical progress: + - The initial testnet for Cosmos SDK 47 is live, focusing on stability before expanding participation. + - Ongoing provider-side enhancements for Akash Console 2.0 include contributions from the community. + - Improvements to inventory exporter functionality were completed with community support. + +### Active Governance Proposals +- **[Rair Protocol Proposal](https://github.com/orgs/akash-network/discussions/709)**: + - Garrett Minks and Ed Prado presented the integration of Akash as a decentralized compute layer for deploying DApps. + - The goal is to move away from centralized solutions like GCP and offer Web3-native compute options. + - Proposal outlines a phased approach, starting with configuration migration and progressing to full feature parity with GCP-based setups. + - Community members were encouraged to review the proposal and provide feedback on GitHub. +### **[Provider Incentives Pilot 2 (PIP-02)](https://github.com/orgs/akash-network/discussions/696)** +- Presented by Cheng Wang: + - PIP-02 doubles the funding size from the previous pilot to expand GPU capacity and address rising demand. + - GPU models, including A100s, RTX 4090s, and future-ready 5090s, were detailed in allocation plans. + - Zeke Ezagui raised questions about: + - Flexibility in upgrading to 5090 GPUs when available. Anil clarified that allocations would be reviewed case-by-case to accommodate next-generation hardware while balancing commitments to current GPUs. + - The inclusion process for community providers in the incentive program. Cheng and Anil confirmed a manual vetting process based on outlined criteria, emphasizing fairness and adherence to quality and availability standards. + - The need for clear instructions for community providers to apply. Tyler committed to sharing detailed steps and ensuring community awareness. + - Anil reiterated that existing customer workloads would guide allocation decisions, with options to transition customers to upgraded hardware where feasible. + +### [Governance Proposal Best Practices](https://github.com/orgs/akash-network/discussions/170) +- Tyler Wright highlighted updates to governance proposal guidelines: + - New guidelines aim to streamline the process for submitting and reviewing proposals. + - Community members were encouraged to refer to these guidelines for leveraging the community pool effectively. + +### Open Floor Discussions +- Tyler encouraged participants to raise any additional topics or questions. +- Updates on SIG meetings and regular working groups were shared, including: + - Zealy meetings, focusing on developer onboarding. + - Akash YouTube working group, prioritizing technical content development. + - SIG chain meetings to discuss the Cosmos SDK 47 upgrade. + - SIG provider discussions on ongoing efforts related to Akash Console 2.0. + +## Action Items +- Tyler Wright will continue gathering feedback and ensuring transparency in SIG operations. +- Amanda Keay will finalize event plans for NeurIPS 2024 and ETH Denver 2025. +- Robert Del Rey will complete Zealy rewards distribution and redesign the onboarding process for developers. +- Artur Troian will stabilize and expand testnet participation for the Cosmos SDK 47 upgrade. +- Community members are encouraged to review and provide feedback on the Rair Protocol proposal and vote on PIP-02. +- Governance proposal updates and best practices will be shared to guide the community on effective use of the community pool. +- Announcements regarding SIG working group schedules and opportunities for engagement will be shared via Discord and GitHub. + +# **Transcript** + +Tyler Wright: All right, welcome everybody to the Akash steering committee. It is October 31st, 2024. during these monthly meetings, the steering committee gets together talks about everything that's happened over the course of that month in terms of SIGs, working groups and beyond. we follow a typical agenda which I will move over to now. But again, if anybody has any specific items that they want to discuss as a part of steering committee, again, please drop them in. We usually try to have these things in advance because oftent times we have a full plate of agenda items. But again, if there's anything specific that anybody wants feel free to drop it in here now. All right. Again, you can look at notes from the past meetings here. + +Tyler Wright: notes, transcripts, recordings for all the steering committees since January 2023 are available here. Again, one of the things we start off by doing is reviewing, discussing, and addressing any community feedback, grievances, or conflicts. This could be anything you see in SIG's working group structure. Anything that you think can be improved on, feel free to raise your hand and we can discuss those things right now. Cool. again, if anybody sees anything between meetings, feel free to reach out to myself or any member of the core team, insiders, etc., and we can again continue to u improve the process, make it easier for folks to get involved, etc. All right, continuing one of the big items that we discussed during these, steering committee calls is, the project boards. + +Tyler Wright: again, these are transparent public facing boards that anybody from the community can kind of track what's going on across community marketing initiatives as well as product and engineering. you can see our road map and these items are discussed at steering committee as well as other SIGs and working groups and continually updated by members of the core team and other members of the community that are working on specific efforts. So if you're ever interested in what's on the future of the road map across again product and engineering, again, please look out. This is always constantly being worked on and constantly being updated. I know some members of our community and marketing team have been working hard and have been on the road over the last month. and it's just been again a tireless amount of work that's been done. + +Amanda Keay: + +Tyler Wright: I do want to kick it off by handing it over to Amanda to just talk a little bit about some of the events that have gone on over the last month, including Cosmoverse and others, as well as a look forward to again some of the events that are on the horizon. + +Amanda Keay: Yeah, thanks Tyler. + +Amanda Keay: So about a month ago, I'll start three of us from the core team were able to go to permissionless in Salt Lake City. We had a couple different speaking engagements and an official side event during that week. it went really well. I felt like the conference had a lot of really high quality people that came by, a lot of specifically AI developers that were interested in talking with us. + +Amanda Keay: Zach and I were manning the booth and I think as far as quality leads and the amount of leads, it was up there with the amount total that we got altogether going to token. So, it was a really good success for us there. and then we just a week or so ago got back from Cosmoverse in Dubai. That event was really good. a three-day event. Greg, we actually led the AI track at Cosmoverse. So, we were able to have our branding front and center as well as multiple speaking opportunities by both Greg, Anneil, and Zach. So, that was really awesome. We also hosted a AI afterparty following our AI track day just right next door. we had 300 plus attendees show up. + +Amanda Keay: So we were able to really flex our branding there and just prove that Akos branding is as strong as it is right now. So that was really great. Looking forward to the next month. We don't have any travel per se in November. A few hackathons that we might be visiting this month but then we're really focusing our efforts on Nurups which is in Vancouver this year from the dates November through the 14th. So Akos will be doing a larger booth at the main event as well as Greg got accepted to be a speaker on the main stage and we are planning on doing a social house just right down the road a really cool venue used to be an old bank so we have that space for two days we're going to have some workshops some special speakers we're finalizing that now as well as just a space for people to come and network and talk and if they wanted to hack they can have + + +### 00:05:00 + +Amanda Keay: Akos compute that we're going to give credits for and just kind of build our branding in the more AI space. looking forward to that doing a lot of planning. so that is taking a lot of time right now and I think that will put us through to the end of the year and then already honestly working on ETH Denver events which is in February. So things are moving rather quickly and it's exciting. + +Tyler Wright: Thank you, everybody that's been involved in all those events over the last month. And as we look forward, as a reminder again, there's been a lot of discussion in GitHub around Q4 proposal and now there's a vote on chain. So, if you have the ability to vote, please do so. as we continue to again, fine-tune and, continue to build the brand that's already very strong. So, much appreciate everyone's time. Does anyone have any questions for Amanda about anything events related? I know she has to head out very soon to some other obligations. Cool. All right. + +Tyler Wright: we talked about it in again a weekly working group around the website and docs. again there's folks that contribute to console. If you are contributing in any way via the states and working group structure please make your contributions known via comments inside the specific area in which you're again contributing. this helps with transparency and making sure it's easy for folks that are contributing to get rewarded for those contributions. + +Tyler Wright: so again just want to make that u clear to everybody that you can look on this board. again get involved in the signing working groups. We discuss specific issues that need solving inside each of the repos and then again if anybody can get involved in the community we look for those contributions. So thank you to all that are getting involved. I did see that Robert had some items specifically that he wanted to discuss on the community and marketing side. So, Robert, I'll give you the four to quickly talk about Zilly and the Kosh YouTube working group. Yes. + +Robert Del Rey: Thank you, Can you guys hear me? All Really cool. so yeah, as you some of you may know, we are leading Pyber and I are leading the Aash dev on boarding campaign on CV. It's a platform that helps us create missions and make it look like a game to engage with a cashache. this is the second three month campaign. So we basically do six months of campaign on silly engaging with more than 2,000 people which is awesome. the spring number three of the second season ended just yesterday. So right now we are just doing the math to determine the amount of rewards that are going to be paid out. We're going to start paying out those rewards on Monday. + +Robert Del Rey: you can also expect our city working group call happens every So on next Monday in our call you can also expect the project status In that report we add information analytics like we add how many people are engaging with the platform and more stuff that we share with the community. So you can see how we are doing and how is Aash benefiting from this. So really cool. it was wild trying to manage this while on the road during Cosmoverse. but we managed to do it. very happy for the support I got from Benji and also more people that engaged with this. We had a really good call on during Cosmover. I actually share the screen. + +Robert Del Rey: Sorry, I share my camera during verse and 20 people joined that city working group call and they were very happy to see our aash booth in Cosmo verse and got really excited. one thing that I can tell you is that yes, the campaigns are done in editing, but we created a document and we compile of the best submissions that we got on Cely from guides and videos to designs all those of the best really really good quality submissions we have them in a document and we're going to share those with you also very soon. + + +### 00:10:00 + +Robert Del Rey: we will give some extra rewards to those participants going the extra mile. So as for now on November the first two weeks of November only expect the rewards being paid out but no more sprints at the moment. we are actually redesigning the process and we want to make it look more like a user journey like the next phases of cely or whatever tool that we decide to use to do this. + +Robert Del Rey: we want to make it look like a journey where people get to know a cache, they join the social media, read the documentation, they start deploying and doing stuff on a cache and then at the end we show them how to get involved in GitHub like a star when you put a start in one of the repos to get all the updates there's going to be mission about that so people can start the cache GitHub + +Robert Del Rey: + +Robert Del Rey: stuff and yeah so yeah it's going to be really nice we're going to go back to the roots of silly on boarding new developers we are very thankful for the people participating every month in the sprints but with this user journey we want to go back to the initial goal of this campaign which was attract new developers to a cache so it's a concept we're still developing it so that's the work we're going to do in the following weeks hopefully and release that to the public in the next two weeks mid November. + +Tyler Wright: Perfect. Thank you. + +Robert Del Rey: So that on ceiling. Let me know if you guys have any question about it. One, two, three. No, that's okay. you can also drop any questions in the chat or go directly to the city chat for more stuff. in regards to Akash YouTube one or two months ago we started the Aash revamping efforts we believe the Aash branding is super strong and we can complement that having a strong YouTube channel. So I got many insights from the insiders going to Cosmo many cool ideas that I'm drafting in a proposal. + +Robert Del Rey: So in that proposal I'm going to show you the next phases of the Aash YouTube and how we believe we can better use this platform to educate people on a cache just to tell you a little something is that we want to focus on technical videos of a cache how to do deployments the different aspects of the console the cash chat how to contribute on GitHub those things that we say on the calls that we say them right we want to turn + +Robert Del Rey: + +Robert Del Rey: those into videos that people can see and actually learn how to get involved and contribute to a cashache. So that's the only thing I wanted to say on YouTube. at the moment we have 20 videos uploaded from the steering committee calls. I'm waiting for approval to go live. That should happen very soon. But after those videos are live, the focus is going to be on creating technical videos about the different aspects of Aash Network. Yeah, that. + +Tyler Wright: Excellent. Thank you,… + +Robert Del Rey: The next YouTube working group call, forgive me Tai, I don't know when it's going to happen. Maybe we can have it on next the 5th, or the following Tuesday. Either way works fine for me. + +Tyler Wright: Robert, for that detailed update across Zeely and the Akash YouTube. Again, there's specific working group for ZLY that meets Mondays as well as the working group around the Akash YouTube which again I will make an announcement and add it to the calendar which everybody can track at network development. So I'll put a link to that in the chat for folks to just track the calendar that can add SIGs and working groups. + +Tyler Wright: to their own calendars and stay up to date on when meetings are across the month. Go ahead, Robert. Okay. + +Robert Del Rey: + +Robert Del Rey: The third topic I had was an introduction to LATAM nodes. the guys approached me during Cosmo and they told me they have a big data center and they want to talk to the cache team and find the best ways to work together. So I don't know if that can happen by the end of this call after everybody shares their updates but just wanted to give you the heads up about latam notes. Actually, many validators passed by the cash booth saying they have resourc and also inquiring about the foundation delegation program. + + +### 00:15:00 + +Tyler Wright: + +Robert Del Rey: So, I don't know if they're in this call already, but just giving you the heads ups. Fate again. + +Tyler Wright: Excellent. I think we can take that conversation outside of the steering committee call just… + +Tyler Wright: because again we can handle that elsewhere but I'll follow up with you and get the necessary folks together to talk about that. Go ahead. Sorry if I'm butchering your name. I don't know if you're trying to speak, but I do want to move on just for the sake of time because I know there's some discussions that we want to get to as well. again, as Amanda alluded to, there's a couple of hackathons on the horizon. for folks that want to get involved or want to learn more, again, there's a SIG community where we talk about everything from events to hackathons to just the Kosh community in general. + +Tyler Wright: So again, this is where these topics are discussed in more depth. and there's more focus discussion from folks that are very passionate about these topics. So again, I don't know if Adam specifically had anything that he wanted to cover. Don't feel obliged, but again, I know that there some recent messaging that went out around the hackathon 3. We just discussed it on a couple of previous calls. but just wanted to call that out here today as another initiative as well as I believe there's a meta hackathon that's going to be going on in Brazil that a clash is going to be supporting and sponsoring in a number of different ways and that's coming up quite soon as well. + +Tyler Wright: I did want to see if there's anything else on this marketing board or anything else that we've discussed in SIGs and working groups that folks want to talk about right now before I quickly jump over to the product and engineering roadmap. Yep, we'll get to the PIP during the discussion portion. Thank you, Zeke, for bringing that up. All right, moving on to the product and engineering roadmap. again, this is another area that gets updated consistently by members of the core engineering, etc. there are various people working on projects across product and engineering side. so again, we look to get updates from folks. + +Tyler Wright: I know one of the bigger things that's been tracked is the upgrade to Cosmos SDK47. Again, we talked about this during the SIG chain. I do want to kick it over to Archer real quick just to talk about where we are. I know that we have an active test net and again some messaging is going to go out to some folks in the community that have showed interest in getting involved in that initial test net. But I just want to see if there's anything at a high level that Archer wanted to discuss around Cosmos SDK 47 upgrade or anything else on the product and engineering roadmap. + +Artur Troian: Thanks, T. I'll try to be quite quick regarding SDK47, yes, we finally started our first test net literally yesterday. there have been couple mishaps that we had with the ramping it up, but they all been sorted and that's pretty much good news. We're going to keep this test net at this moment quite low on participation. Reason being is there are still couple things that are not quite stable and we just want to make sure that we solve all of them first before we allow wider participation from the test net and our hope is that probably in two weeks we should be able to expand participation. + +Artur Troian: then moving on to the provider there have been couple things related to the provider stability things as well as the inventory like issue 259 and the core team which is diligently working to cover all of those issues and keep releasing new features as well as bug fixes. one more thing in sort of more broadband we have finally got our snap food service up and running huge thanks to Zeke for completing that task and it's pretty much done by the community. + +Artur Troian: This is great example of community participation in Akash efforts as well as a little bit of credit goes to Luna for working on our inventory exporter for the Promeigious. I saw first just literally a couple minutes ago and hopefully we're gonna get released it soon. And I think that covered it. Back to you. + + +### 00:20:00 + +Tyler Wright: Thank you, Archer. we discussed it in SIG providers yesterday. I know there's been a significant amount of work from the product team around the provider side of Akos console as a part of the console 2.0 effort. so again whether it be the free trials that have come recently, fiat payments, there's just a number of new work coming out of the console 2.0 know efforts and I think there's going to be continued work from some of the efforts from home and HQ and just continuing to again improve on the console experience. So big shout out to the product team for all the work that they've been doing and for the community for continuing testing feedback etc. Just want to see if there was anything else more specifically. Again you can get a demo. + +Tyler Wright: we got a demo on the provider side of the console from Jigger yesterday during SIG providers. The video and the transcript will be available soon. So you can take a look at that. But I just wanted to see if there was anything else specifically on the product and engineering roadmap that anybody wanted to discuss more specifically before we jump into some discussion if not then again we're at the part of the agenda where we will dive into some of the active discussions. again usually we try to carve out some time during the steering committee for discussions that are getting a fair amount of traction. I know there's two discussions that we'll be talking about today. + +Tyler Wright: One is the discussion for rare protocol and aash network full integration and the other discussion that we'll discuss in a little bit more detail is around the provider incentives pilot number two which is currently on chain for vote after again discussion for a number of weeks. I think we'll start off with the rare protocol. and then we'll take a couple of minutes to I know that there's a couple of participants that have taken some time out of their day to join us today. so I want to kick it over to Garrett and Ed from the rare protocol team. Again usually what we do is folks have already read through the discussion in great detail. + +Tyler Wright: + +Tyler Wright: Garrett and Ed, if you can give a high level on, rare protocol, the benefits the network and then maybe a followup to any of the open discussions, then we can just spend maybe two to five minutes talking about this discussion and figure out next steps and then from there we can jump into the PIP 02 discussion following that. + +Garrett Minks: Awesome. Thanks,… + +Tyler Wright: With that said, I'll hand it over to Garrett and you can just kick us off. + +Garrett Minks: And thanks so much for having us on. We've really enjoyed getting to know the Akos community and also get our open deployment layer. I would say an MVP version of our stack is already kind of up and operational on the Akos marketplace, which is super cool. and thanks so much to Zeke especially for helping us figure out exactly how to structure the SDL to get all of that working. We have our six core microservices that encapsulate the protocol are now on and kind of an MDP version on the Apache marketplace to deploy which is super cool. + +Garrett Minks: So, as a really high level, I'm the founder of Ver Protocol, also the CTO, and then Ed, who's on the call, is our CEO, and does all of our awesome partnerships and, integrations, all the business side, of the house. So, I can speak, some to the tech side and our, big picture reasoning for really wanting to decentralize the compute, layer of our stack. So we originally started as enterprise SAS dab development software products where kind of doing the same approach as the third webs and the buttons and those kind of companies of the world and through the bare market kind of decided to do this quite interesting pivot to a fully open source deployment layer. So sorry about the airport some nonsense in the background. + +Garrett Minks: so since we've kind of pivoted to open source we've had all sorts of awesome things happen to the project got picked up by quite prestigious ac So part of the Redbeard Ventures token accelerator now and has really helped us grow our dev community. we're about 3,500 devs strong in our GitHub now. And as part of this mission to kind of democratize deploying DAPs more easily and in an open source way, we also want to basically open up the compute layer and kind of get off of GCP. + + +### 00:25:00 + +Garrett Minks: when we originally developed the core software, everything was very much built around a GCP Kubernetes setup and really to scale and to fulfill the mission of having an open deployment layer, we want to have of course the underlying compute, also be open and permissionless. So, that's kind of the big goal behind what we want to do. And then our proposal is basically focusing in the first phase all of the very specific things that we think we can do to make it easier for new developers to pick up our open deployment layer and deploy it onto AOS things like kind of ironing out some of the finer points with SSL kind of see some of the other items and then with the second phase to really figure out how we can make a feature parody version of our deployment layer with all the + +Garrett Minks: scaling features and functionalities that we currently have on GCP. So, that's a high level. I don't know, Ed, if you wanted to say anything. + +Ed Prado: Yeah, I'll just add it's great to be here. We've loved working with you. We've been to several conferences. We're getting a lot of signal on Akos and certainly One of the things that was interesting when we spoke to Chang is that we represent a way to monetize and leverage your plain vanilla compute away from AI, which I think is a really important part of your model. and we also represent, a web three sort of integration and developer group that we can bring in and actually build DAPs. And as we go down this journey, there's going to be more and more integration between AI and web 3. we were just at a conference and tons of people were talking about that. So, we think that the time is right and we think we have the right product, we have the right developers, and we're excited to discuss and see if we can get this done with you guys. So, thank you for your time. + +Tyler Wright: Thank And again, I've dropped in the discussion in the chat for folks. Again, the ask is from the community pool for again their efforts. and so again, you can check out the entire ask and just get more information on the specifics on top of what Garrett and Ed just mentioned. So, is there any specific questions that anybody has at this point while we have few members from the team here live that they want to get answered? Go ahead and kneel. + +Anil Murty: + +Anil Murty: Hey guys. I'm sorry. I was just actually reviewing the proposal right now as you guys were talking. maybe I'm missing it, but what exactly is the service? If you could just explain it in one sentence or… + +Anil Murty: two sentences. What does the service do? + +Garrett Minks: Sure. + +Garrett Minks: So in a nutshell, the open deployment layer makes it easier for a new developer coming in to deploy a DAP. So instead of starting from scratch, they can start from a 95 99, percent complete DAP. So the full front end, backend, Mongo database, Reddus, all of those microservices that we have in the template that I just dropped into the chat, those are all out of the box working. And then effectively to make the DAP their own, they would go in and switch out a few of the underlying API keys. So we provide a default alchemy key say to do the syncing. they could go in modify the Docker image and then have their own syncing engine. + +Garrett Minks: And importantly, they have their own backends, too. That's something that not a lot of other companies kind of in this similar vertical to ours will open source. third web, things like that. they keep a lot of that stuff closed. so, yeah, in a nutshell, it's a open source deployment layer that makes building new distributed applications easier. + +Anil Murty: + +Anil Murty: Got it. so I guess I'm a little confused as to why. So the whole idea with console is to be the tool that people use to deploy stuff onto And in the past when we have had people talk about building potential other clients, it's been one of two ways… + + +### 00:30:00 + +Garrett Minks: It wants dark. + +Anil Murty: which is if you have other platforms that are building something for web3 or decentralized applications but trying to compete with something like a versel there's a few projects that have done that. + +Anil Murty: they'll typically integrate Akash as part of their platform and use it purely for infrastructure along with something like Filecoin or something else for storage. and that's typically something that they just do as part of their platform. what I'm not understanding here is why is this a community proposal for Akash specifically and also also just looking at the screen that Tyler is sharing that seems like a really big team for what you're talking about which is a few SDLs I mean we don't have a huge Q automation testing team just so + +Garrett Minks: Sure certainly. So I can speak to kind of So of course our infrastructure is all kind of Docker based already. So the way that we've architected it is a bunch of these containerized microservices just right now we're deploying them largely inside of Google and then our containers are being kind of created and destroyed and the GKE setup. so we have the way that we've constructed our system I think lends itself quite well to how AOS works. It's just that key difference and that key differentiator is, we don't want to have devs to have to pay fiat and use some centralized server that they could get turned off or censored, right? We want to have a native web three compute option for deploying web3 applications. + +Garrett Minks: that's the real impetus for us trying to basically fully decentralize our stack from kind of the top down because I think it kind of doesn't matter if you're using the blockchain and have all these awesome decentralized features in your application if it's ultimately running on a compute layer that is run by Google. so yeah, that's the, high level reason why we want to do it. And then the more sort of brass tax way that we're able to accomplish it is by basically porting over all of our existing config maps like existing manifest files, all that stuff that we've done in Google. + +Garrett Minks: we're basically migrating and moving over and it seems like Jiao asked about the yncing. So we have two ways to do syncing in our system. one is a kind of out of the box solution that uses alchemy largely to do all the RPC type services. We also have a native one where you can pop in your own RPC URLs into the environment variable file of the docker at build time and then basically sync that way and then all of those transactions when they sync will then get stored in the mongo which is another microser that gets deployed nicely when that one SDL is run. + +Garrett Minks: So basically when somebody deploys a DAP with our system they're running their own entire self-s sovereign self-contained DAP infrastructure including the backend in the rare node microser and… + +Tyler Wright: I know we need some time for other discussions. + +Garrett Minks: then their own mongo in that micros service that helps + +Tyler Wright: I would just ask that anybody here today if they haven't already, please feel free to drop comments and discussion. Again, this is how we continue to make sure that the community is as involved with everything that has to do with community pool spend. if anybody has any additional questions, thoughts, concerns, votes of approval, whatever the case may be, ple please drop those in the GitHub discussion. and then we'll continue to again fine-tune and figure out what the next steps are. But very appreciative of Garrett and Ed taking the time out of their day to join us today and safe travels, Garrett, for sure. But thank you very much for taking the time. + +Garrett Minks: Awesome so much. Thanks for having us and I'll hang on for the rest of the call too. + +Tyler Wright: + +Garrett Minks: Okay. + +Tyler Wright: Excellent. All right. + +Tyler Wright: Continuing to move along. again, there's a couple of other items that, are on chain. so again, please get involved in some of these discussions. I know that Huey dropped in some, metrics from Q3 events in some of the past quarters. So, please track that. but right now I do want to because I know that folks have been talking about it and want to talk about a little bit more. I do want to kick it over to Chang to talk a little bit more at a high level. I know we've talked about it in previous calls prior to this discussion going up but talk about PIP at the highest level and… + + +### 00:35:00 + +Tyler Wright: then see if there's any questions from anybody here that can be discussed. + +Cheng Wang: Thank you,… + +Cheng Wang: Ty And let me know if Changbot v1.2 is bothering you guys and I'll remove the filter here. so in terms of PIP provider incentives pilot number two, this is the follow on to provider incentives number one, right? the first level of incentives was just for a quick recap in everyone's information was approximately $5 million in size and funded approximately 400 additional GPUs that have all today to this day been added to AOS network. And as far as where we are in the commitment of those funds, initially we started I think the first contract with a provider or two back in March of this year and throughout between March and this point in time we are still in the process of fully deploying All those funds at this point in time have been fully committed. Of course the spend will continue to move forward. + +Cheng Wang: So we're at peak basically GPU capacity from pip 01 chips at this moment in time and pip 02 is a double of that size up to 10 million and there are a lot of community discussion around that particular item in GitHub as well and so currently this I think is already on chain for vote and the idea here if you can scroll down a little bit so those chips up top in the current table that's been displayed right now are the ones that were committed to in PIB01. And in the table a little bit further down, these ones right here are the ones that we're expected to, we're estimated to deploy funds towards for PIP 02. Again, these are, high level est estimates based on the best of our understanding with us and the core team rather in the community at large, And this mix can change a little bit over time, right? So this is the essential makeup here. + +Cheng Wang: the biggest thing I'll say is the idea here is to bring greater numbers of highly sought-after GPUs onto a Kosh network to be able to power larger workloads with larger tenants, right? those are all extremely important especially as some of these things begin to scale. We're already running up against maximum utilization as you guys will see if you go to the stats network today. with trial wallets as well as with credit card payments up online now we're essentially red line on all the high-end GPUs we have and we're at near I think record usage today which is incredible from GPU side of things so if there are any questions please drop them in 810080s of course the most sought actor models there and L40s etc will be kind of the replacement model for the A180s MI300's + +Cheng Wang: and the H200's are the looking forward set of models, right? kind of the newer generation and of course the RTX490 is crowd favorite there as far as inference capabilities go in a distributed fashion. and A6000s which kind of round out the lower end of those particular models to service clients on that side of the spectrum. That's Fire away. + +Tyler Wright: Perfect. Go ahead, Zeke. + +Zeke Ezagui: + +Zeke Ezagui: So, a couple questions. I'll start out with, it looks like the timeline for this is going to be 6 to9 months. Is there any thought in wanting to do 5090s … + +Cheng Wang: + +Zeke Ezagui: because those are going to release in spring of + +Cheng Wang: That's a great question. + +Cheng Wang: Probably I think just to give you an idea in terms of committing to these ships. So, hypothetically we go out to six, eight different providers and look for these resources. right 4090s we have 204 here kind of roughly allocated. That doesn't mean we'll take down a swad of 204 all at once. It'll probably be done in tan so in that vein, if there's, excess funds and we want to reallocate when the 5090s come out, I'm sure, we'll do so. I currently not envisioned here, but I think we should be flexible over time for But Neil, I was just going to say if you could please take that on, that'd be great. + +Anil Murty: + +Anil Murty: Yeah, and that's a good question, one of the other things to keep in mind here, and Chen, keep me honest on these numbers because we did them a while back. I may be, confusing some of them. the numbers that are on this chart that Tyler is sharing, these include GPUs that are committed currently and GPUs that will be added in the future… + +Cheng Wang: That's + +Anil Murty: because as Chang said, if you go and look at network today pretty much all the GPUs of all the models are being utilized and so our utilization rate is really high. What that means is that there are actual customer workloads running on the GPUs that we have committed contracts to right now. And so what that means then is that as these contracts get to their end, we can't just abandon the existing GPUs that have customer workloads running on them. So we have one of two options. + + +### 00:40:00 + +Anil Murty: we can either work with those existing customers and offer them potentially the next generation GPU and then transition them to these new clusters or we can continue maintaining the existing clusters. So I think we'd have to sort of look at these a little bit on a case by case basis. but your point is completely valid which we have to look at the next generation of GPUs in many of these cases. + +Tyler Wright: Excellent. Thank you. + +Zeke Ezagui: Yeah, that makes sense. and my next question is there was added after some discussion the 5 to 10% for community members. what's going to be kind of the process on if I'm a community member, how do I go about trying to get, approval or whatever getting some incentives to do so? what's going to be the process for + +Cheng Wang: + +Cheng Wang: I think we'll have to probably iron that out when the time comes. It really depends on I think the parameters that we set or are roughly that of a tier 2 data center requirements, right? So, with that being said, I think as long as the u community provider can uphold these, of course, quality, availability, density, all those requirements, and I think it's really just an open discussion. I don't think there's anything too structured at this point in time. Anal, I hate to hot potato this over to you once again, but I'd figure it seems pretty straightforward, the structure here or the requirements. + +Anil Murty: + +Tyler Wright: Go ahead and + +Cheng Wang: So, I don't imagine there's too much vagaries here to deal with. + +Anil Murty: Yeah,… + +Anil Murty: I think yeah, so I think Tyler is sharing that portion of the screen, Zeke. after some of the feedback from you and other folks that have been really strong providers on the network for a long time, we added those bullet points specifically for trying to outline what would be potentially the criteria for somebody that could be eligible for the community portion of this pool including the percentage allocation to community providers. + +Anil Murty: So, definitely take a look at that if you haven't already and please provide feedback if that sounds good to you. But that's a general idea. and again, this is kind of a precursor to us implementing an onchain mechanism for allocating funds to all community providers and not just a subset of them. + +Zeke Ezagui: Yeah, makes sense. So that just be, a GitHub discussion. + +Zeke Ezagui: That would be messaging someone at the core team. that's kind of what I was talking about. + +Anil Murty: That's correct. + +Anil Murty: Yeah, it'll be pretty manual for now because we just don't have the resources within the core team to go and implement what is needed for us to be able to have onchain incentives and not get into some of the problems that some of the other GPU marketplaces have had with civil attacks and… + +Tyler Wright: Wait, you + +Anil Murty: and spam accounts and things like that. + +Anil Murty: + +Zeke Ezagui: And… + +Zeke Ezagui: if I'm interested, would that just be, sending you or chain a message? Would that be sending Tyler message? Would that be, doing the GitHub discussion? + +Anil Murty: yeah so I think… + +Anil Murty: if there are people that are within the community that meet the requirements of so I guess there's two steps to this right one is the community and people that review this proposal agreeing on the criteria that's outlined in the proposal here specifically the bullet points below the + +Anil Murty: + +Anil Murty: that Tyler is sharing. and then assuming that that is good and this proposal actually passes then the pro process would be if the community provider meets those requirements then the core team being the stewards of driving the provider incentives pilot would ensure that those criteria are met and… + +Anil Murty: then ensure that there is fair allocation of resources across all the providers that meet That criteria. + +Tyler Wright: much appreciate the questions and… + +Tyler Wright: the responses. Again, if anybody has anything that any other questions, thoughts, feel free to drop in the GitHub discussion. I'll follow up with any updates as pertains to just structure. again, as Anil mentioned, it's going to be manual, but we can fine-tune where the best place for people to interact. and I'll make that a bit I'll drop a comment over the next couple of days with how to do that. Again, this is on chain for vote right now. + + +### 00:45:00 + +Tyler Wright: so again please vote if you haven't and again continue to drop in messages in this discussion and we'll continue to track it at sick rs or Any other questions as it pertains to PIP number two? Terrific. I'll also drop in the recording and transcript from this steering committee meeting as a comment as well just so people have it easily Real quick another discussion update that I want to call out Adam with support from other members of the team has updated best practices for governance proposals. + +Tyler Wright: Again, this governance proposal is the best way to get funds from the community pool. Again, the community pool is available to all members of the community and is a great resource to get people building and helping to grow the Akash network through feedback, through the last year plus of seeing things in action. Again, there have been some updates made to the governance proposal guidelines. So, please take a look at those and it'll tell you, how to start off, from an idea to getting a request from the community pool and having conversations with the community. So, again, if anyone has any questions, feel free to drop them as comments, but play please take a look at that discussion around best practices for a kosh governance proposals. All right. + +Tyler Wright: Is there any other discussions that anyone wants to talk about right now? All right. If not, then usually this is a portion where we just open it up for discussion. real quick, I know we only have nine minutes left. I want to be respectful of folks time because I know people take time out of their busy days across both the core team as well as other community members. So is there any other topics that anybody wants to discuss right now? much appreciate rare protocol team for joining us. thank you to Chang and Anneil for fielding questions around PIP02. again please get involved in discussions. + +Tyler Wright: Please stay up todate on all the things that are going on across the Akos community by looking at the project boards. There's a number of ways to contribute if you look at the bounty boards. As you look ahead again, there's a working group for Akos YouTube that will be added to the calendar soon. ZLE meetings every week. there's also going to be, SIG chain where we'll talk a little bit more about the Cosmos SDK 47 upgrade. again we get updates on all things provider related at sig providers. So there's just a number of meetings that happen throughout the month where you can get involved have very very specific discussions around themes and topics. I know there's a number of folks that are going to get more involved in SIG support. Again support is where issues that are related to the AOS blockchain and just a core codebase go. + +Tyler Wright: + +Tyler Wright: So again, if you want to get involved and contribute there or just learn more about how Akos works, under the hood, please get involved in sick support. Much appreciate everyone's time today. Look out for announcements on discord on social media and again just continue to just reach out and stay involved. But again, much appreciate everyone's time today. + +Tyler Wright: Hope everyone has a great rest of their day and… + +Robert Del Rey: Thank you,… + +Robert Del Rey: Tyler. Stay safe, everybody. + +Tyler Wright: a happy Halloween if you Be in the metaverse. + +Zeke Ezagui: Thanks everybody. + +Cheng Wang: Thank you Tyler. Take care. + + +### Meeting ended after 00:49:38 👋 + diff --git a/sig-chain/meetings/020-2024-10-08.md b/sig-chain/meetings/020-2024-10-08.md new file mode 100644 index 00000000..b4890828 --- /dev/null +++ b/sig-chain/meetings/020-2024-10-08.md @@ -0,0 +1,137 @@ +# Akash Network - Chain Special Interest Group (SIG) - Meeting #20 + +## Agenda +- Akash network updates and validator relations +- Network upgrade: Cosmos SDK 47 and testing +- Validator expansion and token distribution discussion +- Community involvement and foundation delegations + +## Meeting Details +- Date: Tuesday, October 8, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://z6a66fr3xktpajzb5upa5vnaxjls3e4skjeyhce46ctxuhk4fzja.arweave.net/z4HvFju6pvAnIe0eDtWgulctk5JSSYOInPCneh1cLlI) +- [Transcript](#transcript) + +## Participants +- Tyler Wright +- Artur Troian +- Dominikus Brian +- Scott Carruthers +- Hiroyuki Kumazawa +- B S +- Daniel Ishaya +- M R +- Rodri R + +## Meeting Notes + +### Akash Network Updates +- Tyler Wright opened the meeting, discussing the role of SIG Chain meetings in addressing Akash Network blockchain topics, particularly validator relations, network upgrades, and overall health. +- Highlighted recent async discussions in lieu of last week’s meeting to accommodate the heavy workload of the Overclock Labs Core Team. + +### Cosmos SDK 47 Network Upgrade +- Tyler shared that the focus of recent efforts has been the Cosmos SDK 47 upgrade, a significant project led by Artur and the engineering team. +- Artur provided a comprehensive update on the SDK 47 upgrade: + - **Testing Approach:** Localized testing using snapshots from the mainnet for migration validation. + - **Challenges:** High memory requirements, with upgrade processes needing over 384GB of RAM to run reliably. This memory demand has presented logistical issues in setting up sufficient test environments. + - **Progress:** Artur shared confidence that testing could yield reproducible results soon, with hopes to proceed by week’s end. +- Artur also noted that this upgrade process has unblocked other network functionalities like basic blockchain interactions, state synchronization, and deployment creation. + +### Validator Expansion and Token Distribution +- Dominikus raised questions on validator expansion, referring to Akash’s Tokenomics document that suggests gradual increases in validator numbers. +- Artur responded that further validator increases could strain network performance due to latency issues, especially during periods of high transaction volume. + - Emphasized the need for decentralizing token distribution among validators, though the current validator cap is considered sufficient. + - Highlighted that anyone can create a validator, but they must secure adequate delegations to enter the active set. +- Tyler added that foundation delegations now require higher standards, including infrastructure robustness and technical capability. + - Noted that as the network matures, foundation delegations are increasingly awarded to participants showing sustained, meaningful contributions to the Akash ecosystem. + +### Community Involvement and Next Steps +- Tyler discussed the ongoing community testing initiatives, encouraging volunteers to assist with SDK 47 upgrade testing. + - Mentioned that additional channels or Discord updates would provide information for interested community testers. + - Urged community members to reach out if interested in joining the testing efforts and to stay active on SIG Chain’s Discord channel for updates. +- Tyler concluded the meeting by reiterating the importance of community engagement in validator roles and thanked participants for their time and contributions. + +## Action Items +- **Artur Troian:** Complete initial reproducible testing for the SDK 47 upgrade by the end of the week. +- **Scott Carruthers:** Continue developing the testing plan for network upgrades and coordinate with volunteer testers. +- **Tyler Wright:** Maintain updates on testing progress and share announcements on the SIG Chain Discord channel. +- **Community Members:** Reach out via SIG Chain Discord to join testing efforts for the network upgrade. + +# **Transcript** + +Tyler Wright: All right, welcome everybody to SIG Chain monthly meeting today is October 8th. 2024 during the Special Interest group for the chain, This group comes together to talk about everything related to the Akash network BLOCKCHAIN. That includes validators relations network upgrades. And just the general health of the chain, + +Tyler Wright: This meeting is led by members of the Overclock Labs Core Team who is built and maintains the Akash network. Usually we talked about again network upgrade related items this month especially and for the past few months we've been talking about the Cosmos SDK 47 upgrade which is a massive undertaking led by our turn other members of the core engineering team. + +Tyler Wright: I know last week we talked async and did not meet because there's just a number of heads down efforts going on again. There was proposal, let's put on chain to support all the work that turn. The rest of team have been doing that proposal pass on chain. And I know that we're getting closer and closer to testing and then potential network upgrade after against some initial internal testing some client testing and then beyond With that said, I will hand it over to Archer to talk about any updates or anything specifically, he wanted to talk about related to the Akash Blockchain. + +Artur Troian: Thanks a Good morning, everyone. it's been quite a while. We can get an update on the Sdk47 and This sort of Could freeze. For the actual upgrade parts, a couple weeks ago and things don't quite well. We've been usually testing it locally just as a reminder, the way we do it is we take a snapshot from current We do think Old Test 95. That allows us to export. and Manet state into the Genesis are also validators set for test purposes and then just use that Genesis as the seed to the desktop and they're just make sure that all of the + +Artur Troian: API changes and the migrations for working correctly. So the SDK 50 actually has the test notification done in place, but as we are trying to own different fight, there's no way. We can reuse that, also our test infrastructure and all of the environment is built using our approach, and I think we're gonna continue using it for the next to disable future. Anyways, one of the challenges that we have is because of some great is so massive. a one node during the upgrade phase must have seen in 70 gigabytes of RAM. So, To do Testing, you obviously need at least two preferably Make sure that the consensus is not broken so that just might multiply memory by three with safety margin. + +Artur Troian: And you can see easily that really for the single tasks. It takes 384 too much 400 wives of RAM that. And You can easily get this machines distributed, but once again, you're random locally, we're trying to run them In the same machine you like local container or just wider to capture walks and make sure that everything is doing. All right there and that was sort of really challenging for us to get those machines. But I think we sorted the swings out and have environments at this stage. So as soon as I have confidence, that environment is producing reproducible results for the testing. You're just gonna cost understand diet and far up. I do hope that we do it this week. + +Artur Troian: But it doesn't necessarily mean that all other work is done. Especially the provider part but that will unblock Everybody and start testing, just basic blockchain, things related to stay in top and sending deployment creation and so forth. Scott is working on the tests, sort of less plan on how things should be done, and you'll be communicating quite shortly. And I think that pretty much summarizes it, any questions. + + +### 00:05:00 + +Artur Troian: Right about you. + +Tyler Wright: Appreciate that. Artur again, as Artur just stated, once the initial notify tests are passing. That'll unblock a number of other efforts, including documentation around some of the testing that will get done by, members of the sh Validation etc that have already volunteered their time and efforts to support some initial testing. So again, the idea to test everything across the network state game, just basic deployments etc, to make sure that everything is kind of working as planned, and As desired. I did want to see if anybody had any questions as pertains to next steps. For the network upgrade. + +Tyler Wright: Again, you can kind of track all it's going on inside Github, both inside the projects and then elsewhere. I know the work is again open source, and public Artur continues to work on it. So, does anyone have any questions related to the Cosmos S 47 upgrade. + +Tyler Wright: Does anyone have any questions or any topics that they wanted to discuss related to just the cash blockchain in general? Validators etc, that they wanted to bring up at this time? Go ahead, tell me. + +Dominikus Brian: Yeah. Hi guys. I will have this little questions The numbers of validators. So I have been revisiting sort of the akas. Paper on the Tokenomics. And it says that the number of delegators and delegations and also validators in general going to increase over time. So we have increased so from 80 something to 100 in recently how this gonna go going forward, how fast that they increase going to happen. + +Artur Troian: I know, so I don't think in general, the increase in the validators. Means to pursue some sort of effort and one of them was to sort of the centralized all of the tokens, right? The issue is we see in this stage, even they use the hundred qualitators, Second distribution is not sort of spread enough to fulfill those Unreadators and Keep in mind that increasing amount of validators has consequences, And one of them is increased latency, especially when I'm usually a huge models transactions and that just can imply on the health of the network. + +Artur Troian: So to be frank with you, I'm yet to see the need to increase the gap. And if there's somebody else needs to become a validator, definitely writer was so far, 200 or 2,000 token state doesn't benefit natural or community as a thing, right? So I would say. There should be quite just 12 reason to input to increase the gap and I believe many networks, including Cosmos. + +Artur Troian: Osmosis I believe they had a little concerns about resin up the limit. Just simply because of the performance construction. But do you have any particular reasons in mind? + +Dominikus Brian: Yeah, because there is guys interested in, becoming file data and they're thinking about if it's possible for them to spin off, too. Actually a cusvale, daters could be independent team. but sort… + +Artur Troian: The … + +Dominikus Brian: instead of one the sort of thinking, too, + +Artur Troian: there is nothing preventing them from spinning, the validator, It's the question is they need to get delegations? And I don't see. + +Dominikus Brian: Yes, that's fine. + +Artur Troian: Yeah, and I don't think, they have to find a way to get a delegations. And being validator is just not only working getting the money. This is the question is either trust for the can I take my tokens there and so forth? And once again there's a huge concern from the development perspective and respect about performance and we've seen + + +### 00:10:00 + +Artur Troian: This is a 25% of existing active set the knowledge show on time for the network of gray and it really gives Susan Burden for entire team to reach out and building them doing them, great times. And it's gonna be just worse. And if you increase the amount threshold on that Tuesday, actually data. But once again, everybody can create a holiday, it's not + +Artur Troian: It's not the creation of the validator is limited in just the amount of interactive style that. So if they create every data and they get an obligations by themselves to at least start or some like a set of mentioned, there is the foundation, delegation they do, something you do for community, they can get delegations as well, so that can help. But just too much to summarize my point. It's not just feasible this moment to do that. + +Dominikus Brian: Okay, great, thank you. ideally proactive and then supportive kind of Played data set, maybe also delegated delegations will be more of interest if they are invested in a long term and active toward contribution. Okay. + +Tyler Wright: yeah, I'll just add + +Tyler Wright: As I participated in the program and help create the framework. Again, if you look at the discussion that I've attached in the Chat, for foundation delegations. the core is looking for folks that are, interested in kind of smaller Drips, there are requirements for receiving foundation delegations, and the idea is that you are contributing something meaningful and long-term to the akash network projects. So I think in the past especially when the network was very new up time and voting was, the criteria think. Now there's so much interest from so many teams and individuals that are looking to validate on their cost network that the criteria for receiving foundation delegations that's just gone up. There's just more And as Artur + +Tyler Wright: And we are interested in folks with the proper infrastructure and the technical capabilities and those are hands-on. Because again in historically there have been a couple of folks in the active set that have not been as technical or hands on So as a network continues to mature again, the validating set values that will continue to mature. I don't know if it necessarily needs to grow but it's Artur mentioned. Anybody can set up a validator on Akash it's just about having the proper amount of tokens to get into the active set which is at a hundred right now and I don't think there's any plan. To increase that anytime soon. + +Tyler Wright: Any other topics related to their cost blockchain network, upgrades or validators that anybody wants to discuss right now. + +Tyler Wright: All again, anticipate hearing from members of the core team sometime soon, on initial testing cases, I know there's some people on this call and in the community, what are going to be listening to this call later that have already again volunteered? Their time to help those people will be called upon when it's time to do some initial testing. So, look out for announcements there, we may have a couple of improv who meetings or Howard or set up a channel for those are testing. So again, just look out for some more information discord. If you want to get involved and have them reached out yet, please reach out to myself or another member of the core team. And we'll point you in the right direction just announce yourself in SIG, Chain Discord, channel. + +Tyler Wright: For Appreciate the update from Archer much appreciate the conversation again, we will be working together. I'm sure soon on all things related to sick chain over the next couple of weeks especially in testing and then there will be updates on when a network upgrade is scheduled and we'll make sure all validators and all folks in the community are aware of that. But again, appreciate everyone time today. I hope everyone has a great rest of your day and we'll talk online soon. I'm sure. + + +### 00:15:00 + +Tyler Wright: Bye. + +Artur Troian: Thanks everyone. + + +### Meeting ended after 00:20:09 👋 + diff --git a/sig-clients/meetings/018-2024-11-13.md b/sig-clients/meetings/018-2024-11-13.md new file mode 100644 index 00000000..b4d05880 --- /dev/null +++ b/sig-clients/meetings/018-2024-11-13.md @@ -0,0 +1,127 @@ +# Akash Network - Clients Special Interest Group (SIG) - Meeting #18 + +## Agenda +- Updates from the Akash Console Product Team. +- Discussion on recent features and enhancements. +- Updates on the Cosmos SDK 47 Upgrade and its impact on clients. +- Open floor for questions, discussions, and updates from other teams. + +## Meeting Details +- Date: Wednesday, November 13, 2024 +- Time: 08:30 AM PT (Pacific Time) +- [Recording](https://blzzgvq7wf74w6qjclppk66qbckfe7xzngfnrlozgwkdguub7u5q.arweave.net/CvOTVh-xf8t6CRLe9XvQCJRSfvlpitit2TWUM1KB_Ts) +- [Transcript](#transcript) + +## Participants +- Tyler Wright +- Maxime Beauchamp +- Denis Lelic +- Anil Murty +- Jigar Patel +- Joao Luna +- Benjamin Aguirre +- Rodri R +- M R +- B S +- Maxime Cyr + +## Meeting Notes + +### Opening Remarks +- **Tyler Wright** welcomed participants and provided an overview of the SIG Clients meeting. + - Highlighted the bimonthly cadence of the meeting due to limited availability. + - Aimed to facilitate discussions on pain points, blockers, and updates for teams leveraging Akash APIs and related integrations. + - Mentioned this was the last SIG Clients meeting of 2024. + +### Akash Console Updates +- **Maxime Beauchamp** presented recent updates and features for the Akash Console: + - Introduced fiat and credit card payment support, enabling users to deploy on Akash using credits purchased with credit cards. + - Revamped the deployment page for ease of use. + - Implemented a free trial system offering $10 credits without requiring an account, enhancing user accessibility. + - Launched a feature for automated deployments linked to repositories (e.g., GitHub, GitLab, Bitbucket). + - This feature allows automatic deployment updates upon changes to the specified branch. + - Released the Cosmos MetaMask snap wallet integration, enabling AKT support via MetaMask. + - Stabilized free trial support to prevent abuse and misuse. + - Significant improvements were made to streamline backend operations and support higher console usage. + +### Cosmos SDK 47 Upgrade +- **Tyler Wright** discussed the upcoming Cosmos SDK 47 upgrade: + - A testnet is in phase one, with core engineering and community members testing CLI functionalities. + - Phase two will include a sandbox environment for developers to test integrations and make adjustments. + - Documentation and further announcements will be provided via Discord and SIG Clients channels. + +### Open Discussions +- Participants were invited to ask questions and discuss issues related to Akash API, AkashJS, and integration solutions. +- No additional updates or discussions were raised during the open floor session. + +### Closing Remarks +- **Tyler Wright** thanked the Akash Console team for their work and the attendees for their participation. +- Encouraged developers to follow updates and announcements in Discord and SIG channels. +- Concluded with best wishes for the year-end and an invitation to future SIG meetings in 2025. + +## Action Items +- **Community Members:** Test new Akash Console features and provide feedback via the SIG Clients channel. +- Monitor Discord and other communication channels for updates on the Cosmos SDK 47 upgrade. +- **Akash Console Team:** Continue improving features and address issues reported in the Console repo. +- **Participants:** Share ongoing projects and integrations in future SIG meetings for collaboration and feedback. + +# **Transcript** + +Tyler Wright: All right, welcome everybody to SIG clients. This is a bimonthly meeting. + +Tyler Wright: During this special interest group for clients on members of the community and teams that are building clients on a Akash come together to talk about any blockers, pain points, issues etc. This has typically been a monthly meeting but as of the last six months with a number of teams building various solutions on top of Akos and limited availability where this meeting really ultimately ended up with a number of people saying that they were going to join but ultimately that Kosh console team is one of the only teams that would consistently join. We change the cadence to every other month. + +Tyler Wright: Again, this is a meeting for folks that are building easier ways to deploy onto the Akos network. this is for folks that are leveraging the AOSH API or AOSJS or any other integrations to again come together about core code, talk about any pain points etc. We oftent times get updates from the Akash console product team at Overclock Labs about a number of things that they've been working on over the last month or two. again this is the last TIG client's meeting of 2024. there is a number of things that are being worked on by the core engineering team. + +Tyler Wright: you can find those items on GitHub in the projects area. There is a road map for again product and engineering where you can track some of the items that are on being worked in progress right now in testing and on the road map for the future. Again, I know that the members of the Overclock Labs core team are continuing to update the road map and add a number of items based upon priority and importance as we continue to end the year and move into 2025. I know there are a number of teams that have reached out to me publicly and privately that are building integrations and clients and ways to deploy onto the Kasha network. + +Tyler Wright: I think some folks said that they won't be able to make it today. Some folks are going to be ready to go live in the next month or two. so, again, I'm trying to stress those teams to at least join these meetings to give a demo of, their applications in d. Without further ado, unless anybody has any agenda items, I want to hand it over to Max B who usually leads us through just updates on the console team. I also brought in Dennis who leads design on many of the project products as well as marketing, branding, etc. because I know there's just been a number of updates over the last couple of months on the console side. + +Tyler Wright: At our last SIG providers meeting, the Ptor team gave an update on all things related to the Akos provider on the console. This is something that's a part of the console 2.0 effort that also gets discussed during SIG clients. But again, I just want to see if there's any I'll hand it over to Max B and potentially Dennis to talk about what's been going on on the Kosh console front. see if there's any questions on anything related to API, AOSJS, or if there's any other teams on the call that maybe want to talk about potential solutions. the max speed. Feel free to take it + +Maxime Beauchamp: Thanks, There has been a lot of updates definitely in the past two months for console. I'm gonna share my screen so it's easier for everyone to So yeah, the main update in the past two months is definitely fiat payments or credit card payments. So yeah, now users can deploy on a cash using their credit card so they use their credit card to buy credit on console and use those credits to pay for deployments. + +Maxime Beauchamp: So just a quick little demo and yeah at the same time this page for new deployments has been revamped and one of the new features that has been released last week this week and also yeah this is a new thing as well because we're getting spammed by a lot of new accounts for this and u so yeah you can create deployment without signing a transaction or using your own wallet which is a very innovative and game changer for a cash. We've had a record breaking usage through console in the past month because of that. + + +### 00:05:00 + +Maxime Beauchamp: and yeah right now I'm using my own account and I already added my credit card but normally there's a free trial that we implemented which makes it possible for users to use a cash without even creating an account. You can just click on start trial you get $10 of free credits so you can try a cash out without any commitment. and also one of the newest feature as well that was released this week it was done by a community member slash team called human hq. + +Maxime Beauchamp: they've been doing a lot of great work on the website and console and we released that this week which is basically a versol deployment experience. So you can connect your repo or access deploy any repo by just putting up the URL or connect your GitHub bit bucket or GitLab whatever repo and it'll just fetch the repo and deploy it automatically and also update itself when you commit on the main branch or whatever branch you specify. + +Maxime Beauchamp: So this is one of the core features that is part of the console 2.0 project which is available or you can see it on the GitHub project board where we keep track of all the tasks related to that. That was one of the big biggest feature that we wanted to release for console 2.0 know and so yeah you can try it out give us your feedback on it works pretty well not going to go into too indepth demo as of now but wanted to mention it we also added the Cosmos Metallask extension snap wallet so you can connect + +Maxime Beauchamp: your MetaMask wallet which contains a AK support through MetaMask snaps which was done by one of the community members in the past year or so and it was finally released in the past two months. what else? I think this is mostly We done a ton of work behind the scenes for free trial support because it does attract a lot of abuse and people trying to game it. But now we stabilized it and it's a very good thing for a cashache. + +Maxime Beauchamp: So yeah, that's basically it. + +Tyler Wright: Thank you, Max, for going through a number of new features that you and the rest of the team have been working on for some time. I know again wider announcements are going to be going out in the future. but again, if anybody wants to test some of these features that hasn't already tested some of these features, again, feel free to reach out inside the SIG clients channel. But major shout out to all the work from again the product team across a kosh console. Again we'll save any conversation related to the provider side of console for sig providers but I know anal has talked about the console 2.0 plan in general during these SIG clients meetings and that plan is in full motion. + +Tyler Wright: Again, you can look at the product and engineering roadmap to see where things are. But I know both on the deployment side and on the provider side, there've just been a number of updates over the last couple of months and a lot of improvements and continued improvements. Just as a reminder if anybody has any issues that they see related to the Kosh console again inside the console repo there is an area for issues and people can open up any issues. again Max and the rest of the team do a good job of responding to comments or responding to issues and again we talked about it async and s support as well. + + +### 00:10:00 + +Tyler Wright: Any questions on anything Akos console related and the update from Max and the rest of the team again I know there's some other teams either here or that are going to be listening to this call later that are building solutions on top of the Akos network leveraging the AOS API and AOSJS. I just wanted to see if there was any questions that anybody wanted to talk about live as it pertains to the Akash API, AOSJS or any other forms for integrating with the AOS network. Cool. + +Tyler Wright: One thing that we've also talked about during the steering committee as well as SIG chain which we'll talk about next week in a little bit more detail is around the upgrade. Again, the Cosmos SDK 47 upgrade will affect clients. So there is a test net that is in phase one right now with members of the community as well as members of the core engineering team that are working on just again all the actions and functionality of the CLI postcosmos SDK 47. so again there's a test net active right now that's being worked on. + +Tyler Wright: Once that phase one is complete, then folks that are building clients are leveraging the API integrations, there will be a sandbox test environment on those teams to see the updates to the Cosmos SDK47 and make any necessary changes. There will be documentation available too. So again, please look out for announcements across Discord, SIG clients, or just various other channels for next steps there. But just again that's coming out in the next couple of weeks leading up to the new year. So just keep your eyes peeled for announcements there if you're building an integration onto the Kosh network and leveraging again the API or JS. + +Tyler Wright: I did want to see if there's anybody else that wanted to talk about anything related to clients. Cool. If not then again you all can have some time back. Again much appreciate everyone joining the last sick clients meeting of 2024. Again between meetings there will be some updates in terms of Cosmos SDK47. So if you are building an integration, just look out for announcements in Discord and other channels. again big round of applause all the work that the Clash Console team has been doing. so again please look out for continued updates on that clash console side. If anybody has any questions or comments feel free to drop them in SIG clients channel. And then again I hope everyone has a great rest of the month and year on the client side. + +Tyler Wright: + +Tyler Wright: But there's a number of other ways to get involved with So feel free to join another SIGER working group. but again, thank you Max for the updates. Thank you everyone for your participation today and this year. And I'll see you all on the client side in 2025. + +Maxime Beauchamp: Thanks, Tyler. And thanks + +Tyler Wright: Appreciate you all. + +Rodri R: to you both. + +Tyler Wright: Thank you all. + + +### Meeting ended after 00:14:40 👋 diff --git a/sig-design/meetings/023-2024-11-13.md b/sig-design/meetings/023-2024-11-13.md new file mode 100644 index 00000000..0105beef --- /dev/null +++ b/sig-design/meetings/023-2024-11-13.md @@ -0,0 +1,289 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #23 + +## Agenda +- Discuss updates on Akash YouTube channel. +- Review ongoing projects related to branding, merchandise, and event designs. +- Updates on Akash website and documentation working group. +- Address pending items from previous meetings and upcoming plans for Akash Accelerate videos. +- Provide an open floor for participant contributions, feedback, and questions. + +## Meeting details +- Date: Wednesday, November 13, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://ji5fpsj5wsui75zccj6ndnhl56hsuy5ygdcwrq4swjapnxdry4dq.arweave.net/SjpXyT20qI_3IhJ80bTr748qY7gwxWjDkrJA9txxxwc) +- [Transcript](#transcript) + +## Participants +- Tyler Wright +- Denis Lelic +- Robert Del Rey +- Tomoyuki Yasukawa +- James +- B S + +## Meeting Notes + +### Introduction and Context (Tyler Wright) +- Provided an overview of the SIG Design group’s responsibilities, including visual communication, marketing, content creation, and merchandise. +- Highlighted the oversight of the Akash YouTube channel and website working groups within SIG Design. +- Announced an upcoming website working group meeting scheduled for the following day to discuss Figma designs and content improvements. + +### Updates on Akash YouTube Channel (Led by Robert Del Rey) +- Shared updates on completed work during phase one of YouTube channel improvements. + - Reorganized content and removed outdated materials to enhance relevance. + - Updated the introduction video to better align with current branding and focus areas like AI and machine learning. + - Improved video descriptions with clear calls to action, relevant links, and a streamlined layout. + - Created visually cohesive thumbnails that adhere to Akash’s branding. +- Addressed the next steps for steering committee videos: + - Discussed fade-in and fade-out adjustments for a polished viewer experience. + - Proposed scheduling and progressively publishing these videos with a dedicated playlist. +- Acknowledged pending work on Akash Accelerate videos, including a recap video summarizing the event. + +### Merchandise and Event Design Updates (Led by Denis Lelic) +- Reviewed the nearly completed Akash events calendar for 2024, with Neural IPS as the last scheduled event. +- Announced plans to update the Akash swag shop using Shopify templates for simplicity and efficiency. + - Intend to add popular merch items showcased at events but currently unavailable in the shop. +- Highlighted the community’s positive response to event stickers, emphasizing plans to create unique designs for future events. +- Encouraged the community to contribute ideas and designs for upcoming merchandise. + +### Branding and Website Updates (Led by Denis Lelic) +- Introduced recent changes to Akash’s branding, including the adoption of new primary and secondary fonts (Intern and serif). +- Shared progress on updates to the branding manual, to be finalized and shared with contributors. +- Briefly discussed recent and upcoming improvements to the Akash Console, including: + - New trial-to-credit card payment journey for users. + - Enhanced deploy options, including GitHub integration. + - Plans to design and integrate new icons for updated features. + +### Community Engagement and Contributions (Tyler Wright and Denis Lelic) +- Recognized the community’s appreciation for Akash’s merchandise and branding efforts, especially stickers. +- Encouraged community members to join the SIG Design group, contribute ideas, and participate in discussions. +- Noted potential collaboration with a team specializing in 2D and 3D animations for future visual projects. + +### Closing Remarks +- Denis thanked participants for their positive feedback on recent merchandise efforts and expressed interest in continued collaboration on design projects. +- Tyler emphasized the importance of engaging more contributors to support ongoing design and branding initiatives. +- Participants were invited to the next working group meetings for further discussions on the Akash website and related projects. + +## Action Items +- **Robert:** + - Finalize and upload steering committee videos with appropriate edits. + - Review and publish Akash Accelerate videos, including the recap video. +- **Merchandise and Branding:** + - Denis to finalize Shopify template selection and share options for community feedback. + - Update and share the Akash branding manual with contributors. + - Plan new sticker designs and themes for future events. +- **Website Working Group:** + - Discuss Figma designs and page adjustments in the next day’s meeting. + - Collaborate on documentation and new website features. + +# **Transcript** + +Tyler Wright: All right, welcome everybody to SIG design monthly meeting. It's November 13, 2024. During the special interest group for design, the group goes over all things related to visual communication and marketing on this group is a collection of members from the core team, the community that focus on again content creation both written and video content technical documentation. this special interest group oversees the work of the working group for the Akash YouTube channel as well as the working group for the Akash website and documentation. this special interest group for design also covers everything related to acos. network swag that goes out for different events, marketing materials that also go out for different events. + +Tyler Wright: So again there's a number of communication touch points that get discussed during the special interest group for design. Please if there's anything that you want to talk about specifically for me again we have the working group for the Akash website and documentation tomorrow. I know there's a number of folks that participate there and there's going to be some Figma drawings coming soon that we either talk about here today or talk about tomorrow in terms of adjustments and improvements to pages on the website. but today again we just had a working group with the Kash YouTube channel. + +Tyler Wright: I was specifically want to talk about some of the work that's happened in phase one around the class YouTube including the steering committee videos and see if we can get those listed and out of private status right now. I know that Dennis has also been working on a number of videos that are unlisted right now related to Akos Accelerate 2024 and so I wanted to make sure we can get those videos live. I would like to talk about the banner as it pertains to AOS YouTube. + +Tyler Wright: I know we normally would talk about this during the working group session but some folks had some conflict and then after that if there's time I would love to just talk about a little bit more about the digest this is something that BS has been leading but I just want to figure out if there's any blockers or any issues so that we can get an initial PR out there that kind of goes through what's happening in the community as well as this working groups and stere and special interest group and steering committee on a monthly basis and again continue to fine-tune that piece of content from there. Again, if there's anything else that anybody wants to discuss, drop it in. But I'm going to hand over to Dennis because I know Dennis usually is a leader of this group as the head of product design at Overclock Labs. + +Denis Lelic: Thanks, we pretty much talked through the whole intro that I usually do. so one thing I'm not sure if you covered which takes a lot of design resources or our events. this year was a busy year. So we only have one event to go that's neural IPS happening not sure end of the month or beginning of the December. so just like a final final countdown for the event side. + +Denis Lelic: for those of you who are attending these meetings regularly, you probably see we've done a lot of different touch points pretty much everything that events require from booth designs and different materials like merge giveaways. I know Robert here was attending Cosmover, so you probably see some of the stuff that's been done. yeah, and as Tyler mentioned, tomorrow there's a website meeting happening. so I wouldn't take too much time today on that topic. We can go into details tomorrow. + +Denis Lelic: but I think most of the group here is attending that meeting So I'll be happy to see you tomorrow as on the front for the shop.ac.network. I had a look at the Shopify templates. there are some possibilities with the free options. So we don't have to build anything custom. We're going to have a simple Shopify store. So I have my favorite. So I'm just going to share it either on probably Discord. And we'll see if anyone's interested to contribute there as well. + + +### 00:05:00 + +Denis Lelic: We have a lot of merch items that are currently not listed in this current shop. So, I'm looking forward to include those that are often seen in the events but not available in the shop. and apologies for not attending the YouTube meeting. I had a conflict. but I just created a note for myself to deliver that banner and I know I owe you guys a lot of even feedback and stuff like that. So I'll make sure I'll be more involved in that group as well. + +Denis Lelic: but if you guys want to talk about anything related, I know you just had a meeting. but if you want to say anything about YouTube, please feel free to. Yeah, Robert. + +Robert Del Rey: Hi guys, I hope your day is going fine. It's the middle of the week, so yeah, I'm happy to talk a little bit about YouTube and how it's looking so far. I'm ready to share my screen, so I'm going to take over you, Dennis, if you don't mind. All right, thumbs That means Okay, I guess you should be able to see now the Aash YouTube channel homepage, right? This is how we're looking so far. So, in phase one, we mostly reorganize, the existing content. We also deleted some content that was either too outdated or showing people that no longer working in a cache. + +Robert Del Rey: and yeah, we organized this based on the most recent content. We updated the introduction video. before it was a video on what is a cashache. It was like a three years old video and we updated it for this one is more recent. It's a Greg talk and Eric Borheis in the Akash accelerate. This is the thing that subscribers and nonsubscribers see when they visit the Aash YouTube channel. They have for you which is recommended content based on the person our popular these are the videos with the highest view counts. So I guess that's good and normal videos and the future These are videos in other YouTube channels that appear here in the Aash YouTube channel. some of them have a high view count like this one 13,000. + +Robert Del Rey: this one 30,000 and yeah, so we updated also the intro it was only a paragraph but I decided to expand a little bit more about what is a cache, what it does. I tried to add a few keywords like AI machine learning and yeah I don't think of any other links that we're missing here. I guess we're pretty much set as far as this site goes. but we are missing only one thing in my opinion and it's an updated YouTube banner. So yeah that is one thing that I think we're missing. I don't know Dennis if you're working on something like that or maybe you prefer us or BS taking over this and just upload any banner that we come up with. + +Robert Del Rey: + +Denis Lelic: Yeah. we can talk on Discord. + +Denis Lelic: I'm not sure if usually have a group chat but we can put one together where we can just talk about YouTube. + +Robert Del Rey: Yeah, I'll be happy to set up that group chat in Discord with us. + +Robert Del Rey: And sorry,… + +Denis Lelic: Cool. Thank you. No, go ahead. + +Robert Del Rey: you were sending this Okay. + +Denis Lelic: Go ahead. + +Robert Del Rey: And the second thing which I believe is the most critical what Tyler was talking about was our videos that we uploaded. Let me click on our videos here. + + +### 00:10:00 + +Robert Del Rey: So you can see we managed to upload most of the extering comedy call videos with the updated tailor descriptions based on what we spoke on the call. I took the transcripts and based on what we discuss in each of these calls I came up with the description for these videos of course with the help of AI to make it look better and also added some relevant links to more Aash resources. + +Robert Del Rey: For example, I can open any of these videos and you will see a call to action. After the descript after the description, you will see Another call to action about deploying a cache and the link to a cache console and more ways to connect with a cache network. you see it says more about a cache and you see there's nothing below that but don't threat. the reason why it's that way is because when you leave it that way, YouTube adds some videos below this. So basically what people see is a description and below that they see more about a cache and they see three to four videos suggested to them in the description. if we add a link to a specific video, they will see a thumbnail for that specific video here. + +Robert Del Rey: So, for now, I just decided to leave it empty and let YouTube do its magic. so, yeah, at the moment, all these videos are unlisted, meaning that only people with the link can see these videos. And I'm just here to ask you if we can go ahead and We can either go live now with everybody or we can schedule them and progressively publish these videos. whichever way do you prefer, guys? I'm down. + +Tyler Wright: + +Denis Lelic: Yeah, I wasn't unfortunately involved in these meetings. So, I don't know what you guys have settled on. So, I'm just going to let you roll whatever you guys think is best. if you have any opinion, feel free to + +Tyler Wright: I would like to move forward. + +Tyler Wright: The only thing, Dennis, that I would like to get your quick look at is just to make sure that everything looks good from a fade in and fade out perspective. Everything else is just like the steering committee content. + +Tyler Wright: + +Tyler Wright: I would love to just upload all the videos and then figure out a cadence where we're just uploading the most recent steering committee maybe like five days or seven days or some period that's quite short after the steering committee meeting happens. So I would love to get these live and… + +Denis Lelic: That's it. + +Tyler Wright: in a playlist and then we can see if we need to make adjustments from there. I would love to have a steering committee playlist that's fairly high up on the homepage. and then even higher than that, and maybe we can discuss this next, Robert, is Dennis created a bunch of videos for Aos accelerate that I think are unlisted. + +Robert Del Rey: + +Tyler Wright: But I would love to get those listed today as + +Robert Del Rey: Sorry guys,… + +Robert Del Rey: I'm writing just to make sure I don't forget what you say about the steering call video playlist. about the fade in and fade out. Let me do a live demo right now so you can see how the videos look. and we can have Dennis blessing. So let me play real quick. It's a quick 5-second intro. Thanks BS for putting this together. And I edit it in a way that you Tai started speaking right away. usually there is some silence and I just cut that to all the videos to all the 20 student committee call videos. + +Robert Del Rey: Also by the end even though we say goodbye it seems some people stay in the meeting after you end So usually the meeting could be 40 minutes but the recording would be 50 minutes. I also edited that dead error just to make sure that when you say we're done the call is done and one second we jump right into the fade out second and then we have the fade out after you take so yeah that's mostly it that and the thumbnails + + +### 00:15:00 + +Robert Del Rey: this is how the thumbnails look like. this is the design that we went with. We tried to imitate Dennis the best that we could. You see very big a sitting committee the number of the call I was trying to get some acceleration reference and this is what we came up with and of course the aash low name on this corner. So those are the two or three graphic aspects that we are working with in the YouTube side of Akash. + +Denis Lelic: + +Denis Lelic: I see you've put a lot of work there. I know this editing especially if there's a bunch of videos can be really time consuming. So I think everyone here and the whole Akash community appreciates your help around this. it's been too long since anything happened on the YouTube so looking forward to it. even… + +Robert Del Rey: + +Denis Lelic: though even yeah… + +Robert Del Rey: You're going to change that. + +Robert Del Rey: + +Denis Lelic: but even though if I would still prefer if we move rather than we look for some perfection so even if a thumbnail is not perfect it has the basic branding rules it has all the necessary information and even the branding changed a month ago where marketing and some people from the core team decided to introduce some new elements of design. you can see those on the website. but I know you did like a lot of work and I wouldn't go back just to redo all of these + +Denis Lelic: thumbnails and so on and so on. but when we maybe do the next steering committee, we can just introduce the new branding. it's not much a bigger difference. We still have the same color and the what changed is this the secondary and primary font. occasionally the serif. Let me just share maybe the ge. Where is it? Yeah. So there's this ser font happening occasionally. And the next change was this font which is not Satoshi anymore. It's intern now. + +Denis Lelic: but yeah, as I said, these steering committees happen in the past anyway. So the branding is relevant to the time that the meeting happened. so I'm okay with all of these thumbnails, intros, outros. so if you guys wish, we can of course move along and do some u uploading. I mean, it's publishing so already uploaded. + +Denis Lelic: + +Denis Lelic: Yeah, Robert. + +Robert Del Rey: + +Robert Del Rey: Yeah, it's already uploaded and the plan works for Dennis, no worries. we can go ahead and keep the new branding in mind for future videos, which they're going to come. I promise you that. And let's do this. after I set up the group chat on Discord,… + +Robert Del Rey: maybe you can share with us the new branding guidelines so BS can have them in mind when designing the banner for the YouTube page. And at least we can have that with the new branding. What you say? + +Denis Lelic: Yeah. Yeah. + +Denis Lelic: I still have to put together this updated branding manual which is also currently on the website and it just needs to be replaced. I think it's somewhere in the footer. it's called brand resources brand. Yeah, this so download logo kit. It's also I believe here a branding manual is included. So I have to update that one thing if you want to talk about YouTube we still have time. + + +### 00:20:00 + +Denis Lelic: + +Denis Lelic: Otherwise I would just like to cover another topic and that's product design. + +Tyler Wright: + +Denis Lelic: Okay. yes,… + +Tyler Wright: Yeah. … + +Tyler Wright: before we move on, again, I know there's some AOS Accelerate videos. Are those good to publish as well, Dennis? + +Denis Lelic: I can double check just because this happened a while ago six months ago. So just to see what's there I think and all the sessions that happened are there now. But I also have a short recap video of the whole accelerate event and… + +Tyler Wright: + +Denis Lelic: I can also upload that one. It's a two, three minutes long and it just covers the whole day. + +Tyler Wright: Yeah, I think I would love to. + +Tyler Wright: So, it sounds like Dennis, you want to take a look at that before it goes live, but the steering committee videos can go live? + +Denis Lelic: Okay. + +Tyler Wright: Okay, sounds good. and then real quick shameless plug and then also asking Dennis in public directly following this meeting, there's a SIG clients im During that meeting, the Kosh console team will be giving updates on the product side. I'm inviting Dennis there to talk there as at least listen in and see if there's any feedback, but I would love to talk also about the visual communication elements that he's been working on here. So, we'll hear it in two meetings. Go ahead, Dennis. + +Denis Lelic: Today I have backto back meetings. So that's why I couldn't join the YouTube because it was happening for you the first meeting out of one, two, three, four, five. so I just had to do some so yeah product product let me see okay there's some new additions to the console for those of you who use it regularly you're going to see that this thing changed here where users now can start a trial and there's also an option if you start a trial you're going + +Denis Lelic: user is going to convert to the different journey which is a credit card payment. and here is going to offer a switch between a wallet or a credit card payment. new addition is also for example if you go to the deploy there are new options here. build deploy launch container VM and run custom container and here there are a bunch of featured templates and all of these still need icons so I have to do those as well. + +Denis Lelic: yes and there's also an option to deploy through GitHub. so you just connect your account and connect your Git repository and you're good to deploy things from here as well. I got to say some of the stuff that's been newly added is not really just design contribution because developers use this UI component library where they just pull anything they need but if a certain new feature is added where let's say a complete new journey + +Denis Lelic: journey is added then sick design gets involved as So yeah, that's from the front of product design and there's a lot of new features coming to the console in the near future. I know they've been testing some of the stuff, but we'll talk about it when it live or in an hour or half an hour in the next meeting. yeah. Anything else you guys want to talk? We still have Yeah. + +Robert Del Rey: I always have something to say, no, but yeah, really quickly, Dennis, I wanted to also congratulate you about the designs, both for the merch. I'm actually wearing the white Aash Super Club t-shirt now. people Loved it. They also love the black one with the cloudy logo in the back. And the stickers, if they did a sticker competition in Cosmog, a cash would have won the number one. And I will tell you why. Neutron had really good stickers. But if you didn't know anything about the project, you wouldn't know they are from Neutron. But a cash stickers, they cover everything. + + +### 00:25:00 + +Robert Del Rey: the aesthetics was good, the material was very good, but also the reference to a cash network were also very very clear. So that's why for me the stickers got the first place as far as the best stickers go and just wanted to share that with the merch was really and many people passed by the booth and they were impressed by the stickers. They like the Falcon. They like the Bur Khalifa for the Dubai edition, but they also talk about the previous editions and how they were collecting the stamps and stuff about different places where a cashache has been. And quickly wanted to share that,… + +Robert Del Rey: really really good job that + +Denis Lelic: Yeah, thanks. + +Denis Lelic: Yeah, I heard some stories about stickers and people collecting them across different events. I should order maybe a couple of them just to have them stored for the archive somewhere. yeah, but it's good to hear. we have big plans for the whole merch in the next season. so we're probably going to introduce more designs, more items, different themes, and I think as far as I can hear from others and u you as well, those stickers are like a big hit. So we're just going to continue in the next season. + +Denis Lelic: with the whole new bunch of stickers for each of these events. + +Tyler Wright: + +Denis Lelic: So, we're just going to try to always do something unique. + +Tyler Wright: Shout out Dennis. + +Tyler Wright: One other thing real quick. just as a reminder if anybody here on the call or in the community whether it's live events in their own communities and other places again finds people that want to contribute whether it be visual communication content creation please point them in the direction of SIG design. I just saw there was a team that's interested in supporting I think they do 2D and 3D animation. + +Tyler Wright: but again we want to get as many of these teams to join the Discord channel, share their thoughts, ideas, portfolios, and then if they can join one of these live meetings where we can see where they can contribute and add value. I know Dennis is working on 9 million things, has meetings back to back. He still kills it. But again, any support that we can get, I know Dennis would greatly appreciate in terms of new marketing materials, branding, support materials, etc. + +Denis Lelic: Thanks it's not always that bad regards to meetings. Today is just one of those days where a lot of them happen back to back. + +Tyler Wright: That's right. + +Denis Lelic: I would appreciate any design help of course. So thanks and I'll make sure I'll join the next YouTube meeting. I know I said that a bunch of times but no gota got to be there. if you guys want to talk anything else, we do still have time. otherwise, we can just use this time to work on something else. but we'll see each other in 30 minutes in a different meeting. So clients all of you are invited. So see you there. + +Tyler Wright: + +Tyler Wright: And then maybe we'll talk about the blog around the Akash digest during the working group for the Akash website when maybe Bold Panther is there and… + +Denis Lelic: Thank you. Bye-bye. + + +### 00:30:00 + +Tyler Wright: we can just talk about what a PR looks like, any design assets, etc. So, if not today at S Clients,… + +Robert Del Rey: + +Tyler Wright: then we'll certainly see you hopefully tomorrow. And much appreciate everyone's time and energy. Thank you. + +Robert Del Rey: Thank you guys. + +Robert Del Rey: See you tomorrow. + +Tyler Wright: All right. Bye-bye. + + +### Meeting ended after 00:34:08 👋 + diff --git a/sig-economics/meetings/021-2024-11-06.md b/sig-economics/meetings/021-2024-11-06.md new file mode 100644 index 00000000..fabfee8e --- /dev/null +++ b/sig-economics/meetings/021-2024-11-06.md @@ -0,0 +1,126 @@ +# Akash Network - Economics Special Interest Group (SIG) - Meeting #21 + +## Agenda +- Updates on PIP 02 (Provider Incentives Program) +- Community provider participation and guidelines +- General updates and open floor discussion + +## Meeting Details +- Date: Wednesday, November 06, 2024 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://spb2lgjfo22rkltiontajya63on7vc5jg4i77hnsngjdj5xyfkra.arweave.net/k8OlmSV2tRUuaHNmBOAe25v6i6k3Ef-dsmmSNPb4KqI) +- [Transcript](#transcript) + +## Participants +- Scott Hewitson +- Cheng Wang +- Rodri R +- James + + +## Meeting Notes + +### Updates +- **PIP 02 Overview**: + - [Passed on-chain](https://www.mintscan.io/akash/proposals/273) and through the steering committee, with a significant allocation of AKT aimed at bringing more supply to the network. + - It is the largest community spend proposal to date. + +- **Community Provider Amendment**: + - Amendment added to PIP 02 based on community feedback. + - **Allocation**: $1 million (10% of total PIP 02 funds) reserved for community providers. + - **Eligibility Criteria**: + - Strict requirements for resource quality, reliability, and availability. + - Designed to maintain high standards and ensure a positive user experience. + - **Distribution Details**: + - Funds to be allocated on a first-come, first-served basis. + - Maximum cap of $250,000 per community provider to ensure equitable distribution. + +- **Provider Resources**: + - Target resources include H100s, A6000s, and 4090s GPUs. + - Details on resource requirements and application guidelines available in the GitHub discussion. + +### General Discussion +- **PIP 01 Impact**: + - Observed positive impact on daily network spend, indicating successful implementation and demand growth. + +- **Community Feedback**: + - Encouragement for community members to engage with SIG Economics via Discord, Twitter, or GitHub. + - Emphasis on maintaining open communication and leveraging community ideas for network development. + +### Closing Remarks +- Smaller group attendance for this meeting, with fewer updates to discuss. +- Acknowledgment of the community's ongoing contributions and engagement. +- Recording and notes to be uploaded to GitHub for wider access. + +## Action Items +- **Scott Hewitson**: + - Continue monitoring and reporting on the implementation of PIP 02. +- **Cheng Wang**: + - Facilitate communication with interested community providers and guide them through the application process. + - Provide ongoing updates on PIP 02 progress and resource allocation. +- **Community Members**: + - Review [PIP 02 documentation](https://github.com/orgs/akash-network/discussions/696) and apply for community provider funding if eligible. + - Share feedback and ideas through SIG Economics channels. + +# **Transcript** + +Scott Hewitson: All right, everybody. It is November 6th. + +Scott Hewitson: we have it recorded for those that can't attend today and this along with notes will be up in GitHub. I just looked there's kind of a backlog from couple sig economics. So I'll make sure that those notes get updated as well as this one. last talk wasn't a whole lot going on. we talked a little bit about PIP 2, the provider incentives pilot, which has since gone on chain and it passed yesterday was also discussed at steering committee. so has a large chunk of AKT going to bringing on more supply. another prop that recently passed was the Q4 events which passed on Monday I believe. + +Scott Hewitson: + +Scott Hewitson: As always all the reporting on all that is in the GitHub repository for community pool spend requests. we tried to at least from overclock side anyone who anytime we put up proposals want to make sure that we're reporting on it staying in the good graces of the community. All this it's all community dollars. So we have a right to do that an obligation to do that as well. let's see. There was the metam or the final payment for Mystic Labs. if you recall, they had put up a vote for an AKT amount versus a dollar amount. They've since changed that and it passed as well. + +Cheng Wang: + +Scott Hewitson: Yeah, I think that's kind of the major points. Chang, do you want to talk anything about PIP02 at all? just because it is the biggest a community spend prop that's occurred to date. + +Cheng Wang: Yeah, for sure. + +Cheng Wang: For PIP02, one of the things to keep in mind later on addition was the community provider amendment, if you could call it that was edited in the original post where based on feedback from several community members about wanting to be eligible for PIP02 funds from PIP02. + +Cheng Wang: we amended a portion to say 5 to 10% of the total funds available would be allocated to community providers aka those who aren't running data centers as a service right of course there are very strict requirements for availability quality and things like that so I wouldn't want to rehash the language there but please go ahead and take a look at the links that you drop to see that updated language both on chain as well as on GitHub there and the short of it is 10% + +Cheng Wang: % which is a million dollars effectively of the total PIP02 funds will be allocated toward on a come first- serve basis to community providers who want to put their name in the ring and the points of assessment like how we will assess their eligibility will be based on quality, density, reliability all these kind of areas to where we can make sure that all the resources that are brought on my + +Cheng Wang: community providers are of the quality and robustness that potential partners would want to see right in the network because one of the things we have to really ensure is despite the really meteoric growth and a cautious demand at this point in time in fees is one of the things that is stability quality availability all those kind of things so if we have providers who are going to bring resources that u might go down unreliable aren't the quality + +Cheng Wang: not performant as the same GPUs elsewhere will be then that could impact brand quite negatively right and also decrease the user experience so that's something we definitely want to mitigate and we'll likely allocate the million dollars so it's a million dollars in total to community providers it's going to be on a come first-s serve basis point number two point number three is we'll likely limit it to $250,000 right, per community provider such that there's no overwhelm one person taking the entire slice and whatnot, and we'll see kind of how that goes. And anyone who's interested, please reach out to us on Discord, Twitter, email, whatever the case may be. GitHub and we can obviously have these conversations to bring those resources on. And as far as the type of resources, those are of course posted in the GitHub discussion as well. + +Cheng Wang: + +Cheng Wang: So namely H100s, I think some A6000s, 4090s, … + +Scott Hewitson: Thank you for that for the context and… + + +### 00:05:00 + +Cheng Wang: are in the loop as well. So definitely reach out to us and let us know if you are interested. + +Scott Hewitson: the additional color on PIP 02. I think we've had a good I'll say response with PIP01. I mean you just look at daily spend it's going crazy. So hopefully we can build on it and move things a little bit further further in this two-sided marketplace. okay so any going off of PIP don't need to talk about that unless anyone has any questions. I know it's just a small group with us today. + +Scott Hewitson: Does anyone in the group have any questions or any ideas or comments or concerns related to SIG economics? if so, feel free to raise your hand or drop it into chat. I'll just give a couple seconds in case anyone wants to say anything. All right. yeah, we got smaller group today. not a ton of huge major updates, so I think we can cut things a little early. as always, thank you for joining in on these calls. and those that are not here, thank you for listening in. if you have any questions or concerns or anything, please go to the Discord and drop into SIG Economics and, feel free to tag me at hey Huey. + +Scott Hewitson: if you had any ideas, we're always open to ideas and … + +Cheng Wang: + +Scott Hewitson: we get a ton of things from the community members. So, always have our ears to the ground for that. but with that, I hope everyone has a good rest of your day and I'm going to end the recording. Thanks y'all. + +Rodri R: You guys. Thanks + +Cheng Wang: So, it's Thank you everybody. + +Cheng Wang: All And there we go. Thanks guys. + +Scott Hewitson: All right. + +Cheng Wang: You in the metaverse. Hey. + +Scott Hewitson: Yep. Have a good one. Take care. + + +### Meeting ended after 00:07:14 👋 + diff --git a/sig-providers/meetings/022-2024-10-30.md b/sig-providers/meetings/022-2024-10-30.md new file mode 100644 index 00000000..8b6cbc7d --- /dev/null +++ b/sig-providers/meetings/022-2024-10-30.md @@ -0,0 +1,218 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #22 + +## Agenda +- Updates on Praetor team developments +- Provider Console Beta progress and demonstration +- Discussion on PIP-02 proposal and provider incentives pilot +- Updates on trial accounts and white-listed providers +- Open issues, including tainted nodes and operator inventory bugs +- Announcements and follow-ups + +## Meeting Details +- Date: Wednesday, October 30, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://efcdb25mxpxjedpogrnl4gcabiiqrsgfyikp3jxo5dxlucpzlnmq.arweave.net/IUQw66y77pIN7jRavhhAChEIyMXCFP2m7ujuugn5W1k) +- [Transcript](#transcript) + +## Participants +- Tyler Wright +- Jigar Patel +- Deval Patel +- Scott Carruthers +- Andrew Mello +- Cheng Wang +- Zeke Ezagui +- Rodri R +- Vigneshwar Viswanathan +- B S +- Vontario Taylor +- Andrey Arapov + +## Meeting Notes + +### Provider Console Beta Updates +- **Jigar Patel:** + - Demonstrated the new Provider Console Beta. + - Walkthrough of provider setup using the console: + - Connect wallet using Keplr or Leap Wallet. + - Set up provider details including control machine configuration, pricing, and cluster initialization. + - Improvements include simplified K3S integration for both single and multi-node setups. + - Enhanced features for dashboard viewing and attribute management. + - Public testing of the beta to commence after PR review and merge. + +### PIP-02 Proposal Discussion +- The PIP-02 provider incentives pilot proposal is on-chain for voting. +- Participants encouraged to discuss and provide feedback on the GitHub discussion page. +- Potential follow-up during the steering committee for additional clarification. + +### Trial Accounts on Akash +- **Scott Carruthers:** + - Explained the introduction of trial accounts, similar to AWS free-tier. + - Trial accounts currently restricted to white-listed providers to ensure stability. + - Providers hosting trial accounts will receive AKT compensation. + - Increased network bid activity linked to trial accounts noted. + - Open invitation for community providers to join the white list. + +### Open Issues +- **Tainted Nodes Bidding Issue** + - **Raised by:** Andrew Mello + - Issue #253 affecting first-time deployments remains unresolved. + - Prioritized but delayed due to focus on other critical stability issues. + - Commitment to revisiting the issue and providing updates. + +- **Operator Inventory Bug** + - Mixed GPU cluster issues in available versus allocatable resources. + - Andrew to file a detailed bug report for further triage. + +### Announcements +- Upcoming Cosmos SDK upgrade and related testing. +- Participants reminded to monitor the provider announcement channel for updates. +- Continued efforts to streamline the provider onboarding and deployment processes. + +## Closing Remarks +- Tyler Wright thanked participants for their contributions. +- Encouragement to remain active in discussions and follow announcements. +- Meeting adjourned with reminders for next steps and follow-ups. + +## Action Items +- **Jigar Patel and Deval Patel** + - Proceed with finalizing Provider Console Beta and initiate public testing. + +- **Scott Carruthers** + - Engage with interested community providers about joining the trial account white list. + +- **Andrew Mello** + - File the new operator inventory bug. + - Attend the SIG Support call for deeper discussion on ongoing issues. + +- **Tyler Wright** + - Ensure issue #253 remains a priority and drop a note in the support repo. + - Add Andrew Mello to the SIG Support calendar invite. + +- **Participants** + - Review the PIP-02 proposal and provide feedback. + - Stay engaged via the provider announcement channel and Discord. + + +# **Transcript** + +Tyler Wright: All right, welcome everybody to SIG providers monthly meeting on October 30th, 20 During the SIG providers monthly meetings, this group usually goes over anything related to the provider. obviously we have the provider channel and discord. documentation available but any active or live discussions that anybody wants to have regarding anything aos provider related we usually talk about during this monthly meeting. One of the standing agenda items historically has been updates from all the work that Jigger and Dval have been doing in creating Praor as of the last six months. + +Tyler Wright: I believe at this point again the Prador team is now under Overclock labs and has been actively working on the Akash console and a provider experience inside a console. usually we talk to or we get updates from Jigger and Dval and all the work that they've been doing around console 2.0 and the Kosh provider on console. I know there's also been a HIP 02 proposal that is now on chain up for vote. I think some folks may be joining to talk about that. But if anybody has any other agenda items or anything else related to the provider that they want to discuss here today, please drop a note inside the chat and we can get to any of those topics. + +Tyler Wright: there's enough folks from the core team here that can answer any questions if With that said, I'll kick it over to Jigger and Dval because I know there's a number of updates that they've been working on related to Akash console and the provider on console. So, I'll kick it over to them to give us an update on all the work that they've been + +Jigar Patel: Thanks Hey, so I wanted to start with the updates from u work that has been ongoing for provider console beta. and we have created PR and it's on the review right now and I also wanted to demo something today. if everybody agrees on that. Awesome. let me share my screen. + +Jigar Patel: Hope you can see the so basically this is a new provider console. and obviously it will be improved over the time. currently a lot of work is on ongoing right now but let's start with building a provider on it. so first you connect the wallet and obviously you can use caper or lip wallet. so if I use kapper it gives me approve ownership popup. I'm going to approve that. + +Jigar Patel: you might not able to see that pop up but yeah and on this wallet I'm not a provider so it will give me u become pro tab so on Okay. Maybe our node is a little bit behind me. + +Jigar Patel: I just created this wallet and it might not reflect the AD I just sent. yeah so once you wanted to become a provider you can just select the provider you can select the number of servers. + + +### 00:05:00 + +Jigar Patel: So we just removed selecting single and multiload because now we use K3S on both single load and multiload. So you can select how many number of server you want and we'll install K3S on all of them and make a Kubernetes on it. So if you select one for now going to okay and then give your information about the control machine. So let me just copy file to the file next. + +Jigar Patel: So basically it's verifying the access to it. and we'll ask for give the domain name. Then email is optional. Next attribute I can set location region if I want. so central hit here I can set the pricing. + +Jigar Patel: so based on the resources I have so I have four CPU 15 gigs of memory or 16 but one gigs the system takes it storage and the GPU and because I have a GPU right it'll show up the GPU pricing so let's say if I wanted to do 200 on GPU it'll just show me estimated monthly earnings next it will show a password mode or just this be importing wallet. so I'll select the wallet mode and then just copy my website. this is not the one. I just changed my yeah. Yeah. So was the one. Yeah. + +Jigar Patel: So now our building process started and it'll just initialize the G3S and we'll updated the system installing the G clico updating Kubernetes. So we'll just do all this and you say in 13 seconds we installed the Kubernetes on control node. and I'll just go back and change to other wallet or let me just go back to homepage because we are just installing Kubernetes. So we might have a dashboard for it. and you can see it like this is running right now. so if your provider is not online you'll able to see your dashboard look like this. + +Jigar Patel: Basically, it says your code is offline and if your board is online, which is I'm just going to try to find something that is online Yeah, it is online, So, you'll able to see the dashboard, you'll see all the deployments. and then more feature are coming soon. we are adding settings for changing attributes. + +Jigar Patel: those are coming soon you'll able to see that your conforming is connected or not and you are able to create a new wallets on it sorry a new multi-node cluster from it as well. yeah we'll push this update soon after the P merge into beta and we'll open it to testing for public. Thank you. So yeah, that was update from my + + +### 00:10:00 + +Tyler Wright: Thank you very much. I know again a significant amount of work has gone into that from again the console team and other members of the core team that have been supporting. So thank you very much. Cool. a couple of things that we've always touched on again as Jigger has mentioned today and in previous meetings much of the way that providers are being built now is as a result of a updated process that the core engineering team but mostly efforts kind of led by Scott have updated to again the way that the provider + +Tyler Wright: This has done wonders in speaking of speed in which providers can be built. and so again there's documentation that's available to those it's not the documentation that's on the site is still in beta right now. very much like the work from Digger and Dval related to the provider on AOS console. if anybody wants to again build the provider in the beta way, please recap. You can also use the documentation that's available in the Kosh docs. but again all that will be updated in the coming weeks or months as we continue to test and again there's been tests going on for at least six months with this new way to build the so again we have a large sample size of provider stability and all that kind of stuff. + +Tyler Wright: So again, much appreciate the efforts of many folks on this call for all they've done. Any questions on the provider experience on the Akash council? All right. I know some folks who traditionally come to this meeting have conflicts coming out of some other calls. One thing I do want to point out again, there is a pro proposal on chain for the provider incentives pilot number two. This is off of the back of again the first pilot I'm dropping in the GitHub discussion for folks. + +Tyler Wright: if anybody has any questions about the pilot number two how the funds will be used please feel free to drop in a message inside of that GitHub discussion. we might also take some time potentially during steering committee if anybody has any follow-up questions that they might have and they want to talk about it live. Terrific. Is there any other topics that anybody on this call wants to talk about? Go ahead, Scott. + +Scott Carruthers: So I wanted to ensure that everyone on this call was clear especially for those supporting provider builds like Rodri and others in the community and the impact and the use of our AOSH recent introduction of trial instances and possibly some others will have some thoughts on this as well but I'll kick it off. + +Scott Carruthers: so for anyone that's not aware the AOS console recently introduced trial accounts so this is very much akin or synonymous with AWS free tier right so a brand new user to AOS maybe a non-crypto user this wants to experiment with AOS deployments just like they want to experiment with virtual machines on AWS we want to give the ability for someone to easily get started and + +Scott Carruthers: do some initial experimentation on AOS and then eventually obviously if they like the experience and AOSH fits their needs and they would transition out of the trial accounts to paid accounts just as you would in AWS or other cloud environments. The reason I bring this up on this call I are twofold. one I just want to ensure that everyone is aware currently trial accounts are restricted to providers that are on a white list. so obviously if someone is spinning up a cost trial, we want to ensure that they're running on our most stable so we have a white list of providers that, are the targets for trial deployments. so first of all, I just want to make sure everyone was clear on that. + +Scott Carruthers: and then second and again in support of the community I've recently started getting some questions about increased bid because there's so much activity around I think trial accounts are being very eagerly anticipated and I think the community is very excited to use user accounts when seeing a flood of new activity that increases the bid activity on the network. + + +### 00:15:00 + +Scott Carruthers: so if we have any providers that are curious about increased bid activity and we would obviously have to dig into on a individual basis to see if a provider is wondering why there's increased bid activity. We'd have to validate that it's because of trial counts or possibly it could be for some other reason but I've recently heard or fielded some questions on increased bid activity because of trial accounts. let me know if there's any questions on this, but that's basically the two points that I want to make. So, first of all, I just want to make sure that everyone is aware of trial accounts on the AOS network. and that they're currently limited to providers that exist on a white list. I think we're kind of in the mode right now that if other community providers want to be included on that white list, we're willing to entertain that. + +Scott Carruthers: + +Scott Carruthers: So we do have some community providers on that white list currently and we're open to including others so obviously it's a trial account, but the provider is still realizing profits. if a trial account lands on your provider so it's not like the provider would be hosting free compute at that point. They would actually be compensated in AKT just as they would from any other deployment. So again, the two points that I wanted to make was just one, make sure everyone was aware of trial accounts and its impact on providers and the provider white list and also some increased bid activity on the network. Any questions about trial accounts or any of the provider related bits that I just talked about? + +Tyler Wright: + +Scott Carruthers: Yeah, if there's no questions, I think that's it. + +Scott Carruthers: And I don't think I have outside of trial accounts, I don't think I have anything else at the moment. + +Tyler Wright: Thank you very much,… + +Tyler Wright: Just I know that there's a number of moving parts that are happening soon. obviously with trial wallets, fiat payments, the console experience, all the updates there happening on both the deployment side and on the provider side is Jigger and Deval just walked us through. there's a Cosmos SDK upgrade in the works and again there's some testing that is begun and will continue to happen over the next couple of weeks and beyond. I would just ask anybody listening to this or anybody here today. Again, make sure that you keep reminders on and notifications on especially for channels like the provider announcement channel. + +Tyler Wright: I know that Andre and others share date announcements there. Again, if there's any changes that need to be made across the provider or any call outs usually we put those we put those call outs there because obviously it's a permissionless network people giving their emails not always required. So, yeah, again, if anybody has anything, please please make sure that you look out for those announcement channels and stay up to date on all things there. Cool. All right. + +Tyler Wright: + +Tyler Wright: I know we've gone through the agenda and gotten some updates on Akos console and on provider side from Jigger and Dval. Scott went through a bunch of announcements that he's been seeing over the last couple of days related to trial wallets. again, I just want to see if there's any other topics that anybody wants to bring up. I know we've been on here for a little over 20 minutes. but just want to see if there's anything else that anybody wants to talk about at this time. I'm going to take that silence as cool. + +Andrew Mello: + +Tyler Wright: Go ahead, Andrew. Yes,… + +Andrew Mello: Can you hear me now? + +Tyler Wright: can hear you + +Andrew Mello: Okay, great. I just wanted to follow up on the tainted nodes bidding issue that I had brought up on September 18th. that is still an open issue it looks like and that was kind of a priority issue because it affects any user deploying for the first time on a Kosh could potentially hit this bug which leads to a failed deployment. So it's kind of like a critical path that we'd want to make sure is working. + + +### 00:20:00 + +Andrew Mello: And so that's issue number 253 in + +Tyler Wright: Yes, I can drop in a note. + +Tyler Wright: And so I apologize for not doing this beforehand. this is something we talked about in SIG support. We've, triaged it and this is a priority issue. There's just a number of other issues that have become higher priority over the last couple of months related to pod stability, related to some other things that again while this is a priority there's other things that have trumped it over the last couple of weeks. the goal is to get back to it very shortly but we're trying to work through some other related issues. + +Tyler Wright: + +Tyler Wright: I know again we talked about this in SIG support the core engineering team is only so large and so again we're trying to push through as many issues but I can drop a note in issue number 253 in the support repo to just make sure that it continues to get the attention that it should get. + +Andrew Mello: + +Tyler Wright: But again, there's just not enough time and there's a couple other issues that have been more critical that the core engineering team has been focused on. + +Andrew Mello: So I just wanted to again put it out there so it's on the record that this does affect the first deployment experience for any user and… + +Andrew Mello: again thus I thought it should be looked at again. in addition to that I was going to file a new operator inventory bug. I cannot find stability with mixed GPUs. + +Andrew Mello: in the showing of available versus allocatable. I'm having this issue particularly on again clusters with mixed models. not just one model in a cluster and I'll be filing that today as So again more operator inventory issues. + +Tyler Wright: Thank you, Andrew, for identifying those and again u much appreciate when you make these issues. we'll look out for that issue and then again triage it like we have another great call Andrew maybe for you to come to if you have availability is a sick support call to talk a little bit more about these but much appreciate you bringing these up and s providers and then again we'll make sure these get u attention. + +Andrew Mello: All right, sounds good. Yeah, I'll see if I can get added to that sixport calendar invite. Thanks. + +Tyler Wright: Excellent. We'll do. Is there anything else that anybody wants to talk about related to the provider on If not then again we'll follow up with some updates in the provider announcements channel and elsewhere as they are made available. So again please look out for those channels if you haven't already. I think Andrew is again going to file a bug related to the inventory operator. so we'll look out for that issue and then again I'll make sure that Andrew is added to the six support call and we can talk a little bit more specifics about triaging and some of the other things Much appreciate the update from Jigger and Dval. again look out from for continued updates testing coming soon. + +Tyler Wright: If anybody has any questions or comments, please feel free to reach out in the six providers or the providers discord channel or elsewhere. But much appreciate everyone's time today and thank you to all those that are listening later. I hope everyone has a great rest of their day and we'll continue to talk online. But thank you all for the updates and the information. + +Andrey Arapov: Thanks everyone. + +Tyler Wright: Appreciate you all. Bye-bye. + + +### Meeting ended after 00:34:24 👋