From 8c96bd5e70475697157b915fc55be4c07a448fdd Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Sun, 28 Jan 2024 14:06:55 +0000 Subject: [PATCH 001/138] Create meeting notes for Sig-Clients #12 (#468) create meeting notes for Sig-lients Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> --- sig-clients/meetings/012-2024-01-17.md | 157 +++++++++++++++++++++++++ 1 file changed, 157 insertions(+) create mode 100644 sig-clients/meetings/012-2024-01-17.md diff --git a/sig-clients/meetings/012-2024-01-17.md b/sig-clients/meetings/012-2024-01-17.md new file mode 100644 index 00000000..120aa359 --- /dev/null +++ b/sig-clients/meetings/012-2024-01-17.md @@ -0,0 +1,157 @@ +# Akash Network - Clients Special Interest Group (SIG) - Meeting #12 + +## Agenda +- Quick follow up from sig-clients monthly meeting #11. +- Artur Troian update and discussions on Akash API. +- Update on specific Akash clients from representatives present at the meeting. + +## Meeting Details + +- Date: Wednesday, January 17th, 2024 +- Time: 08:30 AM PT (Pacific Time) +- [Recording]() +- [Transcript](#transcript) + +## Participants +- Alani Kuye +- Anil Murty +- Artur Troian +- B S +- Cheng Wang +- Deval Patel +- Greg Osuri +- Jigar Patel +- Joao Luna +- Julia Holden +- Max +- Prashant Maurya +- Rodrigo Rochin +- Scott Carruthers +- Taiwo Omoyeni +- Tyler Wright + +## Meetings notes +#### Tyler Wright: +- Emphasized the goal of alignment among teams building on Akash, discussing tools and solutions for common problems. +- Acknowledged the decision to move the meeting to an earlier time to allow broader participation. +- Mentioned discussions with the Spheron team and the decision to adjust the meeting time. +- The objective is to facilitate participation from different time zones. +- Highlighted updates from the last meeting, including progress reports from teams such as Spheron, Cloudmos, and others. +- Discussed Cloudmos' open-source efforts, particularly the Cloudmos API, and its adoption by teams like Praetor. +- Shared the project board link for Cloudmos' open-source efforts in the chat for reference. +- Teased upcoming discussions, including Artur Troian's insights on Akash API and Joseph's involvement in supporting Akash JS. +- Spheron is planning to share statistics over the last 17 days of January, highlighting their recent work and active leases. +- Tyler emphasized the importance of understanding how people are utilizing Spheron built on top of Akash. +- Commitment to making these statistics available to the community. +- Mentioned a conversation about NodeOps seeking support from Cloudmos. +- The support is specifically related to deployment, not indexing. +- Expressing the hope that NodeOps could join future calls to discuss their needs and receive assistance. + +### Max's Updates on Cloudmos: +- Max shared progress updates from the Cosmos team, focusing on rebranding Cloudmos into the Akash console. +- Announced the completion of rebranding the analytics side, with the launch of the new analytics app imminent. +- Work is underway to make the API more accessible and well-documented to facilitate usage by other teams, with a release planned soon. +- Addressing bugs and issues related to the customers kit, with support added for additional wallets like Leap, Cosmostation, and Kepler mobile. +- Max highlighted ongoing efforts to enhance the user experience for both new and existing users on Akash, with a focus on mainstream adoption. +- Tyler commended Max and the Cloudmos team for their proactive updates, which are regularly shared on the [public-facing and open-source project board](https://github.com/orgs/akash-network/projects/5). +### Discussion on Cloudmos API: +- Tyler inquired about Praetor team's experience with Cloudmos API, seeking confirmation that they obtained everything they needed. +- Jigar Patel from the Praetor team confirmed that they received all the required support from Cloudmos, enabling them to successfully launch the lease transport quickly. +- Expressed gratitude to Max and the Cloudmos team for their assistance. +- Rodrigo Rochin sought clarification from Max regarding the upcoming API key feature, inquiring about potential limits and whether it would be free for users. +- Max and Greg Osuri clarified that while there might be some rate limiting, the use of the API will be free for all users. +- Additionally, the possibility of running one's own API server using the open-source suite was mentioned. +- Max acknowledged the need for improved documentation, especially for users interested in running the services themselves. +- He expressed a willingness to contribute more effort to documentation based on community needs. +### Update from Joao Luna on Client Libraries and Quasarch Platform: +- Luna shared that the client libraries are close to launching and will be open-sourced soon. +- Mentioned that certain logic within the libraries was initially coupled to their platform but is now being made open-source ready. +- The client libraries will be a part of their platform, which is closed source, but Luna expressed the intention to open-source the client libraries for community use. +- Luna highlighted that the client libraries have undergone intense testing and form a core component of their platform. +The libraries, responsible for various functionalities, have shown stability, with a focus on logging-related testing remaining. +#### Quasarch Platform Overview: +- Luna provided a brief overview of the Quasarch platform, targeting web2 developers familiar with services like Google Cloud Platform and AWS. +- Described the platform as a decentralized cloud platform, with the first protocol integration into Akash. +- Luna mentioned the potential for expanding services beyond compute to include storage, identity, and more. +#### Self-Custodial Experience and Crypto Abstraction: +- Responding to Greg Osuri's question, Luna clarified that the user experience is self-custodial, and the platform handles all crypto-related complexities in the backend. +- Emphasized the goal of abstracting crypto complexities for users, providing the benefits of decentralization without burdening users with crypto intricacies. +- Greg Osuri expressed fascination with the platform and suggested the possibility of a more private session to delve deeper into its details. +- Luna acknowledged that while the discussion around funding and open-sourcing had been ongoing, it wasn't a top priority. +- However, they now plan to open-source the client libraries to give back to the community. +- Greg advised Luna on the importance of open-sourcing the libraries to receive valuable feedback before seeking funding. +- Greg emphasized the challenge of assessing the library's quality without the ability to use it and suggested building credibility through open sourcing. +- Luna inquired about a repo called "node API" in the Akash Network organization and asked if it might be a tentative client library. +- Greg was not familiar with the repo but suggested following up offline or potentially involving Artur for more insights. + +### Discussion on AKT Requirement for Deployments +- Tyler welcomed Prashant from the Spheron team and highlighted the issue they encountered regarding the AKT required for each deployment. +- Prashant provided a high-level overview of the issue faced by Spheron as they scaled their activities on the network. +- Noted that with around 550 active providers, they faced challenges related to liquidity and locking up funds for creating leases. +- Shared that Spheron is working on launching providers with zero AKT as a solution to mitigate the problem. +- Plans to announce and test this approach, considering its potential effectiveness for addressing the liquidity and scalability issues. +#### Greg Osuri's Response and Offer of Support +- Greg acknowledged the challenges faced by Spheron and suggested a stopgap solution, offering to provide some AKT as a loan from the core team. +- Raised the idea of reconsidering the five AKT parameter, suggesting a potential reduction during a network upgrade. +- Prashant acknowledged the offer of support from the core team and reiterated the challenge faced by projects in terms of liquidity. +- Discussed the impact on projects as they drive adoption, emphasizing the need for a solution to avoid potential problems for projects. + +#### Artur Troian's Clarification: +- Artur differentiated between two types of deposits: deployment deposit and big deposit, confirming the focus on the deployment deposit. +- Explained that the value of the deployment deposit is under review internally to determine the optimal parameter. +- Greg proposed initiating a governance proposal to change the deployment deposit parameter to one AKT, considering the current value of AKT. +- Prashant questioned the necessity of the deposit, prompting Artur to suggest moving the discussion to GitHub for further elaboration. +- Tyler directed Prashant to create a GitHub discussion specifying the deployment deposit issue for community involvement. +- Encouraged prompt action from Prashant to initiate the discussion on GitHub +- Prashant committed to initiating the GitHub discussion promptly and informed the community within the week. + +### Additional Discussion on Deployment Deposit: +- Greg Osuri recalled that the deposit was initially required because the escrow needed some AKT to get started, preventing misuse. +- Artur clarified two reasons for the deposit: + - Preventing providers from creating deployments without a deposit, exhausting resources quickly. + - Ensuring providers remain active; without a deposit, providers might become inactive. +- Max suggested using USDT for the deposit, and Artur acknowledged the potential, but mentioned concerns about the availability of providers accepting USDT +- Prashant explained that Spheron had its own providers to address bidding cost concerns and liquidity challenges associated with using USDT. +- Prashant proposed reducing the deposit to zero, arguing that maintaining liquidity and capital for USDT could be burdensome for clients. +- Artur clarified that setting the deposit to zero would break the deployment and bid processes, +- Emphasizing the necessity of a deposit for the SQL account to work. +- Artur suggested lowering the deposit rather than setting it to zero, acknowledging the need for a deposit but discussing the value. +### Artur's Presentation on Akash API +- Artur is working on the Akash API and shared insights on solving issues related to changing API versions. +- The challenge discussed was the lack of visibility on the client side regarding the supported Akash API version on the RPC node. +- Artur proposed extending the RPC endpoint to serve version information. This feature will be available in the upcoming partial version. +- There will be proper examples and guidelines for implementing this feature in different languages. +- The clients' discovery checks the supported Akash API version and generates clients accordingly. +- Documentation for providers, including information on types and API requests, is being generated for better human readability. +- Feature Discovery will be available for both provider and node sides. +- Tyler encouraged Artur to initiate GitHub discussions and share information with the community. + +### Additional Points from Artur on Akash API +- The primary goal of the Akash API is to simplify documentation and enhance external user access to products. +- Aim to separate it completely from the Converse, considering them as distinct entities with different purposes. +- Using protobuf for types description from providers like jpcloud to streamline generation. +- Instead of generating protobuf every time, supply already generated protobuf things, ensuring compatibility. +- Focus on making it easy for developers to start interacting with the blockchain. +- The Akash API is still in progress, with upcoming additions to the [repository]( https://github.com/akash-network/akash-api). +- Plans to release it as a mainstream version in the next few months for broader implementation and understanding. +### Discussion on Moderation API and CRDs +- Deval Patel raises a question about whether the Moderation API, which is being developed to expose the CRD (Custom Resource Definition) for white listing and block listing, should be exposed through the Akash API or the Provider Service API. +- Artur suggests keeping it in the provider repository for now. +- Artur clarifies that the CRD itself is not an API but rather a behavioral description of how certain things operate within Kubernetes. +- It is decided to keep the CRD inside the provider repository for the time being. +- Artur informs Deval that the PR review for this matter will be held until some releases related to feature discovery and deploy operator are completed, as these changes affect the deployment process. +- Deval explains that the reason for exposing the API through Provider Services is to provide a UI where users can view the list of filters and update them. +### Closing remarks +- Tyler highlights Luna's upcoming discussion on the Provider schema for next week's meeting. +- Tyler encourages participants to engage in GitHub discussions related to Provider schema and upgrades. +- Prashant's question on provider upgrades to be addressed as a topic in the next meeting. +- Alani Kuye expresses interest in Luna's discussion on the provider schema for its relevance to provider reviews. +### Action Items +- Tyler will ensure that information regarding the upcoming API improvements and documentation release is communicated to the broader community. +- Tyler will ensure the sharing of Spheron's network statistics in the SIG Clients channel for community awareness. +- Tyler will follow up offline, potentially involving Artur, to provide insights into the "node API" repo. +- The core team will work with Spheron to provide some AKT as a loan to address the immediate liquidity challenge. +- The possibility of reconsidering the five AKT parameter will be explored, with potential discussions on adjustments during a network upgrade. +- Prashant will create a GitHub discussion to address the deployment deposit value issue +- Continue development on Akash API; release mainstream version in the next few months. +- Joao Luna to provide Alani Kuye with details on the provider schema offline From bcd8d6d5732a4a76ac84d97cfe524cc0ff954ac5 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Sun, 28 Jan 2024 09:11:02 -0500 Subject: [PATCH 002/138] sig-client Update 012-2024-01-17.md add recording and transcript to notes Signed-off-by: Drinkwater --- sig-clients/meetings/012-2024-01-17.md | 348 ++++++++++++++++++++++++- 1 file changed, 347 insertions(+), 1 deletion(-) diff --git a/sig-clients/meetings/012-2024-01-17.md b/sig-clients/meetings/012-2024-01-17.md index 120aa359..1dfbfb1b 100644 --- a/sig-clients/meetings/012-2024-01-17.md +++ b/sig-clients/meetings/012-2024-01-17.md @@ -9,7 +9,7 @@ - Date: Wednesday, January 17th, 2024 - Time: 08:30 AM PT (Pacific Time) -- [Recording]() +- [Recording](https://75iuscsrjioekyahvk6vad3taa5ikpweibvxs2rf4amjvzvj6gfa.arweave.net/_1FJClFKHEVgB6q9UA9zADqFPsRAa3lqJeAYmuap8Yo) - [Transcript](#transcript) ## Participants @@ -146,6 +146,7 @@ The libraries, responsible for various functionalities, have shown stability, wi - Tyler encourages participants to engage in GitHub discussions related to Provider schema and upgrades. - Prashant's question on provider upgrades to be addressed as a topic in the next meeting. - Alani Kuye expresses interest in Luna's discussion on the provider schema for its relevance to provider reviews. + ### Action Items - Tyler will ensure that information regarding the upcoming API improvements and documentation release is communicated to the broader community. - Tyler will ensure the sharing of Spheron's network statistics in the SIG Clients channel for community awareness. @@ -155,3 +156,348 @@ The libraries, responsible for various functionalities, have shown stability, wi - Prashant will create a GitHub discussion to address the deployment deposit value issue - Continue development on Akash API; release mainstream version in the next few months. - Joao Luna to provide Alani Kuye with details on the provider schema offline + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the first state clients monthly meeting of 2024. + +Tyler Wright: During these clients special interest groups. The group comes together to discuss anything related to deployment tools or anything else clients related on a cost. again out of the last meeting of number of teams gave updates on their progress for 2023 including the sphere on team the cloud a couple of other teams are working on various clients. Also participated again, really the goal is for everybody that's building on top of Akash to be aligned on various schools that they can all leverage ways of solving problems and Beyond one thing that will change moving forward is I will move this meeting up a few hours. I know that there's a couple of teams that are base in Gulf Coast time and so it's just far too late for them to join. + +Tyler Wright: got off the phone with The sphere on team who again, we're trying to stay up to join today's call. and not so again, we're going to move this call up a few hours. So it's earlier in the day for folks that want to participate on that side of the world. Again out of the last meeting there was a cloud most gave a great update and I know there's been significant work that they continue to do much of the efforts of the cloud most team is doing that open source efforts are available on the project board, which I'll attach in the chat right here. I know that they have been working on various items related to the cloud most API, which is now open source and is being used by teams like pretor and others. And so again we might talk about that a little bit today. I do also have some time on the agenda for + +Tyler Wright: Artur who was on the call to talk a little bit more about Akash API, which is a resource that again is available to clients and everybody in the community to be to use and Joseph who is usually on this call has been Hands-On and active in supporting a cost JS which is another tool available to clients and I know something used by Cloud most and others and again just want to make sure that folks that are looking to leverage these tools have access to the those that are core contributors and Developers. + +Tyler Wright: if anybody else has anything that they want to add as an agenda item for today again in future meetings, we'll have more participation from other teams, like spheron and others look out for fearon is talked about putting up some Statistics over the last 17 days of January of some of the work that they've been doing and some of the active leases as again Spherion continues to grow. So again, I'll make sure that those numbers that they want to share with the community are available on how people are using spheron built on top of Akash. + +Tyler Wright: And then again, I know there was some conversation from node Ops that needed some support from cloud cloud most so they thought I believe that the support they need is really related to deployment not necessarily related to indexing. So again, I was hoping that they'd be able to join this call, but I know it's late for them. Cool. I just want to get everybody caught up with that being said I know that the Max's and the cosmos team are working on a number of items related to indexer as well as personal kid max speed. Do you want to give an update on some of the things that are working on and share some wins and update with the community? + +Max: Yeah, Hey, everyone. So in the past few weeks or in 2024. We are currently working still on rebranding for those into the cash console. So we're done with + +Max: rebanning the analytics side of it. It should be announced. soon there are the launch of the new analytics app. So there will be any more analytics in combos. We're also working on making our API more accessible in documented. It's also something that we will soon release. So it'll be easier for other teams that need more specific data. For your application like Prater or other? people that I know from the community that the user API currently but it's not documenting or anything so Yeah in the future. I'll have a Swagger documentation and it'll be much more structured with versioning and + +00:05:00 + +Max: Eventually API key access or not depending on the needs. So that for the API and we're fixing. bugs and issues even there for the customer skit because we transition to customer skit later late in 2023 + +Max: That's been great. There's a few issues that we're working on. But overall it added the support for a bunch of other. Wallets that we didn't support earlier leap customer station. Kepler mobile so you can actually create deployments using your mobile device today with or monitor for current deployments with your phone, but very you use it for and so yeah. what we continue working on the + +Max: the API and rebranding these to a cash console and then after that, we have a bunch of projects just in general intense the user experience for your users or even existing users on a cash to make it more mainstream. + +Max: It's basically it. + +Tyler Wright: Thank you Max. again on a weekly basis the cloud most team updates all the work that they're doing on various projects that are public basing and open source in that project's board. So if anybody has any questions for them, they could feel free to reach out on those specific projects there. The Max's also do a great job of staying active and Discord on the ecosystem Cloud most channel. So if anybody has any specific questions on the Max's or various insiders are there to help and then again anybody has any specific issues the cloud most repo inside the Akash organization is where you throw those issues and the Maxi do a great job of managing those issues and solving those issues in a timely fashion. + +Tyler Wright: Does anyone have any questions on anything Cloud most related? + +Tyler Wright: Pray to our team. I know that you all had previously been leveraging Cloud most for some API stuff. Did you get everything you needed for the time being and they're all set. And then from there also go to Raji has a + +Jigar Patel: Yes, we already get everything what we wanted and because of that we launched the lease transport. That was very quick. Thank you so much Max and the team + +Tyler Wright: excellent Awesome Rodger. I see your hands up. Go ahead. + +Rodrigo Rochin: pay off so this is for Max and what you said about the API keys that will be coming soon any ideas if there's gonna be limits or something or free for some of us or something that + +Max: yeah, pretty sure it's going putting the chat that's gonna be free for all I think I'm not The entirely sure it's just the ideas they need to avoid abusing the API from random developers. So yeah, it's just a matter of controlling the access but The generality is to make it accessible to everyone for free, I think. to be determined + +Rodrigo Rochin: Hey cool. + +Greg Osuri: Jim, there will be some degree of rate limiting, but there's no charge for using API and I don't know what we feel about even in the past Suite is open source, right so you can run your own API if you want. + +Rodrigo Rochin: Actually tried but it didn't continue because I figured it out quote for my needs. But yeah. cool + +00:10:00 + +Greg Osuri: Why weren't able to run the API server? + +Rodrigo Rochin: I tried to download the database or I wasn't sure how I was going. But I wasn't able to for some reason and then said it worked… + +Greg Osuri: . + +Rodrigo Rochin: what I was working on. So I just didn't try to + +Greg Osuri: If you tell the specific error or specific reason you're unable to run API server, we should address that but I was able to run a fairly easily. + +Rodrigo Rochin: I'll give it another train if it's a mirror, which I guess is not maybe I don't know I didn't have enough resources or I don't know why but if I find something I'll share it in this quarter. + +Max: Yeah there we know… + +Tyler Wright: Perfect. + +Max: if you need help and because there's the API and the indexer they're both Application that you can run but for Our documentation to run the services yourself and definitely be improved. We haven't put that much effort into it. But yes, that's something that the community Wants to have we can put effort into it. + +Tyler Wright: Any other questions for the cloud most team before we move on? + +Tyler Wright: cool I see Luna has joined the call. I know that Luna in 2023 and even prior to that in late 2022 was working on some clients Library stuff as well as again can be found on the ecosystem for Terra phone provider in Discord manages that Luna. Is there anything specific that you want to update the team on? And I know that again you also have some quasarch efforts that you are leading as well. But is there anything I don't mean to put you on the spot but anything specific that you want to update the group on today? + +Joao Luna: Yeah, we are actually close to launching and will be open sourcing the client libraries as well. We haven't done it yet. Just because there were some couple logic over there. That was coupled to our platform. We are kind of making it to open source ready. And that's a component that will be open sourced as part of the launch or should be open source as part of the launch of our platform which our clients will be closed Source. it's a whole platform that we are building but as for the clients libraries, they will be open source and for the community to build upon and perhaps even donated to the Akash Network organization later on. + +Joao Luna: I'd say we are pretty satisfied with… + +Tyler Wright: that the great you + +Joao Luna: how It's being a very intensely tested as it's really the core of our platform is that clients Library specifically it's what allows us to do all the punch all the stuff. We just have some further testing to do in regards to the logging part of the clients library in terms of accessing logs and things like that, but overall, it's pretty stable and should be ready to be open sourced together With the platform Max are you asking for them of the platform or the clients livers? I think I did the clients libraries demo. + +Joao Luna: On the platform not yet, but I can send you some screenshots if you are interested and some videos as for the clients libraries. I think I did a demo as a steering committee meeting in 2023. There was a demo perhaps if you are interested, you can also check the recording. But me on this cards… + +Tyler Wright: + +Joao Luna: I can share more details on the platform as well. I think it's not the Focus right now. It's the client libraries, but if anyone is interested, just yummy. + +Tyler Wright: excellent Anyone have any questions on clients libraries again? I know that will be made available publicly soon. Luna in terms of quasarch platform, is that something that you feel comfortable giving a high level maybe 30 seconds to two minutes overview of what you all have been building. I know that you've been + +Joao Luna: Yeah, what puts simply is. It's kind of our main target our web to developers that I used to use in Google Cloud platform AWS and are familiar with those kinds of services and provide a way for them to use them. But in this centralized infrastructure our first protocol integration into the cache, of course, I think it makes sense. But we'll later on be interesting other services be storage identity. + +00:15:00 + +Joao Luna: Whatever or even other services built on compute. So I think akashes a very broad potential and even I mean we could brainstorm a little imagine once we support VMS we could provide something like decentralized ec2, which perhaps is a little bit more reliable than just serverless containers as we currently use them. So yeah, there's lots of potential but it's basically just a decentralized cloud platform, but targeting the web to developers but two people + +Greg Osuri: It is the experience self-custodial or is it posted? + +Joao Luna: and all the crypto is self-custodial. So we handle everything we don't want the user to worry about crypto. they wouldn't even know or need to know that there's crypto involved in the backend. Obviously, we are transparent on that, but it's none of their concerns. we try to just provide the benefits of decentralization and self-serverity. but keep the crypto complexity kind of out of it or abstracted for them. + +Greg Osuri: How does that work either wallet in front for Authentication? + +Joao Luna: that there's a lot of stuff going on, but I can go into more detail that a specific. + +Joao Luna: Meeting or session I'm free to share what we have built. It's just that maybe as of time and Technical complexity. We will be spending a lot of time you're talking because it's interesting stuff. I find it interesting and I love to talk about this stuff, but + +Greg Osuri: Yeah, I'm fascinated. I mean anything that's going to reduce the complexity for a user to use. + +Joao Luna: we are really trying to. + +Greg Osuri: Sir, if you want to do a more private session happy to it's really good one, but I'm very serious. + +Joao Luna: But yeah, just as also just went to that. I know the libraries have been ongoing for quite a while. We haven't really put much effort in open sourcing it yet. I know I opened the discussion for funding but as it wasn't like a priority and I understand it I mean + +Joao Luna: Perhaps other people could have built it but yeah, we'll be open sourcing it because it makes sense. It's just that it took so long because it was not a priority for us because we are just going through building these and trying to get to Market as soon as possible and from Australia perspective. It makes sense because it's kind of strategic asset for us and we can use it to build and deliver something and then we really want to give back to the community. So that's why we will open source the clients and allow people to build a similar stuff or leverage what the clients however they want, but it kind of offered a slight Advantage. Let's say + +Greg Osuri: Yeah, so when it comes to funding I highly suggest you open source a libraries and let us give you feedback from using libraries very hard to determine the quality of the Library without even being able to use… + +Joao Luna: Yeah, I understand. + +Greg Osuri: and the space. + +Joao Luna: That's the feedback I got that idea as So no more is there and… + +Greg Osuri: So I think it's most likely to get funding you got to give something right? + +Joao Luna: I understand. + +Greg Osuri: You got to show something you like build credibility and… + +Joao Luna: Yeah, yeah, it makes sense. + +Greg Osuri: then you can make a case saying that look we spent I don't know 200 hours billions API. We're going to be giving it for a community and we like some degree of conversation,… + +Joao Luna: Yeah, I might have been in a little bit of let's say maybe on my high horse. + +Greg Osuri: and + +Joao Luna: Let's say as I was like, I built the telephone provider. I think I have some credibility. maybe I can ask before actually open sourcing. But yeah, I know but I understand the concerns and we still developed it. The mission is also to open source there's no change there. + +Tyler Wright: Thank you Luna for the update. I think we'll follow up on a number of items offline but much appreciate the update. Anyone have any questions for Luna at this time about anything clients libraries related or the kuye Stars platform coming soon? + +Tyler Wright: Go ahead Luna. + +Joao Luna: Yeah, I also saw there was a repo. I think it was called the node API. Is that a tentative client Library something that we perhaps can merge later on just some insights there or is not related. + +00:20:00 + +Joao Luna: I think it was the repo on the cache Network organization called node API, I think. + +Greg Osuri: I'm not familiar. I'm not in front of the computer to give you better, but I'm not sure. + +Tyler Wright: That might be a question that Artur might be able to answer but we might be able to take that offline with artur's not near microphone right now. I'll follow up there. + +Tyler Wright: cool All right moving along again. As I mentioned at the top of the call, the future calls will be at an earlier time. so that some teams like spheron node Ops and some of the other teams can join us. I know that they try to join us but it's just far too late for them. So again, we'll take that into consideration moving forward. One thing else. I mentioned at the top of the call is fearon is going to provide some numbers on what the sphere on network has been doing. Of course the start of the year in terms of deployments leases Etc with a Kosh Network as their base layer. + +Tyler Wright: So again, I'll make sure that that gets shared and sick clients. So because they want to make that data available to everybody. So everyone can kind of see what's going on in terms of engagement on sphere on currently. + +Tyler Wright: Right, are there any other teams here that want to talk about their specific clients that haven't had the opportunity to yet? + +Tyler Wright: cool + +Tyler Wright: All right, moving along as a part of the open framework and the open structure around a cost. One of the things that were the core team was trying to do a better job of in 2024 is make sure that members of the core team are available. I know that there's six support meeting that happens by weekly where folks can dive into the support repo issues that are waiting triage folks can ask any questions about any specific issues that they need some more guidance on or if they want to help participate in solving issues they can do so, I know Scott Artur and others join that call regularly, but Archer was kind enough to make himself available today to talk a little bit about the Akash API, which is something that again the goal is for more clients to leverage this tool Archer before you jump in there. I do see + +Tyler Wright: that Prashant has joined again. He's a leader over at the sphere on team. I gave a high level update on, some of the stuff Prashant you're going to do in terms of providing some data, but I know that you were talking about a specific issue related to why they KT needed for each deployment. Is that something that you want to talk about at a high level right now, or is that something that you want to kick off in a GitHub discussion? + +Prashant Maurya: I can speak about it on the high level as of now. So if you guys thank you Tyler again for bringing me on I kind of rushed where my house to kind of make sure that I got in this call. So if you guys might notice there are a lot of activities which is happening on the network. And in the past 15 years, we have around today we have seen around 400 closer and 400 actively just found on this front providers. and this is where we kind of found that issue when we started scaling that 550 issue while creating a lease. Is pain like we literally have to go and buy a lot of these who can to ensure is we are able to create those activities. Now whenever we do that our liquidity is locked in. + +Prashant Maurya: And that creates another problem for the projects. We don't have a lot of liquidity in house and we don't Millions of dollars in the pocket to kind of to keep on doing this and we realize now while we were knowing that this issue will come but we were not doing is as we scale that scalability will get hit because of this issue. So before even this call, I think I had to call I had the quality Tyler and I was mentioning the same. and this is causing us a lot of problem. We are trying to solve it we are. Going to be launching some of the providers which are going to be having a zero a kitty bit. We are making some changes around that. And we'll also announce that we'll see if it works out for us. Then we'll also roll it out for everyone to kind of like who's already looking forward to leverage from that. I think they can go ahead and do that. + +00:25:00 + +Prashant Maurya: but yeah, that is what the update is. As of now. I think a lot of people who will start scaling on they are definitely going to face this issue. + +Greg Osuri: It's a good point, I think. As a stopgap we can happy to give Some akt as a loan or something that we can figure out as a immediate solution so that you can continue scaling. From the core team, but I think it's time to reconsider the five. Akt, I believe it's a parameter that can be changed easily during Network upgrade. If not, it will require Network a great bit. I think reducing that to. + +Greg Osuri: When it was designed that I mean this was introduced in. 2020 And we didn't have any insight into how big it could get but why we could eat ourselves a lot of money now, right? So + +Prashant Maurya: Yeah, that is weird. That is where the problem is providers Mighty making lot of money, but the projects were driving that option will leave the money and that creates a problem. And as you mentioned we are as ready to learn the thing we need to see how exactly but we are already working on few things but in the shorter period of time because we are going to see A good amount of new deployments going to become kicking in. So we all have to be waiting for it. You can use this. Yes, Yeah, but… + +Artur Troian: I'm just real quick. + +Prashant Maurya: how much is that is going to be that uses? + +Artur Troian: I was talking there are two types of deposits. There is a deployment deposit and there is a big deposit. Which one are we chatting about beat or deployment? + +Prashant Maurya: deployment + +Artur Troian: Deployment Yeah, so we've been playing with the value a few clients need it was actually so we change the steel sort of trying to understand there has to be some value from + +Artur Troian: as a deposit for a number of reasons, But we still trying to figure out the best. way for that of this parameter is the network parameter, and it has to be changed through governance proposal So we reviewing that all internally and hopefully, maybe next week or so even a conversation on that. But yeah, I think most likely is going to be the governance proposal to over the police. + +Greg Osuri: So why don't we put a proposal to? + +Prashant Maurya: Yeah, I think I think. + +Greg Osuri: to make it one akt + +Artur Troian: so we said it initially to five… + +Greg Osuri: that's + +Prashant Maurya: So my question here is before. + +Artur Troian: because the problem because + +Prashant Maurya: Before you guys even move forward in this direction. I have one question to put forward. So I was very curious is why do we even need the deposit? + +Artur Troian: So let's probably help move this discussion over to GitHub because I didn't saying this is the clients talk… + +Prashant Maurya: Okay, okay. + +Artur Troian: but there's a specific reason for that. So we've already to five when the ADT was what 20 25 cents novices like three dollars. It creates painting about so you can review it. + +Tyler Wright: So Prashant, I think and I appreciate you joining. I know it's late. If you could create a GitHub discussion for this kind of setting your problem and be specific around that's being deployment. Then folks like Greg Archer and others from the community can get involved in that discussion and we can just figure out what the next steps are in terms of. If we need to adjust the deployment initial akt amounts. And then how we go about doing that? Prashant if you could throw that on chain, either before you head to bed tonight or early tomorrow, that would be great and then we can just have a discussion over the next couple of days around that subject. + +Prashant Maurya: Yeah, so we are just so sorry for this. I'll ask him to kind of open that on the tech game side. We're gonna take it forward and open that decision. I inform them as soon as possible within this week. + +Tyler Wright: excellent much appreciated + +Tyler Wright: cool, but + +Greg Osuri: I think if I remember correctly the deposit was required because the escrow needs Summit 80 to get started or some crazy reason like that if I remember correctly. Yeah. + +00:30:00 + +Artur Troian: Yeah, yeah. So the two reasons for that the first of all you can create without deposit. Talent can create deployments run for a few blocks and then it's just gonna be exhausted pretty quickly. + +Greg Osuri: Right, right. + +Greg Osuri: I remember. + +Artur Troian: So there has to be so… + +Artur Troian: what happens is if there is no deposit. The provider is Rock command review gonna be close to me. So there has to be some kind of deposit. So I think yeah Max's point is right. You could guys use usdt for that. The only question is how many providers are. offering usdt + +Artur Troian: During the beat process. + +Greg Osuri: Sounds good. + +Artur Troian: But yeah, we're going to change it. + +Greg Osuri: Thank you. + +Tyler Wright: excellent So again members this fear on team will add that discussion and we'll follow up there on GitHub with next steps. + +Tyler Wright: Max just asked spear on you have your own providers is that is correct, but Prashant do you want to Yep, perfect. + +Prashant Maurya: Yeah, so the reason we wanted to have our own provider again is because of the same reason because a lot of things which we have kind of made those changes into our side is the first is like that becoming a provider again the bidding cost which was Associated again, that was also the pain for us. So we kind of solved it for ourselves. If somebody is kind of looking forward to that have that solution. You can definitely kind of get it done but we don't know how cool that code is I respond of time so we never raise that you are around it, but we can always open a branch where we can submit that so that if somebody's looking forward to that code + +Prashant Maurya: But yeah, that is one of the reasons why we had that and we'll keep on running these providers. You could enable Yes, again, the problem with the usdc is again, so we are running back to the same question is maintaining the liquidity part. even if we go with one one uses right now, imagine if you have to just scale every time whenever you scare, you have to go and keep buying us this on Market keep exploring into your side. what happens if you go and buy too much of how use DC and it doesn't even steal. So there are lot of different birds on the clients side. It basically means we have to come up with a lot of capital first in order to kind of get started. So that is the reason I'm kind of will write down that proposal. we'll write it down. I think that deposit should not be needed. It should just go to zero. And there should be some way around using which we should be able to. find I + +Artur Troian: The Prashant just s. Yeah, I'll jump in real quick on that. You cannot do that to zero as Greg mentioned earlier. This is requirement for SQL account to work and simply removing the setting deposit to zero. We'll just break entire beat processes and entire deployment process. So we kind of do that. The only thing that is doable at this stage is lowering the positive so there still have to be depositive right? It's just the question of what Spies of this deposit is. + +Tyler Wright: I just want to be mindful of time. I know that we'll take this discussion offline. I see a number of folks that are getting involved in chat and I appreciate that again after the sphere on team adds this to discussions. I will share this in sick clients and elsewhere and we can have a wider discussion as a community about this. + +Tyler Wright: cool I did see a question from Luna that's not related to this issue. But it's more related to running a Luna asks having your own providers has that allowed you to have private registries? + +Prashant Maurya: So yes, it does. + +Tyler Wright: Okay, Any other questions for Prashant again, I know it's late. And again, we'll be adjusting the time moving forward so much appreciated Prashant representing Spherion and joining us today. + +Tyler Wright: Cool moving along again. We have about 23 minutes left allotted, but I do want to give some time to Archer who I know has been working on Akash API, which is again available to the community. So I'm going to hand it over to Archer to Talk a little bit about cost API how he thinks it should be used Etc. So Archer take it away. + +Artur Troian: thanks our all Yeah, I'll try to be real quick on that. I'll just quickly share screen. + +00:35:00 + +Artur Troian: So I'm trying to find the tab the issue you're trying to sort of solve here is we are changing API from time and for example adding new features to the deployment process big process at a new modules and so forth that requires us to change the API versioning which every time and that causes problems. from the clients side as there is pretty much no way to + +Artur Troian: understand what kind of version of the API is being supported right now on the RPC node. So we try to sort of hack it initially which was probably not good idea and just before the end of 2018. + +Artur Troian: As I would say, maybe the most easiest and other solutions to that problem. We can extend. + +Artur Troian: RPC endpoint to serve the Russian and it looks pretty easy right now. This feature will be available to the current mind in the partial version. So people are similar idea. Is that the extra? + +Artur Troian: endpoints in the RPC Handler that just reports currently supported the crush API version and then there's a clients discovery that checks that and generates and actually it's a case correct clients for the CPI version right now. It is available in golland. And both provider and not repositories are using this. feature as of right now, we will be having proper examples and guidelines on how to implement this thing for other languages including not just I think so in the idea is that + +Artur Troian: it's just pretty much the product message over here just to show off. what the extent in their Pacino, but if you go to actual discovery oops online So what it does is pretty much just hits the API where RBC important on the Note side and checks if the version is okay, if it supported you just pretty much okay, it's the new. Clients and you don't have to worry about if types are correct. It's a new version and it's also for especially kids with the deployment as the updated quite often in the Portland groups. We have that resources new features like gpus. and we've been having this issue happening quite a few times. + +Artur Troian: After upgrade, so we also generate right now documentation for profs and it can be found over here. Right now it is sort of just generated. Whatever. + +Artur Troian: Provided by grpc. Sorry protocol compiler We will be updating that slightly more human readable information. So this provides just shows up what kind of types and API requests can be handled by RPC at this stage. but then we will be providing examples on how to create clients and how to + +Artur Troian: Use future discovery on the Note side the feature Discovery will be available for provided side as well as we have quite substantial API that is been migrated entirely to what about right now? As soon as we clean is that you should discover on the provider side. + +Artur Troian: I think is it yeah, but + +Tyler Wright: Thank you again, just as Artur and other members of the core team are working on a number of new items in the code base. I want to make sure and they do a great type of volunteering themselves, but make sure that they share These thoughts with the community so they can ask questions anybody that joins these calls especially Sid clients with so many people that are technically working on number of things. And then again we have record for the rest of time from these conversations so our church. Thank you for sharing. Does anyone have any questions on Akashi API related stuff that they want some more detail from Archer over the core team one. + +00:40:00 + +Rodrigo Rochin: That might just share something about my issue. + +Tyler Wright: No, appreciate it. real quick. Did anyone have any questions on a cash API? Again, that's open source. It's available inside the cost Network organization. I've shared it in. + +Artur Troian: It just real quick on the graphic. I think so the sole purpose of that was to simplify + +Artur Troian: documentation as well as access to products for external users and you wanted to just untie it completely from the entire Converse because those things are completely different from this Cycles. Does number one number two was? + +Artur Troian: Just because we use the product for the valve for jpcloud for types description. We found that. Generating from above every time is quite painful second of all environments can be completely different than just troubles. So what we do instead just pretty much supply all generated product above things as for example cubing the last so for user that let's say luna for you guys, whenever you want to do some extent that a clients implementation. So instead of generating product itself to access a cardboard chain, you just use whatever is already and make sure that doesn't create any problems. and the third thing with the Akash API is + +Artur Troian: to make sure that it is really easy entry for the developer. to start interacting with the blockchain so that was the Three main points for Akash API. It's still underway. We are going to have a few more things push to that repo and hopefully in the next few months, we will release it as a mainstream version. So everybody could I have a good implementation and understanding how this thing works. + +Tyler Wright: convertible + +Deval Patel: So under the question here is that regarding the moderation API. that we are trying to expose the crd what we are building through for the white listing and block listing. The address is a hostname and I are images we have created the API in the provider service right now. Do you think so we should expose it through the Akashi PA as well or the provider service API is okay for now? your thoughts on + +Artur Troian: Yes, I slowly provide guys. Thank you. So. I'm still unsure where we want to keep shared use of it because the crds are provided specific and more over there kubernetes specific. I think you're gonna keep them in provider repo for So first of all that this year and the crd right now is leaving inside the provider Repository. and I don't know so the crd is not actually API per se Wright. So the crd is some behavioral description of how some turning things work or operate within the kubernetes, right? It doesn't mean that it exposes API. + +Artur Troian: So for now, yeah, we're gonna keep it inside the provider I think. Shortly, we will be holding this PR. Review until we do some releases related to Future Discovery and deploy operator. Those things are actually changed the big process a little bit. So you will have to revise it when we are ready to review this pure and merge it. I'll give you a follow-up in the pr when you have to do that. + +00:45:00 + +Tyler Wright: Don't go ahead. + +Deval Patel: Yeah understand and the only thing I mean, we expose the API through Provider Services because we want to give the UI all where people can actually look at the list of filters they have right and they can update it. But update will not happen directly through API for now, right so up to be directly through CID, but at least they can read the CID from APA pers. + +Tyler Wright: Thank I think that's a great segue. I know we're coming up on time. Just a reminder next week. There is a number of special interest groups and working groups happening including docs on Tuesday Sig support and sick providers on Wednesday as well as steering committee and some others on Thursday. just want to quickly shout out again. Our chair has reviewed some of the work or not some but the work that the prayer team is done around content moderation. There will be some follow-up happening there. So thank you Archer. And thank you pray to our team for getting that ready. + +Tyler Wright: I know that leading up until next meeting as a part of the state providers agenda. I'm sure we'll talk a little bit more around the discussion that I believe Luna put forth in terms of Provider schema. So again, please we'll save any conversation for that for next week. But go into discussions on GitHub and feel free to chime in there and then we'll follow up next week. And then I just saw prashant's question around provider upgrades and so we can talk about that as a topic next week as well. Is there anything else? Related that anybody wants to discuss today that hasn't been discussed. + +Tyler Wright: Go ahead. + +Alani Kuye: Hey guys. Thanks for the updates. This is very very helpful. Luna if you get a chance offline within Circle, I'll be very interested in that provider schema. Because we've been circling around provider reviews and things along those lines. So I would like to see what you have cooking there and what relationships might exist. + +Joao Luna: Yeah, definitely. I'll DM you. + +Alani Kuye: Awesome. Thank you. + +Alani Kuye: I yield sorry. + +Tyler Wright: Alani always good to hear from you Archer. Thank you very much for walking us through I've dropped the discussion around a provider attributes in the chat for folks much appreciate again Prashant staying up late and joining and talking about some of the things that they're working on. We'll look out for a discussion around the deployment amount as well as we'll follow up all offline about how we can support you all in the meantime Prashant and then I know the troll I talked about providing some data and just like showcasing some of the successes you've had at the start of 2024 with activity on network again built on top of the class. + +Tyler Wright: But again much appreciate everyone's time today. Feel free to reach out to me if you need anything, but I'll be updating the notes making the video available shortly and then we'll continue these conversations online after we move into the rest of this week and next week. Hope everyone has a great rest of their day. Thanks again for participating talk offline. + +Rodrigo Rochin: you guys and they + +Joao Luna: Thank you guys. + +Jigar Patel: picture + +Meeting ended after 00:49:26 👋 + From d535b05c046f349c9c2694d7c30dcd1ad395c96d Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Sun, 11 Feb 2024 12:36:11 +0000 Subject: [PATCH 003/138] Update Readme tables (#477) Update Readme tables --- sig-chain/README.md | 2 +- sig-clients/README.md | 6 +++--- sig-design/README.md | 2 +- sig-support/README.md | 4 ++-- wg-akash-website/README.md | 4 +++- wg-zealy/README.md | 16 +++++++++------- 6 files changed, 19 insertions(+), 15 deletions(-) diff --git a/sig-chain/README.md b/sig-chain/README.md index d8d9ea5f..7dd821a2 100644 --- a/sig-chain/README.md +++ b/sig-chain/README.md @@ -24,7 +24,7 @@ date: 2023-1-09T00:19:20-08:00 | #9 | Tuesday, October 10, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/009-2023-10-10.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/009-2023-10-10.md#transcript) |[Link](https://nyvxvysvdc5oz5zwbmxrvtkyh2n2rrsqkopr2gxgpd7gkptvvsyq.arweave.net/bit64lUYuuz3NgsvGs1YPpuoxlBTnx0a5nj-ZT51rLE) | #10 | Wednesday, November 08, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/011-2023-11-08.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/011-2023-11-08.md#transcript) |[Link](https://sshyyg4r3uoeixzudilhwdkncekgk3yw5m6mulso6foidluersuq.arweave.net/lI-MG5HdHERfNBoWew1NERRlbxbrPMouTvFcga6EjKk) | #11| Tuesday, December 05, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/011-2023-12-05.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/011-2023-12-05.md#transcript) |[Link](https://ak4u4umlhafhkfu5jjckivcgokrrwkzzitwtwpoy5axl6soc5paq.arweave.net/ArlOUYs4CnUWnUpEpFRGcqMbKzlE7Ts92Oguv0nC68E) -| #12| Tuesday, January 09, 2024 09:00 AM PT (Pacific Time) | | | +| #12| Tuesday, January 09, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/012-2024-01-09.md)|[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/012-2024-01-09.md#transcript) |[Link](https://p2eg6ctrzmvcgqmibhpnvtje32gi3rt3nzdyjocfohwt6kiddsma.arweave.net/fohvCnHLKiNBiAne2s0k3oyNxntuR4S4RXHtPykDHJg) | #13| Tuesday, February 06, 2024 09:00 AM PT (Pacific Time) | | | | #14| March, 2024 09:00 AM PT (Pacific Time) | | | | #15| April, 2024 09:00 AM PT (Pacific Time) | | | diff --git a/sig-clients/README.md b/sig-clients/README.md index 53775338..b7ad00b3 100644 --- a/sig-clients/README.md +++ b/sig-clients/README.md @@ -40,11 +40,11 @@ The goal of this SIG is to foster a community around each of these clients that | #5 | Wednesday, May 17, 2023 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/005-2023-05-17.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/005-2023-05-17.md#transcript) | [Link](https://ec54ewcb4dlthczxdq26le66vkbfbawecwztk54vcl4taihf4woa.arweave.net/ILvCWEHg1zOLNxw15ZPeqoJQgsQVszV3lRL5MCDl5Zw) | #6 | Wednesday, June 21, 2023 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/006-2023-06-21.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/006-2023-06-21.md#transcript) | [Link](https://7wma24vbcylbmj2q74v24kte6sy7ysjarnbbgozg7p4yh5gnkiaa.arweave.net/_ZgNcqEWFhYnUP8rripk9LH8SSCLQhM7Jvv5g_TNUgA) | #7 | Wednesday, July 19, 2023 10:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/007-2023-07-19.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/007-2023-07-19.md#transcript) |[Link](https://cd6v6hartdyqkeqjzqpcdpxcum2dq6lcytnyrtzvgk7joid44xfq.arweave.net/EP1fHBGY8QUSCcweIb7iozQ4eWLE24jPNTK-lyB85cs) -| #8 | Wednesday, August 16, 2023 10:30 AM PT (Pacific Time) |Coming Soon |Coming Soon |[Link](https://56oikxuxws6ewboifrwsgwvq2da4gzrg23sx7u5bldufgusgpc5q.arweave.net/75yFXpe0vEsFyCxtI1qw0MHDZibW5X_ToVjoU1JGeLs) +| #8 | Wednesday, August 16, 2023 10:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/008-2023-08-16.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/008-2023-08-16.md#Transcript) |[Link](https://56oikxuxws6ewboifrwsgwvq2da4gzrg23sx7u5bldufgusgpc5q.arweave.net/75yFXpe0vEsFyCxtI1qw0MHDZibW5X_ToVjoU1JGeLs) | #9 | Wednesday, September 20, 2023 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/009-2023-09-20.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/009-2023-09-20.md#transcript) |[Link](https://hy3zv6e5mxhxnese25p5cupfitg236o6aeivmow6fxfvpnqmjr3q.arweave.net/Pjea-J1lz3aSRNdf0VHlRM2t-d4BEVY63i3LV7YMTHc) | #10 | Wednesday, October 18, 2023 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/010-2023-10-18.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/010-2023-10-18.md#transcript) |[Link](https://yofgxnfxaqk4jruuwko7pyrfckw27dtg5thp6c6bv2sfvfq66jla.arweave.net/w4prtLcEFcTGlLKd9-IlEq2vjmbszv8Lwa6kWpYe8lY) -| #11 | Monday, December 18th, 2023 08:30 AM PT (Pacific Time) |Coming Soon |Coming Soon |[Link](https://msr577epylf5qgo6aexm2xbblsreurfi2pgy5ed5ssdw6ztgkxwq.arweave.net/ZKPf_I_Cy9gZ3gEuzVwhXKJKRKjTzY6QfZSHb2ZmVe0) -| #12 | Wednesday, January 17, 2024 10:30 AM PT (Pacific Time) | | | +| #11 | Monday, December 18th, 2023 08:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/011-2023-12-18.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/011-2023-12-18.md#transcript) |[Link](https://msr577epylf5qgo6aexm2xbblsreurfi2pgy5ed5ssdw6ztgkxwq.arweave.net/ZKPf_I_Cy9gZ3gEuzVwhXKJKRKjTzY6QfZSHb2ZmVe0) +| #12 | Wednesday, January 17, 2024 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/012-2024-01-17.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/012-2024-01-17.md#transcript) |[Link](https://75iuscsrjioekyahvk6vad3taa5ikpweibvxs2rf4amjvzvj6gfa.arweave.net/_1FJClFKHEVgB6q9UA9zADqFPsRAa3lqJeAYmuap8Yo) | #13 | Wednesday, February 21, 2024 10:30 AM PT (Pacific Time) | | | | #14| March, 2024 10:30 AM PT (Pacific Time) | | | | #15| April, 2024 10:30 AM PT (Pacific Time) | | | diff --git a/sig-design/README.md b/sig-design/README.md index 12e68835..0af3aa2f 100644 --- a/sig-design/README.md +++ b/sig-design/README.md @@ -27,7 +27,7 @@ date: 2023-1-09T00:19:20-08:00 | #10 | Wednesday, October 11, 2023 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/010-2023-10-11.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/010-2023-10-11.md#transcript)| [Link](https://lpgpnhvzo3h4wr6vc7qy5rggghi2qztpqj6krjuzlevcmcypf63q.arweave.net/W8z2nrl2z8tH1RfhjsTGMdGoZm-CfKimmVkqJgsPL7c) | #11 | Wednesday, November 08, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/011-2023-11-08.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/011-2023-11-08.md#transcript)| [Link](https://mctlnmdevhysanes52tbok6kbc3mgbsgnn6qemc35xhanfc2x67q.arweave.net/YKa2sGSp8SA0ku6mFyvKCLbDBkZrfQIwW-3OBpRav78) | #12| Wednesday, December 13, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/012-2023-12-13.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/012-2023-12-13.md#transcript) | [Link](https://une76rieq3cvbtrnjv3gxaw6kbxaay3tnzqsangya2lfe6ionpva.arweave.net/o0n_RQSGxVDOLU12a4LeUG4AY3NuYSA02AaWUnkOa-o) -| #13| Wednesday, January 10, 2024 08:00 AM PT (Pacific Time) | | | +| #13| Wednesday, January 10, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md#transcript) | [Link](https://zao4urnjuqb6ncx2vacwjuqiyqnucl2ifcfm33blijhw6v6owzla.arweave.net/yB3KRamkA-aK-qgFZNIIxBtBL0gois3sK0JPb1fOtlY) | #14| Wednesday, February 14, 2024 08:00 AM PT (Pacific Time) | | | | #15| March, 2024 08:00 AM PT (Pacific Time) | | | | #16| April, 2024 08:00 AM PT (Pacific Time) | | | diff --git a/sig-support/README.md b/sig-support/README.md index 18a40e26..3d286b7f 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -40,8 +40,8 @@ sig-support is responsible for defining mechanics of how support works at Akash | #22 | Wed, November 22, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/022-2023-11-22.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/022-2023-11-22.md#transcript) |[Link](https://l5yeilkhvwmpqetchbk2pax4nxmu6miv23cxy7iszl7nvgbk4lka.arweave.net/X3BELUetmPgSYjhVp4L8bdlPMRXWxXx9Esr-2pgq4tQ) | #23 | Wed, December 06, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/023-2023-12-06.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/023-2023-12-06.md#transcript) |[Link](https://hzvr27yxq5skbo2dwiw6yums3dd4ujzhibdn44zpod5ebxslfinq.arweave.net/PmsdfxeHZKC7Q7It7FGS2MfKJydARt5zL3D6QN5LKhs) | #24 | Wed, December 20, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/24-2023-12-20.md)|[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/24-2023-12-20.md#transcript)|[Link](https://kesic5sqastbfceerxf7d5zcqcumbjpipfw45q6oxxmcguazpotq.arweave.net/USSBdlAEphKIhI3L8fcigKjApeh5bc7Dzr3YI1AZe6c) -| #25 | Wed, January 10, 2024 07:00 AM PT (Pacific Time) | | | -| #26 | Wed, January 24, 2024 07:00 AM PT (Pacific Time) | | | +| #25 | Wed, January 10, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/025-2024-01-10.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/025-2024-01-10.md#transcript) |[Link](https://p263aeernjmdkonkrihc227wya76yjyvivs5pkojdjx63unz4lha.arweave.net/fr2wEJFqWDU5qooOLWv2wD_sJxVFZdepyRpv7dG54s4) +| #26 | Wed, January 24, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/026-2024-01-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/026-2024-01-24.md#transcript) |[Link](https://47vntytp4ni2s5p2h2qyh5nuqywowtwne2fx4ddudv7iyl3hu5rq.arweave.net/5-rZ4m_jUal1-j6hg_W0hizrTs0mi34MdB1-jC9np2M) | #27 | Wed, February 07, 2024 07:00 AM PT (Pacific Time) | | | | #25 | Wed, February 21, 2024 07:00 AM PT (Pacific Time) | | | | #26 | Wed, March 06, 2024 07:00 AM PT (Pacific Time) | | | diff --git a/wg-akash-website/README.md b/wg-akash-website/README.md index 8fd15ebe..0ff6bcba 100644 --- a/wg-akash-website/README.md +++ b/wg-akash-website/README.md @@ -30,7 +30,9 @@ This working group is responsible for managing and improving the Akash Network W | #18 | Thursday, November 27, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/018-2023-11-27.md) | [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/018-2023-11-27.md#Transcript) | [Link](https://svuqqu3fnqzburnqmdfrvy6bsku3fef2uzsbmspouj5mo2r4gjmq.arweave.net/lWkIU2VsMhpFsGDLGuPBkqmykLqmZBZJ7qJ6x2o8Mlk) | #19 | Thursday, November 30, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/019-2023-11-30.md) | [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/019-2023-11-30.md#Transcript) | [Link](https://ljuj3z4qnrttv4kg3z5owik37rofcpakeuwvmpqbiesastrh2coq.arweave.net/Wmid55BsZzrxRt566yFb_FxRPAolLVY-AUEkCU4n0J0) | #20 | Thursday, December 07, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/020-2023-12-07.md)|[Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/020-2023-12-07.md#Transcript)| [Link](https://bmafqxmmyqqxc65uxwkpgetv4r6yzlx6g3wsfzqqahumvzo4hrmq.arweave.net/CwBYXYzEIXF7tL2U8xJ15H2Mrv427SLmEAHoyuXcPFk) -| #21 | Thursday, December 14, 2023 06:30 AM PT (Pacific Time)| Coming soon | Coming soon| Coming Soon +| #21 | Wednesday, January 03, 2023 06:30 AM PT (Pacific Time)| Coming soon | Coming soon| Coming Soon +| #22 | Thursday, January 04, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/022-2024-01-04.md)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/022-2024-01-04.md#Transcript)| [Link](https://ebt6smszfxnrsafl35ae3krholqikfmckktlj6rw2tpk26lxcmgq.arweave.net/IGfpMlkt2xkAq99ATaoncuCFFYJSprT6NtTerXl3Ew0) +| #23 | Friday, January 05, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/023-2024-01-05.md)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/023-2024-01-05.md#Transcript)| [Link](https://5vpr5a76zkbuulfpmj7mtg24vkn6vpli5zlmcvqd3uupea3bxgva.arweave.net/7V8eg_7Kg0osr2J-yZtcqpvqvWjuVsFWA90o8gNhuao) ## Leads diff --git a/wg-zealy/README.md b/wg-zealy/README.md index 005132b7..17ed8d3f 100644 --- a/wg-zealy/README.md +++ b/wg-zealy/README.md @@ -11,14 +11,16 @@ The working group is created to work on the proposal to see what support is need | Meeting | Time | Notes | Transcript | Recording | --- | --- | --- | --- | --- | | #1 | Friday, February 17, 2023 08:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-crew3/meetings/001-2023-02-17.md) |[Link](https://github.com/akash-network/community/blob/main/wg-crew3/meetings/001-2023-02-17.md#transcript) | coming soon -| #2 | Monday, November 20th, 2023 08:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/002-2023-11-20.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/002-2023-11-20.md#transcript)|[Link](https://omnv3rqpb3qrv5iw4tdpu2eipbonzvjr2khqiponlrtgftkwwybq.arweave.net/cxtdxg8O4Rr1FuTG-miIeFzc1THSjwQ9zVxmYs1WtgM) -| #3 | Monday, November 27th, 2023 08:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/003-2023-11-27.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/003-2023-11-27.md#transcript)|[Link](https://47vhtsd36l63wlteorhccwvklpzihemikfrxljg6mebv2myt7bzq.arweave.net/5-p5yHvy_bsuZHROIVqqW_KDkYhRY3Wk3mEDXTMT-HM) -| #4 | Monday, December 4th, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/004-2023-12-04.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/004-2023-12-04.md#transcript)|[Link](https://sq2ysituuvyyyeuuw7eawkdlbmvqpwtlkqkpogujyh5jfoxexosq.arweave.net/lDWJInSlcYwSlLfICyhrCysH2mtUFPcaicH6krrku6U) -| #5 | Monday, December 11th, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/005-2023-12-11.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/005-2023-12-11.md#transcript)|[Link](https://hp5novctzn3y56mrqix5wq3knexy4w24tk2ugahmstq2ofxzp57a.arweave.net/O_rXVFPLd475kYIv20NqaS-OW1yatUMA7JThpxb5f34) -| #6 | Monday, December 18th, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/006-2023-12-18.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/006-2023-12-18.md#transcript)|[Link](https://efn65ve3e5sebv7bhpgilvvzv23zx3ln6goskfwwrhj5rsmbludq.arweave.net/IVvu1JsnZEDX4TvMhda5rreb7W3xnSUW1onT2MmBXQc) -| #7 | Monday, January 15th, 2023 06:30 AM PT (Pacific Time)||| -## Leads +| #2 | Monday, November 20, 2023 08:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/002-2023-11-20.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/002-2023-11-20.md#transcript)|[Link](https://omnv3rqpb3qrv5iw4tdpu2eipbonzvjr2khqiponlrtgftkwwybq.arweave.net/cxtdxg8O4Rr1FuTG-miIeFzc1THSjwQ9zVxmYs1WtgM) +| #3 | Monday, November 27, 2023 08:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/003-2023-11-27.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/003-2023-11-27.md#transcript)|[Link](https://47vhtsd36l63wlteorhccwvklpzihemikfrxljg6mebv2myt7bzq.arweave.net/5-p5yHvy_bsuZHROIVqqW_KDkYhRY3Wk3mEDXTMT-HM) +| #4 | Monday, December 04, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/004-2023-12-04.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/004-2023-12-04.md#transcript)|[Link](https://sq2ysituuvyyyeuuw7eawkdlbmvqpwtlkqkpogujyh5jfoxexosq.arweave.net/lDWJInSlcYwSlLfICyhrCysH2mtUFPcaicH6krrku6U) +| #5 | Monday, December 11, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/005-2023-12-11.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/005-2023-12-11.md#transcript)|[Link](https://hp5novctzn3y56mrqix5wq3knexy4w24tk2ugahmstq2ofxzp57a.arweave.net/O_rXVFPLd475kYIv20NqaS-OW1yatUMA7JThpxb5f34) +| #6 | Monday, December 18, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/006-2023-12-18.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/006-2023-12-18.md#transcript)|[Link](https://efn65ve3e5sebv7bhpgilvvzv23zx3ln6goskfwwrhj5rsmbludq.arweave.net/IVvu1JsnZEDX4TvMhda5rreb7W3xnSUW1onT2MmBXQc) +| #7 | Monday, January 15, 2023 06:30 AM PT (Pacific Time)|coming soon| coming soon | Coming soon +| #8 | Monday, January 22, 2023 06:30 AM PT (Pacific Time)|coming soon| coming soon | Coming soon +| #9 | Monday, February 05, 2023 06:30 AM PT (Pacific Time)|coming soon| coming soon | Coming soon +## Leads - Piber Dev - Robert Del Rey From 3205ab693b8cb074da7ba92bbd1abd71ca0d05f6 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Mon, 12 Feb 2024 12:59:12 -0500 Subject: [PATCH 004/138] steering-committee Create 012-2024-01-25.md (#469) * steering-committee Create 012-2024-01-25.md add transcript, recording, participants, and meeting details. Chore: Add meeting notes and action items Signed-off-by: Drinkwater * Rename 2024-01-25.md to 012-2024-01-25.md Signed-off-by: Drinkwater * Update 012-2024-01-25.md Signed-off-by: Drinkwater * Update 012-2024-01-25.md Signed-off-by: Drinkwater --------- Signed-off-by: Drinkwater --- committee-steering/meetings/012-2024-01-25.md | 351 ++++++++++++++++++ 1 file changed, 351 insertions(+) create mode 100644 committee-steering/meetings/012-2024-01-25.md diff --git a/committee-steering/meetings/012-2024-01-25.md b/committee-steering/meetings/012-2024-01-25.md new file mode 100644 index 00000000..7e0bd1da --- /dev/null +++ b/committee-steering/meetings/012-2024-01-25.md @@ -0,0 +1,351 @@ +# Akash Network - Steering Committee - Meeting #12 + +## Agenda + +- Review / discuss / address any community feedback, grievances, or conflicts. +- Review [projects list](../projects-list/README.md), prioritize / add / remove if necessary. +- A look at open discussions in [Github Discussions](https://github.com/orgs/akash-network/discussions). +- Open up to any other questions from the community. + +## Meeting Details + +- Date: Thursday, January 25th, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://uh4qrdp5wsvzihnnh7m7conzwkllrei4xawnfsohgjmp5qpjberq.arweave.net/ofkIjf20q5QdrT_Z8Tm5spa4kRy4LNLJxzJY_sHpCSM) +- [Transcript](#transcript) + +## Committee + +- Adam Bozanich, Overclock Labs +- Anil Murty, Overclock Labs +- Artur Troian, Overclock Labs +- Greg Osuri, Overclock Labs +- Scott Caruthers, Overclock Labs + +## Participants + +- Adam Wozney +- Alani Kuye +- Andrew Gnatyuk +- Anil Murty +- Artur Troian +- B S +- Benjamin B +- Cheng Wang +- Crypto Cowboy +- Damir Simpovic +- Deathless +- Denis Lelic +- Deval Patel +- Dimokus +- Evan Neal +- Greg Osuri +- Javier Suarez +- Jigar Patel +- Joao Luna +- Julius Haus +- Max +- Maxime Cyr +- Okhai Omotuebe +- oo o +- Pierre-Andre Manseau +- Poroburu +- Robert Del Rey +- Rodrigo Rochin +- Scott Carruthers +- Scott Hewitson +- SGC | DCnorse +- Tyler Wright +- Zach Horn +- Zach Ross + + +## Notes: + +- Tyler asked the community about whether or not anyone had any concerns or issues with the sigs or wgs. +- There were no issues from the community at this time. +- Tyler led the group through the agenda. +- Tyler introduced the agenda and emphasized community feedback, project reviews, and new discussions. The updated rules can be found [here]( +- Since we're limited on time, discussion topics and proposals will be chosen based on the following criteria: + - When was the discussion topic created? (older ones that have not been discussed in SC yet get priority) + - Has there been discussions in the specific SIG that it applies to? (for example - incentives in sig-provider, spheron stuff in sig-clients etc). SC shouldn't be spending time on ones that haven't been discussed in the respective sigs. + - What level of engagement has there been on the discussion thread itself? (ones with higher engagement should be prioritized over others). + - Is the champion of the initiative on this call? (not being there to talk about your proposal means we don't spend time on it). + - Is the champion someone who is currently active in the community? (generally priority to people that actively participate in other discussions as well is discord and sig/ wg calls) +- Anil highlighted the importance of discussing topics in respective SIGs first. +- Tyler and Scott Hewitson mentioned funds available for community contributions. Bounty board is available [here](https://github.com/orgs/akash-network/projects/6/views/2?sliceBy%5Bvalue%5D=%24%24+Bounty+%24%24). +- Scott C. updated everyone on progress with the feature discovery service. + + +### Projects: + +- Tyler talked about the project list that was used in 2023. A lot of progress has been made across a number of different of projects. +- Tyler introduced project boards for Product and Engineering and Community and Marketing. +- Please feel free to access the boards [here](https://github.com/orgs/akash-network/projects). +- Tyler walked through some of the key items on each board including feature discovery service, AMD support and beyond. + +#### [Product and Engineering Board / Community + Marketing Board](https://github.com/orgs/akash-network/projects) + +- Tyler talked about product and engineering roadmap. +- Artur and Scott gave an update on feature discovery service. + +### Github Discussions: + +- Tyler talked about the GPU Provider Incentive proposal brought forward by Overclock Labs. Cheng mentioned some recent changes to the proposal, based upon feedback, so please continue to get involved in discussions. +- Alani discussed his proposal on a provider review system, similar to AirBNB. His goal was to start a conversation around the UX for deployers. +- Robert and Benjamin talked about wg-zealy, a developer onboarding platform. They talked about the success of the pilot, and some users that came from Zealy, and are now active in the community. +- Please look at the [discussions](https://github.com/orgs/akash-network/discussions) or watch the [recording](https://uh4qrdp5wsvzihnnh7m7conzwkllrei4xawnfsohgjmp5qpjberq.arweave.net/ofkIjf20q5QdrT_Z8Tm5spa4kRy4LNLJxzJY_sHpCSM) for better perspective. + + +### Action Items: + +- Please get involved in all of the discussions on github. +- Schedule meetings for wg-provider-audits and wg-akash-hackathon 2024. +- Put Akash GPU Provider Incentives Pilot Proposal on chain. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the first Akash steering committee monthly meeting of 2024. Appreciate everybody joining. I'm going to drop in the chat a link to the steering come read me. What we do during these steering committee meetings is Anil or myself leads the group through a The typical agenda includes reviewing discussing addressing any Community feedback, which we'll get to in a second. Then we go over list of all the projects that are open and being worked on the engineering side and product side as well as the marketing and Community size. + +Tyler Wright: And then from there we go into a reviewing of any new discussions. I know there's a number of discussions that have been going on over our last few weeks so much appreciate everybody for picture purposes of it participating in those discussions. We have added some criteria because again with this slot is only an hour for the steering committee. So we've added some criteria for order of operations and prioritization during the steering committee for kinds of discussions that we'll talk about. I shared this with folks yesterday in Discord, and we'll use this as a prioritization pool today and moving forward and then with anytime We make sure if anybody has any other questions or discussions they want to talk about. + +Tyler Wright: Please we'll do that at the end. + +Tyler Wright: cool with that said we'll start off with the agenda and'll through so a Neal can continue to I always focusing on a number of things but I'll lead us through the agenda today again, we usually start with reviewing discussing and addressing any Community feedback grievances are conflicts related to the cigs and working groups or anything that you see in Discord or any other channels. Does anybody have any feedback about the six working groups other user groups as we start 2024? + +Tyler Wright: cool Go ahead and Neal. + +Anil Murty: Yeah, just the one note I want to add here is that and this is sort of related to the GitHub discussions and how we prioritize what we spend our time in this state committee meeting. One of the things that we had said when we originally started this open development model about middle over a year ago was any discussions that I mean obviously people can post any sort of discussions on the discussion board. That's an open board but for topics that get discussed here and we spend time on one of the things that we said was important was that the proposals or discussions be discussed in the six first, so if there's something that somebody's proposing as part of clients or something bring it up there. So for example, one of the things we'll talk about today is GPU incentives. This is something that we've been discussing quite extensively in various things including economics and stick providers. There's kind of want to throw it out there in terms of things related to six as well as things to + +Anil Murty: discussions + +Tyler Wright: Thank you Anil. + +Tyler Wright: there's also a note that Huey wanted me to mention in terms of bounties and I'll link to the bounty board in the chat for folks but there are funds available to the community with the stigs and the working groups being the focus for how people are deciding on what is important to build from the community. So again, if the user is joining a specific Sig or working group and the singer working group, as an example docs is looking for more Community contributions and there are a number of people in that. We're in that Sig that are talking about contributing. please feel free to put a bounty for your time and efforts to add new documentation to again the official docs there are funds available for those that are working through the states and working group structure. So again here we wanted me to shout that out. And please I'll add the bounty board for folks to look at but + +Tyler Wright: these feel free to start conversations and contribute to the states and working groups and figure out where you can again. Apply your talents more and receive rewards for them. + +Tyler Wright: cool if there's nothing else on The current structure then we'll move on to the next agenda item around reviewing projects and prioritizing and removing any if necessary. + +00:05:00 + +Tyler Wright: On GitHub again in the Akash Network organization. You can see two project boards one for the product and Engineering roadmap and one for the community and marketing initiatives. These are active boards that we talked about every steering committee and are actively kept up. So if anybody has any questions about anything specific between steering committee's, please look at these boards to track what's going on on various roadmaps, and then we can again go from ask questions in specific projects or on Discord and we can continue conversations there between meetings. cool + +Tyler Wright: All right, focusing up on what's going on in the product and Engineering roadmap. There's a number of items that are in testing right now including provider feature Discovery service AMD support and removing analytics from deploy on AMD support. There's been some members of overclock team are working on documentation round one of the AMD support. And that's going to be distributed to folks in the community to start building providers with AMD gpus. And again, that's documentation will get updated. Does anybody here on the call have any thing that they want to mention about AMD support? + +Tyler Wright: cool I know a big action a big item that affects GPU provided incentives and a number of things that members of the core team including Artur in Scott have been working on has been the provider future Discovery service Archer Scott. Is there anything that you want to highlight for the community again? They can track all the updates here. There's anything that you want to highlight for the community on the call. + +Scott Carruthers: Yes, so Artur doesn't seem to be on the call. So I'll just give a brief update. So post the work that I did Artur is taking the feature Discovery into Automation realm so that providers will no longer have to manually label GPU resources. So we're just going through that and some finalized testing I would assume that it's going to be released very very soon. + +Tyler Wright: Thank you very much I know there's a number of items that are happening in progress as well. And I don't want to spend a great deal of time going through each one of them if anybody has any questions about any specific items in the aim progress column or in the up next or backlog for the engineering and product roadmap, please feel free to raise a hand right now one that I will call out is I know that the working group for Content moderation has been going on for around a year and there's a number of solutions that have been being worked on as of last week. Members of the core team have taken a review at the work that the prior team has been working on in terms of content moderation. + +Tyler Wright: I know there's some next steps that the pretor team has in terms of rebasing after some changes have been made to the court code base, but those conversations are continuing to happen and you can track that those conversations here. So again, there's a continued work happening around content moderation on the provider side. And obviously the cloud most team who I know the Max's are on the call or doing a great deal of work on the cloudnosed API refactoring of the cloud most deployed tool and a number of other efforts Max's. Is there anything that you wanted to highlight? Don't feel like you have to because I know that Workout number of things, but just want to give the ability to talk about anything at a high level that you're working on. + +Max: Nothing special to mention everything is being worked on that decent place. + +Tyler Wright: Excellent and again, I know that Maxi's work around the cloud. Most API is something that I know the pre-tor team is using and a number of other teams and individuals can access. So again, if anybody has any questions about cloudmus API the refactor work any of the readme files again, feel free to drop a question in here and Discord and we'll make sure it gets followed up very quickly. + +Tyler Wright: Cool before I move on to the community and marketing project board. Does anyone else have anything that they want to highlight or any other questions related to anything on the product and Engineering roadmap? + +00:10:00 + +Tyler Wright: Also, look at the items in the release. I know if anybody here is building anything. I know the Scott has done a great deal of work on end testing and there's a number of other items again in the release column. So feel free to look at the various projects. You can track down specific code if you're looking for it or how to do things Etc. + +Tyler Wright: cool Moving along there's a number of items going on in terms of marketing and Community. I know that Adam has been doing a great job of letting folks know what's going on with various events Is there anything that you want to highlight on the events front for the community? + +Adam Wozney: No, I mean The Big Three income or upcoming in person events that are taking place are East Denver boobcon and Nvidia GTC. We're gonna have a presence at each of those events from members of the overclock Labs team and community members representing Akash a lot of things in flight, but everything's tracking really nicely for those three events. + +Tyler Wright: excellence anyone have any questions about anything events related? Again, there is an event working group that Adam leads with other members of the community where they discuss specific events in detail our presence Etc. I know he's been doing a lot of planning around q1, but Q2 is where on the quarter so I know he's doing a fair amount of planning for Q2 and Beyond as well. + +Tyler Wright: Cool one action item that is just been completed is the dove prop around the 2024 across hackathons. So again, thank you to all those that voted and participated in discussions leading up to the proposal going on chain Adams or anything that you want to highlight here. I know a working group is around the corner, but there's anything specific that you want to talk about. + +Adam Wozney: Yeah, very quickly. I'm looking to schedule the first working group for our upcoming hackathons next week. So if you're interested head over to the Discord and jump into the channel, so next week, we'll have our first working group call around planning our upcoming hackathons for the year. + +Tyler Wright: Excellent. Thank you Adam. + +Tyler Wright: again, I know there's a number of items that are community and marketing related that are being worked on this board. Does anyone have anything that they want to talk about specific to any of the projects on the committee and marketing initiatives anyone have any questions comments or anybody working on any of these items want to talk about them any further? Go ahead Robert. + +Robert Del Rey: Yes, I'm ready to present the developer rewarding weekly. I don't know if you're referring that outlining. + +Tyler Wright: Okay, Your connection is a little bit shaky. I can kind of hear you but I can hear a lot of background noise. So just be aware of that. + +Tyler Wright: quickly, I believe what Robert's talking about is Robert and Benjamin cook. There was some Community funds available that they use for a pilot at the end of 2023 for a working group. pilot Zeal is a platform that is a developer Focus platform. They have a fair community and it's a developer onboarding platform Benjamin & Robert went through a pilot that was very successful and led them to put a discussion on GitHub for further programming. So again that item that pilot that took place in 2023 is now over everybody that participated in that pilot has been paid and I think there's a number of folks that are now members of the Discord and are sticking around and getting involved with some other projects. So again that item is now Mark complete. + +Tyler Wright: Is there anything else on the community or marketing initiatives that anybody wants to discuss in more detail at this time? + +Tyler Wright: All right. If not then again. I might see a hand go ahead Andrew. + +00:15:00 + +Andrew Gnatyuk: Yeah, I'm sorry. I'm just another question about the bounty board. I like it. I really do. There's just one thing that if we are going to push the bounty board to the community, let's say right so they can just Luke and share for the bounties. So how are they applying for that just under the Bounty hey, I'll take it and the Soul or how does this should work actually? That for example for three to five people work under the one bar. Let's say that's my question. + +Tyler Wright: Go ahead Scott, and then I can follow. + +Scott Hewitson: Yeah, I just want to jump in so for that right the ideas for bounties can come from anywhere overclock comes up with them sigs working groups come up with them and then it's ideally like, It's not in the traditional sense of a bounty where you do this and then it's paid it, for some stuff where there's new more Nuance. We want to assign the right. + +Scott Hewitson: Overclock Labs put up the proposal for the community support. So we're managing from that standpoint. so if you see something you just reach out either to me Ty whoever and we'll see if it's a good fit. + +Andrew Gnatyuk: Yeah, but if there is two or five people reaching out to you on the same Bounty, picking the one who is eligible or how are you who is the judges who will get the last results? + +Scott Hewitson: Yeah. + +Tyler Wright: The only thing I'll add is again we're trying to push as many folks into the sinks and working groups as possible. So if there are a number of people that are talking about a specific Bounty, I would create some time for those people to talk about their strategies at a sake of working group so that we can again hear these people get to know them at least a little bit as a community before even small amounts that we're handing out so there will be a slight process but the process will move significantly faster than folks trying to again put things on chain up for vote for small amounts. + +Tyler Wright: cool All Next up on the agenda is active GitHub discussions again. We'll start with discussions that have been on for a long time. Hope everybody can see my page. I believe. + +Tyler Wright: the last discussion that we talked about was from there was some conversations around new schema for provider attributes. I know we'll talk about that in a future Sig so we'll cover that a little bit later. But as a Neal mentioned one thing that's been talked about a great deal in Sig economics and in sync providers and has been on for a little while and has got a fair amount of discussion. A lot of discussion is the Akash Network GPU provider incentives. + +Tyler Wright: I guess starting there. Does anybody have any specific items that they would like more clarity on or anything that hasn't been discussed already in the chain. I'll drop the chain in the chat for folks. But again folks should be reading up on all these discussions and really commenting prior to the steering committee so we could just talk about high level points. But does anyone have anything they want to talk about in terms of a cost Network GPU provider incentive? + +Tyler Wright: function Go ahead chength. + +Cheng Wang: If there's nothing just want to make a quick point of order, I think it's quite obvious. We updated the post last night. So there's fresh feedback that we've taken to account from the community which has been I think really good in productive that we incorporated into the latest edit of the post. So please if you read through the original post, this does have a lot more detail and incorporates a lot of what the community has mentioned us far. So, please do take a additional read over on this has changed from the op that was posted about a week ago. + +00:20:00 + +Tyler Wright: All right, if there's no further discussion on that then we'll continue on. with some other items looking at the list. + +Tyler Wright: Artur I know there's a discussion in Discord around Noble usdc. this is discussion that we can continue to monitor async. We don't have to talk about it any further now and I know that this is discussion that a member of the validator community and put on and this is something that members of the core team and some other members of the community are actively working on so we'll continue to track this discussion. And again anybody can feel free to see what's going on inside moving on to some other discussions that again, I guess next up we can talk about the developer onboarding program via zeely again, there's been a working group that's been going on for + +Tyler Wright: Maybe two months now, there's been a pilot that has gone on and I know that Benjamin & Robert inside is in vanguards have been leading this program. So I do want to pass it over to Benjamin & Robert to talk for maybe one minute at a high level about What the ask is from the community and why they think this program is impactful and then we can see if there's anybody from the community that wants to talk or has any questions and then we'll have more folks continue to give feedback here, but I'll hand it over to Benjamin if you want to talk very briefly about the developer onboarding program via zealy. + +Benjamin B: Thank you, Tyler. Will you have the screen share or should I do it? + +Tyler Wright: I'm sure you're right now, but I'm happy whatever you prefer. + +Benjamin B: As long as you scroll down a little during when I go to the later Parts, it's fine. So basically what me and Robert has been doing since a few months back is that we have been using working group we have been trying to find a way to + +Benjamin B: to educate people on a coach with missions which shows to use the platform Sealy and + +Benjamin B: And we ask for funding during December I believe. We were able to get about it from the community pool. and we Created One Pilot and we did another. + +Joao Luna: just + +Benjamin B: And we've learned a lot from this. + +Benjamin B: Basically we have Been able to reward users about free thousand dollars worth of AP for completing missions. + +Benjamin B: we believe that the program has been very successful. I don't really know What people want to hear what you need explained or not? And I will also leave it to Robert's to explain more. + +Tyler Wright: Cool, go ahead Robert and… + +Robert Del Rey: Thanks,… + +Tyler Wright: then Anil. + +Joao Luna: Because okay. + +Robert Del Rey: Benji. Let me know if you guys can hear me Sorry for the noise earlier. + +Tyler Wright: forever Robert your background. I can still hear a little bit of background noise and I think if you continue to talk it might be hard for people to hear. + +Tyler Wright: It might be easier a Neal. Do you have anything that you want to say? And then I have no problem being able to speak very on a high level about Zoe and… + +Joao Luna: so that's + +Tyler Wright: then having folks that might have questions or want to continue discussion and GitHub go. So a Leo. Do you want to go first because Robert it's a little bit hard to hear you. + +Anil Murty: Yeah, So I guess really quickly. Could somebody talk about in terms of… + +Joao Luna: Okay. + +Anil Murty: how long this has been running already or is it not started yet? And if it has been running for a while? Or I guess even if it's not started yet, what is kind of the plan to know if the people that do go through These missions end up sticking around versus just completing the mission then and then worrying about Akash again. + +Benjamin B: I didn't take this question. So we have had the two pilots done, period of about one month + +Benjamin B: We don't have any objective data on. Whether or not users has stuck around. However, we have had the other users mentioned that they have noticed people coming to understand staying in the community of skiing a bunch of questions. + +00:25:00 + +Tyler Wright: Go ahead Robert. + +Robert Del Rey: Hi again, guys. Can you hear me better? Okay. Okay. + +Tyler Wright: Yes. + +Robert Del Rey: Sorry about that guys. and Real quickly about feeling just to support a bit. But then you was talking about we've been doing this for I started by myself onagost 2023 and then Benji helped me decided to join the initiative and we kind of take it seriously around October 2023 and then after speaking with a score and Tyler we were able to get some funding for the pilot and about Sealy for those of you that don't know silly. It's a tool that helps you grow your community their promise is that doesn't matter. What is your community? You can create missions to make your community engaged with your project. + +Robert Del Rey: So I've been using silly for a year and a half by now. I've been a member of Philly, but I also don't silly when I was working in a staking as a validator and we got great success growing up the community, but I wanted to do it differently because many projects were using silly just to engage on social media example go to Twitter and retweet this go to Twitter and our post go to Twitter and Share a threat. The approach we wanted to give was focused on a cash and we wanted to gave me five the developer process and let me explain a little more about that. We made missions to make people get started on a cache. + +Robert Del Rey: The missions were really simple download a cash CLI interact with cloudmose run a GPU testnet provider. And create your own sdl image just to give you some examples. And during the month and something that we officially run the pilot around 76 people interacted with Out of those 76 people 48 were able to get to the second level and they got more Rewards. And out of those 40 something we got 15. People that were able to complete most of the missions. now + +Robert Del Rey: with this pilot, we were able to learn more about Seeley. We were able to optimize the missions to make them more clear. And we were able to have clear instructions, right? + +Robert Del Rey: the next step we want to do is we want to formalize this we want to now it's silly but could be something else right? We want to focus on onboarding developers. it doesn't matter if you're a beginner developer. If you're a system developer, we can create different set of missions depending of the need a cash has the cash Community has better said so the next step from now it's like Fine-tuning what's gonna be the best amount to reward to people to do those missions and what missions can we have? So these steps can build things that are useful for a cash. + +Robert Del Rey: We have some cases that people did it for the first time we have also cases that it was one single household when the Big Brother helped the small brother to do the missions. And it was really fun for them. what we want to do is we want to continue doing the good stuff. But we want to use Sealy to recruit Talent as well. We want to create missions in a way that people can do them and based on the missions. we know where to assign those people if they do many missions about becoming a provider. + +Robert Del Rey: Maybe they can be a good addition for the providers in a cache if they have deployments. They can be good additions for the deployments working group if that's a working group for if there are people that are very engaged with community building and content creation. We can have them to be a cash creators or a cash insiders and even vanguards. So the proposal there has the numbers. + +00:30:00 + +Robert Del Rey: There is another document that has a graph so you can visualized the data better. That was a suggestion Adam left in the comments. I'm going through the suggestions and yeah, we basically wanted to bring this to you guys after nothing encouragement from Tyler and from Scott and from Fiverr. Thank you guys. I believe we reached to the point that now more people in the community can know about this but also can get involved and help us make these initiative better. We also included things like budget for pain for the working hours. And we also included boy get for the rewards. But again those things are up to this caution and that's why we went to bring this to a table today. I hope my explanation wasn't too long or too confusing. But yeah, that's the deal. We want to onboard developers to a cash We Believe silly. + +Robert Del Rey: Outpost to do that and make it a game make it fun making challenging and we see a great opportunity to onboard people develop but also onboard people to be in other areas of a cash not only development like it's super broad the rich that we can have with silly. That's what I have to say for now. + +Tyler Wright: I really appreciate that. Yeah. + +Tyler Wright: I really appreciate that explanation again, if anybody has any thing that they want to add please feel free to get involved in this discussion and then we'll take next steps there. There is a working group brazily that has been meeting pretty regularly. We'll set up the next meeting. And again, if anybody from the community wants to participate and… + +Robert Del Rey: just + +Tyler Wright: get involved in the strategies work with around Sealy feel free to do but again want to make sure that Robert Can Benjamin had some time to talk with the community. And then we have about 25 minutes left. So I'm just like keeping my eye on the clock. Saw a hand up. Maybe it's not up anymore. Go ahead Alani. + +Alani Kuye: Yeah, very quickly just 30 seconds. Robert awesome. I love that idea. I'm just very quick addition if there's a way to gamify sdxl because it's free to use and I've been playing a lot around a lot. I've been playing with it a lot just generate an images and all kinds of things and that's a great way that we can leverage that into marketing just reward we can all go vote for the coolest image just hashtag it with a caution and track that I think I mean, we have a hundred thousand followers, on Twitter alone in the thousand of them could go on. That's the excellent generate images and hashtag it. I think we can always give me fight just make it fun. I think it's a great idea of what you give me to give me fine and engage non-dabs because I can't remember the history is focusing on dance, but we got to think about the real humans out there that are trying to use a system. Unless Keep It Fun. + +Tyler Wright: cool All right, if there's no other questions about the developer onboarding program via zeely, then we can continue on with other discussions. Moving along. I know there's been a couple of conversations around education. Some of them are newer than others. Is anybody here representing the educational ecosystem accelerator Grant proposal? + +Tyler Wright: I would also ask that if anybody here has any education programs feel free to join the Sig Community which happens monthly and you can start to pitch some of these ideas here before again putting proposals on discussions. Anybody can feel free to put this proposed discussion up on GitHub, but it would be better if you talk to members of the community prior. + +Tyler Wright: I do see Alani here, and I know that Alani put up a proposal. Again, if we could just talk at a high level about and I just asked this if anybody at the highest level about what's the problem that you're trying to solve the potential ask I know we could talk about theoretical all day, but I just want to make sure that everybody's crypto clear on. What's the problem being solved the ask and then we'll have folks that can continue this conversation and continue asking questions in the discussion thread. So Alani, I'll give you about a minute or so to talk about the cost network provider review and it's sent to the proposal. + +00:35:00 + +Alani Kuye: I should only 30 seconds the objective here really is around dislodging. Deployer incentives from provider incentives and tackling it very differently. Because as I always say, most problems look like a nail if we're culturally accustomed to use in the hammer. On the other hand if there's no appetite for it and there's a belief that has been solved elsewhere and that's fine because my main objective here is to get this discussion started that perhaps in a two-sided Marketplace. We have to dislodge examine and solve for the other side of the marketplace in a different iteration. We can always look at the details. Obviously everything happens on chain, whether you're going in reviewing level one level two pulling all the data extrapolating into all the legal systems all that's there. So + +Alani Kuye: input is always welcome. Like I said earlier if there's no appetite for it and you feel it's been done elsewhere totally fine, but at least we've talked about it. + +Tyler Wright: Does anyone have any specific comments or questions related to this proposal that it might be better to talk about for a couple of minutes live that hasn't been talked about in the GitHub discussions. + +Tyler Wright: cool + +Tyler Wright: So I'm just reading through a little bit here cool if there's no discussions or nothing to anybody wants to talk about right now. I would just again urge that folks can continue to get involved in this discussion. And then maybe this is something that we talk about again during sick clients if there's not a lot of traction prior to that. + +Tyler Wright: cool All right, are there any other participants here that have any active discussions that they want to talk about that haven't been discussed already? + +Tyler Wright: All right. If not, then again, I just ask that everybody continued to get involved in these discussions. + +Tyler Wright: Everybody here knows that I'm all about pushing things forward. I hate when things say stagnant. So again, please get involved in these conversations from there that I can create action items and we can start to push these things forward. Go ahead Roger. + +Rodrigo Rochin: hail I just wanted to remind you I share an idea about a possible provider building program I think it's a great way to onboard new providers higher quietly quality providers. And make the network more decentralized. I've been running a provider for about a year or year and a half now. I've been leasing some bps's On a centralized cloud provider, which I don't want to name. + +Rodrigo Rochin: It just happens that yesterday one of the notes failed And it's down this probably wouldn't happen if we had a provider in our own. and I think like I said this could on board more people and just a great way to decentralize the network. + +Tyler Wright: Thank you for bringing this up Raji. Go ahead Alan. + +Alani Kuye: Very quickly just throwing this out. They had a left field if anyone is working on, a DNA Bank, on chain on a cost. I would gladly pay for it because I'm trying to inventor the DNA, if my bison about 35 of them coming from Wyoming soon. Let me know. + +Tyler Wright: Excellent, Roger I appreciate you very much for bringing this conversation up. I know that this is something that myself and other members of the core team plan to be very interesting. I know that I reached out to you. So this is something that I want to at least Explore More. So again, if anybody else has any discussions or anything that they want to talk about related to a provider build program and what it could look like obviously Greg has been, acting this conversation kind of sharing the specs for the bill that he's been experimenting with + +00:40:00 + +Tyler Wright: Please we talked about this a bit in sick providers as well less last week. But if anybody or Susan this past week, but if anybody wants to get involved in discussion, please do so and again Rodrigo continue to work to see if it can at least they got an initial pilot for something like this. + +Tyler Wright: Cool, are there any other active discussions anybody wants to talk about it or any other questions about any discussions that anybody wants to ask right now while we have a number of folks from the community and also the steering committee here? + +Tyler Wright: Last item on the agenda is open discussion. Does anybody here have anything that is maybe pre discussion right now or any other topics that they want to bring up with the team that has already been talked about six working groups or anything that anybody wants to highlight right now with the number of folks from the community here. + +Tyler Wright: I'll take that silence as we're all good and everybody's communicated everything they need to communicate. again much appreciated everybody's participation in joining today's call these steering committee's meet monthly on the last Thursday of each month, please take a look at Discord where you can get involved in various things and working groups. There's a calendar that you can see in GitHub where you can add yourself to any of the six working groups. If you want to follow along if you want to get more involved and you have need help adding things to your calendar, feel free to reach out to myself Huey or other members of the Vanguard inside our community so they can direct you. But again, + +Tyler Wright: Let's appreciate everyone's participation and all the various six and working groups hoping for again with all the momentum around 2024 and around Akash Ai and all the things that we're going to be doing. Really hoping that more people continue to get involved. There's been a year of this open framework. There's been so many success stories for 2023. So hoping that just is a Snowball Effect and just continued to roll down hill with just more people getting involved more people just building on the network. So I see something in the chat for end user experience. + +Tyler Wright: That's a maybe you can bring that to Sig design to start and then we can see if we need to create another Sig dcnorse. I'll reach out to you offline to start a conversation around that because I think that's very interesting. There's also a new user group that I think has got a little bit of traction as a recently around video games. I know a number of people run Minecraft servers on Akash and enjoy a number of other video game related efforts. So if anybody's interested in video games and using Akash, feel free to join that User Group, which is in Discord. + +Tyler Wright: There's other topics dcnorse. I appreciate you bringing that up and Thank you everybody for their participation today. I'll follow up with notes transcript and recording for folks over the next day or so. And again, if anybody has any questions about anything get involved in Discord get involved in these discussions, make your voice heard what things go on chain and vote join a cig and a working group. There's so many ways to get involved, look for a bounty. So, please please look to get stay involved. And if you have any questions concerns, feel free to reach out to myself or anybody from the vanguards admin or insiders and we'll direct Hope everybody has a great rest of their day. Thank you all again. Talk soon. Goodbye. + +Cheng Wang: Thanks, everyone. + +Meeting ended after 00:45:21 👋 From 63665075874ffe952da8a5aa3c38ee61cb22b21b Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Mon, 12 Feb 2024 13:53:21 -0500 Subject: [PATCH 005/138] steering-committee Update README.md add meeting links for January 2024 meeting Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index 5ccffebe..97d5064e 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -25,7 +25,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, September 28, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/009-2023-09-28.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/009-2023-09-28.md#transcript) |[Link](https://bw2dirmu4darmwcx74o24hzfkjzs7f33grrc5rdihgysff4kxyta.arweave.net/DbQ0RZTgwRZYV_8drh8lUnMvl3s0Yi7EaDmxIpeKviY) | Wednesday, November 1, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/010-2023-11-01.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/010-2023-11-01.md#transcript) |[Link](https://4yrnmjlm3nco2ccfkbkv67s6cfgvgrge7op5dfwnv6gn46mueqxa.arweave.net/5iLWJWzbRO0IRVBVX35eEU1TRMT7n9GWza-M3nmUJC4) | Thursday, December 07, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md#transcript) |[Link](https://k6mud4r2ua6xarj6c5zqtkxw6fzjrvzjzu6eotsyhsmotles2gaq.arweave.net/V5lB8jqgPXBFPhdzCar28XKY1ynNPEdOWDyY6ayS0YE) -| Thursday, January 25, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, January 25, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md#transcript) |[Link](https://uh4qrdp5wsvzihnnh7m7conzwkllrei4xawnfsohgjmp5qpjberq.arweave.net/ofkIjf20q5QdrT_Z8Tm5spa4kRy4LNLJxzJY_sHpCSM) | Thursday, February 29, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, March 28, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, April 25, 2024 11:00 AM PT (Pacific Time) | | | From b6cac4b9e3af2797865d6a96ecf1638751371e27 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 14 Feb 2024 08:38:58 -0500 Subject: [PATCH 006/138] sig-design Update README.md updated scheduling for Feb 2024 meeting Signed-off-by: Drinkwater --- sig-design/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-design/README.md b/sig-design/README.md index 0af3aa2f..59f5ccfc 100644 --- a/sig-design/README.md +++ b/sig-design/README.md @@ -28,7 +28,7 @@ date: 2023-1-09T00:19:20-08:00 | #11 | Wednesday, November 08, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/011-2023-11-08.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/011-2023-11-08.md#transcript)| [Link](https://mctlnmdevhysanes52tbok6kbc3mgbsgnn6qemc35xhanfc2x67q.arweave.net/YKa2sGSp8SA0ku6mFyvKCLbDBkZrfQIwW-3OBpRav78) | #12| Wednesday, December 13, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/012-2023-12-13.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/012-2023-12-13.md#transcript) | [Link](https://une76rieq3cvbtrnjv3gxaw6kbxaay3tnzqsangya2lfe6ionpva.arweave.net/o0n_RQSGxVDOLU12a4LeUG4AY3NuYSA02AaWUnkOa-o) | #13| Wednesday, January 10, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md#transcript) | [Link](https://zao4urnjuqb6ncx2vacwjuqiyqnucl2ifcfm33blijhw6v6owzla.arweave.net/yB3KRamkA-aK-qgFZNIIxBtBL0gois3sK0JPb1fOtlY) -| #14| Wednesday, February 14, 2024 08:00 AM PT (Pacific Time) | | | +| #14| Wednesday, February 21st, 2024 08:00 AM PT (Pacific Time) | | | | #15| March, 2024 08:00 AM PT (Pacific Time) | | | | #16| April, 2024 08:00 AM PT (Pacific Time) | | | | #17| May, 2024 08:00 AM PT (Pacific Time) | | | From 177b9a8a7e0b5c9102b7e3240984fdb416691a5c Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Fri, 16 Feb 2024 23:37:22 -0500 Subject: [PATCH 007/138] steering-committee Update README.md update schedule for meeting Table. February 29th, 2024 meeting is being moved to March 7th, 2024 Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index 97d5064e..23b0a565 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -26,7 +26,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Wednesday, November 1, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/010-2023-11-01.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/010-2023-11-01.md#transcript) |[Link](https://4yrnmjlm3nco2ccfkbkv67s6cfgvgrge7op5dfwnv6gn46mueqxa.arweave.net/5iLWJWzbRO0IRVBVX35eEU1TRMT7n9GWza-M3nmUJC4) | Thursday, December 07, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md#transcript) |[Link](https://k6mud4r2ua6xarj6c5zqtkxw6fzjrvzjzu6eotsyhsmotles2gaq.arweave.net/V5lB8jqgPXBFPhdzCar28XKY1ynNPEdOWDyY6ayS0YE) | Thursday, January 25, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md#transcript) |[Link](https://uh4qrdp5wsvzihnnh7m7conzwkllrei4xawnfsohgjmp5qpjberq.arweave.net/ofkIjf20q5QdrT_Z8Tm5spa4kRy4LNLJxzJY_sHpCSM) -| Thursday, February 29, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, March 7th, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, March 28, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, April 25, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, May 30, 2024 11:00 AM PT (Pacific Time) | | | From 5f4eac8f8953bd6f710fe90c2d850df80c18568f Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Fri, 16 Feb 2024 23:41:28 -0500 Subject: [PATCH 008/138] sig-clients Update README.md update the meeting schedule sig-clients meeting #13. Meeting has been moved from feb 21st, 2024 to feb 22nd, 2024. Signed-off-by: Drinkwater --- sig-clients/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-clients/README.md b/sig-clients/README.md index b7ad00b3..f69e7ba3 100644 --- a/sig-clients/README.md +++ b/sig-clients/README.md @@ -45,7 +45,7 @@ The goal of this SIG is to foster a community around each of these clients that | #10 | Wednesday, October 18, 2023 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/010-2023-10-18.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/010-2023-10-18.md#transcript) |[Link](https://yofgxnfxaqk4jruuwko7pyrfckw27dtg5thp6c6bv2sfvfq66jla.arweave.net/w4prtLcEFcTGlLKd9-IlEq2vjmbszv8Lwa6kWpYe8lY) | #11 | Monday, December 18th, 2023 08:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/011-2023-12-18.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/011-2023-12-18.md#transcript) |[Link](https://msr577epylf5qgo6aexm2xbblsreurfi2pgy5ed5ssdw6ztgkxwq.arweave.net/ZKPf_I_Cy9gZ3gEuzVwhXKJKRKjTzY6QfZSHb2ZmVe0) | #12 | Wednesday, January 17, 2024 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/012-2024-01-17.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/012-2024-01-17.md#transcript) |[Link](https://75iuscsrjioekyahvk6vad3taa5ikpweibvxs2rf4amjvzvj6gfa.arweave.net/_1FJClFKHEVgB6q9UA9zADqFPsRAa3lqJeAYmuap8Yo) -| #13 | Wednesday, February 21, 2024 10:30 AM PT (Pacific Time) | | | +| #13 | Thursday, February 22nd, 2024 09:30 AM PT (Pacific Time) | | | | #14| March, 2024 10:30 AM PT (Pacific Time) | | | | #15| April, 2024 10:30 AM PT (Pacific Time) | | | | #16| May, 2024 10:30 AM PT (Pacific Time) | | | From ac0271c4488bce5a7b5c6901d068a5b7b443cd44 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 27 Feb 2024 14:48:58 +0000 Subject: [PATCH 009/138] Create meeting notes for Sig-documentation #13 (#481) * Create meeting notes for Sig-documentation #13 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 013-2024-01-23.md add transcript Signed-off-by: Drinkwater * Update 013-2024-01-23.md add recording Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-documentation/meetings/013-2024-01-23.md | 410 +++++++++++++++++++ 1 file changed, 410 insertions(+) create mode 100644 sig-documentation/meetings/013-2024-01-23.md diff --git a/sig-documentation/meetings/013-2024-01-23.md b/sig-documentation/meetings/013-2024-01-23.md new file mode 100644 index 00000000..6a5c92d3 --- /dev/null +++ b/sig-documentation/meetings/013-2024-01-23.md @@ -0,0 +1,410 @@ +# Akash Network - Docs Special Interest Group - Meeting #13 + +## Agenda +- Update on Documentation. +- Next steps for documentation. +- Updates on ongoing website revamp. +- Discussion on documentation contributions from community. +- Discussions on Video Documentation. + +## Meeting Details +- Date: Tuesday, January, 23 2024 +- Time: 7:00 AM PT (Pacific Time) +- [Recording](https://ggtsa72sjsvu3yph245qmj6zvpy7uyys7jerkj72heitmyoiv2na.arweave.net/Macgf1JMq03h59c7BifZq_H6YxL6SRUn-jkRNmHIrpo) +- [Transcript](#transcript) + +## Participants +- Andrey Arapov +- Benjamin B +- Joao Luna +- Mayank Choudhary +- Rodrigo Rochin +- Scott Carruthers +- TG (Thomas Greco ) +- Tyler Wright + +## Meeting Notes +### Tyler Wright +- Tyler Wright welcomes everyone to the first SIG Documentation meeting of 2024, extending New Year wishes to all. +- Discuss current documentation updates and encourage community involvement due to limited capacity within the core team to maintain documentation. +- Emphasis on seeking contributions from community members, insiders, vanguards, etc. +- Proposal to introduce rewards for documentation contributions, considering bounties for specific items. +- Acknowledgment of ongoing changes to the revamped website impacting documentation. +- Encourage community members to contribute new documentation for the revamped website through a dedicated section, ensuring it's back-ported to the current website. +- Assistance available from Tyler for those needing help with documentation suggestions or contributions. +- Shared a [link](https://akash.hooman.digital/) in the chat for the ongoing website revamp. +- Current documentation led by Scott with contributions from the community. +- Updated structure for the sidebar from working group docs 2.0, influenced by Luna. +- Shared link to engineering documentation by Scott Carruthers for in-depth Akash Network understanding. +- Encouraged members to check the revamp website for a preview of the documentation's look and feel. +- Welcomed suggestions for page optimization; encouraged posting in the website revamp or sig documentation Discord Channel. +### Video Content Plans by Thomas Greco +- Thomas Greco shares plans for creating video content, aiming to discuss specific content with Zach and other community members. +- Thomas updates on his video content creation, acknowledging a delay due to documentation finalization concerns raised by Tyler. +- Thomas mentions creating an initial video demonstrating the deployment of a Next.js app, awaiting feedback before proceeding with more content. +- Tyler appreciates Thomas's efforts despite the delay caused by the website revamp, suggests sharing the video in SIG Documentation or Insiders Channel for initial feedback. +- Tyler and Thomas discuss the strategy for finalizing and circulating the videos once completed, acknowledging alignment on the approach with Scott's feedback being beneficial. +- Tyler expresses gratitude for Thomas's efforts and anticipates the positive impact once the videos are finalized + +### Thomas Greco: Migration and Documentation 2.0 Feedback +- Thomas mentioned ongoing rebranding of Cloudmos to Akash Network console. +- Inquired about the completion status of the migration. +- Tyler confirmed the ongoing status, with certain functionalities still in progress. +- Thomas expressed satisfaction with the Documentation 2.0's appearance but plans to review it in detail. +- Offered assistance and a second set of eyes for feedback on flow or any specific areas needing attention. + +### Community Involvement in Documentation +- Tyler emphasized the community effort in updating documentation. +- Encouraged members, including Thomas, to contribute to documentation optimization, copy updates, and more. +- Highlighted the goal of having Scott and Andrey focus on high-level review and merging PRs. +- Scott clarified his role, stating he is more involved in writing and updating documentation rather than restructuring Docs 2.0. +- Advised Thomas to provide structure feedback to Tyler and content-related feedback to himself. +- Suggested using the Discord Sig Documentation Channel for communication. +- Tyler urged participants to consider ways to help with documentation, including editing and identifying gaps. +- Mentioned the plan to create a list of documentation improvement areas and introduce bounties. +- Encouraged community members to contribute suggestions for potential bounties and pricing structures. +- Emphasized the need for setting the tone and initiating the work in defining the pricing structure. + +### Documentation Management and GitHub Process: +- Thomas inquired about the process for content modification and GitHub PRs. +- Tyler explained the absence of an open issues list for Sig Documentation. +- Tyler suggested starting by suggesting items in the Sig Documentation Discord Channel. +- Tyler shared plans to link the repo inside the revamped website for documentation updates via PRs. +- Encouraged updating documentation in the website revamped repo while waiting for the revamp to go live. +- Mentioned the need for documentation on AMD GPU support on the Akash Network. + +### Documentation Updates and New Content: +- Tyler inquired about any new documentation or edits from Scott and Andrey. +- Scott mentioned a community-contributed PR regarding subquery integration for indexing Akash Network attributes. +- Scott identified the need for documentation on GPU provider build, specifically for AMD, as the next significant addition. +- Scott Proposed collaboration with Tyler on splitting the tasks for documentation creation. +- Andrey highlighted the raw format of AMD documentation as comments in GitHub. +- Andrey mentioned existing issues, such as GPU account degradation with mixed GPU vendors, needing resolution before finalizing documentation. +- Discussed potential challenges, including issues with deploying Jupyter containers and locating GPUs for AMD. +- Andrey emphasized the need for a global consensus and addressing outstanding issues before shipping AMD documentation. +- Scott clarified the stance on mixed AMD and Nvidia support on a single Kubernetes worker node, stating it's currently not supported. + +### Hardware recommendations documentation +- There is an existing document with some guidance for hardware recommendations for Akash providers, but it has some problems with the structuring. +- Rodrigo mentioned the importance of updating the experimental build examples section in the documentation. +- Rodrigo acknowledged Shimpa's efforts in revamping the rough draft for Hardware Recommendations, expecting a more finalized version soon. +- The draft will be reviewed by others and then added to the documentation. +- Scott highlighted the community's role in maintaining such documentation over time. +- Suggested that the Providers channel in Discord has become more design-oriented and discussed the idea of separating it into provider design and provider troubleshooting or potentially adding a hardware-specific channel. +- Andrey and Rodrigo agreed with the idea of creating separate channels for hardware-related discussions. +- Tyler supported the idea and proposed discussing it in the Sig Providers meeting. + +### Other matters Discusssed +#### Mixed GPU Vendor Support and AMD Documentation: +- Scott reiterated the current stance of not supporting mixed vendors on a single host, emphasizing the need for clarity in documentation. +- Andrey highlighted considerations for AMD deployments, including the need for additional software and potential challenges in obtaining a "golden image" for AMD. +- Mentioned creating a question in the AMD device plugin repository but awaiting responses. +- Tyler expressed gratitude for Andrey's perspective and suggested discussing these issues during the Engineering sync. +- Tyler emphasized the importance of prioritizing experimental documentation for AMD, allowing the community to provide feedback on the user experience. +- Andrey agreed to proceed with prioritizing documentation for community testing, even if in an experimental state. + +### Closing Remarks +##### Tyler wright +- Thomas committed to creating more videos, with plans to share them in Discord for real-time feedback. +- Tomorrow's Sig Providers meeting will delve into the discussion of creating a provider hardware channel and include a presentation on an open-source auditing tool by Benjamin. +- Continued work on the AMD support documentation with the aim of sharing it with the community for feedback and optimization. +- Ongoing community involvement encouraged for reviewing current documentation, providing feedback, and contributing to the evolving structure and content. +- The mention of Shimpa sharing documentation on builds with Scott, indicating imminent updates. +- Tyler expressed appreciation for everyone's time and contributions. +- Encouraged inviting others interested in documentation to join meetings and Discord discussions. + +## Action Items +- Thomas to share video content in Sig Documentation or Insiders Channel for feedback. +- Tyler to gather feedback on the ongoing migration status bt cloudmos and provide updates in future meetings +- Tyler to share the repository link for documentation updates in the Sig Documentation Channel. +- Documentation on AMD GPU support on the Akash Network to be added to the website revamped repo. +- Scott and Andrey to address outstanding issues with GPU provider documentation and seek consensus before finalizing. +- Further discussion on AMD GPU support and documentation in the engineering sync. +- Shimpa to provide a more finalized version of the Hardware Recommendations documentation. +- Discussion on channel separation to be brought up in the Sig Providers meeting + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to Sig documentation. This is the first state documentation meeting of 2024. So again, Happy New Year to everybody. During the Sig documentation monthly meetings. The group comes together to discuss all current documentation folks talk about documentation Updates. This is a Sig where we're looking for more contributions from members of our core team have limited capacity to continue to maintain + +Tyler Wright: the documentation amongst a number of other responsibilities. So this is something that we're certainly hoping that the community members of the community insiders vanguards Etc and get more involved we're looking to put rewards around this. So again, anybody wants to contribute to documentation. Feel free to share any ideas in state documentation channel on Discord and we can start creating bounties for certain items. I know right now. We're in the midst of a little bit of limbo around the website with some changes being made to the revamped website right now, which have to effect on documentation because the docks are being moved from network slash documentation or slash doctor rather. + +Tyler Wright: What I would suggest in the meantime and I've already talked to the folks that are managing the website revamp as well as they help to manage the current website as a part of the community. Bounty is have folks contribute if they have any new documentation that needs to go on the website and this goes for community members specifically, I would ask that you put it inside of the website revamp o. There is a specific section for docs and you can follow the instructions on how to access it. And then from there it will be back ported to the current website while we wait. But again, these are things that I can help folks with offline if anybody has any suggestions for documentation that they want to see added subtracted or + +Tyler Wright: 12 meeting of the year the group really went over I guess some of the items that I was talked about today next steps for the documentation again, I'll share a link in the chat for folks right now for the website revamp and the structure and the setup obviously can continue to improve but on that docs page you can see a culmination of the current documentation that again has been led by Scott and now is like getting contributions from other people in the community if an updated structure for the sidebar that came out of working group docs 2.0 that Luna was heavily instrumental in + +Tyler Wright: as well as a link to the engineering documentation, which is an effort that Scott Carruthers had been doing basically by himself to have more in-depth documentation for folks that are looking to build on top of Akash or looking to understand the accost Network at the deeper level. So again on the current revamp website, you can kind of get a look at to what the documentation will look and feel like over time. If anybody has any suggestions on optimization for this page again, feel free to drop those inside the website revamp. You can make an issue or you can start a conversation in safe documentation Discord Channel and You can go from there. + +Tyler Wright: Other than that, I know that Thomas who's on the call here today had some plans to create some video content and talk to Zach and other members of the community about specific content so we can talk about that. I know that we also had to have as an agenda item, but usually talk about any new documentation that may have been added in the past couple weeks. I know that again we've been in kind of a holding pattern the past couple weeks, but usually that's something that gets covered during these monthly meeting calls. And then again, we can open it up to the floor if anybody had anything else that they want to specifically discuss that hasn't been discussed related to documentation. + +00:05:00 + +Tyler Wright: cool What? + +Thomas Greco: Yet and I'd love to chime in regarding. + +Tyler Wright: Yeah, absolutely. + +Thomas Greco: Yeah. Happy New Year. first and foremost everybody glad to be back. + +Thomas Greco: So yeah, we can lift off. It was a little bit of a guy they can in between state with the documentation. + +Thomas Greco: You just kind of means that exact and I were. Trying to figure out a plan. + +Thomas Greco: For it's using my time. wisely and specifically + +Thomas Greco: That meant not filming any. Videos of me going to the documentation until it was all finalized. tie you and I spoke kind of on the side and you expressed just a need for videos in video content + +Thomas Greco: and so is a fair share that still and ask + +Tyler Wright: Yes. + +Thomas Greco: alright, so I've been kind of tied up with other projects. It's and the beginning of this year. But as I mentioned on the Thursday's call. I spent together. + +Thomas Greco: an initial video showing deploying and xjs app just like the basic, Bare Bones like baby step video + +Thomas Greco: and some happy to share that I was really kind of waiting to get feedback too from people on my initial video in the format of the videos, but it seems as though no news is good news, and I'm just gonna go forward with it. + +Thomas Greco: Yeah, so yeah in terms of video content. I think over these next few days. I will. + +Thomas Greco: You'll be kind of getting. Some videos from me. + +Thomas Greco: Showing the Akash console. He's deployments. Going to that process. I won't be showing the docs specifically I'll be waiting until the docs are done. to show them and so yeah, let me know. That sounds good. + +Tyler Wright: Beautiful for me. That sounds great. I know that the process has been slowed a little bit by this website revamp being in a little bit of delayed in the launch, especially because there's a couple of critical elements in terms of endings and just the back end structure of it so apologies, but I know that the working group for a cash website and Sig designer working hard to figure that But in the meantime Thomas, yeah, I think some content would be great. I know that Scott gave feedback on their original video maybe a little bit about Pace. I'm sure other people gave you a little bit of feedback as well. But I think you should continue moving forward as you have and maybe drop a video in sync documentation or maybe even insiders Channel as well to get some initial feedback and… + +Thomas Greco: Yeah. + +Tyler Wright: that might be a great place to start and then once it's finalized then I'm + +Tyler Wright: exact will have a strategy on where we can put it and how we can circulate it a wider if we just create some blog around it in the meantime or what the case may do. So I really appreciate those efforts and I think they'll go a long way once they're finalized. + +Thomas Greco: Yeah, no problem and yet wearing Scott's feedback that those. Really useful, so thanks again for that. + +Thomas Greco: It's clear that we're definitely the same page for kind of. what? We think the best. Approach to these really are so yeah. I'm excited for that. + +Thomas Greco: I do have another migration that's happening has been from cloud most to that Akash Network or Not sure if I get the ordering on there like cash console that Network. But is that right? + +00:10:00 + +Tyler Wright: Yeah. + +Thomas Greco: Is that migration done? + +Thomas Greco: but + +Tyler Wright: No, that migration is ongoing so I believe there is. network where you can deploy the Akash console beta which is cloud most back-end. but it does not have the full functionality of cloud most and… + +Thomas Greco: but + +Tyler Wright: I believe that is still ongoing. There's an item that's in the road map. + +Tyler Wright: But yeah, the max are so working on that so you won't get the full functionality of the cloud most app. + +Thomas Greco: I + +Tyler Wright: At console, but you'll get a lot of it and they'll get The Branding element. + +Thomas Greco: okay, go so it's cool to use that and all right awesome and… + +Tyler Wright: Yes. + +Thomas Greco: then the last thing I mentioned was that. But the documentation 2.0. I think it looks really great. + +Thomas Greco: I haven't really got the sift through it in detail. And so that's definitely something I put on my list of things to do, but I just Area if you need the second set of eyeballs on anything. or would just like me to check out the flow of things. whatever area might need assistance don't hesitate to reach out because yeah, I know that can go a long way. + +Tyler Wright: I don't think I'll speak for Scott and Scott can feel free to chime in but one of the hopes of this sig documentation is to get more folks like yourselves that are interested in contributing to documentation and can so that Scott Andre and other members of the kind of core team. They're working on a number of things like teacher editions, just like new products can focus on that and are basically just reviewing at the highest level some of this stuff. I know that Scott again has spent a great deal of effort as Andre and particular time to optimize specific documentation and think about the flow and participate a number of meetings. But as we move forward the goal is that + +Tyler Wright: Scott and Andre can be at this meeting can give feedback. But in between these meetings as much of it's very much a community effort on updating documentation working together to make sure that the flow is optimized updating any copy if it needs to be updated directly and then all Scott and potentially Andre are doing is just like merging PRS and it's just our Been effort so I apologize if I'm speaking on behalf of you, but just want to put + +Scott Carruthers: I think all that is fair and maybe one additional plane of clarification is I'm not really overly involved and they restructuring of document documentation 2.0. So I'm still definitely very involved and writing new documentation are updating existing documentation, but just based on assignments and focuses. I haven't really been to involved in. the Threshold just restructuring of the docs 2.0. So Thomas I would recommend I guess I would say two things. If you have any feedback on this structure of ducks 2.0. I would probably just feed that to Tyler and then Tyler can. distribute that to the people that are working on those efforts or the necessary parties and then if there was feedback on actual + +Scott Carruthers: Content of documentation if you get into a provider documentation and believe that's something should be clarified, then you can definitely bring that to me. So I'd say structure Tyler and then content you can bring to myself. + +Thomas Greco: Okay, and then I mean, I'll probably just use the diet cig documentation Channel. + +Scott Carruthers: Yeah, yeah, that's fine. Yeah, just leave it there and then whoever is assigned or responsible. I'll pick it up from there. So yeah, that's fine. + +Thomas Greco: cool, definitely want to take as much stuff off your guys's Place possible, free Epson bandwidth + +Tyler Wright: Much appreciated and again, especially over the next month or so. I would like participants in this group to start to. Think more about ways that they can help with documentation, whether it's like editing current documentation or gaps whether it be in the sdl. I know Benjamin I talked about that previously gaps that users may be stumbling across that maybe we be able to optimize I would like to start to + +00:15:00 + +Tyler Wright: pray, a list of what those things might be get contributions from folks in the community and have suggestions on a potential Bounty so we can start to put together a board and kind of like a structure that makes sense for everybody of what an edit should cost what a new document should cost so that we can start to figure out next steps in terms of the operational component of Again, incentivizing folks to continue to contribute to documentation. So I'm hoping that folks on this call that are involved right now can really Step Up in setting the tone and doing the work and studying kind of the initial ructure of what a pricing structure might look like. + +Thomas Greco: yeah, okay, that's a good and so just the GitHub just make for content and modification there Edition that process is just like PR is to GitHub Aries. What I'm trying to get at is there a list of open issues or anything? + +Thomas Greco: and githubers project + +Tyler Wright: There's no list of open. + +Tyler Wright: There's no list of open issues right now for the Sig documentation. And in terms of order of operation when I would suggest is start by suggesting items in Sig documentation Discord Channel. And then from there we can start to finalize where items should go. I will link specifically the repo inside of the revamped website where things should be because This will be the place where all documentation will be updated via PR. I'm going to link that to everybody in six documentation after this call with some readme instructions from the website team just on how folks can update documentation and then my suggestion is while we're waiting for the website revamp Continue to update. + +Tyler Wright: A documentation in that website revamped repo and then anything that's really pressing will get back ported manually by a member by either Peterson his team or a member of the core team to the current documentation docs out of network. as an example, and I hate to put some folks on the spot, but I know that Scott and Andre have been extensively testing. AMD support as a GPU type on the Akash Network. I believe that a Next Step would be creating documentation that we can add to the + +Tyler Wright: Docs for folks that are trying to use AMD gpus I'm going to cost Network. We should probably put that on the current website right now because again, I think it will live fairly soon, but we can add it to the website revamp repo and then I'll make sure it gets back towards. + +Thomas Greco: Yeah. Yeah sure That'll be useful which is quite a bit to sift Between overclock too and a cash Network. but specifically + +Tyler Wright: I'll share that repo in. + +Tyler Wright: and sick documentation + +Tyler Wright: real quick. Can we take a brief aside to quickly put a laughing emoji at Rodrigo being a Dallas Cowboys fan. cool + +Thomas Greco: I was actually gonna chime in and say I'm a die-hard Cowboys fan. So I'm gonna have to veto that. + +Thomas Greco: Okay. + +Tyler Wright: There's a number of people we can laugh with prilo this call. + +Thomas Greco: What's up existence? + +Tyler Wright: You want a top existence? Yeah. Cool is anyone. + +Scott Carruthers: Whether it's Sorry for additional side. + +Tyler Wright: Go ahead. + +00:20:00 + +Scott Carruthers: But Broadway is saying that I sound like I'm from Texas. I've never Rotary, that's the first time that anyone has told me that do really do I sound like I'm from, Texas. Because I don't mind that but I've never heard that. + +Rodrigo Rochin: I just moved I think you have a western accent, but I really like it. I dig it. And I figure like you and… + +Scott Carruthers: Yeah, no, I'm from you. + +Rodrigo Rochin: your spare time. You probably wear a cowboy hat in boots, or I don't know. Maybe you're from I don't know but + +Scott Carruthers: No, I'm from. + +Rodrigo Rochin: I really like it. + +Scott Carruthers: All yeah, that's no I'm actually from New York. So I don't know where the Western accent is coming from. But yeah, I'm down with it and… + +Thomas Greco: I mean he had time + +Scott Carruthers: And growing up in New York state. ironically I'm a Cowboys fan as well. So I don't know how that happened but sounds like it's all coming together perfectly. + +Tyler Wright: Yes, Exactly. + +Thomas Greco: Yes, got it. + +Andrey Arapov: Maybe from the past life. + +Scott Carruthers: Yeah. Yeah. + +Rodrigo Rochin: Yeah, I don't know why I just thought you were Western from I don't remember the states of up, Texas, but somewhere in the south. + +Scott Carruthers: Yeah, no,… + +Rodrigo Rochin: But very imagined that you were from,… + +Scott Carruthers: that's a yeah, I mean. + +Rodrigo Rochin: New York. + +Scott Carruthers: Yes, I'm not from the city. So yeah, I definitely don't have the Long Island accent. But yeah, I'm from New York state. But yeah, I'll take the Western accent. I've been told before that I sound like I have a computer generated voice and I sound like Darth Vader. So in those options, I'll take a look. + +Tyler Wright: cool All right. + +Tyler Wright: Does anyone have any documentation or I guess specifically Scott and Andre because I know between last meetings you all. I've been working over things and I'll been break. Is there any new documentation or documentation edits, that might be worth sharing with focus on the call that it + +Scott Carruthers: Okay, if I need to come to mind, so we had a request subquery to their doing some indexing of Akash Network attributes or cost network data, so they submitted a PR and I merge that so that's in Integrations now, so that's a document created by the community. It's obviously been a long time since we did our last Sig documentation. So I bet I would assume that there probably were some small documentation edits, but none of any significance really come to mind something. They come to Andy's mind. So yeah, really the subquery document document Edition is really the only thing I can think of and Tyler to your point that certainly then next document of significance that needs to be added is the + +Scott Carruthers: GPU provider build Andy we obviously can Take this offline, but wonder if we want to split that up. If you want to go through based on your build of the AMD provider on circus scale if you wanted to. kind of divide this up if you wanted to take some of the scaffolding of another way it needed to do this on circuit scale, but obviously another + +Scott Carruthers: bare metal machines will have to go through the install of the + +Scott Carruthers: AMD drivers and then also some guidance on Using rock them or rocm. It's me instead of Nvidious me so we could go through all that in a documentation. So yeah, I'll take this opinion on this and even maybe something that we could work on together this week, but maybe you could go through some of the scaffolding of that and then I could take some of the bare bone structure and turn it into documentation for the documentation site. And yeah, I think that's really the only items that come to my mind. + +Andrey Arapov: Yeah, thanks, but for MD, I think the documentation we kind of have it in a very role format is a form of comments in GitHub that we can copy paste stuff into the official recommendation. But the global thing is that the major issue there is if you can see in the support repo issue number 142 there are there a few things that they like in degradation of the GPU account when you have mixed GPU vendors and medium D on the single host things so yet to be fixed before pushing the recommendation I would say, but I know if people want to have it ship this as fast as possible, even if it's like we'll say in the working way, but + +00:25:00 + +Andrey Arapov: In this specific condition where you have a single per host, then it's fine with me. But other than that, I would prefer rather like to make sure that the provider has this issue fixed first, and there are a couple of more things. Such as when somebody deploys something with the jupyo, if he spawns into the port container, he needs to install specific software to locate the GPU to actually work with it, but + +Andrey Arapov: drivers and stuff like that because these things are getting through the pot by default with a media in immediate review but not with So you need basically to find something to run on AMD and see how painful it will be for the customer because if we ship it this way, then it might be painful for my point of view. Other than that and if everyone is okay with that, I'm fine to ship it this way, but we need to find the global consensus first and only then we should go with the documentation for AMD. Let's try and take + +Scott Carruthers: Yes, I Andy I just to let you know and we can take this up and Engineering sink as well. But we have the once significant issue that you just raised of mixed AMD and video support on a single. Kubernetes worker node. So we talked about that last week and our stances that's not currently supported. So just as we don't currently support end video Gpus,… + +Andrey Arapov: Yeah, fine fine. + +Scott Carruthers: I'm just say most yes. + +Andrey Arapov: Yeah, I remember this conversation. I just want to like to iterate again. Okay. + +Scott Carruthers: Yeah, yeah, so that and we would obviously very clear. It's called us out in the documentation as well. But yeah, the current stances. We do not support mix vendors on a single host. + +Andrey Arapov: Yeah the time and the other thing is that to make sure when you customer creates a deployment in Akash for AMD. He might figure that he needs to install some additional software or just basically get some kind of let's say quote unquote golden image for AMD image Docker image. So it contains all these drivers because there's difference between the plugin the VR is for NVIDIA Whereas in Nvidia device plugin in automatically supports the future and basically mounts over from the host to the pot the directories in the drivers for accessing the immediate GPU and for AMD, you basically need to install specific drivers or have software that already has the driver so to + +Andrey Arapov: so that you are able to basically communicate with the AMD card but generally MD card gets through the container without any problem as a device under a slash dri. So it's all about the usability I would say right now. I've created the question in the issues of the AMD device plugin repository for their developers. And I think I still haven't received any information on that yet. There's a possibility that we also try to look for different kind of plug. And that supports AMD and supports all these things out of the box or in the worst case. We'll have to contribute to In the code, is this extensions and I'm actually not sure how much work would be required there. But I think it's quite extensive so it's for information. + +Tyler Wright: Andy I appreciate that perspective, it's Scott mentioned we can talk about some of the stuff during the engineering sink specific to this issue. I would just say generally if we can prioritize even if it's an experimental State, I know that there's some folks in the community that have AMD gpus and I would just like them to be able to test out General documentation. Even if there's some limitations right now, but I would just like them to test out the process so we can get some Community feedback on some of the things that you're talking about whether it's user experience or onboarding experience or whatever. So if we can be one of documentation for and… + +00:30:00 + +Andrey Arapov: Yeah, Sounds good. + +Tyler Wright: David go from there. + +Andrey Arapov: Sounds good. + +Tyler Wright: Excellent life, cool. Thank you Andrey. Is there any other? Specific documentation that anybody is seen or anybody on the inside of the vanguards are part of the community has seen people in the community get hiccup on or stuck on or anything that anybody has any suggestions on improving in terms of documentation. + +Tyler Wright: Go. + +Rodrigo Rochin: So we talked about this in the Bangor Channel or insiders channel, the experimental build examples there in there. chimpa said and recommended there's always gonna be new hardware being released. and I think he said that he would happily edit them. I'm not familiar with the best hardware for built. But I think that section is very helpful. I presented it to some of the people asking about building providers and Discord, too. And let them know that it would be updated. So not sure if she is here who could keep that updated, but I think it would be really helpful for all of us. + +Scott Carruthers: yeah, so ship is not currently here, but he actually shared a rough draft and these are shrimpas words. It was a very rough draft, but I thought a lot of the content in the direction he was going with or were great so + +Scott Carruthers: Yes, so we know that for a while there's been a document and experimental with some guidance for Hardware recommendations for a cost providers. And we thought there was a lot of polls and problems with the structuring so ship but took on revamping that and as all documentation I would think that that would be something that would be maintained by the community over time because that was another issue with the existing document as obviously hard work can become outdated and that kind of documentation could take a lot of love and care over time, but I think that will work very well in the community. So yeah, the update is shambo's written a rough draft for that and I would think that he would have a More finalized version that people like myself and Andy could review and then get into the documentation very soon. So not putting words in champa's mouth. But basically from what I've seen I would think that as plausible we might have that. + +Scott Carruthers: Hardware recommendation documentation up and the next couple weeks. + +Rodrigo Rochin: Thanks Alex there. I didn't know it existed until two or three weeks ago. If I had seen it before I probably would have started building one of those. + +Scott Carruthers: Yeah. I'd also say this isn't necessarily documentation related, but has some Association Any I was going to reach out to you for your opinion on this as well. I noticed recently that the providers channel in Discord is mostly full of. Conversations around this very topic like Hardware recommendations and people reaching out to others in the community asking what Hardware they use for their provider build in it seems like the providers channel has become very design oriented instead of troubleshooting oriented. And I think that the danger with that is if someone is looking for a troubleshooting topic and might start to become difficult to find past conversations or their current conversation might get muddied by a lot of design conversations. So Tyler and something that we + +Scott Carruthers: May want to consider going forward as I wonder if we'd be better start by having a provider design and a provider troubleshooting. Channel + +Andrey Arapov: Or we could have a hardware Channel Maybe. Yeah, I think it's a good point. + +Scott Carruthers: yeah, something like that. Yeah. + +Andrey Arapov: You brought up Scotty. Yeah, definitely. I agree. + +Scott Carruthers: Yeah, okay. + +Tyler Wright: I agree as well we can figure out how to make that happen. And I think we have sick providers tomorrow. So + +00:35:00 + +Tyler Wright: We can either bring that up tomorrow. Just wait a day or we can just make the change now and just talk about it tomorrow. I don't know how people feel on this call. I know some that'll be on this call also being sick providers, but does anyone from the community have any issues about separating those two channels so we can keep Channel specific to again troubleshooting provider fixes and all that kind of stuff and then a separate channel for Hardware. + +Tyler Wright: All right, figure that out and take next steps there but much appreciate you bringing that up Scott. Does anyone else have anything documentation related that hasn't been discussed? already + +Tyler Wright: I know it's an action items off follow up and share some repos on where people can specifically contribute to documentation. So that again it will live in the website revamp repo and it'll be visible in the staging site. But then again any specific documentation that needs to be added a timely fashion will get back ported to the current website while we For the website recap to happen. + +Tyler Wright: Thomas is going to spend some time continuing to create some videos and I'll share those and Discord with folks so that you can get some real-time feedback. And again we can get those shared across social and attitude YouTube or whatever Zach has in mind for him. And then again, we'll talk about the provider Hardware Channel tomorrow a little bit more detail during Sig providers. I know that as an aside Benjamin who is working on a open source auditing tool believe also be presentation providers to talk a little bit about next steps with his project. So feel free to join that conversation tomorrow as well as I'm sure continued conversations around State providers. + +Tyler Wright: and then yeah, we'll just continue to work on a B1 of the AMD support documentation that I'll be shared with folks in the community and it could be continued to be optimized over time and the community will continue to look at the documentation themselves both the current docs data Costa Network as well as again, the staging link that's available for folks and continue to get feedback on any documentation holes anything that I think can be edited. Proved Etc and we'll start to map out kind of like a Time structure and a pricing structure for rewards around more Community contributions for they cost stocks. + +Tyler Wright: Alright much appreciate everybody if there's nothing else then let you all go a couple minutes early and we can continue to talk on Discord and follow up with those action items. And again as mentioned simple has also been sharing documentation in terms of builds with Scott. So I'm sure that documentation will be available and updated very soon but much appreciated everybody's time and contributions today and we'll continue to work together offline. If you know anybody that wants to get involved in documentation and feel free to have them, join these calls or join the meeting or join the Discord so that again we can find more folks in the community that can contribute to documentation but much appreciate you all. Thank you very much. + +Andrey Arapov: Thank you very much. Thank you everyone. + +Benjamin B: Thank you. + +Scott Carruthers: That's everyone. + +Rodrigo Rochin: Thank you. + +Tyler Wright: the + +Meeting ended after 00:39:06 👋 + From c0592d759f29e6d3943722b64ae46ed99320480f Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 27 Feb 2024 09:50:47 -0500 Subject: [PATCH 010/138] sig-docs Update README.md add to table for meeting 13 Signed-off-by: Drinkwater --- sig-documentation/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-documentation/README.md b/sig-documentation/README.md index 41cc504d..79ebdecc 100644 --- a/sig-documentation/README.md +++ b/sig-documentation/README.md @@ -28,7 +28,7 @@ The goal of this SIG is to foster a community around the creation and maintenanc | #10 | Tuesday, October 24, 2024 07:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/010-2023-10-24.md) | [Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/010-2023-10-24.md#transcript) | [Link](https://j7umqwzmkiglhuckkezav7c2rbh4cirv4d2nrjophespxwsjqtxa.arweave.net/T-jIWyxSDLPQSlEyCvxaiE_BIjXg9Nilzzkk-9pJhO4) | #11 | Tuesday, November 28, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/011-2023-11-28.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/011-2023-11-28.md#transcript) |[Link](https://na7gjhjowrrxc37tzk76rixczxf4st6b3rjpfjrzktiln7yxuckq.arweave.net/aD5knS60Y3Fv88q_6KLizcvJT8HcUvKmOVTQtv8XoJU) | #12 | Tuesday, December 19, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/012-2023-12-19.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/012-2023-12-19.md#transcript)|[Link](https://w3evlgbcqz4g4b4kicipe3gxrblirj4f2czs3eutaibrqrp7xtva.arweave.net/tslVmCKGeG4HikCQ8mzXiFaIp4XQsy2SkwIDGEX_vOo) -| #13 | Tuesday, January 23, 2024 07:00 AM PT (Pacific Time) | | | +| #13 | Tuesday, January 23, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/013-2024-01-23.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/013-2024-01-23.md#transcript) |[Link](https://ggtsa72sjsvu3yph245qmj6zvpy7uyys7jerkj72heitmyoiv2na.arweave.net/Macgf1JMq03h59c7BifZq_H6YxL6SRUn-jkRNmHIrpo) | #14 | Tuesday, February 27, 2024 07:00 AM PT (Pacific Time) | | | | #15| March, 2024 07:00 AM PT (Pacific Time) | | | | #16| April, 2024 07:00 AM PT (Pacific Time) | | | From d354b9759a55506a510f2583d0c53176df7e5f14 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Wed, 28 Feb 2024 15:57:42 +0000 Subject: [PATCH 011/138] Create meeting notes for Sig-Providers #13 (#484) * Create meeting notes for Sig-Providers #13 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 013-2024-01-24.md Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 013-2024-01-24.md add transcript Signed-off-by: Drinkwater * Update 013-2024-01-24.md add recording Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-providers/meetings/013-2024-01-24.md | 377 +++++++++++++++++++++++ 1 file changed, 377 insertions(+) create mode 100644 sig-providers/meetings/013-2024-01-24.md diff --git a/sig-providers/meetings/013-2024-01-24.md b/sig-providers/meetings/013-2024-01-24.md new file mode 100644 index 00000000..cbaf2f05 --- /dev/null +++ b/sig-providers/meetings/013-2024-01-24.md @@ -0,0 +1,377 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #13 + +## Agenda +- Update from Praetor on all of the work that they have been doing. +- Discussion on Akash GitHub Discussions and Provider Review Proposal by Alani Kuye. +- Andrew Mello updates on Akash OS development. +- Open Discussion on all things related to Akash Providers. + +## Meeting Details +- Date: Wednesday, January 24, 2023 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://7jnmboxzie2zlrw5nrmwu7ddgmzxiaywbjvmbx2xpr5qmfss7s3a.arweave.net/-lrAuvlBNZXG3WxZanxjMzN0AxYKasDfV3x7BhZS_LY)) +- [Transcript](#transcript) + +## Participants +- Alani Kuye +- Andrew Mello +- Andrey Arapov +- Anil Murty +- Artur Troian +- B S +- Benjamin B +- Damir Simpovic +- Deval Patel +- Jigar Patel +- Max +- Rodrigo Rochin +- Scott Carruthers +- Tyler Wright +## Meeting notes + +#### Tyler Wright: +- Welcomes everyone to the first meeting of 2024 for the special interest group monthly meetings. +- Highlights diverse participation from various providers, including data centers, individual providers, and those with accommodations and GPUs. +- Mentions the Praetor Team's role in developing a provider build tool for easy provider creation. +- Notes Praetor Team's community pool funds in 2023. +- Updates on the Praetor Team's efforts, including support for GPU testnet, GPU mainnets, and work on content moderation. +- Announces dedicated time for Jigar and Deval to provide a high-level presentation on the team's plans for 2024 Q1. +- Benjamin received community pool funding for an open source auditor and other contributions. +- Announces the formation of a working group for community involvement in tracking Benjamin's team's work on open source auditing tools. +- Seeks community feedback and asks for objections to the working group. +### Provider-Audits Progress Update by Benjamin B +- Benjamin expresses gratitude for the working group channel and the opportunity to share information publicly. +- Outlines the plan for the open source auditing work +- Indicating a schedule until March with the actual work beginning between the half of this month and the last of this month. +- Acknowledges challenges faced by his brother, who has been dealing with environmental issues and working overtime, impacting the progress. +- Benjamin has started preparing smaller details for each system and shares that communication on the plan is ongoing via direct messages (DMs). +- Plans to share more information in the working group Discord once it is set up. +- Tyler acknowledges Benjamin's update and expresses gratitude. +- Commits to creating a working group channel for the open source auditing work. +- Tyler announces the initiation of scheduling for dedicated time on the calendar for discussions in the upcoming week or two. + +### Praetor Q1 2024 Roadmap by Jigar Patel +- Jigar Patel presents the Q1 2024 roadmap for the Praetor Team. +- Key focus areas include addressing user feedback, solving common issues faced by Akash users, and implementing requested features. +- Primary issues to be addressed: + - Enabling multiple drives in ephemeral storage. + - Providing options for custom nodes, including the ability to create nodes in a user's own Kubernetes cluster. + - Implementing a provider notification system for upgrades and important information. + - Enhancing error handling and presenting errors more informatively in the UI. + - Addressing DNS-related issues, including better handling of DNS entries and wildcards. + - Open APIs for collaborating with other teams, specifically for the audit process. + - Handling SSH connection issues with improved UI feedback. + - Integrating any upgrades introduced by Akash into the provider process. +#### Feedback and Discussion on Praetor Q1 2024 Roadmap +- Damir Simpovic offers helpful videos for setting up port forwarding, DNS, and other concepts, especially for new providers. Praetor Team expresses interest in sharing these video links for community guidance. +- Jigar clarifies that the process for Helm-based providers is essentially the same, with the only difference being the decision not to build the node inside Kubernetes, offering the option for providers to create a node if they have large enough servers. +- Anil Suggests addressing limitations for AI/ML workloads, particularly related to data downloading, labeling, and support for shared memory. +- Highlights the need for diagnostic information on GPU card temperatures, voltages, and potential overheating issues. +- Praetor Team acknowledges the feedback and expresses a willingness to investigate and contribute to these areas. +- Anil Murty expresses interest in discussing challenges faced by AI/ML developers, especially related to data downloading, labeling, and GPU diagnostics. +#### Deval Inputs +- Praetor Team expresses willingness to contribute to code libraries and investigate issues related to AI/ML workloads, GPU diagnostics, and shared memory support. +- Praetor Team discusses preliminary plans for Q1 2024 and is open to community ideas and feedback. +- Deval highlights the community's request for a UI feature to add more nodes to a single provider and discusses the challenges and considerations for expanding the roadmap. +- Deval Complaints about the fees for updating provider attributes and suggested to initiate a discussion on GitHub for further consideration. + +### Andrew Mello presents updates on Akash OS development +- Akash OS is currently under development and is powering the largest provider in production on the Akash Network. +- It is designed to be an ISO or an image that can be installed on any machine, providing Ubuntu 22.04, a Kubernetes cluster, and a default account provider installation or configuration. +- New updates include the ability to deploy Akash OS to any machine without the need for an ISO, thanks to Ansible playbooks. +- The upcoming feature, Auto Port Forwarding, will automatically configure new providers with a public domain managed by akashos.com, reducing the barrier to entry for new providers. +- The goal is to make the configuration process seamless for new users and providers, minimizing the need for technical knowledge in networking, firewall setup, and DNS record management. +- A release around the first week of March is expected, making the onboarding process for new providers more straightforward. +- Akash Dash com, where providers can monitor their earnings, is ready for a Kepler integration. +- Providers will be able to claim their account by authenticating with their Kepler wallet, enabling features such as editing the page, setting up notifications, and having an account on Akash Dash com. +- Users and providers are encouraged to try out the new updates, dive into GitHub repos, and provide feedback to improve the tools and make them production-ready. +### GitHub Discussions and Provider Review Proposal +#### Alani Kuye's Overview: +- Alani Kuye expresses gratitude and acknowledges the inspiring work of the community. +- Emphasizes the need to focus on the demand side of the marketplace and addresses challenges faced in past experiences. +- Recognizes the success in increasing the number of providers and highlights the importance of shifting focus to deployers. +- Proposes a strategic approach to incentivize deployers and align with provider incentives. +- Advocates for a low cognitive load for deployers to encourage broader participation from various personas in the ecosystem. +- Stresses the importance of simplifying the review process, drawing parallels with platforms like Airbnb and Amazon. +- Highlights the need to cater to different audiences, including system admins and executives, in the review process. +- Emphasizes the goal of keeping deployers engaged for longer periods and ensuring a seamless experience. +- Acknowledges feedback received on the proposal, addressing concerns about expenses and emphasizing the broader perspective. +#### Discussion on Hourly Rate and Feedback on Provider Review Proposal +- Benjamin B raises a point regarding the hourly rate mentioned in proposals and ad hoc opportunities within the community. +- Tyler interjects, suggesting to keep non-provider-related conversations for the steering committee meeting. +- Tyler encourages feedback specifically related to how the review process may affect providers. +- Alani Kuye provides perspective on the operational differences between incentivizing providers and deployers. +- Stresses the importance of considering the different audiences and user experiences. +- Alani urges the group to think differently and make a mental shift when addressing the needs of deployers. +- Tyler redirects the discussion to Anil, who has provided comments in the chat, and encourages further discussion offline. +### Input by Anil Murty regarding Client Discussion +- Anil Murty provides insights on building clients, targeting specific user segments, and the importance of tactically approaching customers. +- Mentions examples like healthcare clients discussed in a recent Twitter Spaces session. +- Anil suggests focusing on specific actions clients can take to drive further adoption. +- Alani Kuye acknowledges Anil's input and discusses the Twitter Spaces conversation around Solve care clients. +- Anil mentions bringing Solve Care into the Akash ecosystem and emphasizes the need for due diligence. +- Tyler intervenes, emphasizing the focus on providers during the SIG Provider call. +- Anil suggests continuing the discussion on clients in the SIG Clients call or on GitHub, respecting the agenda focus on providers. +- Tyler concurs with the redirection, urging participants to leave comments on the GitHub proposal for Alani. + +### Closing Remarks +- Tyler announces the setup of a working group channel on Discord and plans to initiate the first working group session. +- Reminds everyone of the upcoming steering committee meeting scheduled for tomorrow at 11 AM Pacific time. +- Extends appreciation for everyone's time, effort, and commitment to the future endeavors of the group. +- Invites participants to drop any further questions or comments in the providers' channel for asynchronous discussion. + +## Action Items +- Tyler to create a working group channel for the open source auditing work. +- Tyler to set up dedicated time on the calendar for discussions in the next week or two. +- Anil Murty will schedule a meeting with the praetor team to discuss specific challenges faced by providers. +- Further discussions will be initiated on GitHub to address UI improvements and reduce fees for updating provider attributes. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the first ly meeting of 2024 during the special interest group monthly meetings. The group here goes over anything related to their costs provider. Usually we have a great deal of participation for a number of different kinds of providers on the Akash Network, whether data centers individual providers some some have accommodations and gpus. So again, there's a great representation types of providers during these monthly meetings. + +Tyler Wright: In addition the prior team who is built a provider build tool on that makes it easy to build the provider. If you don't have a great deal of experience using the documentation and CLI. They also received some community pool funds in 2023 and have given updates on all the work that they've been doing as it relates to helping providers be able to build for the GPU testnet and GPU main Nets their work around content moderation and a number of other items that they've been working on in I know as we get ready for as we start 2024 we'll set out some time today for Digger and Deval from the prey to our team to give a high level + +Tyler Wright: Presentation I know they did at the end of I think November's monthly meeting. But just to give a high level of the kinds of things that they're thinking about as we start off 2024 q1. In addition Benjamin who is also I believe on this call recently received community pool funding for an open source auditor and some other open source contributions to indexer and some other items. I know that again. We're going to set up a working group that I wanted to announce here and get some Community feedback as Benjamin in his team start to work on development of the open source auditing tools. + +Tyler Wright: There's going to be a specific working group. So the community can continue to track and work very closely with Benjamin. Hen and his team. does anybody have any objections to having a specific working group for the open source auditing work that Benjamin is team have + +Tyler Wright: Or we're going to be working I'm going to set that up. And then anybody from the community that wants to participate in those working group sessions with more than welcome, and I'll add them as an to the events calendar and to the other calendars that we have for Community groups special description working groups. + +Tyler Wright: Real quick before we move on and Benjamin. I know that you are just received community pool funds over the holidays. Do you want to give a high level as we get ready to tell the working group on where you are in some quick next steps. It could be a minute or less and then we can really dive in at that dedicated working group session next week or whenever we have that. + +Benjamin B: Sure, Thanks for the word. So now that we have the working group Channel we can start to share some stuff publicly. We have a plan on what to do in for everything until March but we have the timeline between the half of this month and the last of this month to start work and my brother has been having a lot of the issues. We Face environment and has been working a lot of overtime. So we have not had the opportunity to do a whole lot yet. I have been starting to prepare a lot of smaller details on what we need to include in each system and we have a plan on how we should develop each system. + +Benjamin B: between our DMs but as soon as this working group generous don't I will share some more information there. + +Tyler Wright: Thank you min. So I have an action item that I'll create a working group channel for the open source auditing work as well as start to set up some time on the calendar for folks to live over next week or two. + +00:05:00 + +Tyler Wright: Cool real quick. I know that there are a number of discussions that are happening right now in akash's GitHub. + +Tyler Wright: So I really appreciate those that are bringing up discussions and those are participating in the discussions. If you see anything that you want to participate in again, this is an important part of the open source framework to get a community feedback. I've dropped it in there but specifically as it relates to providers and I know that Benjamin again recently received community pool funding we don't want to take a significant time, but I do want to shout out Alani who's on the call here today and is also put a proposal for a cost network provider review and incentives proposal. It's proposal number four 53, and I wanted to again I hope that we can have folks that are on this call or in the community just give feedback and get help discussions. But with Alani here live alani's if you so desire, I just want to give you + +Tyler Wright: maybe a minute or so to talk at a high level about the review proposal and maybe some of your thoughts and initial feedback that you've been getting on the discussions if you don't mind. + +Alani Kuye: You're sure and tie things were organizing these guys always get to see you all and it's very inspiring to see all the work that everyone is doing. The more importantly it's also good to see that we're still solving for these difficult problems as many of I kind of do my thing behind the scenes but I think given where we are right now, one of the things we encountered, in the past. when I run the program we solved a lot for the providers went from what eleven to almost 300 in a matter of months, thanks to a lot of your efforts in just a shout out on the pre-to-team Maxine, everyone on this call, played a role in that so I think when we give it to the other side on the demand side, I'm coming from a strategic perspective in that. + +Alani Kuye: we've solved a lot for provider side. It's easy to become a provider today in that process continues to evolve positively and it's reflected in the walk you guys are doing I think taking the demand side which is where we need to really focus and dislodging it and Tackle them differently because two sided marketplaces have two very different unique needs and of course everything happens on chain. So from a provider perspective, how do we make it easy for folks who continue to deploy when we incentivize them so I know Chang had put something up for God and provider incentives with I + +Alani Kuye: About a nine million dollar proposal or something like that. But how could we code terminally tapping to that to incentivize deployers to stay longer and that requires a very strategic approach, and that's why I'm pushing very hard to dislodge both and Tackle them are separate exercises. that way we understand all the metrics and data literacy around incentivizing deployers, but also symbiotically tapping into The provider incentives finally, which I think is even more important making the cognitive load. So low. + +Alani Kuye: That even the folks in web 2 who may not know where to start can participate because your ecosystem is not just devs and we've been solving so much for developers that we live in human beings, behind the scenes and we're not just building for us and our friends right? We're building for a much broader arm strategic audience. So everyone from students conferences Architects Executives, artists bloggers, media folks every Persona is reflected in who deploys and how do we make it easy the review process, you can't take a gunship little fist fight right the same way. We know that low cognitive load. It calls rapid adoption in high cognitive load is the other way around + +Alani Kuye: So as it is today as admitted easy for providers will continue to solve for that based on incumbency. We need to Pivot to the other side, but approach it very very differently because deployers haven't even lower cognitive look to get in and how do we do that? Make the review processes just like Airbnb or Amazon. We know there's a referral program somewhere within the ecosystem. All those things are related, but we have to dislodge both, we can lump everything into One big exercise, and I think what B is doing is fantastic, especially the audit information. Think about those who want to do due diligence and providers, especially with complex workloads, There's two audiences. There's a systems admin and there's your executive as an executive. I don't have the time. + +00:10:00 + +Alani Kuye: to go into those details so your one review was there any level two is where you go deeper into it. So we have to solve for those audiences because again time is a premium and the easier we make it the more we tap into that audience and more people have longer deployments instead of the drive by that would tend to see and as a market involves we need to be cognizant of that because you can't scale what you can't simplify and we have to Pivot and start to solve. the other side of that Marketplace which are deployers and how can we keep people deploying for longer? While making sure it Remains the medical policy and everything happens on shame. So you have to sign every transaction every way you ever wish where you put it off there. So that's my perspective. I mean always open to conversation. I've gotten everything from it's too expensive. good dance costs. I mean this isn't one person building, we have to look at this thing from a broader perspective. There's different personas that are involved in this exercise. It's not a money issue because again, + +Alani Kuye: And we're talking to wife gay, and it's gonna involve everyone most of which are on the score anyway, so it's not new territory. It's just a way to make sure that we're solving for the other side of the transaction. We're too comfortable with providers. So I want to be the bad guy to say let's start paying attention to deployers and do uncomfortable things because in my experience the things you're not comfortable doing other things that actually going to work. So let's move a little bit away from our comfort zone and do something different. + +Alani Kuye: Benjamin + +Benjamin B: Yeah, I have one thing. I tried to comment on the discussions page, but I must have closed my car. Anyways, I just wanted to speak about the hourly rate. I don't think that regardless of how big of our project this could be. I don't think it's necessarily about projecting up anyway. But I want to say that. + +Benjamin B: the most proposals and other ad hoc opportunities that have been erased within the community of either being 50 dollars per hour for the proposals and what I've seen I've also seen some hoc opportunities with up to 100 dollars per hour. So I don't think it's super weird that you're getting these comments that they already read this quite large. + +Tyler Wright: Real quick, just for the sake of time and I know there's a number of things on the agenda. I just would ask that we can keep any conversations related to anything that's non provided related in the discussions. We'll have some time to talk about that during the steering committee tomorrow, but I just wanted to specifically see if anybody had any feedback because I know that there was some conversation about who should be able to review, what that criteria is and so I just wanted to as alani's building this out and thinking this out a little bit more from the provider perspective. I just want to see if any providers how to initial thoughts and how this review process, may affect them. And again if nobody has any thoughts right now or they want to put those in discussion feel free to do that, but I think any conversations on rate and any of that kind of stuff we can save for steering committee or get help discussions if y'all don't mind + +Alani Kuye: Yeah, and that's our man. Thanks for I'm raising that tie and I think we'll provide a perspective. we know we solve for providers multitude ways, And that's why we having this conversation because everything related is we have to Take an operational maturity perspective, we can't Benchmark this based on the X exercises for providers the same way you incentivize pools for providers is not the same way you do it for deployers. It's very different audience. It's a different Market places a different process. + +Alani Kuye: Right, I mean back in the day when we have to build, some of the first providers, how long it took Gamo farms and all that means setting up servers. I mean it was insane but compare that till today it's easy point point click click and everyone on this call can attest to that right? So in moving to that other side, we can't say based on what we've done for providers, those same procedures and methodology will apply to deployers. It's a very different audience. It's a very different + +Alani Kuye: At places ux heavy right the folks who will be doing the death tasks QA uat before the five stages of development. I mean been doing this 22 years that there are no shortcuts. Okay, those audiences are a mixed bag. So you have folks from from folks on the Legacy space both another one technical right who want to see providers and who are these that's why you use the anilogy of Airbnb or Amazon. + +00:15:00 + +Alani Kuye: I don't have to go to those platforms to check reviews on some of those wholesale providers that can see them on bloggers referred me different ways. You can scan that Gap, right? So my point is I think this is where you have to think of it. Let's look outside of our comfort zone. Why does this look different because we're now working on the other side of the marketplace coming from someone who's Bill Marketplace isn't my last company I saw but 28 million because we build 30,000 driver. So I want to suffer three million people. So again, that's what I'm trying to get. What's this month to think differently like make a mental shift? You You're Building, for those who are not incumbents looking from a very different perspective. That it's a little bit uncomfortable at first, but when you start to understand why the bigger picture starts to make sense Anil. + +Tyler Wright: Sorry, that was me. I think a Neil put some comments in the chat. and then I think I'll also put some comments in discussions. And again, we can just continue this conversation offline. And again, we could talk a little bit more about it and steering committee and thread go ahead and + +Anil Murty: Watching three so really there's no other way to build this out then to go build those clients, go after specific segments of users and then very very tactically individually go and go go after customers and make sure that they're successful on Akash, So if you saw the Twitter species yesterday, it's all care. That's an example of a customer that took us a long time to get to and it's stuff like that that really was going to drive us forward. So I mean There are seven clients that are being great including sphere on and clouds each of these questions you slightly different patterns of the ux so,… + +Alani Kuye: Yeah. Yeah, Anil good to hear from you. + +Anil Murty: my suggestion and… + +Alani Kuye: I think the Twitter supposedly was interesting right… + +Anil Murty: I'll definitely read Your data post and… + +Alani Kuye: because That's a two-year conversation in making and… + +Anil Murty: comment on that as well is if you can identify specific things that these clients can do in order to help Drive adoption further. + +Alani Kuye: for those who don't know. I brought salt care into the akashicial system. Okay, and… + +Anil Murty: That's probably the best thing for us to do on the client side is presentation or… + +Alani Kuye: the same due diligence we're talking about today is the same thing that we're trying to do two years ago when I brought them in and… + +Anil Murty: my thought at this point, but I don't want to take up all the time in the provider say we should definitely talk Hey Alani,… + +Alani Kuye: the first one. + +Anil Murty: talk about this in this declines. so I'm sorry to intermed. We'll have to take this off of to another call. This is the sick provider call. And yeah, I don't know about history assaultier, but for two years it was nothing that was done on it and all this happened in the last two months. So I'm sorry to cut you off but we really have to focus on providers on this call and we can definitely talk about clients on the sick clients call we can talk about it in GitHub, but Tyler your choice here, but I don't think this is the right place to talk about. and if there is Merit and bring it up in the meeting clients in demand + +Anil Murty: + +Alani Kuye: don't think + +Tyler Wright: Yeah, no. Yeah exactly. And I think I made that clear a couple times. But again, if anybody can look at the GitHub proposal and leave comments in there. I know that Alani is looking for more feedback. That would be greatly appreciated. + +Tyler Wright: cool Continuing to move along. I know that again the pre-tor team has once again update on some of the things that they are thinking about for q1 2020 2024 real quick. And I think Alani also just mentioned it in regards to the GPU provider incentives. I know that's a conversation that Chang put up on chain, I think a week or so ago and there's been a lot of great discussion. thank you to folks on this call and other folks in the community that have participated in discussion. If anybody has any further thing that they want to talk about or any other questions, feel free to drop it in the GitHub discussions, and I know that we'll talk about this tomorrow during the steering committee meeting but again because this also touches that provider I just want to mention it here on the providers monthly meeting. + +00:20:00 + +Tyler Wright: And again push people to go looking at discussion give feedback ask questions and then join the steering committee tomorrow to talk about it in more detail. + +Tyler Wright: cool with that being said does anyone have any questions on GPU provider incentives before we move on to an update on some of the things that the prayer team are thinking about for q1 2024? + +Alani Kuye: All right. + +Tyler Wright: All right, igar. I'll hand it over to you or at the ball because I know that you all have been putting some time and effort into a specific plan a perfect. And then once the pre-tour team has presented a plan and we gotten questions from the prayer tour team. Then Andrew Mello was mentioned in a chat that he has some updates and I'll hand over to Andrew Mello. So jigarette and Deval you guys go first and then what open up to questions and then we'll follow with the angel Mello. + +Jigar Patel: Thanks Shadow. So for this presentation, basically we wanted to get a feedback from everybody about our q1 roadmap. And this is just like we are in the last meeting we presented over 2024 roadmap and we are chilling down to what we're gonna work on this Q one particular. + +Jigar Patel: These three months and based on the user feedbacks. we have certain things that our users and Akash users are facing right now issues currently they are not able to do multiple drives in FML storage test. One of them issued others are no issues. Sometimes they're facing a node issue where they wanted to supply custom nodes or they wanted to do a node in their own kubernetes cluster. So that's our other Focus as well. We are doing a kind of starting provided notification, which is very very basic right now, which will basically opt in process where you obtain for email notification. So if there is a upgrade on a network that + +Jigar Patel: All the providers have to do it. We kind of store their email address and just send them out and notifications. So people know that there is upgrade and we have to update our provider. We're gonna continue core provider service contribution. There's one more thing was the log issue. So whenever the providers become whatever using old process They're not able to see any logs if they wanted to see what's happening behind the scenes. So + +Jigar Patel: we are also building that log process. We're also doing a little bit better job at have error handling right? So, let me just share my screen real quick and I can go through the process or what we are going to do in just share + +Jigar Patel: so basically our plan in q1 is to solve this kind of primary six issues and then some misk operates that we are actually doing to resolves of the most. Ask supports from our community. So this is the exercise that we did from the last provider meeting. We found out that what are the areas that we are spending most of the time giving the support and let's solve that issues first. I work what are the most asked features from our providers in both provider channels and our ecosystem director channel, so + +00:25:00 + +Jigar Patel: Solving those issues are starting with everywhere multiple drives in every storage. So this issue comes a lot where small providers who don't want to give a personal storage, but they wanted to do multiple driving FML So basically combined storage process and then doing that into the Custom node options. So multiple ways to do it currently Akash core Library creates a node inside the kubernetes that we are not to do it, but we will give that option to users if they wanted to create a motor if they're servers is big enough so they can handle node. So that was one of the requirement because a lot of small providers are becoming provider where they only have + +Jigar Patel: Eight gigs of RAM and what eight CPUs sometimes even lower than that if they run nor inside the kubernetes, then it's become very like they cannot provide a lot of resources to network, So that's why we opt out to do question more but we will give them a new options where they can even choose the public mode they want if they want to use Twitter node, that's fine and They wanted to create a node inside a kubernetes because also be qns option probably notification what I explained earlier will give you important information like upgrades in an email in obviously. + +Jigar Patel: We will continue doing the provider service contribution in a core Library. we've been from that there will be a change is coming in. So we did a PR in control moderation, but obviously there will be a changes in coming as courty members who mentioned so we have to change our code as well. But yeah, that's and also any more contribution needed. We will be happy to provide that will stream logs into build process. This do you Longview feature that a lot of user requested we all so will be able to do a little bit more on error handling side because a lot of the errors are very common if the machine goes offline during the process we kind of like if we have an issue connecting it and + +Jigar Patel: SSS process don't give us kind of what are the errors And in the past our user had troubles. According to those errors because they don't know what's happening. And then we have to go into see logs and see what's happening maybe on their part is not open. Maybe DNS is not resolved. So things like that we want to do basically present better in UI, so I'll say thirty forty percent of the supports is just something they didn't do prior to Trader Bay process, right and that process with their doing it. + +Jigar Patel: Probably have error and then we have to you did that. Probably there. You're not right. So basically showing the process a little bit more informative. So they know what's happening. when they ask questions they know what's there on their facing so we can be at better head and error ol Miss cup breads, obviously DNS issue. So I would say another 20 30 percent providers have issue where they are not good at putting to DNS entries and our documentation. It doesn't handle that much very well on that issue as well. So a lot of people forget to put + +Jigar Patel: A wired card English or providers into their DNS. So we don't even know what's 30 years in a site. So right now in the dashboard when you become a provider, it's just says that your providers are fine, but we should see that if that DNS is rolling to their IP. If not, then we can better so that issue or give them steps to how to resolve that issue. Obviously we are gonna do the open apis for other teams like Benjamin where we can forward it now. + +00:30:00 + +Jigar Patel: Audit process to them now rather than the modri on it. So that's coming in connection issue again, A lot of people are having this issue. We wanted to just handle that better at the UI level again better talks and any upgrades that Akashi is putting in we will put into the process and put into the updates. Yeah, so that's our q100map any feedback Is very helpful God damir. + +Damir Simpovic: Okay, can you hear me? + +Tyler Wright: Yes. + +Damir Simpovic: All right regarding the first two points that you mentioned about what supports questions are the most common. I've actually made the I'm sure you are you remember but it's been quite a while since I see anybody mentioned it there is a number of videos that I did. That are primarily done for Helm based provider installs. However, there are also + +Damir Simpovic: they also apply to Such as how to set up port forwarding for any provider whether it's helbase or better based how to set up DNS. + +Damir Simpovic: Again, it doesn't matter which type of install. Anyone is using those videos are the same they will apply to everyone. etc. So, yeah, feel free to not trying these information videos. I don't make any money or anything of them, but just trying to make your life easier. You can just direct and you can just direct and have them watch these videos there 20 minutes half an hour and they will have a much better idea because you are right. A new providers especially home-based providers or somebody who's doing this for as a hobby or as they don't know. They don't know these things and it's very new to them and these concepts are + +Damir Simpovic: I mean everybody can has a + +Jigar Patel: Thanks, Absolutely. We will put your videos link again, for us. We are not gonna build any videos for that. We were just directing to forward some kind of videos in YouTube showing that how to do DNS entries, And if you have build I know so I've watched some of your videos, So what are we gonna do we gonna put your videos into the link so they can see how it work. It's working again. I just wanted to clarify and now pretty use Helms, So from even last year, So the whole process is it's exactly same we're just not building the node inside the kubernetes. That's the only difference because then those are one of the things that we had to manage. So if the note is not catching up then + +Jigar Patel: They will have some issues into the releases, So that's why we opt out but that's why we are giving the node option now. So that big enough there if they have multiple clusters, we can run configure with the node inside that right. but yeah, I just wanted to clarify we are using him is not different than the core process. quieter + +Tyler Wright: Go ahead. + +Anil Murty: Hey guys. Yeah, So awesome presentation. I like all the things that you have on the slide a couple of other ones that I can add and I have a few more notes on this second past you jigar couple of things. I've seen a lot of particularly the AI ml devs that we are trying to attract to GPU marketplaces. That they run into our number one if you're running a AI training job or even in some cases a fine tuning workload. You might want to be data downloading essentially data and then labeling it which is very CPU bound and then at the same time being able to access that same data to run training. So you might have a really large data set of several millions of objects downloading that into a + +00:35:00 + +Anil Murty: into some storage or area memory and then accessing it separately for the gpus to be able to train on it and one of the limitations today we have is that we don't support shared memory natively. And so that's an area that we have to look at Potentially in the next few months. I'm hoping so there's an issue that's created for that. and then the other thing also that I've noticed a lot of times happen with again people that are using gpus for various reasons is anytime one of these GPU cards overheats and sometimes results in the cache. + +Anil Murty: There isn't a lot of diagnostic information today that we're able to surface up in terms of for example, the temperatures on the voltage on the cards things like that. So that's another thing that I was wondering if there's something that we should do about it, but not saying that any other things on your roadmap need to be changed, but just wanted to throw them out. There is other pieces of feedback I've seen Thanks. + +Jigar Patel: Thanks for the feedback il. Yeah, if you wanted to ask to spend some time in doing any and kind of research in Ram issue or overheating issues right? Please let us know that's why we have read put the provider service contribution. That's one of the things that we wanted to do more in 2024 putting some hours into code libraries as we have done in past where the country for sorry content moderation, right? So we have a better understanding how the things work. So yeah. + +Tyler Wright: The ball,… + +Anil Murty: That sounds good. Yes. + +Tyler Wright: go ahead. + +Deval Patel: Yeah, sorry you can go. + +Deval Patel: Can you hear me? + +Tyler Wright: No. Yeah, I can hear you. I don't think anything else is speaking. I know did you have anything that you wanted to say? + +Anil Murty: No just gonna say I should raise my hand. I was just going to respond to jigarette say that sounds good. We can set up some time. I'll work with you to discuss some of the things that I've heard from people that are trying to do fine-tuning and machine learning type of workloads on providers in the challenges that they run into we have solved a couple of them, but there are some really big ones that we need to solve supporting. Sha. So, thank you. + +Deval Patel: Yeah, so these are just preliminary things… + +Tyler Wright: Thank you. + +Deval Patel: what we have in the q1 broad webinar higher level, we can go more deeper in the one to one or meeting where you can dive and prepare a roadmap for us. Right and we are open to ideas. What are the important things and facing whatever the challenges you are facing or hearing from providers in terms of GPU providers or our CPU providers, They're happy to accommodate that right another thing which is actually a lots of people are asking is that they make single provided node with the Creator and then they want to add more nodes towards the same collider, right? + +Deval Patel: Right now there is no UI available for that. Right? We have to guide through them and guide them through some manual process. So yes that is another option. We should consider adding into the roadmap right? But then the roadmap because becomes bigger and it becomes multi quarter roadmap, right? So those are the things we try to avoid, so that those are the things I would like to say one more thing. I want to mention is people are complaining about updating coorder taking too much amount of akt. So let's say just recently few providers updated there provider attribute and it charged them feet create which is about seven and half dollars, So think about that to reducing so if we can reduce that, that would be nice. + +Tyler Wright: Cool, I think if you don't mind making a discussion around that we can talk about that more in GitHub and then take some necessary steps. There must appreciates jigar you and Deval going through a prayer's plan for the first quarter 2024. Does anyone have any initial questions or feedback about what the priorities are going on? + +00:40:00 + +Tyler Wright: cool I think you'll set up some time with the Neil to talk about some of the items that he's been seeing and then again, we'll work on next steps and flushing us out and maybe turning this into a discussion to get more feedback from folks that maybe are not on this call but much appreciate the presentation and we'll continue moving forward. + +Tyler Wright: Cool, if there's no questions for the pray to our team that I know Andrew Mello wanted to give some updates. So I will hand the floor over to Andrew Andrew take it away. + +Andrew Mello: Hi Tyler, if you want to just pull up the GitHub of a cost OS while I talk about it for a second here. That might be helpful. It's a GitHub crypto and coffee slash a coffee list. + +Tyler Wright: I just Hold on just one second. + +Andrew Mello: Just in case there's folks who haven't seen it. + +Andrew Mello: On the phone today, so, thanks. + +Andrew Mello: Yeah, so it's still under development and is now actually powering the largest provider in production on the cost. So it has now, been a bit battle tested in production and with that in mind there definitely some updates that I wanted to bring some attention to so as some of you may know and some of you may not know a Costco acid basically built to be an ISO or + +Andrew Mello: An image that you install on any machine to basically give it Ubuntu 22.04 a kubernetes cluster and a default account provider install all configured for you automatically and up until now that required you writing that image to an actual, USB key or an ISO to attach that to a VM or attach that to your bare metal and boot from it and I have now been able to create ansible playbooks to deploy Akash OS against any VPS or bare metal without the need for the iso so that's a really nice update that I'm gonna publish in the next coming days here, but we are able to deploy now a cash OS to any machine without the iso part, which is really nice. Also, probably the most important feature that I'm going to be working on in this coming month on. + +Andrew Mello: a contrast is what I'm calling Auto port forwarding. So basically new providers are going to be automatically configured with a public domain managed by akashos.com. And until the user goes in and changes that domain they're going to have a joke like a generic domain name and what that's going to allow us to do is basically manage their port forwarding for them and so for onboarding new providers, and one of the largest pain points we have right and have had over. + +Andrew Mello: The time here is setting up the networking doing firewall doing DNS records all that. it's not a good time. And to be honest, It's really excluded a lot of potential providers because that right there is a barrier to entry for a lot of people in a technical knowledge, kind of Gap, people might know how to get through a website or get through an install of something but they're not necessarily familiar with how to do, firewall port forwarding or how to set up their DNS records perfectly. So a Costco Essence is looking to solve that for onboarding new users and onboarding providers and I'm really would like to see a conscious go to market with that as kind of a main feature right to make the easiest configuration possible for someone. So I'm + +Andrew Mello: Paying a release around first week of March for that where a new provider deploying The Playbook or deploying the ISO. + +Andrew Mello: is going to have a provider up and running automatically and I'm even considering going a step further with it and funding those initial providers set up fees so that there is just zero friction right that initial domain and provider could again be managed in a way that we make that completely seamless to the user and that's really the ideal because asking these new providers to get the akt become firewall experts be domain experts, right? We've got a lot of odd stacked against them. So I'm trying to reduce those barriers to entry kind of as quickly and hearing them as what's most important and I think the most important thing to solve for the new provider is going to be that with auto port forwarding and automatic Dom. + +00:45:00 + +Andrew Mello: And for them so they can just get up and running and then either prompting them for the akt for the setup fee or just doing it for them and worrying about it later. So that's my thoughts on what's coming next on Akash OS and the Playbook will be live within 48 hours or so up on the GitHub. + +Andrew Mello: Akash Dash com is now ready for a Kepler integration. So Akash Dash com is where you can monitor your provider earnings and how much your provider has made over time with really easy to understand, numbers for dollars and cents and so a class staffs.com is going to get a Kepler integration where providers will be able to claim their account. So when you go to check your provider right now, they BDO dot computer and it comes up with the stats. You just see kind of read the concept here is to turn that into read Wright information where once you authenticate with your Kepler wallet as the provider with your provider wallet, you'll be able to edit, the page you'll be able to do things like set up notifications and you'll essentially have an account now on a cash so that's gonna enable + +Andrew Mello: Them features down the road monitoring notifications all that fun kind of stuff we can start to do with it and expand on and yeah, those were kind of the big updates of what I'm working on with the cost OS And again Akash OS is once again now powering the largest providers in production. So I would definitely recommend you take a look at how it's built. Yeah. + +Tyler Wright: Does anyone have any questions for Andrew on anything? He just talked about in his updates? + +Tyler Wright: as Andrew just mentioned both with the parade or tool and with the Kash OS tool I would urge everybody to just try these things out to dive into the GitHub repos, test these tools out give feedback about things that you see to the prey to our team to Andrew so that we can continue to improve these tools and make sure that they are production ready but Andrew much appreciate your efforts and the update. Sorry Andrew, we're going to say something else. + +Andrew Mello: nope. That was it. Thank you. + +Tyler Wright: awesome Does anyone else have any other topics of discussion provider related that they want to discuss at this time? + +Tyler Wright: I'm much appreciate the conversation today the updates from Andrew from the praetor team discussions around what Benjamin is about to start building. And again, I'll set up a working group Channel and Discord and also start to set up the first working group session there. Thank you Alani for talking a little bit about your proposal that you put in discussions again reminder for everybody steering committee is happening tomorrow at 11AM Pacific as a part of the agenda. We will go through some of the just active discussions. I know there's a number of that have come in over the last couple of weeks. I would urge anybody that's going to talk about their discussion at steering committee tomorrow to just talk about it at the highest level about what you're trying to do ask what the problem that you're trying to solve and then we're going to continue to promote discussion over. + +Tyler Wright: Next week and then again, we'll hear from the steering committee because there's so many discussions happening whether it be around provider incentives where we've been discussion that Alani put forth. Obviously, we could spend an hour on each and I just want to make sure that we're just staying extremely focused and talking about the meat of what's going on with these discussions and then pushing people to get active and GitHub didn't get more feedback from the community. Cool again much appreciate everyone's time today great conversation. this is a couple of action items that will follow up on but if anybody has any questions comments or anything that they want to talk about further that they've heard here today. Feel free to drop in sick providers Channel and we'll just continue to talk async online but much appreciate everyone's effort time and commitment and really excited for what we got going on the future. + +00:50:00 + +Tyler Wright: Hope everyone has a great rest of their day. Thank you. + +Alani Kuye: Thanks dar. + +Andrew Mello: + +Tyler Wright: Over bye. + +Meeting ended after 00:50:46 👋 + From bb5bad3f164706de4db49b9077258b49a8c87d79 Mon Sep 17 00:00:00 2001 From: Hewi <121134490+heyhewi@users.noreply.github.com> Date: Mon, 11 Mar 2024 14:14:04 -0500 Subject: [PATCH 012/138] sig-economics: create meeting 13&14 and update README. (#506) * sig-economics - Create 013-2024-02-07.md Signed-off-by: Hewi <121134490+heyhewi@users.noreply.github.com> * sig-economics: Create 014-2024-03-06.md Signed-off-by: Hewi <121134490+heyhewi@users.noreply.github.com> * sig-economics: Update README.md Signed-off-by: Hewi <121134490+heyhewi@users.noreply.github.com> --------- Signed-off-by: Hewi <121134490+heyhewi@users.noreply.github.com> --- sig-economics/README.md | 4 +- sig-economics/meetings/013-2024-02-07.md | 215 ++++++++++++++++ sig-economics/meetings/014-2024-03-06.md | 309 +++++++++++++++++++++++ 3 files changed, 526 insertions(+), 2 deletions(-) create mode 100644 sig-economics/meetings/013-2024-02-07.md create mode 100644 sig-economics/meetings/014-2024-03-06.md diff --git a/sig-economics/README.md b/sig-economics/README.md index 88f147a8..9630ac03 100644 --- a/sig-economics/README.md +++ b/sig-economics/README.md @@ -24,8 +24,8 @@ Meetings happen every [First Wednesday of the Month](https://calendar.google.com | #10 | Wednesday, November 1, 2023 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/010-2023-11-01.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/010-2023-11-01.md#transcript) | [Link](https://6cjhlgaiutfckbasf6sqjbypkrhyjgll463t67f7aw3af5gtghea.arweave.net/8JJ1mAikyiUEEi-lBIcPVE-EmWvntz98vwW2AvTTMcg) | #11| Wednesday, December 06, 2023 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/011-2023-12-06.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/011-2023-12-06.md#transcript) | [Link](https://czik4rsznmpaxems7ffmui4fiaar7waib6gtwy5jt4pptosygpla.arweave.net/FlCuRllrHguRkvlKyiOFQAEf2AgPjTtjqZ8e-bpYM9Y) | #12| Wednesday, January 10, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/012-2024-01-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/012-2024-01-10.md#transcript) | [Link](https://gbxszp7zaubg3dskphdcgwpqkjtz3mb3zgtq46ka2yyzzkfij7na.arweave.net/MG8sv_kFAm2OSnnGI1nwUmedsDvJpw55QNYxnKioT9o) -| #13| Wednesday, February 07, 2024 10:00 AM PT (Pacific Time) | | | -| #14| March, 2024 10:00 AM PT (Pacific Time) | | | +| #13| Wednesday, February 07, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/013-2024-02-07.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/013-2024-02-07.md#transcript) | [Link](https://6rzdyy2kxzn4qpilczq7vdvfd52kxb65rk4cnhor32f4cibhkqmq.arweave.net/9HI8Y0q-W8g9CxZh-o6lH3Srh92KuCad0d6LwSAnVBk) +| #14| Wednesday, March 06, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/014-2024-03-06.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/014-2024-03-06.md#transcript) | [Link](https://l7relb4v4vhxhw4shqui4iyoyyeqdt6ogwpx2thybmneridemfnq.arweave.net/X-JFh5XlT3PbkjwojiMOxgkBz841n31M-AsaSKBkYVs) | #15| April, 2024 10:00 AM PT (Pacific Time) | | | | #16| May, 2024 10:00 AM PT (Pacific Time) | | | | #17| June, 2024 10:00 AM PT (Pacific Time) | | | diff --git a/sig-economics/meetings/013-2024-02-07.md b/sig-economics/meetings/013-2024-02-07.md new file mode 100644 index 00000000..5e2f15e5 --- /dev/null +++ b/sig-economics/meetings/013-2024-02-07.md @@ -0,0 +1,215 @@ +--- +title: "Economics SIG Meeting #13" +key: "sig-economics-meeting-13" +date: 2024-02-07T18:00:00Z +contributors: + +- Adam Bozanich +- Adam Wozney +- Alani Kuye +- B S +- Cheng Wang +- Denis Lelic +- José Henrique Targino Dias Góis +- Max +- Rodrigo Rochin +- Scott Hewitson +- SGC | DCnorse +- Tyler Wright +- Zach Horn + +--- + + + +# Akash Network - Economics Special Interest Group (SIG) - Meeting #13 + +## Agenda + +* Updates since last monthly sig-economics meeting. +* Updates on provider incentives. +* Open up to community for ideas or concerns. + +## Meeting Details + +- Date: Wednesday, February 7, 2024 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://6rzdyy2kxzn4qpilczq7vdvfd52kxb65rk4cnhor32f4cibhkqmq.arweave.net/9HI8Y0q-W8g9CxZh-o6lH3Srh92KuCad0d6LwSAnVBk) +- [Transcript](#transcript) + +## Participants + +- Adam Bozanich +- Adam Wozney +- Alani Kuye +- B S +- Cheng Wang +- Denis Lelic +- José Henrique Targino Dias Góis +- Max +- Rodrigo Rochin +- Scott Hewitson +- SGC | DCnorse +- Tyler Wright +- Zach Horn + +## Notes + +**Introduction and Updates** +- Scott initiated the meeting, gave a recap of meeting #12 and any outstanding items in discussions or on-chain items related to sig-economics. + +**Discussion on Provider Incentives** +- Provider incentives is currently being voted on-chain via [Proposal 246](https://www.mintscan.io/akash/proposals/246). The spend is only for Phase 1 of the program and is ~$3.5M worth of AKT. +- Cheng lays out the three phases of Provider Incentives Program (PIP). Phase one consists of a large committed pool of resources that require 1 year contracts. This is to ensure that there is a baseline level of supply that is not subject to individuals or companies adding/removing resources regularly. +- Phases two and three will be more closely like a "liquidity pool" where rewards are disbursed based on configuaration, uptime, and other metrics. This phase is still in progress and requires more thought on ways to operationlize effectively. +- Alani asked Cheng who owns the providers/hardware that is going on the network? Cheng responded that Data Centers and other individuals that go into the 1 year contracts are the ones who actually own the hardware and any depreciation or tax implications would be from their end. +- Cheng also states that while these providers are being paid for by the community pool, the revenue collected from these machines will go directly back into the community pool. +- Scott also calls out that everything that is being done will be be reported on as information arrises and funds are spent. There are no hard dates for reporting but Overclock Labs will be as transparent as possible given some information is commercial contracts. + +**Other Discussions** +- Alani emphasized the point that individuals need to actually be reading proposals both in Github Discussions and when they go on-chain. He has concerns for when people read a few lines and sharing their opinions without fully understanding what is being proposed. +- Cheng brought up the point that the Cloudmos team's six month contract for continuation services ended, but that the wallet used for the acquisition still has a significant amount of funds (due to the run-up in price of AKT). The proposal in [Github Discussions](https://github.com/orgs/akash-network/discussions/472) would repurpose lefrtover funds to continue paying the Cloudmos team for an additional 12 months. + +### Action Items +- All are welcome to contribute! Anyone who wants to contribute please visit sig-economics in the [Discord Server](https://discord.gg/akash) + +## Transcript +This editable transcript was computer generated and might contain errors. People can also change the text after it was created. + +Scott Hewitson: All right everybody. This is the 13th I think economics call second of the year. + +Scott Hewitson: last month's call went a little long. There was quite a bit of discussion about provider incentives and a few questions on the Community tax and inflation props that it passed so I would encourage anyone who did not go to last month's call to read those notes and GitHub. And yeah, I'm not sure if we have too much to talk about to today. Let's see from the discussion side. There wasn't a whole lot going on outside of the provider incentives is currently on chain and being voted on scheduled to pass at the moment. I'll drop the link right here. So if you haven't seen it, please vote whichever way and yeah. + +Scott Hewitson: And then let's see if we had so in Discord not a whole lot of chatter just kind of, follow-ups from last session. So again check that out if you can. And I think for this call, maybe we can just kind of wrap a bow on the last bit of Provider incentives now that it's on chain and then kind of open it up to the community for any questions and concerns or anything that they want to talk about regulated to cig economics at Large. So with that Cheng, do you mind talking shortly of one Probably the fourth time that you've done it but a little bit more about provider incentives just to … + +Cheng Wang: No, I love it. + +Scott Hewitson: give everyone the lay of the land and maybe talk about some of the things that we incorporated since the last call before going on chain. + +Cheng Wang: Yeah, there are quite a bit of work and ideation went into the last version that you saw go on chained for provider incentives program. We're calling the PIP for sure. We like to make things nice and snappy with the naming abbreviations there. So the primary change is I'm going to be is the phasing so phases one two, and three and each phase corresponds to particular bucket of funds that are allocated to GPU resources. So the biggest in phase one is currently what's on chain for approximately 3.5 million USD. All right, things fluctuate a little bit given market prices of akt, right, but either way the phase one is going to be for the committed pool of resources for those of you I'm sure most of you have read through it for those of you who didn't commit a resources. Takes into account some of the feedback from the community which is if we run a short lived. + +Cheng Wang: Provider incentive campaign what happens when those resources drop off? How do we ensure continuity for tenants? All that kind of stuff. Right? So the committed pool is how was expanded right relative to presentation terms to the total phase of total first presentation program in order to sign one year long commitments with various data centers in order to bring those high-end resources from data centers who are professionals at their job and do this for living so that those really resources are reliable. And number two is to ensure that those providers are adequately paid right and not dependent fully on, hosting workload. So we do anticipate these things to sell out very very quickly and they're not being an issue there and third is just continuity, So if you're someone doing some serious work, whether it's AI ml driven or something else and you want to deploy your applic + +Cheng Wang: And your use case you're back in whatever. It is on a caution Network you want continuity, You don't want these resources to disappear in three months. You're not out here just to kind of experiment potentially you might run proof of concept type of workloads, right just to get things started. But ultimately you want them to persist. So that's what the committed pool does. + +Cheng Wang: There for one year long leases and it'll be specifically with data center providers Not just like anybody out there the other two pools phases two and three are what we'll call liquidity pool. So that is going to be your very familiar with how pools are constructed. We'll have specific configurations that will map out. They're more likely be in the meeting like more the consumer grade chips or slash medium lower and data center great chips, right like that save you 100 30 90s 40 90s that ilk of Chip will be in that with those particular pool with us specific configurations necessary right for the network and that'll just be completely Community Driven and anyone who want to contribute those resources can contribute and that's that tier and then there's a final tier face three and these things don't have to occur. Sequentially they can occur concurrently, right just depending on timing and various other factors of when these resources + +00:05:00 + +Cheng Wang: on how they can be secured Etc phase three in the last one we'll call Next Generation R&D pool reason being is AI. mean technology in general moves extremely quickly and AI even more so + +Cheng Wang: And these chips really fall in and out of favor very very quickly. the life cycles are super duper short, 100s a 100 for example, I'm not sure if some of but those chips Nvidia has already stopped manufacturing in 100 in favor of the replacement architecture l40s. And so the l40s chip is replacing the a100 and a lot of people out there even those who are and I'll haven't even really, in their brain retrained it if you will that's a borrowed term to using l40s versus a 100s. So, the Next Generation pool allows the core team to go out there and stay on The Cutting Edge right like AMD support for example, a key core feature. We've been working on for a while. So, amd's enter the chat. So that's one other field of group of chips that we need to really keep an eye on right and in addition to that down coming down the pike is h100 right now. + +Cheng Wang: In the Krav as far as Nvidia is concerned and just generally right h200s are coming out. Then there's the whole Blackwell architecture b100s are in the next two years or so or year potentially and then there's the X Series right that's coming out after them lay around 2025 for NVIDIA and I'm not even sure what amd's roadmap and times like timelines look so suffice to say the R&D Next Generation pool allows us to really experiment in small bursts with some of these Where our chips and architectures to see what the actual supply and demand curve for potentially would look like and to encourage people to use these chips right and get data for the community for a caution and work so we can understand in subsequent iterations of providers incentive for two pip part three, etc. Etc. Can be more tuned to actual data, so + +Cheng Wang: Those are kind of the three phase one is already on chain proposals slated to pass as Huey's outlined and shared and that's what we got there any particular questions or thoughts around that? + +Scott Hewitson: Yeah, just a quick clarifying question. So we got to the committed pools 12 months the next one phase two. The liquidity pool says four months. obviously some of those things can be running concurrently, the liquidity pools probably more interesting to some of the people at home who's got their 40 90s. Do we have any rough timelines on when we're thinking to implement something like that, or is it going to be and after that after the committed pool? + +Cheng Wang: I don't think it'll be after so. + +Cheng Wang: the committed pool once I passes we will like a lot of my new show So sorry if I'm a little boring. I'll try to go over quickly. So once we get the funds we have to get into a point where right now we're talking to, on the core team side a bunch of data center providers as far as you're availability as we get the funds just because get the funds doesn't mean the chips will be ready right away. These things are rather scarce in the environment at this point in time. So, as we get them onboarded in some significant quantities will be able to bring them online. We're gonna bring them online as quickly as we can as far as hotline goes. I can't say with absolute certainty, but I definitely say measured in weeks lower number of weeks, as far as getting them on and it might be within phase one some of those resources might be phased as well because we can't just go to the store and grab a bunch off the shelf and put them on right those in quite work that way so we would love to get the first sub phase if you will face one launch ASAP and more + +Cheng Wang: information will be available as soon as we get that but I don't really have too much to share at this point in time too much concrete. So sorry, I can't directly answer that but What we want to get these things on online and we want to showcase or that continue to Showcase rather a caution networks capabilities, right? We've already demonstrated the entire animal stack right from inference to fine-tuning to training every other, deep in projects out there. As you know said they can do one of the other but no ones actually proven anything in the wild other than us. So we'll continue to work on that. Yeah, Alani I go for it go first. + +00:10:00 + +Alani Kuye: Here. hi Cheng. and part of me. I'm not as informed on this year. or not, a 100s are they? across owned overclock own provider owned data center owned who actually is the custodian of the infrastructure + +Cheng Wang: and Great question. So who physically owns the hardware will be the data center. The actual machines themselves will be data centers and the data centers themselves will become providers on a caution Network for putting their Hardware onto the network as far as who's going to manage the providers for data centers who are comfortable managing it themselves. They will do so for those who are not comfortable managing themselves the cash 14 and ocl core team will work with people in the community as well as using internal resources to manage those providers. as far as not the I guess custodian might be a way to look at it right at the administrator of those resources as So there's one path. + +Cheng Wang: Data center will be the owner of the resources. They will either manage it themselves as a provider or Outsource the provider management to ocl core team VZ like the community right in some way shape or form in that way. then so that's how those resources be put on to the network. + +Alani Kuye: So from a tax perspective who gets the carpets and who gets the Opex. If I'm gonna depreciate that over four years for example, right you sir,… + +Cheng Wang: So yeah. + +Alani Kuye: I'm going with it, right. + +Cheng Wang: Yeah, so the benefit the capex depreciation will definitely come out of the data center. so let's say I am data center, AI machines.com, right? And I have a bunch of a 100s or H 100s and I decide to sign an agreement with ocl to put these resources on the caution Network. So then at that point, it's simply a commercial agreement from the data Center's perspective. That's all it is. Right. They get paid their money for putting resources on to network and that's all gravy there and thats not That's simply just a very plain commercial agreement between overcog collabs and a data center or several data centers. And so the data center in this case will operate normally would they incur their Opex right and their capex? It's all baked into whatever they charge overclock labs and the kind of Comm. + +Cheng Wang: Right over a year or if it's on demand and other whatever the scheme is, right the duration is that's all baked into the price. So they take their capex depreciation on those chips. And obviously they incur the Outbacks of it as well as far as but the other operation side the only nuances in terms of Provider management for the sake in the instance where caution Network core team manages the provider right? That's where the operational cost will come out of the provider incentive pool, right? Because there is some Elementary. So for example, there's a Community member. Let's just say who manages a provider or set up providers? They would have to be paid for their work right? So that there's of the pool. + +Alani Kuye: Okay, I was just trying to get a better and thanks to clarifying that because I was thinking if I 100 K and it costs 120 for your depreciation plug the economics, cognit on the books and either way I get it back somehow right? Someone's gonna you put the taxes I can offset that. + +Cheng Wang: exactly + +Alani Kuye: From an accountant. + +Cheng Wang: Yeah. Yeah,… + +Alani Kuye: Alright. Thanks. + +Cheng Wang: totally. So if you get a hundred dollar chip, Let's just say and the lifetime value of it is let's say five years and do linear depreciation. You can write off 20 bucks out of the hundred per year for five years. And offset, whatever your income is right in those five years with that particular thing and then whatever your Optics is, obviously that takes your bottom line down as and then whatever revenue is your Revenue so that all go against your state at Revenue there so for data centers, in this case. they're only revenue is directly going to be the contract that they get paid on and so in the event, this is something really interesting too. I'm not sure if we were able to put that in discussions, I think we might have which is + +Cheng Wang: Data center for gives sign data center science contract with ocl bring resources on Kosh Network right save those resources are $100 right costs those overclock Labs $100, but that's been funded by the community pool that passes then to the data center that agreement is tied off all clear then from the tenants perspective, right? They're going to use resources on the network that is managed by who Clash Network, Minister administrator, shall we call it and those revenues that flow through ultimately + +00:15:00 + +Cheng Wang: Where the zacho to we're going to all the excess net of paying expenses. I think this is what we talked about. We'll go back into the community pool. So if we buy resources in the community pool for a hundred dollars, right and obviously we're going to ensure that the prices are highly competitive and not overtuned right but having said that once the inflows come in net of whatever the expense are. Let's say, Alani is managing a provider and he gets paid, five percent out of this whatever is coming through. I'm just throwing out random numbers right then 95% of those revenues would go ocl a cautionary core team that manages provider will be putting that at the end of the program back into the community pool. So it'll be this pretty virtuous cycle where the community pool will be ultimately refilled by usage. Yeah anytime. + +Alani Kuye: Pretty solid. Thank you. + +Cheng Wang: B's had two questions as the PPA elected by Syrian receive a salary at our parent did that I don't think that PPA receives. A salary per se like so we're gonna talk through it on the steering committee. the ask there might be some consideration for administering the program. Like I said before as far as costs go those haven't been really super clearly defined. for one thing as far as who is the PPA I think + +Cheng Wang: What is it provider program in administrator as we're calling too many acronyms here. I think that administrator I personally would nominate ocl because we have the resources and Personnel to do it and we've always been extremely transparent to the community there. So that's the number one. So, yeah, in terms of costs, they're likely will be something but likely if ocls elected as the primary administrator, we likely would not take anything as far as a fee goes because that's just kind of cost of doing business for us. Number two, there's transparency reporting requirements. They're actually how regularly I'm too apologies already. No, so we don't know what the Cadence ought to be. You can definitely expect them regularly inconsistently. It won't be regularly every six months right be something like that, but we just don't know exactly what the Cadence is because we don't know as far as reporting how the date is gonna be aggre. + +Cheng Wang: how long it's going to take us to Crunch that information put it into something that's shareable but suffice to say I think you can believe and it don't take my word for it. I just look at all the community governance proposals. We've submitted in the past and all the reports that Scott Huey here has been at the helm of and pushing those opposite Community as far as putting money back into the community pool as far as access funds go number one number two showing, all the reporting what was called Google. + +Cheng Wang: Data Studio things called looker studio now so all those reports are out there and shared with the community to view and we do Endeavor to do the same thing here. Thank you Scott for sharing that so something like that. You can expect something like this and obviously if there are questions and things like that, we'll post updates because this is such a huge thing will likely post updates maybe and GitHub discussions should there be enough for it at the very least. We'll be talking about it on seeing economics it provider, across a whole bunch of things and working groups as well because this is the biggest program launch today and they're gonna be a lot of questions and a lot of curious mind. So we'll definitely share the data very very ask consistent as we can but also not So frequently, let's just say daily or weekly that it kills us on the administrative side,… + +Scott Hewitson: Right. Yeah,… + +Cheng Wang: Because we do have a lot of things are juggling. Yes, Scott. + +Scott Hewitson: so I think just to add to those two questions from BS the PPA if any work is coming from overclock. We're not going to be taking money for effort. if there's other folks in the community that need to help there that can help out then that would probably make more sense because people need to be compensated overclock Labs. we have our own payroll we have our own thing. So we're not using Community funds to pay that and then the reporting side I dropped in this dashboard from events. my view on this is kind of as things start coming in and that's when we'll get the information out. So yeah, I don't know if it's a quarterly probably is, I can count on that for sure just because + +00:20:00 + +Scott Hewitson: we should be doing that but really, the second I learn about an expense or it's realized or whatever I'll put it up and hopefully just have it running. So there's a lot of transparency behind it. everything in the community pool it's the community pool. So it's kind of like a public programs like governments. It's like we should be showing what we're spending money on and how that's growing the network. So hope that helps add some flavor. + +Cheng Wang: Up Bravo. Thank you Scott. it perfectly said + +Scott Hewitson: awesome Does anyone else have any questions or concerns related to provider incentives prop 246? + +Scott Hewitson: I'll take that as a no if you do if you think of something or you don't want to talk about it here feel free to drop in Discord and we'll be sure to get you a good response. At this time, I'd like to Alani. What's up? + +Alani Kuye: Yeah, just very minor commentary, thank you guys for all the work you've been doing. I also just want to emphasize that it's important for people to read. these proposals in their entirety before quantificating I think oftentimes It's very concerning when people just read four or five lines without really comprehensively understanding. What a proposal is about and just firing off a grenade and opinion basically, so I think we should really spend more time within these things and really understanding it. So we have literacy around contacts and where it's going because we want to be careful. We don't get so bogged down and tactical mindset and not meet the overall strategic objective. That's just import from my side. + +Scott Hewitson: I think that's a great Point Alani. I mean we live in a world where everyone reads headlines and makes their decisions off of that. So, I mean, it's easier said than done but for areas where there's pontification or grievances or I think we've been able to do a good job to alleviate any concerns or at least address them and explain, An altering point of view,… + +Alani Kuye: No. + +Scott Hewitson: so I agree with that 100% + +Scott Hewitson: awesome + +Scott Hewitson: We still have quite a bit of time. So if there's anything you want to discuss any ideas you have anything related to Sig economics or anything that's growing the network the floor is yours if you want it. + +Cheng Wang: I did have one quick one if I can shoe horn myself in there for No,… + +Scott Hewitson: I suppose. + +Cheng Wang: so I will not be seating my time someone else now in this case. I think the other big thing is we put in to get up discussion to wanted to give a little bit Time air time for the provider incentives want to marinate a little bit. But one thing we did want to and the pain of transparency is for the continu. + +Cheng Wang: Of cloud most right and they're continued contribution to overclock Labs. I put up a discussion there just to keep things on total up and up and that we are extending our relation Cloud notes because the team is great and obviously they've worked for years. Now. I'm within a caution Network in a fantastic fashion. So we're continuing that for at least another 12 months hopefully more but the slated agreement right now is for 12 months and we're repurposing the funds from the original funding of the six months and as well as the cloud most acquisition there is some access funds left over to support that and I think there was one set of questions from ZJ, which is he has some questions. Will it be using you denominated payments as far as what the expectation the Costco it's kind of very little bit based on hours worked and stuff like that, but it'll be slightly above what the + +Cheng Wang: I'm run rate was for the first six months. That's number one and number two the funds vest over the next one. So it'll just be monthly payments. So it wouldn't be a whole big shot all up front with the acquisition that vests over time. It'll Simply Be work that's been done. it'll be like a contract So a salary if you will continue to work being done and I'll be paid out over time on a monthly basis and that'll be denominated. Whatever the Says at the time of payment we snap it there and that's historically how we've done it. + +00:25:00 + +Scott Hewitson: Awesome. Thanks for covering that a little bit + +Scott Hewitson: is there anybody else that wants to bring up anything can be related discussions proposals any ideas? Yeah. Leave it open for a minute. + +Scott Hewitson: No takers this time because Andrew G's not here to ask me five questions to keep me honest. I love that guy. No, I mean last call was I think was an hour and 20 minutes. We're at 30 minutes now. So, I think a lot of stuff got hashed out in the last call. If I think we can wrap up at this time. Unless anyone has any last things they want to say and if you do have any, comments concerns questions, whatever you want. Feel free to drop them in Sig economics and Discord. I checked that very regularly and try to be very responsive there. so with that, I think we're going to end the call and we'll see y'all next month and + +Alani Kuye: All right. Thank you. + +Scott Hewitson: alrighty + +Cheng Wang: Thank you everyone. Thanks Alani good to see you. Yeah, right. + +Zach Horn: thanks guys take + +Meeting ended after 00:26:37 👋 diff --git a/sig-economics/meetings/014-2024-03-06.md b/sig-economics/meetings/014-2024-03-06.md new file mode 100644 index 00000000..f08adc1f --- /dev/null +++ b/sig-economics/meetings/014-2024-03-06.md @@ -0,0 +1,309 @@ +--- +title: "Economics SIG Meeting #14" +key: "sig-economics-meeting-14" +date: 2024-03-06T18:00:00Z +contributors: + +- Adam Wozney +- Andrew Gnatyuk +- B S +- Cheng Wang +- Moss Business +- Robert Del Rey +- Rodrigo Ronchin +- Scott Hewitson + +--- + + +# Akash Network - Economics Special Interest Group (SIG) - Meeting #14 + +## Agenda + +* Updates since last monthly sig-economics meeting. +* Updates on provider incentives. +* Open up to community for ideas or concerns. + +## Meeting Details + +- Date: Wednesday, March 6, 2024 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://l7relb4v4vhxhw4shqui4iyoyyeqdt6ogwpx2thybmneridemfnq.arweave.net/X-JFh5XlT3PbkjwojiMOxgkBz841n31M-AsaSKBkYVs) +- [Transcript](#transcript) + +## Participants + +- Adam Wozney +- Andrew Gnatyuk +- B S +- Cheng Wang +- Moss Business +- Robert Del Rey +- Rodrigo Ronchin +- Scott Hewitson + +## Notes + +**Introduction and Updates** +- Scott initiated the meeting, gave a recap of meeting #13 and any outstanding items in discussions or on-chain items related to sig-economics. + +**Discussion on Provider Incentives** +- Cheng Wang provided an update on the Provider Incentives Program (PIP) since it has passed on-chain governance and funds have already been used to secure contracts. +- As of the time of this meeting new resources such as 4090s and H100s have come on the network for available use. +- Andrew asked if these resources are already being leased or if there are use cases that are coming on to the network soon to use them. Cheng responded by saying that there are multiple tenants that the core team has been talking to and expects the providers to fill up. +- Andrew asked for further clarification on whether we are incentivizing resources while they are being used or just to have them up. Cheng responded by calling out that these new providers are signed contracts so they will be up but obviously don't want them running empty. Any funds they make will also be sent to the community pool. + +**Other Discussions** +- Moss Business, a small content creator, asked about security issues related to the network or if there were some SIGs on security. Cheng suggested going to [sig-providers](https://github.com/akash-network/community/tree/main/sig-providers) as some of the questions that Moss Business asked are being worked on there. +- Andrew asked where we are in AKT 2.0 and what still needs to be done. Scott responded by calling out the [AKT Token Page](https://akash.network/token/) that shows the main features being: + - Take and Make Fees - Live + - Stable Payments and Settlement - Live + - Incentive Distribution Pool - Not live but make/take fees are currently going to the Community Pool + - Provider Subsidies - In progress with PIP + - Public Goods Fund - Not implemented but Community Pool has been the placeholder and where contributors can seek funds to grow the network. +- Andrew brought up Io.net raising $30 million to compete, how is the team thinking about this? The core team's stance is that the pie is large enough for many players and competition is welcomed and good for the space at large. + + +### Action Items +- All are welcome to contribute! Anyone who wants to contribute please visit sig-economics in the [Discord Server](https://discord.gg/akash) + +## Transcript +This editable transcript was computer generated and might contain errors. People can also change the text after it was created. + +Scott Hewitson: All right, all today's call. This is the cig economics monthly call for March. We've had quite a few of these I will call out that I did not get the notes up from the last call. So that's squarely on me. We've had a ton of things going on. So I will make sure to get that done shortly after this along with these notes, but that is on me and my bed, so kind of kicking things off. I was looking at proposals that have passed since the last call we had the provider incentive pilot, which we talked about. It was actually on chain while we had this last call which tasks and then also kudos to the folks doing the developer onboarding proposal via zealing that passed as well. So excited to see what comes of that. + +Scott Hewitson: And from discussions there wasn't anything major that I saw and then from the Discord chat. It's not too Lively. But sometimes we get a questions a few answers. I think today we can kind of talk about obviously the provider incentives program and where we're at with that since the proposal is passed and I'll pass that over to Cheng in a minute and then as always we can open it up to community members if you have Any questions concerns or just want to jump on your soapbox and talk about economics. So with that Cheng if you don't mind you could give us a little. + +Scott Hewitson: quick recap with where we're at with the PIP phase one phase one is the only one that went on chain and passed so we can just talk to that or if anyone has questions about the other phases we can talk about that as well. + +Cheng Wang: Yeah, I'll go through and talk about phase one real quick and touch on the others and we can open up for discussion from there. phase one past resoundingly and of course it's been great since then, prices have appreciated thus far the market I think is responded the economics environment I think is improving. So we'll see, it's going really well. We have thus far engaged to Providers one and that's already existing one. So we work with both of these before as soon as the information is finalized. We'll of course communicated to everyone publicly but we are throws of getting those resources signed and spun up and I think it's now coming on starting to come online. I think yesterday a bunch of h100 came online. So I don't know if anyone saw that the latest and is located in Quebec and Canada, and so we're starting to get all those fun up. So in terms of the resources that we + +Cheng Wang: Be targeted based on the discussions there a 100s a6000 and 40 80s or 40 90s. Excuse me. We are getting all those spun them is just gonna take a little bit of time to nail all those things down. and really looking forward to it. I think the resources are all we currently in terms of pace as far as the allocation the budget goes for phase one we spend about I would say 60% year marked about committed committed about 60% of the phase one budget ready to these resources some have come online some are in the process of coming online. And so there's still a little bit of ways to go as far as finding the additional resources that we want to Target. So that's phase one. + +Cheng Wang: Phase two is still in design the stuff around that we were talking about it internally in amongst according yesterday the composition of that and the execution and especially operation of it it's gonna be challenging for sure because it's not on chain deck stuff right where we're doing it fairly manually to start. So there's that and then phase three obviously will be a little bit more kin to phase one. So low on the operational load and just gonna be more so on the back end work that the core team has been doing + +Scott Hewitson: Thank you for that update with Pip. Yeah, does anyone have any questions or concerns or anything else? They'd like to know about provider incentives Andrew. There we go. I got my man and asking questions. + +Cheng Wang: a price of PR + +Scott Hewitson: He's here to keep us all honest,… + +Andrew Gnatyuk: Yeah. Not just a quick question and… + +Scott Hewitson: and I love it. + +Andrew Gnatyuk: maybe I missed it somewhere on the previous six for this h100 so I saw them on the stats do we have clients to use them? do we have some will use cases that are gonna on board and we will see that they are already released or something that + +00:05:00 + +Cheng Wang: Yeah, so the resource I think just came online yesterday. And so we do have some organizations that are looking to use them already. And so we're gonna get that spun up. That's number one. And number two is we have some Partners who I don't want to necessarily announce you get in and I say Partners likely but we're working with a couple of companies on the kind of client side who are developing toolkits themselves to enable fashion appointment and all that kind of stuff, right? And so + +Cheng Wang: They're integrating Akash as we speak and we'll make a caution Network an option for people who are using, what they're building on top of just the raw machines themselves, And so once that comes online, we should see a lot of these things fill up. So as far as in my head what I know, I think they're at least two to four two for sure and probably four if not five very high potential use cases for these machines. We definitely won't have them up online running, vacant right? Because we haven't really pushed it out. And so once Step One have these resources set to connect them with the folks who we know already working on connecting them. And so that's really in progress step three is work on the partners where I guess + +Cheng Wang: Yeah, Partners those just say who need these resources and continue develop them so they can use them and the final bit would be to not the final bit. But the next thing is advertise, right really promote this as soon as we know the resources are stable and tested up online running all that kind of good stuff. + +Andrew Gnatyuk: Some got it. Thank you. + +Scott Hewitson: Does anyone have any other questions regards to the pit or one phase two? Yeah, we got some background chatter. There's a TV and Cheng's background. + +Scott Hewitson: awesome Yeah, I mean I don't know if we have a ton to talk about on this call. I did want to call out a few folks. I see b s I believe you've come out on a couple of these calls and then I see moss business so welcome to you folks, if you want to introduce yourself feel free. If not, also that's fine. And we're always looking to having people join these calls, we get a ton of great ideas out of these calls from coming from wherever so yeah Andrew, what's up? + +Andrew Gnatyuk: If this one more question to clarify, so if I understand correctly, we are incentivizing the providers when their gpus got least right not when they just go on the market. + +Cheng Wang: no, so for phase one because for phase one the way we're doing it is we go to the providers for these high-end resources and we sign long contracts with them and then pay them for it. So in this particular instance, we cannot just say hey put these resources on a caution and we'll pay you if there's usage we have to commit to it and it's just one of those things where it's a chicken and egg challenge, right? We have to have those resources online in order to continue to attract the use cases that come on a caution Network and grow the network. So that directly answers your question there. And so the other part what that means is because they are already being paid. + +Cheng Wang: Contract right? So then whatever that gets generated to those particular wallets, as far as least Revenue that will cycle back and go back towards the community pool. So it's kind of like all this virtuous cycle, So let's just say I'm a data center, I sign a contract with overclock Labs because we have to be the entity to face off against someone to sign a contract right for hundred thousand dollars for whatever resources right? Overclock Labs through the community pool pays me a hundred thousand. I'm good. I don't care what happens you can use it you cannot use it when those resources get used. It goes into a wallet that ultimately we'll require those providers to send the funds back to us and it's all on chain and public and auditable so they can't really, do anything squarely and get away with it. So once those funds come back into the wallets ultimately at the end of everything will aggregate at do all the accounting and the reporting to show the community. Hey, here's what the usage was Etc. And then the + +Cheng Wang: access will be of course sent back to the community pool. So that's for phase one phase two will be a little bit different in that. Yeah face-to phase two be a little bit different because it'll be more free for all and open to everyone in the community who has, resources that meet the requirements and so they'll be essentially the same thing. They'll be paid for those resources and uptime right as functions of how we calculate and then + +00:10:00 + +Cheng Wang: For that. I think the guidance will be since you're getting provider incentive to just have these resources online, you're essentially being paid for it anywhere regardless of usage. There will be I think requirements for prices. So you can't essentially egregiously double dip, So let's say the market can bear four dollars per hour. We would likely have that price push down, right if you're already getting some sort of compensation from the pool, but we were so ironing that out in detail. + +Scott Hewitson: Yeah, and go ahead and Moss business. + +Moss Business: Hey, can you hear me? Okay. Awesome. + +Scott Hewitson: Yep can hear you good? + +Cheng Wang: on the clear + +Moss Business: I'm a small content creator. So I just have kind of a discovery question. Mostly interested in are there any sigs where a discussion around security like Security in the Akash Network would be discussed appropriate. + +Cheng Wang: Security in what sense from a deployment sense from a blockchain side of things deployment side of things. + +Moss Business: Correct. Yeah. + +Cheng Wang: Yes, so I would say Sig providers might be where you want to go for that. So when you say security it's kind of like if I deploy something is my deployment secure is the provider trustworthy and all those kind of things So I think for that particular thing, we have one of the first features we started working on has been one provider thanks to you for dropping us. So the auditing right the ability for providers themselves to audit workloads that are running on their machines so that They can then adhere to their own local jurisdictions and requirements. Whatever those are right. So for example, if someone comes in and deploys. + +Cheng Wang: I don't know if Kim Jong-un wants that deploy some workload on to Andrew's machine and Andrew's beholden by law to prohibit those types of things as a provider. He should be able to crawl through and see what's actually running and secure himself, right? that's one part. Another part is then how much can the provider see or cannot see that's another component of it and a final part of it is on So this is from the tenant side if I deploy an image and that image is open and public right? I'm less likely to want to push forward. + +Cheng Wang: Push excuse me proprietary stuff that I've worked on because I don't want someone to just steal my secret sauce, And so provide then Secrets right is another important thing. how can I as a tenant secure my Docker image so that someone can't just easily go in and look at what I'm deploying. So those are all things that are being worked on. If you look at in our community board that Huey just drop there and you click into projects like the product engineering roadmap in there. You'll be able to see the items that I just talked about in great detail and all the kind of discussion history and development history associated with each + +Moss Business: Thanks so much. That's a exact conversation that I was interested in was the tenant security securing a Docker and the ability per provider to look inside of the container and stuff like that. So I'll definitely take that combo to the sake the providers say that you mentioned. + +Cheng Wang: For sure, and then follow along in me and the GitHub it's all open. So if you want to look like in history the development Pace what's been done? What hasn't been done what's on whom that stuff should all be fairly transparent there. If not, just hit us up in one of the things we're working groups. And Community will be more than happy to talk about it. And if you have a question just drop into one of those groups in Discord paying the question and off you go. + +Moss Business: Thank you so much. + +Cheng Wang: Pleasure. Thank you. + +Scott Hewitson: Thank you for that question Moss business and thank you for joining the calls. when I was at East Denver I get a lot of questions right all these projects doing kind of the same thing as you guys what sets you apart and I truly believe that something that sets us apart is this open framework where everything is being built in the open? Everyone can verify everything everyone can jump into any call and see what we're talking about? it's pretty awesome. And if you've been in crypto for a while, everything's open source, and the folks that go down that route end up having success where some of the closed systems may not have as much. So I just want to add that little tidbit because it was something fresh at East Denver. I was just there last week. But yeah. so + +00:15:00 + +Cheng Wang: said + +Scott Hewitson: what that does anyone else have any other questions? I mean we can move along from the Pips stuff. Does anyone have any questions just regarding anything or any ideas or things that you might want to see moving forward chain? + +Cheng Wang: Yeah, it's not Andrew No, so I think the one thing that I want I wanted to exactly what you mentioned regarding what you've observed in East Denver and everything. You said regarding our open framework. I want to emphasize to this group and everyone can do their parts and smaller big however, it is right is there's there as this space in right continues to develop there will be and there are and have been a lot of attempted copy cats where people who want to go into the space because that sector is hot. It's kind of like defiles hot. + +Cheng Wang: through the nose, there's so many networks out there. I don't even care anymore with some stuff like I use what I use. I know what I know. I really don't care about the other stuff. It's just all kind of like the regurgitation of the same idea over and over again having said that there will also be a lot of potential projects and projects that come out that are Very vague not transparent we'll make claims and not back them up all that kind of stuff. Right? And for here at Akash, everything is open. We can't hide behind b s right if it's out there it's out there and we have to just kind of deal with whatever the actual realities of it are. So I think for us as a community everyone here if you can do one thing that'll be incredibly helpful is if we can all do our part in this spelling. + +Cheng Wang: False information misinformation that's being spread about a cost potentially out there wherever Twitter Etc where people say this versus the other and just to let you guys know in our conversations with even funds right who are interested in taking a position on a caution and stuff like that. They come to the core team and ask questions. Hey, how do you differentiate between yourself and project XY project Z whatever it is, right and I have to tell you. + +Cheng Wang: The level of sophistication of research from these funds oftentimes. I would say 80 to 90% of the time is pretty poor. if I were a professor grading these assignments, I would probably give them a d to be kind like they should be able to distinguish these things and I think part of the challenges the information isn't readily necessarily out there as loudly and as frequently as we can hope so, I want to definitely ask everyone whenever you can have the opportunity to say something like hey, here's some information.'s whatever here's what I see, back it up with facts and just continue to push that out there and not get into the kind of the Tit for top on vague. Yes, right. So That's the PSA I have. + +Scott Hewitson: Thank you for that ng. Yeah, as you dropping a cheeky note that we can't hide behind you b s your name is BS so, said that throw that out there. Does anyone else have any ideas or concerns or comments in regards to get economics or the token or how things are running? Yes, that's right. + +Scott Hewitson: doesn't look like we have any there is. Go for it. + +Andrew Gnatyuk: Yeah, That's me. I've missed you. So let's meet you all so let's talk. + +Scott Hewitson: All right. + +Andrew Gnatyuk: Yeah, just a question. you do fraction to memory. Where are we right now with the attached economics 2.0? + +Scott Hewitson: 2.0. Let's see. We've done let me just pull this up real quick. did + +Scott Hewitson: so we got take rates implemented right we've got + +Scott Hewitson: I'm just pulling up everything on this. So the + +Andrew Gnatyuk: Take her and make her face, right? Okay, and + +Scott Hewitson: Yes, those are not flowing to stakers yet that all flows to the community pool. So, something that will need, there's the incentive distribution pool planned and that kind of is like the pool for everything. And then from there it goes out to public goods fun providers and is staking potentially burning and then community pool. So right now, In the interest of Simplicity, We've done those take rates to the community pool. Obviously the community pool has been the source of funding for a lot of great initiatives and + +00:20:00 + +Scott Hewitson: it really just is a bottleneck of engineering efforts. We've got a million things going on. So implementing all of this stuff from akt 2.0 is takes time and it kind of shuffles with importance, when we have something for an engineering task. That's the higher priority that gets pushed up probably simply because we're having success. from the economics side and being able to do everything that we need to do is but yeah, I mean there's a lot of things from it, I think. let me just pull up because I want to say the token page on the website has. + +Scott Hewitson: The five things so the main features make it take fees stable payment and settlement those both are live, the incentive distribution pool that is not provider subsidies kind of with this prop and in the public goods fund which is kind of like the community pool. So I'd say it's a Technically two out of five live, but you could probably say a half from some of the other so maybe two and a half to three out of five complete and we're effectively, working most of them are complete but there's some engineering efforts that we that go behind Those modules of creating the different pools and all that other stuff. I hope that that helps any of those little bit of a ramble as I was going back and forth through resources. + +Cheng Wang: That was great I think one thing that I would love to add to that is. + +Cheng Wang: Of the primary features that contribute most to akt 2.0 those have been done. Right? So the take fee being the primary element of it that in and of itself I think is the biggest economics to be frank like the incentive distribution pool and the sub pools. I suppose below that those are all kind of counting stuff like operational things. That'll be nice to segregate going forward when things can be more tidally organized by potential by group and use case. So that's kind of a nice to have at this very moment in time as the community pool and fun continues to grow that will become more important later on because we don't want to have one big bag of money in the community pool slashing around then the mandates aren't that clear Etc though? We've I think work really hard in terms of when proposals the sequ. + +Cheng Wang: Of getting things up on GitHub discussion answering questions and then on chain Etc writing all these things out. I think we've been really good at that. So that's what I want to say. what we've done so far are the most important things that enable economics 2.0 to start running and that has been done the next big things. I think from a feature and usability perspective is some of the behind the scenes stuff then that will make stable payments more useful because right now all the IVC Channel jumping crap, it just makes USC not as usable user friendly as we wanted to be. So that's I think one thing that's currently on the back burner and as he Illustrated when we have enough engineering band with will be tackling that as well. So yeah, and then in terms of the priorities mentioned previously the secret stuff like provider features Discovery, that's another thing that was just pushed out that is a huge blocker that we needed to on unblock in order to have phase two of the pit be possible right because we need to be able to + +Cheng Wang: Providers and say what resources have you brought on and be able to see all that stuff in a database and record and all that good stuff. but yeah, I think the progress there as far as the organization of the IDP and accounts a little bit definitely lower priority because it's just organization at that point and the big thing after that is just again here we mentioned distributions of stakers. that's going to be a big piece. But as both I think we can cross that bridge once usage climbs up, Quite significantly, right because I think we're just at the tip of the iceberg at this point as far as usage on the network goes. + +Scott Hewitson: Yeah to add to that having the take fees flow to the stakers and validators. I think from a retail perspective that's something that people want that we don't have implemented at the moment but to Cheng's point, There's good Network spend but until it's a point where it's significant. It's like all right, I got my hundredth of a cent, from the take fees for staking a bunch of akt, it's not gonna be as a people aren't going to be like, wow, this is awesome until there is significant network activity Network spend. + +00:25:00 + +Andrew Gnatyuk: Yep. Got it. Thanks. + +Scott Hewitson: first Alrighty, does anyone have any other questions or concern Has anyone want to bring up anything Vlogs? Thanks for jumping in. I don't know if you want to throw any words of wisdom or anything. + +Andrew Gnatyuk: Yeah, I still have one concern. I want to ask chance basically let's See it this way on this bull run. + +Scott Hewitson: Okay. + +Andrew Gnatyuk: Let's say akt is pumping right? We're not talking about much on the exact prices, But let's say eight ten bucks 15 whatever. Yeah, and it turns from a security talking right for the network the more office speculative talking and let's say we have lots of unsticking or unbonding and let's say our network has just 30% or 20% in staking. because right now we have 60 and before that we have 75. + +Andrew Gnatyuk: Is why I was asking about the incentivize for the stakers because at the beginning everybody was like we have great APR and we need to stay because that's just like 380 tokens one. once it's just pumping up, right? But the market shift for example in two years and we will have to deal with with this, lots of tokens just freely looking around the success indexes and that stuff and that's what makes basically concerns me. + +Scott Hewitson: Yeah, I think you… + +Cheng Wang: Gotcha. + +Scott Hewitson: it's important to note that there's a Min and Max inflation parameters and it's basically the amount that you're gonna get and from staking rewards is dependent on the amount state. So the less + +Scott Hewitson: staked there are the staking percentage is gonna be that they're all parameters that can be changed subject to governance and they have been changed with governance proposals. But in general, that in the cosmos ecosystem, the less tokens that are staked the town or balance to that is the staking APR goes up. So if you have everybody staked then it's those rewards of split between those that are stake when there's only three of us staked we're gonna get all of those rewards. So there is that counterbalance to come back that but I definitely understand your concern and some chains even they deal have, low staking percentages and low State bonded percentages and really high aprs and it still doesn't incentivize folks to stake. + +Scott Hewitson: So I think that's kind of on the whole network at large to be able to get to a point where we have that big network activity that big Network spend to where ideally, someday most of the rewards that you're getting are from Network spend versus just the inflationary rewards because that everything is in speculative without Revenue coming back from the chain and the network. + +Andrew Gnatyuk: Yep. Got + +Cheng Wang: Yeah. Yeah, I would add to that is. + +Cheng Wang: Just as Huey said and I wouldn't necessarily like just zooming out a little bit. I wouldn't. + +Cheng Wang: Place too much stock in the micro right now from the day-to-day perspective, because right now the market is still trying to figure out where things are right is akt gonna continue to move one way or the other. I don't know the market will do what the market does and on top of that. There are also governance parameters. We can definitely toggle as well. Right? So the inflation Max and all those kind of things that are things that we can definitely toggle to ensure right to if staking rate Falls below certain perspective and point rather and it becomes an actual concern that is shared by, the core team in the community at large something that as a community everyone right can submit proposals to let's say bump inflation up such that, stakers get a little bit more return right on akt though. I would say if you're holding akt return has been pretty good as play not gonna lie. So the knobs right do exist for us to toggle these + +00:30:00 + +Cheng Wang: Particular things one thing I would have to say is finally on this point. If you look at even though bonded Ray has fallen from the 70 percentage to 60% ish the total value Bond, it has gone up significantly, So the economics S in context it's not just the wall percentage necessarily that matters. + +Scott Hewitson: security + +Cheng Wang: I would argue that by having 60% Bond date at this point in time. We're more secure now than we were at 75% simply because the value of network is grown so considerably so it's a lot harder to Do stuff. + +Scott Hewitson: Yeah, the cost to attack in raw numbers has gone up. + +Cheng Wang: for sure exactly it exactly + +Andrew Gnatyuk: Going agree on that. Okay. Thank you guys. + +Scott Hewitson: No, thank you. + +Cheng Wang: always good to voice us. Thank you. + +Scott Hewitson: Alrighty, does anyone else have any last thoughts or comments or concerns? Hey,… + +Andrew Gnatyuk: Yeah, yeah, I do like one last question what direction for you? Let's go. Let's + +Scott Hewitson: We got some time if you got a couple it's all good. + +Andrew Gnatyuk: So the last news from Twitter ionet has raised 300 million to build the largest decentralized GPU Network in the world. And so the AI compute shortage, what's your thought on that? It's basically like GPU Marketplace and Solana. It's not like I'm advocating Savannah right now. + +Scott Hewitson: Yeah, I mean so it was 30 million. Yeah, yeah. + +Andrew Gnatyuk: I'm fully Akashi, I just have this. Yes. It's Because they give it to me and I was just wearing it today. Yeah. + +Scott Hewitson: Yeah, so no, they congratulations to their team. I think it was 30 million that there is but some prominent backers. + +Andrew Gnatyuk: Yeah. + +Scott Hewitson: I mean, everything we do and Greg is pretty outspoken about this. he says anyone who's In the same direction, building for the same long-term goal, it's competition let the protocols, the proof is in the pudding I guess so, it's not that it's a distraction or whatever, we're here to build and we're here to do our thing. if anything it's a validation that people are looking at this there's a need for this and people are putting money behind it. So if anything I think it's good news for Akash that other companies are raising to do what we are already doing. + +Cheng Wang: Yeah, I mean this is a way thing about it again zooming out a little bit. It's trillion dollar market. Let's just be frank. Right and so there's more than enough space for everyone to Palo Al around and so if let's just say you look at the actual true market leader in this space as far as the cloud space goes right and then GPU space if in AMD for example is no slouch and they're still kicking but even though Nvidia is dominating sucking most of the oxygen out of the room, If AWS despite their market dominance is your and gcp are still tremendous players in their own, So there's why I say that only to say the market is very big and it's ripe or people to come in and try to see what they can do and more attention on the space is always a good thing. What I would say is, we've historically shy away from intentionally avoid the language big is fast, whatever it is, right because it's all qualifiers and highly subjective stuff right and again, + +Cheng Wang: The best represent putting right and so we'll see and the market is big enough for many companies to thrive and it's just about getting product Market fit and getting adoption all this kind of stuff. So yeah, it's good to see the space growing. I would just say do your own research, open systems. all of our information is out there information on a lot of the other companies projects, excuse me. Just don't exist. + +Andrew Gnatyuk: Yep, totally agree. + +Scott Hewitson: awesome + +Cheng Wang: and it's cute for them, too. I would just say, we're pretty serious a just saying. + +Scott Hewitson: There's Andrew have any other questions he'd like to ask. But awesome. + +Andrew Gnatyuk: No, I'm good. + +Scott Hewitson: Again, as always it's a pleasure to have these calls pleasure to hear everyone's thoughts. And yeah, I think we can wrap up and As was since he's here. We'll see all in the metaverse. + +00:35:00 + +Andrew Gnatyuk: Yep. you… + +Rodrigo Rochin: See you. + +Andrew Gnatyuk: Bye. Thank. + +Scott Hewitson: Take care. wedding + +Robert Del Rey: You guys thanks. + +Andrew Gnatyuk: I guess. + +Robert Del Rey: Scott & Cheng. + +Cheng Wang: There on thank you. just + +Robert Del Rey: All right. + +Scott Hewitson: Have a good one. + +Meeting ended after 00:35:16 👋 From 1e5199f746fe4eebf094f1ba5cc0fe5b9cab3aa8 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 13 Mar 2024 11:07:29 -0400 Subject: [PATCH 013/138] sig-design Update README.md add meeting date Signed-off-by: Drinkwater --- sig-design/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-design/README.md b/sig-design/README.md index 59f5ccfc..c3c865e8 100644 --- a/sig-design/README.md +++ b/sig-design/README.md @@ -29,7 +29,7 @@ date: 2023-1-09T00:19:20-08:00 | #12| Wednesday, December 13, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/012-2023-12-13.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/012-2023-12-13.md#transcript) | [Link](https://une76rieq3cvbtrnjv3gxaw6kbxaay3tnzqsangya2lfe6ionpva.arweave.net/o0n_RQSGxVDOLU12a4LeUG4AY3NuYSA02AaWUnkOa-o) | #13| Wednesday, January 10, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md#transcript) | [Link](https://zao4urnjuqb6ncx2vacwjuqiyqnucl2ifcfm33blijhw6v6owzla.arweave.net/yB3KRamkA-aK-qgFZNIIxBtBL0gois3sK0JPb1fOtlY) | #14| Wednesday, February 21st, 2024 08:00 AM PT (Pacific Time) | | | -| #15| March, 2024 08:00 AM PT (Pacific Time) | | | +| #15| March 13th, 2024 08:00 AM PT (Pacific Time) | | | | #16| April, 2024 08:00 AM PT (Pacific Time) | | | | #17| May, 2024 08:00 AM PT (Pacific Time) | | | | #18| June, 2024 08:00 AM PT (Pacific Time) | | | From f15234ea01340e9d2ffec31a9cb58500790d8d91 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 15 Mar 2024 02:29:10 +0000 Subject: [PATCH 014/138] Create meeting notes for wg-zealy #7 (#470) * Create meeting notes for wg-zealy #7 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 006-2024-01-15.md add transcript and recording Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-zealy/meetings/006-2024-01-15.md | 374 ++++++++++++++++++++++++++++ 1 file changed, 374 insertions(+) create mode 100644 wg-zealy/meetings/006-2024-01-15.md diff --git a/wg-zealy/meetings/006-2024-01-15.md b/wg-zealy/meetings/006-2024-01-15.md new file mode 100644 index 00000000..20822481 --- /dev/null +++ b/wg-zealy/meetings/006-2024-01-15.md @@ -0,0 +1,374 @@ +# Akash Network - Zealy Working Group (WG) - Meeting #7 + +## Agenda +- Recap of the pilot phase, including feedback sharing. +- Budget and Time Length for Zealy Initiative +- Discussion on the action plan, particularly focusing on mission frequency and rewards payout. +- Progress Updates + +## Meeting Details +- Date: Monday, January 15, 2024 +- Time: 11:30 AM PT (Pacific Time) +- [Recording](https://pwxu73zd32wt2eg5bbao4apsgs6zso2bu4v4ixu2wyf7bv3dbvuq.arweave.net/fa9P7yPerT0Q3QhA7gHyNL2ZO0GnK8RemrYL8NdjDWk) +- [Transcript](#transcript) + +## Participants +- Benjamin B +- George Pro +- Robert Del Rey +- Scott Hewitson +- Ty Wright + +## Meeting Notes +### Progress Updates: +##### Robert Del Rey: +- Shared screen to showcase feedback, ensuring no sensitive information was disclosed. +- Received twelve responses over a two-week period. +- Notable comment from a non-technical participant expressing motivation to deploy on Akash. +- Emphasized the success of onboarding individuals into Zealy, shared the positive impact in Discord. +- Discussions about the missions during the week with Benjamin. +- Some feedback indicated a need for more detailed mission instructions, specifying testnet or mainnet deployment. +- Instead of creating missions from scratch, planning to provide guides on Akash processes. +- Each section of a guide will be treated as a mission, addressing clarity and expectations for participants. +- Emphasized the importance of learning from feedback to improve the mission structure. +- Mentioned the possibility of incorporating both beginner and advanced tasks into Zealy. +- Invited participants to share initial ideas or comments on the proposed mission restructuring. +- Mentioned the potential for more complex tasks in Zealy while maintaining beginner-friendly elements. + +### Monthly Sprints Proposal +##### Robert Del Rey: +- Suggestion to transition from a pilot to monthly sprints. +- Expresses belief in the success of the pilot and the potential for ongoing improvement. +- Envisioning monthly missions with continuous community engagement. +- Proposed ideas like introducing new missions, special Discord roles (Zealy quests, Zealy boss), and showcasing completed missions. +- Shared screenshots of submissions from the "Create your own website and host it on Akash" mission. +- Highlighted the significance of users successfully deploying websites on Akash. +- Demonstrated Discord screen to showcase participant submissions and engagement. + +### Budget and Time Length Discussion +##### Robert Del Rey: +- Transitioning to the next segment focusing on budget and time length for future campaigns. +- Discussing whether to propose a signaling proposal or directly seek funding through the community support proposal. +- Opened the floor for ideas and opinions from the group, considering their perspective on the initiative's progress. +- Asked about their feelings on starting from scratch, having one pilot, payout rewards, and discussing the future. +##### Ty Wright's Input: +- Acknowledged the success of the experiment in creating community initiatives. +- Shared thoughts on the program's design, which was initially a pilot with resources from the community support proposal. +- Discussed the concept of a micro grant program, focusing on smaller amounts for initiatives, potentially up to $2,000 USD in AKT. +- Proposed a discussion on the program's outcomes, cost for the entire year, and mission before seeking on-chain funding. +- Recognized the success of the Zealy pilot, suggesting that it could be a yearly program to bring new users to Akash. +- Encouraged discussion on whether another round of pilot testing is needed before proposing on-chain funding. +- Referenced the recently passed community budget and suggested further asynchronous discussions in Zealy chat. +- Emphasized the presence of enough evidence, case studies, and real-life examples from Zealy to support a discussion and plan for the year. + +### Next Steps: +- Robert expressed having enough data to create a proposal, including stats on rewards paid out, participant engagement, and completed missions. +- Suggested planning for sustaining the initiative for one year, potentially with a second plan for six months. +- Ty Wright supported the idea of moving forward with a proposal and encouraged discussing the budget and outcomes for the program over the entire year. +- Ty Wright proposed engaging in a GitHub discussion or talking to Hewitson and Ty Wright about potential funds for a secondary pilot. +- Ty Wright suggested a quick discussion offline between Benjamin and Robert to decide on numbers and details before engaging in broader discussions. +- Encouraged fast-tracking the process due to the existing case studies and successful pilot outcomes. +- Benjamin inquired about the possibility of utilizing January funds for a quick continuation of the pilot to maintain momentum. +- Benjamin expressed the need for planning details such as the number of people to include in the program. +- Ty acknowledged that Benjamin and Robert have demonstrated the ability to handle various aspects of the initiative, emphasizing the working group's ownership. +- Benjamin suggested involving the working group in planning to ensure agreement on essential details. +- Acknowledged the need for collective agreement among those actively involved and interested in the initiative. +- Concluded with the idea that everyone actively interested in the initiative should have a say in determining fair numbers and statistics for the program. + +### Plan Moving Forward: +- Ty Wright suggested taking a week to devise a comprehensive plan covering management costs, rewards amounts, desired outcomes, etc. +- Proposed presenting the plan either as a draft or in a document format, whichever is easiest for the team. +- Scheduled a working group Zealy meeting for the following Monday to iron out details on the record before initiating GitHub discussions. +- Emphasized the importance of including clear breakdowns of management costs and other details in the GitHub discussions. +- Benjamin confirmed the clarity of the plan, suggesting ironing out details offline before discussing them in the next meeting. +- Opened the floor for suggestions or adjustments to variables such as the number of personnel needed and the amount of rewards. +- Ty Wright expressed the importance of starting from a place where the team feels comfortable and appreciated, rather than imposing arbitrary numbers. +### Rewards Payout Overview: +##### Robert Del Rey: +- Exporting data from Zealy provides basic information in an Excel file. +- Data includes usernames, addresses, and mission completion details. +- Noted the simplicity of the process but discovered a challenge during the second pilot extension. +#### Challenge Encountered +- Participants from the first pilot had existing point balances when the second pilot started. +- Points earned in the second pilot needed to be matched with the existing balances for accurate reward calculation. +- Run a separate export and matched the data to calculate differences between the first and second pilots. +- Determined points for winners who participated in both pilots to avoid overpayment. +- Acknowledged the complexity and expressed plans to improve the reward determination process. +- Proposed structuring missions so that only the last mission provides rewards, simplifying calculations. +- Suggested limiting mission completion to once a month for easier reporting and winner determination. +#### Current Status: +- Confirmed readiness to pay out rewards, acknowledging the need for improvements in future calculations. +- Robert expressed the intention to proceed with reward payouts and announced a brief announcement regarding gathering addresses from participants. +- Raised the question of whether to ask participants for addresses again or confirm existing ones before sending out rewards +- Benjamin suggested allowing participants to change their addresses if needed by DMing before payouts, but otherwise, proceeds should be sent to their provided addresses. +### Rodrigo's Remarks: +- Rodrigo congratulated Robert and Benjamin for their leadership in taking over the Zealy program. +- Initially skeptical due to past experiences with other programs, Rodrigo acknowledged the success and user growth achieved through Zealy. +- Commended Robert and Benjamin for effectively leading the initiative and gaining users. +- Supported the idea of going on-chain and securing funding for the entire year, expressing confidence in the effectiveness of the Zealy program. +- Offered assistance and expressed readiness to help in any capacity to ensure the continued success of Zealy. +- Robert recognized the support from Rodrigo and the entire community in contributing to the success of the Zealy program. +### Remainder of Funds: +- Benjamin inquired about the handling of the remainder of the funds and proposed drafting a proposal for their usage. +- Ty Wright provided two options: either use the funds for new missions or return them for a clean break while planning next steps. +- Suggested discussing further with Hewitson and Ty Wright regarding the decision and ensuring transparency in handling the funds. + +### Other matters discussed +#### Scheduling Next Meeting: +- Ty Wright proposed scheduling the next Zealy meeting for either 9:00 AM or 9:30 AM Eastern time next Monday. +- Robert confirmed the availability of both times and expressed gratitude for the flexibility in scheduling. +- Decision was made to hold the meeting at 9:30 AM Eastern time to accommodate participants' time zones better, especially for Hewitson. +- Robert confirmed the chosen time for the next meeting and expressed gratitude. +- Ty Wright expressed appreciation to everyone, indicating the meeting's conclusion. +## Action items +- Ongoing efforts to enhance mission details and instructions based on feedback. +- Benjamin and Robert to work on the proposal details, including cost analysis and program goals. +- Ty Wright and Hewitson to provide guidance on the budget and funding options. +- Group to initiate GitHub discussions for the Zealy program +- Group to Schedule a working group Zealy meeting for the following Monday to discuss and finalize details on the record before initiating GitHub discussions. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Robert Del Rey: All right, and happy Monday everybody. Welcome to the silly working group called This is the first one we have on 2024. We are almost three weeks in 2020 24 things are going fast. But yeah. Let's make it happen. So as I was saying earlier. I want to discuss two segments. I want to divide this whole into segments unless you want to add anything else to the agenda. But these are the topics. I'd like to go over in today's call. the pilot we had the second phase we ended and we also share a feedbacks form. I'd like to go over some of the feedbacks. That is 10 just that can be in the recording and you can see the updates in the future. + +Robert Del Rey: Also, I'm gonna discuss the action plan that we have for the action plan that Benji and I discussed this week about how the missions are going to look from now on. This includes the amount of missions and the frequency that we're going to release missions. Lastly the rewards payout we were doing the calculations and yeah, we're almost ready to pay out the rewards. We're gonna discuss that in a sec. And the next segment it's gonna be about budget and time length for the Sealy initiative just for next campaigns determine if we want to do this for three times in the year for times we want to do this every month. That is the other segment about so that we can prepare better. + +Robert Del Rey: To release this to the broader Community as far as proposal goes and discussion goals. I like to go over those topics. So yeah. If you guys have another topic that we can add to the agenda now will be a great time to drop it or you can also drop it in the chat below. I will give you one to two seconds, right? + +Robert Del Rey: Alrighty. Let me bring up my notes. I will also go ahead and share the screen real quickly. So you can see some of the feedbacks there is no personal or sensitive info share in this form. So I will go ahead and share the screen. having said that all right. So yeah, we got five responses In a two weeks period which I find cool. We have a few comments as you can see one of the question is what were your key takeaways from this event. And for example, this comment says I'm a very thick not a very technical person but this event encouraged me to actually try to deploy various things on a cache. + +Robert Del Rey: Learning a few things in the process and definitely will use a cash if I ever need to run some workload in the future. I'm considering for a website llllms mbpns. I love this comment is crazy because the intention we initially had and Benji. It's a witness you Tyler our witness, right? The mission we had was onboarding people into Sealy and I believe this feedback. it's a great one. I even share it in the Discord. if you go below we have other comments we have and additional feedbacks on the missions and this one we're gonna have more details actually Benjamin. I went over during this week why we were chatting about the missions and one key comment. + +Robert Del Rey: Is the missions can be more detailed, some of them had clear instructions, but it wasn't clear what we were expecting some had clear so we're not clear if we were gonna be on test net our main net if I gonna deploy these forever. I have to run this forever or if I just need to run this take a screenshot and then submit the screenshot right? We'll learn a lot in the process. So one of the solutions benjamini came up with instead of coming out with missions out of our minds. Is that we're gonna get guides about how to do certain process on a cache. + +Robert Del Rey: And we're gonna divide that guide in some sections and each section is gonna be a mission. For example, let me give you an example. There is one guy. It's about creating a basic web app in Python and deploying it on a cache sounds really cool. Right so. + +00:05:00 + +Robert Del Rey: It got three steps. So each step is gonna be a For example, the first mission for this one. It can be the requisites that you need to do this. So to ensure that you can follow along the guide you need to use Python you need to use Docker maybe you might need to use visual studio, right? + +Robert Del Rey: And you need to get that and create that account before getting it started. So the first mission could be that and when you do that mission you will have access to the other Mission which is about creating the environment. The next mission is gonna be creating and testing the web app. maybe we believe that doing the missions that way people are gonna learn even better. The missions will be funner more fun, I guess and everything's gonna be clear in a sense that you're gonna know the step you're currently on. And when you do it only when you do it, you're gonna be doing the next step. + +Robert Del Rey: And maybe finally when they complete all the steps and follow the guide to completion that's the time where they can claim the required and that way it's gonna be easier for us calculating the rewards which was another whole new mission for jamin. because on how silly exports that data if that's a right way to say it. I know I said a lot so far in this introduction. I don't know if you guys have a question or if I should go ahead and continue with my talking, but maybe I'd like to know if you have some initial ideas on how the missions would change now. + +Robert Del Rey: If not that terrifying guys, if you have any random comment, just popping up just drop it in the chats or in the CD score. But yeah, that's one that was about. The feedback we got. And I also about how the missions are gonna look based on that feedback. We want to keep making this environment fun and learning for everybody. I'm pretty sure we're gonna have time and a space for more complicated tasks. + +Robert Del Rey: I don't see why cannot add those into silly to and complement them with also The Beginner's task that I was just talking about. But really nice. Also, we're thinking that that is an extreme just to make it easier for us and to keep track on the Sprints the rewards the money. All of that. We also believe that if we run the Sprints in a monthly basis. + +Robert Del Rey: Instead this was a pilot, right? But based on what we noticed on the Pilot We believe that during this into something that we come up with New Missions to do every month and we keep the ball rolling like you say guys doing monthly different missions and having different people do the missions and complete them and give them A special roles on Discord like silly quests computer or silly boss. Those are many years I'm just trying to say that Benjamin. we see a great future in this first pilot was super successful in very knows some of the things we can improve and also let us know they're real power that is behind this because I don't know if you also so the screenshots that I share on the + +Robert Del Rey: on the silly these courses about some websites people did I don't know if I can share this in the screen. do you still see the form or you see these corner? + +Benjamin B: I still see that. + +Tyler Wright: Still through the form. + +Robert Del Rey: Yes because I share only that is really nice. Stop sharing. one second guys + +Robert Del Rey: We're live, Just commented the window. okay here you can see my Discord you see it. people awesome. Thank you so much. So these are some of the submissions we got for create your own website and host it on a cash. And yeah, it might not be the bestest graphic designs in the world. But what for me they look beautiful man because these are Creations people just + +00:10:00 + +Robert Del Rey: and design these got the info they needed they put on a cash and did their submissions and for me that is I don't know. it was really good. I mean, I bendy saw it first when he was reviewing the missions, but when he shared that with me, I was so blown away, even though I don't understand anything that says here and overall how people were able to I don't know. Maybe they had this going and they just move it to a cash. I don't care. Maybe they did it from zero. I don't mind but the key thing is that they were able to deploy the website on a cache or run the website on a cache. + +Robert Del Rey: and yeah for me that was super powerful and we want to do more of that in the ceiling. So yeah, just let me move on a little unless you guys have any other question about the feedbacks. We got the action plan. We got for the missions. I will go ahead and briefly talk about the rewards payout I don't want to get in many super profound details because Yeah, how would you export data of silly you click on export members exports data and you're gonna get an Excel file and there you will have the username if they sign up with an address. You will see the address you will see how many missions they did in but I guess it's accurate to say that it's super basic. + +Robert Del Rey: However, it's that basic that we discover something while doing this pilot and when extending the pilot. so the first time we did it we didn't have Anybody doing the missions so basically everybody started from zero when the first pilot ended. We just exported the data and it was super easy to see how much everybody won for the missions. + +Robert Del Rey: However, the second time we did it exactly we run the second screen people have started doing missions. and those that already did missions were getting The points to do for doing the second pilot extension, And those points were being added to their previous Point balance that they have from the first pilot. So ported this info again when the second pilot ended We explored the info again and everything was at it to the final result. So basically we had to run a separate. We got to export the info again, and we basically kind of matched it with the first export with it. And we calculated the difference in rewards between the first time people did it. + +Robert Del Rey: And the second pilot we also had people that only got rewards from the second pilot those were easy to discover because it was their first time they were beginning from zero. But we by doing this matching and subscribing subtracting. We were able to determine the points for winners in the second pilot that also want something in the first pilot. + +Robert Del Rey: And we were able to determine the exact amount that they won. So we won't be over paying them. We were able to get calculation. we learned the way to do it. I don't know it's queer complicated. It definitely can be proof. I guess Benjamin's talking about modifying some script. So yeah, I'm pretty sure we're gonna overcome that in and make it easier to determine the rewards for next time. So the possible solutions would be like what I say before we can structure the missions in a way that only last mission when you complete the process of tasks that last mission is the only one that is gonna give you the prices. + +Robert Del Rey: and the other making sure missions you can do them only once a month. So we have that report once a month. It's also gonna be easier to determine the winners and then Those are easier to find they're not winners. But yeah, that's the situation with the rewards payout. I guess that we're already have the final number. Im sorry. I just haven't said that. I'm a site to pay out the rewards. So that's on me. High honestly, but yeah, that's the situation with the rewards right now and that's gonna be for the first segment of this goal feedback's Mission action plan and the rewards payout. Do you guys have any questions about what I just said + +00:15:00 + +Robert Del Rey: in the meantime, I'm reading what Benji sent in the show. So I can modify the script I made to save price information. To make sure this doesn't happen again. Yes. Sure. And yeah, I'm pretty sure we're gonna find a way I don't have about it. It's just that it's crazy. How the more we get involved in this the more we learn about it, right and more things we discover along the way trust me. If you ask me about all of this three months ago, I wouldn't be able to answer you health of the questions. and yeah, I'm sure we're gonna get that sorted out. + +Robert Del Rey: My dad, It's been a while experience. So that's why I want to really discuss the next segment of this call, which is about the budget we're gonna have for this and the time length for the next campaigns and if we are gonna have a signaling proposal to see how the community feels about it, or if you should just go straight away. + +Robert Del Rey: And ask for more funding from the community support proposal the best way to go forward. I don't know. I'm just like setting the pace now I love to know some of your ideas Maybe you Thanks for working on a holiday. Thanks for having time with us. Maybe you can let us know. How do you feel about all of these as an Akash team member as a core team overclock team. Sorry as in a cash. Call Robert Clock Team. How do you feel about seeing these initiary from zero maybe having one pilot pilot to paint out rewards and now discussing about the future. How do you see it as a court team member And how do you sit in the future starting from here? I guess that's my question man. + +Ty Wright: Yeah, no, I think. This has been an ideal kind of experiment in. + +Ty Wright: Just creating Community initiatives, obviously there's been a number of technical ads but I think this kind of programming. I know it's something that Adam wozni has thought about a lot, Huey and myself and other members of the core team and also thought about a lot is empowering folks like you Robert who are very involved and have great ideas and they're creating kind of programming that's going to get folk other folks like yourself and other new users, that can potentially be inside which vanguards Etc. So, at the highest level, I think this is been a success obviously who Akash have now been, inspired to use it through this program. I think it was always designed to be a pilot, where the resources came from the community support proposal. + +Ty Wright: I don't know how you all want to move forward really the idea around the community support proposals for smaller items smaller. Bounties and rewards that are less than 500 dollars in akt, kiwi and I want to put forth a discussion. I would involve other members of the community to create a program that would really be a micro grant program. So no amount larger than maybe two thousand USD in akt, but the goal is to really push initiatives this right before. a proposal like this, which I think should eventually go For a discussion and then on chain to get funds for the entire year. + +Ty Wright: You don't know how these programs are going to fair. When you think about them. I think before diving into a community pool. It's great to be able to Pilot some of these things and test how successful some of these programs could potentially be I think it's what we did here and you and Benjamin have been great leaders and have shown all right, zealy is a platform that people will use isn't something that can grow. something has legs and we can use In my opinion the successes of the pilot. In a discussion that can start like hey, this is what we think it'll cost for the entire year to run this program. This is the outcomes. We think this is the mission of the program and again with the Wind from the pilots. I see. No reason why this wouldn't pass and just be a yearly program, that would be another way to bring new. + +00:20:00 + +Ty Wright: users onto the Akash platform so that's how I think about it. If you all think that it needs another round of pilot before it potentially goes on chain. I can talk to Huey because I believe the community Budgets just passed last week so we could talk about using potentially some funds from January to continue on with the pilot. We can continue that conversation async maybe in zealy chat. But again, whether it be like the case studies or the feedback that you just got or, examples of some of The real life thing that people have done on zealy. I think there's enough evidence and there's nothing this way more than enough of a case. + +Ty Wright: To put a discussion on to to create a plan for the year, and figure out how much + +Robert Del Rey: awesome No,… + +Ty Wright: I know I said a lot so I apologize. + +Robert Del Rey: I did you said. What's great? Thank you. You were more that bad enough. it was actually exactly where I wanted to go. what in thought could start gathering for all now on so when we come up with a discussion, we have enough to get proposal. I got a few stats like the numbers of rewards paid out how many people have engaged in missions how many missions were completed? So I guess we're gonna think about how much will it cost to outdo sustain this for one year maybe have also a second plan for six months and share that with you guys and go from there what you say and also adding the real life examples that you say by the end. + +Ty Wright: I + +Ty Wright: I think for me that's the best step forward again. Benjamin and Robert you have shown the leadership, to kind of run this program and continue moving forward. So from management standpoint, I think we're in a good place. It's just about what those missions are and this a really defining what the program is and what success could look like for the program over the course of the year, + +Robert Del Rey: awesome time Thank you. Benjamin if you want to jump into the common now, maybe you got some extra comments. You want to say see you in the comment Rodrigo actually assisted some people In the first stages on the pilot. So rather maybe if you want to share anything feel free to drop so to do so I'm just talking right? I got to direct this but this is basically Open Mic if you want to just jump in and say anything just do go ahead Benjamin. So your hand first. + +Benjamin B: I think a great way to continue Just discussing should we have the main discussion being GitHub? Where should we try to agree on numbers and the details here? What do you guys think is the best option? + +Ty Wright: it's my opinion that from a leadership standpoint. Maybe this is something you Benjamin and Robert could talk about offline and then can have a discussion if there is a desire to Support funds for a secondary or a third pilot, talk to Kyrie and I about it and then if not, then I think it should just go up and GitHub discussion. + +Ty Wright: and frankly if you want to put up in a GitHub discussion before and the next steering committee meeting, that also might be good because then again we can kind of fast-track this because again, we already have case studies and proof in the pudding from the pilots. + +Benjamin B: Yeah, I think it makes sense to do either one or two of those because I don't think this should be living off that proposal forever. And we're trying to plan some of the details of time me and Robert's already but basically what you're saying is that we should try to come up with some details. Of exact numbers of them we can move forward with discussion. + +00:25:00 + +Ty Wright: Yeah, I think we can move this very quickly. The only reason why I say it might be if you all decide hey can we have 1,000 or 1500 dollar USD in akt from the January part of the community pool or Community Support budgets because we don't want to lose any momentum that we had over the last couple of weeks and we feel like we have a good momentum going and that would make sense. If you feel like the momentum wouldn't be lost and you all could wait a couple of weeks until you figure out a long-term plan like this as Robert just said it could be you all figure out what a plan for the year looks like, but then you're just asking for Quarterly, Chunks on chains similarly to what? + +Ty Wright: the overclock team does with and what Adam does with the events proposal, you have a signaling proposal proposal for the whole year and then you have a community spend proposal for every quarter. You can do it that way or it might just be easier to just manage it for the year and get that money up front, and obviously depends on how much money you all think this program needs and obviously Huey and I can help with the budget if you think hey his x amount of dollars too much we can say can we do it for cheaper or no to make that it makes sense, so we're certainly a sounding board. But I do think you all have shown the ability to own this outright, Where everything from again? + +Ty Wright: Building out the missions, following up with members of the community judging the missions and paying out you all have shown the ability to handle that so we should continue in that same thing. + +Benjamin B: Also, thanks for that answer. I think that we can definitely do that and While I don't see needs to take you more and do it instantly maybe Robert wants to do that. I think that we need some help to figure out really some things. how many people should we? It's fair to include in this program. the hackathon the proposal is currently asking for free people and then How much is fair to ask per person? I think those details are nice to agree upon in the working group called + +Benjamin B: because sure mean Robert can just figure something out and then people can say yeah, we kind of agree we don't agree but if something can be agreed upon in this meeting that would mean that at least everyone involved and actively interested in this no start. Yeah. we all think this is fair. + +Ty Wright: That makes sense. I guess from that standpoint. Maybe you all take the week to kind of devise a plan that would include management costs like everything, rewards amounts, desired outcomes all that kind of stuff and it could be presented either get a dish draft or it could be in a dock whatever is the easiest for you all and then we can have a + +Ty Wright: working group zealy meeting same time next Monday where we iron out all these details on the record before putting it on GitHub discussions, and obviously the GitHub discussions would include those details This is how much it costs to manage this program and it'll just be broken down there and so be very clear to everybody but we'll also have again next week's conversation on the record where the participants all agree to what we think is fair for all those things. that Benjamin is that more of a clear plan moving forward. I know Rodrigo has his hand up. So I apologize for keep. + +Benjamin B: Yeah, I think that's more clear. So we give iron out our details of line. and then we discuss it in the next meeting if you feel like there is a need to adjust it or should we we could just next meeting try to I don't know we could have this variables for every single thing. We can say we think that we need two or three people for this. Then we should be good. We think we need this amount of rewards and then we could discuss everything because I don't know if you want to bring in suggestions in anything or if you rather want us to just yeah, we think we need this. Do you think this makes sense? + +00:30:00 + +Ty Wright: Yeah, I think everybody circumstances are different and I'd rather start from a place of this is where you all feel comfortable and feel, appreciated and can do the best possible effort versus us, trying to put some arbitrary number for some dollars and sense of theoretically we don't control, you know what I'm saying? So we're just working alongside you + +Benjamin B: Also, I understand though. Maybe we should let the Rodrigo take the mic. + +Ty Wright: Yeah, sorry Rodrigo. + +Rodrigo Rochin: It's no worries guys where the love hearing all this? Just wanted to I raise my head because I want to congratulate both Robert and Benjamin like it was already mentioned You took over the Sealy program and are the leaders here? to be honest, I was a little skeptical at first about silly. Because from it my experience with other silly Quest or provincial. I don't know what you come. I've seen lots of scammers and what we saw another dead Nets and with the faucets which were abused and honestly at first I thought some of the missions were a little overpriced or over rewarded but it does look like + +Rodrigo Rochin: we actually gained some users from it, which I truly didn't expect as many but it did see it we can see in this court. I mean we have a lot more users. I'm sure many of them came from silly. and I said, I wanted to congratulate you and I think that what Tyler is saying that you can get a + +Rodrigo Rochin: I mean this going on chain and getting the Grand or funding or whatever you want to call it for the entire year would be great because boy it does seem like the silly program works. I try to participate that at first but then over the holidays and things I haven't gotten a chance to complete some of the tasks and everything, but I don't know how many y'all have anymore, but that's wanted to conqueria. It seems like it works. and if I can help on something, I'm ready to help. And yeah, let's keep it going. + +Robert Del Rey: Thank you so much for other youth Amendment. And also thank you for your support. I remember when I was trying to do the cloud of stuff like recording with a cash Builders and contributors Rodrigo was actually one of the first that raised his hand to help me out and we recorded something there. It seems like it was a while ago, and it was just like last year, but thank you so much for your support buddy. You awesome and also the rest of the cash community. + +Rodrigo Rochin: Here with magnets took over this you all you and Benjamin are the leaders here. You started you didn't own you. I think it was Adam or maybe Tyler mentioned that this is the first time the community actually build the program on their own. Done it great. + +Robert Del Rey: Thanks, brother. So you Wake up guy? I don't have. No more topics to this cause I do have some homework from this call and just for the recordings I go ahead and pay out the rewards now. We'll do a brief announcement. We'll gather the address that I need to gather because people want prices now For the first time so I need their addresses people that won in the first pilot and then one in the second. I don't know if I should ask for addresses again or just confirm with them. Hey, should I send the prices to this address? I don't know what you think about that. Go ahead Benji. + +Benjamin B: I was planning to say something else, but I think in that case you can say something like if you want to. Change your address, Please DM me before the payouts. They were something so they have the opportunity to change it. But otherwise just send it to their address. And what will I was going to ask Tyler here… + +Robert Del Rey: awesome + +00:35:00 + +Benjamin B: because you and Scott are in charge of the other proposalis. And what should we do with the remainder of the Farms? Should we? Draft our proposal and basically if it passes. and we keep them and if it doesn't pass we send them back or what do you think is fair + +Ty Wright: I think either you can do one or two things. I think you can either add new missions and continue on taking those funds towards those New Missions while we put the community pool proposal on or if you just want to have a clean stop right now while you figure out next steps this return it and then I feel strongly that things will move forward, and there's got the fun at that point, so it's just cleaner. That's what we do there was a bunch of community resource funding from last year. And even though the proposal asks for this year. We just return that last year and then we got the new funds this year. It's just much cleaner and just transparents. so short answer is if you want to use those funds to continue on with zealy feel free to do so, if you want to have a clean break and just pay out people for Pilots one and two right now, then just return them to Huey and you can talk to Huey offline about that. + +Benjamin B: Yeah, me and Robert can continue the discussion for sure. + +Ty Wright: all the other thing is I let me know if you want to have the zealy meeting next Monday at 9:00 am or 9:30 Eastern. We usually have the website meetings 9:30. So that's why I might have had it for 9:30 as opposed to die. I apologize. But let me know what time you want to have the meeting next week and I'll add it to the calendar and then we can go from there. + +Robert Del Rey: here What when did you say you have the website call? Sorry. + +Benjamin B: for me or go first + +Ty Wright: I usually have nine thirties on Thursday and I like the per half hour because if we have people in I don't know it just gives people an extra little bit of time especially Huey because he's in Central Time Zone. So it's really even 8:30 versus 8… + +Robert Del Rey: Mm-hmm + +Ty Wright: if we could do it at 9:30 next week. I think Huey will have more time if not at this time is too late for some folks and we can do it earlier and just how this work with you we offline to make sure that it's available. + +Benjamin B: This time works for me. + +Ty Wright: Okay. + +Robert Del Rey: So this thing works for me to I thank you. + +Ty Wright: Yeah again,… + +Robert Del Rey: but Sorry,… + +Ty Wright: I just want to go ahead. + +Robert Del Rey: you were suggesting to change the day from Monday to Thursday. So here we can join right? + +Ty Wright: No, I'm suggesting just to change the time the day could remain next Monday, but instead of 9 am… + +Robert Del Rey: Not okay, okay. + +Ty Wright: which I think we've done meetings in the past at Eastern 6 AM Pacific now we're going to do it at 9:30 because that gives Huey an extra hour or excuse me extra 30 minutes because she's based in a later time zone than the East Coast. So it's earlier for him that is for the rest of us. + +Robert Del Rey: Good. + +Robert Del Rey: Okay, okay. Thanks, Yes, so I said it again. Yeah this time works. + +Ty Wright: So we'll do next Monday at 9:30 AM Eastern United States time and all of everybody can translate that to their local time. So I guess start talking at UTC. I apologize. + +Robert Del Rey: That's cool. I learned talking UTC because of working remotely honestly. + +Ty Wright: he + +Robert Del Rey: But it's still sometimes I struggle so just send the invite and if it doesn't match we just complaining this girl,… + +Ty Wright: Perfect. Yes exactly. + +Robert Del Rey: Awesome, so I don't have anything more guys. If you have something more to add I guess it's the time to drop it now. If not, I guess we can wrap up this call. What you say? + +Ty Wright: Appreciate y'all. + +Rodrigo Rochin: Okay. Yeah for sure. + +Robert Del Rey: Hey Ty. We appreciate you. + +Ty Wright: presentation + +Robert Del Rey: Thank you so much for your help and setting up these calls. All right other. Thank you for joining Benji. And thanks everybody for joining this call and listen in the future until next time right as stay safe everybody. + +Ty Wright: Absolutely. Hey Roger. + +Benjamin B: Yeah, thanks everyone. + +Rodrigo Rochin: but you Yeah. + +Ty Wright: If you can hear me, let's talk offline about that discussion that you put forth on GitHub. So I think that's a really interesting idea. So I'll follow up with you probably tomorrow about that. + +Rodrigo Rochin: awesome, as am I thought we were going to talk about it on I don't know what to call it the community the one we're really discuss the GitHub discussions. + +Ty Wright: Yeah, the steering committee. + +Ty Wright: Yeah, yeah. + +Rodrigo Rochin: That during Community… + +Rodrigo Rochin: which I think you moved it to end of the month. but ready to talk to you too. + +Ty Wright: Exactly this I got the sick last week. + +00:40:00 + +Rodrigo Rochin: Glad You think it's a good idea and I think it could benefit the network as well. We will get new providers and that see what happens. + +Ty Wright: No exactly. I got some ideas. So I'll follow up and stuff some time with you this week to talk about that in more detail. All right,… + +Rodrigo Rochin: Awesome everything. Thank you. + +Ty Wright: appreciate y'all. Have a great day. + +Rodrigo Rochin: same here, but + +Benjamin B: You too. Bye. + +Meeting ended after 00:40:40 👋 + From 4676fdba06e6d54adaeaa8ca933d62ecc5eeab4f Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 15 Mar 2024 02:31:27 +0000 Subject: [PATCH 015/138] Create meeting notes for Wg-zealy #8 (#473) * Create meeting notes for Wg-zealy #8 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * wg-zealy Update 008-2024-01-22.md add transcript and recording Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-zealy/meetings/008-2024-01-22.md | 487 ++++++++++++++++++++++++++++ 1 file changed, 487 insertions(+) create mode 100644 wg-zealy/meetings/008-2024-01-22.md diff --git a/wg-zealy/meetings/008-2024-01-22.md b/wg-zealy/meetings/008-2024-01-22.md new file mode 100644 index 00000000..f6b93c2e --- /dev/null +++ b/wg-zealy/meetings/008-2024-01-22.md @@ -0,0 +1,487 @@ +# Akash Network - Zealy Working Group (WG) - Meeting #6 + +## Agenda +- Briefly review the purpose of the Akash Zealy initiative and its successes to date. +- Discuss cases of suspected users abusing the system and share details about any rewards withheld due to suspicion. +- Introduce the new tiered mission structure for February. +- Present the draft proposal based on the pilot results and discuss the proposal's key points + +## Meeting Details +- Date: Monday, January 22, 2024 +- Time: 6:00 AM PT (Pacific Time) +- [Recording](https://4dq4pkkqqmljo2ukbfplejfpdjw2itvunyzo3hf24zra73afipwa.arweave.net/4OHHqVCDFpdqiglesiSvGm2kTrRuMu2cuuZiD-wFQ-w) +- [Transcript](#transcript) + +## Participants +- Benjamin B +- Robert Del Rey +- Rodrigo Rochin +- Scott Hewitson +- Tyler Wright +- Крис Тофер + +## Meeting Notes +### Progress Updates: +#### Robert Del Rey: +- Robert Del Rey informed participants that the second pilot had concluded on January 5th. +- Mentioned a delay in reward distribution due to holidays and transition back to work. +- Discovered two users sharing a similar email address, raising concerns of potential abuse. +- Discussed a case of a user with a display name discrepancy on Zealy and Discord. +- Shared screen to illustrate the document and highlighted the issue with the letter "e" in the username. +- Created a specific mission for the user to claim the reward and resolved the issue promptly. +- Requested Benjamin B to provide details on these abuse cases. + +#### Benjamin B +##### Rewards and User Behavior +- Benjamin B provided further details on additional abuse instances. +- Shared screenshots indicating a user, NinjaBus, with multiple accounts attempting to claim rewards. +- Noted that NinjaBus and Alphotox accounts were flagged as potentially linked due to duplicate activity. +- NinjaBus claimed to be brothers with Alphotox, raising doubts about the legitimacy of their claims. +- Scott Hewitson shared insights on common patterns observed in testnet scenarios regarding duplicate accounts. +- Emphasized the importance of scrutinizing claims and paying out rewards based on the highest legitimate account activity. +- Robert Del Rey clarified that while NinjaBus was paid in the first pilot, no rewards were issued for the extension or the Alphotox account. +- Benjamin B acknowledged the lack of established rules during the pilot phase. +- Benjamin proposed implementing a maximum one-account policy per household or device in future iterations. +### New Missions Demo +- Robert presented a demo of the new missions format for the Akash Zealy initiative. +- Robert showcased the quest board on the Akash Network dashboard with draft missions. +- Robert explained that the missions were not colored because they were not yet active. +- Introduced the concept of an introductory mission, demonstrating how participants could download programs and submit their Docker setup ID to claim the mission. +- Discussed the possibility of auto-validation for certain missions to streamline the process and avoid wasting time. +- Benjamin B expressed approval of auto-completion as long as it didn't exceed the budget. +- Robert demonstrated the customizable options for missions, including quizzes and cooldown periods for retry attempts. +- Robert continued with a demonstration of the subsequent mission, focusing on creating and testing a web app environment. +- Highlighted the importance of following the guide sequentially for successful completion. +- Invited input from Scott Hewitson, Tyler Wright, and others on desired developments within Akash for future mission focus. +### Feedback on desired developments within Akash for future mission: +- Tyler Wright expressed appreciation for the demo and shared high-level thoughts on the goals of Akash Zealy. +- Emphasized the importance of finding and engaging power users within the community, leveraging Zealy as a vehicle for community growth. +- Highlighted potential focus areas such as dockerizing specific layer two projects and running AI models on Akash. +- Scott Hewitson affirmed Tyler's points and thanked him for the comprehensive overview. +### Final submission requirements for New Missions +- Robert continued the demo, presenting the third mission, which focused on containerizing, testing, and uploading the application to Akash. +- Robert explained the step-by-step process, including creating a Docker image, running it on Akash, and the final submission requirements. +- Raised the question of the best method for submission and sought input from Benjamin B. +- Benjamin suggested collecting usernames for the first mission to track success, allowing screenshots for the second mission (optional), and proposing guidelines or screenshots for the final mission. +- Acknowledged the possibility of rewarding the best submissions and conducting a review process for the final mission. + +### Draft Proposal +- Benjamin presented a draft proposal outlining the Akash Zealy initiative, its pilot results, and plans for the future. However, it wasn't ready for public sharing yet. +- The group agreed to prioritize discussing expected outcomes and resource requirements for the program. +- Initial results from the pilot were positive, with some increased Discord engagement observed. +- Robert suggested shifting the focus from "Zealy" to a broader "developer onboarding program" to avoid confusion and gain wider community support. +- Benjamin proposed exploring options beyond Zealy for specific initiatives, such as sponsored contests, to attract different developer segments. +- Scott Hewitson suggested framing the program as a way to bring in new developers, leveraging the pilot's success. +- Rodrigo Rochin shared his initial skepticism about Zealy turning positive based on pilot observations. +- He suggested exploring other platforms or tools with a higher concentration of developers for future initiatives. +- The group acknowledged the need for a clear and concise program name that resonates with the wider community. +#### Tyler Wright's Input: +- Tyler emphasized the importance of focusing on developer onboarding while acknowledging Zealy's utility. +- He highlighted the need for a clear path for Zealy users to transition into deeper community engagement, such as hackathons, working groups, or joining Discord communities. +- Tyler stressed the importance of showcasing Zealy's effectiveness in driving participation in existing community programs. +- Robert acknowledged the need to retain the talent attracted through Zealy missions. +- He emphasized the potential to transition users from Zealy participation to becoming insiders, vanguards, or active community members on Discord or other platforms. +#### Funding amount: +- Initial proposal: $2,500 per month for rewards ($500/week for 2 users). +- Discussion around confusion between weekly and monthly calculations. +- Benjamin clarified the proposal is for $2,500 per quarter, not month. +- Scott suggested using the full $6,000 per quarter for rewards if possible. +- Overall agreement that the requested amount is reasonable. +#### Proposal presentation: +- Robert plans to present the proposal to the steering committee on Thursday. +- He will incorporate feedback from the call, including: + - Highlighting the broader "developer onboarding program" focus. + - Clarifying the use of Zealy (might explore alternatives). + - Elaborating on rewards and their purpose. + - Emphasizing the goal of retaining participants beyond the program. + - Adding information about onboarding experience, marketing, and post-program engagement. + - Highlighting desired outcomes, such as attracting more developers like Robert, Benjamin, Rodrigo, and CJ. +## Action items +- Group to Establish clear rules and guidelines for future inititiatives to prevent abuse. +- Continue refining and finalizing missions for publication on the Akash Zealy platform. +- Tyler Wright and Scott Hewitson to provide further input on the draft proposal.. +- Group to Consider renaming the program to "Developer Onboarding Program" or similar. +- Explore additional engagement strategies beyond Zealy missions +- Benjamin will update the proposal based on the call discussion. +- Robert will present the proposal to the steering committee on Thursday. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Robert Del Rey: All right, and we Off to the Races Thank you Tyler for the reminder and start recording and Everybody that is here in this call Happy beginning of the week and those listening maybe later. Welcome to the cash silly working group call where we discuss all things about the cash silly initiative. and that the year with a successful pilot and we are in plans of how this is going to look like for the remaining of the year or for the next few months. I guess this call is going to be great to decide a few things. And I wish her the agenda have with you and if you want to add anything to be agenda, feel free to drop it in the chat, or just let me know. + +Robert Del Rey: Things I want to cover is the rewards paid out and users and abusers. We got a few cases of maybe people trying to abuse the system and we want to talk about those so we can learn and see how we can manage those. In the next location I can say right away that we haven't paid anybody that we got that we are suspicious on yet. I wanted to wait for these calls so we can all discuss it and maybe get to a consensus the next Topic in the end is gonna be the new missions that we have planned for the month of With the new structure and everything it's gonna go in levels. You're gonna do one Mission then another and then the last mission is gonna be the mission with the rewards. it's gonna be fun. + +Robert Del Rey: In the last topic of the agenda. it's raining a lot here guys. I don't know if you can hear it. What is crazy? the last topic of the agenda is gonna be the proposal exposition. we were able to craft a draft with the results of the first pilot how we got there how we ended it and how we plan to continue and how much it's gonna cost. We have Initial Ideas so we can start the real discussions. So yeah, those are the main topics I have unless I think about anything else if you guys have another topic like I said drop in the chat, if not, You can tell me now. If not, I can just go ahead and start right in. + +Scott Hewitson: Sounds good. + +Robert Del Rey: I said thumbs up. Scott said sounds good. So we have the blessing now. Let's do this. So guys the second pilot ended. On January 5th because of the holidays and other works and that transition period between the holidays and start working again, We waited a few more days to pay the rewards. And just last week I made the announcement that We got the numbers ready for the rewards. In that document we found two users that share a similar email address. And maybe Benjamin can share more details about these abusing cases. + +Robert Del Rey: we haven't paid at that person yet, but that was something that happened. We discovered two identities. That was one of the interest instances. and other two There was one girl that I couldn't find in the document in the Winner's document. + +Robert Del Rey: But then I was able to find her in the first winner document. So in the first pilot, she actually won a few akt and I checked the history and whatever and we never paid her that But she trying to claimed that last Friday, so I was trying to find her in the latest document that the winners document number two for the second pilot or the extension of the pilot. Sorry, and I didn't find her in that extension document but I went to the first document and I found her there. So I paid the rewards it was a 10K 18 rewards. That was an easy one. The other one was one guy and I'm going to share the screen for this. + +Robert Del Rey: the second guy there was a discrepancy in the user. on silly and the user also for the document so in the document + +Robert Del Rey: Let me see if you can guess you can see my screen. Yeah. I'm just showing you silly. + +Benjamin B: Yeah. + +Robert Del Rey: So I won't show you the document in this way. Let me do it again. I'm so sorry. + +00:05:00 + +Robert Del Rey: I'mma just go with the entire screen and screen too. All right Okay, you're gonna see my beautiful background. This is something you don't know about me. I love geography like you have no idea guys. and this is one of the best backgrounds I have. I don't know if you can see it. But what I wanted to show you was the winners document to this is the results. It's in my notion. Let me know if you can see it. Can you see it? + +Scott Hewitson: Yep. + +Robert Del Rey: So this is a user ID that you will have on Sealy. This is related to your silly user. It looks like a hash rate. And yeah, this is related to your username. This is gonna be your username on Sealy. And this is going to be the Discord handle as it says. So what happens I sure the announcement that we had the winners. Please come and claim the rewards some people send me their address. whatever this guy sent me a message shaped bershapi what apps So on this core. It only says beer shop. It doesn't have the e at the end. but when I export the document + +Robert Del Rey: it comes out with this e at the end same as the silly username, but on this score, the guy doesn't have that name. It's a British app without the e at the let me know if guys can see it here. You sit here? + +Scott Hewitson: Click on their name again because sometimes you can change your display name in a channel, right? Okay. + +Robert Del Rey: Yeah, this is the original when they text you so the display name is Spirit Shop, and the user is very sharp without the e. so on the document it has + +Tyler Wright: And the only difference is the E. Sorry to cut you off. + +Robert Del Rey: it's It's okay. Tyler's. Yeah, the only difference it's the E on the username. So what I did was the following and now you will be able to see a cash ceiling. I created One mission specifically for that guy. it's called claim akt reward test and I sent him this Mission and told him be at the end. Go to this Mission and click on the mission. Let me know you mission. So when the guy claimed the mission, I went ahead and exported the document again. In the mission was there. so Okay. It's taking a little while to load. But yeah, this is the guy. + +Robert Del Rey: and he did the mission right away. So I don't know if there is an error with the document here. you can see it here. He claimed 30 minutes ago as soon as I sent him the message. He claimed the mission. So even here these courses Bishop B with the e at the end, but on this Korean doesn't have the e. So, I don't know what you guys think about it. I haven't received any other message from a similar account. I just decided to pay the akt after he claimed the mission right away, but I wanted to bring you the story case so you can let me know what you think about this. There are two other abuser instances that maybe bendy can expand a bit more. but yeah, I wanted to share that initially with you guys. + +Benjamin B: Yeah, I just want to say that I think that your solution here was quite good because while this might have happened due to maybe a name change or something and there's no one called the beer shape or whatever in the Discord like the linked name. No one has that. so I think it's fine for the other two abusers. I just want to quickly mention that we noticed that they had. Let me share some screenshots actually. + +Robert Del Rey: Chairman, go ahead. + +Tyler Wright: Cool while you're doing that I see and maybe you can't talk and I'm having a difficulty pronouncing your name. But this is a working group for zealy is an initiative that Robert and Benjamin are leading up as a part of the vanguards and part of the Akash Community to continue to bring more developers into the ecosystem. So I don't know if you have anything that you would like to contribute or any questions that you may have. But I just want to see if the person that just joined has any questions comments or anything that maybe they want to put in chat or just talk about + +00:10:00 + +Benjamin B: All Thank you And back to what I was saying. I sent a link in the chat and I noticed that this guy ninja bus had been using an account on the CLI that was alphotox. This is the same name as another user. So we flagged this as someone with duplicate accounts trying to get multiple Rewards. After they reached out they mentioned that they were brothers, but I don't know how much you should trust people. + +Benjamin B: Anyways, these two accounts are linked. That's all we know. Go ahead Tyler. + +Tyler Wright: I know Scottish is hand raised, but the only thing I'll say very quickly is we've + +Benjamin B: Do you have anything? + +Scott Hewitson: Sorry, I wasn't. Yeah, I was just gonna sit like I was going down the same track as tie. we see this all the time at the test net. So anytime there's someone trying to claim at the same email address or we've seen, combinations of it's where so you can clearly tell this is A duplicate and so in that case, the ones that are grouped I pick whichever one is the highest amount of Rewards pay that and then forget everything else, because they did complete a bunch of stuff. Just good. I can pay it and then most of the time to we do it and then nobody ever comes back and complains or if they do then you say what's up with this and then no response, so the second they're just looking for something easy, it's an easy. + +Scott Hewitson: easy way to get extra and if you just push back a tiny bit, they'll probably stop and if they don't we can elevate it. + +Robert Del Rey: Thanks, Okay in that case. + +Benjamin B: Yeah. Thank you Scott. + +Robert Del Rey: I'm sorry Benjamin real quick to add some context. We did pay ninja base in the first pilot, but we haven't paid anything for what he did in the extension and nothing to the alpha looks account, which is duplicate the abuse account. Just wanted to add that for context. + +Benjamin B: Yeah, I think the decision we made is that during the pilot we don't have many rules set right now. I think that we can put the blame on us we can give them the benefit of the doubt because while they're obviously linked it's not like two user free It's not. Done in that way. So I think the minimal rewards paid out is fine for figuring out this rule. So next time we will have a rule that says Max one person per either household or her a computer or something like that or just no duplicate accounts or allowed. + +Robert Del Rey: Thanks, baby. That's great. + +Robert Del Rey: Yes, so far that's all I had on rewards users and have users. It's a funny name Ben if you have anything more about the abusers cases, I can go ahead and move on to the next topic of the agenda. All right. Thank you humbs down. this is a quick demo. For how the new missions are gonna look like if you are on this call or you see this recording later you will get some Alpha and how the missions are gonna look like. And maybe that can give you some heads. So let me know if you can see the Akash Network dashboard the quest board. Sorry. + +00:15:00 + +Benjamin B: I see. + +Robert Del Rey: let me remove So this missions they're not color because they're not active. You can see here the label it's draft. I can publish them. But if I publish them people will start to do them. And I don't want that. maybe we publish them on February or whatever. We start the next phase on this program, which is gonna be soon, hopefully and the missions is three missions as you can see here, but this three missions are only one Mission and I will start with the first one so you can understand better. The intro it's gonna be a basic web app in Python and deploy it on a cache intro. + +Robert Del Rey: So you have a little intro this is bait or this is based on a great guide that Benji shared with me a few months back and help me to get started a little in this and basically that process I through I mostly went through because I didn't complete it. That is what it's gonna happen in different missions. So this is the first one the intro basically to complete the missions. You need to download these and you download these three programs, whatever. + +Robert Del Rey: And after you download the programs. Here says submit your Docker setup profile ID. So once you are done with this, you need to create a Docker desktop account. And to claim this first mission you need to submit your Docker desktop for a file. That's the most basic info I can know right now and it's easy to find if you can think of another piece of information. That they can use to submit this and proof that they downloaded this. Let me know. I'm also thinking that since this is just downloading stuff. This Mission can autovalidates and the guys do them and go to the next mission in the chain. Wanna stop real quick. So you guys can let me know what you think. I see one hand Go ahead brother. + +Benjamin B: Yeah, I think as long as we don't try to limit rewards to fit a budget. I think Auto completion here is fine. + +Benjamin B: And still have the response so that when they have to write their name, can it just automate anyways. + +Robert Del Rey: Yes, yes. Let me show you right I set up in url, but we can change that to empty. And it can validate It just come up with a bottom to claim Mission or we can do text. and they can write whatever they want here + +Robert Del Rey: Also, if we are looking for a specific answer we can have a cool down here and they can try again. Maybe one hour later one week later. So yeah, really cool. We can also have a quiz or Paul and we can add a question specifically What's your name? I don't know. This is just improvising and here they can add quite option r or option b But yeah, it's very customizable if that answered your question Benji. + +Benjamin B: Yeah. + +Robert Del Rey: And yeah, we can do this no Auto validate draft and you go. Here is it? + +Robert Del Rey: You see It's number box that they can write and after they write they click on claim, but I can claim because I'm an admin but you get the picture guys. no, no, okay. Okay. Are we here? + +Robert Del Rey: Can you guys hear me? Okay, okay. + +Benjamin B: Yes. + +Scott Hewitson: Still can hear you? + +Robert Del Rey: Thanks for a second. I felt like the electricity was out. + +Robert Del Rey: There were problems I guess no worries. So we continue this is gonna be like the intro it's gonna be Auto validating. I believe it's a great option. So people don't waste time and they can continue to the next mission in the chain. It's gonna be the same title, but now it's creating and testing your web app. And now you can see how this is turning a bit more fun. Because now if you can do this it's because you did the other steps in the missions the second step is this now you're gonna create the environment for the application in Visual Studio or something like that being explained to me. + +00:20:00 + +Robert Del Rey: I'm pretty sure that we're gonna get lots of questions in their cash daily. Hopefully that's the case. But this is how the mission would look guys. You have all the commands here and you have a description what's gonna do and the steps if they read this in order they would be able to do it. But if they jump from here to the last part they won't be able to do it in my opinion. So you have to follow the guide. And this is the example with Benji's guide, but I believe we can fit anything a cash related in this format. And that is one question I had for you Scott and Tyler or maybe for others in overclocks, like what? + +Robert Del Rey: What are the things that you would like to see being develop the most in a cache and maybe we can focus on that for one or two months and do missions that support that goal or for our clocks or for the cash Community if that makes sense, I believe it does. So yeah going down to the submission method. I just did three x because I don't know what would be like the best roof. I believe I screenshot will do or maybe one copy of the code. I don't know Benjamin what do you think about it? But that's basically it. and the third mission it's like the last You made it all. This is the final step. Now we're gonna containerize test and upload the application that these guys did. + +Robert Del Rey: You have here create a file and the name Below Docker image you got the comment the commands you got everything and then the last part is run it on a cache. + +Robert Del Rey: And yeah, I'm very happy to see how they actually look way prettier than the first missions. I don't know if that's gonna do something. But if I was a super developer or maybe a beginning developer, I would like to see this instructions and the content I'm gonna use in the CLI or the environment whatever. But yeah, I like the way it looks that's one personal note. I want to leave there. Please help me with the submission type. I don't know Benji. What would you like to see submitted? It's gonna be like their application, but maybe we should have some guidelines not to leave it so open. on the first pilot, but leave it + +Robert Del Rey: openly enough that people can do their stuff and build on a cash and run on a cash and it's still claim the missions maybe for the last mission and this is something I just thought maybe they won't win rewards right away and we can get a few submissions like five ten people do this and we can review what is the best application and maybe that one can take the final price? yeah, I leave that to the floor. So yeah, maybe what's up, man? + +Benjamin B: So let me start with the last idea you had I think that it makes sense to have some rewards like that. I think there should be a bit of both for some there should be the best if you create a video for example, maybe just record the best and also to speak on how I should have this Mission so I think for the first one we can collect the Username and have it all to complete this gives us some data and we can go track and see how successful as this Mission bin for the second one. Maybe a screenshot, but we're not going to pay out rewards for your step to I'm guessing so. If they do a screenshot or not, it doesn't really matter. So I think they should just be allowed to go do the next step if they want to. + +Benjamin B: And for the last one, I think that either we can have some guidelines set so that they have to keep it on mine for a minimum of a few days or something. So we have time to review. or we can And send us A screenshot maybe we can also well validate it to their username. So if they have their Docker username we can see uploaded an image that works and then we will also see the screenshot that They also did deploy it. + +00:25:00 + +Robert Del Rey: Awesome, and thanks for the input. I will do the changes and have them reflected in mediately. Thank you so much, And yeah that's all for the new and demo Tyler. Go ahead man. + +Tyler Wright: It's not like that was really awesome. I know that you ask for some feedback from the overclock Labs theme. At the highest level one. It would be great if you could share and I know you haven't gotten to that part yet, but the second discussion and the proposal for the next steps. so that he and I can take that internally and continue to push it forward with some other thoughts because I think at the highest level what zealy is trying to do and I think overclock Labs is trying to do that. And so it's a cash Community is we want to find more. + +Tyler Wright: vanguards and power users like yourself, if you want to find more Benjamin's we want to find more Roberts more Rodrigo's more shimpas or julius's and I think using zealy at the vehicle to get folks like that into the community is a great idea. at the highest level, I know that's what with eat Denver and a number of those conferences that members of the community and the core team will be going to trying to figure out dockerizing specific Layer Two or the East project and running their nose on the Akash Network and building svls that make it easy for other folks to do that. It's something that is very interesting and obviously anything + +Tyler Wright: An running specific AI hugging face models on a cache could be an interesting challenge to bring out more technical users to understand that kind of stuff similar to Julius. But again, I can write that more. I can write that down. But I just want to put that on record of something like high level things that I know the coaching to think about. I'm sure you might have some others again. + +Robert Del Rey: Thanks thing. + +Scott Hewitson: No, thank you covered it well. + +Robert Del Rey: awesome + +Robert Del Rey: Yeah said Cindy Robert I wrote some but yeah, if you're free to send those over you can send me at the end if you want to send them in the CBD score, but whatever Thanks for those suggestions were really nice. I wrote some myself to and I believe now we'll be perfect time to start going over about the proposal and plan the next steps four days or maybe people and start the next phase of this. I don't know you're gonna call it still. + +Robert Del Rey: If you want to go over the proposal and I support you. That'd be nice if you can take over the second segment of this call. If you're ready, of course. + +Benjamin B: Yeah, Thank you Robert. I mean Let me share my screen. + +Robert Del Rey: everybody + +Benjamin B: so I have not published this to GitHub yet because + +Benjamin B: I don't think it's quite red. I think that we should go over this and try to agree on some stuff. I wrote this draft just before the weekend and I wrote some resources. I think we need and just a general overview of how it could look like. I'm not sure if this is enough. I don't know if this is too much. Do you want a few minutes to read through this everyone? + +Robert Del Rey: Okay. + +Scott Hewitson: I'll read it real quick. + +Tyler Wright: Is this in a state where you can send out a draft? Just or whatever. + +00:30:00 + +Robert Del Rey: I guess we can go over the basics while you still see these craft… + +Benjamin B: Sure, I can do that. + +Robert Del Rey: but basically it talk about Seeley what it is what we have done so far and how the pilot went. And what we're going to focus specifically is. if the resources required are + +Robert Del Rey: maybe good enough for the community so we can post this and start getting the conversations going. and I'm more specifically interested in the spec that outcomes and I like brainstorm to come up with these outcomes, but cause I love to hear your guys perspective from overclock perspective and make sure the outcomes we're working towards to are aligned to the outcomes that you guys want to see in our clubs and that the broader Community wants to see so yeah, basically at least personally what I would like to focus on right now in this discussion is the resources required and the expected outcomes. + +Robert Del Rey: Basically, but that's me. I don't know Benji if you would like to focus on other topics outside those Scott or Tyler the rest of the participants, right? + +Tyler Wright: I think that makes the most sense for me. I think Benjamin does a good job of laying down the foundation and the whole story and so I can read that but I think the outcomes and how much to ask is the most important thing to talk about + +Tyler Wright: Scott you have your hand raise? + +Robert Del Rey: Go ahead. + +Scott Hewitson: No, I'm just reading through this. No, I mean I think we did the pilot and you just quickly go over high level results. what did we learn from the pilot? it says 925 akt was rewarded between 22 or 25 Mission 76 users. Do we see any of those users hanging around in Discord more or is anybody But is people to come do it and then leave we want to try to make it somewhat sticky. + +Scott Hewitson: Go ahead. + +Rodrigo Rochin: So yeah, like I said in our last silly meeting call. I have seen more people after the Silicon paint in this court. And it does look like some of them are staying I did also say that I was a little skeptical about silly. but it seems it's working and Robert and Ben are doing a great job. + +Scott Hewitson: No,… + +Robert Del Rey: Thank you so much, brother. + +Scott Hewitson: I mean I missed the last call. So sorry if any of that was discussed. But yeah, no, I think at least from my perspective, some people don't know what zealy is or whatever. So if we do put this forward you Say hey, this is a developer onboarding program or something a little more broad that I mean, we're using zealy as the tool to do it. But just to get wider support from Community validators. Whoever if you say hey, we're trying to bring on new developers and look we've already done that through these Pilots. It's just further bolsters the narrative or the case to get money. + +Robert Del Rey: Thanks, I like the name. Also. You said the developer onboarding program, right? + +Scott Hewitson: So yeah, something like that. + +Robert Del Rey: Yeah, yeah. Thank you. Yeah, I like that because sometimes I think yeah It's been helping us doing those missions, but I don't want to see getting in the way and become an obstacle for people to onboard Akash it's great. How silly help us do these but yeah, like you say Scott. I don't like the focus to be on silly or to have people think too much about silly. So I guess it's great if we start the Also saying instead of silly. It's a community growth to whatever. + +Robert Del Rey: This program is a developer onboarding program using silly and that's it. And I believe that that will be even more powerful to introduce the document in my honest opinion and that way we don't Focus like that much on silly because everything is done through silly. So it has enough participation I guess in this program. Thank you for that. + +00:35:00 + +Scott Hewitson: Yeah, and then I also kind of opens you up to if there's other ideas or options to explore getting the high level goal of onboarding more developers than you kind of have a little leeway to do so. + +Robert Del Rey: thanks, go ahead and + +Benjamin B: Yeah, I think not limiting. Everything to seal is a great idea because what happens if you just want to host a fun fun little sponsored contest, so I've had this example idea in mind for some time. imagine that we want to bring over web to Developers. We for example team up with some game developer influencers who could help share game jump and then to this users we could sponsor their server so we could help them Host Game Servers. Just as an example that could not be done through silly in the same way. + +Benjamin B: Go ahead rodr. + +Rodrigo Rochin: Yeah, like you'll say and like I said, I was a little skeptical about silly especially because I didn't think that there's many developers there and I do see how silly helps you out to manage this program and makes it easy and there are tons of users there. Although I thought or think that they're mostly just nothing folks What's it called? Let's scavengers the People just looking for airdrops and stuff. but yeah,… + +Robert Del Rey: this bounty hunters + +Rodrigo Rochin: maybe they're there. They Bounty Hunter. Yeah, so it could be used silly with another platform or another tool where there are more developers. I'm not sure which one but of their properties one + +Robert Del Rey: Go ahead Tyler. You got your hand up. + +Tyler Wright: The only thing that I'll add and I don't think there's anything wrong zealy. I see other communities also using zealy. So to Scott's point. I do agree that focusing on just the developer onboarding is the most important but we could talk about the kind of communities you really has and all that kind of stuff just as a starting point and to everyone's point we can switch later. I think to Scott's point about stickiness. I think that's one of the things that we have to make sure that whatever platform we use we're making sure that there's a path for zealy users. So we're getting people from zealy Community to get really interested in the cash or other communities once we get them interested and once we have them doing something where do we push some next and I think that's just as important as doing the missions because + +Tyler Wright: than whether it's into the Discord or whether it's having them do more bounties. we just want to keep them in the community and keep them building for as long as possible. So I think that's something very important to think about and continue to focus on as a part of this experience. + +Tyler Wright: I'm sorry real quick or whether it be like the hackathon, there's all these other programs that are, getting community pool funding right now. I think it'd be great to Showcase zealy's power and pushing people into Hackathons pushing people into working groups and cigs pushing people into the Discworld communities that they join the Insiders or eventually join the vanguards, and if those are things that are actively being thought about and being pushed I see no reason why this wouldn't be something that everybody in the community understands and wants them back, because again, we're already using the existing programs that Adam has worked so hard to build, and others and we're just again using zealy at the vehicle to continue to push people into those programs. + +Robert Del Rey: Thanks, though. Yeah, we'll definitely put more thought on those points you say and how we're gonna retain those talents because how much over 76 users interacted downloaded stuff and did something on a cache. So we should be able to keep at least a percentage of those people and make them inside. There's make them vanguards or make them just normal community members, but they are there on these corn telegram supporting else so yeah, I guess we demonstrated that we can use the tool now. The next critical point is how we're gonna + +00:40:00 + +Robert Del Rey: turn those testers or users into a cash community members, I believe we are aligned there, Yeah, I'm sure we are. It's gonna be a great news if we can do that. Go ahead Benji. I'll see you. + +Benjamin B: Yeah, I want to add something to what the rotor was saying. I don't think that we should just have the celebrating users trust. I think that a big portion of this is that we have to find users so we can decide a little longer on how we are supposed to do that. But just relying on a platform to give us organic users. I think that's not enough and on a Reddit. We can try to Market on Twitter and then we can try to Market through. all other sorts of Medias but I think that. + +Benjamin B: The success we have had now, I think that's without almost any marketing at all. So I think if we start to actually push the marketing initiatives, I think this can scale up really well and we can try to Target real users who or developers but then also if we find people that are not Developers as long as we shape the missions, so it doesn't matter. And then we can have any users and how much they want to learn is up to them. So, I don't know if you were here earlier in the cold Rodrigo. But basically we discussed one of the new missions that we're going to release. And if you're not a developer and you have never touched a command line or never touched a script. + +Benjamin B: There's a big chance you won't be able to complete it or at least you will. Be scared from it. However, if someone wants to learn, I think that even if they are a developer before a cost or not, as long as they're willing to learn how it works and maybe get an interest for Akash after that. I think it's good enough. + +Tyler Wright: So real quick,… + +Robert Del Rey: Absolutely. + +Tyler Wright: I do want to add to that point that Benjamin made because I think it's worth talking about. I know that Adam has been thinking about to continue to improve the onboarding experience for people that are like vanguards or there's General people that come into the chat and hey, they want to learn more. I love the idea of zealy being an option because some people just may want to learn on their own and we can send them to the docs. We can send them to Cloud most we can send them to pray or we can do a number of options. But some people maybe we need to be incentivized and zealy because there'll be funds behind it. could back. All right here this guy get started and potentially get paid, and maybe we'll get a whole batch of folks that come in that way earn a couple AKA now that they have that akt they can use it, + +Robert Del Rey: I can go ahead. this is an open stage. At least for you guys. You're like the founders of this project. So if you want to say something just jump in. + +Benjamin B: Of course. + +Benjamin B: Anyways, I just wanted to say that I think there's been enough time to go through this. I think you've had 15 or 20 minutes to read for this now. + +Benjamin B: I'm asking Easter anything you want to add besides there was some things discussed here about the expected outcomes, especially related to things such as insiders program and working groups. Vanguards Etc. How do you all feel like should we change anything here? Should we add something more besides that we want to try to focus even more on this we have missions. And then what do you think about the funding? I don't think this is a huge ask for the community pools size. But maybe it's a bit much for this specific proposal. I want some feedback on everything here on whether or not you agree or not. Go ahead Roberts. + +00:45:00 + +Robert Del Rey: Thanks ji. Maybe just for the record you can just say how much will it be for the length of the campaign or how much we think will be enough and for how many months we plan to do this? + +Rodrigo Rochin: yeah, I hadn't read the document generating it now, so + +Scott Hewitson: Just quick question,… + +Tyler Wright: but I'll go ahead. + +Scott Hewitson: You want it? I got it. All right, so I'm just looks like two people 500 bucks a week because it's 250 a week or per person per week for 2500 USD a month. Where's the extra 500 bucks? Just I see. 500 a week times four weeks two grand I think is completely reasonable. for How many months a quarter? + +Benjamin B: Everything is for a quarter and these are rewards this would be for each user here. + +Scott Hewitson: Okay. + +Scott Hewitson: So wouldn't it be six grand for the quarter because two grand a month. I know that's really nitpicky. But + +Benjamin B: Let me see. two weeks in a year divided by 4 times 250 + +Scott Hewitson: five I guess yeah going off of weeks versus months. + +Benjamin B: to be a free files into 250 per person. By my calculations, it's correct. Let me show you here. + +Scott Hewitson: No, that's fine. I mean if you're going off of weeks versus I was just going off a month four weeks in a month, but not every month has exactly four weeks. So + +Benjamin B: Yeah, I was going by the hours and USD power so it would be accurate and by the quarter + +Scott Hewitson: Gotcha. No,… + +Robert Del Rey: But I think that's a great. + +Scott Hewitson: I think this is fine. + +Robert Del Rey: I just got sorry. + +Scott Hewitson: no, I was just gonna add so we have the five grand a month in rewards. This is just an idea but not saying we have to do it which is wildly under underutilized. So if anyone out there has any ideas and wants to do stuff, please let's spend some more money, it's like if that's not getting used we could use that. I don't know if we can use that for rewards until it starts getting used more. But I think this ask is completely fine. I don't have any issues with it. I think it's reasonable. we've been transparent as long as we got the steering committee on Thursday. I don't know how you feel about turning something quick and getting it out there, but I think it would be really nice to be able to bring this up and steering committee for, carve out. + +Scott Hewitson: Four or five minutes at Ty can squeeze it in there to say. Hey, this is what we're thinking and the goal is to get more developers to get more folks building on a cost and by the way, we have some proof that some of it works and we have some more people in here. But time is of the essence since steering committee is on Thursday if we want to get it in, I'm just thinking trying to get full support from community and the steering committee. + +Tyler Wright: I would agree with that. + +Benjamin B: awesome + +Robert Del Rey: Thanks. + +Tyler Wright: I think the ask is more than reasonable. And if we can get this online and start to get folks Rodrigo great. It'd be great to get your thoughts on it, especially + +Tyler Wright: when people say I didn't think this gonna work but that makes everyone feel good. But yeah, if we can start getting comments on here I can add some and hopefully we could talk about this on Thursday. I forget it in the next day or so, then I'll make sure we talk about it on Thursday. + +Robert Del Rey: Yeah, I can. + +Rodrigo Rochin: And also really sounds great. + +Robert Del Rey: Go ahead and… + +Robert Del Rey: really sorry. + +Rodrigo Rochin: Sounds reasonable and… + +Rodrigo Rochin: like I said, I do see more users in this court. + +Robert Del Rey: Thanks, And thank you Tyler and Scott. We're gonna reward this to make sure we add the topics that you mentioned how we can use this to retain more people the developer on boarding program and maybe we can work with the wording on the funding. so there is no confusion because I believe there was a confusion between what is Scott was reading and what Benji was trying to explain in the funding. So maybe we could work the word in a little but yet you can add it to the agenda for this Thursday. I'll be happy to go over this and finally present this to the rest the brother Community if that makes sense and what had Benjamin + +00:50:00 + +Benjamin B: Thank I was going to mention kind of the same things. I will be going over some of the things with mentioned in the cold today. And this discussion will be up today with the changes. I will make it so that the focus is it's clear that we might go away from Sealy if we think it's required. I will elaborate what seal is. I will reward a couple of things like this. And do you really think that this needs to be rewarded? I think that and All in all is pretty clear, but Maybe just because you didn't have time to go over it. It created the confusion. + +Tyler Wright: Yeah, I don't think it needs to be reworded all that much and… + +Robert Del Rey: Yeah, that's a great point. + +Tyler Wright: I don't even think you need to put an emphasis on the idea of potentially moving away for zealy. I think you can focus on it's a developer onboarding program. Zealy is what we're using and if somebody wants to come back and back. I think we should use this program or okay, let's do the research. But again zealy is shown that there's a community there and the pilots have been successful. So I don't want to just make people have to make more decisions. We'll move forward with zealy until others say have better guidance, + +Tyler Wright: But yeah,… + +Benjamin B: also + +Tyler Wright: I think just the structure is good. I would just add the stuff about the six working groups. I would add more information about the onboarding experience and how we want to potentially Market this get people that join the community to leverage zealy to earn as a path earn rewards and learn more about Akash and then that stickiness, after they complete the program how we push them into other things and those outcomes of again finding more Roberts Benjamin's Rogers CJ simpos. I'm sure I'm leaving on a number of folks in the community, but that's just a few of key. is that are accountable build a number of different ways both technically and not technically and just support the growth of the community if we can find + +Tyler Wright: four more five more each of you. I think we'll be in a really really good place. + +Benjamin B: Also, thank you for this. I will also mention that we agreed that during this call that the details or reasonable. + +Scott Hewitson: Yeah, I think to ask amount. I think it's perfectly reasonable + +Benjamin B: Adele's come out the expected outcomes Etc. + +Tyler Wright: Yeah, I think this is. + +Rodrigo Rochin: You could look fine like sorry. + +Tyler Wright: N't. No no,… + +Tyler Wright: go ahead Roger. + +Rodrigo Rochin: They're like Tyler's there anything this doesn't need much rewarding anymore and… + +Rodrigo Rochin: it would be great to push it on Thursday and have it going this quarter. + +Robert Del Rey: Sounds like a deal. Thank you guys for your input. + +Scott Hewitson: I think maybe one thing to add It's just at the end of it. Just give a report just some kind of transparency of hey, This is what the results were after it was done so that we go back to ask your more for another quarter. Then people can make educated decisions. + +Robert Del Rey: Let's go also based on that I believe. Benji we should go ahead and have the cell file with the previous winners and how much we have paid so far. I believe that's also a good piece of information to have there. + +Benjamin B: If you could send all the relevant links you want to add here I could add them. + +Robert Del Rey: Sure, you got All right, you're righty. I would say this has been a really solid call guys. Thank you for joining and thank you for your time also for those listening to the recording. Thank you, and please get involved. I don't have anything more to add so far. I believe the points were great. and there is some thinking we're gonna do Benji you and this week until Thursday, but yeah, it seems that first is gonna be the day that we reveal ourselves to the community, but knowing the way that you thinking and So guys, yeah, that's all for me. Unless you have anything else that you want to add before we wrap this up? + +00:55:00 + +Benjamin B: Queer employment. Thank you everyone. I'm super appreciative of these calls. + +Robert Del Rey: Awesome. thanks everybody. + +Tyler Wright: Please thank you. All this is amazing really excited for the future. + +Robert Del Rey: Yeah. Yeah, let's see how it goes, right? Thank you for joining us. Stay safe and until next time guys, okay? + +Rodrigo Rochin: integral great job that you guys + +Scott Hewitson: All right. + +Robert Del Rey: you see + +Benjamin B: Bye everyone. + +Meeting ended after 00:56:59 👋 + From 1185364c7d63b892ff011d7efc2a63f778caaac8 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 14 Mar 2024 22:48:32 -0400 Subject: [PATCH 016/138] sig-chain Create 013-2024-02-13.md (#485) * sig-chain Create 013-2024-02-13.md Signed-off-by: Drinkwater * Update 013-2024-02-13.md Signed-off-by: Drinkwater * Update 013-2024-02-13.md Signed-off-by: Drinkwater * sig-chain Update 013-2024-02-13.md add recording and transcript Signed-off-by: Drinkwater --------- Signed-off-by: Drinkwater --- sig-chain/meetings/013-2024-02-13.md | 97 ++++++++++++++++++++++++++++ 1 file changed, 97 insertions(+) create mode 100644 sig-chain/meetings/013-2024-02-13.md diff --git a/sig-chain/meetings/013-2024-02-13.md b/sig-chain/meetings/013-2024-02-13.md new file mode 100644 index 00000000..41275fc7 --- /dev/null +++ b/sig-chain/meetings/013-2024-02-13.md @@ -0,0 +1,97 @@ +# Akash Network - Chain Special Interest Group (SIG) - Meeting #13 + +## Agenda + +- Discussion of network upgrade plans for q1 2024 +- Proposals on chain for vote. +- Open discussion + +## Meeting Details + +- Date: Tuesday, Feburary 13th, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://swcn57cpu3ttvpgaf7e52xsv5wil57wtyredtvnd6bprntawwl3a.arweave.net/lYTe_E-m5zq8wC_J3V5V7ZC-_tPESDnVo_BfFswWsvY) +- [Transcript](#transcript) + + +## Participants + +- Alani Kuye +- Artur Troian +- B S +- Rodrigo Rochin +- Scott Carruthers +- Tyler Wright + + +## Notes + +- Tyler mentioned that the core team is working on a number of items. +- Artur reitterated that there are 3 upgrades planned for the quarter. The work for network upgrade has been deplayed. +- Artur has implemented changes for expedited proposals. +- Artur mentioned that CosmosSDK 50.0 is very useable. Going to plan to get there quite soon, and want to upgrade potentially end of q2. +- These are quite drastic changes so this will be added to the roadmap some time soon. +- After expedited govenernance proposals, closing status of the lease, is the next planned upgrade. Network upgrade will allow users to see why lease was closed. +- ICA is also on the table. Packet forwarding is more important. This is the 3rd governance proposal. + +### Action Items + +- Schedule upcoming network upgrades. +- Keep community updated via discord. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to Sig chain monthly meeting number 13. This is the second monthly meeting of 2024 during the sink chain monthly meetings. The group goes over anything related to validating the Akash blockchain Network upgrades anything around those topics. We also talked to some validators that are another ecosystems and Cosmos SDK and Cosmos ecosystem and are maybe again up doing upgrades on other projects and it might have Intel that might relate to potential Akash upgrades again out of the last meeting. We talked about a number of upgrades that are playing for q1 of 2024. + +Tyler Wright: I know that the core team has been extremely busy doing some other work that you can track on the roadmap. And so there's been a little bit of delay in figuring out the next Network upgrades. I know that Archer is going to talk maybe a little bit at a high level as that's a potato what's next and then we'll continue to work on specific plans async. But yeah, I'll just hand it over to Archer if he has anything, but he wants to talk about specifically and I'll just take notes in the background and then if anybody has any discussion questions or anything that they wanted to discuss related to Blockchain Network upgrades Etc. Feel free to drop those in the chat and we can go for those in a little bit. But our Trail handed over to you. + +Artur Troian: Thanks not. All right. Hello, everyone. + +Artur Troian: Yes, so the chain updates are slightly behind our initial schedule that we have plans later. at the end of times 23 so we have trained Network upgrades plans for this quarter and this stage a little behind you Quite important features needs to be done for Provider Services. but I would say nearly the finished State for the Provider Services and you're gonna start working on the upcoming network of great related for the + +Artur Troian: expedited governance proposals quite soon. So we have actually implemented the changes itself. What we have to do is testing and hopefully it's going to take maybe for two weeks. And then If nothing interrupts this schedule maybe in end of February, but Market we' I'm grading our Network the biggest thing on the table though is decay. be gonna start thinking maybe and of Q2, it looks like Christmas Decay 50.0 is + +Artur Troian: usable right now quite a few changes have been updated. We're going to start planning in this phrase. + +Artur Troian: quite soon We don't know though, if it's gonna be one stage update or we're gonna have to do through interim stages. I'm not sure yet. Most likely we will have two due to quite drastic changes. in the schema, and I believe they require to have interim updates, but anyways, we gonna have roadmap is that + +Artur Troian: On time and of February, I think. so we have also planned two more updates after Governor expedited government proposal. So number two. Sorry will be related to deploy please status. + +Artur Troian: No, Closer status in the lease and that's been requested by quite a few. + +Artur Troian: Are users that when lease has been closed for whatever reason like out of funds or it's been unstable or stars and so forth parent design does not allow to put exact reason why it was closed and we gonna be providing Network upgrade to fix that. It's going to be simple change. I didn't one more Fields into the lease and provide there will be required to put the correct status and why this was closed. As well as when this is being closed by the user. It's still gonna be the reason cell caught by user. So it's going to be providing way more transparency for most more sites. + +00:05:00 + +Artur Troian: and then there is an ICA on the table, but we still like the process of thinking this is low priority for us right now. Most likely that first one will be f*** it forwarding which is again, we have sort of code base implemented, but it needs to be tested quite thoroughly. So I think this is sort of the update for this time. Are there any questions? + +Artur Troian: Okay, tell her about + +Tyler Wright: Purpose. Thank you very much Archer. again, people can track the roadmap and see what the core team is working across the number of different efforts on GitHub in the project section as Artur mentioned as soon as Artur and Scott are finished with some other provider work that they're working on next steps will be made in determining when Network upgrade will happen for the exponent expedited governance proposals. Then after that you heard Artur on the next two upgrades that are planned or in the works if anybody has any feedback about order of operations or schedule again, I know folks have been talking about ICA and GitHub discussions and it is very much on the roadmap. There's a support ticket that people can track but again, + +Tyler Wright: there is been collaboration discussion on order of operations, especially with a smaller core team. If anybody has any questions about those order of operations, feel free to bring those up in this meeting with discuss or in steering committee. But again the path forward the Archer is outlined seem to make sense for continuing to question that work forward. Does anyone have any specific questions about anything else? + +Tyler Wright: pain related Network upgrades or validators + +Tyler Wright: cool So again, this is plan to be a short meeting anybody else. go ahead Rodrigo. o your sound is + +Rodrigo Rochin: quick question when use these global Enable or Clans yet? + +Tyler Wright: Yeah, so I think the question was when usc Noble enabled. I believe the Archer put a comment in the chat. I know this is something that folks have been asking for but I believe this is Packet forward dependent which is why pack it forwarding is being moved up. Correct me from around art. + +Artur Troian: Yeah, that's absolutely correct. So first of all pocket forwarding needs to be enabled for that that's number one requires network of great. The second is Once again, there's no much use of it. So we're trying to balance the features that being requested and what we can provide right now. So we definitely keep an eye on the things and thank you for bringing that up. As soon as we see that this becomes really Origins, but really it stops huge amount of people from deploying that we're gonna reshuffle. Our priorities but for now, it's gonna be one of the lowest but we still hope to implement it sometime obviously. + +Tyler Wright: Yeah, I think an Artur and other members of the community have also talked about this packet forwarding should unlock a number of items both on the wild side and some of these other items. So once pack it forwarding is unlocked and that's something that's playing for q1 might be pushed out a little bit to Q2, but it certainly high priority in the next top three urgent Network upgrades. Once that's implemented then I'm sure we can take next steps whether it's in this call Sig economics or async to figure out all that packet forwarding unlocks and how we can continue to network forward from there. + +Tyler Wright: Does anyone else have anything that they want to discuss here today? + +Tyler Wright: All right, much appreciate everyone taking the time again when more concrete announcements are available. I'll make sure those announcements are distributed in the validator announcements Channel as well as to those that are part of that email group for validators so we can again continue to have constantly communication. Hopefully again, I do want to shout the validators for many of them are very active and votes and have been more active than historically. So again, we're going to continue to up that number but much. Shape the consistent participation by so many. + +00:10:00 + +Tyler Wright: But other than that, I hope everyone has a great rest of your day. If anybody has any other questions comments concerns Network upgrade or cost blockchain related. Feel free to drop those in sick chain and Discord or reach out to me and look at those all but Archer thank you for leading us through another call and we'll continue to again keep the community updated between meetings if we have any updates to get. Much patient every time that have a great rest of the day. + +Meeting ended after 00:11:27 👋 + From 9d952ddfda77b894212f769245229aa0a6d0e1a7 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 19 Mar 2024 22:27:53 -0400 Subject: [PATCH 017/138] sig-support Create 027-2024-02-21.md (#492) * sig-support Create 027-2024-02-21.md Signed-off-by: Drinkwater * sig-support Create 028-2024-03-06.md Signed-off-by: Drinkwater * sig-support Update 027-2024-02-21.md add transcript Signed-off-by: Drinkwater * Update 028-2024-03-06.md add transcript Signed-off-by: Drinkwater * Update 027-2024-02-21.md add meeting 27 recording Signed-off-by: Drinkwater * sig-support Update 028-2024-03-06.md add recording for meeting 28 Signed-off-by: Drinkwater --------- Signed-off-by: Drinkwater --- sig-support/meetings/027-2024-02-21.md | 271 +++++++++++++++++++++++++ sig-support/meetings/028-2024-03-06.md | 108 ++++++++++ 2 files changed, 379 insertions(+) create mode 100644 sig-support/meetings/027-2024-02-21.md create mode 100644 sig-support/meetings/028-2024-03-06.md diff --git a/sig-support/meetings/027-2024-02-21.md b/sig-support/meetings/027-2024-02-21.md new file mode 100644 index 00000000..eda20047 --- /dev/null +++ b/sig-support/meetings/027-2024-02-21.md @@ -0,0 +1,271 @@ + +# Akash Network - Support Special Interest Group (SIG) - Meeting #27 + +## Agenda + +- Participants will look at issues in [Akash Support Repo](https://github.com/akash-network/support/issues). +- Scott Carruthers will lead triaging issues, and discussion of implementation for issue fixes. +- Scott will discuss Support from the community and ask for any community feedback. +- Participants can have an open discussion of any other issues or support related items on Akash Network. + +## Meeting Details + +- Date: Wednesday, February 21st, 2024 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://cwya3qcl4ejhb75ct5d4vgcoyhsce46zvv2q42khi6kc76qhsxpq.arweave.net/FbANwEvhEnD_op9HyphOweQic9mtdQ5pR0eUL_oHld8) +- [Transcript](#transcript) + +## Participants + +- Andrey Arapov +- B S +- Damir Simpovic +- Maxime Beauchamp +- Rodrigo Rochin +- Scott Carruthers +- Tyler Wright + + +# Meeting Notes + +- Scott led the group in triaging issues in the support repo. +- Scott assigned two issues to himself related to protobuf. https://github.com/akash-network/support/issues/184 +- The group talked about https://github.com/orgs/akash-network/discussions/486 +- Artur is working on https://github.com/akash-network/support/issues/183 and tracking this issue. It is marked "p1". +- Core team looked at the issue with provider attributes fees. There is a lot of complexity with provider attributes updates. There is a lot of data, and thus the fee does make sense. + + +### Support + +- Damir mentioned that he sees some questions about deployments. +- Rodri has seem more users in Discord. +- Scott talked about Provider Feature discvoery services. The core team is rolling out provider release slowly, starting with 5 select providers. +- Feature discovery will be released to more providers, over time. +- Slow roll out will allow for sanity testing of code base and documentation. + + +### Action Items + +- The group will look at the new docs and make sure things look clean. +- Feature discovery service will be rolled out to more providers on the Akash Network. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: The provider bid price I believe. + +Tyler Wright: And… + +Tyler Wright: I believe you're going to do some initial provided attribute rather change pricing. I believe that there was going to be some internal quick testing to determine if there should be a discussion or an issue. I just want to see if that has happened. Otherwise we can just continue to track it inside of the ticket and go from there. + +Tyler Wright: All right, welcome to six biweekly meeting. This is a six support on February 21st 2024. How much appreciated everybody for joining during these six support biweekly meetings the core team goes through any issues that are waiting triage. If anybody here that's added any of those issues want to talk about the issues and more detail. They're more than welcome to participants can also talk about any issues past or present that are either open or closed just discuss status or Solutions Etc. + +Tyler Wright: From there. I usually hand it over to someone like Roger or somebody else from the Insiders or vanguards. It's very active and Discord. I can kind of give an update on support going on and any new issues that might be coming up from users and using So again, we'll talk what touch on that but the agenda usually starts and we'll start again today with handing it over to Scott that will go through any issues and support repo that nutria thing. I also see Max on the call here again, as I do every couple of weeks got out to Max and the cosmos team anybody has any issues related to Cloud most feel free to drop those in the cloud. + +Tyler Wright: Repo as well as in the ecosystem Cloud most Channel. I know that Max is a great job. And the rest of the team do a great job of responding to any issues that the community members or core team or anybody else sees with the cloud most product and they Continue to update it and improve it. + +Tyler Wright: Same thing on the index of side. But again anybody has any issues Cloud most related. We can save those to the end and discuss any of those issues here, but we start off by going through any issues in the support repo and they caution Network organization and that's related to the core code base. So again, if anybody has any issues that are core related as you all know, feel free to drop those in the support repo and then don't label them at all. What happens is again, you can just add a waiting triage label and during these biweekly meetings we go over look at the issues and put an importance on the So without further Ado, I'll hand it over to Scott to lead us through triaging any issues are waiting Triads over the last couple of weeks. + +Scott Carruthers: All right. Thanks. Tyler else share out my screen. + +Scott Carruthers: Is everyone able to see my screen? + +Scott Carruthers: So I was just reviewing things that are awaiting triage prior to the call and… + +Tyler Wright: Yes. + +Scott Carruthers: I think we maybe have just three or four. So I think we should be able to fly through these pretty quickly. So going from the top type of typescript protogeneration that Max opened based on. recent discussions and this being owned by the core team primarily and certainly will be Consulting. I know that Maxi did some work on this prior, so certainly be In communication with him and coordination with him. I'm just going to assign this. To myself since I'm going to be primarily taking this on. So this was not only for typescript but also JavaScript and possibly rust in the future as well. So I'll be in the protobuf generation. So again awesome myself to that this issues and this initiative is for generating. + +Scott Carruthers: Protocade definitions for other languages other than go has been discussed. pretty Ad nauseam over the last couple weeks. So I don't think they're prior any questions on this. Let me know if there's any questions but this is something that I'll be deep diving into and focusing on over the next couple weeks. + +Tyler Wright: Scott do you know what you want to label it? it's the P2 for you, or is it more of a key one? + +Scott Carruthers: Sure, I can apply a label as well. + +Scott Carruthers: Yeah, I would definitely classify it as a P2. + +Tyler Wright: excellent + +Scott Carruthers: Okay, next up update core packages to go version 1.12. So already has some applicable labeling but some of the arter just open to track and that some of the he'll be updating. They core code base with himself. So I will assign Archer. + +00:05:00 + +Scott Carruthers: This issue. + +Scott Carruthers: Again, this will be going through both the node and the provider code base and updating. Go version 2 1.22 so pretty simplistic. I just again something that we're just using for tracking internally in the core team. + +Scott Carruthers: so feedback for small providers that are again their wallets drained, so Andy I was actually looking at this prior to the call, I don't know if you've had a chance to review this but is actually wondering if at least just initially and obviously we can do additional assignment if necessary, but as I read through this this is very much. into something that possibly a new provider needs some guidance on typical tactics and techniques for so that if you read through the text of this or talk about their wallet getting drained because of withdrawal + +Scott Carruthers: transactions so obviously we can adjust that 12 or 24 hours is if necessary in also talking about their wallets being drained it bidding on very small workloads. So obviously we have some techniques so in the pricing script that other providers are using to ensure that they're not bidding on. Workloads would point one CPU if necessary. So yeah, are you okay with me assigning this to you? I'll send it as a P2 and I think this is just something that you could pretty easily respond to in this conversation with some initial suggestions. + +Andrey Arapov: Yeah, I think… + +Tyler Wright: go ahead and + +Andrey Arapov: what you said exactly what's happening. But I was checking, the transactions for visual. They are really cheap. They are a hundred times less than I send so and… + +Scott Carruthers: Yeah. + +Andrey Arapov: they don't use it happen that often the usually happened once twice a day something like this. So even if he did like it more often, I think it's more maybe even related to that updated attributes that this consuming three akt because if he puts there, something like Small amount also maybe he doesn't know about the deposits 5kt when there are bits happening. Maybe he just check the balance, but just It doesn't I think require that much attention to be honest, but we could just drop simple message that hey this is that and you need to make sure that you have enough make it is in Bottle depending on the amount of CPUs. + +Scott Carruthers: Yeah. + +Andrey Arapov: And that's it. + +Scott Carruthers: Yeah, I clearly agree probably in five minutes. You could probably at least I'm just responding and… + +Andrey Arapov: Yeah. Yeah. + +Scott Carruthers: discussion to see if he has any. And yeah, that's an interesting point as well. I wonder if these cognizant of Return of the five dollars is put in or a five akt that's put into escrow and Elise closes. So yeah, it may just be a new provider that just needs our guidance on a number of design issues. + +Scott Carruthers: hm support. this actually opened last month, so I'm not sure why this wasn't assigned prior. So this is a topic that's been getting a lot of closely recently as we're looking to bring more. we went through the exercise of doing training Through Thumper and now we're have some other candidates that are interested in doing AI model training on the Akash Network and shared memory. As something that's critical to those AI workloads in the training. So again something that we've been discussing both internally and other six calls significantly, so I know that + +Scott Carruthers: We have some people possibly that will be assigned and focused on this so I'm ready for right now. I'm just assigned archers to this, but there may be other people that are assigned to this in the very near term and it's already labeled a P1, which I think is definitely appropriate. But I hear a handed someone have a question. + +Tyler Wright: No, Roger just put something in the chat. But yeah,… + +Scott Carruthers: Okay. + +Tyler Wright: I think you're all set. + +Scott Carruthers: So I guess I'll just take a pause because of this being such a significant issue and point of attention. Does anybody have any questions shared memory support and the fact that we're very much focused on this and are hoping to allow this through a cost appointments somewhere in the next week or two. So any questions or concerns on this front? + +00:10:00 + +Scott Carruthers: Yeah. + +Scott Carruthers: so again, we have some other issues. I'm not sure why these are actually been open for a long period of time. Come and haven't had assignments one essentially. Labeled as not an issue is protobuf brush generation, which we already talked about for typescript. So again, I will assign myself to this as the Proto seat generation for other languages other than go is and then I'm going to be very much focused on. + +Scott Carruthers: I'm not gonna touch right now. This one that's labeled not an issue. We could review that. Later, but that goes through all the issues that have been open the last couple weeks and actually a couple that have been out there without assignment spending a little bit longer than that. So I guess I'll just open it up for discussion. I think that brings us through the triage and assignment any questions or concerns on any of these issues? + +Scott Carruthers: Okay, if there's no questions or concerns, I'll turn it back over to you timer. + +Tyler Wright: excellent much appreciated stuff again, if anybody has any + +Scott Carruthers: Yeah, we get a free continue to track it and our next session when Archer is on. He may have some thoughts of his own but yes, sir, Taking a step back. So make sure this clear what we're talking about. There's been a couple of issues raised recently or provider concerns recently anytime you update. Your provider attributes it's costs three dollars or I'm sorry keep on messing up aktn and hours a currently cost three akt on average to update provider attributes. So there's been some discussion recently in the community on why? + +Scott Carruthers: Those transactions are so much higher than any other transaction. So, the least creation or deployment creation or those kind of transactions are typically very cheap and they update a provider attributes is much more expensive myself and Andy and others in the core team looked at this yesterday and I mean as basically just a matter of the complexity. So obviously on any blockchain they calculation of transaction costs. They're built into that is a estimation of the computational power and a complexity of an operation. So if you look at provider attribute, updates + +Scott Carruthers: the amount of data that's included in the message body significantly higher than it would be for a delegation which the body would only have a short string obviously when we're doing provider attribute updates. It can be that the Json body is much larger. So we basically understand where we don't want to be dismissive of the concern, but updating a provider actually views should be Or other infrequent operation. We definitely are cognizant of the fact that if you're adding new GPU models or enabling persistent storage or something like that. There are legitimate activities that require provider attribute updates, but that's simply in our investigation. we don't see any evidence of this being a bug within the code basis just if you look at the + +00:15:00 + +Scott Carruthers: gas wanted and gas used estimation when the client is sending a provider attribute update. They're at least wave Castle being set to Auto based on the complexity of the operation is calculating that this is a much more computational heavy more complex operation. And yeah, I mean, that's really + +Scott Carruthers: All there is to it we can continue to look at this and Andy and I actually haven't had a chance to test this but we're discussing yesterday. It's possible that you could get those. provider attribute updates through a transaction by adjusting gas Auto to something manual and possibly it would be possible to get that transaction at a cheaper. + +Scott Carruthers: Champa damir. I know they had your hand up for a second. Did you have any thoughts on these regards? + +Damir Simpovic: Just my two cents Simply because I was doing those. + +Damir Simpovic: I probably did over a hundred of those. but I didn't honestly even know it's granted the akt PRI price was much lower but once + +Damir Simpovic: Once I figure everything out. I haven't touched anything. I don't think That this is really such a big concern honestly. even if it is But three akt or… + +Scott Carruthers: Okay. Yeah that. + +Damir Simpovic: three and a half akd. I don't see that. + +Scott Carruthers: I'm as one of our most prominent providers. I'm glad that you voice that opinion because that's certainly our opinion internally as well that this shouldn't be a huge concern because updating your provider attributes should be a very infrequent activity as I said earlier and you are echoing those Sentiments of it not being a concern and should be infrequent activity. yeah, I think that's obviously if we continue to get some pushback or send a satisfaction within the community we can look at this further. But yeah, I mean, just simply this is a more expensive transaction based on the complexity. + +Tyler Wright: Thank you Again, we'll leave that is a discussion right now, but that's a discussion in the chat. So if others want to get involved, that would be great so we can again. Get more people involved at least in the conversation. Yeah, so I'll continue to push that through we'll maybe talk during about six maybe talk about it during State providers. But again, I heard it a couple of great opinions here. So if we can get those into discussions, I would be great. + +Tyler Wright: All right moving on with the agenda at this point. We usually Reach out to someone like Rodrigo who I see here now and others that are insiders vanguards or active in Discord and other channels in the community. + +Tyler Wright: I just wanted to see on the support side. Was there anything new that anybody has been seeing in terms of new questions new comments new concerns with the network that maybe documentation can be updated or a processes maybe updated. Has anybody seen any new themes from the community? Go ahead damir. + +Damir Simpovic: So what I've noticed was a few questions regarding. when somebody Creates an order but that's not start loose. Basically, it doesn't accept any of the orders and the deployment sometimes do not get automatically closed. + +Damir Simpovic: by the providers and In which case the 5 akt requires to place a bid? remains in escrow indefinitely I think I've seen twice this already. So not sure what's going on. this is just looking further it has happened yet. Or perhaps it did but it's not and really big scale. But if somebody could even use this maliciously to drain. the smaller provider wallets because for one open order they will basically drain. 50 or + +00:20:00 + +Damir Simpovic: 100 provider it's so for five akt they gain 5880 or 500 a value quote unquote. So, I don't know. perhaps something to + +Tyler Wright: Perfect. Thank Damir. I'm taking some notes. I don't know if anybody else has seen some of those same questions or anything or has any comments or questions about what damir just mentioned. + +Tyler Wright: again, I'm taking some notes and I'll make sure that we add any additional action items related to what damir just mentioned there Roger. Don't feel the need to talk. I know Max you're probably doing a million things too, but I see you both active in Discord is or anything. That you all have seen that you wanted to call out. + +Rodrigo Rochin: nothing specifically just more users that are previous weeks and scammers still there, but we handle them as soon as you + +Tyler Wright: excellent + +Maxime Beauchamp: Yeah, nothing. Yeah when I said + +Tyler Wright: Thank you, damir. Cool, so we talked about support in Discord and other channels Scott has led us through issues that are awaiting triage and we've looked at any support issues in that repo. + +Tyler Wright: Max is here. And again, if anybody has any questions or concerns or any issues related to Cloud most I know Max is very responsive. Is there anything else that anybody wants to discuss related to support at this time? + +Tyler Wright: Go ahead Scott. + +Scott Carruthers: so I just want to make sure everyone is aware where we're at with the introduction of feature discovery on the network. So I've been in communication directly both with Broadway and damir about this and obviously Andy as well, but I've been testing feature discover heavily over the last couple of weeks and we have been making small adjustments based on. a minor issues that we've discovered during testing where to the point that we want to start rolling this out on to mainnet Providers and we want to do so in a limited fashion and with some selective providers to make sure that as this gets rolled out to Maine that we don't experience any other issues or there's not any other code adjustments that need to be made so currently we haven't merged they + +Scott Carruthers: the provider release candidate to Main because We don't want new providers coming out to the network to default to this new version that includes feature Discovery, but we just want to roll it out to a few providers. I would think that would be something on the magnitude of world out to five select providers. Make sure they're not having any issues over the first couple of days and then we'll merge the feature Discovery into Maine and then start rolling out in Mass to the rest of the network. So this doesn't require a RPC node update is only a provider. day and mostly some changes to the inventory operator within the provider code base. So as I said earlier rotary and damir are definitely both cognizant of this because I reached out to them yesterday as possibly being a couple of our first providers and he has actually already + +Scott Carruthers: experimented with this release candida on his main provider as well and also just some breaking changes and breaking news that applies to That Andy will find interesting. the current release candidate that's out right now, which is zero five zero RC 15. We notice both through. + +00:25:00 + +Scott Carruthers: Andy's experience on his mainnet provider and also some additional testing on Sandbox providers that there's a issues where labeling so along with feature Discovery being a mechanism where we can see the amount of gpus and other Hardware on the network feature Discovery also introduces automatic labeling. So no longer are providers going to have to manually label nodes for GPU resources or persistent or storage resources, but they feature Discovery through that those Hardware Discovery mechanisms will do automatic application of kubernetes labels. + +Scott Carruthers: Andy earlier this week notice and we've also experienced this on some sandbox providers that the labeling is falling off after a 30 minute window and we've already identified the issues as something with a kubernetes watcher that and this is why Archer isn't on the call today. He's making the code change the necessary to alleviate that issue. So soon and I think in the next couple hours, we're gonna see I think what would be RC 16 dropped and then what's that is available. I had conversation with rotary about this this morning. We were going to upgrade his provider, but now we're waiting this new release candidate with this latest issues remediation, so we don't want any upgrade in their providers and their operators until we make that announcement that that issue is alleviated, but I just want to bring it up on this call so that + +Scott Carruthers: obviously rodray and damir are very foundational in our support of providers in the community as well. So again, we're only going to roll this out to five select providers initially and then when we get to the point of doing the main net upgrade, obviously want to make sure that you're cognizant of these changes. So this will be announced but I kind of just wanted to give a quick status update on where we're at with feature discovering probably what they successful look like for the remainder of the week. + +Scott Carruthers: Rodrigo, go ahead. + +Rodrigo Rochin: So yeah, just wanted to mention that ready and I read the docs in. y'all know I'm not an expert like the mirror and Andrew your spot. But ducks and instructions look perfect. So shouldn't have a problem with you already. + +Scott Carruthers: Yeah, that's great. And that is actually another reason that we wanted to just do this for five initial providers not only doing certainly checks of the code base but also some sending checks to the documentation and this week upgraded his provider to rc15 and he said he was pretty much disabled to copy and paste all the docs. So we got some initial great feedback from the documentation. But if there's any need for clarity, we definitely want to get those in place the documentation before we send it out the community as well. + +Scott Carruthers: Yeah, that was it. Let me know if there's questions on that + +Andrey Arapov: Scott I just wanted that if that's at 5.14 not 15 yet and when I was checking 5.14 the storage wasn't returned. So the presentation storage was empty in provider status information. And I know if you had the chance to test it more with 0.15. I just had my time for that yet. + +Scott Carruthers: Yeah, so yeah, let me go back and maybe I wasn't entire eclair when that is precisely the issue that we're rectifying currently and the reason why arter isn't on this call is he's looking at that so with the introduction of so when we were looking at your provider or this week, we saw the feature Discovery wasn't reporting persistent storage. And the reason for that was the necessary labels were on kubernetes nodes. So that issue is now been identified and it's a issues where kubernetes washer falls off after 30 minutes. So that's precisely what arter is. currently introducing new code to rectify so when rc16 or whatever the next release candidate is issued will definitely want to do retesting of that. But that's precisely what the current focus is on. + +Andrey Arapov: Nothing for colorification. Everything is clear now. + +Scott Carruthers: Okay, great. Go ahead, damir. + +Damir Simpovic: Regarding the sandbox provider. I actually started doing this today that discussed with Yeah, I mean it's just actually started doing this and most of the stuff is done. all I need to do is to actually just install the + +00:30:00 + +Damir Simpovic: Your Castle but not sure if I could run. + +Damir Simpovic: I could run an RPC note, which is in the sandbox if that I need some kind of a Snapchat or is there. something somewhere that I can download from + +Scott Carruthers: Yeah, so we could have approach that into that two ways. Andy, and I actually is two weeks ago. I went through the spin-up of a new RPC node in a sandbox and it was a little bit painful based on. Snapchat I use I get into this and show you how so we definitely could go through the procedure of spinning up RPC node in your provider and your sandbox provider and we can definitely go to the process but there's really no reason in sandbox. You just can't use the public RPC endpoint and again the new Provider updates do not require any RPC updates. So using this the public RPC node in sandbox should be fine. Then that would definitely be the easier path. + +Damir Simpovic: All right. Thank. + +Tyler Wright: Thank Anyone have any other questions really want to discuss before I let all go. + +Tyler Wright: Again much. + +Scott Carruthers: and it And… + +Tyler Wright: I'll go ahead Scott. + +Scott Carruthers: if it wasn't query shampa, so appreciate building out a Sandbox provider and testing feature Discovery there before you update Euro plots. We'll want to I was just that you wait to the actual provider build until the latest release candidate is release which should be in the next couple hours. So I'll definitely reach out to you directly once we're ready to proceed with that. + +Damir Simpovic: Thank That will Certainly not happened earlier than tomorrow. So no worries. + +Scott Carruthers: Okay. Sounds good. Thanks. + +Tyler Wright: Of anything else that anybody wants to discuss before I let y'all go. + +Tyler Wright: If anybody has any ideas that they want members of the core team to demo or anything like that related to testing environment set up Etc. I know that's Scott and Archer I've done this previously so you can look at previous video recordings from I think of six support meeting, maybe two or three ago, maybe 24, but again if there's any other Concepts that anybody wants more clarification on when technical standpoint feel free to reach out to me or feel free to drop it in Discord channel for six support and we can talk about adding those to a future agenda. + +Tyler Wright: Much appreciate everyone's participation today again. If you're watching this later, feel free to join these meetings in the future and get involved in contributing to core code whether it be on the passport coach core code side where you can find issues in the support repo or supporting Cloud notes on their continuing growth and development in the cloud most repo, but there's a number of ways to get involved, but again much appreciated everyone's time today. Hope everyone has a great rest of your day and we shall talk soon. Thanks again now. + +Scott Carruthers: Thanks, everyone. + +Andrey Arapov: I think + +Rodrigo Rochin: You later. + +Meeting ended after 00:34:34 👋 + diff --git a/sig-support/meetings/028-2024-03-06.md b/sig-support/meetings/028-2024-03-06.md new file mode 100644 index 00000000..ddfd53b6 --- /dev/null +++ b/sig-support/meetings/028-2024-03-06.md @@ -0,0 +1,108 @@ + +# Akash Network - Support Special Interest Group (SIG) - Meeting #28 + +## Agenda + +- Participants will look at issues in [Akash Support Repo](https://github.com/akash-network/support/issues). +- Scott Carruthers will lead triaging issues, and discussion of implementation for issue fixes. +- Scott will discuss Support from the community and ask for any community feedback. +- Participants can have an open discussion of any other issues or support related items on Akash Network. + +## Meeting Details + +- Date: Wednesday, March 6th, 2024 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://xut7rmdqwninrlvm75t7cxmmpgrt4tyboramnw3b2rcpaa6gy76a.arweave.net/vSf4sHCzUNiurP9n8V2MeaM-TwF0QMbbYdRE8APGx_w) +- [Transcript](#transcript) + +## Participants + +- Andrey Arapov +- Deval Patel +- Scott Carruthers + +# Meeting Notes + +- Scott led the group in triaging issues in the support repo. + + + +### Support + + + + +### Action Items + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Scott Carruthers: Hello I'm just waiting to insure the recording and transcription has started but it looks like it has so hello everyone and Welcome to our six Port meeting for early March 2024. I think this is going to be a rather quick session. We're just going to go through the normal Cadence of going through the assignment of issues that are currently awaiting triage. I looked at those issues before our call started and I think there's just a couple and they're going to be rather straightforward assignments. So we will go through the Issues assignments in triage and then we'll open the floor to any questions from the community. So let me stop sharing the current slide and I will reshare with a issues brought up + +Scott Carruthers: Okay, is everyone able to see my screen? Okay. Okay,… + +Andrey Arapov: Yeah. + +Scott Carruthers: so as I said, I believe that there's only a couple of issues that are currently awaiting triage. So I'll go from the latest. Their earliest created and go to the top. So we have two currently awaiting triage. And the first one is home charts and tidying up environment definitions. So something that arter created a couple days ago, I think at the end of last week. I'm just suggesting that the environment variables should be defined in the config map instead of the deployment or staple set. so I'm just going to remove a waiting triage from this and I will put this as I think a P2 is probably. + +Scott Carruthers: Sufficient classification for this and then I'm going to assign this to larger. He might want myself or Andy to contribute to this as well, but I'll initially assign Archer and we can go from there. + +Scott Carruthers: And then the only other issues that was irrading waiting triage is the Akash maintenance 10. the network upgrade that was announced yesterday. Also actually already has assignments, but for some reason it was left in a waiting triage, so no need for assignments, but I'll take away awaiting triage and I'll classify this as a P1 as it's mostly just planning exercises. + +Scott Carruthers: So again, the triage is pretty simple this week. Those were the only ones that I saw awaiting triage and we now have assignment on all open issues. Are there any issues on this list either the ones that I just went through? Assignment or otherwise that we want to discuss during this meeting. + +Scott Carruthers: If no one else has any thoughts or questions, I guess just for the recording and the transcript just to highlight something. So yesterday we announced the intention and watch the government's proposal to. Do the latest Network upgrade which is going to be Akash main Net10 upgrade. There's several things that are included in that upgrade and I would say they to most significant that at least come to mind readily fixing gas issues for provider updates. So this is something that's been discussed rather frequently in recent Sig providers. And I think also in this meeting six support prior and we had attributed. the + +Scott Carruthers: fees for provider attribute excuse me a provider Ashby updates being that there are larger Json files within the body of the message. So there's some expectation that those gas fees would be higher just based on the processing of the Json body, which is martial larger than for a great deployment or a delegate transaction. But as the core team was looking at this further, we actually realize that this is also attributed ill to occurrence mechanisms within the code base that when they update a provider attributes happens we go through Ascend a check to ensure that none of the attributes that are being updated are currently associated with a live deployment. So in other words if I have a deployment + +00:05:00 + +Scott Carruthers: live and it used the US west region attribute, then it was built into the course software that provider shouldn't be able to update an attribute that's already in use in a current lease. So one of the manifestations of this and ramifications of this is there was a process you have to go through and iterate through all leases associated with a provider and that ended up becoming a very expensive operation. So we're going to take out that requirement to go through all active leases and to ensure that the updates are not affecting any live leases. So that's going to dramatically affect the computational load from a r attribute update. So that's one of the things that's going to be introduced and mainnet 10. So this should dramatically lower the cost of + +Scott Carruthers: Provider updates and attributable attribute updates and then the second thing that I mean at 10 is going to + +Scott Carruthers: unlock is the lowering of deposits both from a provider perspective so bid Deposits and also deployment deposits. So we're going to based on the currents cost and price of akt it definitely makes sense to drop those down somewhat dramatically from the current five akt standard and you can look in the proposal to see exactly what those are being lowered to but I believe one akt and I think maybe one of them is also being lowered to 0.5 akt dramatic lowering. Of the bid deposit and they deployment deposit and we've received feedback from the community that this is somewhat of a blocker when you're creating. + +Scott Carruthers: Dozens or hundreds of deployments on this a lot of akt that was put into mascara and deposites part previously. So we've taken that feedback and we'll know introduce that Network change and I think there's going to be far less friction going forward. + +Scott Carruthers: So quick recap and run down of some of the things that are upcoming and the main attend upgrade any questions or concerns in those regards. + +Scott Carruthers: Okay, I'm gonna stop sharing that and I'll go back to just sharing this. + +Scott Carruthers: if I can find a share I'll just go back to sharing the slide + +Scott Carruthers: just as a placeholder. So really that concludes then our main parts of our agenda, of course in six support. We always want to go through the triage of open issues. And then also we like to open it up to the floor for a lot of times. We have some Insiders. In attendance, so today is just myself and Andy and Deval from the Prater team. So we don't really have a representatives from the Insiders group. A lot of times insiders will bring up things that they're seeing within the community and within Discord and other support channels. So without Insider participation in that today, I would say that. For my own perspective a majority of the activity or the last couple weeks since our last six support probably. mostly involved upgrade some so we've recently introduced feature Discovery and + +Scott Carruthers: Into the provider code base. So We've had a lot of activity recently and just helping providers as they go through the upgrade to current provider version 054. I know that the Prater team is also enabled that upgrade as well. So I think both of our teams are just assisting we haven't had any Showstoppers or major issues, but of course anytime we're going through that kind of upgrade activity. There can be one-off anomalies or just some clarification on the documentation or the upgrade procedure. So I would say that that's a majority of what I've seen within the community in the last couple weeks and since our last meeting Andy or Deval do you have anything that you would want to highlight on prominent support issues that have come up in the last couple weeks? + +Scott Carruthers: Okay. + +Scott Carruthers: Yeah, Yeah and definitely appreciate the Prater team assisting in Providers the build via the Prater app to the current 054 version so that we can have feature discovery. Enabled on a vast majority of may not providers. + +Scott Carruthers: So there aren't any other issues or support focuses that we want to highlight over the last couple weeks one final thing that I wanted to mention In Deval, this may be of interest to yourself and possibly some others listening to this transcript. We're going through a migration of so the network website migrated several weeks ago. And is been the plan to migrate the documentation site to the same platform. So the new network site is running on a Astro platform and we created a new version of the documentation site on Astro as well. And this is the documentation site that you'll + +00:10:00 + +Scott Carruthers: Visit if you go to network and hit on the docs link, it goes to that new site, but we've primarily been updating documentation and the community is continue to use the old documentation site as of this morning. We've actually transitioned to the new documentation site. We're going through some cleanup and ensuring that all the documentation that have been updated or added on the old documentation site is now added on the new documentation site and there are a couple of holes there that were trying to remedy is as soon as we possibly can but just to ensure that everyone is aware. I just want to ensure that there's no confusion as someone visits data cost.network it actually now redirects to Not as some is no longer a subdomain of docs out of network, but it's now a path. So the new Dockside is available at a cost.network. + +Scott Carruthers: Backslash docs so on the docs path instead of a subdomain and as of this morning anybody that visits docstatacos.network the old URL is now redirected to the new documentation site. So a lot there and I don't want that to be confusing but just the main takeaway is as of this morning. We're now live on the new documentation site and if anyone sees a redirect when they're trying to visit the old URL or they're just a little bit surprised when they visit the documentation site that the look in the field is now different. That's the reason we introduce the new documentation site as of this morning. So Tower and the rest of the team wanted me to mention that on this call just to make sure everyone is aware. + +Deval Patel: You got it. + +Scott Carruthers: So that's And that's really all I had so Andy and Deval OS you have any matters that you want to? Bring Outside of that. I think we can wrap up. + +Andrey Arapov: Yeah, I think we can wrap up. Thank you very much, Scott. Thank you. + +Scott Carruthers: Okay. + +Deval Patel: Yes. Thank you rest. Thank you. + +Scott Carruthers: Thanks a lot guys. I'm gonna stop the recording and I'll stop the meeting. So yeah, I appreciate it guys and I'll see you next time. Okay, you too, okay. + +Andrey Arapov: to have a good + +Meeting ended after 00:13:15 👋 + + From 952d99a811728446aa9f49e877e9dfa05f601c9f Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 19 Mar 2024 22:40:40 -0400 Subject: [PATCH 018/138] sig-support Update 028-2024-03-06.md update notes Signed-off-by: Drinkwater --- sig-support/meetings/028-2024-03-06.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/sig-support/meetings/028-2024-03-06.md b/sig-support/meetings/028-2024-03-06.md index ddfd53b6..bc7957f2 100644 --- a/sig-support/meetings/028-2024-03-06.md +++ b/sig-support/meetings/028-2024-03-06.md @@ -24,16 +24,24 @@ # Meeting Notes - Scott led the group in triaging issues in the support repo. - +- Scott talked about [issue 186](https://github.com/akash-network/support/issues/186). Artur made this issue. This is marked "p2". +- Scott talked about the Mainnet Upgrade [issue 189](https://github.com/akash-network/support/issues/189). This is marked "p1". +- Scott talked about in detail about the gas issues that will be solved by this Mainnet upgrade. +- Scott talked about the parameter changes that are on chain now where the deposit amounts will decrease from 5 AKT to 0.5AKT. ### Support - +- Scott has noticed that the majority of activity that he has seen is around provider upgrades, and use of feature discovery service. +- Documentation is updated as users interact with it. +- Andy and Deval have seen typical behaviour in Discord as well. +- Documentation site on the new akash.network website needs some migration. Some clean up is ongoing. ### Action Items +- Mainnet Upgrade is planned for March 13th, 2024 if it passes. +- Core team and wg-akash-website group are working on docs site to make sure migration is finished. # **Transcript** From 511fb9f690e3cfe898f3951be0a7ca7028f49138 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 19 Mar 2024 22:49:31 -0400 Subject: [PATCH 019/138] sig-support Update README.md add meeting notes, recordings, and transcript to meeting table Signed-off-by: Drinkwater --- sig-support/README.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/sig-support/README.md b/sig-support/README.md index 3d286b7f..467c5586 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -42,11 +42,15 @@ sig-support is responsible for defining mechanics of how support works at Akash | #24 | Wed, December 20, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/24-2023-12-20.md)|[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/24-2023-12-20.md#transcript)|[Link](https://kesic5sqastbfceerxf7d5zcqcumbjpipfw45q6oxxmcguazpotq.arweave.net/USSBdlAEphKIhI3L8fcigKjApeh5bc7Dzr3YI1AZe6c) | #25 | Wed, January 10, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/025-2024-01-10.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/025-2024-01-10.md#transcript) |[Link](https://p263aeernjmdkonkrihc227wya76yjyvivs5pkojdjx63unz4lha.arweave.net/fr2wEJFqWDU5qooOLWv2wD_sJxVFZdepyRpv7dG54s4) | #26 | Wed, January 24, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/026-2024-01-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/026-2024-01-24.md#transcript) |[Link](https://47vntytp4ni2s5p2h2qyh5nuqywowtwne2fx4ddudv7iyl3hu5rq.arweave.net/5-rZ4m_jUal1-j6hg_W0hizrTs0mi34MdB1-jC9np2M) -| #27 | Wed, February 07, 2024 07:00 AM PT (Pacific Time) | | | -| #25 | Wed, February 21, 2024 07:00 AM PT (Pacific Time) | | | -| #26 | Wed, March 06, 2024 07:00 AM PT (Pacific Time) | | | -| #27 | Wed, March 20, 2024 07:00 AM PT (Pacific Time) | | | - +| #27 | Wed, February 21, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/027-2024-02-21.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/027-2024-02-21.md#transcript) |[Link](https://cwya3qcl4ejhb75ct5d4vgcoyhsce46zvv2q42khi6kc76qhsxpq.arweave.net/FbANwEvhEnD_op9HyphOweQic9mtdQ5pR0eUL_oHld8) +| #28 | Wed, March 06, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/028-2024-03-06.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/028-2024-03-06.md#transcript) |[Link](https://xut7rmdqwninrlvm75t7cxmmpgrt4tyboramnw3b2rcpaa6gy76a.arweave.net/vSf4sHCzUNiurP9n8V2MeaM-TwF0QMbbYdRE8APGx_w) +| #29 | Wed, March 20, 2024 08:00 AM PT (Pacific Time) | | | +| #30 | Wed, April 30, 2024 08:00 AM PT (Pacific Time) | | | +| #31 | Wed, April 17, 2024 08:00 AM PT (Pacific Time) | | | +| #32 | Wed, May 01, 2024 08:00 AM PT (Pacific Time) | | | +| #33 | Wed, May 15, 2024 08:00 AM PT (Pacific Time) | | | +| #34 | Wed, May 29, 2024 08:00 AM PT (Pacific Time) | | | +| #35 | Wed, June 12, 2024 08:00 AM PT (Pacific Time) | | | From 64cf4348f43fe2ded17e4865bf6a1a7128748cd9 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 20 Mar 2024 12:53:45 -0400 Subject: [PATCH 020/138] wg-provider-audits Update and rename README.md to README.md Signed-off-by: Drinkwater --- wg-provider-audit/README.md | 36 ++++++++++++++++++++++++++++++++ wg-provider-monitoring/README.md | 34 ------------------------------ 2 files changed, 36 insertions(+), 34 deletions(-) create mode 100644 wg-provider-audit/README.md delete mode 100644 wg-provider-monitoring/README.md diff --git a/wg-provider-audit/README.md b/wg-provider-audit/README.md new file mode 100644 index 00000000..7f94e530 --- /dev/null +++ b/wg-provider-audit/README.md @@ -0,0 +1,36 @@ +--- +title: "Provider Audit Working Group" +date: 2023-1-10T00:19:20-08:00 +--- + +# Akash Network Provider Audit Working Group + +This working group is for developing an open source auditor tool for providers. The Pi3 team requested funds for building this open source tool, which passed on chain + +## Meetings + +[3rd Wednesday of Every Month](https://calendar.google.com/calendar/u/0?cid=Y18yNWU1ZTM3NDhlNGM0YWI3YTU1ZjQxZmJjNWViZWJjYzBhMDNiNDBmYjAyODc4NWYxNDE1OWJmYWViZWExMmUyQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20) + + +## Contacts + +- [Discord](https://discord.com/channels/747885925232672829/1200172631480094771/1202611858008187001) + +## Goals + +- Pi3 is looking to contribute to the Cloudmos indexer to expand their tasks to include examples such as: benchmarking, testing RPC nodes, tracking the lease uptime of providers, and other trackable metrics to include in their API. We would also want snapshots of this database to be made semi-regularly, if there is demand for this. + +- Pi3 Team is looking to create our own open source services: + - Stat-based, tier-based auditing service, where filtering API can be used on Cloudmos & signing can happen for CLI users. Example on the filtering this would allow. + - General auditing, where we can have a general audit similar to how Overclock Labs sign their providers, and how Moultrie Audits signed providers. We create a set of criteria that we think are "good enough," and sign generally from this. + - KYC-based auditing on providers and tenants. Details for this are TBD and to do the KYC, we would be working with companies that do this as a service. + - Yet another Akash Stats Page, if there is demand for one. In the past weeks, some questions have not been able to be responded to due to data not being formatted in such a way. + - To our knowledge, this relates to: rich lists as a pie graph, the community pool growth over time, and provider filtering shown as a demo here. + +## PRDs and other documentation + +- [Proposal 242](https://www.mintscan.io/akash/proposals/242) + +## Related SIGs + +- [sig-provider](../sig-providers/README.md) diff --git a/wg-provider-monitoring/README.md b/wg-provider-monitoring/README.md deleted file mode 100644 index 01173304..00000000 --- a/wg-provider-monitoring/README.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: "Provider Monitoring Working Group" -date: 2023-1-10T00:19:20-08:00 ---- - -# Akash Network Provider Monitoring Working Group - -This working group is for defining any specifications and scope of code changes for making it easy to monitor providers. Note that this working group does not deal with provider analytics but is considered with pure monitoring of the infrastructure (for improved uptime, SLA and such) - -## Meetings - -To be scheduled - -## Lead(s) - -- Anil Murty, Overclock Labs (@anilmurty) -- Jigar Patel, Praetor App (@jigar-arc10) -- Joao Luna, Quasarch (@cloud-j-luna) - -## Contacts - -- [Discord](https://discord.com/channels/747885925232672829/1070501619625623633) - -## Goals - -- Discuss challenges of monitoring providers -- Write spec - -## PRDs and other documentation -TBD - -## Related SIGs - -- [sig-provider](../sig-providers/README.md) From 7b4e131c6df4f4d6c756e1f15bdeb7523983aa3a Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Fri, 22 Mar 2024 11:39:42 -0400 Subject: [PATCH 021/138] steering committee Create 013-2024-03-07.md (#503) * steering committee Create 013-2024-03-07.md Signed-off-by: Drinkwater * steering committee - Update 013-2024-03-07.md add recording Signed-off-by: Drinkwater * steering committee Update 013-2024-03-07.md Signed-off-by: Drinkwater --------- Signed-off-by: Drinkwater --- committee-steering/meetings/013-2024-03-07.md | 403 ++++++++++++++++++ 1 file changed, 403 insertions(+) create mode 100644 committee-steering/meetings/013-2024-03-07.md diff --git a/committee-steering/meetings/013-2024-03-07.md b/committee-steering/meetings/013-2024-03-07.md new file mode 100644 index 00000000..23fcd5fb --- /dev/null +++ b/committee-steering/meetings/013-2024-03-07.md @@ -0,0 +1,403 @@ +# Akash Network - Steering Committee - Meeting #13 + +## Agenda + +- Review / discuss / address any community feedback, grievances, or conflicts. +- Review [projects list](../projects-list/README.md), prioritize / add / remove if necessary. +- A look at open discussions in [Github Discussions](https://github.com/orgs/akash-network/discussions). +- Open up to any other questions from the community. + +## Meeting Details + +- Date: Thursday, March 7th, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://aqjulyegruxs4xdwltfkkxqieagkmqc7dcbewovdw2wk7tj72hka.arweave.net/BBNF4IaNLy5cdlzKpV4IIAymQF8Ygks6o7asr80_0dQ) +- [Transcript](#transcript) + +## Committee + +- Adam Bozanich, Overclock Labs +- Anil Murty, Overclock Labs +- Artur Troian, Overclock Labs +- Greg Osuri, Overclock Labs +- Scott Caruthers, Overclock Labs + +## Participants + +- Anil Murty +- Artur Troian +- B S +- Cheng Wang +- Deathless +- Denis Lelic +- Deval Patel +- Greg Osuri +- Joao Luna +- Julius Haus +- LOWO +- Maxime Beauchamp +- Moss Business +- Pierre-Andre Manseau +- Robert Del Rey +- Scott Carruthers +- Scott Hewitson +- Zach Ross + +## Notes: + +- Anil led the group through the steering committee agenda. +- Anil asked if there was any community feedback. +- Deval talked about meeting members of the team at EthDenver. Deval shared the feature discovery upgrades are going well with Praetor built providers. +- Anil reviewed projects. + + +### Projects: + +- Anil started with community and marketing board. The group talked about EthDenver 2024. Max talked about how amazing EthDenver was. +- Max talked about how many people knew Akash at the Booth, and he talked about all the events that the team participated in. +- Cheng mentioned that EthDenver exceeded all of our expecations, and talked about Akash Accelerate. +- Anil talked about Nvidia GTC 2024. Cheng added that Akash is working with Brev Dev to share a booth. Anil mentioned that Brev is a web2 platform, so it will great to be along side them. +- Artur talked about KubeCon EU in Paris. This will be the first Akash presence at Kubecon. Insiders will be helping to run the booth. +- Anil mentioned that it would be amazing to talk to Kubernetes developers. +- Anil talked about GPU Pricing page. With the Provider Incentives programs, there are more resources online. Pricing page will help people to understand how many GPUs of a certain type, price range, and beyond. +- GPU Pricing will be added to Cloudmos and Console. +- Cheng talked about Akash Accelerate 2024 event, which is up for discussion. This will be a single day event leading up to Consensus 2024. +- Cheng also talked about how the presence will be increased for future events in Q3 and Q4. Greg talked about how there should be a working group for future events. +- Anil talked about the Committed Pool. It is hard to find the right kind of GPUs, but there have been some datacenters that have come onto the Akash Network via the committed Pools. These are 1 year committments. +- Andrey and Shimpa have been helping to monitor uptime. +- Anil talked about the Liquidity Pool. This pool will be more on demand, and there needs to be work done on setting up a mechanism. +- Robert talked about the Zealy campaign. Robert thanked Greg who donated more AKT to the program. There are many missions on Zealy for deploying, providers, content, and beyond. + + +#### [Product and Engineering Board / Community + Marketing Board](https://github.com/orgs/akash-network/projects) + +- Anil talked about the analytics being moved to stats.akash.network. +- Anil talked about improvements to Cloudmos API and improvements to Cloudmos. +- Anil and Artur talked about Feature Discovery Service. This was released at the beginning of March 2024. Implementation will continue with a number of new features coming soon. +- Anil talked about the paramater change for bid deployment amount. The minimum bid escrow has been changed from 5akt to 0.5akt. This is on chain for vote. +- Deval talked about how these changes will have a positive impact for providers as well. Deval also talked about the gas issues that will be apart of the future network upgrade that is up for vote right now. If that vote passes, the network upgrade will happen March 13th, 2024. +- Support for SHM is coming soon. This is code complete. Anil mentioned that a lot of users have been looking for this future. + + +### Github Discussions: + +- Akash Accelerate has been discussed in detail, and the comments have been overwhelmingly positive. +- Anil talked about discussion #490 +- Anil talked about discusion 488. Support Cancel Unstaking may not be possible right now. Anil does not believe this is a huge priority. +- Anil talked about discussion 487. Anil mentioned this is very well written. Anil talked about challenges around building a ML too. Anil asked can this be built on Cloudmos/Console. +- Anil also talked about connecting with projects like Brev Dev that already have traction. Deval mentioned that Awesome Akash +- Anil talked about discussion #496. Greg mentioned there is no use case for Smart Contracts on Akash. Greg and Artur would reccomend against moving forward with any smart contracts on Akash, at this tine. Anil added some comments to the discussion. +- Greg is open to anyone building on Akash. ICA is maybe something that can be prioritized because there are use cases there. +- Artur talked about Packet Forwarding. Packet forwardinng will help with discussion 495. +- Artur talked about Network Upgrades. The core team will have network upgrades coming soon. There will a move to Comsmos SDK 47. + +## Open Discussion + +- Cheng talked about the Akash Hackathon. Tracks are being developed, so please feel free to chime in. +- There is a working group for the Akash Hackathon. + +### Action Items: + +- Please get involved in all of the discussions on github. +- A working group should be spun up for events and a bigger presence. +- Add a Zealy card to the community and marketing board. +- March 13th, 2024 Mainnet Upgrade, pending vote passing. +- Artur will look at [discussion 495](https://github.com/orgs/akash-network/discussions/495). +- Artur will work on + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Anil Murty: All right, everyone and welcome to another steering committee meeting. for March and we'll see if we get a few more people. But as usual the agenda for these meetings is to go over any sort of community feedback previous or conflicts. + +Anil Murty: First give a few minutes for that and then talk about any progress of being made on projects that are in the works right now both across engineering and product as well as marketing and community. And then review any open discussions that have been coming into the discussion board. And then in general prioritize things based on. When the topic was created as there been a lot of activity in terms of people part in them. and if there's somebody from that specific team the person that submitted to discussion on the call So that's General agenda for today. Any questions from anyone on the call before we start digging into these? + +Anil Murty: Okay, so we'll get started with some general feedback from anyone. Is there any sort of community feedback as far as things not going so any sort of grievances or anything else that anybody wants to bring up? + +Anil Murty: Usually yeah, pretty silent response to this one. But yeah, I don't know if there's anything positive you want it that's welcome as well. Yeah, they will go ahead. + +Deval Patel: Yeah, thank you so much for giving us these opportunity. I met this week Greg Maxine and other team members from It was nice meeting you all in first time at Greg in person. Other than that, we are working with a couple of providers to bring their machines on board and I'll be provided the feature Discovery right now. So it The upgrade is working fine. So we see providers are creating machines. Other than that, there is something comes up here to support them in general. We see good things are coming to attach. So yeah. + +Anil Murty: Thank you for sharing all that positive sentiment. You will appreciate that Greg. Did you have you hand up or? + +Greg Osuri: No other accident I want to do. + +Anil Murty: Okay. + +Greg Osuri: I wanted to clap my hands, but it was really good meeting you Deval and the team. We could finally connect after all these years. + +Anil Murty: awesome All right, any other feedback from anyone on the call? I know there's a few people that parked in the last couple of minutes. Give it a few seconds to see if anybody else wants to. want to talk + +Anil Murty: Okay, I think there is a no. The next thing on the agenda is to review some of the projects that are in progress or what completely recently. So for those that are joining us for the first time you can head over into Akash Network into the repository here and click on projects and what you should see is two boards here. You should see a board that tracks all the world that's happening on the product and Engineering side and then the tracks all the things happening on the marketing Community side. So that's something that Anyone that wants to look at it? + +Anil Murty: So I'm going to start with marketing Community for a change because as Deval said we just bunch of people who already did Denver so it'll be good to sort of talk about those things first. So obviously top of Mind here is Eid Denver just got over. I don't know if somebody from either maybe Adam or anybody that actually really went to Denver could give us just a quick summary of any of the highlights or things that are worth talking about + +Anil Murty: Good Max. + +Maxime Beauchamp: They run. So yeah, the event was amazing. There's so many feedback from the people that we met there. There's a bunch of workshops that we did and I did one the first day that I arrived at the Desai house. And everyone was super attended asking questions super interested. During the booth so many people came to the boot knowing a cast a lot of people. wanted to know more but I was surprised by how many people were actually already aware of Akash and just excited to see us in person. + +00:05:00 + +Maxime Beauchamp: I know Greg did a bunch of talks and a lot of people the rooms were all packed and the demos worked perfectly. So with a minute an amazing event, I think overall. + +Anil Murty: Yeah, I couldn't make it out there in but based on what I saw. I just got the feeling that compared to even pasties Denver's this one was widely successful particularly given that we're so associated with the cosmos ecosystem. It was awesome to see, as pretty much be taking center stage on multiple events. So super cool Artur. Did I see your hand up? Was there something you wanted to add? + +Artur Troian: no, there was + +Anil Murty: Okay So that's kind of the main thing. I think on the completed side, unless Adam or Cheng. You want to add any other from the completed list coaching. + +Cheng Wang: Yeah not know so much the completed list here, but just kind of my springboarding off of the Denver. I think when going into this event, we weren't sure how big or successful it would be and this vastly reality vastly exceeded our expectations here and this really brings I think really powerfully into the momentum at least for akashic salary, which is caution networks first summit ever. And so just one of to throw that into just it's a really really good sign and gives us the momentum going caring into this for sure. + +Anil Murty: super cool Awesome, which brings us to the next conference that we are going to have a prison set that is NVIDIA GTC coming up in a couple of weeks here. + +Anil Murty: Believe the plan here is to have a presence with another partner of ours and then, have obviously a bunch of meetings with folks that you up there. I don't think Adam is on the call. I don't Cheng or somebody else. If you want to add anything else to that. That's basically the kind of summary that I know of. + +Cheng Wang: Yeah, so Nvidia GTC conference here. We are working with brevdev. And so they have the booth primarily here and we'll be kind of writing their coattails on that because they got access to the booth and everything like that through Nvidia and they have pretty good sweet terms there. So we Co will be kind of like a secondary Marquee at their Booth it'll bread that primarily will be hosting a couple of small things one is going to be more very tiny person-ish VIP dinner before that happens. So we're currently, reaching out to Partners who will be there in perspective folks that we want to connect with right specifically. Let's say in India, that would be really nice. Some of the red team will be there as well. But yeah, as far as attendance goes, I think and Neil and myself will be there in addition to Zach on the core team and that's what we have. yeah the come and take it is coming I have + +Cheng Wang: gigantic box of merch that is shipping to my house because I am a few hour drive away. So I'll be driving down there and muelling our stuff over. + +Anil Murty: Looking forward to this. I wish I could have made it to eat Denver, but I'm really looking forward to in video GTC in a couple of weeks. And as Cheng said brev, is this platform that is basically for all intensive purposes where besides over two platform at a conference that is not a crypto conference is a huge thing. So I think hopefully that will be a very successful Endeavor for us. + +Greg Osuri: We should read about it. + +Anil Murty: awesome + +Greg Osuri: We'll add a few hundred to the market cap. + +Anil Murty: Thank you. exactly + +Greg Osuri: You see what anchor did anchored guys yesterday tweeted saying that we're going to GTC conference and the token pump 40% Just going to GTC. + +Anil Murty: it's + +Greg Osuri: It's nuts. + +Anil Murty: awesome at the same time that Nvidia GTC is happening. There's also kubecon you happening in the same weekend. So at least on the core team. We've kind of split resources between these two. So from our side, I believe Artur is going I don't know if anybody else is on the core team side, and I know there's some folks with the community that are going as well. but + +Artur Troian: Yeah, thanks so it's gonna be our first presence on keep calling. It's gonna be kind of small, but I think it should be really cool to be To see once again all our insiders and second of all. + +00:10:00 + +Artur Troian: Speak to people that actually develop interesting for asking during this features like you videos and so forth. I believe you're gonna have both there so it should be fun. and considering huge success of Ethan where I Super excited to just be there and how part of another team members promote the car on that side So yeah, it's gonna be I believe from Akash other was me and me and then couple inside there as well. + +Anil Murty: amazing and I think it'll be cool to also figure out if you can find non crypto folks that want to build. On top of our open source code base That'll be amazing win out of this. I think. So sweet, let's see. What else you want to talk about here. So you Jesse hand up. + +Anil Murty: no, okay. + +Anil Murty: So I think out of the remaining things the one that might be most relevant to talk about maybe is the GPU pricing page that we're working on. So one of the things that we realized is, we just to backtrack a little bit if you've been following what we've been announcing we brought up a bunch of GPU Supply in relation to the committee pool from the GPU incentives. We did this earlier this week. And so one of the things we're trying to do is improve the website so that it's very clear to people that these GPS are available and in certain price point similar to the marketing message that was sent out through the cash Network handle earlier this week about h100 as well as a 6000 becoming available. So this task is basically to add GPU page. So if you're curious about this, you can take this task as well. So it's very active. + +Anil Murty: Ended right now. Once the website thing is done or more or less in parallel. We're also going to be looking at a modification to the cloud mode slash Akash console UI so that when people use the renter GPU workflow, they get bids that are very tailored to GPU pricing and shows the a minimum pricing and average that sort of thing so that we're very focused on answering the question that people have when they come looking for gpus, which is how many of them are utilize right now? How many can I get what models are there? And what's the lowest price I can get potentially from you and so that's kind of the goal here as well as for the work that's going to be done within the console Any questions on that one before we move on? + +Anil Murty: awesome All right. the six. That's great. o. So other than that, I don't know and even from the marketing team want to suggest anything else you want to talk about. I think that pretty much covers these things in terms of things. We want to talk about maybe Akash accelerated if anybody wants to talk about a little bit more about what the plans there are and what's expected. + +Cheng Wang: Yeah, for Yeah, Akash accelerate and Greg. I know this is your brainchild near to you. So please chime in. It's going to be a single day in May. I believe the Monday prior to the consensus conference right leading up into consensus. I think which starts on Wednesday. It'll be a single day and the theme around it. I mean it's up on GitHub for discussion and I think as well but around permission really open systems right with and with Akash being a Cornerstone of that open system and I think the best River presentation of that but that's kind of the thing around it. It's gonna be an awesome Texas a single day starting nine 10ish in the morning and three fourish in the afternoon with breaks and with a break in between of course Very speakers that we're trying to get a hold of if the community things there is there are speakers who will be a good fit there and you want to nominate them or just kind of let us know. Please do and + +Cheng Wang: Kind of it for now one. Last PSA is with conferences really being the success again of ethana really demonstrating it with future Community proposals that we will be submitting really in a week or two for Q2 and Q4 conferences for the rest of the year. caution will be attending we're going to really increase the budget. We're going to be proposing right in an effort to really establish a cautious of Presence in relevant conferences. Obviously, we're not going to just spray and pray but with the conferences, we will be attending and making sure that we have a very strong Marquee to establish a brand. + +00:15:00 + +Greg Osuri: Yeah, so it was very obvious. I mean we had very small presence but incredible reception right so I think improving our Presence will be incredibly valuable considering we have a bull market coming. Really I think more people need to know about so I want to see more effort from the community and what different things we can do at the event, IDE dinners every day every night for events around happy hours, to workshops and a lot of ideas That we could do So I think it'd be great to have some working group on this. to make some recommendations as to what we need to do better events. + +Anil Murty: Because we have will spin up a working group. Start winds coming ideas are not good. They will. + +Deval Patel: It will be in Austin right we can plan ahead for yourself. + +Anil Murty: Yeah, yeah in concert with consensus right Cheng. Yep. + +Cheng Wang: Yeah consensus starts on a Wednesday that week in May. I forget exactly which day we're planning to do it on a Monday which people will be coming in, early and stuff like that. So we don't want to overlap with consensus and get kind of drowned out right since it's our first one. But yeah, it'll be in the same week as consensus Wednesday will be on Monday. + +Anil Murty: Yeah, and while the chength and Greg were talking I just realized a couple of things that I missed previously because they were down the list, but I just want to call out. one of the items here is establishing sources in contracts for the committee pool providers. So this has been a task that Chang Greg myself and a few folks from the community of spent a lot of time in the last few weeks on and we've talked to I think probably close to a dozen different sources for these gpus and it's been noted very well in the original discussion. It's been kind of hard to get access to the right age 100's a180s even in 1880s in particular any six thousands part. + +Anil Murty: as you've seen from the announcement, we have two really good sources both of which we have used in the past. So one of them has been a provider on the network for several months that is now supplying as the RTX 40 90s as well as the h100 hex cluster and then another provider that was used for the thumper AI training exercise that's applying as the h100 pcie nodes as well as the a6000 nodes. So that's what's up on the network right. Now. You should have seen a boost in the number of gpus by close to 150. And then we're on track to get an additional 64 A180 gpus PCI nodes from that seems like in providers so + +Anil Murty: So that's all squared away for the most part. We'll just be monitoring the providers we've set up monitoring for them so we can track up time and stuff huge. Thanks to Andre on our side for a lot of work on that as well as with the shimper ship has been huge in terms of helping out on that from the community. And so now that we have, decent amount of Supply on the committed pool. We are going to shift our focus in the next few days to the liquidity mining portion of this so, Cheng myself folks with the community anybody that wants to participate in this we're going to work on a mechanism for how the liquidity mining pool portion of this is going to be run in terms of people getting gpus. So the key difference just for people that are not available. It is the first pool which is the committee pool is higher in gpus and the idea it's a commitment for a year and + +Anil Murty: In public commitment for years because number one these are hard to get so, you want to retain them for a year and second when your commitment you get a significantly better pricing. And so that's kind of the reasoning for why we put those in the committee pool. The liquidity mining pool is going to be lower ngpus. A lot of these are going to be potentially attractive to minors that have had RTX 40 90s 30 60s 1080s, whatever you call whatever those might be and it's going to be more on demand to Commitment. So we're gonna iron out the process for this there's a lot of work involved in terms of defining a process as well as building tools that can track the up time of the providers and as well as count, the fact that the resources that we're committed on day one remain on each day throughout the entire time of the incentives. So all that work needs to happen before we can open this up and that's the reason for why this is taking a little bit longer. + +00:20:00 + +Anil Murty: But that's a huge Focus now going forward. + +Anil Murty: I think that's pretty much all the things on the marketing and Community side and there's anybody wants to bring up anything else. Go ahead Robert. + +Robert Del Rey: It's live for a little over one week now. No, it's gonna be one week tomorrow. So far, we got 41 submissions. Some of them are Some of them are spam. yeah, that's how it is. This is gonna be a month campaign. I want to actually take this moment to thank Greg for giving us a little bit more funding. Scott. Thank you Tyler as So for making this a reality on my side. I'm doing social media outreach. so I'm in talks will keep people in the cosmos people system and beyond to see if we can get these further and more people can know about it today. I'm going to cry to meet up and I'm gonna talk to people about these + +Robert Del Rey: and yeah so far everything is looking good. We have got lots of feedbacks. I in the telegram. I've seen questions in the Discord. There was see a question that came up on silly and then the guy went to the deployments chat and he got assistance super appreciative of that and if you guys have any feedbacks or things that could be interesting to make them a game, but with me and I can convert them into a mission right now we have missions about creating web apps dep On a cache. We have some content creation missions as well. They got missions for providers and more missions are in the work. So just wanted to be update on that guys on the sitting committee called. Yep. + +Anil Murty: Thank obert. That is truly amazing work and I just want to say that personally I've seen other projects put out zeli missions. I don't think I've participating any of them. But I've seen a lot of them put them out and they've been super awesome that you're taking on the initiative to do this for just a quick question. Do you know if there's a card on this board somewhere for this Elite that's happening. If not, it'll be nice to get one of those cards here. So people are bad. + +Robert Del Rey: I don't remember where I saw it, but I'm pretty sure I believe I sold one with a silly name on it. I don't know what it is. We don't have discussion for the proposal. + +Anil Murty: Okay. + +Robert Del Rey: I can send you the link for that. + +Anil Murty: Sounds good. We'll create a card for that. Awesome. It was yep, if there's nothing else in the marketing Community side. I'm going to move on to the product engineering side of things. + +Anil Murty: So bunch of things happened on the product and Engineering side as well. So just moving on to the released column here. and I think all the way down a little bit about AMD maybe so first off the cloud most team delivered essentially first a big chunk of what we're calling the quote-encode Rebrand of Const Cloud, mostly cash console and one of the things there was to split off what used to be calculates inside the UI to its own page called stats for a custom Network. And so this work is complete. I'm sure bunch of you have seen this page already, but I just wanted to call it that anything else you want to add on this. Max from cloudmusting + +Maxime Beauchamp: No, that's pretty much It's gonna be upgraded probably in the future with more stats. + +Anil Murty: Yep. It's really cool. We're going to look at some potential small design changes to this over time and then get feedback from the community as well. So if you have any situations for the stats page to post them on Discord or anybody in the core Team Max myself and would love to get the feedback. So that's number one. + +Anil Murty: The problem mostly also worked on refactoring and improving the Club Moss API so that other folks that want to pull this information. Can you utilize it the primary to customers if you can call them customers for this right now are the pretor team and the folks working on the website. So great work here as well. I don't know trade routine if you have any feedback that you want to bring in here or everything's good when you say + +00:25:00 + +Anil Murty: Awesome, and then the next big thing over here or not a big thing, but relatively small thing but something that hopefully will make people aware that we support payments is when you go into the UI before the way to change from uaqt to you usdc was kind of two levels deep in the UI when you enter deploy something and so this address is that thing and sort of made it up top relatively small change hopefully it makes it pretty clear to people that we support usdc comments. And in the big thing that Artur in Scott from the core team have been working on for several weeks now is supporting a feature called feature Discovery service, which basically a service that allows that they're basically discovers all the resources on again provider and exposes them to an API Arturo Scott free to jump in or here talk about all the work that you've done you. + +Artur Troian: Yeah things so this is so far from Reading one of the biggest referrings for the last year related to the provider itself a year behind this entire thing is to remove human factor from first of all from library in manually notes and contributes. the second of all is to + +Artur Troian: make discovery of the provider Hardware snapshots. + +Artur Troian: Which automated and the implementation was a little bit positive for us. We had quite a few hiccups. However than obviously testing and everything else called us to bring this to pretty much stable level and release it last week. So with this stage what it does is sweeps entire providers a lot of things related to the GPU of what I really use on so forth and then positive through to the cloud Moss it allows to display. For example, how many a hundreds located on the network on critical provider? How many of them being used on so forth? the design of the future is complete implementation is not complete. We are planning to add quite a little things to be in the next few months. + +Artur Troian: Are expand information about memory? CPU to bring detailed CPU information what kind of features it supports and so forth than hopefully also that we're gonna be able to enable automated labeling of the It should provider manual interaction completely from the perspective I think that is it. + +Anil Murty: Thanks Artur that detailed update and just to retreat what artist said the primary outcome of this Mammoth exercises. Basically this enables two things one is today when you go to deploy something in Cloud Moss console or literally anything that uses that there was an You can see providers and you can see model names of gpus but when you actually created these or when you want to just go and look at how many gpus are on the network. There's no way to do that. So there's no way for somebody just go onto Cloud Moss today and find out A1 or 80s on the network how many of them are being utilize and so this will lead into much better you user experience from that standpoint and then also help us build that pricing phase that we talked about. + +Anil Murty: So amazing work. the big thing that is going to be coming up a relatively small change but a big impact something that multiple people have surfaced up including the parade routine as well as the state on team is as the price of akt has appreciated as well as the number of leases that are created on the network there's a huge tax on the provider side as well as not so much on the tenant side, but more of the provider side where every time the provider wants bunch of vids. They've got to submit five akt deposit times the number of bits that I want to create and that's a huge burden in terms of the amount of deposits they got to make + +Anil Murty: and so the primary change for reducing the minimum requirement for what that bit should be and changing it from 580 to 0.58 which is effectively a 90% discount or 90% reduction that is on chain right now the governance proposal and so once that passes this change is going to affect good Artur and then they will after that. + +00:30:00 + +Artur Troian: Yeah, just a little connection to that. So it's not exactly the talks. it's very deposit on both sides and provider. This deposit is returned back the provider as soon as our beat is being closed. So for example provider loses or one product realize and listen to close those funds returned to the provider and the full amount. For the tenant any unused amount from escrow account is going to be returned back to the account. So the effectively task so it attacks is just the deposit. that + +Artur Troian: there is a for deployment to be up and running. And in terms of Provider the positive we are still dividing if it actually necessary to have it. We'll see we might actually remove it in future, but we decided to just lower it for now to he's process for everyone. + +Anil Murty: Yep enough. I used the word tax Loosely. But yeah, it's basically a deposit that we will put for in order to bid on workloads and then get it back when the bit closes Go ahead. They will. + +Deval Patel: Yeah, thank you for doing this for us. the big deployment amount change that mostly affects the deployer I would say right but as well as it, gives the more liquidity to provide us to support more and more developments with the lower amount of Equity right as well. As I think there is another I art in this one somewhere. It changes the transaction cost of updating provider. That's a big helper for us because people are calling us cameras in the Discord. So when the transaction charge three akd to update a provided so Thank you. + +Artur Troian: So that's the different discussion. I believe thing that you just mentioned you just called gas Calculation so that's another topic. We have Network upgrade for it coming up next Wednesday. because this update is quite quick and… + +Deval Patel: Yeah. + +Artur Troian: We are actually working right now. We haven't posted any information in the issues just yet. As soon as we rob everything up releases We are going to put information into the issues as well as in the Discord explaining what was going on. It wasn't actually a box it was by Design and + +Artur Troian: there was a little thing that we missed a couple years ago not actually missed that was intentionally. But because the amount of business grown up it started to cause pain a little bit. Anyways, we have removed this part for now. Once again, you're gonna provide all the details on what's going on and why this issue was causing gas to go 200 million years on some transactions. Is going to be fixed next one today and everybody should be happy with. + +Deval Patel: Yeah, thank you so much. + +Anil Murty: awesome And then following that there is work that has started for this feature, which it's more like removing the limitation that you have had but you can even call it a feature but essentially being able to specify the size of shared memory that you would want when doing a deployment. This has come up over the course of us speaking with teams that want to do. AI workload training as well as inference and it's something that the expectancy typically when they're doing those things. So this is going to be a pretty significant unlock for us being able to support such workloads as well. So Artur in Adam are actually working on this feature right now. And other than that, I don't think this much more importantly wanna add some good. + +Artur Troian: Industrophic. So as a feature. The implementation class has been done. just in the testing phrase because we have the Glock of things to be released and this moment you're waiting until we make plant releases and then we're gonna manage it. This thing doesn't require any networks whatsoever. It's just gonna be rolling update. Hopefully maybe next week or we're gonna be able to push it to the public. + +00:35:00 + +Anil Murty: Thank you I think that's pretty much all the ones I wanted to go over at least for now. We don't have to dig into the things that are in the bucket next we can talk about the next meeting. I do want to get to some of the discussions as So unless anyone wants to bring up anything specific on the engineering and product side. I'm gonna move on to talking about discussions. + +Anil Murty: It's so the last thing on our agenda is to typically review any GitHub discussions that have been posted since the last steering committee and then prioritize ones that have had a fair amount of activity or interactions as well. As ones that are represented by folks on the call today, so Jumping over to the discussions here. We talked about Akash accelerate already. So I don't think we need to spend a whole lot of time on that one. I don't think there's anybody that objects to this. I've read through the comments. There's literally overwhelming support for all of this so I don't think Need to be the source anymore, but I don't know any last words anybody wants to talk about in terms of accelerate. + +Anil Murty: It sounds good. We'll continue to make progress on this in post updates to the community as we Define this going forward. + +Anil Murty: I Look to most of these issues today morning. There were a bunch that were not really proposals but just questions about things so this one just talking about, somebody who wants to migrate from AWS and is wondering if a lift and shift is better or starting fresh and so my recommendation was first is if you're already running container native and using an orchestrator like eks, then you can probably Port that over relatively easily to Akash, but if not then Press might be better. But I think directly as Robert in rotary. I've said here the best thing to do is to send these folks over to discard for this kind of questions. + +Anil Murty: Support canceling on speaking. I have definitely seen this and personally, I feel like it's a cool thing to advert. I don't think it's particularly necessary from growing demand or growing use usage on the network perspective, but my suggestion was it would potentially be a good task for somebody in the community, but I'm curious if people have thoughts about this. + +Artur Troian: so let me + +Artur Troian: Wait concession of father and staking I don't think we support that. so let me Yeah,… + +Anil Murty: we don't and that's what they ask. yeah that + +Artur Troian: let's so we're gonna have a sick chain. I believe next week. And I'll try to cover that thing. I'm not sure we can do that just yet is the current business Decay that we are on. so There is no even cancel transaction. And I'm not sure it actually makes sense to discuss it just yet. And yeah, I need to double check it but I believe you cannot support it at this moment. + +Anil Murty: yeah, and also unless anyone disagrees. I don't think it's a huge priority. It's not something that necessarily hinders it option of Akash network from a tenant deployment perspective. + +Anil Murty: Okay, mostly question there. It is a proposal from Human HQ for building the solution for deploying llms from hugging face onto I don't know if somebody from the human SQ team is on here to talk about this. I don't Would see anybody that looks like they might be from a human HQ team but I write through this proposal. it's really well written. So I like that part of it, but I think in my mind at least so First off I think, being able to build a solution that allows easy deployment of models that are hosting logging faces awesome. + +Anil Murty: But my main concerns on this were number one, it talks about building a new UI and a new platform. My first concern was why Just build on top of Cloud Moss, which is open source now and then the second thing was while the solution can be built the harder problem always is how do you get people to use that solution when there are a whole bunch of similar Solutions out there, right, connect with f****** face the main challenge that we have felt and so we meeting the core team have discussed potentially building what we were calling on hashemel at some point in one of the big challenges with anything like that before we go and invest a bunch of time and money into it is + +00:40:00 + +Anil Murty: Hugging phase themselves, we've talked with folks there including the founder of marketing phase and asked if they would integrate and let us have a button to deploy on a cash and it's a chicken and egg problem where they want to see a lot of workloads running on our cash before they will consider doing that and we want to get that button in order to get a bunch of workloads running on us. It's chicken in a problem there. So if you can get that going then it's a huge driver for demand from that channel in the absence of that the better strategy here, which is something that we're pursuing with companies like bread. For example, we talked about in the agtc conference coming up plus a couple of other ones that they're speaking. It's right now is to integrate with them and have them use us as their primary infrastructure provider. And so when they already have Traction in the market and a builder UI and a user experience that is extremely easy to run open source models on. + +Anil Murty: It automatically drives demand for us in which is what we wanted to be doing. So that's kind of my two main piece of feedback on this, but they will + +Deval Patel: I think that can be solved with minor changes in just our templates of the llm models what we host right now with awesome markers or that kind of thing. I believe we just need hugging phase API key or something from whoever wants to deploy the models, right and we can add that into templates. + +Anil Murty: Yep, And that is kind of my first comment here as And we actually already have a couple of templates for a few llms. That work. So yeah, if anybody else has any feedback on this it hasn't gotten many responses. I did want to talk about it because this spend a lot of time writing up this proposal. So what is the main intention? Yeah. Maybe want to move on from that. There was a proposal or request not really proposal is not asking for any funds or anything but a suggestion for doing cartesi smart contracts. I personally have no idea what this is, but Greg going. + +Greg Osuri: Yeah, so we don't have use case for smart contracts on a cash and improving expanding their tax service in the code base. Is not advisable with our use case, so I would say I would recommend against incorporating. Anything that's not called to our use case. Arthur + +Artur Troian: Yeah, I'm just hundred percent support that opinion. So they cannot be just single use case for this more contracts. But the second of all most likely the use case can be done without even smarter drives. So we are in the background trying to find what kind of things we could probably increase your but at this moment you just completely opposite of bringing that into the network another point is Smart contract usage as this stage is quite complicated. So it's going to be frankly saying waste of the resource on this point. + +Anil Murty: I'm just gonna drop a couple of quick things here and So that we're aware of what? + +Anil Murty: We're going. + +Cheng Wang: Did have a quick question regarding the smart contract. I suppose some I haven't read this but what you're trying to solve here could be accomplished at the application layer, right? It doesn't have to go into the core code base. So whatever logic you need a program, I feel like could be done further Upstream. + +Anil Murty: yes, so the folks that gregoric actually have spoken with us a few times about doing exactly that so, that potentially be an alternative to this. + +00:45:00 + +Anil Murty: but + +Artur Troian: A little money discussions again about the usage of contracts. For example, the Gory it was Told that they could create deployments on a car using from work and they needed them but that could be just cheered any products. So yeah. + +Greg Osuri: yeah, so the finish I thought sorry. + +Artur Troian: Yeah, we're just trying to summarize here that in probably.% out of time 9 cases out of 10 the use case can be sold quite simply without Smart compacts and pretty much every time he discussion about them. It's just people just want to have them because it's cool without any + +Artur Troian: proof of Need for this particular use case + +Greg Osuri: Yeah, so Ideal World with ice IBC a gorak should be able to make a call on a cash. if we need to make things happen for that enablement. maybe it's worth considering I see a whatnot because there are multiple use cases people have been asking for ICA. but incorporating smart contract module inside Akash is not use case less. I don't think we need to do that much amount of lift and take that much more risk because every time you had code it's more unstable, right so + +Greg Osuri: If cut I don't know or Curtis, is it a separate chain? It is a module if they want to call. stuff on a car great I mean Why not but if we need to incorporate a module and no go that would be my response to this. + +Anil Murty: Yep, makes sense 100% And also the person who wrote this notes that nobody in Carter. He seems to care nobody in our castings to care person is a middleman. + +Greg Osuri: Okay. + +Anil Murty: So go out. + +Greg Osuri: Just your average bag holder. + +Artur Troian: Yeah ideas on the ICA. So as far as very cool was time. We discuss with them. I know it's probably topic to support conversation. You just pull up as we tied this thing. They wanted to have deployment on a car through a glory to using IBC and English in accounts. It was apparently the biggest blocker was they still need to talk to the blockchain and to the provider directly. For example, check the status of the deployment status of the reasons and so forth. So it wasn't issue only to rule the transactions, but how to roll events and this moment is quite unstable. So + +Artur Troian: Agreement back then was like, It actually doesn't make sense. It's easier for us to just use API directly without some fun through IBC or caution and deploy in a car instead of deploying through IBC. + +Anil Murty: Make sense. I'm gonna move on from this given no one seems to want to Champion this at least on the path. So for now I put some comments in the discussion, but feel free anybody else that wants to jump in and post some comments. As Huey has a comment. + +Anil Murty: Okay, you're saying it can happen without Smart contracts as well. So it's not good. Next one's five akt lock we talked about that. + +Anil Murty: cross chain swaps from 60 chains + +Anil Murty: Rango, I think this one people already commented that there's something that can be done Robert. I think you've made a video about how this can be done as well. So he's interest to get into this but go ahead. + +Artur Troian: I need to get deeper into that. You might need to wait until we got pocket forward in I know it's been on discussions a lot and we've been pushing back forwarding or quite a while right now. But I think having that will simplify there's always going to bring native. Usdc from the USD. Please hold down so if you saw the picture was like USBC oxlord usdc because too many hopes for the swap. When we bring back and foreign. is it out quite dramatically? That's what we hold on that. I'm gonna speed this issue to make sure that we are on the same page and we're trying to solve the same issue. + +00:50:00 + +Artur Troian: And I believe accidentally leap wallet dance something like that already. I'm not sure about how to check it. It's really just to have. Quite a good working examples instead of having many barely working. So let's maybe hold on that. + +Anil Murty: So I was good. Yep, if you want to post a comment on the searcher. You can go ahead and do that later, and I don't think it was. Yeah. + +Anil Murty: I'm gonna say I don't think the person that even wrote it is on the corner, so that one he provided incentives away. This takes us back to the last thing we talked about in the last steering committee. So I think that's all the discussions for now. Anybody want to bring up anything else that we haven't talked about on the discussions? + +Anil Murty: Good after. + +Artur Troian: Yeah, just want to bring a little bit of update related to the network upgrades and we're gonna have discussion on the six chain next week. But as a summary we are slightly behind the schedule for now. There are three Network upgrades on the table. Number one is it's going to be executed next to you to fix gas issues with the provider update and then we're gonna have expedited proposals and following up is the least status. We are heavily working on a day preparing to update for the awesome cdk for 27. Because as you know, the 45 has been deprecated over the year ago, and it's not been supported and it has actually quite a few issues in terms of usability. + +Artur Troian: So we are targeting to get it sometime middle this year, but hopefully sooner actually I'm gonna bring a couple of my Milestone Stones provided to the network upgrades itself where everyone could just see the progress on them and estimates on when they're gonna be executed. + +Anil Murty: Thank you Hunter. Okay, so that kind of brings us to the end of the session today opening up to anyone that wants to bring up any questions or general things. We've got about five minutes one of the call. So we'll take a minute. See if anybody want to talk about anything in general. + +Anil Murty: going + +Cheng Wang: Just a quick announcement here for the next Akash hackathon that we will be hosting there will I think Adam has already Adam mossen. He's not on the call, I believe but he's ready I think gone into several of the sigs across this court to Garner ideas for the particular tracks and use cases that we want to encourage people to build on the first hackathon that we hold held last year was Theodore hacks timing wasn't the most ideal thing it was literally like budding up and in putting up against the GPU Marketplace launched in August, And so this time around we learned a lot from that particular hackathon will we what went well and what didn't and so this aeration should be a lot better and highly encourage folks who are technical especially to go and chime in give your thoughts and opinions and those who aren't even to participate and just kind of see what's up ideas are always welcome. + +Anil Murty: It's And I believe we also have a working group if I remember for hackathon. So there's that Avenue as Great. Thank you Cheng any other final thoughts? Or questions concerns from anyone before we and today. + +Anil Murty: Okay, I'll take that as a no and I think with that we can kind of conclude this month's steering committee meeting. Thanks again everyone for coming to these. It's you awesome to see. These probably get the most amount of attendance. So it's really nice to see everyone here and hopefully we're doing a good job in terms of running these as well as keeping everyone Awesome, that'll stop presenting and I guess we can in the call for today. Thanks, everyone. Bye. + +Scott Hewitson: Have a good one everyone. + +Cheng Wang: take care all + +Meeting ended after 00:55:08 👋 From 33a3a154c59e0c77122a5018153975848ab20f8b Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Fri, 22 Mar 2024 11:42:04 -0400 Subject: [PATCH 022/138] steering committee Update README.md add meeting 13 to table Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index 23b0a565..9496edfa 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -26,7 +26,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Wednesday, November 1, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/010-2023-11-01.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/010-2023-11-01.md#transcript) |[Link](https://4yrnmjlm3nco2ccfkbkv67s6cfgvgrge7op5dfwnv6gn46mueqxa.arweave.net/5iLWJWzbRO0IRVBVX35eEU1TRMT7n9GWza-M3nmUJC4) | Thursday, December 07, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md#transcript) |[Link](https://k6mud4r2ua6xarj6c5zqtkxw6fzjrvzjzu6eotsyhsmotles2gaq.arweave.net/V5lB8jqgPXBFPhdzCar28XKY1ynNPEdOWDyY6ayS0YE) | Thursday, January 25, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md#transcript) |[Link](https://uh4qrdp5wsvzihnnh7m7conzwkllrei4xawnfsohgjmp5qpjberq.arweave.net/ofkIjf20q5QdrT_Z8Tm5spa4kRy4LNLJxzJY_sHpCSM) -| Thursday, March 7th, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, March 7th, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md#transcript) |[Link](https://aqjulyegruxs4xdwltfkkxqieagkmqc7dcbewovdw2wk7tj72hka.arweave.net/BBNF4IaNLy5cdlzKpV4IIAymQF8Ygks6o7asr80_0dQ) | Thursday, March 28, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, April 25, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, May 30, 2024 11:00 AM PT (Pacific Time) | | | From 2e05697cc2e5d947f75556ce7495156cffd86f4e Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Sun, 24 Mar 2024 11:02:25 -0400 Subject: [PATCH 023/138] steering committee Update 013-2024-03-07.md remove spelling issue Signed-off-by: Drinkwater --- committee-steering/meetings/013-2024-03-07.md | 1 - 1 file changed, 1 deletion(-) diff --git a/committee-steering/meetings/013-2024-03-07.md b/committee-steering/meetings/013-2024-03-07.md index 23fcd5fb..9fb13889 100644 --- a/committee-steering/meetings/013-2024-03-07.md +++ b/committee-steering/meetings/013-2024-03-07.md @@ -103,7 +103,6 @@ - Add a Zealy card to the community and marketing board. - March 13th, 2024 Mainnet Upgrade, pending vote passing. - Artur will look at [discussion 495](https://github.com/orgs/akash-network/discussions/495). -- Artur will work on # **Transcript** From 204ba079b4cd79c072c32c0ffe04c2d10243a783 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 25 Mar 2024 14:15:53 +0000 Subject: [PATCH 024/138] Create meeting notes for sig-clients #13 (#517) * Create meeting notes for sig-clients #13 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 013-2024-02-22.md add recording and transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-clients/meetings/013-2024-02-22.md | 177 +++++++++++++++++++++++++ 1 file changed, 177 insertions(+) create mode 100644 sig-clients/meetings/013-2024-02-22.md diff --git a/sig-clients/meetings/013-2024-02-22.md b/sig-clients/meetings/013-2024-02-22.md new file mode 100644 index 00000000..c09b6a19 --- /dev/null +++ b/sig-clients/meetings/013-2024-02-22.md @@ -0,0 +1,177 @@ +# Akash Network - Clients Special Interest Group (SIG) - Meeting #13 + +## Agenda +- Quick follow up from sig-clients monthly meeting #12. +- Update on specific Akash clients from representatives present at the meeting. +- Presentation fron Piyush ( Hooman HQ team ) + +## Meeting Details + +- Date: Wednesday, February 22, 2024 +- Time: 08:30 AM PT (Pacific Time) +- [Recording]((https://x5g5djwxzxixepgqsmxl6rupiipshcicdmq5bf2tjac35fjv5f6q.arweave.net/v03RptfN0XI80JMuv0aPQh8jiQIbIdCXU0gFvpU16X0)) +- [Transcript](#transcript) + +## Participants +- Anil Murty +- B S +- Cheng Wang +- Julius Haus +- Maxime Beauchamp +- Piyush Choudhary +- Rodrigo Rochin +- Tyler Wright + +## Meetings notes +#### Tyler Wright: +- Tyler Wright opens the meeting, emphasizing its purpose: to discuss client-related topics concerning tools built on Akash. +- The focus is on improving user experience, avoiding redundancy, and fostering collaboration. +- Tyler mentions the influx of teams integrating Akash into their ecosystems and encourages them to join the meeting. +- The meeting format may adjust to accommodate new teams and their needs. +- Updates from Cloudmos Team are integral, as they address bugs and community issues swiftly. +- Community members can ask questions or report issues via Discord Channel or Cloudmos repo. +- Tyler expresses gratitude for the Cloudmos Team's responsiveness and support. +- Max from the Cloudmos Team is expected to provide updates later in the meeting. +### Recap of last SIG Clients Monthly Meeting +#### Tyler Wright: +- Discussion on Luna's team updates regarding client libraries and potential collaboration offline to push libraries forward. +- Sphereon team's discussion on scaling their tool built on Akash infrastructure, expressing concern over the 5 AKT bid deployment. +- Sphereon team desires a lower AKT amount for scalability due to increasing AKT price. +- Discussion initiated, feedback provided, awaiting further parameter changes to lower AKT amount. +- General discussion on APIs. +### Updates from Maxime Beauchamp (Cloudmos Team) +- Released a new stats app, extracted from Cloudmos into its own domain [stats.akash.network](https://stats.akash.network/) +- [Cloudmos API](https://api.cloudmos.io/v1/swagger) updated with its own documentation on Swagger. +- Working with the core team to implement the server provider service Discovery endpoint, rolling out slowly to the mainnet. +- Continuing work on rebranding Cloudmos into Akash console 2.0, progress tracked on the project board. +#### Console Migration Progress: +- Tyler confirms the console migration is ongoing and not yet finished. +- The migration is a significant effort, tracked on the [project board](https://github.com/orgs/akash-network/projects/5/views/1) , and prioritized but may face delays due to other priorities. +### Introduction of Piyush's Project +#### Tyler Wright: +- Piyush has been working on an LLM solution and has successfully revamped the website and managed the Akash Network website. +- The team has participated in working group sessions and discussions. +- Next step after initiating a discussion was to present a demo to SIG Clients. +- Piyush will provide details about the project they're working on and give a one to two-minute demo. +- Tyler hands over the floor to Piyush to discuss the project and provide a demo. +### Piyush Choudhary's Presentation +- Piyush discusses their work on revamping the official Akash Network website +- [Proposes a solution](https://github.com/orgs/akash-network/discussions/487) for streamlining the deployment of LLM models on Akash. +- They highlight the complexity involved in deploying LLMs on Akash compared to other platforms like Amazon SageMaker. +- Piyush presents their solution, including a universal SDL to load LLMs from Hugging Face and deploy them on Akash. +- They divide the solution into a universal backend UI for deploying multiple elements into a single deployment and a dedicated LLM deployment option for Akash. +- Collaboration with Alani and ongoing development efforts are mentioned, along with obtaining PRC. +- Tyler encourages attendees to watch the attached video and provide feedback/comments on the discussion board. + +### Other matters Discussed +- Piyush proposes starting a dedicated support group to assist users with deploying applications on Akash. +- Piyush highlight the need for dedicated support due to numerous user inquiries and discussions on various platforms, including Discord. +- Piyush suggests providing guidance through written guides, local video explanations, and personal assistance from themselves and their team. +#### Tyler's Response: +- Tyler acknowledges the value of Piyush's proposal and notes the existing support provided by Akash insiders and vanguards. +- While recognizing the support structures in place, Tyler appreciates Piyush's contributions and willingness to assist users. +- Tyler mentions the responsiveness and assistance provided by insiders and vanguards in addressing user inquiries and needs. +- Tyler encourages brainstorming on how to enhance support, such as documenting Docker image generation and deployment processes. +- Suggestions are made to create documentation, videos, or other resources to address common questions and issues. + +## Action Items +- Tyler to continue pushing for updates from other teams and encourage them to drop updates in SIG Clients. +- Community members to push opportunities or projects related to Akash integration to SIG Clients for discussion. +- Tyler to adjust schedule due to community members attending East Denver, with the steering committee meeting moved to the following Thursday. +- Attendees encouraged to reach out on Discord for any questions related to SIG Clients or other projects in the ecosystem. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to sync clients monthly meeting number 13 during the sick monthly meetings. The group goes over anything related to clients that are building tools on top of Aka Usually we get updates from cloud most team. I know there's previously been updates from Luna who's been working on clients libraries a number of other teams that are building Integrations either on top of a cost or folks to deploy or other tools that again make it easier for people to use Akash. + +Tyler Wright: So during these conversations we talk about themes around again improving user experience just general tooling so that there's not redundancy of efforts as people are continuing to build on top of Akash and just a place for collaboration. I know there's a number of teams that have reached out to myself and other members of the core team Community about Integrations that they're building to again bring cash into their ecosystem. So those are really exciting things. We're trying to push as many of those teams to join this meeting just to participate and show off some of their work. + +Tyler Wright: Again, as we continue to move forward at the time needs to move will do that so that we can accommodate a number of new teams that are learning about Akash testing out a cost and figuring out ways to Leverage The plethora resources that are on a cost right now and they're coming down the pipe. + +Tyler Wright: Quickly before we go into just updates from various teams. I want to go over some items from the last say clients meeting as always we talked about some of the updates from the cloud most team. I know they do a great job of addressing any bugs or any issues that anybody from the community has as they use cloud most which is right now the preferred deployment tool. + +Tyler Wright: if there's anybody that has any questions or comments, there's a Discord Channel ecosystem Cloud most where you can ask and get pretty quick feedback. You can also put any specific issues that you see with the cloud nose app inside the cloud most repo in their cost Network organization. So any issues there the max is and the rest of the community do a great job of looking at those issues commenting on this issues and then stopping them pretty quickly so much appreciate that. We'll get some updates from Max later on. + +Tyler Wright: Beyond that there was a discussion around some updates that the Luna's team has been doing as a potential s libraries. So some next steps. I'll be taking offline in terms of pushing clients libraries forward. I know that Luna has been working on a number of other efforts of related to quasarch and some other projects. So again again update there and then a member of the sphere on team joined the call and was talking about scaling of their tool that's built on using a cost infrastructure. There was a discussion around the five akt bid deployment that goes in and it's held the sphere on team talked about wanting that akt amount to be lowered so that as they continue to scale. + +Tyler Wright: It's easier for them to do so because five akt because the price is growing it's going up, it's becoming more expensive. The action item from that was again. They put a discussion in there folks gave their feedback the next exercise was if they had any additional thoughts because again Akash is open if they have any parameter changes that they would like to put in to lower that akt amount. anybody else is more than welcome to put those Unchained up for vote and again, we would love to see that participation. + +Tyler Wright: But it has not happened quite yet. So we'll continue to track back to action item as a move forward. + +Tyler Wright: Other than that there was some general discussions around apis. But again, that's a wrap up of what happened at Sid clients monthly meeting number 12. Before we move on to a presentation from peers. I do want to see if there's any updates. Usually we check in with Max B or other representatives from other teams that might be here today to talk about any updates on cloud most or any other tools that are being built that are in the Sig clients category. So does anybody have anything that they want to specifically give an update on before I handed over to Max the given update on some of the progress has been made over the last month with clients. + +00:05:00 + +Tyler Wright: Max, I'll hand it over to you. Is there anything on update side that you want to get to the community and relates in regards to what's been going on the cloud most over the last month? + +Maxime Beauchamp: Thanks so yeah in the last month, we released a bunch of things including the new stats app that is now extracted from the Clubhouse app into its own app under the domain name stats that I cache that didn't work. You should be redirected to this app. If you go from the Akash Network website or simply from the cloud multiplier. It's been also updated to remove these pages and In the sidebar, you can just click on the link and bring you to the app. Also, we released a new version Of the cloud most API which has its own documentation under a Swagger. app API Can make it there in a chat? + +Maxime Beauchamp: which is now live in the functional functioning pretty well. We're also working with the + +Maxime Beauchamp: with the core team that we are part of as well and to implement the server the provider service Discovery endpoint, which is the now slowly rolling out to the mainnet which will provide more information about the hardware that the provider has and we're also continuous continuing our work to Rebrand Cloud nose into the Akash console 2.0 which is the going and you can follow the progress on the project board in so that's all I have in the big lines of updates for the past month. + +Tyler Wright: Thank you Max. Does anyone have any questions for Max about anything Cloud most related they want to ask at this time? + +Tyler Wright: All right as mentioned I do reach out to all of the teams that are The Sid clients repo page on a monthly basis to check in with them. See if they can come to the meeting. Some folks they can and then may not always be able to make it I try to get them to also give updates and sick clients so that they're giving the community updates on their projects. Think if they can't make this meeting live and I'll continue to push that as we can do as we move forward. + +Tyler Wright: You Julius asking the chat is the console migration finish. No, this is an item that's currently in progress. I know that on the project board as Max is dating in the chat. There is a large item for the refactor. This is a big effort and it's ongoing and sometimes the Maxes get pulled in a number of other directions as it pertains to updating things like endpoints API. Are so it's important effort and it's certainly prioritizing in progress right now, but you can contract that in a project board. + +00:10:00 + +Tyler Wright: If all right, if there's no other questions related to Cloud most and nobody has any questions or any updates on any other specific clients, then I do want to hand it over to huge who again has been working for some time on an l and llm solution. Let them go into more detail on exactly what he's been building. But again piyush and his team worked on the website revamp and successfully completed that work and have been managing the Akash Network website as well. the team again has also put up a discussion as participated in a number of working group sessions. And so the next item related to the specific project that here in the human. + +Tyler Wright: HQ team are working on after putting up a discussion was to join a safe dude, give a demo and talk to folks live about what they're working on. So I thought that say clients would be the best place for them to do that. I'm going to drop the discussion in the chat just in case people haven't already seen it, but then I'll hand over the floor to be used to talk at a high level about what he's building and then maybe give a one to two minute demo for people on this call and then people watching the video and then if anybody has any questions, we'll hold those questions until after that short demo and then we can have a continued discussion from there. So without further Ado I'll hand over to piyush appears if you want to share your screen or anything. Feel free. + +Piyush Choudhary: So good everyone. So I'm beautiful. So I've been working on the official occasion Network website River and we successful area from the official occasion Network website, which is already and instantly we put forward a proposal that is live discussion board 87. So the audio was to streamline the process of deploying elements onto the cost. so that is a huge requirements or use demand from the community sites but the complexity is too much when doing something to Akash, we have to first figure out how the islands are looking. What is their code Base by going on to the hurricane face and then we have to be a talk of image and all so this is a huge work involves all deploying elements under cast and we can see how many face is kind of a GitHub for elements and if we can have a streamlined process of + +Piyush Choudhary: Alums onto cast the uses of the network can increase in this case for example, if you say this is the Alum example that you can see on hugging Pace. I want to deploy it on to Amazon airlift. I have a option to directly deploy it onto Amazon Spacemaker SDK, but if I want to deploy this model onto Akash, I will have to go to the complexity of + +Piyush Choudhary: Setting up a local environment creating a Docker Park creating a documentation SGL file. which might be to complex and to learn the process to the purchase single elements and there are thousands of them that are available on being page. So to streamline this process we created this solution and I have attached this video which shows a quick demo that we have created to showcase the proof of concept and validate the So the idea is to create a universal STL which will load all the elements into a single place from hugging face and these auction to launch the elements and it will launch albums in a machine that I still has been deployed and then there is a base other which can be used just like an API to talk to them anywhere similar to the church if it's kind of the universally I think any number of others interested in this case we have divided this + +Piyush Choudhary: Into two part one. Yes. We are creating a universal backend. So this is kind of a universal UI backend UI which can deploy multiple elements into a single deployment. So you just have to launch rsgl file and it will load and all multiple elements from the base and it will provide you an option as you can see in the videos to launch the elements and then there is a second solution, which is more towards how the Amazon image is being struct. + +Piyush Choudhary: Example, let's say and we have option to deploy or it on Amazon salesmaker. So in this case dedicated Alum deployment, so we are going to create a similar kind of functionality for the cost where we will have a deploy onto a cost the cloud modes option and it will deploy. Of course, you will be ours because you cannot add options onto the plugin face UI so we will have our UI where all these elements will be loaded and you have the option deployed on broadcast and also Alani is our advisor in this case and we are developing the solutions and we are working on the solution for past few months. So also we have got the PRC in this case. So any questions for more than welcome. + +00:15:00 + +Tyler Wright: Thank you for your site. I know some folks may not have had some time to watch the video yet. But again if folks on this call and then folks watching this and take a look at this discussion, give some feedback write some comments. Ask some specific questions. If you need some time to digest today, that would be great. So again that we could take the next steps on figuring out how we want to move this idea presentation forward or if the network is potentially not ready for it or just again some comments on this discussion would be a great. I appreciate PSU staying up a little bit late too at least talk about the discussion a little bit with this group. + +Piyush Choudhary: Thank you. + +Tyler Wright: does anyone have any initial questions again? If not, then feel free to drop those in the discussion and leave questions there so that more Community time and + +Tyler Wright: All right at this part of the agenda. I want to open it up to anybody that might have anything clients related that they want to discuss. Is there anybody that wants to discuss anything clients related that's again the floor is yours. Feel free to raise your hand and ask any questions comments Etc. + +Piyush Choudhary: So I have one thing like I'm considering to start deployment as a dedicated group says it's something that I can talk about here. + +Tyler Wright: Yeah, yeah, feel free to talk. + +Piyush Choudhary: Yeah. Yeah, sure So there is in blocks of the users who are asking how to deploy Into Cash. There are multiplicative discussions that are being started and all Discord also they were a lot of questions but please no dedicated support available to help them write their applications on the gosh and this is something that is required. I guess at this point and also I've been opposed finite my God the website on the car with proper guy and local video explanations and all so I think I was just being installing starting with employment Health dedicated book which can be a primary point of contact and can help anyone deploy any type of applications on drugs with dedicated support and I can relate this through me and myself and my team so yeah. + +Tyler Wright: Thank I know that my initial feedback on this idea. I think I shared there is the Akash insiders and their cash vanguards that do a lot of that kind of work. + +Tyler Wright: this is something that as I think about it. We'll talk to Adam a little bit more because I know that you do a great job here just individual helping folks. + +Tyler Wright: I know that folks like Piper dents and others are helping people with complex and simple sdls and helping them. I know Rodrigo's doing the same thing Max. I'm sure and others. So again, there is currently infrastructure through Discord and we push people from other places into Discord to have those kind of real-time conversations, but I don't want to diminish the input in and the value that you as an individual certainly can bring to Discord, but I do want to make it clear that there are institution there are places that do that right now and again support structures that have been in place for some time that I know users from the community of expressed to me privately in publicly that they get responses from insiders and vanguards in a very reasonable time and anything that needs to get taken to + +00:20:00 + +Tyler Wright: anything specific that they need they get so I do want to shout out the support that's currently happening at the beginning to deployment and setting up providers and discordant elsewhere. But does anyone else have any? specific thoughts about + +Tyler Wright: What Peter's just brought forth brainstorm? + +Tyler Wright: All Yeah This is something that I've taken note of as part of the open discussion for this sick clients meeting and we can continue to brainstorm something like this because again, I'm much appreciate the help that you provided to the netted out team and all the help that you provide to anybody that's trying to interact with the website and elsewhere. So want to make sure that we continue to utilize those skills wherever we can. + +Piyush Choudhary: It say I agree with you, I think. There's already some things of in place. I think the only thing that I want to say that what things can get it by the vanguards is like they can start pushing on to describing how GitHub bills through Docker images can be used to deploy on to the cost like how they can automate the docker image generations to get a bills and then how they can have a deployed on a constable problems. So yeah, there is something that and godsend about + +Tyler Wright: Love that and we'll talk a little bit more about some of those ideas that you have and maybe they could be. Docs videos Etc. There's a number of ways to Make sure that users have that kind of information especially if you get those questions, that's a lot. I know that again kind of sidebar but shimpa put out a great video on the provider side. I know some people ask or asked about Forwarding all the time. And so you made a specific video about that that will touch on next weekend providers. + +Tyler Wright: Is there any other open discussions that haven't been discussed at anybody wants to talk about right now? + +Tyler Wright: again much appreciates the updates from the clubhouse team and participation here today. Thank you Max. I will continue to try to get updates from other teams and have them drop it in Sig clients and pushes hard as I can for them to do that and then again, I'll add it to the notes once it's dropped in Discord. and then I as more teams are finding out about the costs understanding the power of Akash and looking to integrate, again, the core team and members of the community. If you see any of those kinds of opportunities or projects out there, please push them to this stage so we can see how folks are building on top of Akash. And again leveraging the resources. + +Tyler Wright: If there's nothing else then again, I'll let you all go much appreciate everyone's time today. Yeah, I hope everyone has a great rest of their day. There's a couple of cigs and working groups next week, but the schedule has been adjusted a little bit because of I know a number of folks from the community and the core team will be at East Denver. So the steering committee meeting that was originally planned for next Thursday has been moved to the following Thursday. So two weeks from today. And again, there's a couple of other changes but much appreciated everyone's time and efforts today. If anybody has any questions ready to see clients, feel free to drop those and Discord or feel free to reach out to the cloud most team or any of the projects in the ecosystem area. Hope everyone has a great rest of their day. Thanks again everybody. Talk soon. Bye. + +Meeting ended after 00:26:13 � From 6aa5274cf67df9c692a79980a173e0123e695695 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Mon, 25 Mar 2024 10:20:31 -0400 Subject: [PATCH 025/138] sig-clients Update README.md add meeting details for meeting 13 to table. Signed-off-by: Drinkwater --- sig-clients/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sig-clients/README.md b/sig-clients/README.md index f69e7ba3..dd97bf11 100644 --- a/sig-clients/README.md +++ b/sig-clients/README.md @@ -45,8 +45,8 @@ The goal of this SIG is to foster a community around each of these clients that | #10 | Wednesday, October 18, 2023 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/010-2023-10-18.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/010-2023-10-18.md#transcript) |[Link](https://yofgxnfxaqk4jruuwko7pyrfckw27dtg5thp6c6bv2sfvfq66jla.arweave.net/w4prtLcEFcTGlLKd9-IlEq2vjmbszv8Lwa6kWpYe8lY) | #11 | Monday, December 18th, 2023 08:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/011-2023-12-18.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/011-2023-12-18.md#transcript) |[Link](https://msr577epylf5qgo6aexm2xbblsreurfi2pgy5ed5ssdw6ztgkxwq.arweave.net/ZKPf_I_Cy9gZ3gEuzVwhXKJKRKjTzY6QfZSHb2ZmVe0) | #12 | Wednesday, January 17, 2024 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/012-2024-01-17.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/012-2024-01-17.md#transcript) |[Link](https://75iuscsrjioekyahvk6vad3taa5ikpweibvxs2rf4amjvzvj6gfa.arweave.net/_1FJClFKHEVgB6q9UA9zADqFPsRAa3lqJeAYmuap8Yo) -| #13 | Thursday, February 22nd, 2024 09:30 AM PT (Pacific Time) | | | -| #14| March, 2024 10:30 AM PT (Pacific Time) | | | +| #13 | Thursday, February 22nd, 2024 09:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/013-2024-02-22.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/013-2024-02-22.md#transcript) |[Link](https://x5g5djwxzxixepgqsmxl6rupiipshcicdmq5bf2tjac35fjv5f6q.arweave.net/v03RptfN0XI80JMuv0aPQh8jiQIbIdCXU0gFvpU16X0) +| #14| March 27th, 2024 09:00 AM PT (Pacific Time) | | | | #15| April, 2024 10:30 AM PT (Pacific Time) | | | | #16| May, 2024 10:30 AM PT (Pacific Time) | | | | #17| June, 2024 10:30 AM PT (Pacific Time) | | | From fbc442855916be68b67f77d9f4c87d92aabcbcc2 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Mon, 25 Mar 2024 10:21:08 -0400 Subject: [PATCH 026/138] sig-clients Update 013-2024-02-22.md fix recording link for meeting 13 Signed-off-by: Drinkwater --- sig-clients/meetings/013-2024-02-22.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-clients/meetings/013-2024-02-22.md b/sig-clients/meetings/013-2024-02-22.md index c09b6a19..c0b034b6 100644 --- a/sig-clients/meetings/013-2024-02-22.md +++ b/sig-clients/meetings/013-2024-02-22.md @@ -9,7 +9,7 @@ - Date: Wednesday, February 22, 2024 - Time: 08:30 AM PT (Pacific Time) -- [Recording]((https://x5g5djwxzxixepgqsmxl6rupiipshcicdmq5bf2tjac35fjv5f6q.arweave.net/v03RptfN0XI80JMuv0aPQh8jiQIbIdCXU0gFvpU16X0)) +- [Recording](https://x5g5djwxzxixepgqsmxl6rupiipshcicdmq5bf2tjac35fjv5f6q.arweave.net/v03RptfN0XI80JMuv0aPQh8jiQIbIdCXU0gFvpU16X0) - [Transcript](#transcript) ## Participants From d65e9a5bb339e5f5b6e0e921b11402f65ed353a4 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Wed, 27 Mar 2024 13:40:06 +0000 Subject: [PATCH 027/138] Create meeting notes for sig providers #14 (#521) * Create meeting notes for sig providers #14 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 014-2024-02-28.md add transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-providers/meetings/014-2024-02-28.md | 361 +++++++++++++++++++++++ 1 file changed, 361 insertions(+) create mode 100644 sig-providers/meetings/014-2024-02-28.md diff --git a/sig-providers/meetings/014-2024-02-28.md b/sig-providers/meetings/014-2024-02-28.md new file mode 100644 index 00000000..9b35e9ea --- /dev/null +++ b/sig-providers/meetings/014-2024-02-28.md @@ -0,0 +1,361 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #14 + +## Agenda +- Update from Praetor on all of the work that they have been doing. +- Open Discussion on all things related to Akash Providers. +- Update from Scott on provider feature discovery +- Discussion on provider feature discovery testing group +- Provider incentives phase one update + +## Meeting Details +- Date: Wednesday, February 28, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording]() +- [Transcript](#transcript) + +## Participants +- Alani Kuye +- Andrey Arapov +- Anil Murty +- B S +- Damir Simpovic +- Deval Patel +- Jigar Patel +- Max +- Rodrigo Rochin +- Scott Carruthers +- Tyler Wright +- Zeke E +## Meeting notes +#### Tyler Wright: +- Tyler Wright welcomes participants to the monthly provider meeting and outlines the agenda. +- Updates on recent developments from the Praetor team and provider feature discovery progress are expected. +- Tyler announces the upcoming provider beta testing group and calls for community participation. +- Phase one of provider incentives has commenced, with negotiations ongoing for data centers with H100, A100, and RTX A6000. +- Phases two and three of provider incentives are in progress, with more information to be shared in the coming weeks. +- Transparency measures, including a document detailing finalized arrangements, will be shared with the community as arrangements progress. +- Participants are invited to ask questions or share comments on the provider incentives before moving on to other agenda items. +### Updates from Praetor team(Jigar) +#### Jigar Patel: +- Jigar Patel discusses ongoing efforts to support providers and prepare for GPU device upgrades on the Akash network. +- Plans for implementing the Feature Discovery model and conducting audits to ensure provider compliance and performance are outlined. +- Participants are encouraged to report any specific issues or challenges related to provider services for timely resolution. +- Resources available in the community repository, including templates for audits, are highlighted for community members' reference. +#### Tyler Wright's Response: +- Acknowledges Jigar's update and emphasizes the importance of provider audits via the community repo template. +- Mentions that some providers may have been set up via praetor and encourages Jigar to follow up with them for further clarification. +- Invites participants to ask questions or share concerns with the praetor team through the ecosystem praetor channel, acknowledging potential delays in responses due to team members' participation in EthDenver. +### Update from Scott on provider feature discovery +#### Scott Carruthers +- Scott reports that feature discovery has been tested by insiders and community providers over the last week. +- Minor issues were noticed, such as the inventory operator not picking up changes when taken offline, which has been rectified. +- Scott will be testing the latest release candidate and expects to roll out the update to the wider network by early afternoon. +- The update has already been implemented on some of the largest providers, including Europlots and ry. +- Documentation updates have been significant due to feature discovery, including removing manual labeling of GPU nodes or persistent storage nodes. +- Scott requests assistance with documentation updates. +- Tyler acknowledges the update from Scott and mentions further announcements for a wider upgrade from all providers with GPUs on the Akash network. + +### Updates on Provider-audits Working Group +#### Tyler Wright: +- The working group has commenced its activities since the last providers meeting, with Piberdev and the team providing a short document outlining their plan for the next three to six months. +- Meetings will be held on a monthly basis for the next three months as the team focuses on building the auditing tool. +- Interested individuals are encouraged to join the working group sessions to contribute and ask questions. +- Starting in April, meetings will increase in frequency to ensure progress aligns with the six-month delivery window. +- Tyler Wright offers to add interested participants to the calendar invites for the working group sessions upon request. +- Participants are encouraged to reach out if they have any questions or wish to be included in the calendar invites. + +### Provider Attribute Changes and Transaction Fees +- Jigar Patel raises a concern regarding charges incurred without making significant changes to provider settings. +- Rodrigo shares his experience of being charged 3 AKT after a provider restart without making changes. +- Damir explains that charges occur only when changes are made, and the amount charged depends on the complexity of the transaction. +- Deval highlights that smaller providers may be disproportionately affected by transaction fees, even for minor changes. +- Scott addresses Rodrigo's issue, stating that it was a result of a feature discovery version but has been rectified. +- Scott explains the rationale behind the charges for provider attribute changes and offers to revisit the issue if there's significant community concern. +- Tyler Wright suggests documenting the discussion in the appropriate channel for further community input and continues the discussion there. +- Tyler acknowledges Scott's contribution and suggests continuing the discussion in the designated channel for broader participation. + +### Update from Anil Murty on Provider Incentives +- Rodrigo Rochin raises a question regarding contacting potential providers with relevant GPU types. +- Anil provides clarification on the process for engaging with potential providers and negotiating long-term commitments. +- An update is given on the procurement status of GPUs, with two sources identified for all three GPU types targeted for the committed pool. +- Anil expresses gratitude to Shimpa and Andrey for their assistance in managing providers and facilitating GPU procurement. +- An overview is provided of the customer demand driving the procurement of additional GPUs, including the expansion plans for accommodating increased usage. +- Anil announces the onboarding of a well-known customer for foundational model training using an RTX H100 cluster. +- Discussion ensues on the timeline for onboarding new providers and meeting customer demand, with expectations set for early next week. + +### Additional Updates from Anil Murty +#### Anil Murty: +- Anil Murty provides insights into the planned ramp-up with Solve Care, aiming to deploy up to 10,000 nodes on the network by the end of the year. +- Focus on initial rollout primarily in Southeast Asia, leveraging providers with locations in key cities like Singapore, Osaka, Tokyo, Melbourne, and Sydney. +- Andrey is actively involved in setting up providers in each Southeast Asian city, aiming for representation from multiple data center companies. +- Anil highlights the challenge of visualizing multiple providers in a single location on the map, acknowledging the potential impact on perceived provider presence. +- Participants discuss potential solutions to address the visualization challenge and provide feedback on deployment strategies. + +### Other matters discussed +- Damir Simpovic inquires about the support for Feature Discovery in the current Praetor version and its roadmap. +- Jigar Patel responds that currently, Feature Discovery is not supported but is on the roadmap, and updates will be communicated to the community. +- Deval Patel confirms their commitment to supporting Feature Discovery and suggests discussing further offline. +- Damir expresses willingness to address topics requested by the community for educational videos. +- Jigar acknowledges Damir's contribution to educational resources and expresses gratitude. +- Tyler commends Damir for his videos on port forwarding and expresses appreciation for his consistent contributions. +- Deval mentions plans to provide more educational resources and invites suggestions for topics based on community inquiries. +- Damir expresses readiness to consider topics for future videos based on community requests. +- Tyler thanks Damir for his contributions and expresses enthusiasm for future educational opportunities. +- Meeting concludes with expressions of gratitude from Tyler Wright and Deval Patel towards Anil Murty for his updates and insights. + +## Action Items +- Tyler Wright to provide further details on the upcoming provider beta testing group and communicate the call for participation through the appropriate channels. +- Overclock Labs Team finalize arrangements for phase one of provider incentives and prepare a document to share with the community for transparency. +- Tyler to coordinate and schedule monthly provider audits working group meetings for the next three months. +- Tyler Wright to document the discussions regarding provider attribute changes and transaction fees in the appropriate discussion channel for further community input and discussion. +- Scott Carruthers to provide additional clarification and documentation regarding the charges associated with provider attribute changes. +- Praetor team and Damir to collaborate on educational resources and suggest topics for future videos. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the first ly meeting of 2024 during the special interest group monthly meetings. The group here goes over anything related to their costs provider. Usually we have a great deal of participation for a number of different kinds of providers on the Akash Network, whether data centers individual providers some some have accommodations and gpus. So again, there's a great representation types of providers during these monthly meetings. + +Tyler Wright: In addition the prior team who is built a provider build tool on that makes it easy to build the provider. If you don't have a great deal of experience using the documentation and CLI. They also received some community pool funds in 2023 and have given updates on all the work that they've been doing as it relates to helping providers be able to build for the GPU testnet and GPU main Nets their work around content moderation and a number of other items that they've been working on in I know as we get ready for as we start 2024 we'll set out some time today for Digger and Deval from the prey to our team to give a high level + +Tyler Wright: Presentation I know they did at the end of I think November's monthly meeting. But just to give a high level of the kinds of things that they're thinking about as we start off 2024 q1. In addition Benjamin who is also I believe on this call recently received community pool funding for an open source auditor and some other open source contributions to indexer and some other items. I know that again. We're going to set up a working group that I wanted to announce here and get some Community feedback as Benjamin in his team start to work on development of the open source auditing tools. + +Tyler Wright: There's going to be a specific working group. So the community can continue to track and work very closely with Benjamin. Hen and his team. does anybody have any objections to having a specific working group for the open source auditing work that Benjamin is team have + +Tyler Wright: Or we're going to be working I'm going to set that up. And then anybody from the community that wants to participate in those working group sessions with more than welcome, and I'll add them as an to the events calendar and to the other calendars that we have for Community groups special description working groups. + +Tyler Wright: Real quick before we move on and Benjamin. I know that you are just received community pool funds over the holidays. Do you want to give a high level as we get ready to tell the working group on where you are in some quick next steps. It could be a minute or less and then we can really dive in at that dedicated working group session next week or whenever we have that. + +Benjamin B: Sure, Thanks for the word. So now that we have the working group Channel we can start to share some stuff publicly. We have a plan on what to do in for everything until March but we have the timeline between the half of this month and the last of this month to start work and my brother has been having a lot of the issues. We Face environment and has been working a lot of overtime. So we have not had the opportunity to do a whole lot yet. I have been starting to prepare a lot of smaller details on what we need to include in each system and we have a plan on how we should develop each system. + +Benjamin B: between our DMs but as soon as this working group generous don't I will share some more information there. + +Tyler Wright: Thank you min. So I have an action item that I'll create a working group channel for the open source auditing work as well as start to set up some time on the calendar for folks to live over next week or two. + +00:05:00 + +Tyler Wright: Cool real quick. I know that there are a number of discussions that are happening right now in akash's GitHub. + +Tyler Wright: So I really appreciate those that are bringing up discussions and those are participating in the discussions. If you see anything that you want to participate in again, this is an important part of the open source framework to get a community feedback. I've dropped it in there but specifically as it relates to providers and I know that Benjamin again recently received community pool funding we don't want to take a significant time, but I do want to shout out Alani who's on the call here today and is also put a proposal for a cost network provider review and incentives proposal. It's proposal number four 53, and I wanted to again I hope that we can have folks that are on this call or in the community just give feedback and get help discussions. But with Alani here live alani's if you so desire, I just want to give you + +Tyler Wright: maybe a minute or so to talk at a high level about the review proposal and maybe some of your thoughts and initial feedback that you've been getting on the discussions if you don't mind. + +Alani Kuye: You're sure and tie things were organizing these guys always get to see you all and it's very inspiring to see all the work that everyone is doing. The more importantly it's also good to see that we're still solving for these difficult problems as many of I kind of do my thing behind the scenes but I think given where we are right now, one of the things we encountered, in the past. when I run the program we solved a lot for the providers went from what eleven to almost 300 in a matter of months, thanks to a lot of your efforts in just a shout out on the pre-to-team Maxine, everyone on this call, played a role in that so I think when we give it to the other side on the demand side, I'm coming from a strategic perspective in that. + +Alani Kuye: we've solved a lot for provider side. It's easy to become a provider today in that process continues to evolve positively and it's reflected in the walk you guys are doing I think taking the demand side which is where we need to really focus and dislodging it and Tackle them differently because two sided marketplaces have two very different unique needs and of course everything happens on chain. So from a provider perspective, how do we make it easy for folks who continue to deploy when we incentivize them so I know Chang had put something up for God and provider incentives with I + +Alani Kuye: About a nine million dollar proposal or something like that. But how could we code terminally tapping to that to incentivize deployers to stay longer and that requires a very strategic approach, and that's why I'm pushing very hard to dislodge both and Tackle them are separate exercises. that way we understand all the metrics and data literacy around incentivizing deployers, but also symbiotically tapping into The provider incentives finally, which I think is even more important making the cognitive load. So low. + +Alani Kuye: That even the folks in web 2 who may not know where to start can participate because your ecosystem is not just devs and we've been solving so much for developers that we live in human beings, behind the scenes and we're not just building for us and our friends right? We're building for a much broader arm strategic audience. So everyone from students conferences Architects Executives, artists bloggers, media folks every Persona is reflected in who deploys and how do we make it easy the review process, you can't take a gunship little fist fight right the same way. We know that low cognitive load. It calls rapid adoption in high cognitive load is the other way around + +Alani Kuye: So as it is today as admitted easy for providers will continue to solve for that based on incumbency. We need to Pivot to the other side, but approach it very very differently because deployers haven't even lower cognitive look to get in and how do we do that? Make the review processes just like Airbnb or Amazon. We know there's a referral program somewhere within the ecosystem. All those things are related, but we have to dislodge both, we can lump everything into One big exercise, and I think what B is doing is fantastic, especially the audit information. Think about those who want to do due diligence and providers, especially with complex workloads, There's two audiences. There's a systems admin and there's your executive as an executive. I don't have the time. + +00:10:00 + +Alani Kuye: to go into those details so your one review was there any level two is where you go deeper into it. So we have to solve for those audiences because again time is a premium and the easier we make it the more we tap into that audience and more people have longer deployments instead of the drive by that would tend to see and as a market involves we need to be cognizant of that because you can't scale what you can't simplify and we have to Pivot and start to solve. the other side of that Marketplace which are deployers and how can we keep people deploying for longer? While making sure it Remains the medical policy and everything happens on shame. So you have to sign every transaction every way you ever wish where you put it off there. So that's my perspective. I mean always open to conversation. I've gotten everything from it's too expensive. good dance costs. I mean this isn't one person building, we have to look at this thing from a broader perspective. There's different personas that are involved in this exercise. It's not a money issue because again, + +Alani Kuye: And we're talking to wife gay, and it's gonna involve everyone most of which are on the score anyway, so it's not new territory. It's just a way to make sure that we're solving for the other side of the transaction. We're too comfortable with providers. So I want to be the bad guy to say let's start paying attention to deployers and do uncomfortable things because in my experience the things you're not comfortable doing other things that actually going to work. So let's move a little bit away from our comfort zone and do something different. + +Alani Kuye: Benjamin + +Benjamin B: Yeah, I have one thing. I tried to comment on the discussions page, but I must have closed my car. Anyways, I just wanted to speak about the hourly rate. I don't think that regardless of how big of our project this could be. I don't think it's necessarily about projecting up anyway. But I want to say that. + +Benjamin B: the most proposals and other ad hoc opportunities that have been erased within the community of either being 50 dollars per hour for the proposals and what I've seen I've also seen some hoc opportunities with up to 100 dollars per hour. So I don't think it's super weird that you're getting these comments that they already read this quite large. + +Tyler Wright: Real quick, just for the sake of time and I know there's a number of things on the agenda. I just would ask that we can keep any conversations related to anything that's non provided related in the discussions. We'll have some time to talk about that during the steering committee tomorrow, but I just wanted to specifically see if anybody had any feedback because I know that there was some conversation about who should be able to review, what that criteria is and so I just wanted to as alani's building this out and thinking this out a little bit more from the provider perspective. I just want to see if any providers how to initial thoughts and how this review process, may affect them. And again if nobody has any thoughts right now or they want to put those in discussion feel free to do that, but I think any conversations on rate and any of that kind of stuff we can save for steering committee or get help discussions if y'all don't mind + +Alani Kuye: Yeah, and that's our man. Thanks for I'm raising that tie and I think we'll provide a perspective. we know we solve for providers multitude ways, And that's why we having this conversation because everything related is we have to Take an operational maturity perspective, we can't Benchmark this based on the X exercises for providers the same way you incentivize pools for providers is not the same way you do it for deployers. It's very different audience. It's a different Market places a different process. + +Alani Kuye: Right, I mean back in the day when we have to build, some of the first providers, how long it took Gamo farms and all that means setting up servers. I mean it was insane but compare that till today it's easy point point click click and everyone on this call can attest to that right? So in moving to that other side, we can't say based on what we've done for providers, those same procedures and methodology will apply to deployers. It's a very different audience. It's a very different + +Alani Kuye: At places ux heavy right the folks who will be doing the death tasks QA uat before the five stages of development. I mean been doing this 22 years that there are no shortcuts. Okay, those audiences are a mixed bag. So you have folks from from folks on the Legacy space both another one technical right who want to see providers and who are these that's why you use the anilogy of Airbnb or Amazon. + +00:15:00 + +Alani Kuye: I don't have to go to those platforms to check reviews on some of those wholesale providers that can see them on bloggers referred me different ways. You can scan that Gap, right? So my point is I think this is where you have to think of it. Let's look outside of our comfort zone. Why does this look different because we're now working on the other side of the marketplace coming from someone who's Bill Marketplace isn't my last company I saw but 28 million because we build 30,000 driver. So I want to suffer three million people. So again, that's what I'm trying to get. What's this month to think differently like make a mental shift? You You're Building, for those who are not incumbents looking from a very different perspective. That it's a little bit uncomfortable at first, but when you start to understand why the bigger picture starts to make sense Anil. + +Tyler Wright: Sorry, that was me. I think a Neil put some comments in the chat. and then I think I'll also put some comments in discussions. And again, we can just continue this conversation offline. And again, we could talk a little bit more about it and steering committee and thread go ahead and + +Anil Murty: Watching three so really there's no other way to build this out then to go build those clients, go after specific segments of users and then very very tactically individually go and go go after customers and make sure that they're successful on Akash, So if you saw the Twitter species yesterday, it's all care. That's an example of a customer that took us a long time to get to and it's stuff like that that really was going to drive us forward. So I mean There are seven clients that are being great including sphere on and clouds each of these questions you slightly different patterns of the ux so,… + +Alani Kuye: Yeah. Yeah, Anil good to hear from you. + +Anil Murty: my suggestion and… + +Alani Kuye: I think the Twitter supposedly was interesting right… + +Anil Murty: I'll definitely read Your data post and… + +Alani Kuye: because That's a two-year conversation in making and… + +Anil Murty: comment on that as well is if you can identify specific things that these clients can do in order to help Drive adoption further. + +Alani Kuye: for those who don't know. I brought salt care into the akashicial system. Okay, and… + +Anil Murty: That's probably the best thing for us to do on the client side is presentation or… + +Alani Kuye: the same due diligence we're talking about today is the same thing that we're trying to do two years ago when I brought them in and… + +Anil Murty: my thought at this point, but I don't want to take up all the time in the provider say we should definitely talk Hey Alani,… + +Alani Kuye: the first one. + +Anil Murty: talk about this in this declines. so I'm sorry to intermed. We'll have to take this off of to another call. This is the sick provider call. And yeah, I don't know about history assaultier, but for two years it was nothing that was done on it and all this happened in the last two months. So I'm sorry to cut you off but we really have to focus on providers on this call and we can definitely talk about clients on the sick clients call we can talk about it in GitHub, but Tyler your choice here, but I don't think this is the right place to talk about. and if there is Merit and bring it up in the meeting clients in demand + +Anil Murty: + +Alani Kuye: don't think + +Tyler Wright: Yeah, no. Yeah exactly. And I think I made that clear a couple times. But again, if anybody can look at the GitHub proposal and leave comments in there. I know that Alani is looking for more feedback. That would be greatly appreciated. + +Tyler Wright: cool Continuing to move along. I know that again the pre-tor team has once again update on some of the things that they are thinking about for q1 2020 2024 real quick. And I think Alani also just mentioned it in regards to the GPU provider incentives. I know that's a conversation that Chang put up on chain, I think a week or so ago and there's been a lot of great discussion. thank you to folks on this call and other folks in the community that have participated in discussion. If anybody has any further thing that they want to talk about or any other questions, feel free to drop it in the GitHub discussions, and I know that we'll talk about this tomorrow during the steering committee meeting but again because this also touches that provider I just want to mention it here on the providers monthly meeting. + +00:20:00 + +Tyler Wright: And again push people to go looking at discussion give feedback ask questions and then join the steering committee tomorrow to talk about it in more detail. + +Tyler Wright: cool with that being said does anyone have any questions on GPU provider incentives before we move on to an update on some of the things that the prayer team are thinking about for q1 2024? + +Alani Kuye: All right. + +Tyler Wright: All right, igar. I'll hand it over to you or at the ball because I know that you all have been putting some time and effort into a specific plan a perfect. And then once the pre-tour team has presented a plan and we gotten questions from the prayer tour team. Then Andrew Mello was mentioned in a chat that he has some updates and I'll hand over to Andrew Mello. So jigarette and Deval you guys go first and then what open up to questions and then we'll follow with the angel Mello. + +Jigar Patel: Thanks Shadow. So for this presentation, basically we wanted to get a feedback from everybody about our q1 roadmap. And this is just like we are in the last meeting we presented over 2024 roadmap and we are chilling down to what we're gonna work on this Q one particular. + +Jigar Patel: These three months and based on the user feedbacks. we have certain things that our users and Akash users are facing right now issues currently they are not able to do multiple drives in FML storage test. One of them issued others are no issues. Sometimes they're facing a node issue where they wanted to supply custom nodes or they wanted to do a node in their own kubernetes cluster. So that's our other Focus as well. We are doing a kind of starting provided notification, which is very very basic right now, which will basically opt in process where you obtain for email notification. So if there is a upgrade on a network that + +Jigar Patel: All the providers have to do it. We kind of store their email address and just send them out and notifications. So people know that there is upgrade and we have to update our provider. We're gonna continue core provider service contribution. There's one more thing was the log issue. So whenever the providers become whatever using old process They're not able to see any logs if they wanted to see what's happening behind the scenes. So + +Jigar Patel: we are also building that log process. We're also doing a little bit better job at have error handling right? So, let me just share my screen real quick and I can go through the process or what we are going to do in just share + +Jigar Patel: so basically our plan in q1 is to solve this kind of primary six issues and then some misk operates that we are actually doing to resolves of the most. Ask supports from our community. So this is the exercise that we did from the last provider meeting. We found out that what are the areas that we are spending most of the time giving the support and let's solve that issues first. I work what are the most asked features from our providers in both provider channels and our ecosystem director channel, so + +00:25:00 + +Jigar Patel: Solving those issues are starting with everywhere multiple drives in every storage. So this issue comes a lot where small providers who don't want to give a personal storage, but they wanted to do multiple driving FML So basically combined storage process and then doing that into the Custom node options. So multiple ways to do it currently Akash core Library creates a node inside the kubernetes that we are not to do it, but we will give that option to users if they wanted to create a motor if they're servers is big enough so they can handle node. So that was one of the requirement because a lot of small providers are becoming provider where they only have + +Jigar Patel: Eight gigs of RAM and what eight CPUs sometimes even lower than that if they run nor inside the kubernetes, then it's become very like they cannot provide a lot of resources to network, So that's why we opt out to do question more but we will give them a new options where they can even choose the public mode they want if they want to use Twitter node, that's fine and They wanted to create a node inside a kubernetes because also be qns option probably notification what I explained earlier will give you important information like upgrades in an email in obviously. + +Jigar Patel: We will continue doing the provider service contribution in a core Library. we've been from that there will be a change is coming in. So we did a PR in control moderation, but obviously there will be a changes in coming as courty members who mentioned so we have to change our code as well. But yeah, that's and also any more contribution needed. We will be happy to provide that will stream logs into build process. This do you Longview feature that a lot of user requested we all so will be able to do a little bit more on error handling side because a lot of the errors are very common if the machine goes offline during the process we kind of like if we have an issue connecting it and + +Jigar Patel: SSS process don't give us kind of what are the errors And in the past our user had troubles. According to those errors because they don't know what's happening. And then we have to go into see logs and see what's happening maybe on their part is not open. Maybe DNS is not resolved. So things like that we want to do basically present better in UI, so I'll say thirty forty percent of the supports is just something they didn't do prior to Trader Bay process, right and that process with their doing it. + +Jigar Patel: Probably have error and then we have to you did that. Probably there. You're not right. So basically showing the process a little bit more informative. So they know what's happening. when they ask questions they know what's there on their facing so we can be at better head and error ol Miss cup breads, obviously DNS issue. So I would say another 20 30 percent providers have issue where they are not good at putting to DNS entries and our documentation. It doesn't handle that much very well on that issue as well. So a lot of people forget to put + +Jigar Patel: A wired card English or providers into their DNS. So we don't even know what's 30 years in a site. So right now in the dashboard when you become a provider, it's just says that your providers are fine, but we should see that if that DNS is rolling to their IP. If not, then we can better so that issue or give them steps to how to resolve that issue. Obviously we are gonna do the open apis for other teams like Benjamin where we can forward it now. + +00:30:00 + +Jigar Patel: Audit process to them now rather than the modri on it. So that's coming in connection issue again, A lot of people are having this issue. We wanted to just handle that better at the UI level again better talks and any upgrades that Akashi is putting in we will put into the process and put into the updates. Yeah, so that's our q100map any feedback Is very helpful God damir. + +Damir Simpovic: Okay, can you hear me? + +Tyler Wright: Yes. + +Damir Simpovic: All right regarding the first two points that you mentioned about what supports questions are the most common. I've actually made the I'm sure you are you remember but it's been quite a while since I see anybody mentioned it there is a number of videos that I did. That are primarily done for Helm based provider installs. However, there are also + +Damir Simpovic: they also apply to Such as how to set up port forwarding for any provider whether it's helbase or better based how to set up DNS. + +Damir Simpovic: Again, it doesn't matter which type of install. Anyone is using those videos are the same they will apply to everyone. etc. So, yeah, feel free to not trying these information videos. I don't make any money or anything of them, but just trying to make your life easier. You can just direct and you can just direct and have them watch these videos there 20 minutes half an hour and they will have a much better idea because you are right. A new providers especially home-based providers or somebody who's doing this for as a hobby or as they don't know. They don't know these things and it's very new to them and these concepts are + +Damir Simpovic: I mean everybody can has a + +Jigar Patel: Thanks, Absolutely. We will put your videos link again, for us. We are not gonna build any videos for that. We were just directing to forward some kind of videos in YouTube showing that how to do DNS entries, And if you have build I know so I've watched some of your videos, So what are we gonna do we gonna put your videos into the link so they can see how it work. It's working again. I just wanted to clarify and now pretty use Helms, So from even last year, So the whole process is it's exactly same we're just not building the node inside the kubernetes. That's the only difference because then those are one of the things that we had to manage. So if the note is not catching up then + +Jigar Patel: They will have some issues into the releases, So that's why we opt out but that's why we are giving the node option now. So that big enough there if they have multiple clusters, we can run configure with the node inside that right. but yeah, I just wanted to clarify we are using him is not different than the core process. quieter + +Tyler Wright: Go ahead. + +Anil Murty: Hey guys. Yeah, So awesome presentation. I like all the things that you have on the slide a couple of other ones that I can add and I have a few more notes on this second past you jigar couple of things. I've seen a lot of particularly the AI ml devs that we are trying to attract to GPU marketplaces. That they run into our number one if you're running a AI training job or even in some cases a fine tuning workload. You might want to be data downloading essentially data and then labeling it which is very CPU bound and then at the same time being able to access that same data to run training. So you might have a really large data set of several millions of objects downloading that into a + +00:35:00 + +Anil Murty: into some storage or area memory and then accessing it separately for the gpus to be able to train on it and one of the limitations today we have is that we don't support shared memory natively. And so that's an area that we have to look at Potentially in the next few months. I'm hoping so there's an issue that's created for that. and then the other thing also that I've noticed a lot of times happen with again people that are using gpus for various reasons is anytime one of these GPU cards overheats and sometimes results in the cache. + +Anil Murty: There isn't a lot of diagnostic information today that we're able to surface up in terms of for example, the temperatures on the voltage on the cards things like that. So that's another thing that I was wondering if there's something that we should do about it, but not saying that any other things on your roadmap need to be changed, but just wanted to throw them out. There is other pieces of feedback I've seen Thanks. + +Jigar Patel: Thanks for the feedback il. Yeah, if you wanted to ask to spend some time in doing any and kind of research in Ram issue or overheating issues right? Please let us know that's why we have read put the provider service contribution. That's one of the things that we wanted to do more in 2024 putting some hours into code libraries as we have done in past where the country for sorry content moderation, right? So we have a better understanding how the things work. So yeah. + +Tyler Wright: The ball,… + +Anil Murty: That sounds good. Yes. + +Tyler Wright: go ahead. + +Deval Patel: Yeah, sorry you can go. + +Deval Patel: Can you hear me? + +Tyler Wright: No. Yeah, I can hear you. I don't think anything else is speaking. I know did you have anything that you wanted to say? + +Anil Murty: No just gonna say I should raise my hand. I was just going to respond to jigarette say that sounds good. We can set up some time. I'll work with you to discuss some of the things that I've heard from people that are trying to do fine-tuning and machine learning type of workloads on providers in the challenges that they run into we have solved a couple of them, but there are some really big ones that we need to solve supporting. Sha. So, thank you. + +Deval Patel: Yeah, so these are just preliminary things… + +Tyler Wright: Thank you. + +Deval Patel: what we have in the q1 broad webinar higher level, we can go more deeper in the one to one or meeting where you can dive and prepare a roadmap for us. Right and we are open to ideas. What are the important things and facing whatever the challenges you are facing or hearing from providers in terms of GPU providers or our CPU providers, They're happy to accommodate that right another thing which is actually a lots of people are asking is that they make single provided node with the Creator and then they want to add more nodes towards the same collider, right? + +Deval Patel: Right now there is no UI available for that. Right? We have to guide through them and guide them through some manual process. So yes that is another option. We should consider adding into the roadmap right? But then the roadmap because becomes bigger and it becomes multi quarter roadmap, right? So those are the things we try to avoid, so that those are the things I would like to say one more thing. I want to mention is people are complaining about updating coorder taking too much amount of akt. So let's say just recently few providers updated there provider attribute and it charged them feet create which is about seven and half dollars, So think about that to reducing so if we can reduce that, that would be nice. + +Tyler Wright: Cool, I think if you don't mind making a discussion around that we can talk about that more in GitHub and then take some necessary steps. There must appreciates jigar you and Deval going through a prayer's plan for the first quarter 2024. Does anyone have any initial questions or feedback about what the priorities are going on? + +00:40:00 + +Tyler Wright: cool I think you'll set up some time with the Neil to talk about some of the items that he's been seeing and then again, we'll work on next steps and flushing us out and maybe turning this into a discussion to get more feedback from folks that maybe are not on this call but much appreciate the presentation and we'll continue moving forward. + +Tyler Wright: Cool, if there's no questions for the pray to our team that I know Andrew Mello wanted to give some updates. So I will hand the floor over to Andrew Andrew take it away. + +Andrew Mello: Hi Tyler, if you want to just pull up the GitHub of a cost OS while I talk about it for a second here. That might be helpful. It's a GitHub crypto and coffee slash a coffee list. + +Tyler Wright: I just Hold on just one second. + +Andrew Mello: Just in case there's folks who haven't seen it. + +Andrew Mello: On the phone today, so, thanks. + +Andrew Mello: Yeah, so it's still under development and is now actually powering the largest provider in production on the cost. So it has now, been a bit battle tested in production and with that in mind there definitely some updates that I wanted to bring some attention to so as some of you may know and some of you may not know a Costco acid basically built to be an ISO or + +Andrew Mello: An image that you install on any machine to basically give it Ubuntu 22.04 a kubernetes cluster and a default account provider install all configured for you automatically and up until now that required you writing that image to an actual, USB key or an ISO to attach that to a VM or attach that to your bare metal and boot from it and I have now been able to create ansible playbooks to deploy Akash OS against any VPS or bare metal without the need for the iso so that's a really nice update that I'm gonna publish in the next coming days here, but we are able to deploy now a cash OS to any machine without the iso part, which is really nice. Also, probably the most important feature that I'm going to be working on in this coming month on. + +Andrew Mello: a contrast is what I'm calling Auto port forwarding. So basically new providers are going to be automatically configured with a public domain managed by akashos.com. And until the user goes in and changes that domain they're going to have a joke like a generic domain name and what that's going to allow us to do is basically manage their port forwarding for them and so for onboarding new providers, and one of the largest pain points we have right and have had over. + +Andrew Mello: The time here is setting up the networking doing firewall doing DNS records all that. it's not a good time. And to be honest, It's really excluded a lot of potential providers because that right there is a barrier to entry for a lot of people in a technical knowledge, kind of Gap, people might know how to get through a website or get through an install of something but they're not necessarily familiar with how to do, firewall port forwarding or how to set up their DNS records perfectly. So a Costco Essence is looking to solve that for onboarding new users and onboarding providers and I'm really would like to see a conscious go to market with that as kind of a main feature right to make the easiest configuration possible for someone. So I'm + +Andrew Mello: Paying a release around first week of March for that where a new provider deploying The Playbook or deploying the ISO. + +Andrew Mello: is going to have a provider up and running automatically and I'm even considering going a step further with it and funding those initial providers set up fees so that there is just zero friction right that initial domain and provider could again be managed in a way that we make that completely seamless to the user and that's really the ideal because asking these new providers to get the akt become firewall experts be domain experts, right? We've got a lot of odd stacked against them. So I'm trying to reduce those barriers to entry kind of as quickly and hearing them as what's most important and I think the most important thing to solve for the new provider is going to be that with auto port forwarding and automatic Dom. + +00:45:00 + +Andrew Mello: And for them so they can just get up and running and then either prompting them for the akt for the setup fee or just doing it for them and worrying about it later. So that's my thoughts on what's coming next on Akash OS and the Playbook will be live within 48 hours or so up on the GitHub. + +Andrew Mello: Akash Dash com is now ready for a Kepler integration. So Akash Dash com is where you can monitor your provider earnings and how much your provider has made over time with really easy to understand, numbers for dollars and cents and so a class staffs.com is going to get a Kepler integration where providers will be able to claim their account. So when you go to check your provider right now, they BDO dot computer and it comes up with the stats. You just see kind of read the concept here is to turn that into read Wright information where once you authenticate with your Kepler wallet as the provider with your provider wallet, you'll be able to edit, the page you'll be able to do things like set up notifications and you'll essentially have an account now on a cash so that's gonna enable + +Andrew Mello: Them features down the road monitoring notifications all that fun kind of stuff we can start to do with it and expand on and yeah, those were kind of the big updates of what I'm working on with the cost OS And again Akash OS is once again now powering the largest providers in production. So I would definitely recommend you take a look at how it's built. Yeah. + +Tyler Wright: Does anyone have any questions for Andrew on anything? He just talked about in his updates? + +Tyler Wright: as Andrew just mentioned both with the parade or tool and with the Kash OS tool I would urge everybody to just try these things out to dive into the GitHub repos, test these tools out give feedback about things that you see to the prey to our team to Andrew so that we can continue to improve these tools and make sure that they are production ready but Andrew much appreciate your efforts and the update. Sorry Andrew, we're going to say something else. + +Andrew Mello: nope. That was it. Thank you. + +Tyler Wright: awesome Does anyone else have any other topics of discussion provider related that they want to discuss at this time? + +Tyler Wright: I'm much appreciate the conversation today the updates from Andrew from the praetor team discussions around what Benjamin is about to start building. And again, I'll set up a working group Channel and Discord and also start to set up the first working group session there. Thank you Alani for talking a little bit about your proposal that you put in discussions again reminder for everybody steering committee is happening tomorrow at 11AM Pacific as a part of the agenda. We will go through some of the just active discussions. I know there's a number of that have come in over the last couple of weeks. I would urge anybody that's going to talk about their discussion at steering committee tomorrow to just talk about it at the highest level about what you're trying to do ask what the problem that you're trying to solve and then we're going to continue to promote discussion over. + +Tyler Wright: Next week and then again, we'll hear from the steering committee because there's so many discussions happening whether it be around provider incentives where we've been discussion that Alani put forth. Obviously, we could spend an hour on each and I just want to make sure that we're just staying extremely focused and talking about the meat of what's going on with these discussions and then pushing people to get active and GitHub didn't get more feedback from the community. Cool again much appreciate everyone's time today great conversation. this is a couple of action items that will follow up on but if anybody has any questions comments or anything that they want to talk about further that they've heard here today. Feel free to drop in sick providers Channel and we'll just continue to talk async online but much appreciate everyone's effort time and commitment and really excited for what we got going on the future. + +00:50:00 + +Tyler Wright: Hope everyone has a great rest of their day. Thank you. + +Alani Kuye: Thanks dar. + +Andrew Mello: + +Tyler Wright: Over bye. + +Meeting ended after 00:50:46 👋 + From 4ae73bf8262ce9079273b8863a7bc1024e74ca09 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 27 Mar 2024 09:41:12 -0400 Subject: [PATCH 028/138] sig-providers Update 013-2024-01-24.md update meeting details Signed-off-by: Drinkwater --- sig-providers/meetings/013-2024-01-24.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-providers/meetings/013-2024-01-24.md b/sig-providers/meetings/013-2024-01-24.md index cbaf2f05..8e032e0d 100644 --- a/sig-providers/meetings/013-2024-01-24.md +++ b/sig-providers/meetings/013-2024-01-24.md @@ -9,7 +9,7 @@ ## Meeting Details - Date: Wednesday, January 24, 2023 - Time: 08:00 AM PT (Pacific Time) -- [Recording](https://7jnmboxzie2zlrw5nrmwu7ddgmzxiaywbjvmbx2xpr5qmfss7s3a.arweave.net/-lrAuvlBNZXG3WxZanxjMzN0AxYKasDfV3x7BhZS_LY)) +- [Recording](https://7jnmboxzie2zlrw5nrmwu7ddgmzxiaywbjvmbx2xpr5qmfss7s3a.arweave.net/-lrAuvlBNZXG3WxZanxjMzN0AxYKasDfV3x7BhZS_LY) - [Transcript](#transcript) ## Participants From 5e29372c760f606f52fa9d9aa5379995b4e0e896 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 27 Mar 2024 09:43:56 -0400 Subject: [PATCH 029/138] sig-providers Update README.md add meeting details to table for meetings 13 and 14. Chore: arweave recording link for meeting 14 Signed-off-by: Drinkwater --- sig-providers/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sig-providers/README.md b/sig-providers/README.md index 53d11d8b..f42318dd 100644 --- a/sig-providers/README.md +++ b/sig-providers/README.md @@ -27,9 +27,9 @@ Provider SIG covers everything pertinent to Providers on Akash Network. This inc | #10 | Wednesday, October 25, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/010-2023-10-25.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/010-2023-10-25.md#transcript) |[Link](https://2aefpzwgiwj6jzkl5fdsn7us3pjprpnpkoqqrrsu6bjaukktnxya.arweave.net/0AhX5sZFk-TlS-lHJv6S29L4va9ToQjGVPBSCilTbfA) | #11 | Wednesday, November 22, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/011-2023-11-22.md)| [Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/011-2023-11-22.md#transcript)|[Link](https://2ubf2cciht62e3qpxjur4h3ihccbyk6v2hbanktvxq2wcnifp5sa.arweave.net/1QJdCEg8_aJuD7ppHh9oOIQcK9XRwgaqdbw1YTUFf2Q) | #12 | Wednesday, December 13, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/012-2023-12-13.md)|[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/012-2023-12-13.md#transcript)|[Link](https://ro5kevc2mbgfpzyb7ufa5bor6thecu23sbzrqrham53ivpiljp2q.arweave.net/i7qiVFpgTFfnAf0KDoXR9M5BU1uQcxhE4Gd2ir0LS_U) -| #13 | Wednesday, January 24, 2024 08:00 AM PT (Pacific Time) | | | -| #14 | Wednesday, February 28, 2024 08:00 AM PT (Pacific Time) | | | -| #15| March, 2024 08:00 AM PT (Pacific Time) | | | +| #13 | Wednesday, January 24, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/013-2024-01-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/013-2024-01-24.md#transcript) |[Link](https://7jnmboxzie2zlrw5nrmwu7ddgmzxiaywbjvmbx2xpr5qmfss7s3a.arweave.net/-lrAuvlBNZXG3WxZanxjMzN0AxYKasDfV3x7BhZS_LY) +| #14 | Wednesday, February 28, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/014-2024-02-28.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/014-2024-02-28.md#transcript) | Coming Soon +| #15| March 27, 2024 08:00 AM PT (Pacific Time) | | | | #16| April, 2024 08:00 AM PT (Pacific Time) | | | | #17| May, 2024 08:00 AM PT (Pacific Time) | | | | #18| June, 2024 08:00 AM PT (Pacific Time) | | | From 22f8a7d5af05b4a9526d8d82899c948dfc1c0b36 Mon Sep 17 00:00:00 2001 From: Anil Murty <19495789+anilmurty@users.noreply.github.com> Date: Thu, 28 Mar 2024 12:58:11 -0700 Subject: [PATCH 030/138] Draft Praetor & Akash Provider Product Strategy (#524) Create praetor-akash-provider-console-strategy.md initial commit Signed-off-by: Anil Murty <19495789+anilmurty@users.noreply.github.com> --- ...praetor-akash-provider-console-strategy.md | 59 +++++++++++++++++++ 1 file changed, 59 insertions(+) create mode 100644 product-strategy/praetor-akash-provider-console-strategy.md diff --git a/product-strategy/praetor-akash-provider-console-strategy.md b/product-strategy/praetor-akash-provider-console-strategy.md new file mode 100644 index 00000000..200de15c --- /dev/null +++ b/product-strategy/praetor-akash-provider-console-strategy.md @@ -0,0 +1,59 @@ +# PraetorApp (Akash Provider Console) Product Strategy +Note: some of the initiatives outlined are contingent on Praetor joining the Akash Core Team (for which there is a proposal submitted in the discussion board) + +The Overclock and Praetor teams have been working closely to align on a product strategy and roadmap and it should come as no surprise to anyone that the focus going forward, is going to be around two broad areas: + +- Making PraetorApp part of a cohesive product experience that includes Console.Akash.Network (Akash Network’s primary deployment console). This includes rebranding and potentially integrating it better with Akash Console, to serve as a complimentary “Akash Provider Console”. It also includes open sourcing PraetorApp to align with Akash Network’s open source strategy. + +- Building solutions to problems around onboarding, monitoring, updating/ upgrading and troubleshooting Akash providers of all sizes (1 node to 1000s of nodes). Specifically, the problems that the two teams will solve are ones that have been surfaced by the Praetor team and Akash community while onboarding hundreds of providers onto the network overall the last couple years. The next section summarizes these problems, and organizes them by themes that will lead to a feature roadmap. + + +## Key Problems and areas of work + +### Telemetry +Akash providers currently do not have enough visibility into software issues as well as resource issues happening in the underlying infrastructure - in many cases, providers cobble together solutions themselves. To this end, there is critical need to provide first class telemetry in terms of: + - Logging + - Monitoring + - Error Reporting + - Provider config stats + - Automated Testing (Liveliness Probing) by running small deployments continuously and reporting back success/ failure. + - Grafana dashboard for visualizing all that data + +### Kubernetes Cluster Management +Providing better tooling to allow providers to maintain their Kubernetes cluster and software packages installed on it +- Akash providers rely on Kubernetes underneath and must often make changes to that configuration. For example a provider may start as a single node (as they are “testing the waters” on Akash) and then (as demand increases) decide to add on more nodes. PraetorApp today isn’t able to accommodate easily transitioning from running a single node (that may have been set up using K3s) to multiple nodes (running full fledged K8s). Ability to scale number of nodes as the provider grows is crucial. +- Providers need to upgrade to new Kubernetes releases from time to time +- Providers may need to apply specific software packages like CUDA and upgrade those as new versions are released + +### Provider specific RPC Nodes +Akash providers rely on RPC nodes (for bidding and communicating with tenants) and oftentimes the RPC nodes can be unreliable. While our documentation requires that providers setup their own RPC nodes, not all providers do that today. Making it easy for providers to install an RPC node during provider set up would alleviate this issue. + +### Easier Provider Updates/ upgrades +Making it easy for providers managed by Praetor to check and update to the correct Helm Charts, particularly if there are multiple Helm Chart versions released per provider service release. + +### Storage Setup and Configuration +Providers often have ephemeral (rootfs) storage setup with no redundancy (sometimes even with multiple disks - they don’t set them up to replicate data). Not having redundancy in ephemeral storage poses a risk because a disk failure can cause the deployments to be lost if there isn’t room to redeploy to another node. Making this easy to do (as a RAID1) as part of the provider setup, makes providers more reliable. +While PraetorApp supports setting up persistent storage at provider set up time, it does not support being able to add persistent storage after the provider has been set up (and did not include persistent storage to begin with). + +### Notifications +Providers have a need to notify and be notified about things. Broadly this is in 3 ways: +- Notify tenants (who have subscribed to them) about any issues +- Get notified about network upgrades and provider releases +- Notify tenants about provider resource reclamation - this is specifically for cases where a provider is bringing on resources that they have a long-term contract on in some centralized public cloud and therefore can only offer the resources “part-time” + +### Content Moderation +As Akash Network grows demand and reaches Web2 customers, there is a growing need to enable providers with tools to be able to moderate the type of content they host and prevent content that is harmful to their reputation or could harm them legally. The Praetor team has already been working with the Overclock Labs team on such tools and will continue this work. + +### Open APIs +Praetor has and will continue to build a store of key provider data that may be useful for other deployment clients or customers/ partners integrating with Akash Network. Making this data available through Open APIs will enable Akash Network to grow faster. + +### Documentation +Documenting various technical things related to setting up and managing a provider is crucial to growing the number of providers on the network. This will include: +- Video examples for set up +- Better documentation on SSH +- Documenting how to setup and configure port forwarding +- Documenting the common DNS pitfalls and how to fix them +- And more + +### Provider revenue and profitability data +A stretch goal for PraetorApp (and there are other ecosystem projects that have tackled this problem that we will aim to integrate with) but as demand on the network grows, giving individual providers tools to understand how much revenue they have generated over time, visualizing trends and relating that to their costs will go a long way in helping providers realize the value of choosing to provide compute resources on Akash Network. From e057d0a453af31da7b169d5caa1a5ca6ba58a7f8 Mon Sep 17 00:00:00 2001 From: Andrey Arapov <107317698+andy108369@users.noreply.github.com> Date: Tue, 9 Apr 2024 12:11:41 +0200 Subject: [PATCH 031/138] update provider audit template (#539) --- .../-provider-audit--template.md | 21 +++++++------------ 1 file changed, 7 insertions(+), 14 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/-provider-audit--template.md b/.github/ISSUE_TEMPLATE/-provider-audit--template.md index 4b2955a3..ab72f58d 100644 --- a/.github/ISSUE_TEMPLATE/-provider-audit--template.md +++ b/.github/ISSUE_TEMPLATE/-provider-audit--template.md @@ -1,13 +1,3 @@ ---- -name: "[Provider Audit] Template" -about: This is a template for all Akash Providers looking to be audited. Please fill - out all fields below. -title: '' -labels: Provider Audit -assignees: brewsterdrinkwater, andy108369 - ---- - --- name: "[Provider Audit] Template" about: This is for Akash users interested in having their providers audited by Akash @@ -18,7 +8,7 @@ assignees: andy108369 --- ## Prerequisite Steps: -### 1. Make sure your provider has community provider attributes: +### 1. Make sure your provider has community provider attributes and your contact details (email, website): ``` Example: @@ -30,10 +20,13 @@ assignees: andy108369 value: akash - key: tier value: community + info: + email: "" + website: "" ``` -[Ref documentation:](https://docs.akash.network/providers/akash-audited-attributes#standard-attributes). +[Ref documentation:](https://akash.network/docs/providers/akash-audites-atributes/#attribute-auditors). ### 2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP) ``` @@ -47,12 +40,12 @@ anything.ingress.akash.pro is an alias for nodes.akash.pro. nodes.akash.pro has address 65.108.6.185 ``` -- More info on what DNS records should look like are available in the [Akash Documentation here](https://docs.akash.network/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/step-5-domain-name-review). +- More info on what DNS records should look like are available in the [Akash Documentation here](https://akash.network/docs/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/#step-5---domain-name-review). ### 3. Please make sure your Akash provider doesn't block any Akash specific ports. - If you are using a firewall, please follow this doc: -https://docs.akash.network/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/step-9-firewall-rule-review +https://akash.network/docs/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/#step-11---firewall-rule-review - If you are behind NAT, then you need to make sure these ports are open between your provider worker nodes and the internet. From 015cc5091e7995c811755e4d5edda0733a007bb5 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 9 Apr 2024 10:50:51 -0400 Subject: [PATCH 032/138] sig-chain Update README.md add meeting 13 details. Chore: Add meeting 14 and meeting 15 to the table Signed-off-by: Drinkwater --- sig-chain/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sig-chain/README.md b/sig-chain/README.md index 7dd821a2..7dd3da89 100644 --- a/sig-chain/README.md +++ b/sig-chain/README.md @@ -25,9 +25,9 @@ date: 2023-1-09T00:19:20-08:00 | #10 | Wednesday, November 08, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/011-2023-11-08.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/011-2023-11-08.md#transcript) |[Link](https://sshyyg4r3uoeixzudilhwdkncekgk3yw5m6mulso6foidluersuq.arweave.net/lI-MG5HdHERfNBoWew1NERRlbxbrPMouTvFcga6EjKk) | #11| Tuesday, December 05, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/011-2023-12-05.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/011-2023-12-05.md#transcript) |[Link](https://ak4u4umlhafhkfu5jjckivcgokrrwkzzitwtwpoy5axl6soc5paq.arweave.net/ArlOUYs4CnUWnUpEpFRGcqMbKzlE7Ts92Oguv0nC68E) | #12| Tuesday, January 09, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/012-2024-01-09.md)|[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/012-2024-01-09.md#transcript) |[Link](https://p2eg6ctrzmvcgqmibhpnvtje32gi3rt3nzdyjocfohwt6kiddsma.arweave.net/fohvCnHLKiNBiAne2s0k3oyNxntuR4S4RXHtPykDHJg) -| #13| Tuesday, February 06, 2024 09:00 AM PT (Pacific Time) | | | -| #14| March, 2024 09:00 AM PT (Pacific Time) | | | -| #15| April, 2024 09:00 AM PT (Pacific Time) | | | +| #13| Tuesday, February 13, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/013-2024-02-13.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/013-2024-02-13.md#transcript) |[Link](https://swcn57cpu3ttvpgaf7e52xsv5wil57wtyredtvnd6bprntawwl3a.arweave.net/lYTe_E-m5zq8wC_J3V5V7ZC-_tPESDnVo_BfFswWsvY) +| #14| March 12, 2024 08:00 AM PT (Pacific Time) | | | +| #15| April 09, 2024 08:00 AM PT (Pacific Time) | | | | #16| May, 2024 09:00 AM PT (Pacific Time) | | | | #17| June, 2024 09:00 AM PT (Pacific Time) | | | | #18| July, 2024 09:00 AM PT (Pacific Time) | | | From 784d5c710dd705841f9cd59a0d80a7c92f183fd3 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 15 Apr 2024 03:33:06 +0000 Subject: [PATCH 033/138] Create meeting notes for sig-community #12 (#527) * Create meeting notes for sig-community #12 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 012-2024-02-13.md Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-community/meetings/012-2024-02-13.md | 229 +++++++++++++++++++++++ 1 file changed, 229 insertions(+) create mode 100644 sig-community/meetings/012-2024-02-13.md diff --git a/sig-community/meetings/012-2024-02-13.md b/sig-community/meetings/012-2024-02-13.md new file mode 100644 index 00000000..afc85756 --- /dev/null +++ b/sig-community/meetings/012-2024-02-13.md @@ -0,0 +1,229 @@ +# Akash Network - Community Special Interest Group (SIG) - Meeting #12 + +## Agenda +- Discussions upcoming events (approved through governance proposal). +- Discussions on Hackathon Working Group +- Brief update on Akash edu (launched two weeks ago). +- Overview of available bounties on the bounty board. +- Update from Scott and Tyler on bounty-related matters. +- Robert and Benjamin developer onboarding updates for the zealy project. + +## Participants + +- Adam Wozney +- Andrew Gnatyuk +- B S +- Benjamin B +- Julius Haus +- Max +- Robert Del Rey +- SGC | DCnorse + +## Meeting Details +- Date: Tuesday, February 13, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording]() +- [Transcript](#Transcript) + +# Meeting Notes +### Event Updates +##### Adam Wozney: +- Adam discusses his involvement in upcoming events, particularly ETHDenver. +- Highlights Akash's significant presence at ETHDenver, expected to be four times bigger than previous events. +- Mentions Greg, co-founder of Akash, participating in panels and events at ETHDenver. +- Adam's role as a moderator or emcee at ETHDenver, with various activities and panels planned. +- Akash's sponsorship of Dorahack's App Chain Day, including unexpected booth presence. +- Invitation for community members to participate in Akash activities at ETHDenver and Dorahack by contacting Adam. +- Announcement of Kubecon in Paris and available free tickets for interested community members. +- Details on Akash's participation in Nvidia event, including a cocktail party and booth sponsorship. +- Approval of an event at Consensus in Austin for Q2, emphasizing Akash's unique focus on AI. +- Mention of potential future events leading up to Consensus. +- Adam prompts participants to ask questions or get involved in event-related discussions via Discord channels. +- Invitation for participants to share any upcoming events they're involved in or interested in attending, encouraging further discussion. + +### Hackathon Update +##### Adam Wozney: +- Governance proposal for the hackathon passed about a month ago. +- First proper kickoff call with the hackathon working group held recently. +- Tentatively scheduling the first hackathon of the year for April 1st kickoff, in about two months. +- Seeking community members interested in paid opportunities for the hackathon. +- Roles include: + - Community Manager: Respond to questions in Discord and on the Dorahack website, manage workshops and activities. + - Events Manager: Coordinate kickoff and end-of-show calls, manage workshops and activities. + - Marketing Manager: Find potential sponsored tracks, recruit judges, assist with project evaluation and winner announcements. +- Emphasis on finding judges and sponsoring tracks to encourage community involvement. +- Paid opportunities available for these roles. + +### Discussion on participating in external hackathons +#### Andrew's Query: +- Andrew Gnatyuk raises a question regarding past participation in hackathons, specifically mentioning involvement in events like "hackathon solana" and other blockchain-related hackathons in 2020. +#### Adam's Response: +- Adam Wozney acknowledges Andrew's question and mentions that while he personally doesn't have the bandwidth for additional projects due to his current workload, he is supportive of Akash's involvement in external hackathons. +- Suggests that if there's interest in participating in upcoming hackathons, a proposal should be put together, following the process similar to governance proposals. +- Recommends initiating discussions in the community SIG or the hackathon working group. +- Notes that proposals for hackathons occurring in less than a month might not allow sufficient time for proper governance, while those happening in two to three months could be considered. +- Acknowledges the need for someone to manage these initiatives and highlights that he won't be able to contribute much due to existing commitments. +- Encourages individuals willing to dedicate time, even if self-funded, to manage such initiatives within governance proposals. +- Stresses the importance of reaching out to developers interested in decentralized computing and AI/GPU technologies through hackathon participation. +- Adam Wozney expresses support for the idea of participating in external hackathons, contingent upon the formulation of governance proposals and active management by interested individuals. +- Encourages further discussion within relevant working groups or SIGs. + +### AkashEDU Update +##### Adam Wozney: +- AkashEDU launched approximately two weeks ago. +- Over 300 people have registered and completed various curriculum projects. +- Plans to add new curriculum to maintain interest and engagement. +- Collaboration with Akash insiders and community members to develop provider courses and create videos. +- Call for anyone interested in creating courses for AkashEDU to contact Adam or join the AkashEdu Channel in Discord. +- Long-term vision for AkashEDU includes providing comprehensive technical and non-technical understanding of Akash Network, potential certification for participants, and support for projects through governance proposals. + +### Community Bounties Update: +##### Adam Wozney: +- Bounties are available on the GitHub bounties board, offering paid opportunities to support or grow the Akash ecosystem. +- Interested individuals can access the bounties board through the [provided link](https://github.com/orgs/akash-network/projects/6/views/2?sliceBy%5Bvalue%5D=%24%24+Bounty+%24%24). +- Current bounties include building a doc container for StarkNet and documentation for a hybrid processor provider. +- Community members interested in bounties encouraged to check the board regularly for updates and opportunities. +- Benjamin notes that one bounty seems to have been paid out, and another is currently being worked on. +- Continuous monitoring of the bounty board is essential as opportunities may update quickly. +- Opportunities for involvement in bounties may arise from discussions within working groups and special interest groups. +- Individuals with ideas for projects beneficial to Akash are encouraged to pitch them within relevant community groups. +- Governance proposals can also be initiated through GitHub discussions for larger-scale projects. +### Zealy Developer Onboarding Initiative +#### Robert's Update: +- Robert Del Rey provides an update on the Zealy developer onboarding initiative. +- Mentions successful testing of Zealy recently. +- Expresses gratitude for the support received and highlights the readiness of the program to launch. +- Discusses the evolution of the program from pilot to full-scale implementation. +- Describes improvements made to the missions, now catering to system developers, community members, and content creators. +- Explains the classification of participants based on mission preferences to streamline the process. +- Teases an upcoming mission focused on creating a documentary about the story of cloud computing and Akash's role in the market. +- Encourages participation and engagement through GitHub discussions and Discord channels. +#### Benjamin's Input: +- Benjamin B emphasizes the importance of reading through and commenting on the [discussion page](https://github.com/orgs/akash-network/discussions/457) for the proposal. +- Indicates readiness to create the proposal based on the feedback received. +#### Adam's Remarks: +- Adam Wozney commends Robert and Benjamin for their work on Zealy and expresses optimism about its potential impact on Akash's educational efforts. +- Encourages individuals interested in supporting Zealy to join the Zealy working group on Discord and participate in GitHub discussions. +- Highlights the significance of the upcoming proposal for Zealy's funding. + +### Closing Remarks: +- Adam shares his progress in reviewing Akash Insider applications and reaching out to potential candidates. +- Encourages interested individuals to apply to become an Insider via the new Akash website. +- Concludes the meeting with appreciation for everyone's participation and updates on various initiatives. +## Action Items +- Adam to finalize the schedule for the April 1st Hackathon kickoff and communicate it to the working group. +- Recruitment for Community Manager, Events Manager, and Marketing Manager roles for the Hackathon to begin immediately. +- The proposal for the next phase of the Zealy program will be finalized based on community feedback and submitted for funding. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Adam Wozney: All right. I think we live. Thank you guys for joining today's Community Sig call on what days today the 13th of February the day before Valentine's Day. So hopefully everyone has plans for their significant others, and if you don't have significant others, hopefully have plans to maybe find one or if you don't want one. it's really up to you. + +Adam Wozney: But today we're going to be chatting about all things community and the Akash Network just as a reminder of folks that have joined these calls are just to let people know who never seen these or maybe watching. The recording the Sig Community calls are really focused on discussion support topics and managing kind of cost Community initiatives. Those Community initiatives can run from events to the hackathons that we're doing education programs or even programs that you guys are individually working on zeli for example So that's really what the focus of these calls are before I get into my agenda to cover some items. I wanted to see if there is any agenda items that you guys wanted to cover or include in the conversation. + +Adam Wozney: Go ahead Robert. + +Adam Wozney: Cool, and y'all add that to maybe the very back end of my agenda just maybe a quick update from you see what thoughts you have or you and Benjamin? I know you guys are kind of working closely on that. So yeah, I'll include that for you guys at the end here any other agenda items or things you'd like to discuss or revolving around kind of Akash community activities. + +Adam Wozney: All right, so the handful things to cover I'm gonna go over some of the upcoming events that we have in person. That's all approved through the governance proposal that passed a few a month or so ago. We're gonna talk about our hackathon which as a working group formed around upcoming hackathon. That will be hosting. I'll give a very brief update on Akash edu, which is something we launched about two weeks ago. And then I'll talk about some of the bounties that are available on the bounty board also been Scott could join because I know him and Ty have been kind of leading that but I can cover that at a high level and then I'll pass it over to Robert in Benjamin to see if they want to give any kind of developer onboarding updates in terms of the zeely project that they're working on and then if there are any other items that you guys think about or want to feel free to let me know and we'll include it in. + +Adam Wozney: Gender these are meant to be informal. So as I'm talking through your hand up. You have a question or thoughts or feedback and we want to include you guys in the conversation. But first I want to talk about events for me personally. It's been taking up a lot of my time. Especially East Denver which is coming up in a little under two weeks. I believe Akash is gonna have a gigantic presence there, which is pretty cool. I've attended many members the past before joining, the Akash community and from my previous kind of + +Adam Wozney: events that I've hosted or participated within the Akash ecosystem. This one is maybe probably four x bigger, which is really cool. And I think that's just because a lot of excitement about what is going on and within the ecosystem. So we're gonna be having Greg co-founder of Akash, he's gonna be on several panels throughout the side events and on stage at Denver itself. I'll be moderating or I'll be em, seeing the Adam Denver event, which is something that we kind of spearheaded initially Adam Denver was gonna be we'll bring in a couple folks from different Cosmos projects to do small Meetup the last couple hours and it's turned to turn into nine different projects that are spot kind of helping support through sponsorship. I'm series of panel events. It's not going to be just about Kosh but we're gonna have a big representation there with + +Adam Wozney: Myself moderating Greg will be on a panel to be a series of. Panels and speaking opportunities throughout the day and there will be a little networking break some fun video game activities, which you can kind of participate in and then the after-party which is just networking and grabbing light bites and some drinks so that can be a bit one of the big events. We're also sponsoring Dora hack their app chain day, which I believe is on the 27th. We're gonna have a booth there, which I actually just found out yesterday. I thought we were sponsoring it would have some banners up but we are gonna have a booth there. So I think I'm gonna kind of lure in some of the Insiders and some overclock folks to help support the booth that we have. We want to be there all day. It's kind of on and off so we can kind of go in and hang out every now and again, + +Adam Wozney: I think those are the big things a lots of activities happening for eat Denver really really excited about that. If anyone that's watching this call or watching the recording is gonna be adding them or able to send me a DM or message in the general chat and just tag me and I would love to get you included in some of the Akash activities that we're doing whether it's helping out at the booth that we have at Denver helping out the boot that we have now at door hacks for their Train Day or getting involved in Adam Denver. Those are the big three events that will be doing and then of course. We'll probably be doing a tweet or a message soon about all the different activities Greg will be speaking yet because he has seven different events. He's talking about which is kind of wild. So I hope he's a tea with them because Voice make it straight by the end of the event. So I think that we're the next two big events that are happening. This quarter are Kubecon's gonna be happening in Paris. It's the first kind of web to we kind of event akash's sponsored and participated in + +00:05:00 + +Adam Wozney: As a part of our sponsorship, we actually have a few additional tickets those tickets are about 1500 dollars, I believe and we're looking for folks that are interested in attending kubecon. We won't be able to fly them out or fly folks out from the community, but if people can get to Paris if they can, cover their own costs to get there. We will be able to give them a free ticket and in return we're hoping that they can help out at a boost that we have. We're good on coverage. We don't need any additional support at the booth, but I think having a few extra hands on deck is always beneficial. So if you want to free ticket to kubecon which cost quite a bit and you're gonna be in Paris send me a DM I put a message in the coupon Channel inside of the caution Discord if you have any questions in there throw it in there. + +Adam Wozney: And then finally Nvidia which is happening over the same time period actually as kubecon we're gonna have one of our insiders. It's actually on this call participating in that we're going to be doing a cocktail party with a partner. We're having a small very private VIP dinner with the cash folks and maybe some VIPs and then we're also sponsoring of Booth with a partner at Nvidia, which is cool. And this is another web toy kind of event because + +Adam Wozney: Videos so big and Ai and gpus now it just made sense for a cost to be there. So we'll see what comes out of it, but I'm really excited for those three events. Last event thing I'll mention is we have already approved an event happening in Q2 consensus, which is happening in Austin. It's kind of the oldest in the crypto space. It's just a giant event that happens over the course of four or five days in Austin. We are going to be doing a booth there or sorry not Booth but I'm Meetup. That'll be on site at consensus. So won't be a side event. It's actually part of the consensus programming and it's because we got in so early we're gonna be the only kind of individual Meetup that's gonna be focused on AI that happens throughout consensus, which I think will bring a lot of attention to Akash, which is really cool. And there's also some talk of some other big event. + +Adam Wozney: are thinking about hosting and lead up to consensus which more details on that to come in the future, but I want to plan seeds of some Alpha for you guys to kind of get excited about So those are the big person events activities that are happening and over the next two or three weeks here. If you have any questions about that, you can head into the Discord channels. There's three temporary Discord channels for each of those events that I mentioned that you can ask your questions or get more involved in or just kind of see what's going on besides those person events. Are there any upcoming events that you guys are participating in are interested in kind of getting involved in any kind of person events that you guys are thinking about that happen this quarter or throughout the rest of the year. Any questions or thoughts on that? + +Adam Wozney: All right, cool. Next thing is the hackathon. So our governance proposal passed about a month or so ago and we just did our first proper kickoff call with the hackathon working group this week right now. We're tentatively scheduling our first hackathon of the year for April 1st kickoff. So that's in about, a little under two months. The two big things that were working on is I put it in an application for community members that are interested in helping out with the hackathon a paid opportunity similar to what we did for our last hackathon last fall. Basically, we're looking for a community manager someone who's able to for one or two hours throughout the course of week respond to questions in regards to the + +Adam Wozney: Done inside of our Discord and on the door hacks website, which is where our hackathon will be located. We're looking for an events Someone who can help put together and manage workshops and activities and a kickoff call and end of show call for the hackathon which will last, over the course of what a month and a half or so. + +00:10:00 + +Adam Wozney: And then we're looking for a marketing manager and really that focus is gonna be on finding potential sponsored tracks so we can partner with other projects that have a Synergy between the Akash Network and what they're building just sponsor a track and then encourage their Community to get involved in our act upon as well. As this part of this role is gonna be finding judges folks who will be able to dedicate their time to revealing all the applications and the projects that come in drafting feedback for those projects and then also contributing to the end of the hackathon call where we announce winners and then judges and kind of share their thoughts on the hackathon overall. So three big roles, those are paid opportunities. If you have any questions about the hackathon joined working group Channel inside of the Akash Discord and we'll get you guys involved in that. So any questions in regards to the hackathon. + +Adam Wozney: All We're Trucking right along. next up is Akashi to you. So we launched Akash edu last about two weeks ago. I think right now we've had a little over 300 people who've actually registered and gone through each of the different curriculum projects, which is pretty cool. I am starting to think about adding new curriculum to the courses because while we have this interest I want to kind of keep the care and stick model going where there's new courses people coming back and trying to update their education on all these different things. + +Adam Wozney: so I'm working with one of our Akash insiders to potentially put together a provider course and then there's a couple other folks from the community that are interested in creating videos in regards to Akashi to you. So there is anyone interested in creating courses for Kashi to you send me a DM or jump into the Akashi to you Channel, which I believe we've relaunched inside of our Discord. And any questions on Akashi to you right now. + +Adam Wozney: All one last thing you'll actually mention what it cost you since this is really the second wave of us kind of putting a proper kind of encouraging people to take these courses. We did the first push about four or five months ago, which is one course and now we added three more. I'm planning + +Adam Wozney: On what was I going with this? this is it so the long term Vision just for folks that are maybe curious because I've seen some governance proposals go up and the Discord chat in Discord discussions about educational programs. The long term vision of Akashi to you is to create enough curriculum that will give people a full-fledged understanding from a technical vantage point and from a non-technical advantage point of the Kash Network essentially at a certain point. I want people to become certified and that's something that we can share with folks. They can put on their LinkedIn they can use it to find jobs. They can use it to kind of launch their own projects and then we can also find projects that potentially support through governance proposals through the Adu program. I see a lot of different opportunity for Akashi to you but it is still early. So keep your fingers across tight that everything kind of progresses nicely. But so far, we're off to a good start on Akashi + +Adam Wozney: cool Next up is bounties. So for folks that are unfamiliar. We do have bounties that are launched inside of GitHub bounties board and kind of a regular Pace. Generally the bounties are focused on things that will help support or grow the Akash ecosystem. And they are paid opportunities to build these things. + +Adam Wozney: So for anyone I'm just going to put it in the chat here as soon as I can get it open for anyone that's interested in getting involved in these opportunities. You can go to this link. That's the bonus board. And if you have any questions about the bounties that live right now, which there's two that are live one is building a doc container for starknet that can be deployed in And the other one is documentation for a hybrid processor provider all the details and what those mean. I don't even fully know what they mean all the details for what those things are requesting are inside the GitHub in that link there. You can put in your questions put in your thoughts a few folks from the overclock the side are responding and monitoring those questions. So feel free to jump into that chat anytime. Any questions on the bounties? + +Adam Wozney: Cool go for Benjamin. + +Benjamin B: I also wanted to say that they just checked on both of them. And one seems to be paid out. Excuse my voiceless and the other one seems to have someone working on it right now. So they don't look to be available right now. + +00:15:00 + +Adam Wozney: It's funny before this call. I went in there and it looks like someone went in and just updated it. So always be tracking the bounty board because things are updating very quickly there. thank you for that call a Benjamin, but we're looking. There's no art and fast bounties that are every week. There'll be a new Bounty. It's kind of when they come up through Community conversations GitHub discussion special interest group calls through people's feedback. So they kind of pop up every now and again, but it does happen like Robert says they go fast. So if anyone is interested to kind of get involved in those bonus track that board that's probably the best place to go to kind of get the updates, but go ahead Benjamin. + +Benjamin B: And without that I think it's probably possible to reach out directly in the working groups and in the special interest groups that you're interested in when something is discussed. So if something is needed you can say hey I'm able to do this if I get about + +Adam Wozney: Absolutely. I would probably. Yeah, exactly. I think a lot of the bounties that kind of pop up are through conversations that are had in all the different working groups and special interest groups. So if you have an idea on something that you think would be beneficial to akash, you can jump into those specific groups those Community groups and sigs and working groups and kind of pitch them there and then from there there's a couple different ways and go but you can create a bounty around it or even if it's a bigger project you can go into GitHub discussions and create a potential governance proposal and a template for governance proposals are inside get up discussion. So good call out Benja other than that, those are really the big Community kind of activities that are taking place right now. + +Adam Wozney: Any other thoughts or community activities you want to call out before we maybe hand it over to Robert and Benjamin on some celiate developer onboarding updates. + +Adam Wozney: All right. Go ahead Andrew. + +Andrew Gnatyuk: Yes, I just a quick question. So a previous time 2020. We used to participate in different hackathons just on tracks like consolana and the other blockchains. Do we still plan to do that just to get more Akash attention on that or + +Adam Wozney: Yeah, so it's not anything that I'm personally working on. I'm in terms of my day to day and kind of agenda. It's pretty much locked in. I don't really have much bandwidth for anything else. However, I'm definitely Pro getting involved and external hackathons. I think if we did that we'd probably do the same thing that we do for a lot of these governance proposals put together proposal we see a hackathon coming up states with salana and it's in Three months I would say anything that's less than a month. That's probably not enough time to go through a proper governance proposal. But if you see something coming up, that's maybe two to three months out that's hackathon related and you're like, I think Akash could sponsor a track here. I think it's absolutely worth starting a conversation maybe in the community Sig or you're getting going to the hackathon working group because it's not because that's what we can kind of use that as a for all hackathon activities our own and external. + +Adam Wozney: But put your thoughts in there and then if you see the beginning some positive traction over a few days, maybe throw together a government's proposal the hardest problem with that is we need someone to manage it and that's why I'm saying that I won't be able to kind of help out with that very much just because I have a lot of these activities that I mentioned to you. But if someone is willing to dedicate time including pay for themselves to manage this inside their governance proposals, I'm totally Pro the idea. I think we should try to get out to all possible developers that are interested in viding compute deploying on a decentralized network or getting involved with aigp or in the AI GPU world. I think any kind of activity that kind of links with that in terms of the hackathons that are happening external to our own. Yes. I'm super on board with it, but it probably be something I have to go through a governance proposal and starting in a discussion group through one of these working groups or special interest groups. That makes sense. + +Adam Wozney: All right, cool. awesome + +Adam Wozney: Cool, that's it for my updates. The last thing in the agenda was zealing developer onboarding. I know it's something Robert and Benjamin have working on for a while. The first pilot project kind of happened last year and I would say it was a success and so because of that we're looking to scale it up a bit and kind of do some new things. So yeah Robert Benjamin wanted to see if there's any updates. from zeely + +00:20:00 + +Robert Del Rey: Hey guys, can you hear me? Alright? + +Adam Wozney: Yep. + +Robert Del Rey: I have unable that it seems like he bought a real recently and he just tested it out right now. So that's why I asked anyway guys. Yeah Thank you so much for the words, the developer on board the initiative that Benji and I are leading on Sealy. It's ready to take off this week. We had the silly working group called where we share the next mission. We're gonna have available For the next space of the silly program. I'm not gonna call it a pilot anymore. So yeah the city program. It's about to come in real real hard just to mention a few of the Nations that we're working on. + +Robert Del Rey: I won't say anything. If you want to see the missions I go to the silly working group chat on a cash Discord in and go there. If you have any questions also, we have to discussion going on on GitHub. Please go over the proposal and leave your comments and thoughts. Something that I will say we have done some improvements to the missions initially. We were focused on Beginner developers, but now the focus. It's brother. in the sense that we want to bring system developers or so regular community members and also real good content creators and something we did for that is that we have + +Robert Del Rey: different missions based on the type of quests that you want to do. Let's say you're only interested in the developing missions. If you do that mission, you will have access only for the developer missions. Let's say you just want to create content and you don't want to develop anything. That's also fine. You can do the initial first mission for that and have access only for the content creation mission. Which is amazing That will help us to classify. The participants better something that happened in the pilot is that we got many people participated, but we couldn't Classify them properly. So I guess this is going to help us out with that one Mission. I'm gonna say though. + +Robert Del Rey: It's about content creation. And I believe is if we get a good winner for this one. You're gonna love it Adam and you're gonna add it in the cash key to you. Let me tell you the name of the mission. one second All right. I lost It's month to so yeah, we're gonna have permissions for one more months to a month three. This one is for month. Number two. and it's about create A documentary about the story of cloud computing and what is a cash role in the cloud computing Market? + +Robert Del Rey: Benjamin I believe this topic it's amazing if we can get somebody to do a real 10 15 minute video about it. It's gonna be good information or all the people that watch the video and if they do that they might be able to earn some AKA out of it and who knows what comes next? So yeah, that is one mission that I can let you know again, if you want to see all the missions you can go to the GitHub discussion or you can go to that cache Steely channel on Discord. But yeah, that is what I wanted to say. I don't know when you have any extra go for it, man. + +Benjamin B: Yeah, I wanted to have that. I linked the discussion page in the shot and we would really appreciate if you could read through it and comment a little because we are ready to create the proposal. and Robert shared some updates on Discord as a comment and I don't think we need to create another discussion page. But if you feel otherwise, please comment that and maybe we live and release the proposal this week. + +Adam Wozney: very cool cool + +Adam Wozney: so if you are interested folks listening in the call, if you are interested in kind of giving your feedback thoughts or maybe even potentially getting involved in supporting kind of Robert and Benjamin's momentum within zeely jump into the zealy working group inside of Discord, but especially going to GitHub discussions because that's where all the conversations are happening right now in terms of zeli and then next steps for that will be a proposal fingers crossed that it gets funding because I feel really positively about Seeley. I think it's a great kind of supportive project for all of our educational efforts at accomch so very big fan and thanks to Robert and Benjamin for all the work. They've been doing on really cool stuff. Any questions for Roberta Benjamin on the zeli activities. + +00:25:00 + +Adam Wozney: No, okay, cool. that's really all we have for the call. I know Julius just joined. Sorry Julius but we wrapping things up today. We covered all the upcoming events East Denver kubecon and video and ways to get involved to kick off of the hackathon which is tenantly scheduled for April 1st, but if you're interested go and apply into hackathon working group Channel, there's a link in there to apply to support it and get paid and rewarding for supporting that we talked about Akashi you and some new courses if you're interested in creating some courses for that send me a DM we talked about the current bounties that live looks like a lot of them have been kind of snatched up already. So definitely document that page and bookmark that get a bounties board page. And finally we talked about ceiling and all the efforts Robert and Benjamin working on return to zealy more wrap up our call any final thoughts questions concerns anything that's top of mind for you guys. + +Adam Wozney: No last thing I'll actually mention is I finally have found I'm kind of caught up on all the events stuff that I've been working on. So I'm finally starting to go through the occasion cider applications and reviewing and reaching out. while I haven't really started going through them since the end of last year 2023. So we have about 60 or so applications that I've gone through and I'm started to reach out to some folks. So hopefully we'll have some new caution cider which for folks that are listening in their kind of the tip of the Akash Community sphere. hopefully we'll have some new insiders over the next few weeks here. So if you are interested in that head over to the brand new Akashi website, which looks beautiful by the way for anyone that's been helping out with the cash website and you can apply to become an Insider there. But the last thing I'll mention Anything else? Everyone's good? I think we're all good. + +Robert Del Rey: Thanks, Stay safe everybody, right? + +Adam Wozney: cool Thanks guys. We'll see in the next one. Larry y'all + +Meeting ended after 00:27:52 👋 + From 6834c14e0a600b3bb3d00d4b2c4607820962ea44 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 15 Apr 2024 03:33:34 +0000 Subject: [PATCH 034/138] Create meeting notes for wg-provider-audit #1 (#546) * Create meeting notes for wg-provider-audit #1 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 001-2024-02-21.md added transcript for meeting chore: add video recording Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-provider-audit/001-2024-02-21.md | 344 ++++++++++++++++++++++++++++ 1 file changed, 344 insertions(+) create mode 100644 wg-provider-audit/001-2024-02-21.md diff --git a/wg-provider-audit/001-2024-02-21.md b/wg-provider-audit/001-2024-02-21.md new file mode 100644 index 00000000..7bf6e9a0 --- /dev/null +++ b/wg-provider-audit/001-2024-02-21.md @@ -0,0 +1,344 @@ +# Akash Network - Akash Network Provider Attributes Working Group-Meeting #1 +## Agenda +- Welcome and Introduction +- Overview of Working Group's Purpose +- Review of p-i-3's Progress and Next Steps +- Discussion on Meeting Cadence and Timelines +- Any Other Business +## Meeting Details +- Date: Wednesday, February 21, 2024 +- Time: 10:00 AM PT (Pacific Time) +- Recording +- Transcript + +## Participants +- Alani Kuye +- Andrey Arapov +- Anil Murty +- B S +- Benjamin B +- Deathless +- Luna +- axime Beauchamp +- Maxime Cyr +- Rodrigo Rochin +- rUqeRT +- Scott Carruthers +- Tyler Wright + +## Meeting Notes +#### Tyler Wright: +- Tyler Wright welcomed everyone to the meeting. +- The working group emerged from Sig providers, focusing on tracking the p-i-3's work on building an open-source automated auditor on the network. +- A proposal was put up on-chain at the end of 2023, which passed. +- Tyler shared the proposal in the chat. +- The group aims to monitor the p-i-3's work and address any questions or concerns. +- Dedicated sessions will be held for discussing project-related matters. +- Cloudmos team's contributions were acknowledged. +- Currently, the auditing process is managed by Andre, with a template available in the community repo. +- The working group intends to improve the auditing process over time. +- The focus of the inaugural meeting is to check in with the p-i-3 team and establish meeting cadence and timelines. +- Benjamin was handed over to provide updates on the p-i-3's progress and next steps. + +### Benjamin Update (p-i-3 team) +- Learning GoLang for contributions, along with Sebastian. +- Planning to structure the project by creating prototypes first, then integrating into Cloudmos. +- Conducted small testing for benchmarking system capabilities. +- Challenges with accessing working temperature data. +- Seeking options for outsourcing KYC updates and verifying companies' information globally. +- Requesting ideas or connections for improving verification methods. +#### Questions for Discussion: +- Are there better options available for outsourcing KYC updates? +- Ideas on how to verify companies' information globally? +- Suggestions for improving verification methods? +- Open floor for discussion and suggestions regarding the questions raised by Benjamin. +### Anil's Updates +- Anil Murty suggests expanding benchmarking tests to include parameters available through Nvidia SMI command, such as fan speed and temperature. +- Anil Murty mentions previous use of KYC services by the labs team, potentially offering options or recommendations for other providers. +- Benjamin expresses interest in KYC solutions with minimal involvement of third parties. +- Maxime Beauchamp discusses benchmarking methods involving specific workloads or Docker containers on providers, potentially integrating benchmarking into the provider service. +- Benjamin and Maxime discuss the feasibility and benefits of integrating benchmarking into the provider service natively. +- Benjamin acknowledges the potential cost-saving benefits of utilizing the discovery service for benchmarking. +### Scott's Updates +- Scott Carruthers discussed the upcoming release of a functionality called feature Discovery within Provider Services. +- Feature Discovery is accessible via grpc and provides visibility into individual providers and across the network. +- Full GPU Discovery is a key aspect, offering information on GPU types, allocation, and availability. +- Worker nodes with multiple GPU models will provide detailed information on allocated GPUs. +- The functionality will enable analysis across the network, indicating total GPUs and allocation status. +- Rollout to strategic providers like Shimpa and Rodrigo is underway. +- Benjamin B acknowledged the inclusion of CPU information and potential for future additions based on demand. +- Information is accessible via direct grpc queries or the Cloudmos API, with a provided grpc query link for exploration. +- Participants are encouraged to explore the provided link for firsthand experience with the feature. +### Potential falsification of resource information by providers. +- Luna raised concerns about ensuring providers do not falsely advertise their resources. +- Scott Carruthers emphasized that feature Discovery aims to address this issue by providing constant, real-time updates on resources through a grpc stream. +- Feature Discovery operates at a PCI bus level, not relying on third-party binaries. +- Luna inquired about potential vulnerabilities at lower levels beyond the PCI interface. +- Scott Carruthers acknowledged the possibility but stated that, currently, there are no known limitations or concerns regarding feature Discovery's effectiveness. +- Benjamin B suggested that, despite safeguards, there may still be ways to falsify information, but addressing such issues would require time, incentives, and further exploration. + +### More Questions (Benjamin Update p-i-3 team ) +- Benjamin B raised a question regarding the accessibility of global databases for certain countries, noting potential challenges in obtaining data. +- Alani Kuye inquired about the process for provider checks, audits, and incentives, particularly regarding participation in incentive programs and the audit process. +- Tyler Wright redirected the discussion, suggesting that questions regarding provider incentives and audits should be addressed at the Sig providers level. +- Tyler clarified that a specific working group is primarily focused on developing automated auditing tools, while manual audits are conducted as part of the provider incentive pilot program. +- Further discussion on provider incentives and audits is scheduled for the Sig providers meeting next week. + +### Functionality and usage of the "provider TX audit attributes" command. +- Benjamin B resumed the presentation, mentioning the possibility of reading data via API instead of relying heavily on CLI commands. +- Benjamin posed a question regarding the ease of using the "provider TX audit attributes" command and sought clarification on its functionality. +- Andrey Arapov explained the process of broadcasting transactions on the blockchain to sign attributes and monitor changes, emphasizing the importance of ensuring attributes are signed. +- Andrey clarified that while it's theoretically possible to broadcast specific attribute changes, the tool typically broadcasts all signed attributes. +- Benjamin discussed potential future uses of multiple wallets for signing purposes and expressed gratitude for Andrey's insights. +- Andrey offered to provide further information and requested to be pinged on Discord for assistance. + +### Project Deliverables and Timeline +- Benjamin B expressed gratitude for the shared link and concluded the presentation, addressing any remaining questions. +- Tyler Wright raised the topic of project deliverables and suggested establishing a cadence for progress updates and testing phases. +- Tyler proposed a monthly cadence for the first three months, transitioning to a weekly cadence thereafter to meet the proposed timeline. +- Benjamin agreed with the proposed timeline, noting that most tasks will likely be completed simultaneously rather than staggered. +- Sebastian confirmed agreement with the proposed meeting schedule and timing. +- The team agreed to continue monthly meetings, with potential transition to weekly meetings in the future. Meetings will continue on Wednesdays at 7 pm. + +### Final words +- Tyler Wright proposed creating a plan for the first deliverable to be discussed in the next meeting, along with a short testing plan, to ensure tracking of progress for those unable to attend meetings. +- Benjamin B expressed a preference for online discussions over using images for benchmarking, inviting input from team members on alternative approaches. +- Benjamin B thanked participants for their contributions and assistance in answering questions throughout the meeting. +- Tyler Wright confirmed plans to create a specific repository for the working group on provider audits, containing meeting notes and relevant documentation. +- Tyler extended gratitude to all participants and encouraged continued involvement in the Discord community. +## Action Items +- Benjamin B to further investigate the possibility of a solution for KYC with minimal third-party involvement. +- Maxime Beauchamp to explore the feasibility of integrating benchmarking into the provider service and report back with findings. +- Andrey Arapov to rovide additional information and guidance on the broadcasting of transactions for attribute signing. +- Tyler Wright to create a specific repository for the working group on provider audits, containing meeting notes and relevant documentation. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the inaugural session for the working group provider audits. + +Tyler Wright: This specific working group, which has come out of Sig providers is designed with the intent of tracking the work that the pi 3 team is doing related to building an open source automated auditor on the network. they put a boat up on chain and that boat passed gonna drop it in the chat for folks. And again, this happened at the end of 2023 and they've been working this part to get up and running have attended a number of meetings to again get themselves up and running but we are going to have a working group related to just again monitoring the work if the high three team has any specific questions that they have obviously they know that they can reach out on Discord or come to six support or other very sigs. But again, we'll have a dedicated session. + +Tyler Wright: where we can go over anything related to the funds anything related to the project that the pi 3 team is going to be working on. I know that part of most of that project is around again an automated auditor solution, but I know there's also some most miscellaneous contribution being made to Cloud though so much appreciate the cloud most team in being here. I'm not obviously right now the process for auditing is managed by Andre and folks there's a template in the community repo for folks that set up providers and want those providers to be audited by Andre. But again, this should improve that process over time. For this inaugural meeting. I know that we just want to check in with + +Tyler Wright: the high three team and see where they are at this point. I know that they might have some questions and then we can figure out this meeting today or at least talk about it right now or talk about it today and then finalize between meetings just a Cadence for how often this group will meet and just a general timeline. I think the pi 3 team will share with us on when deliverables should be expected. So without further Ado, I'll hand it over to Benjamin who I think has something to share and we'll talk at a high level about where the pi 3 team is and next steps. + +Benjamin B: Thank you I think this introduction was Enough, so I'm not going to talk more of that. I will instead share my screen and I will get started. + +Benjamin B: So before we show our actual updates I want to say that we have some points here that we have done before and outside of anything. You'll see. for example, because a contributions are mostly preferred to have in either golang or in the node.js. And Sebastian has been working on learning golang. I will also be doing this for my contributions, but I'm not started on that. Not yet. then we have a lot of internal planning on how we want to structure everything and to speak briefly on that. We have made the choice to First create some prototypes. + +Benjamin B: And then create the actual systems. So we'll first get it up and running using our own systems and then we'll try to after that integrate it to cloudmus will integrate. To Cloud almost again and maybe work with the greater team to get started with. Some of our stuff as well. So for the benchmarking system updates. We have done some very small testing just to see what's possible or This is not a lot of to show for here. We've been able to get for example the capabilities. For this thank you. So what instructions you can give to it and it will work fine. + +Benjamin B: the product and vendor names so for example and vidy and + +00:05:00 + +Benjamin B: 1070 if we were speaking about gpus. And for CPUs, it will be something in the land. Or something very specific. But let's just say I 700 by 7,700. then we have + +Benjamin B: more things as well We also have the figure out how to read the memory size for the entirety of the rent of the working load. We also want to try figure out if we can do this for just the party renting but that's irrelevant to the fact checking the resources that's more of You get what you're paying for maybe? And then we also try to get the working temperature out and at least in the configuration. I was unable to do it. because of access and after searching a bit this kind of made sense. We want to do. more here And we're not going to start doing the action benchmarking it. for the kyc updates + +Benjamin B: We have Some options here. but instead of going in depth over what's this is and I just want to go over to the questions instead. That I have here. Is there anyone here that knows if there are better options available Even better if this could be outsourced to someone in the community. maybe if you know someone who deals with this sort of stuff, it's a very specific ask but you never know. + +Benjamin B: And I'm also wondering if anyone has some ideas on how to verify companies in another way. I know that in Sweden, we're able to have Some contact information websites Etc. That are linked to your company. But I was trying to find some Global source for this and I was only able to find it. I was thinking about maybe you can connects to The Domain in some way, but you already do that when you least from the provide around even And look up the domain. You don't know if someone has lied about the information. So I'm not sure how to continue There. + +Benjamin B: If you have any ideas, please raise your hand now on either this questions. + +Benjamin B: Feel free to go ahead. + +Anil Murty: Hey Thanks for putting all this Here for us review one question and one comment. So on the benchmarking Test that you're talking about. I know you mentioned gpus, but could you extend that if possible include a bunch of parameters that are available through the Nvidia SMI command? So it will give you things like The fan speed the temperature out of those things from the Nvidia semi command. They might be a little bit of passing that you have to do, but it's pretty extensive what you can get from it. And then the comment I had was as far as kyc as a service goes. we meaning the labs team have used kyc in the past for various tests. So we might have some options there, but + +Anil Murty: In general are you just looking for recommend suggestions for other kyc as a service providers? + +Benjamin B: Yes, either that or if you can offer some sort of the solution where the idea of the thing would be if providers could give their ATT to someone and that's someone or not company or whatever could do the kyc. Of course, it's possible to do everything with another third party, but the less part is involved the better. It's rather one that wants to speak more of something or should I go to the GPU question? If so, just please free to go ahead now. + +Tyler Wright: I saw that Max and Scott Heather hand up Matt. Did you have something specific about the land about kyc or was it about just general Benjamin benchmarking? + +Maxime Beauchamp: It was about the benchmarking. So if someone else wants to talk about the kyc I can wait. + +00:10:00 + +Benjamin B: No, no, go ahead with benchmarking. That was the first part of the question. + +Maxime Beauchamp: And I was talking with archer this morning about that topic specifically Because right now I assume that the way that you want to do the benchmarking is to run like a specific workload. Or a Docker container on each of the providers… + +Tyler Wright: Good. + +Maxime Beauchamp: if I'm not mistaken to get that information. + +Benjamin B: Yeah, we want to both do something where we can read off information. And then we also want to run some sort of image that needs specific work and if that retires the attributes are actually real or not. So perhaps if you have a certain CPU Euro offering maybe we can even go as for us. To check or the capabilities the same by actually testing the capabilities. I don't think we're going that far but more like running some workload and seeing how fast an extent and compiling that's data. + +Maxime Beauchamp: okay, and so yeah, I was thinking further about this and I think ideally because right now Scott will probably talk about this but the team has been working on releasing the provider Discovery service which kind of does that exposes more information about the GPU right now, but I'm pretty sure it can be extended to and more information related to the CPU memory and stuff. and when I was talking with archer this morning is I think the best way to do benchmarking. Would be to integrate it natively in the provider service. because for example if the providers don't have any space available to run the benchmarking. + +Maxime Beauchamp: Workload, you can't Benchmark that provider if it has a white list or something like this. There's a lot of constraints. to run a workload on the provider. So I think the best way to do this and if you mentioned that you want to learn golang, I think the best option for benchmarking would be to introduce it in the provider service natively. + +Benjamin B: Yeah, I think that makes a lot of sense. I still think it could be worthwhile to verify it in extent. But maybe the benchmarks will speak for themselves. I know that Luna wants to talk a little about how the attributes work. But if you would solve this through the discovery service instead, I'm guessing a lot would be saved in fees. So this could be an objectively better solution. I also see that Luna erased. their hand also if you want you can speak more on this Banner. + +Tyler Wright: I think Scott had his hand up. + +Luna: I think Scott yeah. + +Tyler Wright: I think Scott had his hand up and then Luna can go right after. + +Benjamin B: Yeah. + +Scott Carruthers: Yes, Ben. I do you mind if I just steal the screen sharing for one second? + +Benjamin B: Yeah, Let me. Close it. + +Scott Carruthers: Are you able to see my screen? okay, so to part of Max's point,… + +Tyler Wright: Yes. + +Scott Carruthers: so I just want to make sure that there's no redundancy and also that your application and your efforts can draw on from any existing information, so were about to release a functionality with them Provider Services called feature Discovery. And if you look at the terminal this is exposed via grpc. So this is a provider in sandbox that is currently running the feature Discovery service. So if I do a grpc query of that we can see that as far as + +Scott Carruthers: Let me get up to node 2. + +Scott Carruthers: So you can see that in part of feature sc We're doing full GPU Discovery. So this is going to give us full visibility into individual providers. And of course across the Expanse of the network as well. So this is just a provider with a single Nvidia Tesla T4. But if it had + +00:15:00 + +Scott Carruthers: if we have worker knows that have several different models, we'll get information on the type of gpus in the wall. So get allocated and elocatable information so we can see that all and in this section. So we're doing GPU Discovery and then we're also able to tell on those worker notes. How many are El capable essentially total gpus and also So this is a provider that had a total gpus and had for concealing we would say allocated for and then as I said, this will not only give us visibility for your perspective the most important thing would be on a provider basis. But then also this is going to give us the ability to be able to do analysis across the network and be able to say, the Akash Network currently has 100 a100 and 75 of those are currently allocated. So this is something that we're actually currently rolling out to a number of strategic providers, like shimpa and Rodrigo it's about to go through + +Scott Carruthers: Great on his provider. So we just want to do a little bit more sending a checking and a controlled Manner and then we're going to start doing a network where I provider upgrade. So the end result of that is feature Discovery and what I'm showing you should be available on the network within the next several days. gpus while the most important driver for feature Discovery, we're also doing things as a GPU and memory level as well. So again, I just want to make sure that your cognizant of this or this might be some things that you can draw into your application instead of doing some of the Discovery yourself, I just want to make sure that you are aware that this feature is imminent. + +Benjamin B: Yeah, thank I see that even some CPU information. It's available here. And I'm guessing that… + +Scott Carruthers: Yes. + +Benjamin B: because you're able to get the vendor you're probably able to get everything else to that in some way at least so… + +Scott Carruthers: Yeah. + +Benjamin B: if there's demand for anything more this can be added on to at any time. + +Scott Carruthers: Yeah, okay, and I will share in the chat and this goes for anyone that's kind of interested in saying this as you can see. I'm just collecting. So another important point in this is this information is all being consumed by Cloud most into their indexer. So you could get this information through direct grpc queries to those individual providers. But soon you also be able to query they Cloud most API to give feature Discovery information. But if you're interested in this information, I'll post this grpc queer Link in this is a provider that's going to be up for some time. So if you want to go in and play around with this at all yourself and see what information is available, you'll have that. + +Benjamin B: Yeah, please feel free. + +Scott Carruthers: Yep, that's all I had. + +Luna: All Thank I think this is a general question and it kind of ties with the feature discovery. And it's really just how are we making sure that providers don't? + +Luna: don't bake or falsely advertise their resources. So for instance, we might be getting GPU information from an binary. I think it's Nvidia semi, right? but I think that could easily be replaced with some malicious or fake binary that just Returns the information that provider once so we can falsely advertise resources that he doesn't have is it something that we are concerned about or not? Really? + +Scott Carruthers: Yeah, you know what? We're absolutely concerned about it and say if anything that was I would say that there's two primary drivers for feature Discovery. One of them being provider incentives being imminent and we want to be able to not only an appointed time but consistently through a grpc stream be able to tell if resources are removed inserted into system. So one of the drivers for feature Discovery is for provider and setas we're going to have a Constance and hack of not what providers are advertising via attributes manually but through this Hardware Discovery process. So yeah, that was certainly one of the big drivers for future discovery. + +Luna: I think it doesn't the feature Discovery software per se also have the limitation that it could be faked. So what exactly is the software querying I think if it uses some system binaries, they could easily be mimic to show information that would be false and does the provider will also relate it or the feature recovery allows all the relay that false information. + +00:20:00 + +Scott Carruthers: Yes, so the feature Discovery is not relying on any third party binary. We're doing Discovery at a PCI bus level. + +Luna: okay, and every made any discovery on + +Luna: possible ways that it could still be fixed or is it another concern at that level? I'm not familiar with the PCI level. + +Scott Carruthers: so I could not somehow be manipulated at a hardware level. I mean it's possible I think for the current. + +Luna: I mean, I mean not at the hardware level but at the lower level than the interface that you are attracted. + +Scott Carruthers: yes, I guess as a short answer would be at this current period of time so obviously if we Encounter any of those kind of concerns over time. We'll certainly address them for the initial purpose of feature Discovery. As I said, the primary goal being that we have a consistent view for provider incentives. So obviously we could always get into the provider ourselves through test appointments and things like that and do further. Station, but for the purposes of what we initially need feature Discovery for and for sending a checks of Provider hardware for provider incentives. I'm not aware of any limitations or concerns + +Benjamin B: Yeah, I'm guessing. in some way it should be possible to fake it regardless because + +Benjamin B: a culture doesn't really run your computer. You're the one with the access to it, but I'm guessing that this will take time to figure out and should also need some incentives to do it. All right. There was one question. That was not fully answered. I think. And I believe it was related to this. + +Benjamin B: and now I know we got a message in the shots that mentioned that their likely sent a global database. but for some countries it's possible to get this data easily for some other countries. It's not as easy. So thank you for those from that a lot of episcopes + +Alani Kuye: Hi guys. I just had a question around incident, Senator checks and Audits and incentives. if they providers are up, I mean first things for us are the providers opted into the incentive program or every provider just gets it that's the most high level question and secondly won't that be predicate on them? + +Alani Kuye: to get incentive then you have to obviously be a part of the audit process, right and the audits. I don't believe they'll be scheduled and they just happen on an ad-hoc basis that way, you don't have common providers. No one deal. It's gonna be and making sure they're ready to pass it and then they go back to the usual antics. + +Tyler Wright: I think that'd be more of a question for Sig providers at the highest level. I know there's operation in place to make sure that anybody that's participating in the provider incentive pilot program is getting audited with regularity and that'll be mostly manual but specific to this working group just push it forward. This specific working group is more mostly focus on the provider auditing automated tool. That's the high three and his team are working on. So if we can save that conversation for six providers, which is happening on schedule next week, that would be terrific. Unless anybody have yeah. + +Alani Kuye: Yeah. Thanks Tyler. + +Benjamin B: Did you have anything else or? it's memo. Okay, let me share my screen and I will continue with. The presentation and then Anil if you can send over more information. At the later point when more about the kyc provided you're using and if it's possible maybe to what I mentioned, that would be great. + +Benjamin B: Okay, I can see it for the auditor and this is the last part of the presentation. + +00:25:00 + +Benjamin B: We have seen that it's possible to read the data with API. This means that we don't have to utilize CLI in the same way that we originally didn't know if we would have to rely on that much. And then for all the thing, I went through the CLI commands and I have a question. Is it as easiest Around the provider TX audit attributes command. But then sharing the shot. Or is it the bombing another way to actually command for it? This sounds super simple question, but it looked more to be related to they actually provider, but maybe this is how we do it. I'm guessing someone here should know how the sign. command Works, especially Andrew + +Benjamin B: there's no need to talk about this here if you don't want to but that's just an open question. I'm hoping to get an answer. I'll ask it in Discord. + +Andrey Arapov: There is just a broadcast the transaction on the blockchain that this certain attributes were signed and trying to address the attributes and if the provider adds new attributes, they have to be resigned and something that I have script for a monitoring from time to time once a week plus minus and if I see some provider changes attributes like this, I'm just like a sharing the transaction again to make sure that the new attributes are signed and if they have removed a lot of stuff I can remove there is a broadcast transaction to remove what's been signed. So to make sure that the older ones aren't signed but not so necessary in some cases, example, for example, if provide your changes better to better three type of storage and then changes back so there is no reason going on sign the previous ones because they can change any time. So the better for us to make sure the sign because we trust him anyway, so + +Benjamin B: Yeah, I understand. and what you're doing here is essentially that all of the current attributes you're signing and then you can again do all of the current attributes. I'm on signing and then signing again. Or do you do with them or… + +Andrey Arapov: Yeah, if it's not necessary to unsign… + +Benjamin B: attribute basis? + +Andrey Arapov: then we know you can just like a broadcast again to sign the new ones and that's it the CLI to automatically handles this so just broadcast that all of this attributes are signed now and that's it. + +Benjamin B: Okay, I understand. But now we're talking about it. You can't sign a specific attributes here, right? but rather + +Andrey Arapov: No, at least like not what I've seen maybe on the protocol layer. It's somehow somewhat possible. But I'm not sure I think the tool just check the real attributes from the chain and just broadcasted. Hey, I signed this sort of but theoretically I think it's possible to broadcast if you modify the code some sort of attributes, I think but the battery harder could clarify it. + +Benjamin B: Yeah, I think maybe this has some potentially using the future, but we weren't planning to use it in that way. We were planning to set up a multiple wallets instead so that if we wanted to sign for multiple things if you want to sign everyone from Germany with one at risk, we can do that for filtering purposes. anyways, thank you a lot and if you want to share A description for that maybe it could be useful for us also. + +Andrey Arapov: Yeah, I'll look at it. Just ping me on the discorder like things. + +Benjamin B: Thank you. And then I want to continue with the last Point here is that with successfully been able to read some of the cloud most API, but now that I read in the Discord that it was updated. I'm not sure if it's outdated or not. But this is a really small thing that this is a fixable + +Benjamin B: Thank you for sharing that link likes. + +Benjamin B: I'll go through this later. So that's everything for the presentation and everything for my questions as well. So now it's up to anyone else if you want to raise your hand and if you want to give feedback or ask questions or anything. Actually, there's one more thing. I heard Tyler in the beginning of King about if we have any deadlines to say because of the way we're doing we're first creating our prototype or our internal solution and then creating the Integrations. We don't have this yet. + +00:30:00 + +Benjamin B: We don't have any rough timelines for anything right now besides and what was mentioned in the proposal. I hope this wasn't your question, please go. + +Tyler Wright: No. Yeah, I just think from a deliverable standpoint. I know that as outlined in The Proposal is a three to six month timeline to do a number of these contributions. I think they intended start date was a end of January. So I think we're close to schedule right now, but I just want to figure out a Cadence and then from a deliverable standpoint when some other members of the community we can go into a testing phase. I know that you have to do some deep diving into provider future discoveries the updated the cloudnos API, so For me, I'm thinking and this is up for discussion right now. If we + +Tyler Wright: Yeah, Anil just dropped in some information about kyc as well. So I know that's something else. I'm thinking maybe for the first three months like a February this next meeting in April. We stay in a monthly Cadence but it seems like after that we should be able to move to maybe a weekly Cadence where we'll have specific things that we will start to be able to see demo and test and continue to optimize that that seemed like a fair enough timeline as we try to hit That six month deadline at the high end. + +Benjamin B: Yeah, I think that makes total sense because most of the things we're doing we can work on all of them separately or most of them but they're not going to get finished at the different time periods. Really they're going to get finished or be able to be tested roughly at the same time. So doing it monthly now works for me and maybe Sebastian has something to add here How you can allocate time for meetings and such? + +rUqeRT: I think it's all good. + +Benjamin B: And that's the same time. as today Wednesdays at 7pm + +rUqeRT: Yeah, sounds good. We're doing monthly and then we're doing by Weekend. Yeah like that. + +Benjamin B: also Is there anything else? + +Tyler Wright: cool No, I would just say maybe as we lean into next meeting you will have more of a plan as a pertains to that first Deliverable look maybe the following month and maybe a short testing plan or something like that. I just wanted to be tracking. A deliverable wise so that folks that may not be able to make the time because again I appreciate I know it's late for a lot of folks in Europe but folks have family. So I want to make sure that if people can't join the meeting they have some specific deliverable that I can hand out alongside the notes and the recording and the transcript for people to track over the next month or two and then we can go from there. With something that's more concrete and visual. + +Benjamin B: Yeah, that makes sense. One last thing for me. is that someone I think it was Anil mentioned how maybe it doesn't make sense to use images to do the benchmarking in that case. I would prefer to do some offline discussion. So please feel free to send at the end if you have some idea how that could look like. But I feel like if the resources are really utilized regardless if you can rent it or you're not going to be able to do it if they're already working the course nourishing. but if you don't reach out and we will probably just continue as normal with our plan to create the docker images to essentially + +Benjamin B: Do some workload to figure out how fast the CPU is maybe it has. test test so that we can actually verify the advertised resources fully and not just how good they are. And then be able to give them scores or a combined score. + +00:35:00 + +Benjamin B: Thank you everyone for joining today's meeting. And thank you everyone… + +Tyler Wright: excellent + +Benjamin B: who could help answer all these questions. That's it for me,… + +Tyler Wright: Okay. + +Benjamin B: but I'll leave it to Tyler if you want to. Have some final words. + +Tyler Wright: No, I again much appreciate Ben walking through I will create a specific repo inside of the community post specific folder for the working group for provider Audits and to be a lot of read me and add the meeting notes for this meeting and then much appreciate everybody that's involved in these conversations today to continue to stay involved be a Discord. I'm going to continue to add a number of folks to the meeting link just so they have it on the calendar. And if anybody wants to be added feel free to let me know but yeah, we'll continue to track the work of the pie three team there again much appreciate the work today and we'll talk more about auditing and that process at the pertains to providers for the incentives at the sick providers meeting because I know some other folks that can make + +Tyler Wright: Here today want to be a part of that conversation. So Alani if you have time next week to join sick providers, that would be greatly appreciated and we can go from there. + +Tyler Wright: All right, I hope everyone has a great rest of their day. Again. Thank you all part three team for leading us through thanks for all the questions and we'll share those resources on discourse that can continue to make sure we're not Doing redundant things as Scott has mentioned that we're just leveraging all the work that the community is doing to continue to push these efforts forward and other efforts so much appreciate everyone's time today, and we'll talk online. + +Andrey Arapov: I think + +Tyler Wright: Thank you. + +Benjamin B: Thank you. + +Scott Carruthers: That's done. Thanks, everyone. + +Luna: Thank you. + +Meeting ended after 00:38:24 👋 + From e4c6ca4a0f103e3ed93070f40c0f7251491b064c Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 15 Apr 2024 03:34:05 +0000 Subject: [PATCH 035/138] Create meeting notes for wg-zealy #10 (#542) * Create meeting notes for wg-zealy #10 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 010-2024-03-18.md added transcript for meeting chore: add video recording Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-zealy/meetings/010-2024-03-18.md | 312 ++++++++++++++++++++++++++++ 1 file changed, 312 insertions(+) create mode 100644 wg-zealy/meetings/010-2024-03-18.md diff --git a/wg-zealy/meetings/010-2024-03-18.md b/wg-zealy/meetings/010-2024-03-18.md new file mode 100644 index 00000000..923fe2f3 --- /dev/null +++ b/wg-zealy/meetings/010-2024-03-18.md @@ -0,0 +1,312 @@ +# Akash Network - Zealy Working Group (WG) - Meeting #10 + +## Agenda +- Address reward distribution issues. +- Discuss current and upcoming missions . +- Social media activity by end of month. +- Resources for mission creation. +- Zealy update on scam prevention and Zealy community continuation. + +## Meeting Details +- Date: Monday, March 18, 2024 +- Time: 6:00 AM PT (Pacific Time) +- [Recording]() +- [Transcript](#transcript) + +## Participants +- Robert Del Rey +- Scott Hewitson +- Tyler Wright + +## Meeting Notes +### Review of missions: +#### Robert +- Over 100 submissions reviewed, including some low quality and copy work missions. +- Robert and Benjimin conducted a two-hour review session, highlighting standout submissions. +- Shared two notable images from Stable Diffusion, considering showcasing them on Discord. +- Emphasized the importance of effort and quality in submissions. +- Proposed sending weekly reminders to discourage low quality and copy work missions. +#### Feature Missions: +- Mentioned upcoming missions for GTC and KubCon events. +- Introduced a mission to attend the event and take pictures with Akash theme, aiming for social media visibility. +- Encouraged participation in missions for increased social media support. +#### Feature Mission: Providers Mission +- Scheduled to be shared around Wednesday or Thursday. +- Aimed at reminding providers about the mission. +- Providers who meet the criteria can earn extra AKT. +- Encouraged participation for those providing resources to Akash Network. + +### FAQ Document Update: +#### Robert +- FAQ document sent out last week; well-received by the community. +- Includes common questions such as mission participation on mainnet or testnet and wallet connection requirements. +- Currently contains five to six questions, addressing the most frequently asked queries. +- Open for feedback from community members; comments welcomed. +- Document pinned in Discord for easy access and reference. +### Zealy Role Administration: +- Discussion on setting up Zealy roles in Akash Discord. +- Process involves adding admins and connecting Zealy Community with Akash Discord. +- Template mission to claim Zealy role to be created. +#### Admin Setup: +- Tyler to be added as admin in both Akash and Zealy. +- Tyler seeks reference and documentation for security confirmation. +- Robert to provide an example of Zealy role appearance in Discord. +- Tyler finds documentation from zealy.io for reference. +- Tyler confirms receiving the admin invite for Zealy, appreciates the assistance. + +### Zealy update on scam prevention +#### Robert: +- Rise in scam communities observed, prompting Zealy's certification process. +- Communities need to be verified to appear in searches and be highlighted on Zealy's website. +- Verification requires upgrading to a monthly plan, starting at less than $200. +- Benefits of verification include increased exposure and higher data export limits. +- Funding from Greg is appreciated and will cover the cost for the next three months. +- Need to accept more missions and increase participation to meet goals. +- Upgrade to the monthly plan for certification and enhanced visibility. +- Continue campaign efforts to attract more participants. +- Discussion needed on future plans after the campaign ends. +- Ability to cancel the plan after three months and reassess options. + +### Twitter Spaces Promotion: +- Discussion on promoting the upcoming Twitter Spaces event. +- Robert plan to share the link on Discord and Telegram once available. +- Tyler offers assistance in amplifying the event. +- Scott suggests highlighting the community-driven nature of the program during the Twitter Spaces event. +- Emphasis on the program's evolution from zero to Zealy. +- Scott offers to provide community support funds for a giveaway or bounty during the Twitter Spaces event if needed. + +### Closing Remarks: +- Robert expresses gratitude and invites further communication and feedback. +- Meeting concludes with wishes for a great week ahead. +- +## Action Items: +- Robert to evaluate the benefits of zealy verification and decide on upgrading to the monthly plan. +- Tyler to follow up on pending tasks and Zealy discord roles. +- Robert to consider sending weekly reminders to prioritize quality in mission +- Robert to Continue promoting feattured missions for community engagement. +- Robert to share and remind providers about the providers mission. +- Robert to Prepare for the Twitter Spaces event and coordinate with Cosmos Spaces for promotion and logistics. +- Robert to Continue to update FAQ document based on community feedback and emerging questions. +- Robert to share the Twitter Spaces link once available and highlight community ownership during the event. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Scott Hewitson: started + +Robert Del Rey: No worries. We help each other. Thank you so much Scott. thank you guys for joining today's call. + +Robert Del Rey: Silly I cash ceiling working group called. This is the second call after the campaign officially started and I got a few items in the agenda. Seems Benji won't be able to join today. That's okay. The recording will be available on GitHub. And a quick update I was able to update the last call into the Sealy working group. I don't know how to call if it's a threat a Blog but in the silly working group in the cash GitHub, you will be able to find the last recording and also this one in the next one and the next one. So yeah the agenda for today. + +Robert Del Rey: it's gonna be about The missions we review some submissions. Some people are not getting Rewards. Also missions that we posted and we're going to post in different groups of a cash, Discord. + +Robert Del Rey: There is social media activity coming up by the end of the month. also resources to help people make missions and let me add one quick update about Seeley it's trying to prevent some scam communities and there is something we almost do if we want to continue with this community. I will leave that one by the end. So guys unless you have any other topic that I didn't mention I will go ahead and start with the items of the agenda. Go ahead Scott. + +Robert Del Rey: Thanks for reminding men and no Nobody got back with me on that honestly. me write it down to… + +Scott Hewitson: Okay. my God,… + +Robert Del Rey: because he + +Scott Hewitson: I don't know Ty is able to do it. I know he made it said Corey, but it not I'll take Corey today make sure that gets done. + +Tyler Wright: So can you reiterate I might have missed this while I was at I apologize. what is with the roles that need to be done? Because I can make sure that gets done today. + +Robert Del Rey: thanks Tyler's man. + +Robert Del Rey: if we connect I catch this score and silly. It's gonna be easier for us to assign Rose to people and also track where they go within a cash Discord. This has nothing to do with the silly update. I just mentioned this is something else. So if it's possible to have those silly rolls at it, that'd be great. And yeah. + +Tyler Wright: Did you put a note in the zealy channel? I just need to find that note so I can just go a little bit more information. I apologize you. + +Robert Del Rey: It's a good man. No worries. Yeah, I can get it for you. I + +Scott Hewitson: Yeah. I'm gonna at you and it + +Tyler Wright: Okay. beautiful + +Robert Del Rey: Mmm, thanks Scott. + +Scott Hewitson: there you go. + +Scott Hewitson: I got you fam. + +Robert Del Rey: Yeah, yeah, I know so. Yeah, that. We're gonna go over that in a second. So yeah, the most important thing is that we were reviewing missions. We are over the hundred submissions Mark already. We have some good submissions, but we also have some low quality and copy work missions Benji and I did a review session. We sat down for two hours going over each Mission and a second some rejecting Suddenly, he's not here to showcase the developing missions, but I'm here to show Two submissions that we have from a stable diffusion. + +Robert Del Rey: Let me see if I can share the screen. window, okay, let me know if you guys can see it + +Scott Hewitson: Yep, I can see it. + +Robert Del Rey: Awesome, so we have this one. That I like a lot. And this one? I don't know how to feel about this one yet. But at least it's a cash. + +Robert Del Rey: so yeah, those are two of the bestest images that we found with there are a few more but these two. I think we're worthy. The Highlight. I would share them on this court too later today. There are some building missions. Like I said, but Benji was supposed to Showcase those. I wish I could with him after this cold. No worries guys. But based on that reviewing session we sent a reminder in the description. So guys can keep in mind that We are here To do the missions, But we have to make an effort and the advice was to avoid doing low quality low effort and copy work missions. + +00:05:00 + +Robert Del Rey: Maybe we can send that reminder on a weekly basis, but we never sent that reminder before so it's okay if they did some spammy submissions. Hopefully it decreased now. But yeah. that I don't have this stack number like the legit submissions. But like I said, we are over the 100 people Mark, which is a very nice. If you have any questions about this one, I will move to the next Topic in the agenda. + +Scott Hewitson: Do whatever you'd like because you're already crushing it. + +Robert Del Rey: Thanks, That's a good one. I have used the pin message feature. I believe having this reminder will also benefit. Thank you so much Scott. + +Robert Del Rey: And let me write it down. I only can do one thing at a time once that + +Scott Hewitson: you're holding that money. You got to do the mic drop and you can right. + +Robert Del Rey: Man, this is already green message But I got it. Thank you so much guys, so moving on the next topic. It's about the feature missions the working group missions as GTC and kufcon are happening this week. If I'm not mistaken. We open up a missions. It's attend to cook Comfortis take a picture with their cash theme of the other people you find there. And you might have a chance to win some akt just a little context. The reason why I want people to do that is because I want a small as most support as we can have in social media. + +Robert Del Rey: So having different people posting on social media. Hey, I'm here with the cash team that could help the numbers on social media. I know it's not fun experiment if you ask me. So That's the Fisher mission that we had for last week. We opened it up and I shared them in the events group in the silly groups. But also the temporary groups that Adam created let him letting people know that they have that opportunity in case they want to take advantage of it because that's the good thing about it. It's not mandatory that they do missions. But if they want to do the missions they have missions to do. For this week. The Fisher mission is going to be the providers mission. + +Robert Del Rey: Around Wednesday or Thursday. I will go ahead and share them and remind providers that we do have a providers mission in case they provide some resources to a cash Network and meet the criteria that we have. They can earn some extra akt. Besides whatever they're getting paid if they're getting paid by providing resources on a cash. So yeah, that's the Highlight mission of this week. They providers Mission. Let's see how it goes any questions on this topic in particular. + +Robert Del Rey: If not, that's okay. Thank you so much. The next one is short. Also, it's the Twitter Spaces by the end of the Sprint. I share it with my good friends of cosmosa spaces. They have a validator on a cash and a few other networks in the cosmos ecosystem across the spaces is a big validator and they do lots of spaces. They have a big following too and most importantly within friends for almost two years. So it's a good relationship that we have. the thing is that by the end of this month. We're aiming for March 25th next Monday. + +00:10:00 + +Robert Del Rey: We're gonna do a Twitter spaces so we can update Their audience about how we see doing and how people can take advantage of a cash silly and how to get involved. So basically I want to leverage their following on the cosmos ecosystem so I can share this serious stuff and hopefully get more people in the silly train. We are thinking of doing a small giveaway for the people that joined the spaces. And hopefully they join and they win the prices that we have available for everybody. Like I said, the day is going to be next Monday. That way we have one week remaining from the Sprint and we can also remind people that another Sprint is coming up for month number two. + +Robert Del Rey: It sounds like a good plan. Let's see how it is in practice, but I'm very optimistic about it. And I believe social media campaign. It's also very important because we can be sending reminders in the group chats. Right? But if Outsiders don't see this on social media, it's gonna be uphill battle to try to get more in new people to try this campaign. yeah, and I want more. that on the touristspaces topic. the following topics are limited Power Man. that the other one is that we did a FAQ document. The frequently asked questions document. We sent that last week people like it. + +Robert Del Rey: And we just added the most common questions. We got so far, if people have to do missions on mainnet or testnet. And if they have to connect their wallet to participate we clarify that over there too. So yeah at the moment it's like five six questions, but there are the most questions that these people have asked so far. Everybody can comment in case somebody joins and want to drop a feedback. They can comment the feedback. And also I pin that message in this course, so it's easy to find. And yeah, that's that with About the city role. Let's go back to that one. + +Robert Del Rey: Yes, I was saying yeah, it's just having roles. There is not much work to do on that. if you want to do what just let me know we can do that in two minutes. You just have to be admin in their cash silly community and connect the silly Community with a cash Discord after you connect that we're gonna create a mission. It's a template so it's not too hard. So the silly Community can claim their City role and that role is going to be added in their Discord profile. I don't know if you noticed that my profile for example, it sets server booster. inside there. It says Bangor by having this silly role. + +Robert Del Rey: Everybody doing silly missions are gonna have a silly role in their Discord profile. It might not mean much but even as recognition people like that and I believe it's good to have it and go ahead. + +Tyler Wright: I think this all makes sense. I guess my one question is am I a admin as Corey and admin and zealy? I'm not sure if that's the case and… + +Robert Del Rey: Either I will need to add you. + +Tyler Wright: okay so we might Yeah, so if you could add me as an admin and zealy at my + +Tyler Wright: Akash email that would be great and then if there's a link I'm looking at the link that was shared by + +Tyler Wright: But was reshare by Huey, but was originally shared by you Robert and it makes a lot of sense if there's any reference that you can provide from zealy just because I'm in conversational Corey right now. I just want to make sure from the security standpoint. He's feeling comfortable and then I can let loose from there. But I see there's a quick screenshot that she dropped in here if there's Any other information? I'm sure I can find it too is really. to school + +Robert Del Rey: Maybe I'll go ahead and also send you an example of how the city role looks like in your account after you have it. + +00:15:00 + +Tyler Wright: actually + +Tyler Wright: You know what? No, I'm good. I found a quick link. That's from zealy.io their documentation integrating into Discord. + +Robert Del Rey: Okay. + +Tyler Wright: I think this is all Cory would need. To make a determination. + +Robert Del Rey: Awesome, man. + +Tyler Wright: So yeah, if you can add me as an admin. Then once I hear back from Corey saying That we should be in a good place. + +Robert Del Rey: If you don't mind this page, you can see the members. This is Fiverr. Benji has the same permits as I do and this is Andrew. I don't know if Andres aware of this is still let me + +Robert Del Rey: let me ask him. Yes review Okay, so Thai I have At a cash Network. That's it. + +Tyler Wright: Yeah, Costa Network. Yes. + +Robert Del Rey: By l e r at a cash dot Network, awesome Please I have seven eight nine. Yes. + +Tyler Wright: Yes, Am I social security number is not just kidding. right + +Scott Hewitson: What's your speed trays? + +Tyler Wright: got it. + +Tyler Wright: Yeah, I got it. + +Scott Hewitson: Don't looks like he dropped off. there we go. + +Robert Del Rey: Okay, that was quick. Sorry about that. + +Tyler Wright: No, no, I received the invite so much appreciated. + +Robert Del Rey: Good good. Okay, and the last thing I want to cover it's about the Sealy. Update so last week. They posted that they noticed a rice in a scam communities. Some people are creating communities to scam people which is super bad. So what are they are doing they are? Certifying communities they are like betting communities as you can I'm not sharing the screen yet. Let me share again. I won't end this call this time. I promise. Okay, so as you can see here, we are still under the free plan and we are on listed. + +Robert Del Rey: is not that they are gonna delete all of this and throw our work away. No, but as long as we are unlisted our community' In the search if you search for A cash Community is not going to appear. Also, if you go to Sealy web page directly. They highlight communities. these are mines. But here you can see new communities silly highlight new communities and that helps to get a few extra more people. But as long as we remain unlisted, there is no way silly highlighters here. So I already asked what needs to be done in order for us to be verified. + +Robert Del Rey: and I close silly. And basically we have to buy the Long story short. Yeah, if you have the monthly plan, they certify you right away. The planet the moment just so we're still gonna need to buy it. And I will explain that in a second. But the starting plan is starting at a little less than $200 a month. This will give us some things. the limit to claim Quest at the moment we have 5,000 XP per month, which is nice. The issue comes when we want to export the data. We can only export up to 100 members. And during the pilot this work. + +Robert Del Rey: Because all the submissions were less than 100 but since we went over this number already, I believe we would need to get at least the standard monthly plan so we can go up to 1,000 when we're exporting the data. like I said as soon as you upgrade. your profile is gonna be certified right away and we still gonna have a chance again to appear in the main page and also if any random person wants to search for a cash And they search for a cash. They will be able to find it since we are going to be certified. + +00:20:00 + +Robert Del Rey: So that is what I wanted to drop about that cash silly update. It's good. That funding hasn't been an issue with this. One thing that I was speaking with paint is we need to accept some missions and we need to get more people doing this Mission so we can get to the Depending number that we planned before starting this Mission. I guess that's a good problem to have. And since we also get some extra funding by Greg which we're gonna be super eternally grateful. I believe $200 for the next three month is gonna be $600. I think we can do it and we have to do it since it's gonna help us get in the data and it's gonna help us being highlighted in the main page. And yeah. Even though we are legit. + +Robert Del Rey: If a new random person find this and see us as unlisted in red like that, they're not gonna feel very confident about trying out a cash City. So yeah, I guess this is something that must be done at least for that three months of the real campaign. After we're done with the campaign, I don't know. What we're gonna do I was reading and we can cancel. anytime if is the annual plan which We're not gonna go with that one. So as soon as the three months and we can cancel that and then we can get to decide what we're gonna do after. + +Robert Del Rey: But yeah guys those are all my topics. We went over the missions review the feature missions with the events and the providers missions for next week. The Twitter spaces that's coming up next week the FAQs and the resources for the community members the city rolls and the silly updates. So that's all I had for you guys. Thank you for joining and those listening to the recording. Anything else you want to discuss before we wrap it up go ahead tie. + +Tyler Wright: Sorry, I'm looking for I know that you talked about the Twitter spaces. Is there a link that we can put a couple of places? So that's easier for people to access can we put something on Discord events? Do you have all that kind of stuff set up yet already or you just let me know when that's good to go and then just dropping the zealy channel and then we can just like Reddit wherever we need to spread it. + +Tyler Wright: You're on mute. + +Scott Hewitson: Yeah. + +Tyler Wright: I think yeah. + +Robert Del Rey: Yes, I was commuted. This mic work, it's harder today. I don't know… + +Scott Hewitson: It's Monday. + +Robert Del Rey: what happens. So guys. It's Monday. + +Tyler Wright: yeah, it's + +Robert Del Rey: It's Monday. It's + +Robert Del Rey: so as I was saying the space is set up already. But the guys haven't sent the spaces link as soon as I have the space link, I will share on this core on Telegram and maybe I can ping you so you can help me amplify it if you want to. All right. + +Tyler Wright: Yes. Yes, please I want to + +Robert Del Rey: Okay. Thank you guys Scott. + +Scott Hewitson: Yeah in regards to the Twitter spaces. it's awesome here. You're always plugging into other communities you're doing. I mean getting the word out as something you do. totally appreciate that. maybe one thing you can highlight while you're talking about them is just the mere fact that this program is a community program that was through the community like you did Pilots you did this and it's completely Community owned. It's kind of a cool story because it's from zero you can have resources to put up together a whole program and this is the prime example of that. Just the random,… + +Robert Del Rey: That's right, Good. + +Scott Hewitson: throw it out because our process is, we want people who are building or doing things the progress the network to get funding like ASAP and there's multiple Avenues to do so. + +Robert Del Rey: Yeah, man, absolutely. Sure sure that that's a great one, And I can feel your we say it because I love it I'm that example this came from zero We went from zero to Seeley this. + +Scott Hewitson: Yeah, you're the prime example. That's right. + +00:25:00 + +Robert Del Rey: So yeah, man, I love to talk more about that. You got it. + +Tyler Wright: Yes, please from zero to zealy. That's a quotable right there, + +Scott Hewitson: Yeah. + +Robert Del Rey: I just made that up. Thank you. So guys thats that for now anything else you want to cover? + +Scott Hewitson: yeah, one other thing on the Twitter spaces if you're doing planning on doing a giveaway or something, but you don't have the funds we can always do a 50 hundred dollar Bounty something like that similar to the spaces. You did a while ago. Those are offers that will always be able to do just with the community support funds so Please let me know if you need that. + +Robert Del Rey: I should wear I sure will my guys again. Thank you for your support. It's great working with you. Again. If you have any other feedback any other idea that might be fun to try making a mission out. Just let me know. We're working on some new missions. To unveil on the second month and Benji and I are super excited about how things are going. So if you want to still drop more wisdom as you have done in the past, please do it anytime anytime. + +Scott Hewitson: Love it. + +Robert Del Rey: So yeah, that's all for me. + +Robert Del Rey: for the deliverables Yes, I guess I'm gonna keep on working on the things we were working on last week. We are trying to refine the numbers. We want to come up with the stats determine exactly how many people don't this missions how many people done develop permissions how many people did content creator missions and hopefully we can have that number ready for next week, which is the last week of the first month of this campaign. and really nice. I mean I miss talk about how things are going again. + +Robert Del Rey: so yeah, that's all I have for this week guys. Thank you for coming for my standup. Anything else you want to cover. If not, there is the Sealy group on a cash Discord. There is also my DMs Del Rey and stuff finances. If you didn't catch this life they're recording is gonna be available on a cash get the Make sure you catch it over there and with that you next time wish you a wonderful week guys. Alright. + +Scott Hewitson: All right. Thanks Robert. really appreciate everything you're doing. + +Tyler Wright: Yes same. + +Robert Del Rey: Appreciate you guys. Bye my pleasure. + +Scott Hewitson: All right. + +Tyler Wright: + +Meeting ended after 00:28:07 👋 + + + + + + From cfa2665068cc911e81a6acf7bc001e5dee44c532 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 15 Apr 2024 03:34:31 +0000 Subject: [PATCH 036/138] Create meeting notes for wg-zealy #9 (#536) * Create meeting notes for wg-zealy #9 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 009-2024-02-12.md add transcript chore: add video recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-zealy/meetings/009-2024-02-12.md | 423 ++++++++++++++++++++++++++++ 1 file changed, 423 insertions(+) create mode 100644 wg-zealy/meetings/009-2024-02-12.md diff --git a/wg-zealy/meetings/009-2024-02-12.md b/wg-zealy/meetings/009-2024-02-12.md new file mode 100644 index 00000000..672ce068 --- /dev/null +++ b/wg-zealy/meetings/009-2024-02-12.md @@ -0,0 +1,423 @@ +# Akash Network - Zealy Working Group (WG) - Meeting #9 + +## Agenda +- Discusions on missions for Zealy developer onboarding initiative +- Discusions on Zealy on-chain proposal +## Meeting Details +- Date: Monday, February 12, 2024 +- Time: 6:00 AM PT (Pacific Time) +- [Recording]() +- [Transcript](#transcript) + +## Participants +- Benjamin B +- George Pro +- Robert Del Rey +- Tyler Wright + +## Meeting Notes +### Discussions +- Robert Del Rey introduces the meeting agenda, emphasizing the significance of the developer onboarding initiative and the proposal for Zealy. +- Robert mentions discussing the missions with Benjimin from the previous week and invites feedback. +- Tyler shares a success story about a contributor who came through Zealy and completed an Akash bounty, highlighting the impact of Zealy on the ecosystem. +- Robert expresses gratitude for the update and suggests incorporating Akash bounties into Zealy to broaden accessibility. + +### Missions for the developer onboarding initiative +#### Robert: +- Robert Del Rey discusses the missions for the developer onboarding initiative, divided into three-month periods. +### Month One Missions: +- Category: "Build on Akash" missions +- Mission: "Create a basic web app in Python and deploy it on Akash" +- Mission details: Divided into three parts - downloading necessary components, creating the environment, and testing/deploying the app. +- Reward structure: XP and AKT awarded upon completion of the final mission, contingent on the quality of work reviewed by the team. +- New campaign features include clearer instructions and consequences for copied or low-quality work. +#### Create an AI powered Akash Wiki +- Robert Del Rey introduces the next mission: "Create an AI powered Akash Wiki" to consolidate documentation about Akash, acknowledging its potential scope and expressing enthusiasm for its potential. +- Benjamin B shares insights on existing projects with similar AI capabilities but expresses concern about the mission's scope. + #### Create AI powered Akash images using SDLX connectors +- Robert Del Rey acknowledges Benjamin's point and moves on to the next mission: "Create AI powered Akash images using SDLX connectors," explaining it falls under the "Akash content missions" category, which aims to involve more participants. +- Robert outlines the reward structure for the Akash content missions, aiming for three to five winners per mission. +- Tyler shares insights about a team building a chatbot related to Akash, suggesting it might not need to be a mission but is worth noting. + +#### More Missions ( Month One ) +- Robert introduces the "Create short-style Akash videos" mission, inspired by a suggestion from the Telegram chat, and explains its requirements and reward structure. +- Robert Del Rey emphasizes the importance of high-quality submissions and mentions there will be more content missions in the following months. +- Robert Del Rey introduces the mission to provide GPU to the Akash Network, highlighting the need for assistance and proposing to drop questions in the providers chat. +- Robert discusses the potential rewards for providers and acknowledges the need to finalize details on AKT rewards. +- Benjamin B expresses concern about the mission's alignment with existing proposals incentivizing GPU providers. +- Tyler Wright provides insights into ongoing efforts to incentivize GPU providers, distinguishing between larger data centers and smaller providers targeted by Zealy. +- Tyler suggests keeping the mission for smaller providers on Zealy separate from the incentives geared towards larger data centers. +- Benjamin B agrees with Tyler's explanation and supports keeping the mission as proposed. +- Robert Del Rey appreciates the input and thanks the participants for their contributions. + +### Month two Zealy missions +- Robert Del Rey introduces the mission for month two: "Deploy a persistent storage solution," highlighting its importance for diversifying participants' experiences with Akash. +- Robert expresses uncertainty about how to structure the mission and plans to seek input from the providers' group on Discord. +- Tyler Wright seeks clarification on whether the mission is for deploying persistent storage as a service or using it as a deployer. +- After discussion, it's clarified that the mission is for providers to offer persistent storage on the network for one month, with potential auditing mechanisms to ensure compliance. +- nBenjamin B expresses confidence that providers won't attempt to abuse the system, suggesting that verification may not be necessary. +- Tyler shares past experiences with attempts to deceive systems, emphasizing the importance of vigilance. +- Robert Del Rey acknowledges the input and adjusts the mission description to "Provide persistent storage solution for one month. + +#### More Missions ( Month two ) +- Robert Del Rey introduces the mission from a previous hackathon: "Creating Frameworks for automated scaling and load balancing," acknowledging its potentially broad scope. +- Robert plans to discuss the mission further with Adam to gain clarity on its objectives. +- Benjamin B shares insights on the challenges of creating a solution for automated scaling and load balancing, highlighting the complexity involved. +- Tyler Wright suggests reframing the mission to focus on creating proof of concepts or integrations that address user experience gaps, making it more accessible for participants. +- Benjamin B and Robert Del Rey express agreement with the idea of allowing proof of concepts in missions to encourage participation and innovation. +- Robert Del Rey emphasizes the importance of enticing people to try out and build on Akash, agreeing with the approach of allowing proof of concepts. + +#### More Missions(Month two) +- Robert Del Rey discusses the mission for month two focused on creating a post about the Akash merch store, mentioning previous discussions with Benjamin B about its implementation. +- Benjamin B expresses concerns about insiders dominating the rewards for the mission, as they may already have Akash merch. +- Robert suggests making the mission a contest based on the best post receiving the most likes, potentially awarding the winner with a prize. +- Robert emphasizes the importance of the mission being about promoting Akash merch on social media rather than solely focusing on sales. +- Robert highlights the potential reach and visibility of social media posts about Akash merch. +- Robert acknowledges the complexity of the mission and the need for further feedback. +- Benjamin suggests allowing insiders to participate occasionally, as long as it doesn't become a recurring pattern. +- Robert agrees with Benjamin's point and moves on to the next topic due to time constraints. + +### Month Three Missions +- Robert Del Rey introduces the third category of missions, which are focused on featuring missions from other working groups to support their initiatives. +- For month one, the mission is "Become a provider on Akash Network," aimed at supporting the Providers Working Group. +- For month two, the mission is "Invite friends to join the Akash developer onboard Initiative Program," supporting the Zealy Working Group. +- Robert explains that the initial target number of invites was 10 but has been adjusted to three to five based on discussions with Benjamin B. +- Robert shares personal experiences with inviting people to similar initiatives and emphasizes the importance of setting realistic goals. +- Robert highlights the mechanics of the mission, where participants share a Zealy link with friends, and their invites are tracked to monitor their success. +- Robert expresses excitement about the mission and encourages participation to support the Zealy Working Group's efforts. + +#### More Missions (Three Missions ) +- Robert Del Rey discusses the mission for month three, which involves creating tools for vulnerability scanning and reporting, a track from the previous Akash hackathon. +- Tyler Wright expresses uncertainty about the necessity of such tools, suggesting that reporting tools may already exist. +- Robert seeks feedback on whether participants have seen or used tools for vulnerability scanning and reporting in Akash. +- Tyler suggests considering a mission focused on contributing to technical documentation, as documentation contributions are valuable and accessible to developers. +- Robert agrees with the suggestion and plans to create a mission related to technical documentation contributions. +- Robert introduces another mission for month three: creating an educational video about the history of cloud computing and Akash's role in the cloud compute market. +- Tyler proposes a mission to incentivize joining the Akash Insider program through Zealy, with rewards tied to specific contributions and participation. +- Benjamin raises concerns about incentivizing Insider program membership and suggests rewarding users for contributing to SIGs and working groups before applying for Insider status. +- Robert discusses the idea of incentivizing participation in the Insider program through XP rewards and creating a test mission to explore the concept further. +- Robert expresses enthusiasm for the upcoming missions and seeks feedback from the team on refining the approach. + +#### More Missions (Three Missions ) +- Robert Del Rey introduces the last mission for the day, pertaining to the events working group and attending real-life events like EthDenver. +- Benjamin suggests fast-tracking Zealy participants into the Insiders program to streamline the application process. +- Robert agrees with the idea of fast-tracking and emphasizes the importance of incentivizing participation. +- Robert outlines the purpose of the event mission, aiming to encourage content creation on social media. +- Robert concludes the discussion on the 15 missions for the campaign and encourages feedback. +- Benjamin suggests leaving room for flexibility in the proposal to accommodate changes in missions. +- Robert agrees and expresses willingness to consider adding or modifying missions in future campaigns. +- Robert emphasizes the goal of encouraging more people to build on Akash through the mission-based approach. + +### Final notes +- The goal is to submit the proposal on-chain by Friday, with flexibility in case of delays. +- Robert summarizes the discussion on the proposed missions for the three-month campaign on Zealy. +- He acknowledges receiving feedback and plans to address it promptly after the call. +- Participants are invited to share any final comments or questions before concluding the call. +- Robert expresses gratitude to the participants and encourages anyone with questions about the Akash developer onboarding initiative to reach out on Discord or via direct message to him. + +## Action Items +- Robert Del Rey to explore the possibility of fast-tracking zealy participants into the Insider program application process, coordinating with Adam +- Robert plans to seek input from the providers' group on Discord regarding how to structure the mission. +- Robert to discuss integrating Akash bounties into Zealy with Benjamin C +- Robert Del Rey to create a test mission for joining the Akash Insider program through Zealy, exploring the concept of incentivizing participation and gathering feedback from the team. +- Robert Del Rey to create a mission related to technical documentation contributions, as suggested by Tyler. +- The group to continue discussing and refining the approach to incentivizing participation in the Insider program through Zealy. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Robert Del Rey: Okay, and here we go your life. Thank you so much for that. So guys happy Monday. Welcome again to the city to the cash Sealy working group session. For these developer onboarding initiative, which is getting better and better by the day. today's agenda. It's short but powerful. Last week I was speaking with Benji. We went over the missions. We want to offer in these campaign. So today's again. It's basically about sharing with Those who are here now and those who listen the recording share with the missions were coming up. And maybe you can drop some feedbacks or initial box. + +Robert Del Rey: We're going to go on a high level through each Mission just Also, the second topic we get for this call is preparing the proposal to finally go on shame now. It's another big one. Which I'm super excited about and we're gonna share more details as this call progresses. So You can share your extreme. I don't know if you can share only the list of missions that is sent to you. + +Benjamin B: Wait, let me get that. + +Robert Del Rey: Sure, no rushman. + +Benjamin B: So the full message that from Rocky days ago + +Robert Del Rey: Yeah, yeah. That one for Friday, I believe the one that shows all the missions in this. Go ahead Tyler. + +Benjamin B: I just copied it here. And they should be able to see no. + +Robert Del Rey: yes. I'll see Thank you so much Tyler. I see your hand up. + +Tyler Wright: Yeah, just real quick. I did want to shout you all out real fast. So. + +Tyler Wright: Last week as a cost prepares for East Denver. There were a couple of bounties that went up online. There will be some more bounties that go up online for building sdls the way to specific East projects. One of those sdls was built in that Bounty was filled by somebody that came through the zealy program. They've been a contributor to the ecosystem and so they've received that down to so it's just great to see them come through zealy have success there and then stay in the community stay active respond to a bounty and they said that if we put more of those kind of down tease on zealy, they know other people would come it was just like building an sdl for a layer to eat a project, but I just want to shout out the workflow and obviously the work that you all done to bring that person into the Chica system. So just wanted to + +Tyler Wright: thank you all aware of that. I'll drop in this specific item here. + +Robert Del Rey: Wow, thank you so much Tyler. It was an aware of that. + +Benjamin B: Thank you for mentioning this. + +Robert Del Rey: Great news, that's great stuff, honestly. + +Robert Del Rey: Really really cool. I wrote down the Akash bounties. Maybe we can come up with some missions base of the cash bounties all over what you were saying, but that's amazing. So the person came from CB he saw their cash boundary. He did the Bounty and he turned the Bounty. That's really amazing. It's really amazing. Thank you again. let's do this. I will go ahead and read you the mission titles for this call for the recording. And after physical, I will go ahead and go over the counties and chat with Benjamin C. What can we bring to see because yeah, I cash is known to have these bounties for everybody, but maybe + +Robert Del Rey: Not everybody can find these polities. So maybe having them on Sealy will help everybody to get more bountystone, which it's gonna be amazing. You may just one second guys before I get start. + +00:05:00 + +Robert Del Rey: All right guys, okay, so I guess I'm writing now. So let's see on the screen. First of all the missions we're gonna go. For three months and we're gonna come up with a series of missions depending on the month. So first, we're going to see the missions for month one again. I was just really the Mission Title so it can be in the recording then if you have any special comment or feedback or question three feet less like question. So here I go the first mission. We got the category build on a cache missions. And we have here create a basic web app in Python and deployed on a cache. This is the first example that we did a while ago. This mission is dividing three. + +Robert Del Rey: So in the first mission people will download what they need in the second mission. They will create the environment more stuff that they need and on the last mission. They're gonna test the app and run the app. So when they do that, they're gonna submit that and after reviewing. They might get their Rewards. + +Robert Del Rey: so before move to the next one since this mission is divided in three. You will see. That mission one and two doesn't give you any XP or doesn't give you any akt, but the last mission of the series will give you the XP and we'll also tell you how much 80 you will earn. After you do the mission and it's not that people will do the mission and they will claim the reward right away on Mission 3 there. They are gonna submit their build and after we review the bill then we're gonna decide They earned the reward based on the quality of the job. + +Robert Del Rey: Things that we added in these new campaign are more instructions. It's more clear now if they do copied work if they do low quality work. We want to set those Solutions. so well moving on to the next one. It's create an AI power at Cash Wiki to find all the information in the patient about a cash. This one is not ready on Steely yet, but it's just a mission idea. We believe it's really fun. And if one person can come up with that, it's gonna be really neat, honestly. I repeat the title again create an AI power a cache Wiki to find all the info and documentation about a cash imagine something like I don't know. How do I spin up a validator? You can write that and you can get information you're looking for that will be really nice if someone can do that. + +Robert Del Rey: Go ahead then. Yes. See your hand, man. + +Benjamin B: I believe there are at least two projects that have done some sort of AI air Chef Pops that have the knowledge of the Akash documentation. And basically does this but besides this I think it's a very large scope for Mission. I'm not sure if we were to like it. + +Robert Del Rey: guidance + +Robert Del Rey: Yeah, it could be too big Maybe. Let's see. I don't know. to the next mission then I create AI power a cache images using sdlx disconnects different. This missions are not on the build on a crash category. They are on the Akash content mission. And something we wanted to do in this next phase is bring more kinds of missions. So more people can get involved. in this missions It's not that everybody's gonna win. It's not that you're gonna create the image. You're gonna submit that and you're gonna win. + +Robert Del Rey: We are going to review those missions. And we're gonna have a minimum of Three to five winners. That is what Benjamin I spoke about last week. now after we're done with this face and we still got budget to have two more winners. We can consider and do that depending on the submissions. But at the moment these create a cash content missions, we plan to have from three to five winners at the moment. + +00:10:00 + +Robert Del Rey: yeah, what are we seeing in the screen Sorry Ben that wasn't watching the phone. + +Benjamin B: Yeah, Tyler said something in the shot and I felt like I had to try it out while you were talking about the missions. + +Benjamin B: So from the looks of it, it's a shot where you can get instructions on how to do things on a college if you ask the correct questions, and I'm trying to see how good this will be Taylor has something more to advise. I see that's your handless race. + +Robert Del Rey: Yeah. + +Tyler Wright: Yes, I just meant to drop that in the chat. That's something that a team is building. There'll eat them for as well. But to your discussion about chat. I know that they can be very involved. I know that piercing the team that worked on the website revamp hotel for work on the chatbot. So, I don't know if necessary that should be a mission to Benjamin's point, but I just want to share this one. I follow up and share what some people are building and people can test already. + +Robert Del Rey: Thanks, That's pretty nice. I really wasn't worth this. Excuse me. + +Robert Del Rey: Okay, let's move on there. + +Robert Del Rey: So in the Creator cache in their cash content missions as I was saying we're trying to get the best content we can. And also things that people have asked in the channels for example this one. It's create short style my cash videos. This one I got it from the telegram chat. Someone actually dropped that suggestion a few months ago. we should have people creating shorts a style videos about what is a cash. What can you do on a cash and I believe to get started the first one it's gonna be A shortest style. What is a cash video make I don't know. But if you can go to the Sealy now and show this Mission so people can see in the recording how they look like. + +Robert Del Rey: There you go. The second one. Exactly. So you see this one XP has akt price. It's not that all the people that participate are gonna win. as I was saying we have + +Robert Del Rey: as I was saying we have avoided for five winners if they have really really good Solutions if there are less submissions than that, we do less prices. Now if we get big amount of submissions we can consider where we do about that. So as you can see the videos emission you have some requirements just to make sure this is valid about it's a mission. You have that the video has to be shared in a social media platform has to be public. You have to share the link to the video. You see below also be creative low quality work or copy work will not be accepted. It is qualified right away. So, let's see how that goes. + +Robert Del Rey: But yeah, this create a cache videos. This one is for the first month. We got some more create content missions. We're gonna go over them in the next month, which is gonna happen shortly now. The last mission I want to share with you about the month one. It's gonna provide GPU to a cash Network. And we need help in this. It's not that we need help. But we got the questions. So we're gonna drop the question here in case somebody wants to shine in but we also want to drop the question in the providers chat. In the question was a moment. + +Robert Del Rey: I was confused. we a question was about deploying persistent storage. We're gonna go to that one in a second. So going back to the provide GPU to a cash Network that mission. Yeah, let's see if we can you guys have a cache are trying to bring more providers to the network. You are incentivizing provide There is a proposal. I believe in class already or providers incentives. So I feel one good mission was + +00:15:00 + +Robert Del Rey: trying to bring providers to provide debut to a cash Network and we got some requirements 99% of time and other requirements and maybe if they jump into this score, sorry if they jump into silly and they do this Mission as a provider. They can turn off you extra more AKP at the moment. I don't have the price number. maybe when did you can go to Sealy and open up? Mission to see how much it was the price. I haven't added it yet. as you can see you will find that the missions in the rewards section. They're gonna show XP and they're gonna show akt so it's a working progress. So this one should show the XP and should show the + +Robert Del Rey: AKP I don't know how many akt we should give out for this but you can see Let me know if maybe we are missing some other requirements to make this Mission successful. + +Robert Del Rey: I've become a provider on the Akash Network. You have to score a minimum of 95% of time for one full month. There is a guy on how to become a provider which we have to attach here in the description. But yeah, that's about it. Maybe you can have some box. You can drop them now or maybe you Benjamin not seen the participants screen now. + +Tyler Wright: But I think Benjamin has his hand up. Go ahead Benjamin. + +Benjamin B: yeah, I wanted to say I'm not sure What's the progress is on this proposal but there is something related to incentivizing GPU providers already, so I'm not quite sure if we should do this missions like this Mission the only being related to the provider or if we should do it for the GPU because if we + +Robert Del Rey: Okay. + +Tyler Wright: Hundred h100 some of the higher-end perfect. You see on the screen RTX a6000 and basically these are commitments that overclock Labs team and other folks from the community are managing where we're looking to bring on Commit. It's a committed pool So for data centers that are usually tier three getting them to come on for a month and giving them a bunch of incentives is not good enough because it takes them a while to get online. they have additional metrics for how they do business go for these folks. We started off with a one-year commitment. and so this is for a data centers that have again multiple gpus I think from a zealy challenge perspective if anybody has Forty nineties or up? + +Tyler Wright: Or even a 40s that are on that they want to bring on to the network and quantities less than 10, small quantities that I think we could take some funds to incentivize those folks because that they're the first part of this committed pool is it's again for large larger quantities of gpus go ahead Benjamin. + +Benjamin B: Are you referring to using the Bounty proof for that or already referring to using the rewards pool? Because for what you're saying it still makes sense to have this Mission regardless if we have a GPU or if you only have the provider aspect of it. + +Tyler Wright: Yeah, So what I'm saying is I think we should keep this Mission because the current incentive pool is geared more towards data center right now and I feel like this zealy audience is going to be more smaller providers. And so the incentives on zealy would still apply to them where they wouldn't apply necessarily for this first stage phase one of this. incentives program + +00:20:00 + +Robert Del Rey: It's similar to… + +Benjamin B: heroids + +Robert Del Rey: what they were saying bendy not make it we're looking for dpu providers, but make it more General. So everybody can try it out and become a provided on my cash, but they don't necessarily have the heavy equipment like you were saying Tyler which is what this proposal is aiming for bigger heavy players, right + +Benjamin B: Yeah, I… + +Tyler Wright: Yes, exactly. + +Benjamin B: It after you explained everything Tyler. + +Robert Del Rey: Yeah, yeah. + +Benjamin B: I think it makes perfect sense to keep it as is. + +Robert Del Rey: Thanks, Thank you for your input. So while moving on then let's go to month. Number two. Again, thank you for the feedback guys. And for month number two here. We have the deploya persistent storage solution that Nation we don't have it on seal yet. It's just the tire idea. But I believe this one is similar to becoming a provider on a cache we want different people to try different aspects of a cache and I believe if we have people deploying persistent storage solution. It's gonna be good. Even if it's just on a smaller scale or just like a general. + +Robert Del Rey: Storage solution. So yeah, these is the one that I was mentioning earlier. I really don't have any idea how to put it on a mission. I will just go to the providers group and write something like how would you add this to see me? How would you make these a mission? I don't know how to go about this one. It's all I'm trying to say but basically the mission is that have people deploying a persistent storage solution. Maybe they can have that running for one month. and yeah, that's basically the mission. You have any thoughts of questions about it now, it's the best time to discuss it. + +Robert Del Rey: If not, that's okay again, I will drop that question in the chat on Discord to see what those guys have to say. But I believe it would be like a fun mission to have and this is for month to so it + +Tyler Wright: Sorry Robert. Is this Mission specifically for a deployer that needs to use persistent storage or a provider that's going to provide consistent storage + +Robert Del Rey: That's a great question, I mean if it's gonna be for the Providing the persistence storage solution not someone using the storage solution. Does that make sense that? + +Tyler Wright: Yes. I think from that perspective. You could just say provide persistent storage on the network for one month in a provider It could be a CPU provider and I believe that we'll be able to use either. Some sort of auditing mechanism, even if it's manual to make sure that they're running persistent storage over that month. I don't know if you have to get anything else from the providers we can just be like, all right, are they running persistent storage be when they provider gets brought on WE audited it manually if it has persistent storage cool, then they're past phase one. We can check it at the five day Mark to 10 day Mark, and eventually when Benjamin and his brother and their team are done they have automated tool right now. We might just have to do it manually. But yeah, I think that's how we can move forward. Go ahead. + +Benjamin B: I think no one tries to abuse it I think we don't even have to verify it because I believe there goes a lot into trying to fake it more than just actually having it. So if a provider has it you can easily where that data. + +Tyler Wright: Yeah, exactly. I will say and… + +Robert Del Rey: awesome + +Tyler Wright: I'll just put this on the record just from multiple test Nets and multiple other endeavors. You'll be surprised what people try to do, and the lengths I'll go the fake is sometimes I just like it would have been easier to probably do the work successfully, but I digress + +Robert Del Rey: I can't imagine man, honestly. + +Benjamin B: Yeah, if someone can fake it, I think we should give the rewards. + +Robert Del Rey: All Thanks for the input And I changed the word in a bit instead of It's provide persistent storage solution for one month. Thanks guys, the other mission on build on a cash this one we got it from the previous hackathon. I believe nobody please this one and that's why I wanted to bring it up on Sealy. It might be too broad. Thank you said in the other Mission. here we goes. It's about creating Frameworks for automated skating and low balancing. I can tell you the name, but honestly, I don't know what looks like. But it was a track in the hackathon. Maybe I could speak with Adam. Maybe he didn't tell me. + +00:25:00 + +Robert Del Rey: The idea he had on mine when he came up with this truck. But yeah, that's the mission again. Yeah, the missions might be like two brother to be but honestly when I had a mind is like We already did the pilot. We got some simple Nations to do people did the missions. I guess we should go ahead and go level two or level three and making missions more challenging harder for them. s Another thing is that we want people to do the missions, so I don't know. What would be like the meat point in that. Maybe you got the answer being. Yes. your hand up man. Come on in. + +Benjamin B: Yeah, I wanted to speak on the creating Frameworks for automated scaling and the load balancing. and I might even have been a part of creating that track but afterwards I didn't really like it because to create a good solution for this It's quite a large task to create something that works for your personal uses. It doesn't have to be super large but A lot goes into especially the balancing part of it. So how do you want to keep it load balanced? How do you want to make sure that everything is running apps by default don't have something to show for that the automated scaling + +Benjamin B: and if a provider were to go down. Sure you can probably create some sort of General solution. But if you for example host validator and then this part goes wrong and you create a new instance your provider would get if you didn't do it correctly. There please. Go ahead. + +Tyler Wright: Sorry I didn't want to cut you off as you're talking. I guess the best way I could describe is hold in the experience for people that are trying to find things like Alternatives AWS. I believe that should be a mission. if we can have missions that are all right, if somebody's used to a load balance or another tool, but it's very kind of primitive on Akash can we have somebody a build a proof of concept or build an integration that uses some tooling? that could be phase one of a load balancer that folks can use on Akash that's easier to use or easier to integrate. + +Tyler Wright: If we can have some of those stretch missions that maybe you're not even a solution but a proof of concept, then we can get people into the ecosystem that we're like, this is a cool team that's building something and then they could find other ways to incentivize whether it be like the community pool or sick and working groups or many Grant, so again, Benjamin was talking about having user experience, flaws and in the current class product, it'd be great. If you can think about some of those things Benjamin and Robert as mission to try to entice people into the ecosystem. + +Benjamin B: This part that were proof of concepts are allowed. I think that's perfect because Solutions don't have to be perfect even in hackathons. It doesn't have to be production already for it to win prices most of the time. I was thinking yeah, and we want everything to be good. But the proof of Concepts idea is great. + +Robert Del Rey: Yeah, honestly, and you still and just to get people into a cash and get people to try out I guess and get people to real on a cash. so yeah, let's Let's see how that goes. Thanks better moving on the missions for months, too. We got the content missions for this month. Are a bit different you more one is about creating a post about their cash merger store. we spoke a little about that one and bendy. What did we say on Friday about this one should be only for the Insiders to do it. I don't remember where we got into. with this mission the posting about the cash commercial store. You can refresh my mind a little. + +00:30:00 + +Benjamin B: Yeah. Yeah, I talked about this one a little because + +Benjamin B: I think this one. Most people don't really have a coach merch that Tyler just went away. + +Robert Del Rey: Mm-hmm + +Benjamin B: He said the right back and the left. So if we're talking now,… + +Robert Del Rey: Okay. + +Benjamin B: we're just going to say the same things as we did. but anyways The idea here is that some insiders cut a coach merch for free some insiders attending IRL events and get merged for free but normally users in the community. Don't get it. Some people were against if insiders were a big portion of the ones claiming rewards because they're already involved. And we want to onboard new users. So I'm not quite sure how we should feel about this one. + +Robert Del Rey: Thanks, Yeah, I remember now. Thanks for the contents. and you're right, I mean if people see that five six insiders are winning prices, they're gonna Think something's up. But it's okay. I guess how we should go about this mission. first we should make it a contest so the best of all wins the one with more likes it with wings. Yes. Maybe they can have a pot that use that for them. But you got people in the competition. + +Robert Del Rey: I don't know it can get complicated honestly. Yes, we want people to use their cash commercial store. Yes, we're gonna have new designs. how I was ambition in this mission was something like getting people to post on social media rather than having them buying things from the merch store. So maybe we can think a bit more about this mission. But normal community members participate. I don't care if we give them the teacher for free. Of course. We want them to buy the T-shirt, but I don't care. They go with this mission in particular is about having people posting about a cash merge on social media, that can be powerful. + +Robert Del Rey: Yeah, yeah, even if there's five to ten people participate. if then five get three retweets each that's 15. Accounts reach if you know what I mean. + +Robert Del Rey: So yeah, that's more people that can see more about a cashmere and see more about a cash. But yeah, this is just like an idea Again, it can get complicated. So we still left it here because we're going to hear more feedbacks. I don't know Tler. If you have your hand up, maybe you can shame me. I see your head up, baby. Refer to jump into the station man again. + +Benjamin B: I have it up. Yeah. + +Robert Del Rey: I'm just seeing the screen. So I don't see you from my phone. Sorry about that. + +Benjamin B: Yeah, I want to say here that I think maybe we shouldn't have it just and I think this Mission and some of it will go to inside these years because they are the ones who usually have a coach merch right now, some people are against it. But as long as it's not reoccurring super often and they're just 10 minutes in the morning doing a mission and then they can do that every week as long as it's not like that. I think it's fine. + +Robert Del Rey: Mm- Okay, not that makes sense All right moving on because time is taking Benjamin's taking. + +00:35:00 + +Robert Del Rey: Okay, the working group Mission we have for this month and for context Tyler and so it can be in the reporting. We're gonna have three categories for the Nations. That way it's gonna be easier for us to come up with missions. The three categories are built on a cache. Which our missions that people build things on a cache or deploy your stuff on a cache or create a stuff on a cache? + +Robert Del Rey: The second category is a cash content missions and those missions are about creating content about It can be content that they post on social media due to from Discord, but different color for those missions. We create AI power images for the month. We create AI power a cash videos or logos using sdxl. We're gonna see those submissions and the best of those are gonna win prices. Now, the third category is featured Mission or a cash working group Mission. And the reason for this one is the things that other working groups are doing and try to come up with City missions that can help. + +Robert Del Rey: those working groups for example the first month They become a provider like cash Network the working group. We're trying to help it's the providers working group. for the month number two The mission is about Seeley is the working group for the month and the mission is invite reference to join the cash developer on board Initiative Program. I haven't brought that mission down yet, but that's the title invite three to five friends to join the peace developer initiative on silly. Let's see how it goes. The initial number was 10, but after speaking with bendy with lower it down to three to five and let's see how it goes. + +Robert Del Rey: From personal experience. I've tried to invite 10 people to something with the related before and I haven't got any success. The only time I did it was actually because I only needed to invite three people. And that's the reason why I did it that only time. So, let's see how it goes. The mission is in by three to five friends to join their cash on boarding program on Sealy. I'm excited about that. let's see how that goes. And yeah, you can create a mission that people get a costly and they can share that link with a friend. And if that person joins silly we will be able to see. where that person came from so if Tyler invites reference to Seeley, I will be able to see their friends Tyler invited and how many of them + +Robert Del Rey: so I guess it could be fun to try. And that's the mission for month three. + +Robert Del Rey: four month three They built on a cash Discord. It's gonna be sorry guys. I don't know. I'm seeing kind of blurry now. I haven't used my glasses in the whole weekend. Give me one second. Let me get my glasses guys. I can't read. + +Robert Del Rey: I feel Okay, I have been on. It's way better. I usually just use them if I want to see something from afar. I don't need them to see things that are close to me. but sometimes my vision gets blurry right So the mission for month three moving on it's another Akash. I got on Mission. It's about creating tools for vulnerability scanning and Reporting creative tools for vulnerability scanning and Reporting. That's another mission. We had in the cash hackathon. I don't remember if we got a submission for that. + +00:40:00 + +Robert Del Rey: Maybe we have things like that in a cash already. I don't know you tell me guys. Have you seen this before either or Benji tools for their ability scanning and Reporting? + +Tyler Wright: I think there's reporting tools to be honest. I don't know how important this necessarily is. I love the idea of that third category of things that service like cigs and working groups. I would say one thing to add is a potential Mission would be something around technical documentation. I know a lot of developers quote unquote seem like they're better at writing documentation than they are actually developing code, but all contributions are welcome, so it'd be great to have Something that's lower barrier of entry on the developer side for folks that want to conribute. Sig documentation or anything like that. So just + +Robert Del Rey: Thanks, man. + +Robert Del Rey: Okay. + +Robert Del Rey: All right, so moving on. We have the last content mission for month. Three. This one is gonna be really cool. Maybe Tyler you can see the title from here. Maybe when you can highlight it also. But it's about create an educational video about the history of cloud computing in a cache roll in the cloud compute Market. That's a big mission that I see it's about creating content, but it's not like many submissions. Yes. We want to have as many submissions as we can. But we really want to get Best of the Best. + +Robert Del Rey: so I don't know maybe this video can be used later in the future for a cash edu. Maybe it can be used to share it on our social medias. How I see it is a 10 to 20 minute video like a documentary. So people can have the history of computing because not many people know about computer honestly now. Besides that also adding a cash Place In This Cloud Computing history. Go ahead Tyler. + +Tyler Wright: I think that's a great Mission. I was just wondering and I just brainstorming out loud. I wonder if it can make it a mission to join the Akash Insider program and be an Insider for two months, and if you do that to be a zealy then you can earn a certain amount of akt. I know it's like most people that are in the entire program don't necessarily or an akt but I think we're trying to certainly find more technical insiders. And so, if we find anybody through zealy it might be a cool mission to do that is fun to throw that out there. + +Robert Del Rey: Thanks, Yeah, I can do that. I can create a mission become an Insider and the requirements we can have things like amount of months. We want them to be in the program two months like you say and another requirement that I can think right now. It's do at least one Bounty while you are an Insider or one contribution to a passion Network just to give an example, but is that something related to what you're saying, right? + +Tyler Wright: That'd be perfect. I'm not doing inside. this out. because you get looking see for this potentially. + +Robert Del Rey: I can create a destination in short to you and I can also share it in the office hours this week. No problem with that. Thank you. But… + +Benjamin B: Yeah, I want to say something perfect. + +Robert Del Rey: but Sorry to Interruption. And the last thing I wanted to say is that the missions are not targeted to current insiders. It's to people that we won them to become inside. There's and then after they become inside their state do things inside the program and earn some akt after they are in the program. That's what I wanted to say. Sorry. Now you can go ahead and you say about them. + +Benjamin B: Also a mowers and I want to say that simply incentivizing the Insiders program and entering it and it could lead to spam users. I think we have a lot of insiders doing nothing already. I think if we could create a user password, they start in six and working groups and complete about this and everything like that if they can start there and then apply I think we should be reward those users definitely, but I don't think just because they become an Insider we should let them get Rewards. + +00:45:00 + +Robert Del Rey: That's a great observation And maybe we can switch the order. Instead of incentivizing them to become an Insider to earn the price Maybe. We can wait until the end of the campaign. and the people that did the most missions and want the most money we can offer them to become an Insider right away without going to the interview. And that can be the price that's something else I can think right now, but I totally feel you when you say things like if we incentivize them just to join. We're gonna have lots of experiment. Yeah, I do believe we have a decent number of insiders now. + +Robert Del Rey: So maybe this can be part of the prices. Maybe we can out to people that worry me. We are starting the silly campaign again. And now people who do 1,000 XP can get to the Insiders if they want to for example. That's one way we can put it. But yeah, I guess we should avoid incentivizing people to join inside this programming. We're gonna give you some prices. I know that is not what we said but it could be interpreted that way. right + +Tyler Wright: Down I hear what you always saying. No argument. I'm not going to die in a hill actually argument. I'm to argue Counterpoint would be I get what you're saying about spam. But all that would do is they would span themselves into the inside or application. They would not get automatic acceptance. I would still have to go through. the onboarding process and to your point about + +Tyler Wright: to your point about insiders I do understand exactly what you're saying. my hope is that by having these folks that come through zealy. So they're already have the chops that want to be more developer focused because they come through that platform and then they contribute I love the idea of earning a certain amount of XP points like a thousand so that people that join The Insider program or involved a fair amount about the network, but I feel like we can still get people to get to the application process if they go through that application process, which is a manual process and pasta interview, then they're in and they've still have to contribute over a period of time to potentially earn those rewards so there is a clear path, but again, Not until I'm not willing to die on so just wanted to put it out. + +Robert Del Rey: What I will do is that I can create two test missions so we can have the two points of view One mission to pay you want to be an Insider. You can apply to the inside decision this link and we can make that a mission and another mission to we just + +Robert Del Rey: yeah. I mean, it's gonna be only one Mission I had to become Insider. That's it. Yeah. I was sure a test mission with you so you can see it and maybe we can go from there but I believe It's worth it if we can explore how we put it. Because people are already involved into ceilings and you see this mission to become an Insider. Yeah, why wouldn't you try it out and try to become an Insider in case they decide to apply like you say Tyler they will go to the Insiders form and then go to the process of interview. and so if we get that expand it's gonna be good a span in the sense that we're gonna get traffic out of Sealy. I believe that's the main point you want to get across, right? + +Robert Del Rey: So Yeah, I will work on a test mission and Venture with you. and with everybody But yeah, I'm super done. What? And yeah, that was all I guess. one second Benjamin before you go before you go I have the last mission now. + +Benjamin B: Yeah, I have one more thing on this. problem first. + +Robert Del Rey: Yeah, I just wanted to confirm because I have the notification that you and someone else asked the handbook. But now as it's you and Tyler, Okay, no worries Go ahead and I thought it was thought someone else. + +00:50:00 + +Benjamin B: Yeah, you were talking about tensionally having the price beat that they become an Insider. I think we can try to speak with Adam if we can not do that. But instead of that we can have so we can try to Fast Track them into the Insiders program. So if someone from Siri is active on silly. Plus they apply through Sealy. I think that we should Push that interview before other ones so they can skip the queue. + +Robert Del Rey: Love it. Yeah, of course, right? Why not and like you say, they're gonna be earning XP and stuff. So it's gonna be easier for us to determine hey, yeah, this person deserves a class track into the application. If it's gonna be a proof or not that it's gonna go down to Adam. But yeah, I guess having Fast Track in the process gonna be good because yeah, I mean many people are always applying to the inside there's so maybe we can play through insiders now and Adam gets back to you in two months in one month depending on how many applications we have. So I guess fast tracking you in case you want to be inside there. It's gonna be great. Thank you so much Mike. the last mission I have for the day. It's + +Robert Del Rey: it's for the events working group. And this one is about attending and in real life event. The example I did was eat Denver because it's the one that is coming up. The closest I guess but it can be an event and basically is X y c event and take a picture with the cash team at the event. That picture the guys need to share it on Tag a cash and use the hashtag super cloud again. This is a mission to make people create content and have it on social media. + +Robert Del Rey: We don't have to price all the participants, but maybe we can. Give prices to the top three submissions or to of the best submissions. That's the last mission and Yeah with that. I close the 15 Missions at the moment that we have to this campaign. If you have any thoughts or feedbacks now, it's a good time for them then or Tyler + +Robert Del Rey: Okay, thumbs down I will take that as no feedbacks and know that this is about mission right? I'm just kidding. so yeah, that's it. I will go ahead and go over the feedback. You gave me guys will analyze then you do and I will analyze together what missions will be too Brock to do them. And what missions are worth to have if people can come up with a good proof of concept I started was saying because at the end of the day, we don't want to + +Robert Del Rey: Up, the next 10 million dollar application, but we want to have more people deciding to build on a cash and saying hey, I believe this is something that I can do. Let me do it even though it's ugly. Let me do it on a cache because they have this Mission really. So let me do this. that's how I believe people think when they see these nations. Go ahead Benjamin. + +Benjamin B: Yeah, I just want to say that when we update the proposal in another way and we add this Mission so that people can read it. I think that we should also include that these are the ideas that we have but we should leave it open in case we want to change it because some missions down the road maybe we decide yeah, this is a bad one or we can have a better one. But we… + +Robert Del Rey: Mm-hmm + +Benjamin B: but we will list the 15 ones as examples that will likely make the cuts. + +Robert Del Rey: God and yes, I also believe we should add them all. And also maybe we're not adding them now, but that doesn't mean we won't add them in another campaign in the future, right because I'm not planning on stopping this and I know you're not neither Benji. So yeah, maybe those missions that right now we are disregarding. Maybe those will be the highlight missions on the next months of these. Who knows right only the future will tell. But yeah, that's all I got for today about the proposal going on Shane. We are preparing for that Tyler. + +Robert Del Rey: And those listening to the recording the goal we have is submitting The Proposal on chain for this Friday. That's the goal we have but if things happen that prevent us of doing that we want to meet the proposal on Shane if we're not ready yet, but that's the goal we have for this week. And yeah, yeah, that's all for this call guys. It was the initials we're gonna offer for the three months campaign of the Sealy. We went over the titles. We spoke a little of some of them. We got some good feedback, which I'm gonna address right now in the next 30 minutes after this call. And the proposal going on Shane when we are ready. + +00:55:00 + +Robert Del Rey: So with that being said guys, do you have any last comment you want to share or anything before we wrap this column? + +Robert Del Rey: All right, I will take that as I know and with that being said, thank you guys for joining and thank you for those listening to the recording. If you have any questions about the cash developer on board initiative on silly you can go to a cash this course see this Channel and rub your questions there or you can send me at the end to Robert Del Rey if you want to With that being said guys. Thank you again for joining and See you when I see you. Okay? + +Benjamin B: Thank everyone for today. I will. + +Robert Del Rey: Thank you Tyler also. + +Benjamin B: Try to + +Tyler Wright: Thank you. Let me know. + +Meeting ended after 00:56:52 👋 + From e663c633e0c44771729f4d3213a8d2f9a1cc5474 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 15 Apr 2024 12:56:13 +0000 Subject: [PATCH 037/138] Create meeting notes for sig-design #14 (#535) * Create meeting notes for sig-design #14 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 014-2024-02-21.md added transcript for meeting chore: add recording Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-design/meetings/014-2024-02-21.md | 182 ++++++++++++++++++++++++++ 1 file changed, 182 insertions(+) create mode 100644 sig-design/meetings/014-2024-02-21.md diff --git a/sig-design/meetings/014-2024-02-21.md b/sig-design/meetings/014-2024-02-21.md new file mode 100644 index 00000000..e17e94e8 --- /dev/null +++ b/sig-design/meetings/014-2024-02-21.md @@ -0,0 +1,182 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #14 + +## Agenda +- Open discussion on design-related topics +- Presentation and discussion of planned issues +- Support for ongoing projects (product and website) +- Retrospective on past initiatives + +## Meeting details +- Date: Wednesday, February 21, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording]() +- [Transcript](#transcript) + +## Participants +- B S +- Deathless +- Denis Lelic +- Joao Luna +- Tyler Wright +- Zach Horn +- Ларец Иркутский + +## Meeting Notes +### Denis Lelic: +#### Template Section: +- Proposal for a dedicated area on the templates page to recommend trending or notable templates. +- Suggested featuring four tiles for highlighting templates, including new language models. +- In progress: Creating related issues, some requiring additional design work or detailed descriptions. +#### Website Development: +- Collaboration with Tyler and Zach on ongoing issues. +- Retrospective: Reflecting on past efforts, noting a website revamp project initiated about six months ago. +- Goal: To increase attention and progress on existing projects through issue tracking. +- Creation of detailed issues for product and website improvements. +#### Future Projects: +- Designing a credit card payments flow for Cloudmos a cake console. +- Planning a Marketplace for templates, discussed with Cloudmos representatives. +- Marketplace functionality to allow template publishing and purchasing, including user profiles. +- Implementation of Marketplace for templates and credit card payments flow design. +#### Website development: +- Working on a page combining development and community. +- Plans overlapping, reminiscent of the "get started" page. +#### Swag/Merch for Akash Network: +- Denis to DM Robert separately for input. +- Tyler and Denis discussed inviting Robert to create mockups. +- Peter and Greg also involved in swag design. +#### Video Content: +- Limited time for video content creation acknowledged. +- Denis suggests expanding on AKashEdu content with more videos. +- Zach willing to assist, looking for community members with video skills. +- Possibility of collaborating with a professional interested in motion design. +- Denis offers support to any community member willing to contribute to design efforts. +- Event-related design work completed in the past weeks (booth designs, t-shirts, hoodies, etc.). +- Denis encourages Luna to reach out for any design-related needs. + +### Website Enhancement: +- Zach raised an issue regarding the current website layout, specifically highlighting the providers' page and its potential improvement. +- Proposal to combine and elevate the visibility of provider-related information currently dispersed across different pages. +- Denis agrees with the suggestion, emphasizing the need to revisit and improve existing pages for better user experience. +- Denis commits to reviewing the issue raised by Zach and providing support. +- Discussion on showcasing provider information on the homepage for better visibility and accessibility. +- Agreement on the importance of front-and-center placement for provider information due to its relevance to visitors. +- Plans to coordinate further discussion and action on the issue, aiming for a shorter path to access provider information. +- Agreement to discuss the issue further and coordinate actions in the coming days. + +### Other Matters Discussed +- Denis encourages participants to reach out for any design-related assistance or queries, either directly or through the Sig Design channel. +- Joao Luna commits to dedicating more resources to graphic design within their team, aiming to support both their platform and Akash. +- Denis suggests utilizing a framework for communication and issue tracking, recommending sharing updates in the Sig Design channel or creating issues in the website repository. +- Denis concludes the meeting, thanking participants for their contributions and inviting further discussions offline or in future meetings. +- Zach and Joao express gratitude and bid farewell to the group. +## Action Items +- Denis to create detailed issues for product and website next month +- Denis to support Tyler and Zach with website repo tasks +- Tyler and Zach to review and provide feedback on proposed projects +- Denis to initiate design and spec work for credit card payments flow and Marketplace for Cloudmos +- Denis to DM Robert separately regarding swag/merchandise plans for AKASH Network +- Denis and Zach to explore the possibility of creating more video tutorials for AKashEdu, aiming for mainstream platforms like YouTube. +- Zach and Denis to review the current website structure and propose adjustments to streamline access to provider-related information. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Denis Lelic: Hey everybody, and welcome to today's Sig design meeting. A couple of things I have planned for today basically like an overall discussion. I always try to keep this meetings open for anyone to either contribute ideas and just to have open discussion about any design related topic. I have a couple of things on agenda today. + +Denis Lelic: Maybe I'll just start product so I'll shared here in this comment chat section. I have a bunch of notes and issues. I have created in the past and I started creating issues today. This is the first one for help me out loud. So the first one talks about template section. So my suggestion is to have one dedicated area at the for a templates page where we could recommend some of the templates. So for example + +Denis Lelic: If a new language model comes out we can highlight it there. So we would have maybe four tiles where we basically highlight. Anything that's trending at the moment or anything that seems like it's good to highlight at a specific point of time. So that's the first one and I have a list of them but some of them. Just require more To either design or just to write the whole description of an issue and explain the solution and so on but that's on my agenda for probably next month just to create a bunch of issues for product and a thing goes for the website. I know Tyler and Zach were already active there. + +Denis Lelic: in the Website repo but I'm planning to either support Tyler or Zach or with their issues and I'm going to create my own as well just to have a small retrospective. + +Denis Lelic: We basically started this Something similar with the website a couple of months ago and the last year actually so it's more than a couple of months ago. Let's say six months ago. where we created a bunch of issues and then bearish came along and we kind of have a website revamp project that happened after that. So I'm hoping if the issues pile up we're gonna bring more attention to either a specific project and + +Denis Lelic: Here here and see some. progress + +Denis Lelic: in each of these projects we're currently working on. So one thing for product related just to give you a hint. + +Denis Lelic: I'd like to design a credit card payments flow for cloudnos a cake console. Also a Marketplace for templates. That's something I've talked to Cloud nose guys both Maxes. They think it's a great idea to have a Marketplace for templates. So anyone who's maybe putting time and effort into building an sdl and wants to share it but want to earn some akto or whatever. + +Denis Lelic: Those users are going to be able to publish that template in the marketplace. So it's gonna have a functionality to Write that template by that template so it actually brings a lot of different things to it. for example profiles if a user creates a template music she needs a profile and where all of those templates they've created are listed and so on and so on and so on. So yeah, those are kind of like issues that take more time to design and to create and to write the whole spec and the same goes for the website website has some plans Tyler already mentioned a couple of times there. + +00:05:00 + +Denis Lelic: We would need a page. That would actually combine development and community and I already started working on it. But any kind of it's all quite overlapping over the whole website, and it's + +Denis Lelic: certain times it reminds me of it get started page. So that's something I just have to look deeper into and hopefully find a good solution. The next thing would be swag or March for a cashnetwork. Unfortunately, Robert is not here, but I'll DM him separately and me and Tyler already talked to give him an invite. for creating mockups for all the merch we did and end of the previous year and with Sig design, and I talked to Peter. + +Denis Lelic: Last night and we're gonna have Greg involved in that too. So Greg is always happy to participate in swag design. He has his own ideas. So we'll try to support him as well. Yeah. + +Denis Lelic: I'm + +Denis Lelic: Yeah, the last time we mentioned video content. Unfortunately, there was no time at least from my side to do any. video content meaning video tutorials and so on but on the other side because we got a cash edu going on where + +Denis Lelic: community members actually developed quite not a lot of content but some content and I think there are four edu courses they are but from my perspective, I would expand on that and offer more video content on more mainstream path platforms like YouTube. So yeah, that's just something me and Zach we were talking about and maybe this month is the month where we could actually pull one together. so whenever you find time, let me know and I'll just try to clear my schedule and just to prepare at least one to get us going. + +Zach Horn: Yeah, I'm definitely definitely happy to help with those. I think We do need to find somebody in the community that has the video skills to support us in this. I think there's a couple folks that fall into that category. I've actually been dming with somebody professionally who's very interested in creating some walkthroughs and tutorials and kind of motion design type video for us. So we'll see where that goes. It's coming along at the moment but commitment yet, but definitely happy to help it. We want to just spend one of these up like a basic how to deploy on cloud most or something like that. + +Denis Lelic: cool, cool yeah, I'm + +Denis Lelic: Sorry, I'm happy to support, any Community member who's willing to participate in any shape or form design for just Danny? I'm happy to work with anyone. besides everything I mentioned and the last couple of weeks. We did a bunch of event stuff either Booth designs t-shirt hoodies everything that goes along with events. So Luna if you need anything from my side in the beginning of the conversation this meeting actually you've mentioned some of the stuff before we started recording. Yeah, and just feel free to DM me if you need anything from our side. + +Denis Lelic: and as usual I like to keep the floor open for discussion on any design related topic. So if anyone has anything to share anything to discuss feel free to + +Denis Lelic: or Yeah Zach. + +00:10:00 + +Zach Horn: I call we want to I've been looking at the current website and I raise this issue in the website revamp repo we have these two screens one is On the providers page, I believe under the drop-down. Let me pull up the site. Yeah, so if you drop down Network and you go to about Akash. And then providers in the laptop you have that map view that has all the dots with the providers where they are in the world. and then it's also if you go to community. + +Zach Horn: I'm highlighting the issue that I'm trying to raise because I can't find it. You go ecosystem a cost providers, right? And then you have this map of all the providers with their ratings and resources. I've made an issue in the site to combine those and service them or highly on the page because the info is great. It's like if you're looking at the site you can see where the providers are in the world super compelling marketing image and then you can see all the different providers but the resources they're uptime what they have available all that. + +Zach Horn: This is mostly brainstorming at this point. What do you think that is about making that essentially a provider's page? I mean my suggestion is that could literally be providers in the nav or something like that if not that but maybe providers as a subsection on. What's that first drop down Network, you drop down Network and it says providers something like that. what's your first thought on that Denis? + +Denis Lelic: It is here and the chat section as well. Yeah, I think it makes sense. When we look back I think as the website grew through the working group, we kind of added new stuff here and there but it's always good to look back and to see what kind of pages can improve. So I agree. This could be one of them. just to have a good overview of What's going on the other side? the network looks like How many resources where are they located So yeah, I agree a hundred percent with you. I'm gonna look at the issue you've created so + +Zach Horn: Yeah. + +Denis Lelic: just to have a draft there and just going to support you in the comment section and issue here. + +Zach Horn: Sounds good. I mean that just looking at the raph Network. about Akash providers. Yeah, it's three clicks deep which is not ideal. But this graph. I mean we could even showcase this on the homepage in my opinion. I mean that's almost like landing page quality. Because when you're scrolling down, you're getting that sales read quote unquote when you're scrolling down the home page. I feel like that's information that we should. It's front and center right? It's gonna be someone's like first question is How are you guys distributed? What resources do you have all that? + +Denis Lelic: Yeah. Yeah, I agree. I'm just going through the website so Network about a cash. So yeah, you're basically three clicks away from this page. and could be like + +Zach Horn: Yeah. + +Denis Lelic: the path could be way shorter to get all this info. I agree. + +Zach Horn: Yeah, we have the issue open. So I guess we can coordinate a sing and talk about it a little bit tomorrow. See what we need to do. + +Denis Lelic: Yeah. Yeah, cool. Thanks Zach. anyone else? + +Zach Horn: Yeah for sure. + +Denis Lelic: Okay, So if anything design related pops up at you're all welcome to either me or anything and sick Design Channel + +Joao Luna: Yeah, I'll try to have someone from my team. That's now more dedicated to design to also start helping and Their crash site as well. So we'll start to deportals into all sorts of graphic design stuff. + +Denis Lelic: cool + +Joao Luna: So that's something in two weeks. So she'll be quitting her field job and be 100% dedicated to our platform, but I have extra time to also help on a cash. So that's something I'm looking forward for the next couple of weeks. + +00:15:00 + +Denis Lelic: Okay, cool. That's Good to hear. Yeah, I would only suggest to have + +Denis Lelic: some sort of a framework. So either share it in the Sig design or create an issue in the website repo. So we're kind of like Quack of it and keeping an eye on all the issues and everything like design and website related. Of course. + +Denis Lelic: Okay, cool. + +Denis Lelic: if much we talked about pretty much everything from my notes and my agenda so that could be it for today if anyone else wants to talk about anything. Feel free to talk offline or online. Thanks again for joining today. We'll see each other next month. So this one it's a short month. So probably see each other quite soon, but there's a working group or the website happening tomorrow. So b s and Luna your invited and deathless. Sorry, you're invited to participate and that meeting as well. thanks again for joining and You next time. + +Denis Lelic: Bye. + +Zach Horn: Thanks guys. + +Joao Luna: But thank you. + +Zach Horn: Take care. + +Meeting ended after 00:17:38 👋 + From c7f29ddc0bffa35c055129273f6d7c314c7f5bae Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 16 Apr 2024 13:56:39 +0000 Subject: [PATCH 038/138] Update readme tables for February (#549) Feb-tables Co-authored-by: Drinkwater --- sig-community/README.md | 2 +- sig-design/README.md | 2 +- wg-provider-audit/README.md | 14 ++++++++++++++ wg-provider-audit/{ => meetings}/001-2024-02-21.md | 0 wg-zealy/README.md | 7 ++++--- .../{006-2024-01-15.md => 007-2024-01-15.md} | 0 wg-zealy/meetings/008-2024-01-22.md | 2 +- 7 files changed, 21 insertions(+), 6 deletions(-) rename wg-provider-audit/{ => meetings}/001-2024-02-21.md (100%) rename wg-zealy/meetings/{006-2024-01-15.md => 007-2024-01-15.md} (100%) diff --git a/sig-community/README.md b/sig-community/README.md index 074e49f2..a07722ab 100644 --- a/sig-community/README.md +++ b/sig-community/README.md @@ -27,7 +27,7 @@ This SIG (Special Interest Group) is designed for Akash community members to pro | #9| Tuesday, November 11, 2023 11:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/009-2023-11-15.md) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/009-2023-11-15.md#Transcript) | [Link](https://elrhjnozov4zcwv4mcpc7n4za4nyuxelufxrk56hniqprbk3bmka.arweave.net/IuJ0tdl1eZFavGCeL7eZBxuKXIuhbxV3x2og-IVbCxQ) | #10| Tuesday, December 12, 2023 11:00 AM PT (Pacific Time) | Coming Soon | Coming Soon | Coming Soon | #11| Tuesday, January 09, 2024 11:00 AM PT (Pacific Time) | Coming Soon | Coming Soon| Coming Soon -| #12| Tuesday, February 13, 2024 11:00 AM PT (Pacific Time) | | | +| #12| Tuesday, February 13, 2024 11:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/012-2024-02-13.md) |[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/012-2024-02-13.md#Transcript) | Coming Soon | #13| March, 2024 11:00 AM PT (Pacific Time) | | | | #14| April, 2024 11:00 AM PT (Pacific Time) | | | | #15| May, 2024 11:00 AM PT (Pacific Time) | | | diff --git a/sig-design/README.md b/sig-design/README.md index c3c865e8..68a1274d 100644 --- a/sig-design/README.md +++ b/sig-design/README.md @@ -28,7 +28,7 @@ date: 2023-1-09T00:19:20-08:00 | #11 | Wednesday, November 08, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/011-2023-11-08.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/011-2023-11-08.md#transcript)| [Link](https://mctlnmdevhysanes52tbok6kbc3mgbsgnn6qemc35xhanfc2x67q.arweave.net/YKa2sGSp8SA0ku6mFyvKCLbDBkZrfQIwW-3OBpRav78) | #12| Wednesday, December 13, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/012-2023-12-13.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/012-2023-12-13.md#transcript) | [Link](https://une76rieq3cvbtrnjv3gxaw6kbxaay3tnzqsangya2lfe6ionpva.arweave.net/o0n_RQSGxVDOLU12a4LeUG4AY3NuYSA02AaWUnkOa-o) | #13| Wednesday, January 10, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md#transcript) | [Link](https://zao4urnjuqb6ncx2vacwjuqiyqnucl2ifcfm33blijhw6v6owzla.arweave.net/yB3KRamkA-aK-qgFZNIIxBtBL0gois3sK0JPb1fOtlY) -| #14| Wednesday, February 21st, 2024 08:00 AM PT (Pacific Time) | | | +| #14| Wednesday, February 21, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/014-2024-02-21.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/014-2024-02-21.md#transcript) | Coming Soon | #15| March 13th, 2024 08:00 AM PT (Pacific Time) | | | | #16| April, 2024 08:00 AM PT (Pacific Time) | | | | #17| May, 2024 08:00 AM PT (Pacific Time) | | | diff --git a/wg-provider-audit/README.md b/wg-provider-audit/README.md index 7f94e530..9f56f27e 100644 --- a/wg-provider-audit/README.md +++ b/wg-provider-audit/README.md @@ -12,6 +12,20 @@ This working group is for developing an open source auditor tool for providers. [3rd Wednesday of Every Month](https://calendar.google.com/calendar/u/0?cid=Y18yNWU1ZTM3NDhlNGM0YWI3YTU1ZjQxZmJjNWViZWJjYzBhMDNiNDBmYjAyODc4NWYxNDE1OWJmYWViZWExMmUyQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20) +| Meeting | Time | Notes | Transcript | Recording +| --- | --- | --- | --- | --- | +| #1 | Wed, Feb 21, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/wg-provider-audit/001-2024-02-21.md) | [Link](https://github.com/akash-network/community/blob/main/wg-provider-audit/001-2024-02-21.md#transcript) | Coming Soon +| #2 | Wed, March 20, 2024 10:00 AM PT (Pacific Time) | | | +| #3 | Wed, April 17, 2024 10:00 AM PT (Pacific Time) | | | +| #4 | Wed, May 22, 2024 10:00 AM PT (Pacific Time) | | | +| #5 | Wed, June 19, 2024 10:00 AM PT (Pacific Time) | | | +| #6 | Wed, July 17, 2024 10:00 AM PT (Pacific Time) | | | +| #7 | Wed, August 21, 2024 10:00 AM PT (Pacific Time) | | | +| #8 | Wed, September 18, 2024 10:00 AM PT (Pacific Time) | | | +| #9 | Wed, October 16, 2024 10:00 AM PT (Pacific Time) | | | +| #10 | Wed, November 20, 2024 10:00 AM PT (Pacific Time) | | | + + ## Contacts - [Discord](https://discord.com/channels/747885925232672829/1200172631480094771/1202611858008187001) diff --git a/wg-provider-audit/001-2024-02-21.md b/wg-provider-audit/meetings/001-2024-02-21.md similarity index 100% rename from wg-provider-audit/001-2024-02-21.md rename to wg-provider-audit/meetings/001-2024-02-21.md diff --git a/wg-zealy/README.md b/wg-zealy/README.md index 17ed8d3f..70f1b0d2 100644 --- a/wg-zealy/README.md +++ b/wg-zealy/README.md @@ -16,9 +16,10 @@ The working group is created to work on the proposal to see what support is need | #4 | Monday, December 04, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/004-2023-12-04.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/004-2023-12-04.md#transcript)|[Link](https://sq2ysituuvyyyeuuw7eawkdlbmvqpwtlkqkpogujyh5jfoxexosq.arweave.net/lDWJInSlcYwSlLfICyhrCysH2mtUFPcaicH6krrku6U) | #5 | Monday, December 11, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/005-2023-12-11.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/005-2023-12-11.md#transcript)|[Link](https://hp5novctzn3y56mrqix5wq3knexy4w24tk2ugahmstq2ofxzp57a.arweave.net/O_rXVFPLd475kYIv20NqaS-OW1yatUMA7JThpxb5f34) | #6 | Monday, December 18, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/006-2023-12-18.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/006-2023-12-18.md#transcript)|[Link](https://efn65ve3e5sebv7bhpgilvvzv23zx3ln6goskfwwrhj5rsmbludq.arweave.net/IVvu1JsnZEDX4TvMhda5rreb7W3xnSUW1onT2MmBXQc) -| #7 | Monday, January 15, 2023 06:30 AM PT (Pacific Time)|coming soon| coming soon | Coming soon -| #8 | Monday, January 22, 2023 06:30 AM PT (Pacific Time)|coming soon| coming soon | Coming soon -| #9 | Monday, February 05, 2023 06:30 AM PT (Pacific Time)|coming soon| coming soon | Coming soon +| #7| Monday, January 15, 2023 06:30 AM PT (Pacific Time)|coming soon| coming soon | Coming soon +| #8 | Monday, January 22, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/008-2024-01-22.md)| [Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/008-2024-01-22.md#transcript) | [Link](https://4dq4pkkqqmljo2ukbfplejfpdjw2itvunyzo3hf24zra73afipwa.arweave.net/4OHHqVCDFpdqiglesiSvGm2kTrRuMu2cuuZiD-wFQ-w) +| #9 | Monday, February 12, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/009-2024-02-12.md)| [Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/009-2024-02-12.md#transcript) | Coming Soon +| #10 | Monday, March 03, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/010-2024-03-18.md)| [Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/010-2024-03-18.md#transcript) | Coming Soon ## Leads - Piber Dev diff --git a/wg-zealy/meetings/006-2024-01-15.md b/wg-zealy/meetings/007-2024-01-15.md similarity index 100% rename from wg-zealy/meetings/006-2024-01-15.md rename to wg-zealy/meetings/007-2024-01-15.md diff --git a/wg-zealy/meetings/008-2024-01-22.md b/wg-zealy/meetings/008-2024-01-22.md index f6b93c2e..f1e5b93f 100644 --- a/wg-zealy/meetings/008-2024-01-22.md +++ b/wg-zealy/meetings/008-2024-01-22.md @@ -1,4 +1,4 @@ -# Akash Network - Zealy Working Group (WG) - Meeting #6 +# Akash Network - Zealy Working Group (WG) - Meeting #8 ## Agenda - Briefly review the purpose of the Akash Zealy initiative and its successes to date. From ea1919e0970178f2f95637d98bd3ef4d18ab9273 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 18 Apr 2024 10:56:48 -0400 Subject: [PATCH 039/138] sig-analytics Create 2024-02-15.md add meeting notes, transcript, and other meeting details chore: add video recording * Signed-off-by: Drinkwater --- sig-analytics/meetings/2024-02-15.md | 146 +++++++++++++++++++++++++++ 1 file changed, 146 insertions(+) create mode 100644 sig-analytics/meetings/2024-02-15.md diff --git a/sig-analytics/meetings/2024-02-15.md b/sig-analytics/meetings/2024-02-15.md new file mode 100644 index 00000000..aef95e4a --- /dev/null +++ b/sig-analytics/meetings/2024-02-15.md @@ -0,0 +1,146 @@ + +# Akash Network - Analytics Special Interest Group (SIG) - Meeting #11 + +### **Agenda** + +- Open discussion +- Review of sig-analytics 2023 + +### **Meeting Details** + +- Date: Thursday, February 15th, 2024 +- Time: 09:00 AM PT (Pacific Time) +- [Recording]() +- [Transcript](#transcript) + +## **Participants** + +- Alani Kuye +- B S +- Jigar Patel +- Max +- Rodrigo Rochin +- Scott Carruthers +- tentabs +- Tyler Wright + + +## Meeting Notes + +- Tyler talked about all the progress that had been made over the year with sig-analytics. +- Max talked about big updates to the Cloudmos API. There is a new version of the API that was released for anyone in the community to access. There will be no restrictions on access. +- Swagger documentation can be found here: https://api.cloudmos.io/v1/swagger . +- Tentabs asked about other analytics like staking wallets, transaction volume, and other token related analytics. Tentabs is a community member who has been asking some gerneral questions in discord. +- + + +## Action Items + +- Cloudmos team will share any updates on API, and will let community know when older version will be depricated. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to analytics monthly meeting a number 11. Actually the Cadence of this change has changed from every month to every two months just because there's a lot of conversation and continues to happen One of the big items out of 2023 was having a open source indexer, obviously the climos team who's represented by Max here today have made that possible and there's been a significant amount of work. It's been happening around Cloud most API and index there so much appreciate the work. I know that Max will give a small update shortly. But again because of indexers problem, which was a big problem going into 2023 now being solved all and as well as the number of archival nodes have been spun up. I know that overclock team + +Tyler Wright: is one or two archival nodes and there's also a couple of community members that manage archival nodes including Euro plots the Cadence for the analytics monthly if anybody has any questions or comments about anything analytics related on the Akash Network. Feel free to drop those questions in the side this again analyt. score Channel and we'll make sure that they're talking points for future meetings or if we need to spin up a specific working group session around a topic we'll do so I also know that the pirate did and his team as a part of their proposal. Got some. + +Tyler Wright: Funds mostly focus on open source auditing tools, but they also will be contributing to the index or so again as we get closer to those. We'll continue to monitor any changes happen to the indexer through the special interest group for Analytics. cool other than that at a high level again at the last meeting Jin who usually joins these meetings was talking about a dash solution that he's spun up. It's an awesome Akash if anybody wants to spin up their own version and I believe it's been added to the cloud most templates. And again what other action items was adjusting the Cadence of the meeting, so this is the first meeting of 2024. Didn't give a demo of the dash tool as well. So if anybody wants to look at the last meetings recording feel free on GitHub. + +Tyler Wright: but yeah, if anybody has any agenda items they would like to talk about specifically today. Feel free to drop those in chat. Otherwise, I know that again the cloud most team. Now under overclock represented by Max B here today has been working extensively on the clubhouse API as well as some other items next. Do you want to give an update on some of your work as it pertains to analytics and some of the teams work and some of the changes that might be affecting the + +Max: Yeah, So the biggest update that I have for everyone today that we just launched or released the new API. with the new routes prepended with the version so I put the link to the Swagger documentation in the chat. So if you need to change your app. Or looking for specific endpoints that we have exposed. It's all in that documentation. You can just click and try the endpoints and see what the data returns. and so in the future when we change that API or to it updates to it. It'll probably go under the V2. + +Max: and we'll do the same process and update or Notify everyone that we release a new version and stuff. So Yeah, I mentioned in the signaletics chat. There's currently redirects set for the old routes. so you don't have to worry about your outbreaking if you're actually using the old routes that was in the old API. But at some point we will remove them. Just to clean up the code and not deprecated code so to use them Please update them, but we're not gonna review them tomorrow next week maybe in a few months. We'll see. + +00:05:00 + +Max: So yeah, the big update where the API. + +Tyler Wright: Thank you Max. It's much appreciated again the work and the update. We'll make sure that again back and shared widely and Discord. and elsewhere + +Tyler Wright: other than that, are there any specific topics that anybody wants to discuss that pertains to analytics on a cache that maybe Somebody has any questions comments concerns. + +Tyler Wright: No. Okay, go ahead Max. + +Max: If you have ideas about endpoints that you would like to have for. + +Tyler Wright: You're fine. + +Max: For a cash related stuff, Let us know we can implement it and add it to the API. + +Tyler Wright: Much appreciate that Max. Again. If anybody has any endpoint ideas that they want to be added. I know that the Prater team has previously asked for some items and those things have been added with no problem. So, please feel free to reach out to Max on Discord and we can again continue to make improvements to the API. + +Tyler Wright: cool I don't want to waste anybody's time again if there's any updates. At Rodrigo assets. There's any rate limits right now. + +Max: And nope. I don't think so. Please don't it does our API. + +Tyler Wright: cool All right, if there's nothing else I'll go ahead and Max. + +Max: But yeah,… + +tentabs: + +Max: sorry We will implement the rate limiting in. API keys at some point if I + +tentabs: Can I raise my hands? Can you hear… + +Tyler Wright: Yes, perfect. Yes. + +tentabs: Hi, this is 10 tabs. I'm some random guy in the Discord. I've done data for 10 years or something at almost specially product analytics and stuff at some big companies. I'm doing web free stuff full-time right now. I'm mod a Discord and to a bunch of research and stuff and I've been looking a bunch on chain analytics for a cost. So I've been posting some stuff in the Discord and things like that. I guess I was just curious if that's something that y'all spend any time thinking about because it's not really product analytics when I've worked at companies. I haven't really looked at what the stock is doing or anything like that, but I guess I'm just curious. + +tentabs: that's something you think about and then if there's any Questions that you have or anything because I've just spending a lot of time poking around in all sorts of data. + +Max: There's other question for me or for anybody Taylor Tyler. + +Tyler Wright: I think that might be a question for anybody. I know that again ten times has been contributing so you can see some of his comments in the Discord Channel. I are we thinking about analytics and Akash In terms of usage memory and akt daily spending all that kind of stuff. Is that… + +tentabs: I guess I'm curious about … + +Tyler Wright: what the question is? + +tentabs: if you spend time thinking about Trends and staking or unstaking and counts of wallet holders and transaction volume and that type of thing or is that out of scope for the types of things that the folks here. Think about as far as Analytics. + +Tyler Wright: In terms of analytics. I've certainly something. This for this group specifically was really tasked with trying to figure out some of the metrics that you see related to the Akash Network in terms of a staking the more stuff about the token. I believe that's more focused around Sig economics where that's barely talked about and there's very specific questions related to some of these things like, who's holding the most akt all that kind of stuff, but in terms of this specific special interest group, I think the focus is always been around. + +00:10:00 + +Tyler Wright: Increasing understanding Trends in terms of demand how the network is being used. What kind of utilization and resources are being utilized and understanding the complete picture. So that is more. Clients get built. It's more users. Come on to the network. There's really a holistic picture on how the network is actually being used. Hope that answers a question. + +tentabs: Got it. + +Tyler Wright: Go ahead Max. + +Max: Yeah, just add to what you're saying Tyler and the indexer. that we built it could the technically do the things that you were talking about the tentabs the anonymous taking what's the biggest stickers just anything related to Unchained data? because all the stats that we get to display in tunnels using the index series based on Unchained data, so Whatever happens on chain, we can index it and add to the indexer or anybody can do it because it's source. So yeah open and so is your question. + +tentabs: Yeah, totally. Thanks for your thoughts and stuff. I'll check out the economics Sig as well. Yeah, that's all. Thanks for the dashboard and everything. You think y'all have the best reporting that I've seen out of anyone in the lake depend CPU space. So great job. All of you that set that up. + +Tyler Wright: Yeah much appreciate that tentabs one thing I'll also do I'll pass along some of the comments the person that runs Sig economics might be a person you can talk to I'm sure you're familiar but mint scan and there's a number of tools like it. It's a tool that Members of the core team and many members of the community use to kind of track some of that data that you're talking about that on chain data, but I'm going to connect one of our team members that runs that Sig economics meeting to some of these conversations. You've been having a analytics monthly March. + +tentabs: Okay, perfect. I'll dig through the channel and just see what they talk about and stuff over there as well. Appreciate getting to listen on this. + +Tyler Wright: a place our pleasure + +Tyler Wright: Cool, are there any other topics that haven't been discussed yet as it pertains to analytics anybody wants to discuss right now? + +Tyler Wright: as changes get made to the API. I'm sure that announcements will continue to be made but as Max's just mentioned. There's been a significant amount of changes. I'll make sure that The I API links are in the notes. And then again, we'll make announcements in various channels. So that folks can start integrating apis into their flows for apps or whatever else. + +Tyler Wright: Great, if anybody else has any other questions comments or anything again, feel free to drop them in Discord or message me and then we can talk about them at a future meeting or we could talk about them async and Discord or other channels. As updates become available for the working group for provider audits again. We'll make sure that anything analytics related is mentioned during the analytics. + +Tyler Wright: That everybody can access a cash Community groups calendar. + +Tyler Wright: All right, I hope everybody has a great rest of their day. Again. Thank you for the questions comments Max. Thanks for the update on all the stuff going on with the cloud most API. But yeah, we'll just continue to stay connected. And again if I get an update from Jane on anything dash related because I know he's doing a great deal of work on that dash tool that I'll make sure he either provides a demo or a short updates again Olympics for people to stay up to date on + +00:15:00 + +Tyler Wright: All right, y'all again. This is every two months meeting. So I want to see you next month. I'll see you on two months, and if anybody has any questions in the meantime again, we'll just talk on Discord or elsewhere, but I hope everyone has a great rest of their day. Thank you all very much. + +Rodrigo Rochin: Thank you. + +Max: Thanks. See you. + +Meeting ended after 00:15:49 👋 + + From 132ab63442d7336efec6bfbf7f8f06e0e3ded141 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 18 Apr 2024 10:57:21 -0400 Subject: [PATCH 040/138] sig-analytics Rename 2024-02-15.md to 011-2024-02-15.md Signed-off-by: Drinkwater --- sig-analytics/meetings/{2024-02-15.md => 011-2024-02-15.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename sig-analytics/meetings/{2024-02-15.md => 011-2024-02-15.md} (100%) diff --git a/sig-analytics/meetings/2024-02-15.md b/sig-analytics/meetings/011-2024-02-15.md similarity index 100% rename from sig-analytics/meetings/2024-02-15.md rename to sig-analytics/meetings/011-2024-02-15.md From 1743c79fc9ecca0285ce8570eee2a82512baadc9 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 18 Apr 2024 10:59:29 -0400 Subject: [PATCH 041/138] sig-analytics Update README.md added details for meeting 11 chore: add video recording Signed-off-by: Drinkwater --- sig-analytics/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sig-analytics/README.md b/sig-analytics/README.md index df53111a..65cb43d1 100644 --- a/sig-analytics/README.md +++ b/sig-analytics/README.md @@ -30,8 +30,8 @@ Analytics Special Interest Group is dedicated to defining and building tools tha | #8 | Thursday, September 14, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/008-2023-09-14.md) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/008-2023-09-14.md#Transcript) | [Link](https://t5tmhypnhybd3jpbk3amizf6m2pl66msvvbhlqjyqnynouil4ksa.arweave.net/n2bD4e0-Aj2l4VbAxGS-Zp6_eZKtQnXBOINw11EL4qQ) | #9 | Thursday, October 12, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/009-2023-10-12.md) | [Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/009-2023-10-12.md#transcript) | [Link](https://v5ixigio4enkf7qhvlmzfptnlx6zkdite2skrznyil2d3xih6ana.arweave.net/r1F0GQ7hGqL-B6rZkr5tXf2VDRMmpKjluEL0Pd0H8Bo) | #10| Thursday, December 14, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/010-2023-12-14.md) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/010-2023-12-14.md#transcript) | [Link](https://ek6ahcmxfv2mnwpitrfidefkzfm6razh4zlv7cuowuue5tnrqy4q.arweave.net/IrwDiZctdMbZ6JxKgZCqyVnogyfmV1-KjrUoTs2xhjk) -| #11| Thursday, February 15, 2024 09:00 AM PT (Pacific Time) | | | -| #12| April, 2024 09:00 AM PT (Pacific Time) | | | +| #11| Thursday, February 15, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/011-2024-02-15.md) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/011-2024-02-15.md#transcript) | Coming Soon +| #12| April 18, 2024 09:00 AM PT (Pacific Time) | | | | #13| June, 2024 09:00 AM PT (Pacific Time) | | | | #14| August, 2024 09:00 AM PT (Pacific Time) | | | | #15| October 2024 09:00 AM PT (Pacific Time) | | | From a3e69974f188c2a24c7692ecf56cc59e182b2e3a Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 23 Apr 2024 13:13:04 -0400 Subject: [PATCH 042/138] sig-docs Update README.md add date for meeting 16 Chore: Add meeting details for 14 and 15 Signed-off-by: Drinkwater --- sig-documentation/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-documentation/README.md b/sig-documentation/README.md index 79ebdecc..d4550253 100644 --- a/sig-documentation/README.md +++ b/sig-documentation/README.md @@ -31,7 +31,7 @@ The goal of this SIG is to foster a community around the creation and maintenanc | #13 | Tuesday, January 23, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/013-2024-01-23.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/013-2024-01-23.md#transcript) |[Link](https://ggtsa72sjsvu3yph245qmj6zvpy7uyys7jerkj72heitmyoiv2na.arweave.net/Macgf1JMq03h59c7BifZq_H6YxL6SRUn-jkRNmHIrpo) | #14 | Tuesday, February 27, 2024 07:00 AM PT (Pacific Time) | | | | #15| March, 2024 07:00 AM PT (Pacific Time) | | | -| #16| April, 2024 07:00 AM PT (Pacific Time) | | | +| #16| April 23, 2024 07:00 AM PT (Pacific Time) | | | | #17| May, 2024 07:00 AM PT (Pacific Time) | | | | #18| June, 2024 07:00 AM PT (Pacific Time) | | | | #19| July, 2024 07:00 AM PT (Pacific Time) | | | From 04e83bfbcacef6c14a134eaa403021dbb9fd16d4 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 24 Apr 2024 09:44:42 -0400 Subject: [PATCH 043/138] sig-clients Update README.md update dates for meeting Signed-off-by: Drinkwater --- sig-clients/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-clients/README.md b/sig-clients/README.md index dd97bf11..22aa65e5 100644 --- a/sig-clients/README.md +++ b/sig-clients/README.md @@ -47,7 +47,7 @@ The goal of this SIG is to foster a community around each of these clients that | #12 | Wednesday, January 17, 2024 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/012-2024-01-17.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/012-2024-01-17.md#transcript) |[Link](https://75iuscsrjioekyahvk6vad3taa5ikpweibvxs2rf4amjvzvj6gfa.arweave.net/_1FJClFKHEVgB6q9UA9zADqFPsRAa3lqJeAYmuap8Yo) | #13 | Thursday, February 22nd, 2024 09:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/013-2024-02-22.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/013-2024-02-22.md#transcript) |[Link](https://x5g5djwxzxixepgqsmxl6rupiipshcicdmq5bf2tjac35fjv5f6q.arweave.net/v03RptfN0XI80JMuv0aPQh8jiQIbIdCXU0gFvpU16X0) | #14| March 27th, 2024 09:00 AM PT (Pacific Time) | | | -| #15| April, 2024 10:30 AM PT (Pacific Time) | | | +| #15| April 24th, 2024 09:00 AM PT (Pacific Time) | | | | #16| May, 2024 10:30 AM PT (Pacific Time) | | | | #17| June, 2024 10:30 AM PT (Pacific Time) | | | | #18| July, 2024 10:30 AM PT (Pacific Time) | | | From efaa13a896f0f0636b93a0008cde998d67fbc082 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Thu, 25 Apr 2024 13:37:05 +0000 Subject: [PATCH 044/138] Create meeting notes for sig-support #29 (#557) * Create meeting notes for sig-support #29 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 029-2024-03-06.md added transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-support/meetings/029-2024-03-06.md | 434 +++++++++++++++++++++++++ 1 file changed, 434 insertions(+) create mode 100644 sig-support/meetings/029-2024-03-06.md diff --git a/sig-support/meetings/029-2024-03-06.md b/sig-support/meetings/029-2024-03-06.md new file mode 100644 index 00000000..7c0254b4 --- /dev/null +++ b/sig-support/meetings/029-2024-03-06.md @@ -0,0 +1,434 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #29 + +## Agenda + +- Participants will look at issues in [Akash Support Repo](https://github.com/akash-network/support/issues). +- Scott Carruthers will lead triaging issues, and discussion of implementation for issue fixes. +- Scott will discuss Support from the community and ask for any community feedback. +- Participants can have an open discussion of any other issues or support related items on Akash Network. + +## Meeting Details + +- Date: Wednesday, March 20th, 2024 +- Time: 07:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + +## Participants +- Andrew Hare +- Andrey Arapov +- Deathless +- Maxime Beauchamp +- Scott Carruthers +- Tyler Wright +- Zeke E + +## Meeting Notes + +### Introduction and Updates +#### Tyler wright +- Core team and community members discuss issues in [Akash Support Repo](https://github.com/akash-network/support/issues) +- Invitation to community to bring forward any issues +- Lighter attendance expected due to conferences +- Mainnet 10 upgrade discussed (March 13th) +- Parameter change for deposit amounts (from 5 AKT to 0.5 AKT) +- Change went into effect on March 11th or 12th and documentation updated accordingly +### Triage of Open Issues +- Scott facilitated the triage process +- Reviewed open issues in Akash Network support repo +- Identified unassigned issue regarding memory issues on archival nodes +- Andrey provided insight on memory usage and suggested further review +- Scott tagged Arthur for further investigation and decision on the issue +- Andrey Arapov suggested converting the issue into a discussion +- Scott agreed to convert the issue and assigned Andrey for follow-up +- Andrey requested to leave the issue open for reference while creating a discussion + +#### Issue opened by Community member(Issue 195) +- Issue opened by Community member, discussed by Scott and Maxime. +- Scott reviews the issue, notes absence of reliable Per test and local developments. +- Mention of unreliable sandbox and need for local development environments. +- Maxime explains difficulty for new developers to run Cloud locally. +- Discussion on the dated nature of the issue and potential new solutions. +- Maxime assigned to review issues in Cloudmos repository. +- Scott offers support to Maxime throughout the process. + +#### Review of open issues in provider resource release process ( Issue 193). +- Discussion on issue of provider should release resources immediately after never accepted deployment was closed. +- Scott and Andrey share experiences and observations regarding delays in resource release. +- Mention of variability in delay times, ranging from 3 to 45 minutes. +- Andrey provides examples of extended delays, up to 6 minutes, and references a possible 25-minute delay. +- Speculation on the cause, including potential issues with the inventory operator. +- Connection made to related ticket 192 regarding issues with the inventory operator's data polling. +- Andrey suggests further investigation into the connection between the two issues. + +#### Issue reported by Deathless regarding abnormally large GPU and RAM allocatable statistics. +- Discussion on an urgent issue reported by Deathless, involving abnormally large GPU and RAM allocatable statistics. +- Andrey suggests that the issue may be related to the upgrade of the inventory operator from 0.4 to 0.5, with potential impacts on resource visibility. +- Andrey describes the need for manual restarts of the inventory operator to address the issue. +- Scott reclassifies the issue as a P0, indicating urgent attention required, and notes that it's already assigned to Archer. +- Discussion on the impact of high memory allocatable stats, affecting bidding and deployment processes. +- When memory allocatable stats are high, bids are not received if the request uses a wildcard for the GPU model, but bids are received if a specific model is specified. +- Uncertainty whether the issue should be classified as a P0 or P1, but its impact necessitates urgent attention. +- Andrey notes similar issues with the Hurricane and European providers, persisting even after inventory operator restarts. +- Scott highlights the severity of the issue, considering it one of the most severe ongoing issues in the network. +- Agreement to prioritize urgent attention to the issue. + +#### Unresponsive status endpoint issue reported by a provider. +- Andrey discusses the issue of a provider's unresponsive status endpoint, noting other ongoing issues with the Hurricane provider. +- Scott acknowledges Andrey's comments and suggests waiting for further testing before reclassifying the issue. +- Zeke mentions a Discord conversation where a user reported unreachable port 8443, prompting clarification on the issue. +- Andrey suggests updating the engine X Ingress operator config to allow port 8443, which was enabled with the provider upgrade to version 0.5. +- Scott clarifies the issue and concludes the review of unassigned issues, opening the floor for further discussions. + +### Update on Shared Memory (SHM) enablement over SDL. +- Zeke inquires about the timeline for Shared Memory (SHM) enablement over SDL. +- Scott informs Zeke that the code for SHM enablement is complete, with Adam as the primary engineer, and they are awaiting the release. +- Documentation updates have been staged to include SDL examples and necessary attributes for providers to support SHM. +- Scott mentions that the release timing is uncertain, but once released, all documentation will be updated accordingly. +- Zeke expresses satisfaction with the progress, noting the ability to deploy SHM on Akash without manual intervention. +- Scott confirms Zeke's observation and concludes the meeting, passing control back to Tyler. + +### Efforts to combat spam in the Discord server. +- Tyler starts the agenda by mentioning the recent efforts to reduce spam in the Discord server. +- He notes that keywords have been added to a block list, resulting in a decrease in spam. +- Tyler encourages community members to reach out if they encounter any spam-related issues. +- Zeke, a newly appointed Vanguard, acknowledges the effectiveness of the auto-moderator in catching spam. +- Apart from spam, Zeke doesn't identify any significant thematic issues in Discord recently. +- Tyler appreciates Deathless and others for their contributions in addressing issues and providing feedback in the provider and deployment channels. +- He encourages community members to report any issues or suggest improvements for the user experience in the support channel or special interest groups. + +### Other Matters Discussed +- Introduction of Andrew, a new senior software engineer at Overclock Labs. +- Andrew will continue to join future calls and is currently working behind the scenes on various tasks. +- Tyler praises Andrew's work ethic and integration into the team. +- Reminder to mark calendars for upcoming SIG clients and SIG providers meetings. +- Tyler anticipates discussions on provider auditing and feature discovery in the upcoming meetings. +- Appreciation expressed to all participants for their time and energy. + +### Closing Remarks +- Tyler asks if there are any remaining support or core code-related topics to discuss. +- He suggests closing the Sig chain issue related to mainnet 10, which has passed the vote and the upgrade successfully occurred. +- Tyler plans to follow up on several high-priority issues, including 195, 194, 193, 192, and 190, at the next SIG support meeting or sooner. +- Scott informs the group about the migration to the new documentation site over the weekend and asks everyone to report any missing documentation or formatting issues. +- Tyler emphasizes the importance of reporting any anomalies or formatting issues in SIG docs for prompt resolution. +- Tyler acknowledges Scott and Andrey's efforts in ensuring the documentation is clean and ready for community use, thanking them for their oversight and collaboration with Piyush and his team. + +## Action Item +- Tyler to close the Sig chain issue related to mainnet 10 after obtaining consensus from the group. +- Max to follow up on issues 195 and 194 and determine the necessary actions. +- Group members to report any missing documentation or formatting issues in SIG docs for prompt resolution. +- Scott and Andrey to continue overseeing and ensuring the cleanliness and usability of the documentation site. +- Scott to reach out to Arthur for an ETA on the release of SHM enablement. +- Scott to coordinate with Archer to escalate the urgent issue by Deathless for immediate attention. +- Scott Carruthers to tag Arthur for further investigation and decision on the memory issue. +- Andrey to conduct further tests to replicate and investigate delays in resource release. +- Scott and Andrey to monitor related ticket 192 regarding issues with the inventory operator's data polling and assess its connection to the current issue. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to seek support to biweekly. I believe this is number 30 or 31 this support biweekly has been going on since open framework has started. This is a biweekly meeting where the core team and members of the community go over any issues and the support repo inside the accost Network organization that are waiting triage if there's anybody specifically from the community that is brought any issues forward and wants to discuss an issue. This is the biweekly meeting to join where you can meet with members of the core team discuss the issues and again, they can be prioritized and look to be solved. + +Tyler Wright: I know Scott who's been leading us through really the last couple especially in my absence will be leading us today. after we go through the issues awaiting triage usually be looked to members of the community to share any feedback that they've gotten and Discord Telegram and other channels. I know usually we have a number of insiders that join us, but there are a few conferences that insiders members of the core team Etc at so I was expecting a lighter week than usual. With that said the six support meetings transcripts notes and recordings should be up to date out of the last couple of Sig meetings. I know that again Scott lettuce through triaging any issues. He talked about the mainnet pen upgrade which happened last. + +Tyler Wright: Wednesday, March 13th. So week from today last week around this time. There was a plans Network upgrade that took less than five minutes and required again. Now, they upgrade their nodes and then providers have to upgrade their RPC notes. So again, thank you to all about data set participated and all the providers and have since upgraded their nodes and obviously thank you to members of core team here that help with documentation testing Etc. + +Tyler Wright: In addition to the main Net10 upgrade there was a parameter change that what didn't require Network upgrade but did go on chain for boat that's lowered the big deposit amounts for both the tenant side and the provider side believe it changes from five akt to 0.5. Akt. So again that went into effect. I believe March 11th or 12th and has been tested and seems to be Working properly end of the documentation has since been updated. So let's just say recap of some of the things that have been happening over the past a couple of weeks since the last six support meeting and even a little bit prior to that. But without further Ado, I'll hand it over to Scott to triage any issues of waiting triage on just be taking some notes in the background. but Scott's feel free to + +Scott Carruthers: All right. Thanks Tyler. Let me share my screen. + +Scott Carruthers: Okay, is everyone able to see my screen? + +Scott Carruthers: thumbs up it sounds good. So I will. Go into the lakash network support repo and take a look at the open issues. I looked at this a little bit before our call and it does look like there's a couple that don't have assignment or prioritization so we can go through those. first one that we come across that has been created since our last six Port is a review of our provider auditing requirements and Andy has already assigned himself to that. So I'll just progress down to the first unassigned issue. So this was open by Andy so Andy may have a comment and yell rely on you for a little bit of review, but this is + +Scott Carruthers: An issue where we are seeing some amount of memory issues. in certain queries on archival nodes. I Andy would you like to give some more thoughts on this? + +00:05:00 + +Scott Carruthers: Okay. + +Scott Carruthers: Yeah. + +Andrey Arapov: you can see there in the screenshot 140 gig of memory or 157 gig so it means you just needs more memory for its operations,… + +Scott Carruthers: Yeah, I'm just gonna Put a note in that we're leaving this open despite the fact that it… + +Andrey Arapov: but for one hand,… + +Scott Carruthers: carried by increase Ram allocation + +Andrey Arapov: I will think to maybe close it but another hand I'm thinking to leave it for Arthur to take a look and decide if that's expected because if it's not expected then it probably needs to be addressed. I mean the fact that it uses that whole amount of memory for this queries because maybe it's not supposed to use that much of memory And just maybe tie garter just to take a look and decide if he's okay to close it as it is, I would like him just like to go through just understand what happened and decides if it's something that we should really take care. I mean they closer look or not. + +Andrey Arapov: + +Scott Carruthers: Yeah, I tagged him there with that comment share. + +Andrey Arapov: maybe it's growing this time. We don't know so it's definitely not like you wanted to it's the lowest score in terms of priority,… + +Scott Carruthers: And also assign them. + +Andrey Arapov: but that's my five sense. + +Andrey Arapov: Maybe it's worth to change the title of this issue or maybe just leave it because it's not running out of memory anymore since he increased the memory, but it's rather consumes lots of memory, basically. More of a question. + +Scott Carruthers: Yeah. + +Andrey Arapov: Maybe I think it's even belongs more to but you can converse it into a discussion rather than the issue I believe. + +Andrey Arapov: I don't think that there is a possibility to convert it like, the issues into discussion, but I can do it later. + +Scott Carruthers: Okay. + +Andrey Arapov: Yeah, I think it was just a great probably discussion and based on this issues and just leave it in under discussion and close this issue. + +Scott Carruthers: you want me to quote you want me to close the issue and you can just create just Okay. + +Andrey Arapov: No, no just leave it so that I don't forget it. and then I'll create a discussion and refer to this issue because it's not an issue. + +Scott Carruthers: okay, I'll sign you on this as well just for Is a visible there? Okay. Sure. + +Andrey Arapov: Yeah things. + +Scott Carruthers: Okay, so I was actually reviewing this issue earlier today. So this was opened by a Community member. I am going to go back to people that are currently on call. I don't believe that this person is currently on the call. but I okay. + +Maxime Beauchamp: It's narrow. + +Maxime Beauchamp: the new team member + +Scott Carruthers: Okay. + +Scott Carruthers: So yeah, so I just was briefly coming through this before. Her call as you can see There's no reliable Per test and local developments and so I thought I don't know if any so max. Maybe you have some context for this but he's staying in those currently no reliable blockchain for tests and local development for instance tests local environments prior to either download and important DB or uses unreliable sandbox, so I guess there's two then I could write this in the comments and possibly get some further feedback, but the two obvious thoughts that come to mind is so we have the ability to spin up local development environments, which is well documented within our engineering documentation, and I'm also + +Scott Carruthers: Not entirely clear on the comment of unreliable sandbox. So I don't know if anyone else might have some further thoughts on the kind of the Genesis for this. + +Maxime Beauchamp: Yeah, so what he's talking about is to run Cloud those locally. and this is sort of like the indexer and we + +00:10:00 + +Maxime Beauchamp: apparently run the indexer since Genesis and there's a few reasons why we need to have the whole. Database locally as well for the API to run properly or the indexer to run property. So it's a bit tricky for new developers to start working on that locally on Carlos. So yeah, that was the issues that we had with yarrow as a new team members start working on combos. And we discussed it a few times I can see that this issue is created last week. and I think it's a bit dated as we + +Maxime Beauchamp: We were taking it new Solutions. there's another issue I think for tracking this on cloud will austerity so I'm not sure… + +Scott Carruthers: Okay. + +Maxime Beauchamp: if that issues needs to be there. + +Maxime Beauchamp: entirely + +Scott Carruthers: How about would this be a good Next Step Max? I could assign you to this issue and then you could do a review of the issues that's opened in. The cloud must repository and then determine if it's appropriate to close this issues. + +Maxime Beauchamp: Yeah. + +Scott Carruthers: Okay. + +Scott Carruthers: All Yeah Max obviously as a progresses if you need our support. On this in any way, I'm sorry. I have a better understanding of the issue and based on the indexer. It's if not necessary to work with the full may not database. So yeah, obviously as you review that other issue or if you need a support on this, just let us know. + +Scott Carruthers: so I believe that leaves us with two remaining unassigned issues. So the next one is provider should release resources immediately after. Not accepted or the deployment was closed. So I'm rather familiar with this issues. Andy you open this so you may have some thoughts as well. I'll probably assign this to Archer for initial triage and he can triage it further from there, but I know that I was looking at this I think. you and I were looking at this on the same provider and seeing that in my experience the inventory operator when a bid was closed. There was a lag possibly. And this is a very rough approximation but in my testing maybe a lag of two to five minutes between + +Scott Carruthers: when the bid is closed and when those resources are made available again via the inventory operator, so I believe that's generally the issues that were talking about any for their thoughts or clarifications any + +Andrey Arapov: yeah, sometimes it was taking even up to 35 minutes depending on which provider and which condition so it's kind of + +Andrey Arapov: It's not too deterministic to really reproduce in terms of time. But yeah, so, whenever there are all the requests in the network and providers are bidding on them. And even if they did not need lost a bit those resources on some providers in some cases not all they are getting locked up for longer than they should because normally if rather didn't beat on it or if it did but it lost that beat supposed to immediately release this resources. I'll never it's okay to log them up well with this open because it can accept it. But if it wasn't accepted and supposed to release and that can create problem and provider will be just getting running out of resources in case if somebody will be generating lots of requests every 15 minutes and sort of attack sort of + +00:15:00 + +Andrey Arapov: And yeah, I think it's important to look at this closer and I think it started happening since the upgrade to the provider From 0.0.4. So yeah, but at least it doesn't happen across all the providers and only specific cases. + +Scott Carruthers: yeah, so in my experimentation with this, so I was closely looking at the status of the bid on chain and if they was created via another provider or just the bid was closed from the loy. So the deployment was closed. I witnessed that they've close immediately on chain in the inventory operator would take about three to five minutes to recognize and release those resources. I was never able to reproduce the Scenario of the 30 to 45 minutes and I was even testing it on the provider that reported it. So we were somewhat of the belief that there was something else in play. So Andy, have you actually observed or you able to replicate a 30 to 45 minute? Failure to release the resources because I've never seen anything. That extreme I know. + +Andrey Arapov: Yeah, the day that I've tried it I reproduced it and that's what the sticker describes and can you try to scroll down? Maybe there was some update. Maybe to the bottom of it. + +Andrey Arapov: And slightly up if it speaks something about this time delays or something. + +Scott Carruthers: So this says after six minutes, it's still locked. And I did. + +Andrey Arapov: Yeah, so yeah, it was just additional test that I checked if there is something about this five, I mean the mid timeout which is the old value so it was locked for longer than six minutes and then I just didn't want to wait longer. I just realize that probably it will be there for longer time because I run several tests on this problem one of this providers and this one particularly. And yeah, I mean, of course I can run more tests to see if I can still reproduce it. But I believe it's still there and don't think it will be just gone by itself. + +Scott Carruthers: No, I don't think it would be gone by itself either and I think it's very easy to reproduce. So there's a several minute delay. So I was just curious that if we were able to reproduce that extreme delay of 30 to 45 minutes, but here you have an example of six minutes, which is obviously abnormally a long time. So, that's fine. + +Andrey Arapov: Yeah, in the beginning in the top of the ticket. I think I wrote there is Christian to 25 minutes as well. Yeah, yeah,… + +Scott Carruthers: Yeah, okay. + +Andrey Arapov: because I didn't just put the numbers randomly. So it's essentially run some tests on my own. + +Scott Carruthers: Yeah, I'm just saying that the most I could reproduce was three to five minutes but it looks like you were able to reproduce something much greater. So okay, it's fine. + +Andrey Arapov: Yeah. + +Scott Carruthers: the thoughts are comments on this issue. + +Andrey Arapov: not really but I think maybe it's related to the inventory operator the way how it pulled the data because normally what I know, it pulls every 15 minutes and there are some issues if you look at the next ticket 192 why the reports successfully High multiplic in order to operate his hair, yeah this one. so I think it's kind of connected slightly upper one into + +Andrey Arapov: and I will + +Andrey Arapov: about online to have + +Andrey Arapov: So you can open it up. + +Scott Carruthers: yeah, yes so this is actually an issues that this provider ping me yesterday as well. + +Andrey Arapov: So I think + +Scott Carruthers: So yeah, he goes through a period of time where so the provider I'm talking about is + +Scott Carruthers: deathless This is just and… + +Andrey Arapov: yeah. + +Scott Carruthers: then yeah, he's showing so I've seen this issue where we have abnormally and I know that Max has seen this issue before as well. We get abnormally large GPU alcatable. statistics I have never seen this with anything outside of gpus but yeah deathless is definitely currently experiencing this with a Ram allocatable + +00:20:00 + +Andrey Arapov: Yeah what I think is that when we upgraded the internet operator on the provider to all point, five four, I mean, so when we jumped from 0.4, I think even before in this older version of Provider, sometimes when the media device plug-in is getting stopped or restart or just being in the beginning of the insertation. It has in impacts on the amount of the GPU provider sees and when you restarted or when you wait a little bit and then it kind of picks itself, at least it was back then with 0.4 but with 0.5 when you were one + +Andrey Arapov: Because there is entirely changed the way how we winterize things from understood. I think it doesn't self recover. So it needs to be manually restarted as soon as you see this high of excessive amount of Resources and the last command one before the last one. I've just updated five hours ago. Yeah, because I was reporting on the North quite often recently. I was testing these growth AI seeing you so I had to was looking up the GPU in some conditions and I need to restart an old quite often and after it was about it up and I've noticed that issues was always coming back again. So I needed to restart the interior operator. Sometimes it was even reporting zeros. + +Andrey Arapov: So kind of interesting stuff, but they definitely needs to be getting the soft recovered from this issues. + +Scott Carruthers: I was just reading through your comments from five hours ago as well. So yeah, I've Actually reclassified this as a p zero, I think this needs some urgent attention. and it's already assigned to Archer. So + +Andrey Arapov: I think so. But another hand I was thinking when it doesn't show that amount of available resources is unusable like zero or something. So it shows that you have way too many resources one hand and why I'm saying it maybe not be zero, but maybe if you want because providers are able to offer the resources, they just able to offer to much of the resource. So then they have so well another hand. Yeah. It's probably zero. + +Scott Carruthers: yeah, so deathless actually reported yesterday that for some reason when he's getting a high memory El capable stats. so this is a strange issue. understand exactly where the correlation in this is but deathless yesterday was reporting that so he only had a certain node that was reporting incredibly High memory allocate allocatable statistics and whenever was in play and whenever that issue is current he was unable to rent out GPU or he wasn't deployers were not getting bids from his provider if + +Scott Carruthers: The sdl and so again this is kind of strange because you want to think there's any correlation here, but he was reporting and was able to reproduce it. When those memory lkdable stats are very high. If a sdl is requesting a GPU and it has a wild card for the model his provider won't bid if you specify RTX 30 90 or whatever. He has a specific model it will bid. But if he's using a wild card for the GPU, it doesn't bid during so I guess that's still debatable if it's a P0 or P1, but it definitely is having other ramifications. I think it's something that we need pretty urgent attention on. + +Andrey Arapov: The other Handler I think it should really be zero and also hurricane provider. I noticed today. also the comment to the second last one, but European provider is experiencing this issues now persistently,… + +Scott Carruthers: Yeah. + +Andrey Arapov: even if I restart the inventory operator, it's still keeps reporting with the worker now,… + +Scott Carruthers: Yes. All right. + +Andrey Arapov: so it's persistent issues. definitely + +Scott Carruthers: I would actually say this may be one of the most severe issues going on in the network right now. + +Andrey Arapov: no. + +Scott Carruthers: So yeah, we'll definitely try to get some urgent attention on up. + +Andrey Arapov: Okay. Thanks. + +Scott Carruthers: and then + +00:25:00 + +Scott Carruthers: Yeah, no, probably. Yeah,'s Zeke can death was just joined. So yeah, we were just going through the discussion of Resource the inventory operator is given abnormally allocatable amounts at where we are previously just seen on gpus but now we're starting to see it on memory as well. So the case is the issues fully up to date and I requested it from a P1 to a P0 because we understand this is probably the most urgent issue that we have on the network right now. So requested to a P0 to try to get some attention. + +Scott Carruthers: Okay, and then that leaves are very last unassigned issue. Andy do you want to so this was open some two weeks ago do you want to is this + +Scott Carruthers: so the provider stops responding to the status endpoint are you saying that they provide ourselves responding both to the rest API 8443 status endpoint and the grpc part of a44 simultaneously here + +Andrey Arapov: Yeah, it's the most important honestly and it's when the paper writer was enabled. Actually, I have not tested it back again because there are some other issues on the hurricane provider such as the abnormal reports of the resources, And whatever there no restarts. No issues. Okay. I am that's my last command that I said that I want to enable the appealing back again to see if I can still reproduce it, but I haven't got back time to do that issue because those focusing on the other issues and that other issues also. Boiled up with the abnormal report of the resources of thinking maybe that's one of the reasons for that for this issue. I will need to get back to it. + +Scott Carruthers: Okay. + +Andrey Arapov: But I think it's not. + +Andrey Arapov: Be zero of no nor P1 because I didn't have anyone reporting this issue. + +Scott Carruthers: Yeah, I have it as P2 and I'll just put in the comment that waiting for their testing by yourself. + +Zeke E: And I saw someone on Discord this morning put in. + +Andrey Arapov: Yeah. + +Zeke E: A basically saying that it happened to them. It's in the providers Channel. + +Zeke E: + +Scott Carruthers: So just for clarity what exactly did they experience? + +Zeke E: There so they said that Port 8443 isn't reachable. But April 4 is 844 is so + +Scott Carruthers: Okay. + +Andrey Arapov: That must be another thing. It must be that they need to update the engine X Ingress operator config to allow the port 844 because this one is the new part that was enabled since we upgraded the providers to version 0.5. So Yeah,… + +Zeke E: Katrina that's probably up. + +Andrey Arapov: so Zeke if you can just bring me the link to this conversation. I will reply to the person. + +Scott Carruthers: Wait, so just for clarity. I thought Zeke were reporting the opposite. So I thought you were saying that a44 they grpc. Is working… + +Zeke E: The grpc is working. Correct. + +Scott Carruthers: but a four for three is not okay. + +Andrey Arapov: There's the opposite. Okay. just let me know. + +Zeke E: Yeah, I'm sending it to. + +Andrey Arapov: Yeah, yeah. I'll take a look. + +Scott Carruthers: so that concludes our review of unassigned issues are there any For the discussions on any of the issues that we talked about or issues that we haven't talked about this morning that anyone would like to review further. + +Scott Carruthers: Okay. + +Zeke E: I might have missed this but is there a timeline for shm enablement over SEL? + +Scott Carruthers: so as you are probably aware Zeke a number of the cash core team are a kubecon today. So yesterday we got the update that Arthur has so basically Adam about an edge was the primary engineer working on this so it's code complete and we're now just waiting they release I've actually already staged to documentation update so that as soon as this is release, we'll have sdl examples and also, Guys who are providers adding necessary attributes to their provider config for shm supports or ready to go and the code is completed. We're now just waiting for the release that will unlock as shm with team members at kubecon. + +00:30:00 + +Scott Carruthers: I'm not sure when that's going to happen and what exactly we're waiting for. But yeah, that's basically the update that I have. Is this Coco complete and we're just waiting for the release to be cut that will support sham. And as I said, once that happens all the documentation and other bits are updated, so I actually was wondering if we might actually see that release this morning. That didn't happen if you want to. Maybe reach out to Arthur when he's available. Maybe you could get a ETA on when we think that release was going to become available. But that's all the information I currently have. + +Zeke E: Okay, sweetie. It's perfect. Now we can actually Deploy srock on the cost. + +Scott Carruthers: yeah, without the provider having to go in and yeah. + +Zeke E: And manually a bit. Yes. + +Scott Carruthers: Okay, so yeah great question Zeke for because there may be other people that are wondering that because there's been some chatter about this system native support and like I said is code complete so we should be releasing that good update on that and if there's not anything else that concludes our issues review, so I'll hand it back to you Tyler. + +Tyler Wright: Thank you very much, Scott Andre and others. Again, if anybody has any issues that they see over the next couple of weeks, please feel free to add comments any open issues already or if you see any new issues go through the proper mechanisms to again Ask insiders vanguards another members of the community and then if it gets escalated from there, then it'll be added to the support repo. As Max kind of covered they're also is a cloud most repo where any issues related to Cloud most live. I know the cloud most team does a great job of if anybody has any issues that they see in Discord and ecosystem Cloud most Channel or again elsewhere Cloud must team great issues for those and then continues to update those issues so you can monitor + +Tyler Wright: The Cardinals repo as well as roadmap and the support repo to see all the things that are being worked on. + +Tyler Wright: cool, At next part of the agenda. We usually see if any community members are here to give any updates on. Behaviors or themes I've seen and Discord or other channels related to support real quick. I know that the last couple of insiders meetings. There's been a real effort to improve issues around spam and Discord server. There's been a number of keywords that have been added to a list for the block lists and it seems like there's been some significant less spam. We'll continue to monitor that and talk about that during the support repo as well. As this is something that Akash insiders are actively talking about during The Insider office hours. + +Tyler Wright: But again, if anybody has any issue related to spam feel free to reach out to an Insider or myself and will continue to monitor that very closely. Is there any other issues I see Zeke here who has recently been made a Vanguard. So again, shout out to all that Zeke does Zeke have you seen anything in Discord? I know that you just shared some stuff with Andrey related to Port issues. But is anything else thematically that you've seen over the last couple of weeks and Discord that might be worth sharing with the Core team and the other members of the community. + +Zeke E: I mean right off the bat out in the auto model has been very very helpful. And catching spans. So I really like that. + +Zeke E: In terms of schemes. I think that's kind of just been the main one. I mean, yeah, nothing. I can really think about the top of my head. Other than that. + +Tyler Wright: I know that again deathless and some other members of the community have brought for some issues in provider Channel deployment channel so much appreciate content participation obviously deathless giving a number of people feedback sharing opinions thoughts and helping people with the class. So again much appreciate those efforts if anybody sees any glaring themes or issues related to whether it be use of product any of the tool documentation anything that could use update to make the user experience better for a cost users again, feel free to drop something and big support or feel free to attend another special interest group whether it be docs otherwise, + +00:35:00 + +Tyler Wright: Is there anything that anybody wants to discuss that's support or core code related that hasn't been discussed already? + +Tyler Wright: Real quick just for the consensus of this group. The Sig chain issues. It relates to the main Net 10 is still open. I know that has again passed on vote and then the upgrade is successfully happened last Wednesday. Is it fine if I close that issue? For repo just want to get thumbs down from this group. On closing the sigchainish cool. + +Tyler Wright: I will close that issue. I know there's a number of issues that will be followed upon, specifically 195 related to the memory of our archival node. I know that Max will follow up on issues number 194 and figure out where that should go and then issues 193 and 192 which are quite high priority as well as 190 will be major focuses over the next couple of weeks. So we'll look to follow up with those certainly at the next six support meeting if not sooner. + +Tyler Wright: Is there anything else that anybody wants to discuss before I'll let you all go. ahead Scott + +Scott Carruthers: It's just one thing to mention to this group to help us support the community and just make sure that everyone is aware I believe is over this past weekend. We migrated to the new documentation site. So definitely. if you see any chatter in the community, like any missing documentation or any formatting issues or anything of that nature and just so that you're aware in general if you go to akash dot Network, which is right now redirects to network with the path of Docs. So you can visit either of those paths or it's all also the documentation site that is linked off of the network home site. + +Scott Carruthers: So yeah, just make sure the entire group is aware so it should be very clean. they developers of the new documentation site did a diff on the old documentation site. and so hopefully there should be complete parody and there's not any documentation missing so this group is aware. We went through that migration and please let us know if you see any anomalies or any missing information + +Tyler Wright: Yes, great call out If you all see any missing information or anomalies or formatting issues, please drop a message and Sig docs with the specific documentation linked that would be extremely helpful and again will continue to push to have that as clean as possible. But do want to shout out the efforts of Scott and Andre who were very Hands-On and making sure that the documentation matched up as much as possible. I know that push and his team, we're very busy and we're trying their best but much appreciate Scott and Andre's oversight on making sure that documentation is clean and ready to be used by the community because I know a lot of time effort and work put into. + +Tyler Wright: Both like updating the developer documentation. Also the engineering documentation that's been added more recently. So again, thank you very much for bringing that up Scott and all the efforts here. + +Tyler Wright: if there's nothing else then again much appreciated everyone's time and efforts today during this call again. Feel free to drop any comments inside any specific issues. Please stay involved in Discord. And if you see anything worth calling out, please call it on the six support Channel Sig docs or any other respective channel that makes sense and again much appreciate everyone's time and energy today. me, + +00:40:00 + +Tyler Wright: he does not have to speak but I will call out that again the overclock Labs core team. Obviously Max and Andre is a part of that have also added another senior software engineer and Andrew who is on this call and will continue to join these calls in the future. He's working on a number of things behind the scenes and getting his feet wet. But he's a very very cease and go developer that again has gone for the rigorous process of bedding amongst the team and he's been enjoyed to work with the thus far so I'm sure many folks here and listening in we'll get to know him more as time goes on but just want to shout out does not have to say anything at this time. + +Tyler Wright: I hope everyone has a great rest of their day. Thank you very much. For participation today. There's a number of sigs again a couple of sigs got moved from this week to next week because of all the travel, but please add to your calendar Sig clients and Sig providers. I'm sure we'll do some talking about provider auditing some other stuff related to Future Discovery, and I know a couple of client related things. So again Market calendars for next week, because it'll be a basic week next week, but much appreciate everyone's time and energy today. Hope everyone has a great rest of your day. Thank you very much. + +Scott Carruthers: it's + +Andrey Arapov: Thank you. + +Meeting ended after 00:41:46 👋 + From 95b3650550609dc5b80b7dc713bc880496257591 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 26 Apr 2024 14:41:10 +0000 Subject: [PATCH 045/138] Create meeting notes for Sig-docs #14 (#560) * Create meeting notes for Sig-docs #14 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 014-2024-02-27.md add transcript to the meeting notes Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-documentation/meetings/014-2024-02-27.md | 141 +++++++++++++++++++ 1 file changed, 141 insertions(+) create mode 100644 sig-documentation/meetings/014-2024-02-27.md diff --git a/sig-documentation/meetings/014-2024-02-27.md b/sig-documentation/meetings/014-2024-02-27.md new file mode 100644 index 00000000..4c7c0cb5 --- /dev/null +++ b/sig-documentation/meetings/014-2024-02-27.md @@ -0,0 +1,141 @@ +# Akash Network - Docs Special Interest Group - Meeting #14 + +## Agenda +- Welcome and Introduction +- Review of Documentation Updates +- Community Contributions and Collaboration +- Addressing Documentation Issues +- Future Plans and Initiatives + +## Meeting Details +- Date: Tuesday, February 27, 2024 +- Time: 7:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + +## Participants +- Andrey Arapov +- B S, Benjamin B +- Dan Pavel Sinkovicz +- Dimokus +- Scott Carruthers +- Tyler Wright + +## Meeting Notes +### Tyler wright +- Welcome to SIG Documentation monthly meeting #14. +- Purpose: Review new documentation updates from the past month. +- Encourage contributions from the community due to small core team. +- Scott Carruthers praised for improving documentation quality. +- Funds available for specific documentation contributions. +- Engineering documentation for technical users created by Scott. +- Issue with live documentation being addressed by Akash website working group. +- Transitioning users to new documentation URL: /docs on Akash Network website. + +### Community Contribution to Documentation +- Community members asked to contribute to website revamp repo for documentation. +- Specific instructions provided in the repo. +- Uniformity and regularity in documentation encouraged. +- Previous meeting discussed contribution methods: written and video documentation. +- Combination of written and video documentation encouraged. +- Discussions on adding videos to current documentation structure. +- Experimenting with different documentation approaches. +- Scott working on experimental documentation for provider feature Discovery service. +- Documentation under construction for providers upgrading with GPUs. +- Issues with one provider causing rework by the core team. +- Documentation for provider feature Discovery upgrades to be modified accordingly. + +### Relayer Documentation +- Emphasis on the need for more relayer documentation for Akash. +- Dan mentioned desire for simple guide to make relaying on Akash easier. +- Dan tasked with creating relayer documentation, with support from the community. +- Invitation to ask questions or share comments in the SIG Documentation Channel or privately to Tyler Wright. +- Recognition of efforts from the core team and Dan for their contributions to documentation. + +### Future Plans and Initiatives +- Scott, Andrey, and community members acknowledged for their efforts in improving documentation quality. +- Continuous refinement of documentation through battle testing and user feedback. +- Encouragement for users to provide feedback on documentation gaps or consistent questions in the docs channel. +- Rewards available for contributors to documentation. +- Recap of developments since the last SIG docs monthly meeting. +- Discussion on alternative ways to contribute to documentation for those less inclined towards writing. +- Emphasis on collaboration and support from community members in structuring and optimizing documentation. + +### Closing Remarks +#### Tyler wright +- Tyler Wright encouraged questions on documentation. +- Mentioned updates from Thomas Greco and highlighted Sig documentation. +- Acknowledged Europlots' video contribution on port forwarding. +- Encouraged feedback on documentation and offered rewards for new documentation contributions. +- Invited contributions and urged spreading the word to the community. +- Expressed appreciation for attendees' time and contributions. +- Ended the meeting, thanking everyone. +- Emphasized the importance of various forms of contributions beyond traditional documentation, such as videos or Medium posts. +- Highlighted the significance of documentation for community support, including 24/7 support on Discord. +- Stressed the need for user-friendly documentation to facilitate onboarding new users to the Akash Network. + +## Action Items +- Dan to create relayer documentation for Akash, seeking input and support from the community. +- Tyler Wright to provide instructions for contributing to the website revamp repo in the meeting notes and SIG Documentation Channel. +- Scott to provide updates on the progress of experimental documentation related to provider feature Discovery service. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to Sig documentation monthly meeting number 14. During the special interest group for documentation monthly meetings. The group goes over any new documentation that has been updated over the last month. So that folks can ask any specific questions to the documentation writers. this is certainly a special interest group where we're looking for more contributions from the general Community as many know the overclock Labs core team is very small and as momentum continues to push many of the efforts of the core team are now being focused on feature additions the core product and again continuing to improve the Akash Network. + +Tyler Wright: Scott Carruthers who's on this call has been Paramount in taking Sig documentation from what it was which was very fragmented a couple of years ago to something that is very complete. And again, the documentation has gone through rigorous testing from Andrey and other members of the community to make sure that it solves users issues. So much appreciate Scott Andre and others for all their contributions to documentation as we've moved into 2024. There are specific. Funds available to those that want to contribute to specific documentation. + +Tyler Wright: I know over the last month again since the last meeting during Sig documentation meeting number 13. The group went over new ways in which we're asking folks to contribute to documentation. as previously mentioned the website revamp that went live a little while ago, maybe like a couple weeks ago. The docks are now a part of that website revamp. + +Tyler Wright: There are some current issues because Scott Carruthers also did a great job of creating from scratch engineering documentation. So for those that are trying to contribute to the core product those that are end testing. Those are really looking to do things. They're a little bit more technical on that cost network besides again deploy and set up a provider. there's documentation that's been created for again that specific engineering audience. The documentation There's a little bit of a Issue as we went live, but again that issue is being rectified by the working group for their cost website as we speak. + +Tyler Wright: So once that's updated we're going to certainly be pushing users towards the new documentation a slash docs as opposed to Ducks data network. But for anybody here on this call that's looking to contribute to documentation to ask is that you all contribute to the new Ducks so a network and slash docs and then again those changes will be reflected once merged in the new docs and we'll make sure that the structure is updated. I know that's the members of the core team have their own flow, but for members of the community that want to contribute to documentation, we ask that you contribute to the website revamp repo Inside of that repo there are specific. Instructions for those that are looking to contribute to documentation. + +Tyler Wright: I'm going to drop those instructions inside of the chat for here and I'll make them available in notes as well for anybody that needs them. But again because of the way that the new website was constructed, it should be significantly easier for folks to contribute to documentation and there is a flow that we're asking folks. to follow so that there is some uniformity and regularity and how documentation looks especially as we again continue to get contributions from the community. + +Tyler Wright: The last meeting we talked at a high level about again how folks can contribute and again, I've attached how to contribute in the chat here members on that call talked about specific ways that they wanted to contribute including a combination of written documentation. That'll be added to the cost on Network slash docs as well as some video documentation that can either be added on YouTube or over time. I know there's been discussions the last couple of meetings about when applicable adding videos to some of the current structure the documentation so that Folks at learn in different ways have the ability to read and follow documentation and copy code Snippets when applicable or others can just again, I'll pull up a video and follow along with that video. So this is a number of ways that we're looking to for folks that contribute to documentation. + +00:05:00 + +Tyler Wright: Since the last meeting, I know there's been some experimental documentation that's been worked on and continues to be worked Scott on the call and doesn't have to go into deep in depth because I know that documentation is still a work in progress right now, but with the launch of the provider future Discovery service, there's some documentation for providers that have gpus that are looking to upgrade again that documentation is under construction right now. Some of the providers have a successfully upgraded but there was a small issue with one provider that caused. Some rework from the core team and so again documentation related to provided feature Discovery upgrades will be changed and modified to reflect some of those changes. So look out for that documentation coming very soon. + +Tyler Wright: In addition to that I think Dan kind of mentioned it. There is certainly a desire and need for some more relayer documentation. So for folks that are looking to relay on a cost making it easier and having a simple guy for them to go through the steps would be very helpful. I think it would contribute to + +Tyler Wright: More people using the relayer so Dan on the call today is going to help with that documentation. And if he has any questions comments, you can feel free to drop them in Sig documentation Channel where folks like myself Scott Andre other members of the community can provide some insights or he can ping me privately. So again want to shout out the efforts of the core team as well as Dan for their contributions to documentation. + +Tyler Wright: One thing that we ask at every meeting is for folks that want to contribute, again, I'm of the opinion that Scott has done a great job along with Andre and many other members of the community to continue to battle test documentation continue to improve documentation. I know Andre icc's folks that are interacting with documentation and maybe having some issues. There's small little tweaks that get discussed and get added so that again users can come in as quickly as possible be able to build the provider or be able to deploy on the network. So as we continue to move forward if anybody sees any documentation + +Tyler Wright: gaps or if anybody sees any consistent question, can we go over this during six support as well? But if anybody sees any consistent questions that maybe aren't specifically outline and documentation and could be improved by documentation. Feel free to drop those suggestions in docs channel so we can discuss those and then again if anybody wants to step up and contribute to writing that documentation, there are rewards available for those that want to contribute there. + +Tyler Wright: So again, we've talked about what's happened at the last Sig cs monthly meeting. We've talked about some documentation that has been developed over. The last month or is in the pipeline as we continue to move forward. + +Tyler Wright: Kind of think of what else we can discuss. Again for folks that maybe don't feel like writing is there best medium? It'd be great to still map out how you can go through steps. And then I know that there are folks on this call that maybe a little bit less technical that can developing out some of that documentation in the same sort of format as is today. So again, even if you are Technical and don't feel like you're a strong writer, there's still ways that you can contribute to supporting documentation, whether it be testing documentation that's written by others and helping to optimize or again just like structuring out documentation and getting support from other members of the community to help get that documentation merged and live + +00:10:00 + +Tyler Wright: does anyone have any specific questions related to documentation that they want to discuss today? + +Tyler Wright: All The last thing I will say is and I'll link to it real fast right here on this pad that I'm showing I do want to remind folks that again if there's docs obviously right here, but there's other ways in which folks can contribute specific guys, whether it be video or medium posts that maybe fall a little bit outside of specific documentation, but are ways that folks contribute to either writing or doing video around specific initiatives, whether it be deploying on a cost being a provider on the cost or other specific topics that might be interesting to you. So again, + +Tyler Wright: Docs is certainly something that many people in the community interact with quite often. It is a support goal for vanguards and insiders that are giving 24 by 7 support inside Discord and other channels docs are a way that again are supplemental tools that the community can rely on and they can follow step by step. So we want to continue to make those as fine-tuned and is friendly to the user as possible so that we can continue to onboard more and more users to your class Network. + +Tyler Wright: All I know I've been on a monologue. Does anyone have any specific questions about anything documentation related? + +Tyler Wright: If not know where is we can certainly cut this meeting short. I know there will be some updates from Thomas Greco who I will see you later today. So I'll have him put any updates that he has and Sig documentation big shout to Euro plots who again continuously makes videos. I know that he just made a video on port forwarding. So again, we'll make sure that that gets added to the community contributions area and could be a reference video for those that might be having issue with that part of the provider set up. But again, please everyone on this call as you see people + +Tyler Wright: In the community, whereas yourself or interacting whether it's deploying or being a provider on a cost. Please feel free to leave any notes comments about documentation, things you like about it things that you think could be improved again gas and documentation and let's talk about those gaps. And then again, there are specific rewards that this group has access to do the work to again write new documentation that will be merged into a casa Network / stocks. + +Tyler Wright: So if there's nothing else again, if anybody has any questions about upcoming contributions, feel free to drop those in sig-docs much appreciated everyone's time and effort being here today. Again, please let me know if you need anything, but anybody has any contributions that they want to make to a documentation, you're more than welcome and invite your friends. I think this will be some part of the zeli activities as well. So again, this is an initiative that we're certainly looking for more Community contributions or so again, please let folks that you see in Discord or other channels know that want to get more involved. This is certainly a way they get involved earn akt understand more. how it costs works. So again much appreciate everyone's time today and + +Tyler Wright: Sure, we'll catch up and have more folks here at the next six docs monthly meeting. Hope everyone has a great rest of your day. Thank you. As always. + +Andrey Arapov: I think we are. Going on. + +Tyler Wright: everybody YouTube + +Benjamin B: for your own but + +Meeting ended after 00:14:21 👋 + From 8379a026d1415265cf08bdd2cb827320f93d5254 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 26 Apr 2024 14:42:47 +0000 Subject: [PATCH 046/138] Create meeting notes for Sig-economics #15 (#561) * Create 015-2024-04-03.md Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 015-2024-04-03.md added transcript to meeting notes Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-economics/meetings/015-2024-04-03.md | 356 +++++++++++++++++++++++ 1 file changed, 356 insertions(+) create mode 100644 sig-economics/meetings/015-2024-04-03.md diff --git a/sig-economics/meetings/015-2024-04-03.md b/sig-economics/meetings/015-2024-04-03.md new file mode 100644 index 00000000..9f1f34cd --- /dev/null +++ b/sig-economics/meetings/015-2024-04-03.md @@ -0,0 +1,356 @@ +# Akash Network - Economics Special Interest Group (SIG) - Meeting #15 + +## Agenda +* Updates since last monthly sig-economics meeting. +* Updates on provider incentives. +- Open discussions on recent proposals and events +* Open up to community for ideas or concerns. + +## Meeting Details + +- Date: Wednesday, April 03, 2024 +- Time: 10:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + +## Participants + +- Andrew Gnatyuk +- Cheng Wang +- Maxime Beauchamp +- Nick Merrill +- Robert Koschig +- Rodrigo Rochin +- Scott Hewitson +- Tyler Wright +- Zach Horn + + +## Meeting Notes + +### Scott Hewitson: +- Discussion planned on provider incentives and updates. +- Scott reviews recent community proposals and mentions upcoming events. +- Highlight on proposals including upgrades, IBC channel, open source element rejection, and Q2 events resourcing tour. +- Not much discussion on the praetor proposals on GitHub, but they might go on chain soon. +- Scott invites Cheng to elaborate on specific proposals or topics. + +### Cheng Wang provided an update on provider +- Cheng Wang provided an update on provider incentives: + - Approximately 60% of the initial phase one budget allocated + - Committed pool consists of long contracts with overclock Labs core team and providers + - Resources being brought online include h100s, a100s, a6000s, and 40 90s + - High demand for 40 90s due to inference use cases + - Some budget spent on bolstering storage for AI efforts +- Phase Two: Liquidity pool under construction, specifications being ironed out, launch expected within two weeks +- Process for launching phases: Internally review specs, submit to GitHub for community feedback, then launch on chain +- Phase Three: R&D bucket, potential allocation towards Next Generation chips (e.g., AMD support, Nvidia Blackwell architecture) +- Community engagement encouraged for feedback and questions + +### Scott Question on Provider incentives +- Scott Hewitson inquired about joining the provider incentives pool +- Cheng Wang outlined the process for joining: +- Reach out to Tyler, Hewi, or anyone else in the group +- Contact via email or tweet +- Requirements: high-end server-grade chips, data center level two or higher, configuration and reliability standards +- Scott thanked Cheng for the information and suggested pivoting away from provider incentives discussion + +### Fluctuations in GPU capacities +- Andrew Gnatyuk asked about the fluctuations in GPU capacities +- Tyler Wright explained that maintenance and upgrades to providers are causing the fluctuations +- Maintenance announcements are made in Discord and elsewhere to inform the community +- Emphasis on improving provider stability to minimize downtime during maintenance +- Zach Horn added that despite fluctuations, there's an overall upward trend in GPU capacities +- Current total capacity reached an all-time high of 363 this morning +- Long-term trend is positive despite short-term fluctuations + +### Demand to utilize the network's GPU +- Andrew Gnatyuk asked about demand to utilize the network's GPU capacities +- Cheng Wang mentioned pending partnerships and integrations in the pipeline +- Majority of 49 resources to be absorbed by upcoming integrations +- H100 and A100 resources pending integration with a strategic partner for deployment +- Cheng anticipates resources will be soaked up once integrations complete +- Announcement of partnerships planned as part of marketing campaign upon completion of technical work and testing +- Cheng emphasized the importance of fully tested integrations before announcements to avoid disappointment +- Andrew expressed excitement about upcoming announcements +- Cheng confirmed plans to announce partnerships when fully operational + +### Praetor Acquisition Proposal +- Scott Hewitson asked Cheng Wang about the Praetor acquisition, which has been on GitHub for about a week and will likely go on chain soon +- Cheng Wang explained that the Praetor acquisition is similar to the Cloudmos acquisition from about eight or nine months ago +- The goal is to merge Akash Console and Cloudmos into one native experience for tenants +- Praetor serves as a provider management tool, and there's consideration about merging it into Console as well +- The acquisition aims to accelerate development speed and leverage devops capabilities +- Praetor's team members will join the Akash core team to further accelerate development +- Proposal will be put up on chain today, and Scott suggested encouraging discussion on Discord before finalizing the proposal +- Aim to finalize the proposal by the end of the week + +### Questions on Acquisition +- Andrew Gnatyuk inquired about the fee structure for Praetor now that it's proposed to be integrated into Akash +- Cheng Wang mentioned that the proposed plan is for Praetor to be completely open source, potentially eliminating any fees +- With community backing and funding from the core team, there's less pressure for monetization at this point +- The aim is to make Praetor as easy to use for community members as possible +- Any monetization elements in the future will be thoroughly considered and discussed within the community + +### Coinbase learning rewards proposal +- Scott Hewitson requested an update on the Coinbase Learning Rewards proposal, which passed recently +- Cheng Wang provided details on the proposal: + - Budget allocated: $8 million USD + - Multiple campaigns planned over time, each lasting a few weeks + - First campaign focused on education, potentially including quizzes and staking opportunities + - Subsequent campaigns to be more interactive, involving Akash applications and tools +- Plans to iterate based on campaign performance and user feedback +- Zach Horn emphasized the significant opportunity to reach tens of millions of users through the proposal +- Scott invited questions from the group regarding the Coinbase Learning Rewards + +### Key Performance Indicators (KPIs) for the Coinbase Learning Rewards campaign +- Andrew Gnatyuk inquired about Key Performance Indicators (KPIs) for the Coinbase Learning Rewards campaign and its impact on market volume +- Zach Horn outlined primary KPIs for the campaign: + - Total number of users interacting with campaigns + - Usage metrics: impressions, completion percentage, rewards claimed + - Staking participation rate if staking Quest is live +- Scott Hewitson emphasized that the campaign has a max reward per user and will continue until funds are exhausted +- Cheng Wang highlighted the significance of the campaign: + - First paid awareness campaign in Akash Network history + - Opportunity to reach millions of users on Coinbase, potentially high-value users + - Education about Akash's unique value proposition and intersection with AI and crypto + - Increased access to AKT tokens through Coinbase integration, important for utility and institutional custody +- Andrew Gnatyuk acknowledged the significance of the campaign + +### General discussion on strategies to increase trading volume for Akash +- Andrew Gnatyuk raises concern about trading volume for Akash, aiming for improvement. +- Cheng Wang explains that trading volume cannot be directly influenced and varies based on market dynamics. +- Cheng Wang highlights Akash's historical trading volume, averaging over $10 million daily. +- Cheng Wang discusses the importance of considering trading volume in relation to market depth. +- Cheng Wang expresses skepticism about projects with disproportionately high trading volume compared to market depth. +- Cheng Wang emphasizes Akash Network's mature and decentralized token holder base, indicating organic trading activity. +- Andrew Gnatyuk acknowledges understanding. + +### Action Item: +- Group encourage to have discussions on Discord regarding the Praetor acquisition proposal before finalizing it by the end of the week. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Scott Hewitson: All right, gmgm everybody. Is Wednesday April 3rd for this month's installment of Sig economics? Looks like we have a little bit of a light crew today. We'll talk about the last call kind of talked about provider incentives a little bit and the status on that. I know Cheng will talk about that a little bit more as And then just a few questions from the community. I'll take a look at proposals that have gone. I think the last one was in March 6 so Quite a few proposals. We had a suffered upgrade accelerate past. There was IBC channel that the coinbase learning rewards passed + +Scott Hewitson: there was a open source element that was rejected. And then the Q2 events resourcing tour proposal is live. So if you have not voted on that, please do so. Any big discussions? I'd say one of the bigger ones hasn't gotten a lot of chatter, but the pretor open source and pray tour. Proposals on GitHub has not gone on chain yet. We'll probably do that soon. So with that Cheng, do you want to talk about any of those in particular and any order specific order? + +Cheng Wang: Yeah, I guess. Yeah. + +Scott Hewitson: Maybe provider incentives taking you get off. + +Cheng Wang: Provider incentives currently where approximately I want to say 60% allocated as far as the initial phase one budget goes the Faison budget. If you don't recall for anyone reading the transcript or listening to this was the committed pool. So these are long contracts at the overclock Labs core team struck with providers out there. So we're about 60% committed into that and the resources being brought on our h100 that are already on h100 a 100s and a6000 in addition to 40 90s. And so another Toronto of chips are being brought on which are 490s reason for that is because there's a high demand from some of our BD pipeline as far as inference goes in 40 90s seems to be the darling chip for that particular use case. + +Cheng Wang: So yeah, that's where we're currently are. We've spent a little bit also in the committed pool to bolster storage as well because with a lot of these AI efforts Right storage is Paramount just because given the size of the output the data set the models whatever it + +Andrew Gnatyuk: Okay. + +Cheng Wang: I'm always our amount of resistance swords. That's something we're bringing online as well. But that's a drop in the buck here relative to the total cost. So again, we're about 60% into that next phase phase two is the liquidity pool similar to how everyone is familiar with in terms of liquidity pools go so that's still under construction. So we're ironing out the specifications and we'll be launching that soon. So as far as the written spec goes internally will probably get past squared away within the next two weeks or so, of course before anything goes on chain. We're going to submit it into GitHub. + +Cheng Wang: For discussion engaging community and get hopefully some amazing feedback similar to phase one. And so phase two then we'll go on chain Etc rinse and repeat phase three. It's not necessarily chronological per se but I think where appropriate we will put together something and launch that one is a little looser and that it's the R&D bucket. So I would love to allocate towards the Next Generation chips, right? So there's some cool stuff out there as far as + +Cheng Wang: Potentially something with Because I think I correct me from Roma. We do have AMD support that was pushed through a little while ago right that and the Next Generation Blackwell architecture from Nvidia. So that's something really interesting to take a look at and of course after Nvidia GTC the team has really I think Garner a a deep appreciation for just the supply out there what people are looking for how they're using it across the gamut so that's kind of how all the phases shake out currently. I mean if you have any questions guys + +Scott Hewitson: The only thing the question of pose is so we're about 60% committed for that pool for any folks that are wanting to join. is it open? Is what's the process and say hey I fit this category. How can I get in the mix? + +00:05:00 + +Cheng Wang: Yeah. Yeah, I would reach out to pretty much anyone here Tyler specifically you Huey anybody who want to drop a note and say economics wherever you find as easy as to reach us tweet at Greg if that's big enough to get your attention. So the requirements are Pretty straightforward, the high-end resources right server grade chips that we need. Number two is going to be I think at least they disintegrate level two right or higher. And yeah, that's really the basic requirements. And of course there are configuration requirements as Right interconnect stuff, which is obviously related to the chip itself. What's your speed as far as the internet goes and all that and of course reliability up time all those things of course baked into what data center level 2 means we have reach out to us. + +Cheng Wang: Sure. + +Scott Hewitson: Thank you for that. Alright we can pivot away from provider incentives unless anybody has a question. + +Andrew Gnatyuk: + +Andrew Gnatyuk: Yeah. Yeah me again. Hey guys, so I just questions. + +Scott Hewitson: It's new for the first time that again. + +Andrew Gnatyuk: Yeah, yeah. Wow booming with me. + +Andrew Gnatyuk: So one question maybe you can specify this. So I'm just looking on the stats about the GPU capacities and there are big drop downs on the hundred gpus and dropping down and then coming up again. if you can say what is this is all about. + +Scott Hewitson: I go ahead. + +Tyler Wright: What I would say is there's been some maintenance that's been going on and some upgrades to those providers that have been going on that have been affecting the up and down time some folks from the core team as well as the community. They're helping to manage those providers have been doing their best to make announcements and Discord and elsewhere to let the community know when those upgrades and that maintenance is happening and that's what you'll see is when the maintenance is happening for five minutes sometimes maybe an hour those providers will be offline. And then what's the maintenance is done, there's been some feature editions whether it be persistent storage or some other things, but again those providers have been under maintenance which is why you'll see the drop and then coming back online. One of the things that we talked about in six support today. That's a major focal point for the core team and many people in sick providers as well is improving provider stability. + +Tyler Wright: I'm so that some of these things won't happen. So it's maybe as features of being added. It won't be as long as a drop off or there won't be a need for as many of these drop offs. But again, that's just a factor of the network, but pretty consistent behavior and again stuff that's been announced to the community when it's been done. + +Andrew Gnatyuk: We got it. Thanks. + +Zach Horn: Yeah, let me jump in on that point. + +Scott Hewitson: Go ahead Zach. + +Zach Horn: So all the things are tired is saying are definitely correct. there's providers are coming up they're doing maintenance. But ultimately if you look over time, you see this drop over the past couple weeks, peeking around 350 and then it pulls back to 275 And that's the things that Ty is talking about just providers doing maintenance But ultimately it's a good thing, these providers are getting online. they're working through how they're gonna provide on a caution. They're getting more stable over time. We did just hit an all-time high this morning as of right now, we're total capacities at 363 which is technically an all-time high. So the trend is definitely up over time and to Ty's point. It's like I wouldn't worry too much when it drops down and it comes back up and there's gonna be fluctuation, but the long term trend is up. + +Andrew Gnatyuk: Got it. and the follow-up question. so we have an all-time high on the network capacity right for the gpus. Do we have demand to get at least to 60% of this capacities to lead them? + +Cheng Wang: Yeah, so it's definitely incoming so as far as the commitment of the resources go we have a couple of true Partnerships or Integrations right actually impending at this point in time. They're all in the phases of spinning up. So for 49 year resources the vast majority of those will be soaked up via one of these Integrations or Partnerships here. It's just Again part of the testing and it's non-trivial right that amount of technical work to get fun up on to So that should be coming imminently really any day now honestly for the 49 year resources for H 100 and a 100. Those are again pending a particular integration with a strategic partner at this point. And so that's again under testing and there's a whole bunch of things there. I can't say too much about it. But essentially they're a front end or web to front end that essentially gets easy deployment on to a caution or with a caution or + +00:10:00 + +Cheng Wang: the supply backbone for a100 and 100s. And so when that integration completes, obviously it's taking longer than we would ideally right but once those spit out I anticipate that vast majority of these resources will be soaked up far greater than 50% + +Andrew Gnatyuk: Got it. + +Cheng Wang: I'm hoping. + +Andrew Gnatyuk: And if we are talking yeah,… + +Cheng Wang: That weeks. + +Andrew Gnatyuk: yeah, that's + +Cheng Wang: I'm hoping. that's the idea. I can't necessarily promise. I'm not the technical person working on it. But all I do know that there's daily activity in all of those channels with both teams our side and the partner side working on it very very diligently to get this across the line. + +Andrew Gnatyuk: yeah, it is bad enough to promise anything because it's recording and basically we can just point out and say change your promise this yes, I don't promise anything but + +Cheng Wang: I promise my fingers are cross behind my back. + +Andrew Gnatyuk: Yeah, but about Partnerships. you said a few of them are we planning to announce them as part of the marketing campaign or… + +Cheng Wang: Yeah, yes. A hundred percent. + +Andrew Gnatyuk: something like that? + +Cheng Wang: Yeah, we will be announcing those as soon as they are done and completed and running. We don't want to kind of jump the gun if all the technical work isn't complete because that's just like hey cool partnership and then I'll let down right so we definitely want to launch these Partnerships and then make these integration announcements full fully when they're fully tested. And of course we get some initial workloads running and that's when we can let + +Andrew Gnatyuk: No Yeah, that's bad. I mean everybody loved announcement about Something coming up. + +Cheng Wang: exactly + +Andrew Gnatyuk: Yeah, but Thank you for the glorification. + +Cheng Wang: Of course, of course. + +Scott Hewitson: Speaking of providers stability and providers going down back up. This is kind of a natural segue to maybe the discussion about the proposal. That's up. I think Ty dropped it in the chat. Yes. Cheng, could you go a little bit into the idea there the thoughts there it's been on GitHub I think for a week now, so it'll probably go on chainsawat soon. + +Cheng Wang: I'm sorry. Which one is this? + +Scott Hewitson: the prayer tour + +Cheng Wang: I'll pray for excuse me. Yeah, sorry apologies. So the Prater kind of acquisition here it's essentially identical to the thought process behind the cloud most acquisition that occurred about what a year ago at this point in time. + +Cheng Wang: Almost a year ago about I think eight or nine months ago. Wow time flies. So it's really kind of the same idea here where Akash console in the beginning as far as the clients go. There's a cost console multiple clients Cloud most being the native one bring bridging those two things together, which finally I think the merge will be complete at some point in the near future. Then there will be one giant native Akash console experience for tenants, right? that's what cloudmoms is and then for prayer as a provider management tool, I think we're still kind of figuring out to see if it makes sense to kind of merge into console as well. But essentially have a One-Stop shop for both tenants and providers. Obviously, there will be different portals for each and I think you are into both, amazing people to work with and they've been tremendous contributors to the community and this I think just brings that closer and further lines us and we'll be able to come for us. + +Cheng Wang: Between preacher as well, as ocl core team here will be able to really accelerate the development speed of preacher as well as the console in addition to just leveraging some of their devops capabilities as we bring on more resources right via the provider and census in the last stuff. That'll be a tremendous help. I think a lot of value similar to how shimpa has been helping the core team on the provider management side, So it'll be a lot more of that and just involving members of further furthermore within, the core team itself. So that's what we're looking at. So we'll probably put this proposal up on chain today and let her rips and there's no real questions on it thus far at least no opposition. Yeah if there are any questions, please do far away. + +Scott Hewitson: Maybe we can in Discord maybe direct some folks to this and see if we can get some chatter going before we do put it on chain. But yeah, definitely by the end of the week. + +00:15:00 + +Andrew Gnatyuk: yeah, but the question about console even the first Native way when overclock created the council was to I split the web2 users who are using just credit cards and debit cards to pay for the compute and Cloud most for the web free users. As far as I remember. That was the talks when overclock console emerge actually. + +Andrew Gnatyuk: Away,… + +Cheng Wang: Yes, sir. + +Andrew Gnatyuk: one cloudmoss was doing the solution and overclock started to do the console. That's was the basics. the console is for users to pay. We are via the credit card the debit cards Etc and cloudmoss is for basically web free group The users Etc. so now it's not the stuff right or + +Cheng Wang: yeah, yeah, + +Cheng Wang: Yes, I think the updated roadmaps should be published soon. But essentially the user experience will be much more unified than before. So the decision making earlier on is do we have two experiences one to be non-custodial one to be custodial at this point in time? I think it's a lot clearer to have everything be on a single platform and simply based on the users input and choice of whether or not they want to held their own funds or not. It'll drive them towards different workflows. So the portal is all the same. It's gonna be a cost console and then depending on whether a user chooses to pay with, credit card or pay with crypto the path will diverge from there, so it'll be a more unified experience. I think more streamlined and ultimately better, you act as well a little lot less confusing and yeah, I think that that's gonna be the way forward for sure. + +Andrew Gnatyuk: okay also about the brighter so Before Brian was independent it as far as but I know I didn't try to set up my own provider as far as an older took a fee. If you are using their platform this is be still gonna be remained or we just dropping all the stuff and making + +Cheng Wang: I think fee if you took a look at the proposed plan, I'm not sure if it's explicitly called out there my camera call at the moment, but it'll be completely open source. So any sort of fee that is being charged will probably be to at least temporarily reptile because everything's gonna be open source and powered by the community. There's no giant impetus to yet monetization fleshed out for this particular application, right because it is again now at this point in time has the backing the community and community pool and the core team as far as funding and operation goes so that is a lot less challenging now than it would then originally was one is just under pressure team. So yeah. + +Cheng Wang: I don't anticipate not being the way forward. We definitely want to make this as easy to use for her community members as possible and then ultimately whatever modernization elements if any that come through will be, fully thought out and of course vetted through Community discussions as with, all these big things are. Yeah, of course. + +Andrew Gnatyuk: If you got it. Thanks. + +Scott Hewitson: Thank you for that update Cheng, I guess a big thing that passed was the coinbase learning rewards. That was probably I think the largest community pool spend proposal that has hit yet. Are you able to give us an update on that and where it stands maybe some specifics? I know you can't reveal everything but anything that we can let everyone know. + +Cheng Wang: The specifics at this point in time. I don't have too much. Other than that, there will be multiple campaigns for this going forward. It wouldn't be a one and done and the time period will be quite I don't really know what time period is but the guidance that we've been given has been each campaign will probably last a few weeks just depending on kind of the resource. We allocate to it. So the budget that's currently designated is, eight million US dollars worth and so that will be parsed out over the course of at least two to four campaigns is my thought at least two probably more than that definitely more than that because we want to keep these kind of things going over time right continue to educate the user about a costume to expa use this as kind of a marketing another kind of point of amplification for marketing sake. So yeah, the first campaign has already been designed and this is largely + +00:20:00 + +Cheng Wang: To be educational these campaigns following up will be a bit more involved. So potentially interacting with chat Akasha Network as the scxl.com network, image generation detection AI tools that core team in the community has put together. So that'll be probably round two slash three of campaigns and I'm just depending on how those performance of course. We're going to iterate based on the information. We get back in terms of conversion where people seem to respond where people seems not and update our subsequent campaigns with that information. So long story short first one is going to be largely educational read quizzes things like that. Hopefully we can do staking as well as a quest. So whatever you do earn, you can then stake for additional token similar to how a lot of the bounties work with air drops and things like that, right? You've seen, across + +Cheng Wang: Cosmos and other chains, so that's one the second follow-on Campaign largely will of course, they're all educational but can be more interactive as far as using some of the applications. We've built and then from there. we haven't thought about really the third or fourth campaigns yet, but literally based on the information Now we get only learn from the initial campaigns. Of course, we'll share those and calls like this and others. + +Zach Horn: It's worth all the touching on outside of the technicals of literally what these campaigns are going to be the size of the opportunity here. So this proposal it's large right and say million dollars of what was requested. But what we're talking about essentially is reaching tens of millions of users, coinbase obviously has a very large audience that these campaigns do get a high number, users that flow through them and do complete them. So just them in terms of awareness for a cost. This is a huge opportunity just worth underscoring that + +Scott Hewitson: Thank you for that. Does anyone have any questions in regards to the coinbase learning rewards prop at his past? See you later Max. + +Andrew Gnatyuk: And yes, so do we have some fixed apis that are we like looking to reach within with this campaigns and do any of these kpis are I don't know involved with Market volume because it's for cash. It's a bit low right now. and basically what we are giving eight Millions to get the broader audience to use the cash, but basically to trade the cash as well since it's going base, right? So how do we have some of those stuff? I don't know. + +Scott Hewitson: but + +Zach Horn: So primarily what we want to see from this campaign is we want to see the total amount of users that interact with these campaigns. We want usage. So we're going to put these out there. We want people obviously to engage with them to complete the quizzes and to claim their Rewards. If we can get the staking Quest live for this first one. Ideally we want them to flow all the way through the quiz campaigns to the staking Quest and then stake their akt. So in terms of kpis we want to see the total usage. So how many Impressions do these get what is the completion percentage? So of the people that see the campaign and click through it how many actually complete it and claim the reward and then if we can get the staking Quest live we will do a big kpi is gonna be how many of the people that flow through the campaigns end up staking their akt, So in terms of kpis, that's what we want to see primarily a lot of the market stuff is a little bit outside of this but this is as I said before a great Market opportunity to just get in front of a ton of new users and just get awareness for Akash. + +Andrew Gnatyuk: Got it. Okay. + +Scott Hewitson: yeah, I think it's important to note that there's a Max per user. So it's like if you know that the campaign will go until its exhaust until funds are exhausted. That's not like, somebody's doing a little bit and they're getting more everyone's gonna be able to get the same amount it just kind of depends on + +Scott Hewitson: So you never I mean. If price goes up too, it's like you could even squeeze in more folks than what we allocated for. + +Cheng Wang: Yeah, one thing I have to note on the back of the point that the reach here is if you look at historically we've done essentially no true. + +Cheng Wang: Paid awareness campaigns and the entire history of Akash Network. And this is the first time that we'll be doing so and it's on the only I guess truly sanctioned platform right as a public company that coinbase is within crypto as an exchange. So it does a couple things to reach is extremely high here in the orders of potentially millions of users. That's Number two is these are all sensibly high value users or potentially because most of them will be us and definitely KY seed and these are people who are I would think not as read into crypto has So if most of these people may not have interacted with things like defy and stuff like that. Maybe I'm wrong. I don't know how deep the rabbit hole goes within coinbase users. But as far as educating users about a grange sector brand new + +00:25:00 + +Cheng Wang: Can as far as the cost goes and exposing them to AI as the intersection with crypto is going to be another huge potential win for us. So ultimately it's generally like count acquisition is important right people who are interested in college holding a caution / trading Akash, but secondly, it's going to be about just broad awareness in a area that we haven't really reached out to previously and number three is for you have to remember for the utility of Akash Network. + +Cheng Wang: Access to the Token is Paramount, especially now right until I think after credit card payments are spun up access to the Token is hugely important for instance institutionals as well as individuals and teams to be able to use a Cosh Network for its compute resources, right and so coinbase with its integration and its reach and it's I think stature in not just cryptospace but outside of crypto most normies, right? I would say within the US use coinbase. I think having that portal of access into a cost tokens or to use the platform is super beneficial, right and then of course last but not least is going to be the custody component for institutions as well. As super high now with individuals, whoever who have significant, stakes in the caution. They don't want to kind of deal with the Specter of self-custody and stuff like that. The institutional Prime Services is available to them as well. + +Andrew Gnatyuk: You got it. Sounds great. + +Scott Hewitson: Does anyone have any other questions regarding the coinbase learn proposal? And if not, we can open it up to General comments ideas. Anything anyone's working on floor is yours if you want it. + +Andrew Gnatyuk: So just general question again about the trading volume. Do we have some ideas how to increase the trading volume for cash. I mean we are in top 100 on and gecko but I would write in volume is top 500 something at least. + +Cheng Wang: Trading volume isn't something we can really push on our own. I mean some projects I don't know the trade you can't necessarily dream volume. You really have to take with a big grain of salt Andrew. and Yeah. + +Andrew Gnatyuk: Yeah. Yeah, I got that's why it's general question. just to talk about not so specific. + +Cheng Wang: Yeah, I mean in terms of trading volume you look at the history of it over the last I would say even before coinbase listening. I think we were averaging on a daily basis over over 10 million dollars in daily active volume, right or just about there. And so, last couple days I think have been a little bit slower but Overall, I think we've been on average if you take moving averages across a week since maybe beginning of March or something. We've been averaging over 10 million. So that's already a really good feat and one bit of thing one. I think metric that you should definitely take a look for those people looking at markets. Maybe you look at trading volume and depth right? what multiple is your trading volume of your depth and there are some projects out there will have + +Cheng Wang: 20 x the daily trading volume of depth, which is points to me. There's some BS going on in there Exactly or… + +Scott Hewitson: lost Trading + +Cheng Wang: something else. I want to say I don't exactly know. There's some thing that just doesn't sound or look right right. It could be completely above board and that people are just aping into a particular project and just driving volume up and up and up and turn over incredibly high but for projects that have let's say, 500,000 in aggregated debt plus minus two percent and then trading volume is 50 million you're just like + +Cheng Wang: How many times is 500k have to go into 50 million the turnover? Right? it doesn't really quite make sense. And in addition to that you look at the amount of float that is out there and concentration token holders, whatever the case may be. Right? So for a caution Network, we're what three plus years old at this point in time. So our holders Holdings are incredibly decentralized and distributed at this point in time and the markets are quite mature, So trading volume isn't something we can directly control nor that we want to be honest, And so you can kind of rest assure that the activity you do see on a caution network is a hundred percent organic. There's no funny business. it's not being done by us. + +00:30:00 + +Andrew Gnatyuk: got it. Yeah. + +Cheng Wang: Yeah. + +Scott Hewitson: All Does anyone else have anything that else I'd like to add or comment on or pose any questions ideas open to anything? alrighty A little shorter call this month, but that's all right. I think we can close thing or end things now and then, if anyone has any follow-ups or anything they want to talk about please go to Discord and you can ping me or whoever and we can keep the conversation going there. And what that will see everybody next week or next month? Sorry. + +Scott Hewitson: All right. + +Andrew Gnatyuk: And sounds good. + +Cheng Wang: And quicker. + +Andrew Gnatyuk: That sounds good to me. + +Cheng Wang: Thanks everyone. + +Andrew Gnatyuk: You guys next month. + +Rodrigo Rochin: you have to do the + +Cheng Wang: looking forward to see Thanks,… + +Andrew Gnatyuk: Yeah, it's nice to see you. + +Cheng Wang: everyone. + +Zach Horn: Take care guys. + +Andrew Gnatyuk: Bye guys. Bye guys. + +Meeting ended after 00:31:52 👋 + From bf56824eef78e1acad26f7adf0dcf71412c83f28 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 30 Apr 2024 11:21:58 -0400 Subject: [PATCH 047/138] steering committee Create 014-2024-03-27.md (#559) added meeting details, notes, and transcript Chore: Add video recording Signed-off-by: Drinkwater --- committee-steering/meetings/014-2024-03-27.md | 328 ++++++++++++++++++ 1 file changed, 328 insertions(+) create mode 100644 committee-steering/meetings/014-2024-03-27.md diff --git a/committee-steering/meetings/014-2024-03-27.md b/committee-steering/meetings/014-2024-03-27.md new file mode 100644 index 00000000..e4f18bfa --- /dev/null +++ b/committee-steering/meetings/014-2024-03-27.md @@ -0,0 +1,328 @@ + +# Akash Network - Steering Committee - Meeting #14 + +## Agenda + +- Review / discuss / address any community feedback, grievances, or conflicts. +- Review [projects list](../projects-list/README.md), prioritize / add / remove if necessary. +- A look at open discussions in [Github Discussions](https://github.com/orgs/akash-network/discussions). +- Open up to any other questions from the community. + +## Meeting Details + +- Date: Thursday, March 27th, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://aqjulyegruxs4xdwltfkkxqieagkmqc7dcbewovdw2wk7tj72hka.arweave.net/BBNF4IaNLy5cdlzKpV4IIAymQF8Ygks6o7asr80_0dQ) +- [Transcript](#transcript) + +## Committee + +- Anil Murty, Overclock Labs +- Artur Troian, Overclock Labs +- Greg Osuri, Overclock Labs +- Scott Caruthers, Overclock Labs + +## Participants + +- Adam Wozney +- Andrew Mello +- Anil Murty +- Artur Troian +- B S +- Cheng Wang +- Denis Lelic +- Deval Patel +- Greg Osuri +- Jigar Patel +- Joao Luna +- lukas meilhammer +- Matej Leskovec +- Maxime Beauchamp +- Pierre-Andre Manseau +- Poroburu +- Robert Del Rey +- Rodrigo Rochin +- Scott Carruthers +- Scott Hewitson +- Tyler Wright +- Zach Horn +- Zeke E +- zJ + +## Notes: + +- Tyler led the group through the agenda and asked if anyone had any comments or conerns about the open structure. +- During the Projects part of the Agenda, Andrew Mello chimed in to talk about Spheron. + +####Spheron: + +* Andrew Melllo talked about how he is working at Spheron. +* Spheron is establishing a partnership with subspace. They are in Testnet right now, but they are coming to Mainnet soon. Spheron is figuring out best pricing for Subspace plots. +* Greg asked about Spheron. Greg mentioned that the Spheron founder mentioned that Spheron is moving away from Akash because they are not getting credit. +* Andrew Mello responded that he is new to the issues with Spheron x Akash. +* Moving forward the plan is not to speak on twitter. The goal is to integrate Spheron in all the right places. +* Greg asked about the 5akt issue that Spheron brought up. Andrew Mello mentioned that this problem was solved by the parameter change. +* Greg reminded Andrew and anyone else that anyone can make a proposal. Akash is open and owned by the community. It is core team and community that go to events. All teams have a responsibility to +* Andrew reiterated that there was a “breakdown in communication in the past”. Andrew and Tyler are meeting biweekly to work through Spheron x Akash. +* The issues in the past are not issues anymore. Looking forward, Andrew wants to do things to represent themselves to the community. +* Andrew mentioned that Spheron takes credit cards. Spheron wants to communicate the relationship In a positivity. Affective collaborations is the goal. +* Anil mentioned that he is happy to have a Spheron representative at open meetings. Hoping to see more of Spheron at meetings. +* Anil asked about some technical features, and Andrew recommended that Anil take a tour of Spheron. + * There are 3 types of deployments on Akash. On demand and Auto scaling goes to Spheron providers. Spot setting allows user to deploy on the public network. + * Tyler mentioned that continued conversation from Spheron will happen at future sig-clients. + * Rodri mentioned that there were many people at Kubecon that knew about Akash. Rodri mentioned the booth was packed. + + - The community continued discussion around the product + engineering roadmap. + - The community read over open discussoins. + + + + + + +### [Product and Engineering Board / Community + Marketing Board](https://github.com/orgs/akash-network/projects) + + + + +#### [Community and Marketing](https://github.com/orgs/akash-network/projects/6): + +Akash Accelerate passed on chain. +* Adam talked about Akash Accelerate 2024. +* The team has found and signed the event organizers. +* Two sides are meeting weekly until Akash Accelerate 2024. +* Adam is feeling comfortable that things are moving in the right direction. +* There is a general Akash Accelerate Channel in discord for those that may want to help plan or attend. + +Adam talked about the Akash Hackathon 2024: +* Tracks were drafted. A majority of the tracks will be around GPUs and AI. +* participants will be using Dorahacks to register and submit. +* The hackathon will be open for a month and a half starting in early April. +* Details will be communicated to the community for next steps with the hackathon. +Zach Talked about the Akash GPU pricing. +* Core team made it easy for people to see what GPUs are available. +* There is still some work to be done on the Akash.network/gpus page. +* It will be launched in the next 48 hours, but the site is live in beta right now. +* GPU pricing page is based upon data from feature discovery. All providers should please add feature discovery. Announcements have been made. +* Scott C verified that many providers have upgraded, and just a few providers needed to be upgraded. + +Tyler and Robert talked about Zealy: +* Robert mentioned that the first sprint is closing. Second sprint will happen soon. +* Feel free to join the working group to learn about the details of Zealy, or if you want to suggest a mission. + + +#### Product + Engineering Board: + +* SHM is in testing and should be live. The documentation is done. More announcements coming soon. +* Private repos is code complete. Prelim testing has been done, but more rigorous testing will happen next week. +* Tyler went through the high priority relationships. +* Anil mentioned SHM is super important for AI work. Providers upgrading and supporting this is greatly appreciated. +* For GPU pricing, there is a workaround solution for how pricing is being found. +* Anil talked about a demo Hooman HQ made at sig-clients. Anil wants to make sure that Hooman HQ private repo crosses +* Andrew talked about benchmarking API that checks on pricing with live deployments. The code is done. Andrew has a use case that he doesn’t want to talk about today. +* Tyler reminded Andrew of the open framework, if he is looking for rewards for open source work that benefits the Akash Network. + +### Github Discussions: + +Discussions: + +* Tyler reminded people of the discussion framework, so that the most popular and lively discussions are the focus during steering committee. +* The discussion author needs to rally the community to get involved in the discussions. Comments and upvotes will showcase the value of a discussion. +* Tyler talked about the Coinbase Learn and Earn campaign which is live on chain for vote. +* Tyler talked about the discussion Hooman HQ and NetaDAO brought forth. The team gave a demo at sig-clients. This is a draft proposal looking for feedback. +* Tyler opened up discussions to the community. +* Please get involved in the discussions. +* BS gave an update in chat the meeeting chat: + - "Lil D from NDAO, here's a quick summary from envy: it's a "template" docker image that takes a repo URL as an environment variable, watches for modifications based on the master branch's build hash, and reinstantiates itself as changes are detected without ever terminating a lease or needing to rebuild + push additional docker images" + + +### Action Items: + +- Community to participate in open discussions on Github. + + + + +# **Transcript** + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +00:10:00 + +Tyler Wright: the product engineering board go ahead Robert. + +Robert Del Rey: Hey guys, can you hear me? Alright? Awesome. + +Tyler Wright: Yes. + +Robert Del Rey: So yeah about Celia, I'll be short we bendy and I are getting ready to close out the first Sprint. It's crazy to see the numbers of engagements these same week. We had a call and we saw some stats since we have now the silly analytics available. And we're just wrapping everything up to close out the first Sprint and share more details in the working group call which is happening next Monday. But yeah a long story short just closing out the first Sprint getting ready for the second screen and stay tuned for the working group call next Monday. + +Tyler Wright: Yeah, if anybody wants to get involved in missions or want to learn about how things are going late to zealy. Please feel free to join that worker group call again a group discusses missions that get added to zealy as well as engagement funnel all that kind of stuff. So if you want to get involved Robert and Ben do a great job of leading those calls, and again, it's a good group of people that usually join + +Tyler Wright: Again, I know there's a number of items on this board. I just want to highlight some of think Is there anything else on the community and marketing initiative board that anybody wants to discuss before we move on to quickly go over the product engineering roadmap? + +Tyler Wright: I saw Andrew's hand first and then Rodger so Andrew you go first. + +Andrew Mello: Yeah, hi everyone. So bit of an update on my side. I am now at sphere on network, which many of you may know or may not know is a deployment platform straight onto the Akash Network and I wanted to just let everyone know that in the coming months. We have starting a partnership with Subspace and Subspace is in test net right now and they have a lot rather large following and the spec of the workload coming is very similar to the Chia workloads. So they're looking at mainnet in the coming months and just kind of a heads up again spheron is already established a partnership with them in test net and we're gonna be bringing + +Andrew Mello: Some of their community members on board now to do benchmarking and figure out the best pricing for the Subspace plots because again, it is a very similar format to Chia. So just to give everyone a heads up on that again. Looking forward to seeing that grow on Akash. + +Greg Osuri: Andrew I have a question about us Okay,… + +00:15:00 + +Andrew Mello: Yeah. + +Greg Osuri: so your founder recently was made an announcement that we're not supporting that he wants Akash to mention spare on every tweet we do. And he publicly said they're experimental moving away from Akash because we're not giving him. credible with a credit for everything we do. what's your response since you're representing spot on here? + +Andrew Mello: Yeah, so there has been a bit of an update on that. I understand that. Hey, I'm new to this situation between spheron and Akash and that relationship and one of the first things that we just started to do about two weeks ago is established that communication pipeline namely through yler where Tyler and I are now having a weekly call on how we can better properly integrate ourselves into the ecosystem because quite frankly again, I can't speak for or CEO and what he said on Twitter, but I can speak for what moving forward we are planning to do which is not speak on Twitter about any of that stuff and specifically go through the proper channels to integrate. + +Andrew Mello: application into the right places on the network + +Greg Osuri: and second issue I had was about reducing the deposit requirements from 5 akt to more optimal number which I believe now is 0.5 akt. + +Andrew Mello: Yes, that's great. + +Greg Osuri: it's a + +Andrew Mello: It's exactly what kind of unblocked the issue which was we are scaling thousands of deployments which have a very large tax now and that has been problem solved and not an issue anymore at all. And so everything's fine there. Yeah. + +Greg Osuri: That sounds good. Can I expect a tweet from spur on saying that this problem has been solved because last time they made it a big deal about this problem even though it's a propos. + +Andrew Mello: Yeah. + +Greg Osuri: That goes. That anyone can make on chain. and I'm not Clear why it's brown had an issue with that with five. Akt what prevent its poron to make the proposal because it's permissionless. Anyone can make this proposals and The argument was or since anyone can do it. Why don't you do it? So I feel like there is a sort of attitude of US versus them. Even though Akash is open and owned by the community as you see here. Everybody is contributing in this Robert, everybody is contributing right as + +Greg Osuri: God or conferences it's not Akash core team. It's community that has more presence than coding. So Akashi is a community owned project. Everybody has a responsibility to contribute or to modify if they see something that they don't want to I believe the community has been very open in terms of accepting a lot of proposals. So, is there any particular reason why making a proposal was not possible by speron and expectation of someone else doing it was… + +Andrew Mello: Yes, so I will speak to this quite frankly again. + +Greg Osuri: what apartment? + +Andrew Mello: It sounds like there was a breakdown in communication in the past. The way forward now is a weekly called between Tyler and myself. We're trying to get the right people who can be effective to these issues and understand how to approach them with the organization and its structure quite frankly that what you are talking about was not, perfectly translated on the other side and + +Andrew Mello: Again, we have now put in place the right people to be talking about and handling that and quite frankly again, These past issues and things that were said in the past are not blockers or issues anymore. As I had noted we are the largest hyperscaler of deployments on that side. So that was a issue which the team at the time did not currently understand the mechanisms to solve that problem with so again moving forward. I'm looking forward to repairing that connection and making sure that we're doing things effectively to represent ourselves to the ecosystem rather than talking on Twitter, we want to be educating about what the features are of the sphere on network in the proper places. So that's the plan moving forward where again, we're not looking to + +00:20:00 + +Andrew Mello: To continue that conversation of the past we're looking to implement and execute in the ecosystem. So that users are aware. We take credit cards, right? You can deploy on the public occasion Network right now with Visa Mastercard and Amex, those are features that are super important for the growth of the network and… + +Greg Osuri: Yeah. + +Andrew Mello: we want to continue that relationship in a positive way now that there is new structure. How we move forward which is weekly calls communicating with Tyler effectively and as execution focused as possible. + +Greg Osuri: This sounds good. Thank you so much for the committee. And yeah, it will be great as well. + +Andrew Mello: Yes, I will follow up with that and see what I can do. But that does not sound unreasonable at all. And again an effective partnership and cooperation is definitely gonna be the way to go with ourselves for deployments and for hyper scaling employment and reeking new heights there. + +Tyler Wright: I know that there's some hands up. I just want to make it clear. I let that conversation go on because I think it's important conversation to have during committee. But we do have an agenda that we like to follow there is an area at the end where we can talk about some of the stuff in detail. so as we continue move forward, I just want us to be weary of that because I get myself to go through discussions and number of other items. So again, I want that was an important discussion to have Yeah,… + +Andrew Mello: Thank you, I think I answered Greg's questions. Yep. + +Tyler Wright: I saw Rodrigo's hand up. But maybe Anil had something that you want to talk about specifically related to that before we go to Rogers question and then move on to the product and Engineering board and they do want to go first and then I'll follow up with Roger. + +Anil Murty: Sure, and we can certainly take this up later. But what I was curious about Andrew because you're on the call and thanks for joining the call. By the way. We've always wanted somebody from Scare on to join these calls and we haven't had any representation. So it's nice that you're joining these what I was curious about was it's awesome that you guys are driving a bunch of leases on the network. + +Andrew Mello: I would invite you to become a user on spheron head on over We get lap GitHub signups all of the standard authentication methods and you will see what features we offer and to specifically answer your question. There are three styles of deployments on the sphere on network. Those are Auto scaling. + +Andrew Mello: we have an on-demand and then we that spot deployments go to the public Akash Network Auto scaling and on-demand are going to sphere on providers that can support more features, increasing memory of a running deployment. That's one of the features or Auto scaling deployments. Those are additional features that the sphere on providers can support. So I invite you again to go try the platform and you will see that you can deploy on the public network and you can also Deploy on sphere on providers with additional features that are not supported on the public network. + +Anil Murty: Okay, thanks. + +Tyler Wright: excellent + +Anil Murty: Yeah, I've used it eight times by the… + +Andrew Mello: Yep, there are three styles of deployment. + +Anil Murty: You'll be seeing my you. + +Andrew Mello: Yep. + +Tyler Wright: So I'm gonna kill this conversation for now. I know that we can continue to have one of the things that Andrew and I have talked about is having sphere on represented at sick clients where we could go into depth and folks that are actively thinking about these kinds of things can come together and ask specific questions. So again, the steering committee is really focusing the high level objectives, and I just want to make sure to get through all those things rodri. Is there something that you want to talk about in the community and marketing and issues board. I know you've had your hand before a while before I move on to the product and Engineering board. + +Rodrigo Rochin: Hey guys, I'll make it super quick. I was just going to add a little about kubecon. I was expecting a lot of people. Thing or going by the booth, but we had a lot more than I expected. We reach our lead goals 75% on the first day. People from Google late ws and has their approached the booth people who knew who all renew about Akash, and I think we're gonna get more Wrote deploying and providers and some of them are renew about the akt token and lots of interest there and I thought it was a great success and we should attend more of those. Will you really didn't have many free time at the booth and even all of the people who were there? We were busy talking to different guys at the same time. So, + +00:25:00 + +Tyler Wright: Excellent. Thank you very much. + +Tyler Wright: All right, continuing to move along again. As a part of the projects list. We also go over things that are on the product and Engineering board. Shm. I know is something that's in testing and should live over next there. So the documentation is There's been rigorous testing done by a number of folks from core team and elsewhere. And so that is something that again you should see announcements and Discord and other channels very soon making that available. I know that again prior repos is something that is also something that something the community has been asking for a long time. And this is code complete and believe is going to be moved into testing early next week. It's been preliminary tested. But again, there will be some further testing done next week. So I know that those are two items that again should be moving to released. + +Tyler Wright: very shortly. Hopefully before the next steering committee monthly meeting. So I just want to call those out. I know that the Max has been doing a fair amount of work as Zach mentioned on the relationship GPU page. She's been some API and point work that's been done. That work hasn't talked about in sick clients yesterday as well as sick providers. So again, I don't want to Anything that's been talked about in detail last couple of days, but I know this work is ongoing by the max team and again should be moved over to release some time over the next couple of days after a couple of things are fine-tuned. + +Tyler Wright: I know those are the most pressing high priority items that engineering and working on. I know there's a number of product relationships that are happening with the number of pocs and Neil Scott. Is there anything that you all want to call out as pretend the product engineering roadmap before I open up to questions about product engineering Focus projects? + +Tyler Wright: Go ahead and Neil. + +Anil Murty: Yeah, don't forget too much in the weeds, but just want to mention a high level that. The shm size thing is super important because most of the people that use Akash for AI type workloads today need to be able to specify customization size and that blocks a bunch of customers and that's why that's a high priority. So, providers are grading. And supporting. This is really appreciated. And then on the GPU pricing and point the thing to keep in mind, there is no way to directly poor GPU prices directly from the providers itself today. So there is a workaround solution that Maxi and maximum worked out which is fairly close to the actual pricing of the GPU, but it won't be 100% exactly what you said on the GB pricing. + +Anil Murty: I don't want to go into the weeds of how that is being implemented. But if there's anybody that has questions about it, we can take it offline. And then private registry support. The only thing I'll mention there is the folks from Human HQ. They did a demo yesterday about a solution that they're building about how they can improve. Docker builds and deployments on a cash and they talked about supporting private Registries in that same context. So We should probably get to them and figure out if there's any complex between what we Implement here versus what the implement. That's it. Thanks. + +Tyler Wright: Much appreciate you bringing at the sick clients meeting yesterday. There was a demo and we'll talk about a little bit of discussions. But again great to have Folks at that Specialist Group talking specifically both human HQ team as well as an adult. Go ahead Andrew. + +Andrew Mello: Yeah, I haven't been on this call in a bit. So sorry for chiming in with a bunch of info today. But I have had on the back burner a benchmarking API that solves this question on pricing because it does live real deployments. Right? And so the best way to get the price of a GPU is check what the providers offering for it every few hours, right? And so + +00:30:00 + +Andrew Mello: once I get my ducks in a row that code is already done. It just needs to be set up and turned on and I do have a use case for it that I'm not ready to talk about just yet today, but it should be known that there will be an API available at some point with the price of a deployment on a provider that includes two prices one with GPU one without and we can extrapolate from that single deployment what they price things at and Figure it all out. So this has been done. I just need a little bit extra motivation to get behind it and it's around the corner. Yeah. + +Tyler Wright: All I know I saw your hand Go ahead. + +Anil Murty: Yeah would take a lot of time but Andrew that's really great that you had the solution would be nice to know about this because that's literally what Maxi he is not on the call and speaking for him. But that's literally what he has implemented in. The last few days is basically + +Andrew Mello: If you look back I've mentioned this in previous discussions and this was actually something that I had worked on previously before in the last six months that I was at Akash as So this has been something in my wheelhouse for quite a while and me can't speak to how it was Mr. You missed it. So + +Anil Murty: I mean that's exactly the solution that is incriminated now and that's what we're using for the pricing page. + +Andrew Mello: I don't work for Akash. So as I said if there was some form of extra, I need to align it with my time frames and my projects otherwise, so if you want it done or need extra support, you can reach out to me for it. Yep. + +Tyler Wright: there's also a public framework on especially stuff that's open source, we figure out How to incentivize so I would ask that you continue to follow that open framework that everybody else in the community follows. Is there any other topics related to product and Engineering roadmap that anybody on this call wants to discuss before we move into the discussion section. + +Tyler Wright: All Cool going back to the agenda again during this portion. We review any new discussions that have happened since the last year and committee meeting. There are a set of criteria that we hold folks to so that we're not wasting time during the steering committee. We ask the folks that are participating or leading those discussions attend those meetings. We ask and this is something that we saw in previous discussions. If you are putting up a discussion on GitHub the onus is on you the community to contribute to that discussion. If you are rallying the community and there's nobody else that wants to get involved in discussion. That's usually a clear cut sign that's not something that the community is necessarily interested in and then maybe it's time to + +Tyler Wright: collect ideas that go back to the drawing board and come up with a new discussion. So again, that would be the way that I would ask folks to move forward is that you put up a discussion on GitHub and you want people to interact with it because he wanted to move forward then please again, let people know what the discussion is about don't get into the weeds where people have no idea what's going on just high level what you're trying to accomplish why it improves the Akash Network, how it improves their caution Network and then ask people to contribute to discussion and my comments by up votes by all that kind of stuff and consistent communication during the special interest groups and working groups. Then again, the appropriate discussions that need to be pushed forward will present themselves. With that being said, I know that the last meeting was March 7th. And so that again there's a couple of + +Tyler Wright: There's a couple of discussions that have happened since then. I want to focus on discussions that folks are a hero. I know this is something that live on chain right now and is scheduled to close tomorrow, but again, there's active discussion questions from the community those questions have been answered. So I don't know if anybody wants to talk about or has any other questions about coinbase learning rewards and quests proposal right now, but this is a great example of again a discussion that has a lot of folks asking detail questions. And so that gets pushed forward very quickly, but does anyone have me comments or questions on coinbase learning rewards and quests proposal before we continue on + +00:35:00 + +Tyler Wright: cool All right. Another item that has come up in the last couple weeks and is around. + +Tyler Wright: This one that Anil just talked about at sick lines yesterday. Pierce who worked on the website revamp has been working with the netted out team and the POC that they demo was around making it easier for folks, whether the government websites or their doctorizing anything to basically streamline and automate a little bit of that. Containerization process through cloudmose again, they gave a demo and said client so I don't want to go into a great detail here, but they are looking for feedback from the community on their idea. I would ask that if you're on this call. + +Tyler Wright: Steering committee or a member of community you just look at this proposal because again another Dow team as well as a human HQ team spent some time to put this together and work works on the proof of concept, even if it's okay. It's just not something that necessarily is needed by the network or hey, this is a great idea that needs to be pushed forward. Any feedback would be necessary or be welcome. I know there's a couple of folks from Lanetta Dow team here again. This was discussed in great detail yesterday. It's declines. But I do want to open it up to anybody from net adapt. They want to give any high-level points on this specific discussion. Again. This is not even a proposal yet, but just a draft proposal looking for feedback. + +Tyler Wright: I know some of the net of Doubt team might not be able to speak live. But again, if you have any questions, please drop them inside of this discussion so that you can get real-time feedback from team that's working on it. + +Tyler Wright: But we already talked about a cost accelerate which was again discussed by the community and has already passed on chain. So we don't have to go into detail Is there any other discussions that anybody wants to focus on here today that we haven't talked about as a group yet? + +Tyler Wright: All that's not that we can continue move on. But again, I urge everybody on this call insiders and vanguards. I urge you all to get more community members that you see General Chen other channels involved and at least some of these discussions right and this could lead to a number of other ways that people can get involved with the crash, but everyone I know Has an opinion so please feel free to push people towards the discussions. + +Tyler Wright: yeah. BS is putting the chat. He's part of the netted out team just gave a little bit of quick summary. But again, please get involved in those discussions. + +Tyler Wright: All right, if there's nothing else related to discussions and again, the last part of the agenda is related to just open it up to any questions. Does anybody have any specific questions that they want to ask of the steering committee or the community while we're all here? + +Tyler Wright: All right, I'll take that as a no. All right. if there's nothing else I know it's been a fun-filled steering committee monthly meeting as mentioned as a lot going on across a number of different projects teams Etc. The Specialist groups that happen again monthly sometimes by weekly are a great place to get into the needs and get into the details about specific projects that are going on. I know that on this call everybody in this community. it's very very busy, building for Akash or just busy in general. So be great to have constant commun Follow up and consistency from folks in the special prescription working groups so that again if you're working on something and then you just appear for a couple of months. It's on top of mind or at least people have access to it. + +00:40:00 + +Tyler Wright: just want to shut that out. And again anybody has any questions about ways to get involved. Please feel free to reach out to myself Adam anybody from the core team or vanguards inside of anybody in the community because there's a number of clear ways which people can get To anything else to anybody wants to discuss before that. She'll go. + +Tyler Wright: All again, happy Thursday everybody. Thank you for your participation here today, please look out for a number of special interest groups happening next week for following weeks. So if you want to get involved in provider and clients and stuff, with the talk about a little bit detailed today, please join those special interest group for clients. If you have any provider-related questions as an active group of providers that meet a monthly to talk about provider related. Everything. so please feel free to join that group. And then again stick chain will be happening next week or the week after we talk about Network upgrades that are planned for the future six of porches where you can get involved in a number of support issues related to the core product and sick Community design working group for a Cosh website. There's just a pleasure of ways in which people can find and make and find a way that they can get involved and supporting and growing a cost. + +Tyler Wright: off my soapbox. I hope everyone has a great rest of their day. Thank you very much for the time today. I will continue to talk online between meetings. + +Tyler Wright: Appreciate you all. Bye. + +Cheng Wang: Thank you, everyone. + +Rodrigo Rochin: Thank you all by. + +lukas meilhammer: Thank you all bye and I'm not going anywhere. And have a good day guys. + +Andrew Mello: another day + +Meeting ended after 00:46:49 👋 From 533f28d8e1e82b24d591bbefe8d2635d04e0f487 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 1 May 2024 11:59:43 -0400 Subject: [PATCH 048/138] wg-provider-audits Update README.md update meeting table with proper dates and times. Signed-off-by: Drinkwater --- wg-provider-audit/README.md | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) diff --git a/wg-provider-audit/README.md b/wg-provider-audit/README.md index 9f56f27e..74f68390 100644 --- a/wg-provider-audit/README.md +++ b/wg-provider-audit/README.md @@ -15,15 +15,10 @@ This working group is for developing an open source auditor tool for providers. | Meeting | Time | Notes | Transcript | Recording | --- | --- | --- | --- | --- | | #1 | Wed, Feb 21, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/wg-provider-audit/001-2024-02-21.md) | [Link](https://github.com/akash-network/community/blob/main/wg-provider-audit/001-2024-02-21.md#transcript) | Coming Soon -| #2 | Wed, March 20, 2024 10:00 AM PT (Pacific Time) | | | -| #3 | Wed, April 17, 2024 10:00 AM PT (Pacific Time) | | | -| #4 | Wed, May 22, 2024 10:00 AM PT (Pacific Time) | | | -| #5 | Wed, June 19, 2024 10:00 AM PT (Pacific Time) | | | -| #6 | Wed, July 17, 2024 10:00 AM PT (Pacific Time) | | | -| #7 | Wed, August 21, 2024 10:00 AM PT (Pacific Time) | | | -| #8 | Wed, September 18, 2024 10:00 AM PT (Pacific Time) | | | -| #9 | Wed, October 16, 2024 10:00 AM PT (Pacific Time) | | | -| #10 | Wed, November 20, 2024 10:00 AM PT (Pacific Time) | | | +| #2 | Wed, May 1st, 2024 09:00 AM PT (Pacific Time) | | | +| #3 | Wed, June 19, 2024 10:00 AM PT (Pacific Time) | | | +| #4 | Wed, July 17, 2024 10:00 AM PT (Pacific Time) | | | + ## Contacts From 80e3847189f7f21b32b61d044a86cc7f6ae6b09a Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 1 May 2024 12:45:37 -0400 Subject: [PATCH 049/138] sig-economics Update README.md update meeting table with meeting times and add meeting links for sig-economics meeting 15 chore: add video link Signed-off-by: Drinkwater --- sig-economics/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sig-economics/README.md b/sig-economics/README.md index 9630ac03..11ebb393 100644 --- a/sig-economics/README.md +++ b/sig-economics/README.md @@ -26,8 +26,8 @@ Meetings happen every [First Wednesday of the Month](https://calendar.google.com | #12| Wednesday, January 10, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/012-2024-01-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/012-2024-01-10.md#transcript) | [Link](https://gbxszp7zaubg3dskphdcgwpqkjtz3mb3zgtq46ka2yyzzkfij7na.arweave.net/MG8sv_kFAm2OSnnGI1nwUmedsDvJpw55QNYxnKioT9o) | #13| Wednesday, February 07, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/013-2024-02-07.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/013-2024-02-07.md#transcript) | [Link](https://6rzdyy2kxzn4qpilczq7vdvfd52kxb65rk4cnhor32f4cibhkqmq.arweave.net/9HI8Y0q-W8g9CxZh-o6lH3Srh92KuCad0d6LwSAnVBk) | #14| Wednesday, March 06, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/014-2024-03-06.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/014-2024-03-06.md#transcript) | [Link](https://l7relb4v4vhxhw4shqui4iyoyyeqdt6ogwpx2thybmneridemfnq.arweave.net/X-JFh5XlT3PbkjwojiMOxgkBz841n31M-AsaSKBkYVs) -| #15| April, 2024 10:00 AM PT (Pacific Time) | | | -| #16| May, 2024 10:00 AM PT (Pacific Time) | | | +| #15| April 3rd, 2024 10:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/015-2024-04-03.md) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/015-2024-04-03.md#transcript) | Coming Soon +| #16| May 1st, 2024 10:00 AM PT (Pacific Time) | | | | #17| June, 2024 10:00 AM PT (Pacific Time) | | | | #18| July, 2024 10:00 AM PT (Pacific Time) | | | | #19| August, 2024 10:00 AM PT (Pacific Time) | | | From 5db60621711570323046b9974ccaa2d852c74be2 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 2 May 2024 09:42:48 -0400 Subject: [PATCH 050/138] Update and rename 014-2024-03-27.md to 014-2024-03-28.md rename the meeting and update meeting notes Signed-off-by: Drinkwater --- .../meetings/{014-2024-03-27.md => 014-2024-03-28.md} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename committee-steering/meetings/{014-2024-03-27.md => 014-2024-03-28.md} (99%) diff --git a/committee-steering/meetings/014-2024-03-27.md b/committee-steering/meetings/014-2024-03-28.md similarity index 99% rename from committee-steering/meetings/014-2024-03-27.md rename to committee-steering/meetings/014-2024-03-28.md index e4f18bfa..690aa49a 100644 --- a/committee-steering/meetings/014-2024-03-27.md +++ b/committee-steering/meetings/014-2024-03-28.md @@ -10,9 +10,9 @@ ## Meeting Details -- Date: Thursday, March 27th, 2024 +- Date: Thursday, March 28th, 2024 - Time: 11:00 AM PT (Pacific Time) -- [Recording](https://aqjulyegruxs4xdwltfkkxqieagkmqc7dcbewovdw2wk7tj72hka.arweave.net/BBNF4IaNLy5cdlzKpV4IIAymQF8Ygks6o7asr80_0dQ) +- [Recording]() - [Transcript](#transcript) ## Committee From 0685681a32aa9a3eb4315085fb802d756c78749c Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 2 May 2024 09:46:14 -0400 Subject: [PATCH 051/138] steering committee Update README.md update readme table Signed-off-by: Drinkwater --- committee-steering/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index 9496edfa..c7eb35e3 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -27,9 +27,9 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, December 07, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md#transcript) |[Link](https://k6mud4r2ua6xarj6c5zqtkxw6fzjrvzjzu6eotsyhsmotles2gaq.arweave.net/V5lB8jqgPXBFPhdzCar28XKY1ynNPEdOWDyY6ayS0YE) | Thursday, January 25, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md#transcript) |[Link](https://uh4qrdp5wsvzihnnh7m7conzwkllrei4xawnfsohgjmp5qpjberq.arweave.net/ofkIjf20q5QdrT_Z8Tm5spa4kRy4LNLJxzJY_sHpCSM) | Thursday, March 7th, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md#transcript) |[Link](https://aqjulyegruxs4xdwltfkkxqieagkmqc7dcbewovdw2wk7tj72hka.arweave.net/BBNF4IaNLy5cdlzKpV4IIAymQF8Ygks6o7asr80_0dQ) -| Thursday, March 28, 2024 11:00 AM PT (Pacific Time) | | | -| Thursday, April 25, 2024 11:00 AM PT (Pacific Time) | | | -| Thursday, May 30, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, March 28, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md#transcript)|Coming Soon +| Thursday, May 02, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, June 06, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, July 25, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, August 29, 2024 11:00 AM PT (Pacific Time) | | | From 7dcd3ecf96b08b069230eda0bb3292a8cd4c64e2 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 15 May 2024 14:52:49 -0400 Subject: [PATCH 052/138] sig-design Update README.md update meeting table Signed-off-by: Drinkwater --- sig-design/README.md | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/sig-design/README.md b/sig-design/README.md index 68a1274d..145cd180 100644 --- a/sig-design/README.md +++ b/sig-design/README.md @@ -30,16 +30,15 @@ date: 2023-1-09T00:19:20-08:00 | #13| Wednesday, January 10, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md#transcript) | [Link](https://zao4urnjuqb6ncx2vacwjuqiyqnucl2ifcfm33blijhw6v6owzla.arweave.net/yB3KRamkA-aK-qgFZNIIxBtBL0gois3sK0JPb1fOtlY) | #14| Wednesday, February 21, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/014-2024-02-21.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/014-2024-02-21.md#transcript) | Coming Soon | #15| March 13th, 2024 08:00 AM PT (Pacific Time) | | | -| #16| April, 2024 08:00 AM PT (Pacific Time) | | | -| #17| May, 2024 08:00 AM PT (Pacific Time) | | | -| #18| June, 2024 08:00 AM PT (Pacific Time) | | | -| #19| July, 2024 08:00 AM PT (Pacific Time) | | | -| #20| August, 2024 08:00 AM PT (Pacific Time) | | | -| #21| September, 2024 08:00 AM PT (Pacific Time) | | | -| #22| October 2024 08:00 AM PT (Pacific Time) | | | -| #23| November, 2024 08:00 AM PT (Pacific Time) | | | -| #24| December, 2024 08:00 AM PT (Pacific Time) | | | -| #25| January, 2025 08:00 AM PT (Pacific Time) | | | +| #16| May, 2024 08:00 AM PT (Pacific Time) | | | +| #17| June, 2024 08:00 AM PT (Pacific Time) | | | +| #18| July, 2024 08:00 AM PT (Pacific Time) | | | +| #19| August, 2024 08:00 AM PT (Pacific Time) | | | +| #20| September, 2024 08:00 AM PT (Pacific Time) | | | +| #21| October 2024 08:00 AM PT (Pacific Time) | | | +| #22| November, 2024 08:00 AM PT (Pacific Time) | | | +| #23| December, 2024 08:00 AM PT (Pacific Time) | | | +| #24| January, 2025 08:00 AM PT (Pacific Time) | | | ## Leadership From 511182273fb74417c6240ca2428248efacd0533e Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Fri, 17 May 2024 11:13:09 -0400 Subject: [PATCH 053/138] steering committee Update 014-2024-03-28.md update copy and title Signed-off-by: Drinkwater --- committee-steering/meetings/014-2024-03-28.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/committee-steering/meetings/014-2024-03-28.md b/committee-steering/meetings/014-2024-03-28.md index 690aa49a..2e6a5e13 100644 --- a/committee-steering/meetings/014-2024-03-28.md +++ b/committee-steering/meetings/014-2024-03-28.md @@ -141,10 +141,6 @@ Discussions: - Community to participate in open discussions on Github. - - -# **Transcript** - # **Transcript** _This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ From f29951c7970a1de2d758a1cf2280fbda2e26973a Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 11:13:41 +0000 Subject: [PATCH 054/138] Create meeting notes for sig-chain #14 (#585) * Create meeting notes for sig-chain #14 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * sig-chain Update 014-2024-03-12.md add recording and transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-chain/meetings/014-2024-03-12.md | 173 +++++++++++++++++++++++++++ 1 file changed, 173 insertions(+) create mode 100644 sig-chain/meetings/014-2024-03-12.md diff --git a/sig-chain/meetings/014-2024-03-12.md b/sig-chain/meetings/014-2024-03-12.md new file mode 100644 index 00000000..f74545f4 --- /dev/null +++ b/sig-chain/meetings/014-2024-03-12.md @@ -0,0 +1,173 @@ +# Akash Network - Chain Special Interest Group (SIG) - Meeting #14 + +## Agenda + +- Overview of recent and current governance proposals +- Discussion of recent proposal on minimum deposits +- Update on mainnet network upgrade proposal +- Scheduling of planned network upgrade + +## Meeting Details + +- Date: Tuesday, March 12th, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://bwp7ef3o435ht3azllxhma3vbj4u4x4zgtlx3tfc44gjnjkanyqa.arweave.net/DZ_yF27m-nnsGVrudgN1CnlOX5k0133MoucMlqVAbiA) +- [Transcript](#transcript) + + +## Participants +- Artur Troian +- Joao Luna +- Maxime Beauchamp +- Rodrigo Rochin +- Scott Carruthers +- Tyler Wright + +## Meeting Notes +### Introduction and Updates +#### Tyler Wright +- Tyler Wright welcomed everyone to the Sig Chain monthly meeting #14. +- The meeting focuses on the Akash blockchain, Cosmos SDK, governance proposals, and network upgrades. +- Validators and community members are encouraged to join and participate. +- Tyler acknowledged the efforts of validators in voting on proposals. +- Currently, there are three active proposals onchain. +- A recently passed proposal concerns decreasing minimum deposits for deployments and transactions on the tenant and provider sides. +- This change has been tested and is functioning correctly. +##### Active Proposals: + - Highlighted the community and spheron team's contributions to recent discussions leading to parameter changes. + - Specifically mentioned an important active proposal regarding the main upgrade to version 0.332.0. + - Voting for this proposal is ending soon, within the next few hours. + - If passed, a network upgrade is scheduled for tomorrow at 12:37 Eastern Time (UTC conversion to be provided). +- **Network Upgrade Discussion** + - **Tyler Wright** + - Core engineering team led by Artur Troian. + - Messaging about the upgrade will be shared on various channels. + - Documentation updated and available on the docs site. + - Information will be disseminated through Discord and other platforms. + - **Artur Troian** + - Upgrade expected to be quick and easy, minimal downtime. + - Reminder about the US daylight savings time shift; upgrade at 1pm EST. + - First network upgrade of the year, a minor but important change. + - Anticipation for more upgrades later in the year. + - Plan to present and discuss future proposals and enhancements. + - Encouragement for feedback on blockchain improvements. +- **Network Upgrade Discussion (Continued)** + - **Rodrigo Rochin** + - Asked about the lowering of provider AP requirements. + - Queried if it is now cheaper to deploy and have providers. + - **Tyler Wright** + - Confirmed the parameter change from 5 AKT to 0.5 AKT for both provider and deployer sides. + - Proposal 248 outlines the changes. + - Clarified that the parameter change has been tested but defaults to 5 AKT and needs manual adjustment. + - **Scott Carruthers** + - In the process of testing the provider side for the bid minimum deposit. + - Deployment creation using 0.5 AKT is working perfectly. + - Mentioned the need to use a deposit switch when creating deployments via Akash CLI, which defaults to 5 AKT. + - Cloudmos team can set the default to 0.5 AKT on their platform. + - Announcements will be made once provider side testing is complete. +- **Core Engineering Team and Contributions** + - **Tyler Wright** + - The core engineering team is growing with significant community contributions. + - Focus on managing more engineering tasks related to the core product. + - Network upgrades and Sig Chain projects to be included in the product and engineering roadmap. + - Items will be tagged in the backlog section for easy access. + - Aim for transparency and communication through roadmap discussions. +- **Network Upgrade Clarifications** + - **Scott Carruthers** + - Clarified the adjustment lowering provider attribute update prices as part of the network upgrade scheduled for tomorrow. + - Lowering of minimum bid and deployment deposits (already in effect due to a proposal passed yesterday) is separate from the provider attribute update fee reduction. + - **Artur Troian** + - Will release a new CLI version after the network upgrade to include updated default values. + - Historically, the CLI used hardcoded default parameters, but the new release will query the current default bid and deployment deposits if not set manually. + - **Maxime Beauchamp** + - Cloudmos updated to query on-chain parameters, setting the default to 0.5 AKT. + +## Action Items +- Validators and participants are reminded to vote on the active proposal if they haven't already. +- Group to prepare for the planned network upgrade scheduled for tomorrow if the proposal passes. +- Tyler to attach Proposal 248 for Rodrigo. +- Scott to complete provider side testing and communicate the results. +- Cloudmos team to potentially adjust the default deployment parameter to 0.5 AKT. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody. It's a Sig chain monthly meeting number 14. During these blockchain related special interest groups the community goes over anything related to the cost blockchain Cosmos SDK specific governance proposals Network upgrades. So anybody again interested in any of those kinds of topics? This is something that we always invite validators to even though it's recorded and transcribed again folks can manage their identities and just join these meetings and just that they have any specific questions about anything related to Network upgrades validating on the cost or just the cost blockchain. This is a special interest group to join and participate in + +Tyler Wright: I know there's been a number of proposals that have gone on change. So thank you to all the validators that have been voting on those proposals believe there's three active proposals on chain right now and one that recently passed yesterday related to decreasing the minimum deposits around deployment and in transactions on the tenant side in the provider side, so I know that's been checked and tested by the core team and it's working properly so much appreciate the efforts. + +Tyler Wright: Four team and some folks with the community that helped to bring that conversation to light during previous special interest groups for providers clients Etc that led to again that parameter change, but I know there's a couple of active proposals on chain one that I want to specifically talk about that. I hope that folks have voted on is around the main upgrade to version zero that 332.0 again. This proposal is still on chain for boat in the boat is scheduled to end very shortly over the next couple of hours if it is scheduled to pass right now and if it passes there is a planned Network upgrade for tomorrow that plan Network upgrade is for 1237 + +Tyler Wright: Eastern time I'll transfer that over to UTC for folks, but it's a little bit over a day from right now. So again that proposal is still on chain. It folks have not voted on that proposal. You have a little bit of time to do so and if it passes which is on schedule to pass right now, there is a plan Network upgrade plant for tomorrow. Archer so I know is + +Tyler Wright: leading the core engineering team. I don't know if you have anything that you want to add specifically about that may not upgrade again. We'll put some messaging out in various channels documentation has been updated and that will be shared. It's available in the docs site right now, but I will be shared and Discord and Elsewhere for folks to have easy access to but our try and up with anything that you specifically want to talk about about the network upgrade that's planned to schedule for tomorrow. + +Artur Troian: Thanks, I thank you card everything. We're going to spend the upgrade should be quite quick. It's quite a easy change. So I don't expect any long down times. Just the only reminder that you to the daylight savings time shift for folks in the US. It's supposed to be non-face EST but not is going to be like 1pm EST. + +Artur Troian: And yeah so it's a little bit shift, but you Expected time in UTC should be good. Wouldn't that but yeah, that's gonna be the first network of great for this year. It's a little bit minor and sort of not one that we have planned, but I'm glad that we are executing that. + +Artur Troian: I really hope that later down this quarter. We will be able to execute others that we have planned. At the end of the year for the expected proposals and for the least titles and so forth. So we have a lot of things in our table. At this moment, which we are sorting cleaning up and actually priorities. Hopefully by sometimes of these months you will be able to present it to everyone and maybe open some discussions might be gonna have some feedback on things that people want to have on blockchain. But other than that, I think you're all good. + +00:05:00 + +Tyler Wright: Arctic just mentioned as the core engineering team continues to grow a little bit and there's been a great deal contribution from a number of members of the community some of which are on this call. + +Tyler Wright: There's going to be a concerted effort to again handle a lot more on the engineering side with the core product. So again, very exciting time for head anything that's related to Sig chain, some of the network upgrades that we've talked about in the past that previous Big Chain monthly meetings. Those things will all be tagged inside of a product and Engineering roadmap. I said change so if you look in the backlog section again, maybe in the next month or so you'll look at it. You'll see a number of items. I'll be added to just that roadmap and again anything that maybe Network upgrade related will be tagged with big chain. So that easily accessible for validators or other folks that maybe focus on anything just chain related. + +Tyler Wright: But again the core team and again, we do this as a part of steering committee as well will continue to make as many things available as part of the roadmap just for discussion and communication transparency. + +Tyler Wright: Of course. Is there anything else that anybody wants to talk about related to blockchain Rodrigo hand up. Go ahead. + +Rodrigo Rochin: as a quick question at the beginning you said all the lowering provider AP requirements tests and I believe you said the parameter over to place so now it's cheaper to Deploy in and have the providers and if so how much it was it okay, I mean drinking tea. + +Tyler Wright: Yeah, so, I will attach a proposal for you, but the parameter change was from five akt to 0.5 akt on for both provider side and the deployer side again attach that the proposal 248. + +Rodrigo Rochin: That things I did vote in it, but I forgot if it was going to be three or something. + +Tyler Wright: Yes, so it's 0.5. Scott correct me if I'm wrong, but we know that the parameter change when the effect and it's been tested but I believe by default. It's still at five akt and has to be manually switched for some folks. Maybe not on the deployer side because I know the cloud most team also made some changes their product to That affected the parameter change, but Scott. Do you want to chime in here real fast? + +Scott Carruthers: yeah, so if you're creating a so, I'm actually in the middle of doing the provider side testing of the bid minimum deposit that I've done full testing from the deployment creation. Perspective and it's working perfectly. So this morning I created deployments using point five akt and no issues at all. As Tyler was alluding to if you created deployment from the Akash CLI currently the default is still five. Akt. So if you're creating a deployment you would have to use they deposit switch and then using the deposit switch. You could decrease it all the way down to 0.5. Akt but the minimum always at this point from the CLI is still + +Scott Carruthers: five akt and then from the cloud most side. Obviously, they can control that and Max. I don't know if you have any thoughts on this but obviously on the almost side if they wanted to make the defaults 0.5 and I think it would be able to do that within their code. + +Scott Carruthers: So that there will be a number of announcements about this as So I'm almost there. They provider side testing. Of the minimum bid deposit. So as soon as've done I'm done validating that which I should be able to do in the next half hour. There will definitely be communication and these regards + +Rodrigo Rochin: Awesome things. Yeah, I was basically asking because I wanted to update my provider and in my provider from attributes I have been waiting for this to test to that's been more than I needed to. evaluated announcements + +00:10:00 + +Scott Carruthers: Rather Rodrigo,… + +Tyler Wright: Go ahead. + +Scott Carruthers: let me just make sure there's Clarity on. the Adjustment that we're making that is going to lower the prices of Provider attribute updates. That's part of the network upgrade tomorrow. So we have that that will be solved by the network upgrade what we're currently talking about is. Just lowering of the minimum bid deposits and the minimum deployment deposits. So those are two separate things. Those are already in effect because of the network proposal that passed yesterday, and then they lowering of the gas and the fees for Provider attribute updates will go in effect with the network upgrade tomorrow. + +Tyler Wright: Thank you, Scott. Go ahead. Our turn then Max following. + +Artur Troian: He just real quick on the default and deposit value I'm going to cut releases CLI tomorrow after Network rate, so it's gonna include values because what happens is the historically did not quite old parameter. From the network. We just use the Assumption the one that is default hardcoded and then we put in Genesis, but you've been pretty much changing that. and so what I'm gonna do is we got the CLI will query default beat and deployment deposits if they are not sad manually. + +Artur Troian: they're gonna have it right for tomorrow. + +Tyler Wright: Perfect. Thank you Archer. Go ahead. + +Maxime Beauchamp: Yeah, just wanted to mention that we updated the cloudnos so that it queries from the parameteron chain. So the default is based on the Unchained parameter. So it's 0.5 a kitty. + +Maxime Beauchamp: That's it. + +Tyler Wright: Thank you Excellent. So as Artur mentioned some of those changes will be reflected in the CLI after the network upgrade tomorrow, but Scott also mentioned it can be done currently via CLI just with a little bit extra code. So it is working. + +Tyler Wright: I know again we have a little bit over an hour and a half until that mainnet upgrade proposal passes and then again as Scott had mentioned and I mentioned as well. There'll be a number of announcements that'll be shared in Discord and Elsewhere for folks in the community validators Etc. + +Tyler Wright: So, please look out for those announcements and then anybody's on the Insiders or vanguards, I'll continue to share those announcements so that everybody is up to date and ready for the upgrade schedule for tomorrow. I'll make sure to Highlights the time difference and then again reference a time in UTC for the upgrade announcement and for the upgrade timing and then I'll also update any other meetings on the Discord side that may be showing the wrong time currently. Is there any other questions that anyone has related to the cost blockchain or anything else Sig chain related that they want to discuss today? + +Tyler Wright: it's not much appreciate everyone's time today. Again, please look out for a number of announcements that will be shared on Discord and elsewhere in the coming hours. Again, if you haven't voted on any of the proposals on chain right now, please feel free to do so if thank you very much and much appreciate everyone's time here today. I hope everyone has a great rest of their day. Feel free to reach out to me if you need anything, but thank you all. See many of you tomorrow for the upgrade. + +Maxime Beauchamp: Think so + +Scott Carruthers: concern + +Rodrigo Rochin: Thank you. + +Meeting ended after 00:14:53 👋 + From b2b8e73db0bd0df7ee63505982a592e07011dce0 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 11:16:48 +0000 Subject: [PATCH 055/138] Create meeting notes for Sig-Chain #15 (#586) * Create meeting notes for Sig-Chain #15 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 015-2024-04-09.md add transcript for meeting 15 Signed-off-by: Drinkwater * Update 015-2024-04-09.md add recording Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-chain/meetings/015-2024-04-09.md | 148 +++++++++++++++++++++++++++ 1 file changed, 148 insertions(+) create mode 100644 sig-chain/meetings/015-2024-04-09.md diff --git a/sig-chain/meetings/015-2024-04-09.md b/sig-chain/meetings/015-2024-04-09.md new file mode 100644 index 00000000..59285c4c --- /dev/null +++ b/sig-chain/meetings/015-2024-04-09.md @@ -0,0 +1,148 @@ +# Akash Network - Chain Special Interest Group (SIG) - Meeting #15 + +## Agenda +- Review of Previous Meeting +- Discussion of network upgrade +- Proposals on chain for vote. +- Open discussion + +## Meeting Details + +- Date: Tuesday, April 9th, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://qv5qbltorrogit5i3qvsihngxzevuweduyauwodu5rk3yhysu3xq.arweave.net/hXsArm6MXGRPqNwrJB2mvklaWIOmAUs4dOxVvB8Spu8) +- [Transcript](#transcript) + + +## Participants +- Artur Troian +- B S +- Massv +- Maxime Beauchamp +- Rodrigo Rochin +- Scott Carruthers +- Trigs _ +- Tyler Wright + + +## Meeting Notes +#### Tyler Wright: + - Tyler Wright welcomed everyone to the 15th SIG Chain monthly meeting. + - Meetings cover Akash blockchain network upgrades and validator-related issues. + - Tyler thanked those participating in the validators channel and SIG chain. + - Special thanks to those preparing for network upgrades. +### Network Upgrade Discussion +#### Tyler Wright + - The Akash Mainnet 10 upgrade occurred on March 13th. + - Upgrade was smooth and fast with minimal issues. + - Thanks extended to the core team and validators for their efforts and voting. + - Everyone was prepared for the upgrade on March 13th. +### Tyler Wright Update + - Mentioned several proposals that have gone on-chain and either passed or failed in the last month. + - Encouraged validators for their voting participation. + - Highlighted proposal 255 for community funding for Praetor acquisition, which is currently up for vote. + - Directed questions about proposal 255 to the GitHub discussion forum. + - Noted there are about three days left to vote on proposal 255. + - Successfully completed the mainnet 10 upgrade. + - Recognized the active participation of validators and the general community in voting on various proposals. +#### Future Network Upgrades + - Mentioned upcoming network upgrades and past discussions about the Sig chain. + - Noted the small size of the core team and their focus on multiple projects. + - Anticipated more updates on network upgrades soon. + +### Artur Troian's Updates + - **Cosmos SDK 47 Upgrade:** + - Preparation has begun for upgrading to Cosmos SDK 47, planned since last year. + - Currently gathering necessary information and planning the upgrade approach. + - The upgrade will be extensive, requiring thorough planning and testing. + - Previous successful upgrades attributed to thorough testing; the same will apply to this upgrade. + - Cosmos SDK 47 introduces significant changes from version 45, impacting the blockchain and associated projects. + - Identification of necessary updates and migrations is ongoing, with a detailed plan to be developed. + - Estimated timeline for completion is a couple of months. + - **Interchain Accounts (ICA) Proposal:** + - A recent PR regarding Interchain Accounts was not accepted due to current priorities. + - Need for ICA should be discussed and requested first. + - **Importance of Cosmos SDK Upgrade:** + - Current SDK version is deprecated, limiting functionality and compatibility, particularly with IBC versions. + - Upgrade necessary to avoid compatibility issues and support newer IBC versions. + - Extensive client updates will be required. + ### Network Upgrades and Cosmos SDK 47 + #### Tyler Wright: + - Strategies for upcoming network upgrades and the larger project of upgrading to Cosmos SDK 47 are being finalized. + - Plans and updates will be added to the public roadmap. + - Support tickets with the tag "sick chain" will be created for tracking purposes. + - At least one network upgrade is planned before the larger Cosmos SDK 47 upgrade. + - Validators and community members are encouraged to stay involved via Discord. + - Validators can opt into an email list for updates on votes, network upgrades, etc. + - Contact Tyler Wright or another core team member to be added to the email list. +### Validator Communication + - Validators are encouraged to stay active on Discord for updates and announcements. + - Contact information for validators is essential for emergencies and updates. + - Validators can reach out to Tyler Wright or core team members to ensure they have the correct roles on Discord or to provide an email if they prefer not to use Discord. +### Closing Remarks + - Appreciation for participants' time and efforts. + - Look out for upcoming announcements regarding network upgrades. + - Meeting adjourned with thanks from Tyler Wright, Rodrigo Rochin, and Maxime Beauchamp. +## Action Items +- Core Team to continue monitoring the network post-upgrade for any arising issues. +- Validators to provide feedback and report any issues encountered post-upgrade. +- Tyler Wright to add finalized plans for network upgrades to the roadmap and create support tickets with the "sig chain" tag. +- Tyler Wright to ensure validators are added to the email list and have proper roles on Discord. +- Artur Troian to continue planning and gathering information for the Cosmos SDK 47 upgrade and communicate progress and updates to the community. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to seg chain monthly meeting number 15. During the chain special interest group monthly meetings the cash community and all participants in this Specialist Group come together to discuss all things related to the Akash blockchain Network upgrades anything validated related. So again much appreciate the participation from those that are reach out in the validators channel as well as sick chain and thank you to all those that's getting those ready for all the network upgrades and of our last monthly meeting which was March 12th. That was one day prior to the most recent Network upgrade that network of great happened on March 13th to a class main 10. + +Tyler Wright: thanks in part to the core team as well as all the validators that Network upgrade was quite smooth and very fast and again have seen not too many issues since that upgrade has become So again much appreciated everybody that helped vote on the upgrade. We're ready for the upgrade when it happened on March 13th. in addition there have been a number of + +Tyler Wright: Proposals that have gone on chain and have passed or failed over the last month. Thank you all to all those who have been voting. There's one proposal 255 for Community funding for prayer requisition that is up for vote right now. If you have any questions about that, there is a GitHub discussion where you can get involved and asking any questions, but again much appreciate the validators for voting and their active participation may pass Network. Believe it's about three days left to vote there. + +Tyler Wright: So again out of the last month and meeting the group is focused on getting ready for the mainnet 10 upgrade which is since happened successfully as As a number of items on chain related to proposals and votes that again the validators have been very active as well as the general community and voting and participating in the vote. that's getting us caught up to speed. I know there's a couple of network upgrades that I've been talked about in past the Sig chain, but with the core team quite small and working on a number of different things. I'm sure that there will be more updates on upcoming Network upgrades happening soon. I do want to hand it over to Artur to see if there's anything that he wants to add about. + +Tyler Wright: The cost blockchain upcoming upgrades if there's any details to share here today. Otherwise, we can talk async and people can look at the roadmap as well as safe change to score Channel. But again without further Ado, I'll hand it over to Archer to see if there's anything that he wants to talk about related to a Specialist Group chain. + +Artur Troian: Things are more than everyone. yeah, so to start recovered everything in great details. The only thing I would like to add is have started preparation for upgrading to cosmosis Decay 47 so it's been planned since last year that we going to executed some time during this year. The planning means we are just Gathering all the information we need. For us to start work on this upgrade is gonna be rather big and heavy we need to come up with the approach has to be really thorough. + +Artur Troian: Third band for all the aspects and including testing. So the pasta graze that we had during the last year actually over here have been pretty much solid in one of the reasons it was that way because of the testing there's gonna be no exception obviously for the upcoming because as the care grade, but let's say the customer is okay undergo quite drastic changes from 45 to 47 and those changes need to be reflected in all the Blockchain as well as the project things including clients and so forth. So the plan for now is next. We got our identify all the things that needs to be on dated all the migrations gonna have quite thorough. a plan written down + +00:05:00 + +Artur Troian: on that as soon as we confident That we have changes during upgrade and required. Then you're gonna start working on the actual upgrade itself. So it's gonna take some time. I think my maybe couple months But yeah, I'm glad that we officially getting to the stage. and so any questions to this announcement. + +Artur Troian: Okay, so there was a one PR to the note repo in regards to Interchange accounts. So if that person is here listening, we are not going to accept that at this stage. Simply because it's not just a priority and the question is why the ICA needs to be enabled? + +Artur Troian: before going on that has to be discussion first. There has to be, request first, but just like there is pretty much about my only miscrap. Is that using correct great name, but that's easy to fix. But other than that. We won't be able to take it at the stage and just doesn't make sense. Right? So. + +Artur Troian: that person is listening? Yeah, let us know you can reach out and we can discuss through those steps if the ICA I actually required by some other projects. soon so your question about what Christmas Decay brings. It's not pretty much for the cosmosis Decay brings. It's rather the current version we use is in deprecated all the year ago and there are no that's issued. That limits us for example what IBC version we can use we still may be see before which currently is the I think six seven version. So at some point we might be + +Artur Troian: In compatible with some chains and I'm not saying it's gonna actually happen but you just limits what we can do it puts the burden on the relayers as well to keep support for old versions of the IBC. You just probably not a good thing and in overall this SDK just brings also importance also also this poems actually I should say but We just have to make it unfortunately, so there's no way for us to holding ourselves from this change and they're gonna be quite a lot of actually client updates. So that's why the first of all they're gonna be playing price quite thorough all followed by the preparation of the brain cell. + +Artur Troian: All There's no more questions. Tell her about you. + +Tyler Wright: excellent thank you very much Artur again as + +Tyler Wright: Strategies around upcoming Network upgrades as well as this bigger project around upgrading to kazos SDK 47 as plans get more finalized. They will be added to the facing roadmap as well as there will be support tickets made with the tag sick chain. So that in this group as well as folks in the community community can track those various tickets again, I believe there's a plan to have at least one network upgrade apply prior to this bigger Cosmo sdk47 upgrade, but please stay involved in Discord. If anybody here is a validator and wants to be added to an email list that goes out to folks that opt into that email so that they can get update. + +Tyler Wright: Of Discord or anything related to votes Network upgrades Etc. Feel free to reach out to me or another member of the core team so you can be added to that email list. But again, as items continue to be more defined if anybody has any specific questions about next steps how it will impact anything from clients to the general cash Network. Feel free to drop those in again. Look out for updates in the roadmap and the product and Engineering roadmap as well as in the support repo with a tags under sick chain. + +00:10:00 + +Tyler Wright: Does anyone else have any topics that they want to discuss related to the Akash blockchain? or validator relations + +Tyler Wright: then again what continue to work together online? And again, please please if you are not actively and Discord, it's also people listening in later. Please make sure that you add yourself to the email list for all validators and active sets. it's required that there's a way to contact you. We have a way to contact almost everybody. But again just in case of emergency just in case in any issue, please make sure to check Discord frequently. There's a number of items that go into valid or announcements as well as the If anybody from your technical team that is a part of their validator. It doesn't have the proper role again reach out to myself for somebody from the core team or we'll get that rectified. But if you prefer to stay out of Discord for whatever reason, please share an email with me just so we have again an up-to-date contact just in case we need you for any short-term or long-term efforts. + +Tyler Wright: But there's nothing else then again much appreciate everyone's time and effort today will continue to talk async and again look out for announcements related to a number of upgrades potentially on the horizon that are being planned and we'll be finalized soon. But thanks again for everybody taking the time up today to meet very quickly, and I hope everyone has a great day and week. Thank you all. + +Rodrigo Rochin: And kills you. + +Maxime Beauchamp: Yeah. Thanks Tyler. + +Tyler Wright: Goodbye. + +Rodrigo Rochin: Bye. + +Meeting ended after 00:12:13 👋 + From c04b2edc46151efc1fc05418e570cf141f21b135 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 11:24:28 +0000 Subject: [PATCH 056/138] Create meeting notes for sig-economics #16 (#578) * Create meeting notes for sig-economics #16 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * sig-economics Update 016-2024-05-01.md add transcript for meeting 2024-05-01 chore: add video Signed-off-by: Drinkwater * Update 016-2024-05-01.md add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-economics/meetings/016-2024-05-01.md | 487 +++++++++++++++++++++++ 1 file changed, 487 insertions(+) create mode 100644 sig-economics/meetings/016-2024-05-01.md diff --git a/sig-economics/meetings/016-2024-05-01.md b/sig-economics/meetings/016-2024-05-01.md new file mode 100644 index 00000000..08454aca --- /dev/null +++ b/sig-economics/meetings/016-2024-05-01.md @@ -0,0 +1,487 @@ +# Akash Network - Economics Special Interest Group (SIG) - Meeting #16 + +## Agenda +- Updates since last monthly sig-economics meeting. +- Updates on provider incentives. +- Open discussions on recent proposals and events +- Open up to community for ideas or concerns. + +## Meeting Details +- Date: Wednesday, May 01, 2024 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://w6djeix4uozea7pt7fdzqmhenlvt6jf72c4x26cz3brkuboazjsa.arweave.net/t4aSIvyjskB98_lHmDDkaus_JL_QuX14WdhiqgXAymQ) +- [Transcript](#transcript) + +## Participants + +- Adam Wozney +- Cheng Wang +- Joe Deng +- Nick Merrill +- Scott Hewitson +- Tyler Wright +- Zach Horn +- Zeke E + +## Meeting Notes +### Introduction and Updates +#### Scott Hewitson +- Opening remarks, welcoming everyone to the meeting. +- Mentioned the longevity of the meetings, reaching double digits, and the usual format of covering previous discussions, proposals, updates, and open discussion. +- Invites participants to share any proposals or updates since the last meeting. +- Updates on community pool spend, specifically mentioning praetor Acquisitions and their commitment to open sourcing their code. +- Indicates no significant funding requests or discussions, mostly early stage talks. +- Asks Tyler for any pertinent discussions or funding requests related to sig economics. +- Transition to reviewing discussions and proposals from the last month's call. + +### Recap from Last Meeting +#### Scott Hewitson +- Clarifies that note-taking responsibilities have been delegated to community members as part of bounties. +- Provides updates from last month's meeting, mentioning discussions on provider incentives, GPU capacity fluctuations, scheduled maintenance, praetor acquisition, and Coinbase learn and earn program. +- Reports 500,000 activations for the Coinbase learn and earn program. +- Mentions a large governance proposal discussed during the meeting. +- Encourages attendees to check out meeting notes on GitHub for detailed information. +- Passes the floor to Cheng for any updates before addressing his own agenda item. + +### Updates from Cheng +- Provides updates on Coinbase Learn program, mentioning that approximately 98% of the 500,000 users who completed the Akash quest were new to AKT. +- Reports on the first pilot for provider incentives, stating that approximately $1.5 million of the allocated budget has been spent, with the remaining balance between four and a half to five million dollars. +- Mentions upcoming staking quest integration and plans for the next campaign, which will include deeper engagement with Akash tools like Chat or SCXology. +- Indicates that the first campaign will continue for continuity before transitioning to the second campaign. +### Discussions on Community Pool Spending and Provider Incentives +- Scott Hewitson: Discusses transparency regarding community pool spending and provider incentives. +- Cheng Wang: Reports approximately $3.5 million spent from the original pool, with over a million dollars remaining for phase one of the incentives. +- Scott Hewitson: Plans to introduce a dashboard or tracker for provider incentives to enhance transparency. +- Cheng Wang: Provides details on GPU provider diversity and ongoing conversations. +- Tyler Wright: Shares a discussion from the forum about engaging a content writer to promote finance listings, seeks input for Sig Design meeting. +- Zach Horn: Offers to review the proposal and suggests further action once more information is available. +- Scott Hewitson: Acknowledges the potential for exposure to retail investors through community initiatives like "akt to the moon" on CoinGecko. +- Scott Hewitson: Thanks Tyler for bringing attention to the discussion. +### Proposed Tenant Incentives Program +- Scott Hewitson: Introduces his idea for tenant incentives, inspired by two-sided marketplaces like Uber, and proposes utilizing the upcoming network upgrade to implement the program. +- Zach Horn: Offers insights on the proposed tenant incentives program, suggesting a crawl-walk-run approach and emphasizing the importance of quick implementation and testing. +- Scott Hewitson: Acknowledges Zach's input and agrees on the importance of moving quickly with the implementation. +- Zach Horn: Expands on the idea of integrating the tenant incentives program into the Akash website as a user-friendly option for newcomers. +- Cheng Wang: Comments on the technical challenges and the efforts of the engineering team in enabling features like authz within the Akash network. +- Nick: Raises a point regarding the technical considerations and expresses appreciation for the engineering team's efforts. + +### CosmosWasm for Potential Implementation of Tenant Incentives +- Nick Merrill: Suggests considering CosmosWasm for potential implementation of tenant incentives and highlights its benefits in terms of ease of use and auditing. +- Scott Hewitson: Confirms the absence of cosmoswasm or smart contract functionality in Akash and discusses Greg's stance on increasing the attack surface of the network's codebase. +- Cheng Wang: Agrees with Greg's approach and emphasizes the importance of a well-proven and bulletproof use case before considering integration of smart contracts. +- Nick Merrill: Advocates for CosmosWasm, highlighting its battle-tested nature and cost-effectiveness in smart contract auditing. +- Scott Hewitson: Reflects on the evolution of CosmosWasm and acknowledges the initial concerns around smart contracts in the ecosystem. +- Nick Merrill: Discusses the stigma associated with smart contracts and emphasizes the need for cautious consideration in their implementation. +- Scott Hewitson: Encourages Nick to share any further ideas or suggestions on GitHub discussions for broader community input. + +### Akash console 2.0 +- Cheng Wang: Discusses the ongoing discussions within the core team regarding the development of Akash console 2.0, focusing on the integration of cloudmos back into the platform and the implementation of features such as payment via credit card. +- Scott Hewitson: Provides context on the upcoming authZ fix and its implications for console 2.0, explaining how it will streamline transactions and facilitate credit card payments. +- Cheng Wang: Expands on the potential workflows enabled by the authZ fix, emphasizing its role in removing barriers to transactions and improving user experience. +- Scott Hewitson: Highlights the significance of the authZ fix in preventing issues such as unused funds in leases, expressing excitement for its implementation. +### Other Matters Discussed +- Nick Merrill introduces DAO tooling for the Cosmos ecosystem, highlighting cross-chain functionality and sub-DAOs. +- Scott Hewitson discusses challenges with community spend props and explores the concept of vesting schedules for props. +- Nick Merrill shares information about Polytonic as a potential solution for implementing vesting schedules without requiring a Cosmos SDK upgrade. +- The team expresses interest in exploring Polytonic further and discusses its potential integration into the Akash network. +- Scott Hewitson emphasizes the importance of open and collaborative discussions within the community. +- The meeting concludes with appreciation for Nick's insights and a reminder to continue exploring potential collaborations and innovations. +## Action Items +- Tyler Wright: Follow up with the content writer found on Discord regarding participation in the Sig Design meeting. +- Zach Horn: Review the proposal shared by Tyler and provide feedback or further action as necessary. +- Scott Hewitson: Explore potential collaboration with community initiatives such as "akt to the moon" on CoinGecko for retail exposure. +- Scott Hewitson and Zach Horn: Collaborate on creating a type form for tenant incentives using authz and consider integration into the website as a deployment option. +- Scott Hewitson & Cheng Wang: Initiate discussion with the engineering team regarding the technical feasibility and implementation of the tenant incentives program. +- Nick Merrill: Collaborate on putting forth a proposal in the discussion forum regarding the implementation of vesting schedules. +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Scott Hewitson: All right, GM everybody those that are here and those that may be listening have another time today is another installment of big economics. I know we're in a double digits now, we've been having these for quite a while so It's been fun. Usually how we go with. These are cover a little bit from the last meeting and then go to any discussions any live proposals and talk about any of those kind of things and then you usually have a few agenda items usually some things to update folks on some of the programs we got going on and then we usually open it up to trick questions or ideas or basically anything goes for anyone that wants to bring up Has any great ideas so with that? + +Scott Hewitson: Let's go some proposals since the last call. I think the only School community pool spend was for the pretor Acquisitions just a FY FYI on that one. Pray tower all their code and everything's gonna be open source similar to how the cloud most one happened as well. If anyone has any questions on that we can dive it more into that. From the discussion side. It's quite a few I haven't seen anything really like anyone looking for funds. It's kind of just like early discussions. So I don't think we have anything we want to touch on their Thai. Let me know if there's any discussions that you think would be pertinent to talking about instigate economics. And then let's go to last months. + +Scott Hewitson: call Actually, so I was doing the notes for these we just started last month. Where I'm not gonna be doing a community members can be doing that as part of bounties may not be up yet from last call. Yeah, okay it is yeah, so we talked a little bit about provider incentives a little bit updates there, Andrew G our favorite question guys asking about the fluctuations in GPU capacity and there's a small complaint about that. I was just like some scheduled maintenance. So no issues. We talked about the traitor acquisition and a little bit about the coinbase learn and earn. I want to say up to this point. There's been about 500,000 activations meaning 500,000 people have used the Earth done the learn so it's just getting more exposure out there. + +Scott Hewitson: That was quite a large governance proposal that came up. And yeah, I mean nothing you need. Those are high level points anyone's welcome to check out the meeting notes in GitHub. We record and have transcripts of all these meetings in case you missed one. So feel free with that. I think I'm gonna pass it over to Cheng if there's any updates that you'd like to talk about and then I know I have something I wanted to bring out after. + +Cheng Wang: Yeah, for We can keep it fairly Dynamic. Thank you Huey for the great introduction as always in recap. The first thing is with what you mentioned previously and Zach feel free to timing. If you'd like for coinbase urn of the 500 or so thousand folks who have completed. I think one of the biggest Community questions has been how many new wallets or users And when we say users it's kind of a proxy for wallets, right because on chain, you can really track walls to users not necessarily it's not yet. It's fairly Anonymous there but the proxy there on coinbase at least is over. I would say approximately 98% of those 500,000 wallets that have completed the earn Quest had not held akt in their wallets before so with an indicates is that the vast majority of folks who have completed the earn Quest at least a cautious are in quest. We're not at least + +Cheng Wang: Years of akt previously and now we do have people who are at least a lot more familiar with who we are in a sensibly a little bit wiser about what Akash does who we are and our place in the decentralized marketplace as well as independ. So there's that primary thing as far as provider incentives go a quick report on that which is We did. What? Is it the first pilot for provider incentives and thus far to date we avoid approximately. Let me put a pin in there real quick for coinbase learner and we've spent approximately 1.5 million of the original allocated budget as far as dollar terms. Of course that's kind of cemented now, right because those have been spent and the remaining akt currently sitting there because of the broad Market just + +00:05:00 + +Cheng Wang: Oopsia, shall we say over the last couple days and week or so that the remaining balance is approximately between four and a half and five million dollars that remains as far as the budget goes. So thus far has been pretty good what's coming online next is going to be staking Quest as soon as that gets completed for caution thing that ETA should be relatively soon. The requisite teams are currently working on that technical integration. And so of course, we'll make an announcement when that what's taking goes live. We expect to keep the first campaign running for a little bit just to have some continuity and then we pull things down and revamp for phase two or second Campaign which will include a little bit more, deeper diving into a cost tools like a chat or scxology probably chat. So that's kind of where we are today with coimbase earn with regards to provider incentives. We've thus far your marks. Not your Market, excuse me, but committed + +Scott Hewitson: Awesome. Thank you for that update. There's definitely a lot of things going on from the provider incentives and you in I think we had said anything we do with the community pool. + +Cheng Wang: approximately 3.5 million dollars of the original pool… + +Scott Hewitson: We want as much transparency as we legally can give so I anticipate before the next call. + +Cheng Wang: thus far with a little over a million dollars remaining for phase one of the incentives… + +Scott Hewitson: We'll have some kind of dashboard or… + +Cheng Wang: where reserved the committed side of the pool and… + +Scott Hewitson: some just kind of tracker for the provider incident inside. So people can see they can look on chain stuff and… + +Cheng Wang: that's brought on I think close to a hundred forty nineties over I think 60 H 100s… + +Scott Hewitson: then see where we're at and provide all the information that we can as we should be because this is all public goods funding. + +Cheng Wang: same amount of a 100 I think some a6000s as well in addition to some requisite support around that + +Scott Hewitson: So I think at this point, is there anyone before I go into this little idea that I've had does anyone want to bring up any ideas any thoughts literally anything goes as long as it's related to economics. + +Cheng Wang: High-end storage. So those are kind of where the funds thus far have gone to and they've gone to predominantly two or two providers and were of course trying to find more to diversify the offering and… + +Scott Hewitson: I know Andrew's not here to ask his good one question,… + +Cheng Wang: those conversations are ongoing and… + +Scott Hewitson: but hi,… + +Cheng Wang: as they kind of emerge and… + +Scott Hewitson: we'll give it to you. + +Cheng Wang: as additional spend gets allocated will be reporting on that and… + +Tyler Wright: Hey, real quick. And sorry if you can't hear me that clearly… + +Cheng Wang: in the coming weeks. + +Tyler Wright: but there is a discussion on that. + +Cheng Wang: So all that stuff is coming together and obviously as the resources are committed you see the Wednesday resources as the spend is committed you'll see the gpus counts as well as the specific models that we talked about in The Proposal come online. + +Tyler Wright: I just want to shout out and I responded already Forum. It seems like a Content writer that's coming from the angle of trying to get Finance listing and all that kind of stuff. So I've tried to reach out to him privately and see if they would join this meeting or… + +Cheng Wang: back to you in The Newsroom, Erie + +Tyler Wright: join the Sig design meeting, but I just want to share that strategy that somebody put in discussions around basically, trying to get towards so I just want to put that out there and see if anybody here wants to contribute to discussion or presentation to sick design because they're more of a Content writer. + +Scott Hewitson: Yeah. + +Zach Horn: I'll take a look Ty have you spoken to them directly. Do you have any direct contact outside of the discussion or is that the first thing we've heard from them at this point? + +Tyler Wright: I found a Discord and I ping them and I have not heard back yet. But I also put that message in the public GitHub. So when I hear something I will connect you. + +Zach Horn: Sounds good. I'll take a look at the proposal in the meantime. And let's go from there. + +Scott Hewitson: Yeah, so some I'll say I saw. It two hours ago. So, I don't know if I use coin gecko usually but I'm coin market cap. I think coin gecko has a two there, on the right hand side. They're trying to do community stuff or it's like akt to the moon or this that or the other so I mean, it does seem a little bit more on the retail side, which is fine. we need to exposure retail and actual users deployers providers. So yeah, we'll see what comes of it but Thanks for thank you for calling that out time. Appreciate it. + +00:10:00 + +Scott Hewitson: All Does anyone else have anything else they'd like to Got some Joe thanks for joining Nick. I know your camera off don't feel like you need to say anything or whatever, but if you'd like to feel free, it's a very open forum. All right. It's a human. + +Scott Hewitson: Yeah, no, that's great. thank you for coming and if there's something you want to ask, feel free and Discord or here we try to make all these calls as open as possible. Make sure that everybody feels welcome and feels like their voice can be heard. So appreciate you coming in. All right, I think. + +Scott Hewitson: Yeah, so if no one has anything else they'd like to bring up. I've kind of had this idea for a little while. Now we've talked about provider incentives a two-sided Marketplace. So, we haven't support incentivizing the provider side but I also think we should look at the tenant side if you look at Uber or any other two-sided Marketplace and web they're to get drivers on board, they incentivize it but then to get your first ride get 20 bucks off. I think that's something that we should go after a little bit. + +Scott Hewitson: Especially when if we can make it easier for people to pay with akt or they don't have to get akt. So this network upgrade that I believe is tomorrow. It passed on chain is it a part of it is it fixes off Z, which is a mechanism to basically you can authorize funds from a large wallet for someone to use as deployment funds rather than sending them for funds. + +Scott Hewitson: In the past from overclock side. We've done some campaigns in the past using oxy with also done some tenant style campaigns. The reason I like autzee is because you authorize someone's wallet to deploy but they don't actually have the funds so it's not like hey, here's a hundred bucks and then they go to osmosets and dump it right away. That's always been kind of a little bit of a point that we are something that we have to be aware of so. + +Scott Hewitson: My idea for tenant incentives is once the fixed happens. Basically we say hey, all right, we want to put up, 50 hundred k, whatever the number is. I probably start small and then it would all be through autzee. We could have an easy type form where people say, here's my address. Here's what I'm deploying catch a little bit of information and then we can regularly. on Z folks to deploy I think that. Zeke what's up? + +Scott Hewitson: No, I think that could definitely be a better case. I mean I tend to like the crawl walk run models where it's like, being able to do stuff that doesn't scale is easier to the start. Yeah. I know I'll see faucet that'd be awesome. So how I Envision it is basically, once a week go into a type form from whoever owns the wallet and then just copy paste all the addresses and I'll see them, whatever the number 1,000 bucks or… + +00:15:00 + +Cheng Wang: I'll go ahead Zach. + +Scott Hewitson: … + +Zach Horn: The Hot Potato everyone wanted to jump in right away. + +Scott Hewitson: you can obviously any amount and then just weekly any new ads and… + +Scott Hewitson: the other one. So everyone gets a reality of 1000 bucks every month or whatever and the program ends when all the money is gone. So, you… + +Zach Horn: Here's my thought just based on hearing that I think it's a great idea so essentially it's a free tier like it's the way other large Cloud providers. + +Zach Horn: When you come in you set up an account you get some amount of credit to test,… + +Scott Hewitson: there's I thought about a few ways to gain this and whatnot anticipate to put a little + +Zach Horn: on another ones without naming names. I know it's like 300 dollars I think is the standard. + +Scott Hewitson: Discussion and… + +Scott Hewitson: GitHub to kind of collate all the thoughts and… + +Zach Horn: We could do something like that. + +Zach Horn: And I also agree on just moving quickly. + +Scott Hewitson: everything I'm thinking about… + +Zach Horn: So it's like what's the lightest easiest way that we can just get this up and… + +Scott Hewitson: but yeah, I definitely think we should be hitting it from both sides though. + +Zach Horn: running and test it and just see what the response is. + +Zach Horn: I think the way you described it is probably right. It's like type form, we publicize it get people want to use… + +Scott Hewitson: There's my Huey Alpha for the day Zeke. + +Scott Hewitson: Thanks for that input. + +Zach Horn: if they do they can come in and… + +Scott Hewitson: Does anyone else have anything they'd like to add or… + +Zach Horn: fill out the form we all see and then we can get a sense of… + +Scott Hewitson: any ideas or… + +Zach Horn: what people are deploying and what the usages. + +Scott Hewitson: Also open to hey,… + +Zach Horn: long term something that we might want to think about is Yes,… + +Scott Hewitson: that's a stupid idea. You should be doing it like this. go ahead and + +Zach Horn: Zeke's Comment. You're down the road. Yeah, or maybe even sooner because my thought is if it works and we like the mechanism what we could do is essentially integrated into the website. So it's one of your options to get started. So it's essentially like you land on the website. You say you want to deploy you go and you can see deployments that you can do on the network. You can set up your own deployment with your own akt, if you're ready to really jump in or you can use what would essentially be this free tier to test it out really quickly because that's one of the big pain points. I think with using a caution generals you see it. + +Cheng Wang: Was not originally envisaged with it doesn't come standard within the cosmos SDK. So there had to be, a brand new workaround that the core team specifically Archer had to work on to Really enable this particular feature because I don't think we not see was created. It had in mind right with deployments and everything like that on a caution network is more so around staking and enabling other defy things which are a lot more. Deterministic, I guess and simple it's like hey, you do this action this thing occurs and it's a lot more financially undoing the thing. So I just want to say that and Shout out engineering team. I'll put a pin in and go for Nick. + +Nick Merrill: Yeah, so I'm not to be overly self-serving but I'm a doubt-out developer. And we've had our own kind of ought Z struggles. Let's say and I think this is the kind of use case. I think that this makes a lot of sense. This is the kind of use case. I feel like it may be easier to do in contracts with cosmosem. And you I don't remember if Akash has cosmosom deployed. But if that's a route you want to go down we can definitely talk about that in a separate doubt out conversation for Implement and implementation standpoint because I find mucking around with the cosmos SDK can be often more pain than it's + +Cheng Wang: yeah, that's + +Scott Hewitson: Yeah, I know we do not have cosmosem or any smart contract functionality. So the mother folks have asked for that kind of functionality for other various things. But yeah, I know I'd be interesting to see that implementation and how difficult that would be or I know Greg in the past I think in one steering committee. He said that he doesn't want smart contracts on Akash,… + +Cheng Wang: Yes. Specifically there and… + +Scott Hewitson: but I mean, everything's evolving. + +Cheng Wang: think I agree with Greg's point is it's not that no smart contracts on a cost. But if we're going to increase the attack surface on a cost Network's code base. It's got to be very definitive when we can't just be a single use case or something like that. It's got to be something well proven and anyways, open discussion or so anybody can chime in and pitch in with ideas there and it's not to say we wouldn't integrate laws and more or other smart contracts and into cost Network code base, but it's got to be pretty Rock Solid and bulletproof use case for us to definitely consider that especially just give in the development and trajectory, right? + +00:20:00 + +Cheng Wang: Training models fine tuning Etc and just all the workloads are currently being hosting We're really moving towards right higher-end workloads more Mission critical stuff and high production value workloads, right? That's so Insurance security decreasing not expanding attack surface on necessarily all super important for the network overall. + +Nick Merrill: Yeah, that makes a lot of sense. I totally agree, from the attack surface point of view. It's one of these things where depending on what changes if any you need to make to the SDK. Sometimes we find Smart contracts are easier and cheaper to audit, + +Cheng Wang: Yeah. + +Nick Merrill: whatever changes you maybe the goed but it just depends on the use case, and also the other thing about this too is from a cost perspective, Oak doing a smart contract audit is way cheaper, often then doing a bunch of go code Audits and if you're just talking about a vanilla cosmoism, and then a permission smart contract deploy where the contracts have been audited, Cosmos is pretty battle tested at this point. There's a lot of pvl and in just vanilla cause them and endowed out contracts and whatever so it's like I hear you I do think that there's a legit security trade off there, but I can advocate for Cosmos. + +Nick Merrill: despite my own skepticism. I can advocate for Cosmos itself being fine, + +Scott Hewitson: That's great context and I know as a cosmosom came up like it's been around for what two years now year and a half. I know at the beginning people were kind of worried about it or causing laws on the Hub and all this stuff. But yeah to your point. I think it's getting to a point where it's kind of battle tested. + +Nick Merrill: Yeah, I mean I think people hear smart contracts and they think this is gonna be permissionless. Anyone can upload a smart contract scenario and… + +Scott Hewitson: Yeah. + +Nick Merrill: I think that that is often like… + +Cheng Wang: exactly + +Nick Merrill: where a lot of the hesitation comes around. people stargaze + +Cheng Wang: the same ethereum + +Scott Hewitson: For Just too much PTSD from all these rug pulls on ethereum,… + +Nick Merrill: Yeah, exactly, + +Scott Hewitson: . + +Scott Hewitson: So no, that's a great point. honestly if you have any ideas or feel free to bring it up in discussion. So Nick if you're not aware kind of we do redirect folks to or GitHub discussions, they kind of bring up ideas or ideas for gov props when they want to see funding or just ideas in general. So I would encourage you if you have any ideas like that to drop it in there. Alright Cheng beat me to it. + +Nick Merrill: Awesome on it. Thanks. + +Scott Hewitson: awesome Yeah, so anything else anyone wants to bring up? + +Cheng Wang: yeah, sorry I've not the idea but we put a pin in. So the core team has been kind of discussing what console 2.0 ultimately, cost console 2.0 would look like and of course now that when we say console 2.0 that incorporates the + +Cheng Wang: merging of cloud most back into a cost console and having the deployment natively, of course via Kepler and all that stuff is always going to be there the permissionless side. But of course, there's going to be the free tier stuff that we have to consider the stateful interface where people have to create a login and all that kind of stuff and all that is to enable ultimately at some point in time. Hopefully in the near future payment right credit card payments things like that. So the authy that's been pushed through today can help facilitate pave the way to that and make credit card payments a bit easier. So you can imagine a world where someone comes in let's say right let's say everyone here's is familiar with cryptocurrency changes. You go into an exchange you set up an account, Your account is automatically associated with potentially a bunch of different addresses of assets that the platform support right? So let's say you want to + +00:25:00 + +Cheng Wang: Create an akt deposit address and generous and KT deposit address Associated to your account ID in the cases where memos are needed. I guess Memo's kind of serve similar purpose. And once that's done you can then transact and deposit akt as you wish So you can imagine a case where you create a login if you wish to go through the kind of managed route that login then automatically spins up an akt address on the background and whenever you purchase credits, akt gets all the Z right or us economics gets all these to your account to health facilitate transactions very quickly and that + +Cheng Wang: Is one of the potential workflows that it doesn't enable and of course with the push that's being with the fix that is being pushed through and what just about a day from today will enable kind of remove the issue of when you kind of bring in deployment down for whatever reason,… + +Scott Hewitson: Yep, and just for anyone who is unaware of how opsy the fix that is happening. So basically the scenario is I ought to zaching a hundred akt he sets up a lease with you… + +Cheng Wang: right, you can't find a suitable lease the funds get returned to your account. So you don't kind of have to continue to auth Z. + +Scott Hewitson: and the hundred of that it goes into the escrow account. + +Cheng Wang: So that'll really help pave the way for one of the aspects of constant 2.0 as far as enabling beyond our credit card payments. + +Scott Hewitson: He makes a mistake or he wants to change something or change providers. So he closes at least after spending five. Akt instead of having 95 akd left over he has zero akt so that's the fix. So yeah, I'm excited for it just… + +Nick Merrill: Yeah, sure. That's + +Scott Hewitson: because we did campaigns with it a long time ago, and it was a pain But yeah,… + +Nick Merrill: Yeah, I can feel the collaborative space. Yeah, so I'm a core developer of data. + +Scott Hewitson: no, I… + +Nick Merrill: We make a dow tooling for the cosmos ecosystem. + +Scott Hewitson: A great discussion. Does anyone else want to bring up anything? + +Nick Merrill: We're built on top of cosmosem. All of our smart contracts are written in rest and… + +Scott Hewitson: And if not Nick… + +Nick Merrill: we provide interchange doubt tooling. + +Scott Hewitson: if you don't mind,… + +Nick Merrill: So we make Dows… + +Scott Hewitson: I know you said you work for or… + +Nick Merrill: where those dowels can execute arbitrary actions on any other chain that supports Cosmos,… + +Scott Hewitson: you're doing some dowdow if you wanted to don't feel like you could give everyone a 30 second to a minute on … + +Nick Merrill: that down on one chain and… + +Scott Hewitson: what you're doing. We're always open to seeing… + +Nick Merrill: it can do stuff on another chain and you can use IBC to send the assets all around and… + +Scott Hewitson: what folks are working on and it's a very,… + +Nick Merrill: it creates,… + +Scott Hewitson: … + +Nick Merrill: this cool kind of like cross chain down kind of effect. + +Scott Hewitson: collaborative space. So always interested. I know Dao so I mean,… + +Nick Merrill: You… + +Scott Hewitson: it's pretty sweet that you're here. Just out of the blue. + +Nick Merrill: we're on a bunch of chains already, we power kind of a dow ogp Juno was governance runs on us and we kind of fancy ourselves like an ex go replacement. yeah, I think that that's kind of probably the 30 second elevator pitch on doubt. + +Nick Merrill: Yes, we have that. That's the core feature. that we implemented that for a variety of other people. + +Scott Hewitson: I appreciate that and I'm thinking about smart contract and… + +Nick Merrill: We also do core vests with veto flows so you can cancel the vest at any future time through governance or… + +Scott Hewitson: thinking about doubt something that is kind of a pain is when we do have Community spend props,… + +Nick Merrill: one and we also have this notion of sub Dow so you can have … + +Scott Hewitson: right you… + +Nick Merrill: main governance that can have a committee that committee can be revoked and… + +Scott Hewitson: you put up a prop for 50,000 akt and… + +Nick Merrill: you can auth Z authorizations to that committee canvests stuff and… + +Scott Hewitson: then you get it right away. a lot of folks, depending on their jurisdictions,… + +Nick Merrill: then the parent out and… + +Scott Hewitson: they don't want to get that big chunk right away. + +Nick Merrill: cancel the vest or remove that capacity in the future,… + +Scott Hewitson: They want to invested over, you… + +Nick Merrill: whatever we do that stuff all + +Scott Hewitson: a year or something. are you aware of anyone doing any kind of vesting schedules for props? + +Scott Hewitson: If hell, yeah. + +Scott Hewitson: Awesome. I think that's I mean for me personally,… + +Nick Merrill: Have this other solution called polytone. + +Scott Hewitson: that is something that is very interesting. + +Nick Merrill: It doesn't require any Cosmos SDK upgrade or… + +Scott Hewitson: Do we need to'd imagine I don't think I see entertain accounts… + +Nick Merrill: to integrate. + +Cheng Wang: Do you have any documentation we could check on me? + +Nick Merrill: I see. yeah,… + +Cheng Wang: This is super cool, man. + +Nick Merrill: totally. Let me link to that. Just take me. + +Scott Hewitson: because we don't have packet forwarding at the moment. + +Cheng Wang: alright + +Scott Hewitson: I believe that that's something that would need to be. + +00:30:00 + +Tyler Wright: And the packet forward and stuff as well. We have that as a part of the roadmap. So if you have any thoughts there, that would be greatly appreciated. + +Nick Merrill: Yeah, that's right so you can check out I put in the chat our docs on polytone so you can have a look at… + +Scott Hewitson: yeah, if you put up something in discussions about, vesting off of community spend personally I would support that and… + +Nick Merrill: how that works. + +Nick Merrill: Yeah, it only requires IBC. + +Scott Hewitson: three seconds but + +Cheng Wang: That is pretty sick. Thank you, Nick. + +Nick Merrill: Yeah, I'll definitely put something in the chat in the sorry, Scott. + +Scott Hewitson: I think he was saying that it's not necessary. what they've built doesn't require ICA or packet forwarding to get the job done. Is that correct name? + +Scott Hewitson: Nice,… + +Nick Merrill: Absolutely, Innovations all about ecosystems for sure. + +Scott Hewitson: I will definitely be reading over that for sure. + +Nick Merrill: We'll put a prop up on the discussion super soon. + +Scott Hewitson: Okay. awesome + +Scott Hewitson: Yeah, you never know who joins the calls. Yeah, no. No, I'll just say hey this is great. You never know who joins the chat and that's lovely try to be as open and welcoming as possible because clearly what you're working on. Did you know there could be some mutual beneficial relationships going on so + +Scott Hewitson: Hell, yeah. + +Scott Hewitson: That'd be great. That would be great. + +Nick Merrill: Thanks, everyone. + +Cheng Wang: Thanks, Harry. + +Zach Horn: Thanks guys. + +Cheng Wang: Thanks ever. + +Zach Horn: Thank you. + +Cheng Wang: Thanks, Nick. + +Scott Hewitson: awesome All righty. I don't have anything else. Does anyone have any last remarks or ideas or things they'd like to talk about? + +Scott Hewitson: All with that I think I'm gonna stop the recording. Appreciate everyone coming. Thanks again, Nick for giving us all your insights from downtown looking forward to some of that stuff coming forward and we'll be in touch and Good to see everybody. Take care. + +Meeting ended after 00:32:03 👋 + From 0538cd359e6fc7a835574fe5d62074338a10fbcd Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 11:26:21 +0000 Subject: [PATCH 057/138] Create meeting notes for sig docs #15 (#564) * Create meeting notes for sig docs #15 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 015-2024-03-26.md add transcript for march 2024 monthly meeting Chore: add recording Signed-off-by: Drinkwater * Update 015-2024-03-26.md add recording link for meeting 15 Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-documentation/meetings/015-2024-03-26.md | 278 +++++++++++++++++++ 1 file changed, 278 insertions(+) create mode 100644 sig-documentation/meetings/015-2024-03-26.md diff --git a/sig-documentation/meetings/015-2024-03-26.md b/sig-documentation/meetings/015-2024-03-26.md new file mode 100644 index 00000000..3c6ca95f --- /dev/null +++ b/sig-documentation/meetings/015-2024-03-26.md @@ -0,0 +1,278 @@ +# Akash Network - Docs Special Interest Group - Meeting #15 + +## Agenda +- Welcome and Introduction +- Review of Documentation Updates +- Community Contributions and Collaboration +- Addressing Documentation Issues +- Discuss the migration of documentation from old URL to Akash.network/docs. +- Future Plans and Initiatives + +## Meeting Details +- Date: Tuesday, March 26, 2024 +- Time: 7:00 AM PT (Pacific Time) +- [Recording](https://7lvvy6qbe6wq3tzg3zl2vbxvamshk5ibb3bi32m6fbt5vwdlonpa.arweave.net/-utcegEnrQ3PJt5Xqob1AyR1dQEOwo3pnihn2thrc14) +- [Transcript](#transcript) + +## Participants +- Andrey Arapov +- B S, +- Denis Lelic +- Joao Luna +- Scott Carruthers +- Piyush Choudhary +- Thomas Greco +- Tyler Wright +- Zeke E + +## Meeting Notes +### Tyler wright +- Tyler Wright welcomed attendees and outlined the meeting's focus on Akash Network documentation. +- Noted the previous hosting of documentation on docs.datacos.network. +- Highlighted the recent migration efforts led by Scott Andre and others to move documentation to Akash.network/docs. +- Mentioned the URL change and switch from /docs to /docs leading up to the last meeting. +- Acknowledged the decision to consolidate all docs onto Akash.network/docs, with Andre's assistance. +- Identified ongoing issues related to migration. +- Emphasized the need for clarity in phase one of the migration. +- Thomas is Working on CLI documentation, adding 11 labs and creating a series of videos. +- Thomas has already been involved in contributing to documentation. +- Bounty available for community members willing to review and audit documentation on Akash.network/docs. +- Task involves identifying redundant or outdated documentation, addressing spelling issues, and aligning the structure with the new format decided by the group. +- Review documentation comprehensively for redundancy and outdated content. +- Address any structural changes needed to match the new. +### Bounty Assignment Process +- Thomas has already begun reviewing and opening issues for documentation revisions. +- Acknowledges the value of a second set of eyes for confirming changes and avoiding oversight. +- Tyler will create the bounty and share it in the SIG documentation channel. +- Thomas will comment on the bounty with hours and an hourly rate to get started. +- Fixes may vary from simple spelling corrections to more complex formatting discussions. +### Piyush Choudhary's Update +- Raises an issue regarding Cloudmos documentation and the transition to Akash console. +- Shares a link for further discussion and mentions plans to create a PR. +- Tyler acknowledges ongoing discussions and invites Scott to provide input. +- Explains that the rebranding process for Cloudmos console is still in progress. +- Mentions the recommendation from Sig design to merge documentation into Akash Network/docs until the rebranding is complete. +- Thomas asks if Tyler is referring to his PR, which renamed mentions of Cloudmos to Akash console. +- Piyush confirms they are discussing a different topic, unrelated to Thomas's PR. +### Documentation Migration Status +- Scott and Andrey have identified items not yet migrated from the old documentation hosted on GitBook to Akash.network/docs. +- Recent discovery that Cloudmos documentation was missing from the new documentation +- Tyler suggests merging the staging link provided by Piyush to ensure Cloudmos documentation is live on Akash.network/docs. +- Plan to update the documentation further once the Cloudmos rebranding is complete. +### Discussion on Website Redirects +- Piyush raises concerns about the website directing users to Akash console instead of Cloudmos. +- Scott expresses confusion about the redirection and questions the status of Akash console. +- Tyler acknowledges the issue and mentions previous direction to update the deploy Now button. +- Tyler emphasizes the importance of focusing on completing the rebranding process. +- Scott explains the complexity of the situation, emphasizing the need to maintain Cloudmos deploy documentation until a clear transition to Akash console is announced. +- Highlights the need for new documentation sets for Akash console, as the existing documentation is based on the previous iteration of Akash console. +- Piyush agrees with the explanations provided and plans to make a PR to push Cloudmos content to the main site. +### Agreement on Removing Akash Console Documentation +- Tyler acknowledges Zeke's suggestion in the chat and expresses agreement. +- Scott confirms that there have been discussions about removing Akash console documentation. +- Explains that a header was added to the documentation indicating that Akash console was no longer being developed. +- Scott plans to submit a PR to completely remove Akash console documentation after Piyush's PR reintroducing Cloudmos deploy is merged. +- Thomas indicates that his questions have been answered and expresses thanks to Scott. +- All concerns and questions regarding the removal of Akash console documentation have been addressed, and the plan for action is clear. +### Thomas's Feedback on Docs Site Content +- Thomas mentions some small issues with the website content that he wanted to address. +- Specifically points out clarity needed around the placement of technical content within the "Getting Started" section. +- Highlights the section titled "Transactions" within the "Bids and Leases" subsection as being too technical compared to the rest of the beginner-friendly content. +- Tyler asks for comments on the placement of technical content within the "Getting Started" section. +- Encourages asynchronous feedback if anyone needs more time to provide input. +- Tyler appreciates Thomas bringing up the issue and encourages further discussion or feedback from the team. +### Discussion on Video Documentation +- Thomas inquires about the placement of video format documentation. +- Piyush suggests hosting videos on YouTube and embedding them within the documentation if they are highly official. Otherwise, they can be showcased on Akash education with limited minutes. +- Thomas agrees with the proposal and mentions having a dedicated Akash branch for hosting videos. +- They discuss the possibility of adding watermarks or branding to the videos, with Piyush sharing branding guidelines. +- Tyler mentions Denis from the working group volunteering to help with graphics and editing. +- Thomas appreciates the support and mentions using Scott's resources and potentially reaching out to Denis if needed. +### Issue with Documentation Discrepancies +- Scott raises concern about discrepancies in the documentation, specifically mentioning missing steps in certain sections. +- Scott provides an example where a step for changing the default persistent storage class is missing in the inventory operator section. +- Scott suggests running a new diff to identify missing documentation updates from the period preceding the migration to the new documentation site. +- Piyush agrees to conduct a thorough check to identify missing updates and push the necessary updates. +- Tyler acknowledges the issue and marks it down as an action item, thanking Scott for bringing it up. +### Discussions on Docs migration process, and audit process. + - Tyler mentioned the need for further discussions on Akash.Network/docs, migration process, and audit process before moving to other agenda items. + - Initiated phase one of the Bounty for the documentation audit. + - Tyler encouraged participation in documentation contributions, emphasizing the need for spelling changes, identifying outdated information, and making PRs. + - Thomas shared progress on videos intended for the documentation site, aiming for consistency in voice and structure. + - Scott addressed issues with dark mode rendering, resolved by fixing HTML tags in the code block. + - Scott highlighted an issue with copy-pasting from code blocks in Brave browser, noting it works in Chrome but not in Brave. + - Piyush agreed to investigate the issue with copy-pasting in Brave browser to find a solution. + +### Clarification on the use of Akash console versus Cloudmos deploy. +- Andrey raised a question about the use of Akash console versus Cloudmos deploy, regarding a pull request to the awesome Akash repository. +- Scott clarified that the old Akash console is no longer being developed, and Cloudmos deploy will eventually become the new Akash console through rebranding efforts. +- Andrey acknowledged the clarification and expressed intent to forward users to Cloudmos deploy. +### Discussion on the introductory Section of the Documentation Site. +- Scott Carruthers shared his screen to discuss an area needing urgent attention in the documentation, particularly the intro to Akash section. +- He emphasized that the issue is not technical but related to content. +- Scott suggested that the intro to Akash section could be enhanced to provide a powerful and effective introduction for new users. +- He praised existing sections such as the overview of the Akash topology and descriptions of validator and provider nodes. +- Scott expressed concern about including technical details like desex, G6, and transaction types in the intro section, suggesting they are better suited for deeper sections. +- He recommended revising the intro to focus more on providing a clear and user-friendly introduction to Akash for new users. +### Bounties for Documentation Improvement +- Tyler announced three bounties emerging from the discussion: + 1. General audit of documentation. + 2. Akash console documentation update. + 3. Rewriting the intro to Akash section. +- He encouraged participants to provide estimates for time and hourly rates for contributing to the bounties. +- Thomas expressed difficulty in estimating the time needed for the documentation audit but offered to dedicate five to ten hours per week. +- Tyler suggested monitoring progress weekly and breaking down the audit into manageable sections. +- Thomas anticipated that smaller bounties might emerge from the larger audit. +- Tyler expressed appreciation for everyone's contributions and encouraged continued involvement in improving documentation. +- The meeting concluded with thanks from Tyler, Scott, Andrey, Thomas, and Piyush. +- Meeting ended after 00:57:59. +## Action Items +- Tyler and Thomas to discuss watermark placement with Denis offline for uniformity in future videos. +- Piyush to investigate and potentially implement a solution for the copy-pasting issue in Brave browser. +- Piyush will conduct a fresh diff to identify missing documentation updates. +- Scott to submit a PR to completely remove Akash console documentation after Piyush's PR reintroducing Cloudmos deploy is merged. +- Tyler to create a bounty for documentation review and share it in the SIG documentation channel. +- Group to merge the staging link provided by Piyush to incorporate Cloudmos documentation into Akash.network/docs. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: Excellence this group for documentation is a monthly meeting where the group goes over any thing related to a cost documentation. This is certainly a special interest group where Community contributions are very much welcomed and very much needed. I know there's a couple of folks that have been contributing here already. A couple of high-level announcements before we get into the agenda. One if anybody is creating any issues which again documentation now lives in the website, so if anybody wants to contribute to documentation you go into the website repo. I'll share my screen. + +Tyler Wright: He was on the call human HQ have an outline clear instructions on how folks can interact with the docs and contribute beyond that when you go to the issues Any issue that's related to documentation. I see that Thomas already put a dox tag here. I'll also label anything with documentation just so we clearly know is related to the docs and the docs page as opposed to again other parts of the Akash website. For the pull requests. I'll make sure those are labeled too so we can do the same thing there. But as you can see Thomas is already done some labeling. So we'll talk about that a little bit later but much appreciated everybody that's looking to participate for following that structure. + +Tyler Wright: cool In it,… + +Thomas Greco: Yeah, no. Problem Ty happy to help set the standard. + +Tyler Wright: go ahead. + +Tyler Wright: right A couple other things to note on a high level there is a mainnet upgrade planned for next week with that. There will be some documentation that will be added to the website members of the core engineering team will continue to handle those upgrades because they'll be testing upgrades making sure that everything is working sleep seamlessly and so again can update documentation. But once that documentation is experimental. I'm sure I'll just get shared with folks for sanity check. But again, that's something that will continue to be handled by the core team. + +Tyler Wright: Cool outside of that. I know that at a last couple of meetings we've talked about. contributions from the community of just General I know peers was going to do another version of just checking to making sure that the old documentation sites that was docs at a cost.network That's all the docs and now reflected that we're on the dark side of caution Network are now reflected on network slash docs. So I know it's something that piyush has been doing. I know that there's other members of the team some folks here and some folks are not here that have been asked to help audit various pages of the website just to make sure that again the user experience is optimized as possible, especially because there's so many documents that have been migrated. So I think we'll talk about that a little bit later. + +Tyler Wright: In addition, I know that Andrey and some other folks in the community had a request to work on the search for the documentation because it was increasingly hard for folks that were searching for basic keywords to find the documentation that we're looking for. I believe there was a PR that was merged that should help to solve that problem. So, Thank you for those contributions as well. We can talk About a little bit. But again if there's anything else that anybody wants to bring up outside of those subjects. + +Tyler Wright: There's also some documentation that needs to get done for the Akash console. Once that. Brand has been transferred from cloud those two console. There will be an updates. They'll be shared. I think a couple of people have reached out about being able to help with that contribution help with that documentation. Once there's a staging site available. I'll give folks access that staging site so that they can pull more recent screenshots to update that documentation. So again, I'll follow up with folks and you think documentation Discord Channel. + +00:05:00 + +Tyler Wright: One last thing that I believe Scott brought up maybe even that last week last month, was around just a couple of hierarchy pages. I think Thomas brought up a good point that some of the content on the docs page might be a little bit too detailed for some users and can be read classified and there might be a need for some hierarchy pages that just talk at a high level about what some content is. do I know that's something that it's been worked on and talked about go ahead Thomas. I see your hand up. + +Thomas Greco: Yeah, so I piyush was nice enough to take time with me. before this meeting + +Thomas Greco: and that was one of the things that we discussed. I'm happy to kind of publish the feet the feedback he gave me the information he gave me during that conversation. But basically I wasn't sure about the best way. to go forward with getting issues such as that addressed and I think that piyush helped me with kind of figuring out a flow for that which is really opening up issues and getting those addressed accordingly whether I'm the person to work on it or whether the issue creators the person to work on or somebody else. They can kind of be decided. But yeah, I just wanted to + +Thomas Greco: mention that because I did bring it up and there hasn't really been any progression I think on that and just so for the reason. + +Tyler Wright: So just add a little bit of clarity there again, if anybody here sees any documentation issues, inside of the website repo inside of the issues area, you can create an issue we'll look to discuss those issues at these calls or in between these calls and then again anybody that wants to participate in solving that issue can leave a comment. + +Tyler Wright: There are rewards available for State documentation because our core engineering team is working on so many other things that again contributions for documentation for most everything besides again a couple things that upgrades and some other small items is certainly needed and welcome. And so again after creating an issue and we can tag a documentation, then we can talk about it or we could do an async to assign that issue to somebody with it a lot of amount of time and Once the issue is the time that person can work on interlocks continue to track it. And then what's the pr is in there? Then again piyush can work on merging and if he has any questions or if anybody needs to be involved whether it be from the core engineering team to validate any of the documentation Etc and we can do it at that time. + +Tyler Wright: Go ahead. + +Piyush Choudhary: So I would like to ask some questions to Andrey. So we escaped some issues related to updating some of the content on some of the pages of the docs. So it would be great if you can provide some information around those issues. So I had a child with Thomas Wells a shorts and invest in updating those videos special issues sleeping. And so yeah, we play some more information about what they mean when I say move and you say something like that. + +Andrey Arapov: Do you mean you need more information for the issues that I created under website Repository? + +Andrey Arapov: there are only a few send I think they're pretty much descriptive there. So there's stuff like missing your eyes in one step and then there should be some directions to mentioned in on the commentation and the other one should be just removed all the information from Predator. It's basically as what it says there and if you need any additional information, please feel free to and any questions under this issues directly in form of comments. And usually I'm trying to look at them. Sometimes just being me on track or Discord and even if you don't want to directly the questions there for whatever reason just like again me somewhere on slack or in the common chat. There is a website external in slack. So feel free to ask any additional questions because the reason why I created those because at least for my eyes they seem to be fully descriptive. + +00:10:00 + +Piyush Choudhary: So basically we have to extend the descriptions as presentation. + +Andrey Arapov: Sorry, I couldn't hear you. + +Piyush Choudhary: So I'm saying basically have to remove some of the things as for this elections and also expend the descriptions specialization to recommendations, right? + +Andrey Arapov: Sorry, I think I have either connection problem or something. I'll try to change to my headset or what my better just to ask me to the better. It will save more time. Thanks. + +Tyler Wright: Yeah. Maybe Pierce. I don't think it's you Andrey. I know piyush is getting a new mic very soon. + +Tyler Wright: if you want to drop a specific issue or specific questions inside these issues again, I think I can follow. What Andy's looking for in each of these again? I think he's structure them pretty clean. But Thomas if you are going to take on some of these issues or anybody here, if you have any specific questions on the ask just drop them specifically in this comment, that would be best so we can just track it and then once those questions are answered and we can have somebody like I'll take this because I think we want to get these kinds of things updated quickly. + +Piyush Choudhary: yep, I think it's on Scott. + +Tyler Wright: For whatever. You did pierces must clear now. + +Piyush Choudhary: Yeah, I think hiroyuki has some questions regarding how to get rewarding the dogs. So I would say I think you to see R Scott accepted into the docs. So I just said I suggested to basically bring in a program basically very reward accepted pios, whoever creates a PR and the plates update we can have some rewards for the things. So this is something I also suggested in the city dogs channel. and I think it makes sense for all the uses. + +Tyler Wright: Yeah those already and a amount of money for documentation. via the community support + +Tyler Wright: it's like a prop that went through earlier in the year. ic Heroku is someone that I have been actually talking to on that. It's looking big looking to get involved in a number of different ways. And yes for accepted PRS we will for certain items be paying out rewards and I'm going to talk to heroically about those rewards for him because we would love for them to get more involved in this. + +Tyler Wright: Special interest group I think we can have a structure maybe over time. But as we continue to get contributors involved again, please feel free to put how many hours and a rate if you want to inside the comments. Otherwise again folks know how to get in contact with me and we can work offline to figure out like a structure for now. + +Piyush Choudhary: I think it's transferred. + +Tyler Wright: Go ahead Scott. + +Scott Carruthers: yes, so some of this is interesting and I think it's just a sign that we're kind of going through a evolution of how documentation is added and edited and how were the community is involved and where the core team is involved. so where you brought up one issue that was created by Andy that had I believe a cloud most screenshot. Is that the doc audit RPC on No, that was actually created by time. Yeah, go into. I messed it. Yeah that one. I'm just using this as an example, so I guess a couple of questions and these regards as issues are. + +Scott Carruthers: created in the support repository we go through weekly. meeting for assignment of open issues. I'm wondering how that happens in the website repository now, so Andy creates this issue. and how do we have management and I guess he'd like even the expectation when Andy creates this issue is the expectation that piyush or someone from the community is going to take it or is it possible that Andy creates this issue and then he still takes it himself or one of the core team members takes that I guess this is just kind of interesting because I'm not sure that we've ever really gotten into this and I'm also kind of interested because + +00:15:00 + +Scott Carruthers: just based on history. It would be my natural inclination that if I see something in documentation the needs update in that a lot of times I would just go in and do it and now I'm wondering does that process and flow need to change? + +Scott Carruthers: on anything that comes up and we should be creating issues and I shouldn't just be going in and Updating documentation myself, but I should give the community the opportunity to do it. So long, wait a way of I guess specifically what I'm asking is how do we guarantee the issues that are created are assigned properly and should an issue be opened for any documentation update and we first give the community the opportunity to update. + +Tyler Wright: I have thoughts on all about but I'm Jaco first because his hand was up. + +Andrey Arapov: Yeah, I just want to say that for my personal point of view. Yeah, I do agree that the best one you have something to fix or just go and fix save time for you and the others but in my particular case, I was either busy with something else on the provider side or you had time for that or maybe even had mood for that. So I just found the issue and I just filed it up and for anyone to take it whoever wants to take. It's very easy to create a little PR just while the new screenshot create a PR and the issue is basically solved making. + +Tyler Wright: Excellent I love tears go first, but then I'll speak after that. + +Piyush Choudhary: So someone onto that validation is being created for the dogs updated it's a major updated writing some new documentation celebrating the power of new proper text or additions of commands and all and I think it should be done by the core team to make sure that the things that are being updated on the dogs are up to the mall as to the standards and whenever the updates about the places of things already reading some things like fixing some final things and I think it can be done by anyone. So yeah, that's not yeah and + +Piyush Choudhary: It is. + +Piyush Choudhary: Yeah, sounds good. + +Tyler Wright: Yeah, I would agree with many of those points Scott, I guess to answer your number of questions in order from a structural standpoint. And again, this is very much like an evolution process. So as I see it, if a member of the core team, he's some documentation that they have the ability to change or it's urgent enough that they think it needs to be changed. I would say that they continue to move forward changing that documentation, especially if it's a quick effort and then go through the pr process but again the pr can easily and quickly be merged. if there's an issue that is something that + +Tyler Wright: Either an entree's case. He doesn't have time for and it can be changed. It's all right for anybody to make an issue and then put it for somebody else to assign. I think it's a part of this docs. We are going to as a part of the agenda take any issues similar to how we do in six support which reaction those issues and talk about it in the open issues and see If anybody on the call wants to be assigned to them if they aren't already taken by somebody async between meetings because people again to leave comments on any of the open issues. If somebody from the core team is working then they should just assign themselves the issue and again that will just show that nobody else from the community needs to get involved. + +Tyler Wright: I don't think we have to worry about giving Community contributors the opportunity to get all issues that I think there's enough issues to go around. And I would leave it up to the Judgment for Scott's and Andre whether it be new documentation or what else do you are on the ground floor in the testing phases if you all think it's something that the community can help and you don't have the bandwidth. it's really all about helping to manage your bandwidth because as I said on many calls like a lion share + +00:20:00 + +Tyler Wright: With documentation has been Rewritten over years by Scott and with support from Andre and I know that's been very taxing on Scott amongst all the other things. So again getting other people from the community Steve documentation that our Technical and can help this isn't the wrong place. this can be improved to make it clear for users. there are rewards for those kinds of contributions and we would ask people go from through the flow of making an issue getting authorization from this sig that this is a worthy issue that needs to be changed. And then from there just either assigning that to themselves or somebody else from the community can be assign the issue and look to solve it in a timely fashion. + +Tyler Wright: We'll track any of these open issues on a meeting by meeting basis so that if an issues like sitting there long and somebody was supposed to take it then we can reassign it but God as your talking about six supports something I was thinking about earlier today, especially as we get more Community contributions is maybe change the Cadence of this meeting to happen more often the working group for the website six support happens every two weeks because there's just so much happening in those six and it may be + +Tyler Wright: Especially as we continue to grow a good thing to have Sig documentation more frequently. So that contributors can talk about the status of the things that they're working on or we could talk about any open issues. But again that we'll see how I'll keep it for one month monthly for now, but we'll see how issues evolve and over the next couple of weeks and we can work async to again continue to say that hey I got this issue. If somebody has an issue as an example if I create an issue and I want to solve it myself. I would create that issue and I would say that I think this is an issue that I would drop it and say documentation tag, everybody and we can talk async about This makes sense. This is something that you should move forward with and then we can work on the side and if we don't want to wait a month to work on some of these issues + +Scott Carruthers: All… + +Tyler Wright: notice a long-winded answer. + +Scott Carruthers: Yeah, I think that. + +Scott Carruthers: I think that all makes sense. Yeah, I would think that. I'm fine with 11 ago sometime and see how it goes. But if we're going to use this call to do triang of issues just as we do in the sport called that. + +Scott Carruthers: Being on the side. I mean we can definitely give it a month and maybe that proves not to be an issue because piyushen others are kind of on top of this and It's just not necessary to go through that life triage. But if we have a high volume of issues and we want to make sure of timeline assignment and that nothing is going. On triage, then. Yeah, I would seem like we probably have to consider going to every two weeks. + +Tyler Wright: Yeah, but again, I have no problem with because I think a lively group is being built up. I know there's a couple of people that reach out to me privately talking about getting involved in documentation outside of the folks have even on this call that I've already contributed. So I don't have a problem. But I know that many folks are quite busy so we can talk about offline and figure out the best action. Go ahead Thomas. + +Thomas Greco: yeah, I was just gonna say in the event that there is a high priority issue from somebody from overclock kind of spots and nobody can get to it. I definitely feel free to have being me about it. And if I have the ability to the type priority and I have the opportunity to get to it quickly. than that will otherwise, I'd just say now I'm unavailable. But yeah, I just wanted it seems like there's some issues that there's some instances where this might come up so. + +00:25:00 + +Scott Carruthers: Yeah, so I wasn't raised my hand because of anything that Thomas just said specifically so if anybody has a response to that what he just said makes sense to me and appreciate that. He's reading his hand to take on any virgin issues. I was going to cover a different topic as Any other thoughts on that before we move on? + +Thomas Greco: God. + +Scott Carruthers: Okay, so I was also just kind of curious as we're looking at issues Tower. Can you go back to the list of issues + +Scott Carruthers: so I just I guess want a little Clarity and this might just be like a one-off question possibly this is maybe something that we need greater understanding of but I'm a little bit confused on it seems like we intentionally labeled the GPU pricing explanation or GPU pricing explainer that we intentionally labeled that Some good just kind of curious and like I said, maybe this will be clarifying to some other future assignments as well. So that the GPU pricing page exists on they network. So why would a GPU pricing page explainer B classified as docs our way? are we thinking that while the GP pricing page exists on a cost.network there would be an explainer in the documentation site or yeah, just some further Clarity on why that's label Docs. + +Thomas Greco: So I open up that issue. I can kind of speak to it. I think that So the reason my apologies I think for maybe incorrectly tagging that. as docs I think it's just the reason why it was tagged as docs is because I am primarily working on documentation issues, so that was why I think it was maybe a mixture of that and then the mixture of just the whole. + +Thomas Greco: idea behind it. documenting. what the different chipsets are and kind of differentiating between them. but yeah, sorry for any confusion there and feel so yeah, this was something that I personally + +Thomas Greco: as someone who has a minor amount of knowledge around the different GPU chipsets I thought + +Meeting ended after 00:52:40 👋 + From be9b154d3250f4f0df55bb7dbd8bce7a36f44445 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Fri, 24 May 2024 07:36:40 -0400 Subject: [PATCH 058/138] steering committee Update README.md added video link for meeting 05/02 chore: add recording link for march 28th and notes + transcript link for meeting 05/02 Signed-off-by: Drinkwater --- committee-steering/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index c7eb35e3..39f1d9ce 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -27,8 +27,8 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, December 07, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md#transcript) |[Link](https://k6mud4r2ua6xarj6c5zqtkxw6fzjrvzjzu6eotsyhsmotles2gaq.arweave.net/V5lB8jqgPXBFPhdzCar28XKY1ynNPEdOWDyY6ayS0YE) | Thursday, January 25, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md#transcript) |[Link](https://uh4qrdp5wsvzihnnh7m7conzwkllrei4xawnfsohgjmp5qpjberq.arweave.net/ofkIjf20q5QdrT_Z8Tm5spa4kRy4LNLJxzJY_sHpCSM) | Thursday, March 7th, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md#transcript) |[Link](https://aqjulyegruxs4xdwltfkkxqieagkmqc7dcbewovdw2wk7tj72hka.arweave.net/BBNF4IaNLy5cdlzKpV4IIAymQF8Ygks6o7asr80_0dQ) -| Thursday, March 28, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md#transcript)|Coming Soon -| Thursday, May 02, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, March 28, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md#transcript)|[Link]( +| Thursday, May 02, 2024 11:00 AM PT (Pacific Time) | Coming Soon |Coming Soon |[Link](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) | Thursday, June 06, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, July 25, 2024 11:00 AM PT (Pacific Time) | | | From e71a20f982cc15b23e31348927e5cc0ccc051d18 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Fri, 24 May 2024 07:37:24 -0400 Subject: [PATCH 059/138] Update README.md add link for meeting 03/28 Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index 39f1d9ce..9c97b688 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -27,7 +27,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, December 07, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md#transcript) |[Link](https://k6mud4r2ua6xarj6c5zqtkxw6fzjrvzjzu6eotsyhsmotles2gaq.arweave.net/V5lB8jqgPXBFPhdzCar28XKY1ynNPEdOWDyY6ayS0YE) | Thursday, January 25, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md#transcript) |[Link](https://uh4qrdp5wsvzihnnh7m7conzwkllrei4xawnfsohgjmp5qpjberq.arweave.net/ofkIjf20q5QdrT_Z8Tm5spa4kRy4LNLJxzJY_sHpCSM) | Thursday, March 7th, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md#transcript) |[Link](https://aqjulyegruxs4xdwltfkkxqieagkmqc7dcbewovdw2wk7tj72hka.arweave.net/BBNF4IaNLy5cdlzKpV4IIAymQF8Ygks6o7asr80_0dQ) -| Thursday, March 28, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md#transcript)|[Link]( +| Thursday, March 28, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md#transcript)|[Link](https://4wprt5kys3oxjr7ihtu2jgx6mshwts7gzsiv2pfr4qypgrp2xywa.arweave.net/5Z8Z9ViW3XTH6DzppJr-ZI9py-bMkV08seQw80X6viw) | Thursday, May 02, 2024 11:00 AM PT (Pacific Time) | Coming Soon |Coming Soon |[Link](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) | Thursday, June 06, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | | From 75d5e93c5298755f3479bab390e7145dccfa8bb3 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 11:39:39 +0000 Subject: [PATCH 060/138] Create meeting notes for sig-support #33 (#588) * Create meeting notes for sig-support #33 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 033-2024-05-15.md add meeting recording link Signed-off-by: Drinkwater * Update 033-2024-05-15.md Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-support/meetings/033-2024-05-15.md | 380 +++++++++++++++++++++++++ 1 file changed, 380 insertions(+) create mode 100644 sig-support/meetings/033-2024-05-15.md diff --git a/sig-support/meetings/033-2024-05-15.md b/sig-support/meetings/033-2024-05-15.md new file mode 100644 index 00000000..f68c4355 --- /dev/null +++ b/sig-support/meetings/033-2024-05-15.md @@ -0,0 +1,380 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #33 + +## Agenda +- Participants will look at issues in [Akash Support Repo](https://github.com/akash-network/support/issues). +- Scott Carruthers will lead triaging issues, and discussion of implementation for issue fixes. +- Scott will discuss Support from the community and ask for any community feedback. +- Participants can have an open discussion of any other issues or support related items on Akash Network. +- Mainnet 11 Upgrade Follow-up + +## Meeting Details +- Date: Wednesday, March 20th, 2024 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://qc3gxtikakjsqoqohkver467q5u675nuwy7ovtc6j4ajicy7vwna.arweave.net/gLZrzQoCkyg6DjqqSPPfh2nv9bS2PurMXk8AlAsfrZo) +- [Transcript](#transcript) + +## Participants +- Andrew Hare +- B S +- Luna +- Maxime Beauchamp +- Rodrigo Rochin +- Scott Carruthers +- Tyler Wright + +## Meeting Notes + **Introduction and Updates** + - Tyler Wright opened the meeting, highlighting the focus on engineering issues within the support repo. + - The meeting commenced with triaging issues awaiting triage. + - Max and his team maintain communication on issues and fixes via the specific repo and Discord's Cloudmos channel. + - Tyler invited input from Insiders and Vanguards on any relevant discussions or issues noticed in Discord or other channels. + - Suggestions for documentation improvements and specific issues needing escalation were encouraged. + - Tyler acknowledged the seamless Mainnet 11 upgrade and thanked all validators for their contributions. + - Mentioned backend issues related to clients and the ongoing improvement plan. + - Emphasized operations improvements for future upgrades. + - Tyler noted recent announcements regarding provider versions. + - Andrew was recognized for resolving a significant support ticket. +#### Triaging and Open Discussion: +- Scott Carruthers shared his screen to go over issues awaiting triage. +- Discussion on the focus of the current period on upgrading to the new Cosmos SDK. +- Identified key takeaways from the Mainnet 11 upgrade, noting that the Akash network is now in a different phase. +- Scott addressed various issues, including those related to Akash API changes and authorized spend grants. +- Emphasized the importance of keeping clients using the Akash API informed about changes. +- Discussed specific issues, assigning priorities (P1, P2) and responsibilities for testing and resolution. + +#### Akash API and SDK Updates: +- Luna raised concerns about visibility and communication of releases and compatibility for the Akash API and SDK. +- Suggested the creation of an announcements channel for SDK release versions to help users keep track of updates. +- Scott agreed on the importance of clear communication and regular updates, particularly for developers using the SDK. + + **Cloudmos Console Updates:** + - Max provided updates on the Cloudmos console product team. + - Max's team maintains communication on issues and fixes via the specific repo and Discord's Cloudmos channel. + +**Insights from Insiders and Vanguards:** + - Tyler invited input from Insiders and Vanguards on any relevant discussions or issues noticed in Discord or other channels. + - Discussion on recent provider upgrades and the ongoing Mainnet 11 upgrade. + - Hackathon support request for Insiders and Vanguards. + - Rodrigo mentioned increased activity from scammers on Discord. + - BS inquired about the development team on Juno, with Tyler providing information on DAO DAO's involvement and open discussions on GitHub. + + **Conclusion:** + - Tyler encouraged continued support from Insiders and Vanguards, especially during the ongoing hackathon. + - Appreciation expressed for Andrew's contributions and encouragement for staying involved in support activities. + +**Actions Items:** +- Group to follow up on new roadmap and backlog items. +- Max to continue updating and communicating Cloudmos console issues. +- Insiders and Vanguards to provide feedback on Discord observations. +- Group to implement an announcements channel for SDK release versions. +- Continue support for the ongoing hackathon, especially from Insiders and Vanguards. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to seek support to biweekly. I believe this is number 30 or 31 this support biweekly has been going on since open framework has started. This is a biweekly meeting where the core team and members of the community go over any issues and the support repo inside the accost Network organization that are waiting triage if there's anybody specifically from the community that is brought any issues forward and wants to discuss an issue. This is the biweekly meeting to join where you can meet with members of the core team discuss the issues and again, they can be prioritized and look to be solved. + +Tyler Wright: I know Scott who's been leading us through really the last couple especially in my absence will be leading us today. after we go through the issues awaiting triage usually be looked to members of the community to share any feedback that they've gotten and Discord Telegram and other channels. I know usually we have a number of insiders that join us, but there are a few conferences that insiders members of the core team Etc at so I was expecting a lighter week than usual. With that said the six support meetings transcripts notes and recordings should be up to date out of the last couple of Sig meetings. I know that again Scott lettuce through triaging any issues. He talked about the mainnet pen upgrade which happened last. + +Tyler Wright: Wednesday, March 13th. So week from today last week around this time. There was a plans Network upgrade that took less than five minutes and required again. Now, they upgrade their nodes and then providers have to upgrade their RPC notes. So again, thank you to all about data set participated and all the providers and have since upgraded their nodes and obviously thank you to members of core team here that help with documentation testing Etc. + +Tyler Wright: In addition to the main Net10 upgrade there was a parameter change that what didn't require Network upgrade but did go on chain for boat that's lowered the big deposit amounts for both the tenant side and the provider side believe it changes from five akt to 0.5. Akt. So again that went into effect. I believe March 11th or 12th and has been tested and seems to be Working properly end of the documentation has since been updated. So let's just say recap of some of the things that have been happening over the past a couple of weeks since the last six support meeting and even a little bit prior to that. But without further Ado, I'll hand it over to Scott to triage any issues of waiting triage on just be taking some notes in the background. but Scott's feel free to + +Scott Carruthers: All right. Thanks Tyler. Let me share my screen. + +Scott Carruthers: Okay, is everyone able to see my screen? + +Scott Carruthers: thumbs up it sounds good. So I will. Go into the lakash network support repo and take a look at the open issues. I looked at this a little bit before our call and it does look like there's a couple that don't have assignment or prioritization so we can go through those. first one that we come across that has been created since our last six Port is a review of our provider auditing requirements and Andy has already assigned himself to that. So I'll just progress down to the first unassigned issue. So this was open by Andy so Andy may have a comment and yell rely on you for a little bit of review, but this is + +Scott Carruthers: An issue where we are seeing some amount of memory issues. in certain queries on archival nodes. I Andy would you like to give some more thoughts on this? + +00:05:00 + +Scott Carruthers: Okay. + +Scott Carruthers: Yeah. + +Andrey Arapov: you can see there in the screenshot 140 gig of memory or 157 gig so it means you just needs more memory for its operations,… + +Scott Carruthers: Yeah, I'm just gonna Put a note in that we're leaving this open despite the fact that it… + +Andrey Arapov: but for one hand,… + +Scott Carruthers: carried by increase Ram allocation + +Andrey Arapov: I will think to maybe close it but another hand I'm thinking to leave it for Arthur to take a look and decide if that's expected because if it's not expected then it probably needs to be addressed. I mean the fact that it uses that whole amount of memory for this queries because maybe it's not supposed to use that much of memory And just maybe tie garter just to take a look and decide if he's okay to close it as it is, I would like him just like to go through just understand what happened and decides if it's something that we should really take care. I mean they closer look or not. + +Andrey Arapov: + +Scott Carruthers: Yeah, I tagged him there with that comment share. + +Andrey Arapov: maybe it's growing this time. We don't know so it's definitely not like you wanted to it's the lowest score in terms of priority,… + +Scott Carruthers: And also assign them. + +Andrey Arapov: but that's my five sense. + +Andrey Arapov: Maybe it's worth to change the title of this issue or maybe just leave it because it's not running out of memory anymore since he increased the memory, but it's rather consumes lots of memory, basically. More of a question. + +Scott Carruthers: Yeah. + +Andrey Arapov: Maybe I think it's even belongs more to but you can converse it into a discussion rather than the issue I believe. + +Andrey Arapov: I don't think that there is a possibility to convert it like, the issues into discussion, but I can do it later. + +Scott Carruthers: Okay. + +Andrey Arapov: Yeah, I think it was just a great probably discussion and based on this issues and just leave it in under discussion and close this issue. + +Scott Carruthers: you want me to quote you want me to close the issue and you can just create just Okay. + +Andrey Arapov: No, no just leave it so that I don't forget it. and then I'll create a discussion and refer to this issue because it's not an issue. + +Scott Carruthers: okay, I'll sign you on this as well just for Is a visible there? Okay. Sure. + +Andrey Arapov: Yeah things. + +Scott Carruthers: Okay, so I was actually reviewing this issue earlier today. So this was opened by a Community member. I am going to go back to people that are currently on call. I don't believe that this person is currently on the call. but I okay. + +Maxime Beauchamp: It's narrow. + +Maxime Beauchamp: the new team member + +Scott Carruthers: Okay. + +Scott Carruthers: So yeah, so I just was briefly coming through this before. Her call as you can see There's no reliable Per test and local developments and so I thought I don't know if any so max. Maybe you have some context for this but he's staying in those currently no reliable blockchain for tests and local development for instance tests local environments prior to either download and important DB or uses unreliable sandbox, so I guess there's two then I could write this in the comments and possibly get some further feedback, but the two obvious thoughts that come to mind is so we have the ability to spin up local development environments, which is well documented within our engineering documentation, and I'm also + +Scott Carruthers: Not entirely clear on the comment of unreliable sandbox. So I don't know if anyone else might have some further thoughts on the kind of the Genesis for this. + +Maxime Beauchamp: Yeah, so what he's talking about is to run Cloud those locally. and this is sort of like the indexer and we + +00:10:00 + +Maxime Beauchamp: apparently run the indexer since Genesis and there's a few reasons why we need to have the whole. Database locally as well for the API to run properly or the indexer to run property. So it's a bit tricky for new developers to start working on that locally on Carlos. So yeah, that was the issues that we had with yarrow as a new team members start working on combos. And we discussed it a few times I can see that this issue is created last week. and I think it's a bit dated as we + +Maxime Beauchamp: We were taking it new Solutions. there's another issue I think for tracking this on cloud will austerity so I'm not sure… + +Scott Carruthers: Okay. + +Maxime Beauchamp: if that issues needs to be there. + +Maxime Beauchamp: entirely + +Scott Carruthers: How about would this be a good Next Step Max? I could assign you to this issue and then you could do a review of the issues that's opened in. The cloud must repository and then determine if it's appropriate to close this issues. + +Maxime Beauchamp: Yeah. + +Scott Carruthers: Okay. + +Scott Carruthers: All Yeah Max obviously as a progresses if you need our support. On this in any way, I'm sorry. I have a better understanding of the issue and based on the indexer. It's if not necessary to work with the full may not database. So yeah, obviously as you review that other issue or if you need a support on this, just let us know. + +Scott Carruthers: so I believe that leaves us with two remaining unassigned issues. So the next one is provider should release resources immediately after. Not accepted or the deployment was closed. So I'm rather familiar with this issues. Andy you open this so you may have some thoughts as well. I'll probably assign this to Archer for initial triage and he can triage it further from there, but I know that I was looking at this I think. you and I were looking at this on the same provider and seeing that in my experience the inventory operator when a bid was closed. There was a lag possibly. And this is a very rough approximation but in my testing maybe a lag of two to five minutes between + +Scott Carruthers: when the bid is closed and when those resources are made available again via the inventory operator, so I believe that's generally the issues that were talking about any for their thoughts or clarifications any + +Andrey Arapov: yeah, sometimes it was taking even up to 35 minutes depending on which provider and which condition so it's kind of + +Andrey Arapov: It's not too deterministic to really reproduce in terms of time. But yeah, so, whenever there are all the requests in the network and providers are bidding on them. And even if they did not need lost a bit those resources on some providers in some cases not all they are getting locked up for longer than they should because normally if rather didn't beat on it or if it did but it lost that beat supposed to immediately release this resources. I'll never it's okay to log them up well with this open because it can accept it. But if it wasn't accepted and supposed to release and that can create problem and provider will be just getting running out of resources in case if somebody will be generating lots of requests every 15 minutes and sort of attack sort of + +00:15:00 + +Andrey Arapov: And yeah, I think it's important to look at this closer and I think it started happening since the upgrade to the provider From 0.0.4. So yeah, but at least it doesn't happen across all the providers and only specific cases. + +Scott Carruthers: yeah, so in my experimentation with this, so I was closely looking at the status of the bid on chain and if they was created via another provider or just the bid was closed from the loy. So the deployment was closed. I witnessed that they've close immediately on chain in the inventory operator would take about three to five minutes to recognize and release those resources. I was never able to reproduce the Scenario of the 30 to 45 minutes and I was even testing it on the provider that reported it. So we were somewhat of the belief that there was something else in play. So Andy, have you actually observed or you able to replicate a 30 to 45 minute? Failure to release the resources because I've never seen anything. That extreme I know. + +Andrey Arapov: Yeah, the day that I've tried it I reproduced it and that's what the sticker describes and can you try to scroll down? Maybe there was some update. Maybe to the bottom of it. + +Andrey Arapov: And slightly up if it speaks something about this time delays or something. + +Scott Carruthers: So this says after six minutes, it's still locked. And I did. + +Andrey Arapov: Yeah, so yeah, it was just additional test that I checked if there is something about this five, I mean the mid timeout which is the old value so it was locked for longer than six minutes and then I just didn't want to wait longer. I just realize that probably it will be there for longer time because I run several tests on this problem one of this providers and this one particularly. And yeah, I mean, of course I can run more tests to see if I can still reproduce it. But I believe it's still there and don't think it will be just gone by itself. + +Scott Carruthers: No, I don't think it would be gone by itself either and I think it's very easy to reproduce. So there's a several minute delay. So I was just curious that if we were able to reproduce that extreme delay of 30 to 45 minutes, but here you have an example of six minutes, which is obviously abnormally a long time. So, that's fine. + +Andrey Arapov: Yeah, in the beginning in the top of the ticket. I think I wrote there is Christian to 25 minutes as well. Yeah, yeah,… + +Scott Carruthers: Yeah, okay. + +Andrey Arapov: because I didn't just put the numbers randomly. So it's essentially run some tests on my own. + +Scott Carruthers: Yeah, I'm just saying that the most I could reproduce was three to five minutes but it looks like you were able to reproduce something much greater. So okay, it's fine. + +Andrey Arapov: Yeah. + +Scott Carruthers: the thoughts are comments on this issue. + +Andrey Arapov: not really but I think maybe it's related to the inventory operator the way how it pulled the data because normally what I know, it pulls every 15 minutes and there are some issues if you look at the next ticket 192 why the reports successfully High multiplic in order to operate his hair, yeah this one. so I think it's kind of connected slightly upper one into + +Andrey Arapov: and I will + +Andrey Arapov: about online to have + +Andrey Arapov: So you can open it up. + +Scott Carruthers: yeah, yes so this is actually an issues that this provider ping me yesterday as well. + +Andrey Arapov: So I think + +Scott Carruthers: So yeah, he goes through a period of time where so the provider I'm talking about is + +Scott Carruthers: deathless This is just and… + +Andrey Arapov: yeah. + +Scott Carruthers: then yeah, he's showing so I've seen this issue where we have abnormally and I know that Max has seen this issue before as well. We get abnormally large GPU alcatable. statistics I have never seen this with anything outside of gpus but yeah deathless is definitely currently experiencing this with a Ram allocatable + +00:20:00 + +Andrey Arapov: Yeah what I think is that when we upgraded the internet operator on the provider to all point, five four, I mean, so when we jumped from 0.4, I think even before in this older version of Provider, sometimes when the media device plug-in is getting stopped or restart or just being in the beginning of the insertation. It has in impacts on the amount of the GPU provider sees and when you restarted or when you wait a little bit and then it kind of picks itself, at least it was back then with 0.4 but with 0.5 when you were one + +Andrey Arapov: Because there is entirely changed the way how we winterize things from understood. I think it doesn't self recover. So it needs to be manually restarted as soon as you see this high of excessive amount of Resources and the last command one before the last one. I've just updated five hours ago. Yeah, because I was reporting on the North quite often recently. I was testing these growth AI seeing you so I had to was looking up the GPU in some conditions and I need to restart an old quite often and after it was about it up and I've noticed that issues was always coming back again. So I needed to restart the interior operator. Sometimes it was even reporting zeros. + +Andrey Arapov: So kind of interesting stuff, but they definitely needs to be getting the soft recovered from this issues. + +Scott Carruthers: I was just reading through your comments from five hours ago as well. So yeah, I've Actually reclassified this as a p zero, I think this needs some urgent attention. and it's already assigned to Archer. So + +Andrey Arapov: I think so. But another hand I was thinking when it doesn't show that amount of available resources is unusable like zero or something. So it shows that you have way too many resources one hand and why I'm saying it maybe not be zero, but maybe if you want because providers are able to offer the resources, they just able to offer to much of the resource. So then they have so well another hand. Yeah. It's probably zero. + +Scott Carruthers: yeah, so deathless actually reported yesterday that for some reason when he's getting a high memory El capable stats. so this is a strange issue. understand exactly where the correlation in this is but deathless yesterday was reporting that so he only had a certain node that was reporting incredibly High memory allocate allocatable statistics and whenever was in play and whenever that issue is current he was unable to rent out GPU or he wasn't deployers were not getting bids from his provider if + +Scott Carruthers: The sdl and so again this is kind of strange because you want to think there's any correlation here, but he was reporting and was able to reproduce it. When those memory lkdable stats are very high. If a sdl is requesting a GPU and it has a wild card for the model his provider won't bid if you specify RTX 30 90 or whatever. He has a specific model it will bid. But if he's using a wild card for the GPU, it doesn't bid during so I guess that's still debatable if it's a P0 or P1, but it definitely is having other ramifications. I think it's something that we need pretty urgent attention on. + +Andrey Arapov: The other Handler I think it should really be zero and also hurricane provider. I noticed today. also the comment to the second last one, but European provider is experiencing this issues now persistently,… + +Scott Carruthers: Yeah. + +Andrey Arapov: even if I restart the inventory operator, it's still keeps reporting with the worker now,… + +Scott Carruthers: Yes. All right. + +Andrey Arapov: so it's persistent issues. definitely + +Scott Carruthers: I would actually say this may be one of the most severe issues going on in the network right now. + +Andrey Arapov: no. + +Scott Carruthers: So yeah, we'll definitely try to get some urgent attention on up. + +Andrey Arapov: Okay. Thanks. + +Scott Carruthers: and then + +00:25:00 + +Scott Carruthers: Yeah, no, probably. Yeah,'s Zeke can death was just joined. So yeah, we were just going through the discussion of Resource the inventory operator is given abnormally allocatable amounts at where we are previously just seen on gpus but now we're starting to see it on memory as well. So the case is the issues fully up to date and I requested it from a P1 to a P0 because we understand this is probably the most urgent issue that we have on the network right now. So requested to a P0 to try to get some attention. + +Scott Carruthers: Okay, and then that leaves are very last unassigned issue. Andy do you want to so this was open some two weeks ago do you want to is this + +Scott Carruthers: so the provider stops responding to the status endpoint are you saying that they provide ourselves responding both to the rest API 8443 status endpoint and the grpc part of a44 simultaneously here + +Andrey Arapov: Yeah, it's the most important honestly and it's when the paper writer was enabled. Actually, I have not tested it back again because there are some other issues on the hurricane provider such as the abnormal reports of the resources, And whatever there no restarts. No issues. Okay. I am that's my last command that I said that I want to enable the appealing back again to see if I can still reproduce it, but I haven't got back time to do that issue because those focusing on the other issues and that other issues also. Boiled up with the abnormal report of the resources of thinking maybe that's one of the reasons for that for this issue. I will need to get back to it. + +Scott Carruthers: Okay. + +Andrey Arapov: But I think it's not. + +Andrey Arapov: Be zero of no nor P1 because I didn't have anyone reporting this issue. + +Scott Carruthers: Yeah, I have it as P2 and I'll just put in the comment that waiting for their testing by yourself. + +Zeke E: And I saw someone on Discord this morning put in. + +Andrey Arapov: Yeah. + +Zeke E: A basically saying that it happened to them. It's in the providers Channel. + +Zeke E: + +Scott Carruthers: So just for clarity what exactly did they experience? + +Zeke E: There so they said that Port 8443 isn't reachable. But April 4 is 844 is so + +Scott Carruthers: Okay. + +Andrey Arapov: That must be another thing. It must be that they need to update the engine X Ingress operator config to allow the port 844 because this one is the new part that was enabled since we upgraded the providers to version 0.5. So Yeah,… + +Zeke E: Katrina that's probably up. + +Andrey Arapov: so Zeke if you can just bring me the link to this conversation. I will reply to the person. + +Scott Carruthers: Wait, so just for clarity. I thought Zeke were reporting the opposite. So I thought you were saying that a44 they grpc. Is working… + +Zeke E: The grpc is working. Correct. + +Scott Carruthers: but a four for three is not okay. + +Andrey Arapov: There's the opposite. Okay. just let me know. + +Zeke E: Yeah, I'm sending it to. + +Andrey Arapov: Yeah, yeah. I'll take a look. + +Scott Carruthers: so that concludes our review of unassigned issues are there any For the discussions on any of the issues that we talked about or issues that we haven't talked about this morning that anyone would like to review further. + +Scott Carruthers: Okay. + +Zeke E: I might have missed this but is there a timeline for shm enablement over SEL? + +Scott Carruthers: so as you are probably aware Zeke a number of the cash core team are a kubecon today. So yesterday we got the update that Arthur has so basically Adam about an edge was the primary engineer working on this so it's code complete and we're now just waiting they release I've actually already staged to documentation update so that as soon as this is release, we'll have sdl examples and also, Guys who are providers adding necessary attributes to their provider config for shm supports or ready to go and the code is completed. We're now just waiting for the release that will unlock as shm with team members at kubecon. + +00:30:00 + +Scott Carruthers: I'm not sure when that's going to happen and what exactly we're waiting for. But yeah, that's basically the update that I have. Is this Coco complete and we're just waiting for the release to be cut that will support sham. And as I said, once that happens all the documentation and other bits are updated, so I actually was wondering if we might actually see that release this morning. That didn't happen if you want to. Maybe reach out to Arthur when he's available. Maybe you could get a ETA on when we think that release was going to become available. But that's all the information I currently have. + +Zeke E: Okay, sweetie. It's perfect. Now we can actually Deploy srock on the cost. + +Scott Carruthers: yeah, without the provider having to go in and yeah. + +Zeke E: And manually a bit. Yes. + +Scott Carruthers: Okay, so yeah great question Zeke for because there may be other people that are wondering that because there's been some chatter about this system native support and like I said is code complete so we should be releasing that good update on that and if there's not anything else that concludes our issues review, so I'll hand it back to you Tyler. + +Tyler Wright: Thank you very much, Scott Andre and others. Again, if anybody has any issues that they see over the next couple of weeks, please feel free to add comments any open issues already or if you see any new issues go through the proper mechanisms to again Ask insiders vanguards another members of the community and then if it gets escalated from there, then it'll be added to the support repo. As Max kind of covered they're also is a cloud most repo where any issues related to Cloud most live. I know the cloud most team does a great job of if anybody has any issues that they see in Discord and ecosystem Cloud most Channel or again elsewhere Cloud must team great issues for those and then continues to update those issues so you can monitor + +Tyler Wright: The Cardinals repo as well as roadmap and the support repo to see all the things that are being worked on. + +Tyler Wright: cool, At next part of the agenda. We usually see if any community members are here to give any updates on. Behaviors or themes I've seen and Discord or other channels related to support real quick. I know that the last couple of insiders meetings. There's been a real effort to improve issues around spam and Discord server. There's been a number of keywords that have been added to a list for the block lists and it seems like there's been some significant less spam. We'll continue to monitor that and talk about that during the support repo as well. As this is something that Akash insiders are actively talking about during The Insider office hours. + +Tyler Wright: But again, if anybody has any issue related to spam feel free to reach out to an Insider or myself and will continue to monitor that very closely. Is there any other issues I see Zeke here who has recently been made a Vanguard. So again, shout out to all that Zeke does Zeke have you seen anything in Discord? I know that you just shared some stuff with Andrey related to Port issues. But is anything else thematically that you've seen over the last couple of weeks and Discord that might be worth sharing with the Core team and the other members of the community. + +Zeke E: I mean right off the bat out in the auto model has been very very helpful. And catching spans. So I really like that. + +Zeke E: In terms of schemes. I think that's kind of just been the main one. I mean, yeah, nothing. I can really think about the top of my head. Other than that. + +Tyler Wright: I know that again deathless and some other members of the community have brought for some issues in provider Channel deployment channel so much appreciate content participation obviously deathless giving a number of people feedback sharing opinions thoughts and helping people with the class. So again much appreciate those efforts if anybody sees any glaring themes or issues related to whether it be use of product any of the tool documentation anything that could use update to make the user experience better for a cost users again, feel free to drop something and big support or feel free to attend another special interest group whether it be docs otherwise, + +00:35:00 + +Tyler Wright: Is there anything that anybody wants to discuss that's support or core code related that hasn't been discussed already? + +Tyler Wright: Real quick just for the consensus of this group. The Sig chain issues. It relates to the main Net 10 is still open. I know that has again passed on vote and then the upgrade is successfully happened last Wednesday. Is it fine if I close that issue? For repo just want to get thumbs down from this group. On closing the sigchainish cool. + +Tyler Wright: I will close that issue. I know there's a number of issues that will be followed upon, specifically 195 related to the memory of our archival node. I know that Max will follow up on issues number 194 and figure out where that should go and then issues 193 and 192 which are quite high priority as well as 190 will be major focuses over the next couple of weeks. So we'll look to follow up with those certainly at the next six support meeting if not sooner. + +Tyler Wright: Is there anything else that anybody wants to discuss before I'll let you all go. ahead Scott + +Scott Carruthers: It's just one thing to mention to this group to help us support the community and just make sure that everyone is aware I believe is over this past weekend. We migrated to the new documentation site. So definitely. if you see any chatter in the community, like any missing documentation or any formatting issues or anything of that nature and just so that you're aware in general if you go to akash dot Network, which is right now redirects to network with the path of Docs. So you can visit either of those paths or it's all also the documentation site that is linked off of the network home site. + +Scott Carruthers: So yeah, just make sure the entire group is aware so it should be very clean. they developers of the new documentation site did a diff on the old documentation site. and so hopefully there should be complete parody and there's not any documentation missing so this group is aware. We went through that migration and please let us know if you see any anomalies or any missing information + +Tyler Wright: Yes, great call out If you all see any missing information or anomalies or formatting issues, please drop a message and Sig docs with the specific documentation linked that would be extremely helpful and again will continue to push to have that as clean as possible. But do want to shout out the efforts of Scott and Andre who were very Hands-On and making sure that the documentation matched up as much as possible. I know that push and his team, we're very busy and we're trying their best but much appreciate Scott and Andre's oversight on making sure that documentation is clean and ready to be used by the community because I know a lot of time effort and work put into. + +Tyler Wright: Both like updating the developer documentation. Also the engineering documentation that's been added more recently. So again, thank you very much for bringing that up Scott and all the efforts here. + +Tyler Wright: if there's nothing else then again much appreciated everyone's time and efforts today during this call again. Feel free to drop any comments inside any specific issues. Please stay involved in Discord. And if you see anything worth calling out, please call it on the six support Channel Sig docs or any other respective channel that makes sense and again much appreciate everyone's time and energy today. me, + +00:40:00 + +Tyler Wright: he does not have to speak but I will call out that again the overclock Labs core team. Obviously Max and Andre is a part of that have also added another senior software engineer and Andrew who is on this call and will continue to join these calls in the future. He's working on a number of things behind the scenes and getting his feet wet. But he's a very very cease and go developer that again has gone for the rigorous process of bedding amongst the team and he's been enjoyed to work with the thus far so I'm sure many folks here and listening in we'll get to know him more as time goes on but just want to shout out does not have to say anything at this time. + +Tyler Wright: I hope everyone has a great rest of their day. Thank you very much. For participation today. There's a number of sigs again a couple of sigs got moved from this week to next week because of all the travel, but please add to your calendar Sig clients and Sig providers. I'm sure we'll do some talking about provider auditing some other stuff related to Future Discovery, and I know a couple of client related things. So again Market calendars for next week, because it'll be a basic week next week, but much appreciate everyone's time and energy today. Hope everyone has a great rest of your day. Thank you very much. + +Scott Carruthers: it's + +Andrey Arapov: Thank you. + +Meeting ended after 00:41:46 👋 + + From 7d1cbc290c234e31a4478340100a232389767d7d Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 20:14:33 +0000 Subject: [PATCH 061/138] Create meeting notes for Sig-Design #15 (#566) * Create meeting notes for Sig-Design #15 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 015-2024-03-13.md add transcript for meeting 2024-03-13 chore: add recording Signed-off-by: Drinkwater * Update 015-2024-03-13.md add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-design/meetings/015-2024-03-13.md | 141 ++++++++++++++++++++++++++ 1 file changed, 141 insertions(+) create mode 100644 sig-design/meetings/015-2024-03-13.md diff --git a/sig-design/meetings/015-2024-03-13.md b/sig-design/meetings/015-2024-03-13.md new file mode 100644 index 00000000..2805e766 --- /dev/null +++ b/sig-design/meetings/015-2024-03-13.md @@ -0,0 +1,141 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #15 + +## Agenda +- Welcome and Introduction +- Open discussion on design-related topics +- Review of Recent Events +- Discussion on Brand Assets and Guidelines +- Website Update + +## Meeting details +- Date: Wednesday, March 13, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://nnq3ufkztaw2lqjhzhftmlaxw3rt7c3x6hotvsz7gjm2pf7jbgtq.arweave.net/a2G6FVmYLaXBJ8nLNiwXtuM_i3fx3TrLPzJZp5fpCac) +- [Transcript](#transcript) + +## Participants +- Denis Lelic +- Tyler Wright +- Zach Horn + + +## Meeting Notes +### Denis Lelic: +- Denis acknowledges the participation of Tyler and Zach and provides an overview of the meeting's purpose and frequency. +- Recent events from Q1 (EthDenver, KubeCon, GTC) were successfully conducted with swag and merchandise. More events are scheduled, necessitating an increase in design-related tasks. +- Tasks include designing stickers, t-shirts, hoodies, videos, and booth designs for upcoming events. +- Denis mentions ongoing work on the Akash.Network website, acknowledging the need for improvement and planning to review GitHub for updates. +- Denis discusses ongoing website improvements, highlighting the creation of issues on the Akash revamp repository for contributors. +- Encourages interested parties to explore easy tasks in the issue section for contribution opportunities. +- Emphasizes the continuous effort to enhance the website experience and related features. +- Mentions plans for revamping statistics display with more detailed graphs and dynamic elements. +- Announces the addition of GPU pricing, addressing a missing feature on the current website. +- Explains that GPU pricing will be included in the pricing section, allowing users to calculate. + +### Discussion on video contributions + - Tom, a community member, is willing to contribute video content. + - Emphasis on starting with a CLI video, aiming to establish a benchmark for future contributions. + - Zach highlights the iterative process for the first video, focusing on structure, recording methods, pacing, and more. + - Denis plans to assist Tom and mentions challenges with finding a suitable screen recorder for HD resolution. + - Zach recommends OBS (Open Broadcaster Software), an open-source and free screen recorder. + - Tyler emphasizes the importance of brand guidelines and assets, highlighting the availability of Dennis Zach and others for assistance. + - Tyler invited to share any additional thoughts or updates. +### Closing Remarks +- Tyler acknowledges the comprehensive coverage of topics by Denis and expresses satisfaction with the progress. +- Highlights the positive reception of Akash swag at EthDenver, with attendees expressing excitement and appreciation for the designs. +- Commends SIG Design for delivering assets and deliverables for ETHDenver and mentions readiness for upcoming events. +- Denis mentions ongoing discussions and brainstorming for future initiatives, promising to share tangible updates in the next meeting. +- Shares swag designs in the SIG Design Discord channel for community members interested in printing their own merchandise. +- Tyler notes a steady increase in people accessing the Akash swag shop, indicating a positive trend. +- Denis mentions a recent contribution from Andrea, designing a flyer for KubeCon, showcasing community initiatives in utilizing Akash branding assets. +- Denis concludes the meeting, expressing gratitude to participants and noting ongoing work in the background. + +## Action Items +- Denis to contact Tom to offer assistance with video production. +- Denis to explore OBS for screen recording. +- Continuation of ongoing efforts with video contributions and website improvements. +- Group to prrepare design materials for upcoming events. +- Denis to share tangible updates on ongoing initiatives in the next meeting. +- Adam to coordinate printing and delivery of the flyer designed by Andrea for KubeCon. +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: Of brand guidelines and brand assets. I know that Dennis Zach and others make themselves very available and a great representation of the Sig design to help. + +Tyler Wright: Make sure that all brand assets are of the highest quality. + +Denis Lelic: Hey everybody. Welcome to today's sick design meeting. Thanks Thai and Zach for participating today for joining this meeting. So for all of those who might have a look at the recording these meetings happen on a monthly basis. So I believe every first Wednesday of the month, so I'll just start off with a couple of things we've managed to do in the last couple of weeks or months, so we got first events from + +Denis Lelic: Q1 under our belts so East Denver kubecon and GTC with a lot of swag stuff a lot of merchandise Booth designs for those events and they're like a couple of them happening and actually two of them are happening next week. And there's more in the pipeline a lot of events happening this year which means we are going to have to do. A lot more everything event related from design perspective. So stickers t-shirts hoodies both videos and so on. + +Denis Lelic: Other than that, there's a bunch of + +Denis Lelic: cash dot Network our website a lot of work to do on that. part, so I'm just second just opening the GitHub. + +Denis Lelic: Okay, great. + +Denis Lelic: Ness so as we talked in the website meetings, there's a lot of stuff going on as well on the website. I've created Tyler created and Zach Tom as well created a bunch of issues here And the issue section on the website. Dash revamp Repos so anyone who's interesting contributing. Please have a look at the easy tasks here. + +Denis Lelic: and there's a lot more happening and in the pipeline, so we're constantly will try to improve the experience of the website and everything around the website, which means another thing which is in the pipeline is the stats revamped or we're planning to do a lot of more detailed + +Denis Lelic: displaying of stats like different graphs adding new stuff. Just providing a little bit of more of dynamic there. There's another new thing happening, which is the GPU pricing. Something that's been missing on the current website and it's also missing in the section. + +Denis Lelic: Under a batakash and pricing at the moment. We just have pricing coming soon for the gpus and when a user applies to calculate their pricing on a cash network based on their preferences and resources. They want to lease. They just get an estimate based on the CPU memory and storage so gpus coming soon. + +Denis Lelic: on another point we always talk about but I hope we're going to move. soon is the videos. We just talked about it briefly. We got one Community member Tom is his name. + +Denis Lelic: He's willing to do some of the video content contributions and their commutation contribution. So we just have to get started for the first one and we could take it from there. + +Denis Lelic: just hopefully iterate that version until it's something that everyone satisfied with and it's going to create some sort of a benchmark for all the future video contributions and Yeah. + +00:05:00 + +Denis Lelic: and that's + +Zach Horn: So for the video contributions, the one that Tom is working on currently I believe is going to be a CLI video that he's working on with Huey directly. I think for this first one as he said that we're going to try to just get it to a point where It's something that we can use as a reference point for all videos going forward. So, this first one's gonna be very iterative as we dial in all the different pieces. We wanted to have how it's structured how it's recorded pacing, screen recordings using 11 Labs all these different points. As soon as we get this first one done that we have a benchmark one that we can both have Tom continue to do more videos. But also if anybody else wants to participate they'll have a way to do that and I'm sure to ties point from earlier do some light weight Internal Documentation on how that's created and guides for making videos. So the goal in my mind is get a first video done. + +Zach Horn: To a point that everybody is aligned with and then we can go from there and grow our video contributions significantly because we do need videos. It's definitely a top of Mind thing. + +Denis Lelic: Yeah, I think I'll just Tom and see if I can help him in any way. I know when I tried doing some of these videos there was a challenge of finding a good screen recorder. There are great + +Denis Lelic: Apps which you have to download but of course any other product which is good you have to pay for it. but just to have HD Resolution going on and just to avoid anything pixily and stuff like that. But yeah,… + +Zach Horn: I've heard really good things about OBS open broadcaster software. + +Denis Lelic: go ahead. + +Zach Horn: It's open source. It's free to my knowledge. Lots of people use it. Yeah, it's just free and open source. That maybe what time is using already? I'm not sure but yeah, just something I've heard from lots of contributors. + +Denis Lelic: Cool, I wrote it down. I'm gonna try it. + +Denis Lelic: Okay tie you I do have maybe anything you would like to add we could keep this meeting quite short. We pretty much covered everything that's going on some stuff that's been done some stuff. That's still in the pipeline to be dealt with but you have anything on your side. Feel free. speak + +Tyler Wright: No, I think you did a great job of covering it. The only thing that I want to shout out is I know at eat Denver. there was a number of folks that were very excited about the Akash swag, the beanies, I have people still reaching out to me and Discord saying they're gonna wear it every day and people really like the number of the graphics and everything kind of turned out. so just from a events 2024 standpoint, Sig design delivered on all the assets and all the deliverables in terms of Swag for eat them for and I know that everything's on his way for the next couple of events so much appreciate the efforts of this sig there and we'll just continue to work on everything related to the website and elsewhere as well. + +Denis Lelic: Yeah, there's a lot of stuff still going on in the background background. Some of this is still kind of being discussed and brainstorm and as soon as it's Something tangible. I'll share it probably in the next meeting. + +00:10:00 + +Denis Lelic: Yeah, actually asks for some of the swag designs in the sick design Discord channel, so I just shared some of the + +Denis Lelic: We already talked about during Sikh design meetings and the last year I believe. So yeah, he's just trying to print some And produce some of that stuff on his own. But yeah, I'm happy to support anyone who has any design needs. My DMs are open. + +Tyler Wright: Yeah, there's also been a steady uptick of folks that are accessing the Akash swag shop and buying things. trending the right direction as well there. + +Denis Lelic: Yeah, that's good to know. we had a contribution last week Andrea. she is part of Luna's team the cross search. So she designed a flyer for? kubecon so that's something she coordinated with Adam and I think Adam's going to take care of that print that thing and delivered to kubecon. So yeah good to see some Community initiatives going on and people like playing around with Akash branding assets and producing stuff which is cool. + +Denis Lelic: Okay, cool, so We can make it short for today there's a lot of stuff. Of course. We are doing in the background. + +Denis Lelic: But thanks again as I can type for joining and we'll see each other soon. + +Zach Horn: Sounds good. Thanks guys. + +Denis Lelic: Have a good day, bye-bye. + +Tyler Wright: It's above. + +Zach Horn: Thank you. + +Meeting ended after 00:12:32 👋 + From 9d34bfba11bac77b7f24f6235b94a4b383708be4 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 20:16:05 +0000 Subject: [PATCH 062/138] Create meeting notes for Sig-Design #16 (#587) * Create meeting notes for Sig-Design #16 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 016-2024-05-08.md add transcript Signed-off-by: Drinkwater * Update 016-2024-05-08.md add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-design/meetings/016-2024-05-08.md | 404 ++++++++++++++++++++++++++ 1 file changed, 404 insertions(+) create mode 100644 sig-design/meetings/016-2024-05-08.md diff --git a/sig-design/meetings/016-2024-05-08.md b/sig-design/meetings/016-2024-05-08.md new file mode 100644 index 00000000..0d0cb261 --- /dev/null +++ b/sig-design/meetings/016-2024-05-08.md @@ -0,0 +1,404 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #16 + +## Agenda +- Merchandise updates for Accelerate 2024 +- Open floor for contributions and hackathon discussion +- PR and marketing collaboration policies +- Future design and UX/UI improvements + +## Meeting details +- Date: Wednesday, May 08, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://utgdid3tyicjsjmgvznzalfhes33oqqzoytow53oaqvlgg6nbmlq.arweave.net/pMw0D3PCBJklhq5bkCynJLe3Qhl2Jut3bgQqsxvNCxc) +- [Transcript](#transcript) + +## Participants +- Ansh Saxena +- B S +- Denis Lelic +- Fenil Modi +- Poroburu +- Tyler Wright +- Zach Horn + +## Meeting Notes +- **Merchandise Design Review** + - Denis reviewed various merchandise items for Accelerate 2024, including AirPods cases, backpacks, tote bags, notebooks, pins, wearables, socks, business cards, wristbands, gift cards, and stickers. + - Confirmed designs and production quantities. + - Discussed alternatives for an unavailable backpack model. + - Emphasized finalizing quantities and sizes for AirPods cases. + +- **Production and Logistics** + - Most items are in production or ready to be produced. + - Continued vendor communication for quality and timely delivery. + - Emphasized future merchandise reorganization and enhancement. + +- **Future UX/UI Improvements** + - Denis announced upcoming rebranding of the Cloudmos console, including a switch from Material UI to Tailwind CSS. + - Addressing friction points around payment and wallet connections to create a frictionless Web3 experience. + - Plans to integrate private repositories from GitHub and other improvements. + +- **Hackathon and New Contributions** + - Ansh Saxena discussed his project on the Cloudmos console, focusing on tokenizing AI model deployments. + - Sought assistance with running the Cloudmos console locally and expressed interest in ongoing projects. + - Denis and Tyler encouraged Ansh to connect with them and other team members on Discord for support and collaboration. + +- **Community and Support** + - Denis recommended Ansh connect with Piyush (bold Panther on Discord) for assistance with integrating private containers from Docker and other technical challenges. + - Highlighted the community's ongoing efforts to improve the Akash website and backend. + +- **PR and Marketing Collaboration Policy** + - Tyler clarified Akash's stance on PR and communications partnerships, emphasizing that Akash does not engage in empty PR announcements. + - Partnerships must involve demonstrated integration and proof of concept before any co-marketing efforts. + - Zach reiterated this policy, stating that marketing collaborations should reflect real, tested integrations that drive demand on the network. + +- **Akash Accelerate 2024** + - Denis provided details about the upcoming Akash Accelerate event, emphasizing the importance of contributions and collaboration. + - Ansh expressed interest in participating in the program post-hackathon. +**Conclusion:** +- The meeting concluded with positive feedback on the current merchandise designs. +- Encouragement for continuous collaboration and participation in upcoming meetings and events. + +**Action Items** + +- **Denis:** Confirm AirPods case quantities and sizes, find a replacement for the unavailable backpack, and ensure all merchandise items are produced on time. +- **Zach:** Continue looking for contributors and coordinate with interested parties. +- **Ansh:** Connect with Tyler and Piyush (bold Panther) on Discord for further assistance with his hackathon project and discuss the marketplace idea with Max. +- **Tyler:** Assist Ansh with any technical difficulties and ensure he is well-integrated into the community. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Denis Lelic: Hey everybody and welcome to today's syndesign meeting today and not so much crowded. Me and Zach here only. So We're gonna look back on the stuff. We did in the previous month. A lot of work was done around Accelerate 2024. It's happening in Austin, Texas. So I believe it's on 28th 29th. + +Denis Lelic: So I'm just gonna get us started. With merge design, so just to have a look. What was done on that front? So we had plenty of options to choose from. + +Denis Lelic: so I'm just going to present a trimmed down version where we taught it makes sense to produce these items. So starting with airpods case something wrong community members can grab a hold of and speakers attendees and so on could have this item to pack their airpods and Then we had ideas for a backpacks. A cash branded and some other Graphics were involved. Tote bags. And there was different designs for Notebooks like a letter one. then we had + +Denis Lelic: an alternative version and we're actually producing both so the leather one and the Heart cover. + +Denis Lelic: in a bigger size and red, so I think When we asked the core team members, what are their thoughts on these which one should be produced? So we're going with number five here and number nine for red. So there are different designs here then we had pins. We're producing a three pins, I believe it's Greg's head Akash. + +Denis Lelic: Sign so a logo and just like a small Texas state. So it's like a map of Texas and we replaced the star with Akash sign here. + +Denis Lelic: So we got some. wearables merch and so on and so here's an example of vest. Then we have some Akash accelerate branded jerseys from a 14 members. and a different color and have some light packable jacket with the same theme. And a lot of different t-shirts, so I think we're producing all of them. Just not in. Crazy amount of quantity here. Just I think it's 50 each. + +Denis Lelic: So something that's gonna serve different purposes. It could be more. + +Denis Lelic: Corporate depends on the events. So yeah, just to mention some team members are gonna wear these and different events in the future and some of these t-shirts these here are only akashic ce branded, so we're gonna use them in Austin probably but of course, it's + +Denis Lelic: everyone who receives this t-shirt is going to bring it home. So it's going to be some sort of a small reminder as well on the first Akash accelerated event. We got socks. So a lot of these items here are already pushed to production. I believe the socks. I know I talked with + +Denis Lelic: Amanda who's working closely, but Adam wozny on the event side and I think this one is already out in production. Then we talked a lot about business cards. So there's + +Denis Lelic: Options here as I know we mentioned but you need the more designs maybe with a QR code involved on one side and something just the members could just hand out in different events and we can provide a crucial information how to reach someone from Akash or overclock on different platforms like X okay Twitter and so on an email. Then we have a wristband. for the Akash accelerated event We were talking about gift cards. So + +00:05:00 + +Denis Lelic: one thing I know Chang and Huey and some other folks from 14 would like to have is the gift cards where we would offer. I don't know. Let's say 10 bucks or free amount of compute resources. And that's just an idea where still have the kind of evolve and we're exploring different options how to implement this and to make it useful and Right just to make it easy for new users to access these funds and try out probably a cash Council. We have a bunch of stickers. So one of the ideas was. to produce + +Denis Lelic: lots of different designs that are kind of related to different events. So yeah, we have East Denver which is happening in Colorado. We got gosh accelerate which is happening Austin and we have some more mentioning New York here some California and others are more like just + +Denis Lelic: Akash branded like a car supercloud and so on and then we have Three set of three here, which are just carrying A conflict accelerate brand we've kind of established it it was kind of tricky. We still have to communicate a cache, but personally I had a feeling we have to have Something that's going to be memorable and it's kind of brand this event. So this forward sign and AA CC it's kind of hopefully a memorable thing for this event. And then we have this idea where the suitcase or a briefcase. + +Denis Lelic: With all these stickers applied there and we have a one cool GPU unit pack inside. Going on. We have a welcome note from Greg for Just an idea of how we could. + +Denis Lelic: Design different dashboards for this event. So that's one of them. We can have also our cards or stuff like that and napkins archive branded crash accelerate branded. + +Denis Lelic: cups so for drinks and so on with Akash accelerate branding there. + +Denis Lelic: then the next thing would be the Branded venue where the cash accelerate theme so we explored different. things here like + +Denis Lelic: branding the venue, so just putting a big sign up there. on different animations for screens so it could be a cash branded or Akash accelerated branded. back walls different banners like horizontal vertical hanging standing a cache brand of Akash accelerate branded so it's like a mix. of all of them + +Denis Lelic: which is going to go through them all. quickly Yeah, Roll-Ups as well. So that's one thing we were cooking in the last month or so. So a lot of these items are already out and production. Hopefully we'll get them all on time for the event. so that's it on the acoustic fellow rate sign. So sync design is kind of like + +00:10:00 + +Denis Lelic: also covers up one part of the marketing side. So Zach is here as well. So Zach if you want to just share anything there. + +Denis Lelic: Yeah. + +Denis Lelic: And I think for the airport's case, there's a minimum amount is hundred pieces. So it's just a matter of budgeting here yes or no, so, I know Amanda Huey and the rest of the crew are talking about this and unfortunately this backpack is not available. So I've asked Amanda to try to find something that's + +Denis Lelic: at least kind of looks the same and feels the same. So from the quality perspective. I hope it's gonna work. So yeah, otherwise like T-shirts, books this kind of stuff. I believe everything is + +Denis Lelic: as the Polly and who's like taking care of the contacting different vendors and making sure everything is + +Denis Lelic: Produced on time and so I am from my understanding everything is fine all the print files and everything is done. So the only thing was as I said we need to find a replacement for the backpack, so Maybe later today. I'm gonna try to find some. As well and just see what can we receive. In two weeks. Yeah. + +Zach Horn: Yeah makes sense. + +Zach Horn: for the airpods cases What sizes that is Because that was the one thing we're talking about is … + +Denis Lelic: I think it's the Prolia. Yeah. + +Zach Horn: what size do we do if we do airpods cases? I think that's fine. not everyone has Pros, but I think it's okay to have either way. Did we go with multiple sizes or just the pros? + +Denis Lelic: I think it's just a prose just one size,… + +Zach Horn: Okay. + +Denis Lelic: but I can check with Amanda if we could do 50 Pros 50 or the regulars. + +Zach Horn: Yeah, because I have a pair of the regular ones. It's a similar case shape, but I think it's a little bit smaller if we can and it doesn't throw any wrenches in the gears or anything like that. It might be good to do/ you were saying 50 Pros 50 regulars, but pretty small thing. I mean at this point, I think there's higher priority merch things on the table. for the soccer jerseys, which ones did we end up going with it was the stripe ones Nike strike three, I think. + +Denis Lelic: We're doing both here. Yeah. So we have the white and… + +Zach Horn: I see. hang on. + +Denis Lelic: this Coral version. + +Zach Horn: I mean the actual Jersey itself because of the link here is dry fit, but I think we ended up going with a real Jersey. I think it was the strike three. I mean Google that real quick. + +Denis Lelic: I think so. Yeah. Yeah, but from the look, it's kind of pretty much the same just probably there's a difference in materials. yeah, but just from the look, I think we're pretty much there. + +Zach Horn: Gotcha, I think we're well on track there and it sounds like we're gonna have some ongoing merch kind of reorganization and up leveling for lack of a better word. + +Denis Lelic: Yeah. + +Zach Horn: So we can carry some of this stuff through to the other merch designs that we'll have which I'm looking forward to for the official thumbs up from TY + +Denis Lelic: And I don't try looking forward to that. So. + +Denis Lelic: Yeah, that's just something we can. discuss after we've wrap up the whole accelerate stuff and see how items are being produced and so on but just important part from here is we have the designs that we can either find vendors or the just use our shop, basically, so Yeah. + +00:15:00 + +Zach Horn: Welcome if you haven't joined before. Hey. + +Ansh Saxena: Any yeah, just looking on what's Happening. + +Zach Horn: Yeah, of course happy to have you these calls sometimes they're a little more built out. We have more design things on the table, but we have a couple different initiatives going on across the board and everything's running pretty smoothly. So there's not a toned update On the marketing side one thing that I will just as a general. Announcement if you will because we're recording I'm looking for a number of contributors across the board. So these are people that can do written content that can do video. There's a potential growth role that's in the work. So this is my official statement for the record in case anyone's listening later. If you're interested, or you can do any of those things reach out to me because we're looking to bring on I'd say about five people. + +Ansh Saxena: Okay, I'm looking to there's recent hackathon around I've been working on the cloud most console and trying to make it. It's a better thing. I'm more of a deaf person,… + +Zach Horn: amazing + +Ansh Saxena: Yeah. I mean looking around what's happening in a car and what you guys been doing what is happening in design? I'm just curious about everything. Yeah, yeah and… + +Zach Horn: Yeah, of course. Are you participating in the hackathon that's going on right now? + +Ansh Saxena: participating in the heart goes on. I'm just trying to build up something users can deploy their AI models on a cash blockchain? they can also do it right now with the cloud most but more focusing on tokenizing those models that they have deployed. So that other users can have those models after the first one actually sells out to him the deployment actually transfers from one person to other person working on building something like this. + +Zach Horn: Fantastic, that's amazing. + +Ansh Saxena: If I'm able to tokenize it, I'll be able to build a Marketplace have Dows going around them and a lot more utility everything that a smartphone and providing if it's just I'm able to tokenize those deployments. I'm trying on that. + +Zach Horn: That sounds great. Definitely. Thanks for joining today. are you in the Discord by chance? + +Ansh Saxena: Yeah. Yeah, I'm on the Discord. I'm totally connected with Max for resolving of my errors matters helping me out for this thing. + +Zach Horn: very cool Thai who's on the call as well, he's our head of operations. You should connect with him as well. He's obviously big on Discord and can help you navigate the community if you need to connect with anyone else. This is a Tyler Wright on the call with us. + +Ansh Saxena: this person told me + +Ansh Saxena: Okay Okay, Tyler. I can also see you on Discord now. Yeah. + +Tyler Wright: Yeah, but as Zach meant you'll feel free to meet out to me like Tyler core team if you have any other questions or need any help with anything, but it sounds like you're already moving the right direction. So appreciate having you. + +Ansh Saxena: Yeah, I'm mostly like having troubles with having the cloud most console running on my local machine actually been working on this for the past five to six days all day. I've been working and trying out to make this thing work yet. I'm still having some issues. I have to learn a lot things databases Docker and a lot more technical things. Running on this journey is creating exciting for me to learn how Akash is actually working out and what more possibilities I can have that Akash. + +Tyler Wright: Excellent again, feel free to reach out to me if you have anything. + +Ansh Saxena: For the chance. I'm just dming you I guess your event offline on Discord wait so that we can stay connected. + +Tyler Wright: Okay. Yeah, yeah. + +Denis Lelic: So yeah, thanks for Happy to see you here happy that you're involved already in the hackathon and in the community. You're welcome. Also to join different meetings. Either client related or we have one meeting that's happening next week. It's for nakash website. + +Ansh Saxena: I mean + +Denis Lelic: So there's been a lot of work done there by different community members as well. But if you need anything design related. Feel free to reach out on this chord me and I'll help you out as much as I can but I happy to see you're already talking to Max. So that's the right guy to talk to for everything Cloud nose console related and I know Max had an idea a while ago for creating some sort of Marketplace for templates, so I think + +00:20:00 + +Ansh Saxena: This sounds great. I actually didn't discuss a lot about this Market listing. I would definitely love to discuss with them further if you already have an idea about this thing. + +Denis Lelic: Yeah a while ago. I talked to him and I think it's just an idea and nothing tangible at the… + +Ansh Saxena: Mm-hmm + +Denis Lelic: but feel free to talk to him again and just share Your idea and so on. I think he'll be happy to help you out if you need anything that and + +Ansh Saxena: I'll do it. By the way. + +Denis Lelic: cool What… + +Ansh Saxena: This is what you do. + +Denis Lelic: what do I do? + +Ansh Saxena: Yeah, yes. I'm so new. + +Denis Lelic: I do. + +Ansh Saxena: I'm like + +Denis Lelic: I do a lot of design stuff. So everything design related on their cash side, so One day's videos. The other day is something on the product side the third day something else. + +Ansh Saxena: I understand their highness and basically designing everything related to the product. + +Denis Lelic: Yeah, + +Tyler Wright: Yeah, everybody,… + +Denis Lelic: Yeah. + +Tyler Wright: branding products, marketing. + +Ansh Saxena: mmm + +Tyler Wright: Across the entire Gambit for all things. with the parking other member + +Ansh Saxena: Yeah. Yeah. I totally get this. + +Tyler Wright: But if you have any design questions, whereas you're building out like a ux and you need some design support. I need some assets, he would talk. + +Ansh Saxena: Okay, so I don't know who took anything that the moment I've been doing some assets. Yeah. + +Denis Lelic: Yeah, just let me know me on Discord and I could help you out. + +Ansh Saxena: Yeah, okay. Sure. + +Tyler Wright: climate I make a quick announcement that maybe Zach would like and back off of. + +Zach Horn: Absolutely. + +Tyler Wright: All right, there have been a couple of folks. This is more like marketing side, but there have been a couple of teams and individuals that have been reaching out as of recently looking to partner with Akash, and the way that they want to partner with the cost is by doing a Communications or a PR partnership, which means they just want to have a shout them out on Twitter or something and then do the inverse. I just want to make it clear and again Zach can feel free to get his own thoughts on this but from a high level strategy, that's not something that a cost does the community and Zach who leads many of the marketing efforts at Akash have made the concerted and I think proper strategy to not just do announcements everything that it's announces already been integrated and been tested and works and so + +Tyler Wright: if anybody is trying to reach out whether it be a discussions or just in the general Community looking for a announcement without putting any + +Tyler Wright: Integration working or without showing a proof of concept at the very least. I just want to let you know just what's on the record that probably is not something that Akash is interested in again. We love folks that are creating content that shows like development work that shows like a process and shows like something that can drive Demand on the network. But if somebody's just trying has a project and they're just trying to latch on to the coattails of Akash for quote unquote a PR announcement. That is kind of empty that's not something + +00:25:00 + +Zach Horn: Yeah, now you have to hit the nail on the head. I appreciate you putting that on the record, by the way. I'm going to clip that audio and anytime I get one of 10 million. Are you interested in a marketing collaboration thing? I'm just gonna link them your audio. but yeah, I mean that's generally the right direction and entreer context Because these calls recorded sometimes we just stuff for the record, it's very formal in that way. + +Ansh Saxena: Yeah. Yeah I get this thing. + +Zach Horn: Yeah, totally. + +Zach Horn: but yeah, that's generally the idea I mean from + +Ansh Saxena: I don't think This is a good thing. We can't actually move forward just with the ideation thing. You must be actually putting in some efforts that are visible to everyone. + +Zach Horn: So generally the way that the marketing works at a high level. For cash which obviously is this relatively unique open structure. We just want to see integration. So at the point that we're going to talk about co-marketing, we just need to see that your deploying on the network you're using, the resources in some way you're gonna build a tool and then we can get into those conversations over time. But yeah Ty said it perfectly. + +Zach Horn: That's my statement for the record. + +Denis Lelic: Right. Thanks. + +Zach Horn: Yeah. + +Denis Lelic: Okay, so that's I guess off on the marketing side. for the rest of the guys that and join in later. We talked about Akash accelerated which is happening in but three weeks so we just went through different touch points from swag and when you and everything that Needs to be designed there and a lot of these touch points already in production. So + +Denis Lelic: let me just a couple of thoughts on what's happening in the future and there's going to be Bonsall rebranding of console is happening, so + +Denis Lelic: There's gonna be some new additions to the ux UI. We are trying to solve a couple of friction points around payment and connecting wallets and so on so I'm pretty much what? All of the web 3 world is trying to solve so great and creating a frictionless web 3 experience. So + +Denis Lelic: yeah, and I think that's gonna take some time as well in the future just to + +Denis Lelic: Do our best on that front? and of course + +Ansh Saxena: Accelerating something interesting. Can you give me some more details on this? if I'm able to implement something for this hackathon? I'll definitely want to get into this program after working after the hackathon. + +Denis Lelic: yeah, the thing I think is guys from console cloudmos are trying to or they already actually did a big part of switching to a different library from material to tailwind and share cnui Library. So that's one bigger part that they're going to do and on the other and we still have to design a bunch of the stuff I've mentioned on the payment stuff and we're trying to + +Denis Lelic: also connect private repos from GitHub. And so there's going to be a lot of Explorations done in the beginning. And as soon as there's something tangible will share it. you're happy. I'll be happy if you joined one of these calls so we can discuss. What's working? What's not and so on and so on so + +Ansh Saxena: Yeah, would love to join these scores. also one more thing. Is that our guys also working on looking to integrate that private containers thing from a Docker that is like something I'm very much interested in to working on. + +Denis Lelic: Yeah, I'm not sure if Pierce. So his handle on Discord is bold Panther. He's been working on that front. So just trying to connect. Private GitHub repos to the console. + +00:30:00 + +Denis Lelic: So maybe + +Ansh Saxena: Can you write it even a chance as well? + +Denis Lelic: His handle is pulled Panther. + +Ansh Saxena: Thank you. + +Denis Lelic: Yep, so she's also a Community member often joins these calls and he did a lot of work on the Akash website. So we're basically revamped the whole website added a lot of new stuff there. We changed the back end and this was done. I believe in the beginning of the year but yeah. Also someone who I think would be happy to help you out with different related things. + +Ansh Saxena: Yeah, yeah anything with him. + +Denis Lelic: + +Zach Horn: Hey harsh question for you slightly selfishly promote from a marketing perspective and I don't mean to put you on the spot so you don't have to share if you don't want to but how'd you hear about Akash first? + +Ansh Saxena: I already knew about the guys because I've been working initially with strong as well. I've been working on their sdks and with their Integrations on a few of my hackathons very much involved into helicals last year. I went 10 of them. So I have already used this Channel and I remember initially used to leverage a car for their compute things and got to learn about Akash from there in my initial days and from then I had this clue about that the cautious something like some sort of a cheap unit that actually provides Run 10 deployments on the instance,… + +Zach Horn: Amazing. Love to hear it. + +Ansh Saxena: pay for the time that you want the resources not like this a monthly subscription thing and… + +Denis Lelic: Yeah,… + +Ansh Saxena: I love this model. + +Denis Lelic: we're kind of thought it off slow only me and… + +Ansh Saxena: I thought they can be a lot more things revolving around this particular model that you only need to pay for the time you are using the resources and… + +Denis Lelic: Zach. I'm happy this meeting is ending on a good note. So + +Ansh Saxena: not the monthly subscription or something like that. So yeah that got + +Ansh Saxena: Very much interested for parts spending in the hackathon and… + +Denis Lelic: Of course, all of you are welcome to join. all of our next meetings and… + +Ansh Saxena: building or something as well. + +Denis Lelic: if you're interesting interested in design related stuff, me on Discord or you can join the next meeting where we talk a lot of about design stuff is also the Akash website meeting which is happening next week. So I'll be happy to see you there as well. Okay, any questions anything you guys want to talk about while we're here? + +Zach Horn: Not for my side. I think we covered most of the things we had to talk about. Anything else from the design side Denis? + +Denis Lelic: No, I think we pretty much covered everything so. + +Denis Lelic: A product looked really cool. I've been okay. Which product are you referring to? Sorry. + +Zach Horn: All the products Denis they all look amazing things to you. + +Denis Lelic: Okay. + +Tyler Wright: but + +Zach Horn: every Yeah. + +Denis Lelic: Okay. + +Zach Horn: Yeah, I think the merch looks great too. I mean we've done so many iterations of merch over the years, but I really like this current set that we are working on now. I'm a soccer jerseys. + +Denis Lelic: Yeah. + +Zach Horn: I'm really looking forward to I think those are gonna be super cool. + +Denis Lelic: yeah, especially nobody's gonna play soccer and + +Zach Horn: now we have to start the costly. + +Denis Lelic: Yeah, yeah exactly web 3 League. + +Zach Horn: Yeah, that's right. + +Denis Lelic: Go. + +Denis Lelic: Yeah, so thanks For the compliment, I guess on the product side. So we'll do a complete overhaul of the Akash shop where we're gonna present new products new designs and so on and so stay cool so I think we are pretty much. Done for today also On the time side. It looks like we're approaching the end of this meeting. So thanks everyone for joining today. Feel free to DM me as I said many many times for everything design related on Discord. Otherwise, we'll see each other here next month. + +00:35:00 + +Denis Lelic: Thank you. + +Zach Horn: Sounds great. Thanks guys. Take care. + +Denis Lelic: Thank you. Have a good day. Bye. + +Ansh Saxena: And my mind is being very helpful to me as well. + +Meeting ended after 00:36:22 👋 + From 577a71a0320e1540ea2ede0995c8d8b422fd5490 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 20:20:50 +0000 Subject: [PATCH 063/138] Create meeting notes for sig-support #32 (#579) * Create meeting notes for sig-support #32 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 032-2024-05-01.md add meeting transcript chore: add video recording. Signed-off-by: Drinkwater * Update 032-2024-05-01.md add video recording Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-support/meetings/032-2024-05-01.md | 161 +++++++++++++++++++++++++ 1 file changed, 161 insertions(+) create mode 100644 sig-support/meetings/032-2024-05-01.md diff --git a/sig-support/meetings/032-2024-05-01.md b/sig-support/meetings/032-2024-05-01.md new file mode 100644 index 00000000..671e3255 --- /dev/null +++ b/sig-support/meetings/032-2024-05-01.md @@ -0,0 +1,161 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #32 + +## Agenda +- Triaging of Support Issues +- Discussion on Support Themes +- Updates on Network Upgrade and Roadmap Progress +- Participants can have an open discussion of any other issues or support related items on Akash Network. + +## Meeting Details +- Date: Wednesday, May 1st, 2024 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://fp4bufbowjh5thinihsyy52ddcyesjk2yofv4fgjmrhnkahxg5ua.arweave.net/K_gaFC6yT9mdDUHljHdDGLBJJVrDi14UyWRO1QD3N2g) +- [Transcript](#transcript) + +## Participants +- Andrew Hare +- Andrey Arapov +- Scott Carruthers +- SGC | DCnorse +- Tyler Wright + +## Meeting Notes +### Introduction and Updates +#### Tyler wright +- Tyler Wright's Introduction: + - Welcomes participants to the Sig Support Biweekly meeting, marking it as the 32nd one. + - Highlights the focus on issues within the support repository and the core code base. + - Acknowledges the support community's role in assisting new and existing users with the Akash Network. + +- Triaging Process: + - Tyler Wright steps in to lead the triaging process due to ongoing main net and provider upgrades. + - Indicates that all current issues have been triaged, either through internal discussions or previous meetings. + +- Updates and Roadmap: + - Mentions new items added to the board by Overclock Labs core team, outlining a roadmap for the next seven months. + - Emphasizes tracking milestones for engineering projects and potential sub-projects. + - Discusses the progression of items from backlog to live on the Akash roadmap. + +- Network Upgrade: + - Alerts participants about a planned network upgrade scheduled for the next day at 1600 UTC. + - Specifies that it involves validator and provider upgrades, with validators upgrading first, followed by providers after network stability testing. + +### Emergency Provider Upgrade +#### Tyler Wright: +- Tyler Wright addresses a pressing issue regarding the need for providers to upgrade to version 0.5.14 due to a vulnerability that was found and patched. +- Urges community members to upgrade their providers to version 0.5.14 as soon as possible. +- Mentions forthcoming instructions for providers upgrading their nodes and providers, advising participants to watch for announcements. +- Notes that the validator upgrade proposal has passed on chain, with preparations ongoing for the upgrade scheduled for the next day. + +### Open Ticket Discussion +#### Tyler Wright: +- Tyler Wright invites questions or comments regarding any open tickets or offers for participants to get involved in resolving them. +- Encourages participants to add comments to open tickets, suggesting potential solutions or questions, and prioritize tickets by labeling them accordingly (e.g., P1, P2). +### Cloudmos Issues and Updates +#### Tyler Wright: +- Highlights Cloudmos team's diligence in addressing issues in Cloudmos repositories and keeping the community informed via Discord. +- Mentions a console refactor and rebranding on Cloudmos's roadmap, assuring users that it should not impact current usage as features will remain available in the console version, an open-source deployment solution for Akash. +### General Support Discussion: +#### Tyler Wright: +- Tyler Wright transitions to the second part of the agenda, focusing on general support in Discord. +- Acknowledges the lighter attendance due to preparations for the main net upgrade. +- Invites participants to share any recent Discord discussions or issues worth discussing. +- Highlights the role of Insiders in tracking spam and scammers in Discord and mentions ongoing monitoring by the Auto mod bot. +- Encourages participants to notify him if anyone seeking validator role access is not granted and assures verification. +- Notes the plan for communication during the upgrade, with validators updating in the validator channel and providers awaiting specific announcements. +- Announces a steering committee meeting post-mainnet upgrade, welcoming community participation and input on discussion topics. +### Other matters discussed +#### Feedback on Discord Events +- Tyler Wright addresses an issue raised regarding Discord events tooling. +- Considers the possibility of removing it due to random bugs and inconsistencies. +- Requests feedback from the community on whether Discord events serve as a useful indicator or are a distraction. +- Acknowledges the ongoing effort to update events in Discord and expresses determination to improve usability. +### Closing Remarks +#### Tyler Wright: +- Assures availability of meeting notes shortly after the meeting. +- Urges inviting individuals with a background or interest in Akash Network to the sig support meeting to facilitate their involvement. +- Reminds participants to encourage providers to upgrade to version 0.5.14 if they haven't already. +- Tyler Wright thanks everyone for their time and emphasizes watching out for announcements related to the network upgrade. +- Encourages continued growth of the Akash Network and invites further questions or thoughts via sig support or Discord. +- Wishes everyone a great day and anticipates further discussions in Discord as preparations for the mainnet upgrade continue. +## Action Items: +- All providers to upgrade to version 0.5.14 to address the vulnerability. +- Validators to prepare for the scheduled upgrade tomorrow. +- Cloudmos to prepare for the console refactor and rebranding, ensuring a smooth transition without affecting current users. +- Tyler to evaluate the usefulness of Discord events and determine whether improvements or removal are warranted based on community feedback. +- Group to continue monitoring and adjusting Auto mod bot settings to support server moderation. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All Welcome everybody to Sig support biweekly. The date is May 1st. I believe this is number 32 for six support during the six support biweekly. The community goes over any issues inside of the support repo again any issues related to the core code base? Go inside the support repo. There's an escalation path that go happens in Discord to determine if items are really issues. So thank you to all the Insiders vanguards and general community members that help new and existing users get acclimated with the Akash Network. + +Tyler Wright: normally a member of the core team leads us through triaging but I know again there's a lot going on with the main net upgrade with additional provider upgrades. So there's obviously members of core team here, but I will be walking us through the triaging of the issues today and then I'll just call upon anybody that again can help. + +Tyler Wright: After that, we'll go on with the typical agenda and discuss just any support or any themes that might be worth talking about during the six support. Without further Ado than I will pass it to myself to get us going with the triashing of issues. + +Tyler Wright: As you can see there are no issues that currently need triaging everything has been triage already whether it be through internal core discussions and stuff that Court members of the core team are working on or again if it was previously triage at a Miko meeting two weeks ago. + +Tyler Wright: I do want to quickly call out again. there's a number of new items that have been added to the board in the maybe last week or so. overclock Labs core team comprised at the product and Engineering teams have come together to develop a roadmap of things that the core team is going to be focused on over the next I would say seven months again. All these items have been added to the board and they're probably will be some additional atom items that will be added over time as kind of sub-project to some of these major projects. If you can go into milestones and you can kind of track some of the major milestones for engineering and some of these groups. But again, we'll continue to track these items and discuss some more in detail and discuss progress many of these items over time. We'll get moved to the + +Tyler Wright: Akash roadmap some are in backlog right now. But again as they begin to get get moved from backlog to up next and in progress and testing and then again live so just a number of items to look out for One item that I want to touch on Just for everybody here is the network upgrade the believe that the new version has been cut in is in the documentation link. I will share with folks so that they have it and I'll put it in the notes. But again, there is a planned Network upgrade happening tomorrow around 1600 UTC. + +Tyler Wright: This will be a validator upgrade as well as a provider upgrade again as we do with every upgrade the validators will upgrade first. The stability of the network will be tested after that upgrade happens and then once announced providers will upgrade their infrastructure their providers. + +00:05:00 + +Tyler Wright: One thing that has been more pressing and I think some people have seen some notes. + +Tyler Wright: Messages and Discord and elsewhere there is the need for providers to upgrade to version zero dot five dot 14 again. There's been announcements over overnight. There was a vulnerability that was found that was needed to be passed and has been patched and again just sharing that with members of the community so that they can upgrade their providers to again version. 5.14 as soon as possible or version 0.5 dot 14 rather. + +Tyler Wright: Again, there will be some more instructions that happen tomorrow for providers upgrading both their node and the provider but please look out for those announcements. But again, first matter of business will be the validator upgrade again. The proposal has passed on chain this morning. And so now preparation is continuing release has been shared in documentation and again folks validated should just be getting ready for the upgrade plan for tomorrow. Does anybody have any questions or comments about The? Emergency provider upgrade that is going on right now. + +Tyler Wright: All right continuing on again there's nothing that's currently awaiting triage. Everything has been labeled. and has been assigned. I want to see if there's anybody that has any questions about any Open tickets or if anybody wants to get involved and solving any Open tickets. + +Tyler Wright: If not now then again anybody can feel free to add a comment to an open ticket, with potential Solutions questions that they have. And you can see the prioritization of different tickets by labeling here, P1 P2 Etc. + +Tyler Wright: All right continuing to move along with the agenda after going through triassing of issues in the support repo. If cloudmo's team is usually here we will see if there's any Cloud most issues. But again, the cloud most team does a great job of looking at the cloud most repos seeing any issues there and then continuing to keep people up to date in Discord. One thing to note is again. There is a cloud most and you can see this on the road map as well. There's most a console refactor and Rebrand happening. So again Cloud most will be + +Tyler Wright: changing branding and again the visual look will continue to evolve. There'll be some more information that happens over the next couple of weeks that's pertains to the plan for that switch over. It should not affect anybody that's currently using Cloud modes because again much of the work has been refactoring to make all the features that were previously available in cloudnos available in the console version which will be again the deployment solution open source that people can work on and deploy onto a trust with + +Tyler Wright: Cool, if one has any questions about any of the issues and support repo, then we can move on to the second part of the agenda around against General support in Discord. + +Tyler Wright: All right moving along. Usually we have a number of insiders and vanguards during this call, but I know a number of folks are again getting ready for the main it upgrade and doing some other items. So it's a lighter crew today. does anybody on this call want to mention anything that they've seen recently and Discord that might be worth discussing or just again just bring to the attention of this group. + +00:10:00 + +Tyler Wright: All right, I'll take that as a no again. I know that the Insiders look to track spam and scammers in Discord and try to eliminate them words get consistently added to the Auto mod bot again help support modding the Acosta server. So again that will continue to get monitored. If anybody sees anybody in Discord that's looking for a validator role because they are validator in the active set and they don't have access to that Channel. Please feel free to reach out to me or just tag me publicly in that whether it be General chat or whatever Channel we can again verify their validators status and make sure that they have access to the validator channel. + +Tyler Wright: during the upgrade tomorrow folks will be in the valley or channel to just talk about let the community know when they've upgraded their validator. And again we do with every upgrade just stay in tune just in case there's anything that needs to be updated or fixed and members of the community always will stare share snapshots in that channel again for validators. Following that upgrade as I just mentioned at the top of the call then again, there will be a specific announcement that goes in the provider announcements channel that will indicate when providers should be upgrading their provider and their nodes. So please don't feel like you have to do anything until properly notified. + +Tyler Wright: The last thing I will say is after the main net upgrade to tomorrow. planned though. There'll be a steering committee meeting happen again. They got pushed back one week. So if anybody has any disgusting they want to bring up or any talking points, please add to those discussions get folks from the community to participate in this discussions and leave comments. And then again, we'll discuss items and more detail at the steering committee meeting tomorrow after the meeting up great. So it's very very busy period + +Tyler Wright: That's all I have. I know I've been talking a lot. Is there any questions from anybody here today about anything support comments + +Tyler Wright: If not, then again, please if anybody here sees anybody in Discord in the provider channels or some of the other channels and you that they're provider. Please make sure that they have upgraded to zero. Dot 5.14 + +Tyler Wright: Yeah, what I would say is and I'm not at a crossroads right now part of me wants to and this is a direct response to sgcd dcnorse. there seems to be major issues with the Discord events. Just tooling. It just has bugs at random times. I would say I would ask that anybody in the community and I'm determining whether or not I should just remove it all together. But again it is a good indicator for some folks. But the best source of Truth for meetings on the calendar is always the website. I'll drop the link in here again. + +Tyler Wright: I tried to update the calendar in real time and it just does what it wants. I'll change I'll change the dates. I'll add meetings and it just will disappear and there's no Rhyme or Reason. there's been multiple people that have the same issues. So I'm going to determine if the events and Discord are distraction or if it's at least like a call to action that people can then reference against the calendar, but we can talk about that. It's steering committee or Beyond but please I'd like that. yeah, I appreciate that feedback in the chat, but we will update again the steering communities happening tomorrow and we'll continue to update the events and discourse so that it's more usable or usable at all. + +00:15:00 + +Tyler Wright: If there's nothing else then if anybody has any again specific questions about any issues drop them in the support repo, I'll make the notes available shortly after this meeting among. No. I'm a little bit behind on some of the meeting notes, but I will have those before steering committee tomorrow so we can just track again a couple of the last meetings and just continue to look forward if anybody sees anybody in Discord that has go background and wants to get more involved. I urge you to invite them to this six support meeting so that again they can meet some of the core team and look to get involved a little bit more Hands-On with the product or at least again get them acclimated. There's a number of documents that have been developed by members of core team and the community that helped to help folks to understand the cash Network. So again anybody that you see that's looking to get more involved, please push. + +Tyler Wright: Direction at six support client Sig providers Etc. And if you see anybody that's a provider that has not again upgraded to 0.5.14,… + +Andrey Arapov: Think of Tyler. Thank you. Later. + +Tyler Wright: reach out to them send them The Discord announcement that Andy has put in Andres put in provide our announcements this morning and… + +Andrew Hare: I guess. + +Tyler Wright: have them continue to make sure that they're upgrading to again zero dot 5.14, please. + +Tyler Wright: All right, if there's nothing else then I know everyone's busy and we can just get back to work. But again, please look out for announcements related to the network upgrade tomorrow and then again providers upgrading when announced and we'll just continue to work on growing the across Network. Most appreciates everyone's time today. And again, please feel free to reach on six support in a specific issue or just in Discord somewhere if you have any more questions thoughts Hope everyone have a great rest of the day and we'll talk more. I'm sure and Discord and as we get ready for the main net upgrade tomorrow. + +Tyler Wright: Talk to y'all later. Bye. + +Meeting ended after 00:16:35 👋 + From e169b4b937ef7f643300a5854ffa5f080f4645cf Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 20:35:24 +0000 Subject: [PATCH 064/138] Create meeting notes for wg-website #29 (#581) * Create meeting notes for wg-website #29 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 029-2024-04-04.md add transcript for meeting on 04/04/2024 Signed-off-by: Drinkwater * Update 029-2024-04-04.md add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-akash-website/meetings/029-2024-04-04.md | 302 ++++++++++++++++++++ 1 file changed, 302 insertions(+) create mode 100644 wg-akash-website/meetings/029-2024-04-04.md diff --git a/wg-akash-website/meetings/029-2024-04-04.md b/wg-akash-website/meetings/029-2024-04-04.md new file mode 100644 index 00000000..3763f27f --- /dev/null +++ b/wg-akash-website/meetings/029-2024-04-04.md @@ -0,0 +1,302 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #29 + +## Agenda +- Review of website-related issues on Akash Network repo +- Discussion on ecosystem page and token page updates +- Update on graphic for the website + +## Meeting Details +- Date: Friday, April 04, 2024 +- Time: 6:30 AM PT (Pacific Time) +- [Recording](https://yiwmcmmelchqik2ii4s7yt2wzvjy55gwxnpe2uekrwv6rv552sgq.arweave.net/wizBMYRYjwQrSEcl_E9WzVOO9Na7Xk1Qio2r6Ne91I0) +- [Transcript](#Transcript) + +## Participants + +- Denis Lelic +- Piyush Choudhary +- Thomas Greco +- Tyler Wright +- Zach Horn + +## Meeting Notes +### Introduction and Updates +- Denis Lelic opens the meeting, welcomes attendees +- Review of issues on Akash Network repo: Two new issues identified - ecosystem page and token page update +- Piyush Choudhary to address the identified issues +- Piyush presents solution sourced from Discord community for consideration +- Proposal to summarize lengthy text, suggest scrollable solution +- Denis acknowledges possible outdated content, suggests verifying missing parts +- Discussion on updating a graphic for the website, involving Scott or Cheng for updates +- Tyler Wright confirms graphic update, advises verifying community member's advice +- Denis agrees to double-check before updating the graphic + +### Updates on new website features: GPU pricing +- Piyush Choudhary introduces new GPU pricing feature on the website, accessible through menu item and announcement bar +- Denis Lelic elaborates on new section in hero section of home page, detailing options for users to get started +- Discussion on discrepancies in documentation, specifically regarding GPU pricing explanations +- Thomas Greco suggests adding a paragraph to explain GPU pricing for users unfamiliar with GPUs +- Denis acknowledges the suggestion and notes existing explanations on the website, agrees to consider adding more detailed information +- Tyler Wright proposes adding GPU pricing details to documentation for further clarity, to be discussed offline or in sync docs +- Tyler mentions pending discussions on Google Analytics and Akash Accelerate 2024 page updates, deferring further discussion for later +- Zach invited to share any additional points related to Thomas's suggestion or pending topics +### Updates on Google Analytics +- Zach Horn brings up the topic of Google Analytics implementation, notes need for GA code embed on the website +- Tyler Wright confirms the need for GA tracking on call-to-action buttons and pages, stresses high priority +- Zach clarifies the need for conversion tracking and account transfer for GA +- Piyush Choudhary confirms readiness to implement GA code once received, mentions technical issues with tag manager +- Tyler inquires about timeline for implementation, emphasizes the importance of having a timeline +- Piyush estimates 1-2 days for resolution of technical issues and implementation of GA tracking +- Zach acknowledges the timeline and expresses gratitude +### Updates on Akash Accelerate 2024 event +- Tyler Wright discusses Akash Accelerate 2024 event, highlights the need for a landing page with basic information +- Denis Lelic and Zach Horn are working on design and content for the landing page +- Tyler emphasizes the high priority of the landing page, planned for phase one early next week +- Denis suggests considering a theme or visual team for the event, to be discussed further +- Tyler suggests discussing the theme offline, possibly involving SIG design +- Tyler acknowledges Thomas for his contributions to documentation and ongoing support +- Meeting concludes with confirmation of action items and gratitude towards Thomas. +### Discussion on "how to contribute" page +- Denis Lelic brings up Thomas's offer to assist with code or PRs, suggests a brief discussion on the "How to Contribute" page +- Tyler Wright explains the need for a visual guide for new contributors and plans for further discussion over the next week +- Denis reminds the team to check a message on the Akash website external Slack channel +- Thomas Greco shares updates on upcoming PRs and videos for onboarding, mentions the delay due to focus on the agoric mainnet release +- Thomas reaffirms commitment to assisting with onboarding efforts. +### Video content creation and tools discussion +- Denis Lelic and Thomas Greco express gratitude and collaboration regarding video content creation and tutorials +- Denis discusses plans for creating a blueprint for future video contributions, considering software options for editing +- Thomas raises concerns about potential costs for gated tools like 11 Labs, suggests considering free resources +- Zach Horn offers financial support for necessary subscriptions for video creation tools +- Denis confirms no cost blockers and encourages open communication for resource needs +- Denis concludes meeting, summarizes topics covered, and invites further discussion or adjournment +- Team members express thanks and confirm conclusion of the meeting + +## Action Items +- Piyush Choudhary to address ecosystem page and token page updates. +- Denis Lelic to check with Scott or Cheng for updates on the graphic. +- Denis Lelic to double-check before updating the graphic. +- Piyush Choudhary to resolve technical issues with GA implementation within 1-2 days +- Denis Lelic and Zach Horn to work on Akash Accelerate 2024 landing page design and content. +- Tyler Wright to coordinate with Zach and Denis regarding Accelerate 2024 theme and content. +- Tyler Wright and Denis Lelic: Discuss and plan "How to Contribute" page. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Denis Lelic: Hi everybody and welcome to today's working group meeting for Akash website. We meet either on a weekly basis where we discuss everything website related ui/ux adding new features changing content and so on so I'm just gonna get us going. I just had a look. at the repo and the issue sections on the website repo on Akash Network. So let me just grab the link. So you can follow along. And I see there are two new issues. They're created one is for ecosystem page and the other one is token page update. Piyush. Do you want to take us through these two issues? + +Piyush Choudhary: yeah,… + +Denis Lelic: Thanks. + +Piyush Choudhary: depending on Financial. + +Piyush Choudhary: Yeah, so as you can see this is the largest thing pushed out by the commute numbers and Discord so I just grab it from there. So you consideration right now on the system areas. We cannot wait the whole text that is thinking So the status solution which is scroll down so that we can presentation. + +Piyush Choudhary: We store Donuts Edition. So when they follow the god. For the Restriction benefit like this. + +Denis Lelic: Yeah, that seems like a reasonable solution. So I know some of this text may be outdated. I know Greg was writing a lot of this in the previous ecosystem page and I believe there's also links inside of this. So yeah, I do agree if we're missing parts of this text, actually get the whole thing. + +Denis Lelic: yeah good call out. Thank you. + +Piyush Choudhary: So if you see there is a community which is required as 25% brightness living on information. So yeah, I just + +Denis Lelic: Yeah, I'm gonna have to check with Huey or Chang to see what are the updates on this graphic? + +Piyush Choudhary: + +Tyler Wright: Denis this is a graphic that we were talking about that we saw some P back on and we were trying to remember this is the graphic that has to be updated. + +Denis Lelic: I do have all the information or should I just check with Huey and I can update it. + +Tyler Wright: I would say double check with you, but I think the advice from the Community member was correct the double check if you + +Denis Lelic: Okay, you got it. Cool. Thank you. + +Denis Lelic: So yeah. + +Piyush Choudhary: So that's all from myself. + +Denis Lelic: We have you here. Is there anything website related that you would like to speak? about + +Piyush Choudhary: So yeah, so as we can see we have a new feature live on the website GPU pricing. So I was personally public information based and as you can see this light, so everything go to the lectures. So that's the new feature that is simply onto the website. + +Piyush Choudhary: We also have the papers as you can say. + +Denis Lelic: Yeah. this page is reachable through the new menu item called GPU pricing. I believe also through the announcement bar and through this button here view GPU availability also a new section in the hero section actually on the home page where we have get started basically right away above the fold and they're like three options one is to export apply pricing the gpus or get users going either through becoming a provider or deploying their first app. yeah, so I am a piyush anything else. + +Piyush Choudhary: So there is nothing much but there was on the dates going on in dogs. So there was a mistakes or something beings which maybe numbers are falling out and all of them were big or not from ourselves. That's awesome. + +00:05:00 + +Denis Lelic: Okay, Yeah I saw your hand when up first and Tyler then you can go. + +Thomas Greco: Yeah, so I think the GPU pricing stuff looks awesome, but I did have a question. So is there anything that explains? the GPU prep I explained this in more detail. So as somebody who's not. super well-versed and gpus + +Thomas Greco: I like even just a entry level, And paragraph kind of explaining what's going on. I'm not sure if anybody else thinks that would be useful. Or if we should just kind of assume that whoever's looking at this. + +Denis Lelic: Paragraph meaning to explain the pricing or something else. + +Thomas Greco: Yeah, a pricing maybe like chips right, what types of jobs? + +Thomas Greco: A specific chips maybe better equipped to handle stuff like that. again, this is just a half suggestion, it's just something I want to call out. + +Denis Lelic: Yeah, personally. I think that. if you're looking for gpus and you don't know what age 100 or a 100 offers if you don't know if a paragraph can help you… + +Thomas Greco: Mm-hmm + +Denis Lelic: but Yeah, we do explain a little bit in this hover button about the price. So how do we get the price? So it's actually like a bidding. + +Denis Lelic: there's a disclaimer here which this offers a better explanation how the price Are sorted out here. + +Thomas Greco: Okay, I get it I think and I think it looks really really great and it is in deformative and if you have this knowledge going into it then you're good. But yeah. And you're right. I think if you're looking at it. + +Thomas Greco: then if you're in the market for gpus you're gonna know which. the capabilities different ship sets, but I just yeah. + +Denis Lelic: Yeah. Yeah,… + +Thomas Greco: I don't worth mentioning. + +Denis Lelic: cool. Thank you Ty. Go ahead. + +Tyler Wright: Yeah, I think Thomas quickly to that point maybe it's something worth adding in the documentation that we can link to the pricing page. So maybe we could talk about that offline or in sync docs, but I think that would be great. The things that I want to talk about haven't been talked about yet. So I don't want to Sidetrack the conversation. I don't know Zach if you had something you want to talk about relatively Thomas's point, but I want to talk about this Google analytics as well as the classic celebrates 2024 page but yes. + +Zach Horn: Yeah, my points on Google analytics. So let's jump right to that. + +Tyler Wright: Okay, cool. I guess I know this has been something I've been trying to work with internal team member on I think it's just like a access issue for me because I've been looking all over Zach. I know it's been helping out but I know Google analytics is something that we want to get across the website and all the call to actions as well as Pages as soon as possible and have a dashboard. So Zach. I don't know if you had an update. I know that we just talked about this yesterday so they may not be an update quite yet, but I just want to see what your thoughts were on the Google analytics the next steps as well. + +Zach Horn: Yeah, definitely. So the question right up about is I saw the note yesterday that we need the ga code embed on the page. I've access to our overclock on Akash Google analytics account so I can get that any time. What was the thing we recording with our team + +Tyler Wright: That was it the ga code. Yeah, yeah. + +Zach Horn: Got Okay, I can get that. So there's no blocker there. On the Google analytics Point more broadly… + +Tyler Wright: Okay, cool. + +Zach Horn: what we really need and what is highest priority is that we know the conversion rate through each of these rents now buttons so that can't stress it enough. It's super high priority. We need that conversion implemented in GA ASAP so that we can start tracking it page total page volume and it's great but we really need to know of the people that are landing on this page how many are converting through each of these buttons and be able to measure them against themselves? Each other I should say that's highest priority because we want to see other people that are landing here which chips are they converting on and one of the interested in so we can start to gauge demand. So two things one for next steps. What is the status on putting that conversion in place? And then what is the status of transferring that the entire account? + +00:10:00 + +Piyush Choudhary: Can you repeat the last point when you say entire town? what do you mean by an entire problem? + +Zach Horn: As I understand that the Google analytics are under your account currently, that's where we're tracking them. We need those to live. + +Piyush Choudhary: Yeah. Yeah,… + +Zach Horn: Yeah. Got it. + +Piyush Choudhary: so I just need to determine shows quotes that I mean those will be able to still. + +Zach Horn: Piyush your audios not great miss most of that. One more time, please. + +Piyush Choudhary: So yeah, I'm saying once we got the Gtech box as I said in the group, so we'll be able to implemented and all the lighting side is deciding in order Sports will be migrated with that for overlock Lots. + +Zach Horn: Got it. + +Tyler Wright: If we get those GA pose to you today? How long will it take for you to Those buttons are Implement like tracking for the red buttons and… + +Piyush Choudhary: + +Tyler Wright: then make it available to Zach and others. + +Piyush Choudhary: yeah, I was experimenting with the tag managers course to implemented on that are not working. But there are some issues that we think in terms of escrow and the specific cities cycling building algorithm and writers and just resolving those ones those issues are being resolved. I'll be able to presentation person. + +Tyler Wright: All right, when you say no you have issues, that's something that you're blocked by anybody on the core team or… + +Piyush Choudhary: So there's probably some technical issues in the Astro and… + +Tyler Wright: is this something that you're with? + +Piyush Choudhary: the specifics you get wrappings. So. I'm just resolving the issues when I Implement it's a little bit technology. + +Piyush Choudhary: Generally should connect to the United States transport, but it is not connecting producing issues. probably that's something look and this resolving those issues. Once those are it's all a legendary which + +Zach Horn: Okay, I think I understand that. You know what you're saying from a technical standpoint. We do need a timeline on it though. So what do you think in terms of timing? + +Piyush Choudhary: Second us think of wonderful days the patient steps in charge today, then tomorrow I'll be able to Otherwise on teleported for the US medicine. from now + +Zach Horn: Okay, so we're one to two days. So, call it Friday Saturday. Okay, sounds good. + +Piyush Choudhary: Yeah. + +Zach Horn: Thank you. + +Denis Lelic: Okay, cool I know you mentioned briefly the Accelerate 2024. + +Tyler Wright: Yeah with Akash accelerate proposal passing on chain and the production of the actual event is underway to think that was being secured. The date has been set the idea is that we want to have a landing page that we could start getting to people. So people know they're going to consensus or if they just love to pass and want to come to the event. They're more than welcome. So again, toothpages would be like a landing page and some basic information that we look to get up at some point early next week. I know that Denis and Zach are working on the lemonade designs and that's more information becomes available. Yes speakers schedule all that kind of stuff and we would just continue to fill out that page that's closer. But again, the event is scheduled for May 28th. So we want to start making it available for people to + +Tyler Wright: good to be a big link. Yeah Luma and then just again that's a basic information or website. So this is I think secondary to the Google analytics Zach here correctly from wrong, but this is also a high priority item when we're looking to get out and a phase one. early next week + +00:15:00 + +Denis Lelic: Yeah, like anything you want to add to that? + +Zach Horn: No, totally agree, though. + +Denis Lelic: Okay, Yeah, and Tom, I piyush I already saw you you saw the message here from Thomas. He's kind of offer his help with anything code or PR related. Just let Cool I don't know if we should talk about. how to contribute page we talked about it yesterday for a couple of minutes or do you think we could just push it to the next meeting? + +Tyler Wright: I think I can talk about what so I know that one thing that we get a lot of people in the community, is hey, I just found out about Akash, how can I contribute there's a number of ways whether it be doing a secret working group whether it be joint being an Insider a down key, this is a plethora of So I was talking to Dennis and Zach about basically making a visual page. It has some graphics and we can also turn into a handout that we can share with people in this board and elsewhere to make it easier for people to get on board and contribute. I just like being kind of be like a visual YouTuber experience map so we can talk more about that over the next week or so, I think and then see where we are going to the next meeting but certainly their priorities over the next couple of days and next week is around the Akashi accelerate 204 pages. + +Tyler Wright: Go ahead another stuff. + +Denis Lelic: cool + +Denis Lelic: Yeah, just one more thing about Accelerate 2024. I was thinking if we're gonna have some sort of a theme a visual team around the event or maybe it's even content related. On Zach, I'm not sure if you're really That deep into that issue, but that just something that pop into my mind. is it like a theme related? I don't know. + +Denis Lelic: Maybe something around AI gpus. + +Tyler Wright: Or something about Cowboys they get together so we can figure that out. + +Denis Lelic: He yeah. + +Tyler Wright: It's offline. Maybe that's a cig design type of problems. One thing I also want to call out quick is and this is kind of sick documentation related, but I do want to shout out Thomas for all the help that he's with the first video which will be added to documentation as well as he's looking to provide a great deal of support and looking at the documentation auditing specific sections appears. Just look out for some + +Denis Lelic: Thanks Peers, just one quick thing. There was a message it was on slack on the channel like Akash website external. So if you could please have a look at that Tom I saw your hand went up. + +Thomas Greco: Yeah, no, I was just gonna say I like no problem y everybody. And definitely be on the lookout for PR's videos in the coming days and I haven't had time this week to we're kind of getting the details all figured out but ask for why there's been nothing open yet. It's just been because we were getting it figured out and then I'll show with getting this kind of a goric mainnet to release. out the door that took up a lot of brain power, but I'm excited to start firing and all cylinders. Making this thing is a helping people on board, right? + +Thomas Greco: As best as we can. + +00:20:00 + +Denis Lelic: Yep. Thank you, Thomas. + +Thomas Greco: And Shadow 11 labs. the real MVP too + +Denis Lelic: Yeah, Me and Thomas were just like dming and the last couple of days or weeks about video content and tutorials and so on. So we're just trying to figure out a way. that's gonna be + +Denis Lelic: some sort of a blueprint for all the future contributions from community members, and I would just like + +Denis Lelic: explaining how to put a video together and have some sort of brand consistency throughout the videos. And one of them is 11 Labs, but their AI voice over then I provided some graphics that are available also in figma community and we were just discussing what kind of software to use to edit the videos one of the options would be canva because it's free for personal use so just basic editing adding a graphic in the front of the video and Probably get to go and the other option would be da Vinci which is kind of a bit more advanced to. But they're offering also. free package for personal usage + +Thomas Greco: so we could talk. I just add to that Denis and you've been a joy to work too. thank you for all the support. You've given me. We could take this async, but I'm also realizing 11 labs. For example, that is a tool that is potentially going to be gated, if we're kind of looking for free resources. and yeah, I'm not sure how far you can get with 11 labs? For free, so just another thing to keep in mind. + +Denis Lelic: Yeah, I think that the Viking remember correctly. They are offering free tokens every month. So the way I dealt with it, I know it's not perfect. But I just signed up through two different emails and I managed to do whatever I had to do in that time period but we should think about + +Denis Lelic: either subscription or I don't know. We'll see when we get there. So yeah that go ahead. + +Zach Horn: There's absolutely no Blocker on cost for this. If you guys need a subscription, we will get it done. Just let me know how much you need. + +Denis Lelic: Thanks Zach. + +Denis Lelic: Okay, so we covered a couple of different things + +Denis Lelic: pretty much everything that's crucial for this week. the analytics Akash accelerate. So if anyone has anything else to add the discussions we have please go ahead. Otherwise we can just meet next week or in two weeks and we can continue this discussions. + +Denis Lelic: Okay, sounds like very good. So, thanks everyone for joining today. I will see each other on Discord or slack whatever we'll see each other online async and thanks again for joining again see each other next meeting. + +Tyler Wright: Thank you. + +Piyush Choudhary: just + +Denis Lelic: Thank you. + +Thomas Greco: Thanks, everyone. + +Zach Horn: Thanks guys. Take care. + +Piyush Choudhary: tonight + +Meeting ended after 00:24:21 👋 + From 333818b92354861bb55f573ad1b866cb254784ad Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 5 Jun 2024 00:20:17 -0400 Subject: [PATCH 065/138] sig-economics Update README.md add meeting details for may and june meetings Signed-off-by: Drinkwater --- sig-economics/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sig-economics/README.md b/sig-economics/README.md index 11ebb393..1f6d5fef 100644 --- a/sig-economics/README.md +++ b/sig-economics/README.md @@ -27,8 +27,8 @@ Meetings happen every [First Wednesday of the Month](https://calendar.google.com | #13| Wednesday, February 07, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/013-2024-02-07.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/013-2024-02-07.md#transcript) | [Link](https://6rzdyy2kxzn4qpilczq7vdvfd52kxb65rk4cnhor32f4cibhkqmq.arweave.net/9HI8Y0q-W8g9CxZh-o6lH3Srh92KuCad0d6LwSAnVBk) | #14| Wednesday, March 06, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/014-2024-03-06.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/014-2024-03-06.md#transcript) | [Link](https://l7relb4v4vhxhw4shqui4iyoyyeqdt6ogwpx2thybmneridemfnq.arweave.net/X-JFh5XlT3PbkjwojiMOxgkBz841n31M-AsaSKBkYVs) | #15| April 3rd, 2024 10:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/015-2024-04-03.md) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/015-2024-04-03.md#transcript) | Coming Soon -| #16| May 1st, 2024 10:00 AM PT (Pacific Time) | | | -| #17| June, 2024 10:00 AM PT (Pacific Time) | | | +| #16| May 1st, 2024 10:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/016-2024-05-01.md) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/016-2024-05-01.md#transcript) |[Link](https://w6djeix4uozea7pt7fdzqmhenlvt6jf72c4x26cz3brkuboazjsa.arweave.net/t4aSIvyjskB98_lHmDDkaus_JL_QuX14WdhiqgXAymQ) +| #17| June 18th, 2024 10:00 AM PT (Pacific Time) | | | | #18| July, 2024 10:00 AM PT (Pacific Time) | | | | #19| August, 2024 10:00 AM PT (Pacific Time) | | | | #20| September, 2024 10:00 AM PT (Pacific Time) | | | From 7f443a3c6237c28661d77ba2ca82dbae94f968db Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 5 Jun 2024 09:09:39 -0400 Subject: [PATCH 066/138] sig-support Update README.md add meeting schedule Signed-off-by: Drinkwater --- sig-support/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-support/README.md b/sig-support/README.md index 467c5586..f85b2466 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -49,7 +49,7 @@ sig-support is responsible for defining mechanics of how support works at Akash | #31 | Wed, April 17, 2024 08:00 AM PT (Pacific Time) | | | | #32 | Wed, May 01, 2024 08:00 AM PT (Pacific Time) | | | | #33 | Wed, May 15, 2024 08:00 AM PT (Pacific Time) | | | -| #34 | Wed, May 29, 2024 08:00 AM PT (Pacific Time) | | | +| #34 | Wed, June 05, 2024 08:00 AM PT (Pacific Time) | | | | #35 | Wed, June 12, 2024 08:00 AM PT (Pacific Time) | | | From fe590736f03954c61092f44b0580005bd2b8c5bc Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 5 Jun 2024 09:27:25 -0400 Subject: [PATCH 067/138] sig-support Update README.md Signed-off-by: Drinkwater --- sig-support/README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/sig-support/README.md b/sig-support/README.md index f85b2466..a7dc5dc9 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -44,11 +44,11 @@ sig-support is responsible for defining mechanics of how support works at Akash | #26 | Wed, January 24, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/026-2024-01-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/026-2024-01-24.md#transcript) |[Link](https://47vntytp4ni2s5p2h2qyh5nuqywowtwne2fx4ddudv7iyl3hu5rq.arweave.net/5-rZ4m_jUal1-j6hg_W0hizrTs0mi34MdB1-jC9np2M) | #27 | Wed, February 21, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/027-2024-02-21.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/027-2024-02-21.md#transcript) |[Link](https://cwya3qcl4ejhb75ct5d4vgcoyhsce46zvv2q42khi6kc76qhsxpq.arweave.net/FbANwEvhEnD_op9HyphOweQic9mtdQ5pR0eUL_oHld8) | #28 | Wed, March 06, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/028-2024-03-06.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/028-2024-03-06.md#transcript) |[Link](https://xut7rmdqwninrlvm75t7cxmmpgrt4tyboramnw3b2rcpaa6gy76a.arweave.net/vSf4sHCzUNiurP9n8V2MeaM-TwF0QMbbYdRE8APGx_w) -| #29 | Wed, March 20, 2024 08:00 AM PT (Pacific Time) | | | -| #30 | Wed, April 30, 2024 08:00 AM PT (Pacific Time) | | | -| #31 | Wed, April 17, 2024 08:00 AM PT (Pacific Time) | | | -| #32 | Wed, May 01, 2024 08:00 AM PT (Pacific Time) | | | -| #33 | Wed, May 15, 2024 08:00 AM PT (Pacific Time) | | | +| #29 | Wed, March 20, 2024 08:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon +| #30 | Wed, April 30, 2024 08:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon +| #31 | Wed, April 17, 2024 08:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon +| #32 | Wed, May 01, 2024 08:00 AM PT (Pacific Time) |[Link](https://www.altcoinbuzz.io/cryptocurrency-news/ionet-airdrops-5-to-strengthen-community/) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/032-2024-05-01.md#transcript) |[Link](https://fp4bufbowjh5thinihsyy52ddcyesjk2yofv4fgjmrhnkahxg5ua.arweave.net/K_gaFC6yT9mdDUHljHdDGLBJJVrDi14UyWRO1QD3N2g) +| #33 | Wed, May 15, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/033-2024-05-15.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/033-2024-05-15.md#transcript) |[Link](https://qc3gxtikakjsqoqohkver467q5u675nuwy7ovtc6j4ajicy7vwna.arweave.net/gLZrzQoCkyg6DjqqSPPfh2nv9bS2PurMXk8AlAsfrZo) | #34 | Wed, June 05, 2024 08:00 AM PT (Pacific Time) | | | | #35 | Wed, June 12, 2024 08:00 AM PT (Pacific Time) | | | From de304469c972e260a6583a55f7043ddb51ebece3 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 6 Jun 2024 08:40:52 -0400 Subject: [PATCH 068/138] steering committee- Create 015-2024-05-02 (#583) * steering commitee- Create 015-2024-05-02.md Signed-off-by: Drinkwater * steering commitee Update 015-2024-05-02.md add recording link Signed-off-by: Drinkwater * Update 015-2024-05-02.md add meeting notes and action items for meeting Signed-off-by: Drinkwater --------- Signed-off-by: Drinkwater --- committee-steering/meetings/015-2024-05-02.md | 450 ++++++++++++++++++ 1 file changed, 450 insertions(+) create mode 100644 committee-steering/meetings/015-2024-05-02.md diff --git a/committee-steering/meetings/015-2024-05-02.md b/committee-steering/meetings/015-2024-05-02.md new file mode 100644 index 00000000..2e91b4c5 --- /dev/null +++ b/committee-steering/meetings/015-2024-05-02.md @@ -0,0 +1,450 @@ + +# Akash Network - Steering Committee - Meeting #14 + +## Agenda + +- Review / discuss / address any community feedback, grievances, or conflicts. +- Review [projects list](../projects-list/README.md), prioritize / add / remove if necessary. +- A look at open discussions in [Github Discussions](https://github.com/orgs/akash-network/discussions). +- Open up to any other questions from the community. + +## Meeting Details + +- Date: Thursday, March 28th, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) +- [Transcript](#transcript) + +## Committee + +- Anil Murty, Overclock Labs +- Artur Troian, Overclock Labs +- Greg Osuri, Overclock Labs +- Scott Caruthers, Overclock Labs + +## Participants + +- Andrew Gnatyuk +- Anil Murty +- Artur Troian +- Cheng Wang +- Deval Patel +- Dimokus +- Henrikas Ragickas +- Jigar Patel +- Joao Luna +- L +- Maxime Beauchamp +- Nick Merrill +- Robert Del Rey +- Scott Carruthers +- SGC | DCnorse +- Tyler Wright +- Zach Horn +- Zeke E + + +# Meeting Notes: + +* Tyler talked about the change in schedule for the Steering Committee over the next months +* Tyler went through the agenda for the meetings. The agenda can be found on the Steering Committee readme. +* Tyler asked if anyone had any issues related to sigs and working groups? Tyler mentioned that Discord events has bugs. The source of truth for all sigs and working groups is on the Akash Website: akash.network/development. +* Tyler moved to the second agenda item for the projects list. +* There are two project boards. One for Community + Marketing and 1 for Product and Engineering. + +### [Product and Engineering Board / Community + Marketing Board](https://github.com/orgs/akash-network/projects) + +* Akash Mainnet 11 Upgrade happened right before the Steering Committee meeting. This has been released and the network is on v0.34.0. Artur discussed issues that we solved with the Mainnet 11 upgrade including improvements to AUTHZ and Private registries for deployments. All documentation is up to date and available at akash.network/docs +* Console is working through a private repos issue on the client, but that should be resolved soon. +* Artur talked about the Cosmos SDK migration. Discussions are ongoing about which version to upgrade to (v47 or v50). +* Tyler mentioned all the work the core product team and core engineering team is doing on adding items to the backlog for the roadmap. There are a number of items that the core team will be working on over the rest of the year. +* Tyler talked about the Praetor team, and the work that they have done since joining the core team. Praetor will be open sourcing their repos, and this will be shared with the community. Deval mentioned that the Praetor team has added issues to the Product and Engineering Roadmap. Deval and Jigar are also working on testing for K3s Provider Build process. +* K3s Provider build testing has been on going with members of the community, Praetor team, as well as the core team. The goal is to greatly improve provider stability and make the provider build process +* SGNorse asked a question. +* Scott talked a little bit about the Provider build process. The provider build process improvements is designed to be significantly easier and faster. This has been used internally to spin up clusters for testing, etc. Historically this took closer to an hour to build a provider. +* Scott mentioned that testing is on going for K3s in multi node environments. This is the last testing. If anyone wants to get involved in testing, please reach out to Scott or Tyler. +* Deeper discussion on these topics happens during sig-provider. +* Cloudmos refactor and rebrand has been ongoing thanks to all the hard work from Max B and Max C. The refactor work is almost done. There will be a larger plan for the rollout. If anyone wants to get involved in early testing, please reach out on Discord. +* Tyler asked if there was anything that the community wants to talk about related to the Product and Engineering Project Board. Milestones are also available for tracking projects on the core product and engineering sides. + + + +#### [Community and Marketing](https://github.com/orgs/akash-network/projects/6): + +* Tyler talked about Akash Accelerate 2024. Livestream and A/V teams have been worked out. Akash Accelerate is May 28th, 2024. Swag is also being ordered. A number of speakers have been confirmed, and updates will be made to the Akash Accelerate 2024. Adam will be organizing watch parties happening around the world. +* Consensus 2024 will be following Akash Accelerate. Designs for booth have been finalized. +* Tyler talked about the Akash Hackathon. May 17th, 2024 is the last day for the Hackathon. Link available here: +* Robert mentioned that there are weekly workshops for the Hackathon. Scott C, Anil, and Secret gave workshops during the Hackathon. There are a couple of more workshops happening. +* Andrew G asked about Dorahacks and their 100% fees. +* Cheng chimed in that fees are used for operating and paying out the prizes for Akash Hackathon. Andrew mentioned that Dorahacks is delegating to jailed validators. Cheng will make sure this gets followed up on. +* Robert talked about Zealy. The 3rd Sprint started. Robert shared some insights about the wg-zealy campaign over the last 3 months. Shared screen starts at ~ 30:00. +* Robert is thinking about ways to retain members after they finish missions. Robert asked for community feedback on how to get users from Zealy to other groups on Akash. + + +### Github Discussions: + +* Tyler talked about Github discussions at a high level. +* Tyler talked about GitHub discussion 562. Anil gave some feedback. This will get added to the Product and Engineering Roadmap. This discussion has been on going in sig-clients, and in multiple GitHub discussions. + +### Action Items: + +* Cheng will follow up on Dorahacks, and how they are staking. +* Cloudmos to Console refactor and rebrand should be live soon. +* Akash Hackathon closes May 17th, 2024. +* Akash Accelerate 2024 is May 28th, 2024 +* Consensus 2024 is May 29th, 2024 - May 31st, 2024. +* Tyler will follow up with details for bug program. +- Tyler led the group through the agenda and asked if anyone had any comments or conerns about the open structure. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the steering committee monthly meeting of today is 2nd. Again. This meeting would normally take place the last week of April but due to just the next couple of months and how busy they are. I moved this meeting to again the beginning of May that we're having right now, and then the next steering committee will be again the first week of June following consensus 2024, which we'll talk a little bit about later. much. Appreciate everybody that's joining us today. And again everybody that's going to be listening in later. I know it's been a very very busy period with a lot going on in the community. + +Tyler Wright: I'm going to get us started with our typical agenda. So again, all steering committee notes transcripts and recordings can be found from previous meetings and read me in the readme table. there is a public Link in the drive that anybody has access to for the most recent. Recording for the last steering committee, but are weave is who we use to manage. These recordings has had a surge in pricing and so we'll have that up very soon. But if anybody needs access in the meantime to the previous recording again, you can access it on the drive or you can reach out to me, but that should be up in the next two days or by Monday the latest. + +Tyler Wright: Again, we have a typical agenda that we go through where we start with reviewing And discussing and addressing any Community feedback. Then we go into reviewing of the Project's list. This is where we look at the community and marketing as well as a product and Engineering roadmaps, which are all again publicly available and GitHub. Following that we look at any GitHub discussions where we focus on discussions that have a lot of comments and we focus on discussions where participants from that discussion are currently here at the meeting. So again, there's a number of criteria for how we determine which discussions we will discuss though. That will be a focus of the steering committee. + +Tyler Wright: So again following that then we open up to any questions. I would ask that we follow that structure because I know a number of folks might have updates or comments concerns. But again, we'll just go through the agenda at the structured and then if anybody has anything they want to discuss we can save that for the end. Anybody wants to drop any additional items that will have during open discussion. Feel free to throw those in the chat and then we'll note them for later. + +Tyler Wright: So to get us started with the typical agenda. I want to review and discuss and address any Community feedback or grievances are conflicts. Does anyone on this call have any issues related to the cigs or working groups or the community in general that they want to discuss? + +Tyler Wright: Boom, I raised my hand for myself. The one thing that I've been looking at over the last couple of weeks is the Discord events. I know that there's been feedback from the community about the Discord events breaking. I do want to make it clear that again the source of Truth for all cigs in working groups is the Akash website on the development section. There is a calendar where you can track all the six and working groups and you can actually add it to your calendar and track these on a weekly or monthly basis one thing that I'm trying to work out is how to improve or how to use a Discord events again, it's very very buggy symptom number of support tickets out to Discord. I know a number of folks in other communities are having going through the same issue. So that's one thing that I'm trying to improve on so that folks clearly are clear about when + +00:05:00 + +Tyler Wright: Meetings are and again are not solely reliant on events. When sometimes it works seamlessly another times. It just seems to break for no reason whatsoever. So if anybody has any comments or feedback, feel free to send that to me. But again, we'll continue to find ways so that it's very very clear on where and when cigs and working group meetings are + +Tyler Wright: Any other discussions or any other feedback around the cigs and working groups that anybody wants to share right now? + +Tyler Wright: + +Tyler Wright: All right, moving along. The next part of the agenda is around reviewing of the projects list you can this is a version that we tracked the previously but if you go to GitHub and then you go to the project section, there are two project boards that are public these get managed and maintained by members of the community and the core team on a daily basis. So again, you can get real-time views as to what's going on in the community both on the engineering and product side as well as a community and marketing anything that again the community is working on or the core team is working on you can track where it is and whether it's in backlog up next or completed. So again, feel free if you have any specific items that you want to discuss between steering committee. So just in the community look at the road Mac and roadmap and feel free to ask questions or + +Artur Troian: All right. Yeah, so we have completed successfully Network upgrade… + +Tyler Wright: feedback I know members of the community team are double booked for today. + +Artur Troian: which stands our house the options For the deployment deposits in the past… + +Tyler Wright: So I'm going to start off with the product and… + +Artur Troian: what was happening that? + +Tyler Wright: Engineering roadmap. + +Tyler Wright: I know one big item that has been worked on was the network upgrade. + +Artur Troian: Whenever deployment is closed,… + +Artur Troian: the Aussie authorization is canceled pretty much and… + +Tyler Wright: That is something that was in testing. + +Artur Troian: that was sort of bottleneck for my use cases and… + +Tyler Wright: And again, as of I believe a couple hours ago. + +Artur Troian: we are able to find a fix it. + +Tyler Wright: There was a successful Network upgrade. + +Artur Troian: So this is live,… + +Tyler Wright: Thank you to all the validators that upgraded the infrastructure. + +Artur Troian: please enjoy using that there was one more feature related to the providers that we now support private registries. + +Tyler Wright: I'll hand it over to Scott or Artur to talk a little bit about where we are here today and… + +Artur Troian: So pretty much… + +Tyler Wright: some of the next steps. + +Artur Troian: if I need deployment needs to access product containers they can do so. + +Tyler Wright: But again that is been moved from testing to release as it is now live and… + +Tyler Wright: we are on version zero Dot 34.1 + +Artur Troian: All of the documentation and… + +Artur Troian: updates to the console as well as how to deploy it using the CLI. I believe available. There is one issue on the console which is a style mentioned is being fixed right now, and we should have these be on the production. Pretty soon like an hour or so. + +Tyler Wright: Thank you very much. another thing that I just want to shout out talking about some of the forward looking work in the backlog section. I know that both the product team and engineering team of developed the roadmap as they think about the rest of the year and amongst those items have started to map out again some of the major projects that folks that both the core team is going to be working on obviously. There's some items that might be broken down into smaller projects and tickets. But again, please feel free to look at this road map and kind of track some of the major items that the core team is thinking about and working on. + +Tyler Wright: One other thing that has happened, I believe since our last steering committee meeting is around open sourcing of prador. I know some of the Prater folks are on the call here today. It's been great to work more closely with them. And I know that they've already started to open source prador again into three repos that you can see and kind of track on the board the ball. I believe you all are on this call. is there anything that you want had is there anything that you want to add again? + +00:10:00 + +Deval Patel: That's out here. + +Tyler Wright: It's been great having you as a part of the core team. And again, the Prater team is actively working on open sourcing again the front back end security So the ball I'll pass it over to you to talk about anything that you're working on. + +Deval Patel: Yeah, so can you hear me? + +Tyler Wright: Yes, we can. + +Deval Patel: Yeah our project consists of three Depots which is security front end and We open source security yesterday. We are going to open source front and back in today or tomorrow for sure. And yeah. + +Tyler Wright: Excellent again, as soon as the open source portion is done and those repos are created then. There will be more projects that will be added to issues. They'll be added as under those Repros that are folks that they'll be working on and folks from the community can also contribute to go ahead Deval. + +Tyler Wright: I think that's a great segue and again appreciate all the work. The Prater team is doing another item that is in testing. But I know that the main debt upgrade has been a high priority is an updated provider Bill process. This is something thats Scott has been working on and has been using members of the community to test this provider build process Deval just alluded to being in lockstep with again the rest of the core team to vet this new provider Bill process. There's a list of items in terms of again. Just betting to make sure it works in all sorts of conditions and edge cases before we take next steps and updating documentation. So if there's anybody out there that is a provider and wants to get involved in again testing some of these new provider build process. + +Tyler Wright: Developed by Scott feel free to drop a note in the sake provider Channel or just providers and again we can go from there. Just saw a message from dcnorse. + +Tyler Wright: Yeah, yeah. So again, these are the kinds of conversations that we will have in sick providers or we can drop specifically in the roadmap. One of the things that I've been urging insiders and everybody in the community community to do is + +Tyler Wright: please participate in conversations. I know I just said this on the Insiders call. So pardon me for repeating myself, but a number of people have very vocal opinions about the Akash Community again, many of those things very positive, but when there's discussions or conversations about pushing the network forward, I would love if people can make those conversations public and respond to discussions. It's a very open Community where people can collaborate and again can take constructive criticism, but it's much better served in a public setting whether it be in Discord or whether it be in GitHub discussions versus me having a translate private messages, so I would urge anybody that's gone opinion about Prater or anything on these road maps to just express it or just get involved in discussions. It goes a long way. + +Tyler Wright: I am Scott. I know we were talking a little bit about the provider build processes or anything that you want to add. I know that you've been pretty heads down this week with mainnet 11 upgrade version anything you want to add about the provider Bill process, which is in testing currently. + +Scott Carruthers: I'm sorry. I'm not sure how cognizant all the members on this call would be to the provider Bill process that were referring to but essentially it's using procedures using k3s and install scripts which literally takes the provider Bill process down to probably about a 10 minute complete build. + +Scott Carruthers: was a + +Scott Carruthers: Maiden invert Don't know. So yeah, as I was saying it literally takes the provider Bill process down to about a 10 minute process. And when I say the provider Bill process that includes persistent storage, it includes if you have nodes with gpus or includes the install of gpus and container runtime environments for gpus and so across all that spectrum is taking it down to a 10 or 15 minute process. So we've been using this six. Considerably internally so during Dev work our term myself and other members of the core team can now spin up. Complete kubernetes clusters and working providers again with all the answer features including IP leases and storage and GPU support in 10 or 15 minutes. So any of those in the audience that are familiar with the + +00:15:00 + +Scott Carruthers: existing Bill processes can imagine the power abandoned spin up a cost providers that quickly so as Deval Mentioned prior I believe that Prater Bill process has been using k3s in production for a cost providers for some time for single node deployment. So all on one scenario where you have collapse control plane and worker nodes and just single provider use but there's been some hesitation and some concern about using k3s and multi-node environments. K3 asses definitely being using more and more Enterprise. Scenarios over the last couple years. I think the prayer team primarily looked at this during their initial development processes a couple years ago. So we're now taking a fresh look at that and as soon as we can have + +Tyler Wright: Does anyone have any questions about provider Bill process or anything pray to a related? + +Tyler Wright: Again, we'll have continued deeper conversation during sick providers. So feel free to join that special interest group or just get involved in Discord between meetings. + +Tyler Wright: I know that members of the Commerce team aren't currently here because again, they're heads down but I do want to shout out the work that the max have been doing in rebranding from cloud most to Akash console again with the max is a part of the overclock core team the cash console will be in the future the pool for folks that want to deploy via you act. So be like again the same experience that folks have been used to with Cloud most but now it'll be open source where there will be ability for more folks to contribute to the growth of console over time. + +Tyler Wright: I know that Rebrand work and refactor work is almost complete where there will be a staging site available for testing starting next week. And then there will be a larger plan as it pertains to the rollout for the console again deployed tool over the next couple weeks. So look out there if anybody wants to get involved in early testing again, feel free to reach out to myself for the Max's and we can get you involved in that when available, but I do want to shout out all the work that the Max has been doing and getting console ready. + +Tyler Wright: Cool again, we can talk about a number of things that are currently in progress that are being worked on by the core team as well as items being worked on by the community, but with the maintenance upgrade happening today, I know that there has been just a lot going on. Is there anything on this board specifically that anybody wants to talk about in more detail today? + +00:20:00 + +Tyler Wright: One other thing you can look at is again inside some of these items and up next and backlog. You can also track Milestones again, especially on the engineering side and there will be more items coming across different repos being added to this product and Engineering roadmap so much appreciate all the work led by again Anil and Archer in this transparency and all the work that's being released. shout out to their leadership and just the community as a whole for all the work that they do. + +Tyler Wright: All right, moving along again product and Engineering grow back has been covered the community. + +Tyler Wright: And marketing initiatives up. I know that there are another number of initiatives that are being worked on right now with again around events. So there's a Kosh accelerate 2024. This gets updated in pretty frequently by Amanda as pertains to all that's going on. I believe that they're in meetings right now. But as of recently and anybody here from the marketing side can correct me if I'm wrong but live stream and audio visual team has been worked out. So again as Adam prepares for some watch parties that will be having around Akash accelerate. There's been serious discussions and follow up that live stream is going to be working and there will be Again Video available following the one day conference swag is in the process of being ordered for the event. So again people that participate live + +Tyler Wright: Or come to the event live we'll be able to leave with branded Akash Network items that they can wear for the rest of the conference and just wearing their General lives. And there's a number of other items for again speakers are being organized and believe there's a speakers will be updated soon. There's been at least five or six confirmed in a number of people have filled out the speaker application looking to speak at our cost accelerate. So again, there's just so much going on a cost accelerator. I do want to shout out all the work that Amanda Adam the marketing folks as well as the partner that we're using for event management is doing as we prep for Kash accelerate. It's gonna be exciting Day on May 28th again, there will be some more updates on in terms of watch parties if you can't be there live or if you can be there live again, there's links available to register for the event. + +Tyler Wright: Both on the back of Akash accelerate will be consensus 2024 which as of recently again, a cash network will have a at Booth design has been finalized. Shout out to Sig design and Dennis for all the work that it had done there and Zach as well for the messaging components and just general marketing leadership. So again consensus will be following Akash accelerated. I believe the 29th through the 31st. Robert if you're talking you might be on mute. + +00:25:00 + +Robert Del Rey: Thank you so much that I always happens. + +Tyler Wright: Hence why the next steering committee will be moved back a week. + +Robert Del Rey: Yeah about the hackathon real quickly. + +Tyler Wright: But again as updates become available and + +Robert Del Rey: We also have in weekly workshops. Some insiders have helped us and… + +Tyler Wright: as things continue to get paid out there will be sheets available to the community to try to track against again the community pool spend for consensus 2024 as well as Akash. + +Robert Del Rey: and yeah, it's got thank you so much. We had Anil last week. We had secret Network talking about their sponsor track today. And next week,… + +Tyler Wright: Accelerate 2024. + +Robert Del Rey: we're gonna have two workshops. + +Tyler Wright: There anything I'm missing out on or… + +Robert Del Rey: So once happening on Wednesday in charge damir chimpa,… + +Tyler Wright: does anyone have any questions on consensus 2024 or classic accelerator 2024 before I continue on with some of these other items on the board. + +Robert Del Rey: Europe plots is in charge of that one. In the next one is on Thursday. So I just wanted to remind that. Yeah. + +Tyler Wright: Thank you Again more updates will I'm sure be happening around the hackathon as we approach the deadline for the end May 17th. So look out for more announcements from Adam and the hackathon team. Go ahead Andrew. Cool. All… + +Tyler Wright: + +Andrew Gnatyuk: Yeah. Hi guys. + +Tyler Wright: I know the hackathon is next up. + +Andrew Gnatyuk: I'm sorry I missed yesterday's economical. + +Tyler Wright: The hackathon has been running I believe for a little bit under a month. + +Andrew Gnatyuk: I wanted to ask this question before. Yeah. Thanks Cheng. + +Tyler Wright: I'll attach a link here. But the May 17th is the last day for the hackathon. + +Andrew Gnatyuk: Just a question about it's not about the door hacks,… + +Tyler Wright: I know a number of folks have reached out to me privately saying they were going to participate in the hackathon. + +Andrew Gnatyuk: but probably about the dura hacks. So I've noticed they had a note on X validator right and… + +Tyler Wright: So again it's getting down to the time of submitting or making your submissions for the hackathon. + +Andrew Gnatyuk: they have a hundred percent fees. + +Tyler Wright: Please follow the Adora hacks to submit… + +Andrew Gnatyuk: My question is this on the time of a hackathon or… + +Tyler Wright: if you see anybody in the community. And again, there's an entire section in Discord for the hackathon with teams that are being put together a projects that are being worked on. + +Andrew Gnatyuk: is this or you can fill me up on this? why do they have 100% fees? + +Cheng Wang: Yeah, I can jump in there for that Andrew. + +Tyler Wright: So again, feel free to get involved in the hackathon believed again,… + +Cheng Wang: It's a good question. Yeah, the door hacks validator specifically is on 100% fees… + +Tyler Wright: there's about 15 days left. + +Cheng Wang: because the fees are used to pay for their service essentially. + +Tyler Wright: So time is winding down to participate in the hackathon with over 200,000 prizes in UST given out an akt Of again,… + +Cheng Wang: And yeah, so the service as well as the bounties that are given out to just all the hack on winners so that … + +Tyler Wright: please feel free to get involved. + +Cheng Wang: essentially the proceeds and… + +Tyler Wright: Does anybody want to talk about the hackathon or… + +Cheng Wang: commissions other that they would collect go to operating running, … + +Tyler Wright: did anyone have any questions about the hackathon before we continue onward? + +Cheng Wang: their entire apparatus in addition to the winnings the prizes that get old out. + +Andrew Gnatyuk: So the purpose included in those piece, right? + +Tyler Wright: Go ahead Robert. + +Cheng Wang: That's right. Everything prizes as well as just kind of running their operations. the cost it takes to run the operation. Yeah. + +Andrew Gnatyuk: It got it. Okay. Thanks. Thanks. + +Tyler Wright: No, appreciate that question And again, that's certainly something that's being monitored front of mine. But it's Cheng mentioned. Yeah, all everything in terms of rewards and all that kind of stuff comes from those 100% fees. cool Go ahead Andrew. + +Cheng Wang: If there's any jail that it should be definitely cleaned up. + +Tyler Wright: Thank you, Andrew. I'll follow up with you offline about that. + +Tyler Wright: cool Robert I know that you wanted to spend a little bit of time giving an update on zealy. So I will hand it back to you to talk about the developer onboarding programs Robert love to hear an update. + +Robert Del Rey: Cured that are and be super happy to give you guys a quick update about the developer onboarding campaign on Sealy yesterday a sprint number three started. This is the third and last spring of this campaign as we requested in the proposal and yeah, I just wanted to show you some quick as stats let you know about the New Missions offerings and what's gonna happen next we're gonna continue or we're gonna disregard this all together. So we're gonna find out if you don't mind I will go ahead and share my screen real quick. + +00:30:00 + +Tyler Wright: Of course. + +Robert Del Rey: Yes, it's just if you don't mind, thanks, one sec. Okay, let me know if you can see it. Awesome. So let's start with the stats. + +Tyler Wright: Yes, we can. + +Robert Del Rey: This is the last three months. I will start saying that we have learned. A lot about Seeley about the community about the submissions and specially Seeley these tool. So the first thing I want you to see is that in the last three months we have been able to onboard. Are 211 new members that does an account the members that came from the first pilot that we did on December and November December. So yeah, the first two sprints we have. + +Robert Del Rey: 211 members so far you can see here on top. these are the quest that people have claim. Some of them are paid. Some of them are on paid so Just wanted to let you know that here in this graphic. You can see the amount of members. We got over time the highest Bull Run. I don't know how to say it was when we started the first Sprint on March. We got a hundred members right away and then slowly but surely we've been able to keep growing I just wanted to share Yeah, we're gonna continue. This is the third month. but what I wanted to share here with you guys is + +Robert Del Rey: not issues, but some challenges that Benji and I are facing and hopefully you can let us know your feedback or what you think about this. So the first one is The retention of the members. over 200 people 300 members sounds really cool. But how we retain those members. It's the question that's on my mind almost every day. I catch up on this course I send messages. + +Robert Del Rey: Sometimes some Twitter Sometimes some Thank you Andrew for your support on Telegram. but Initially, I thought it was gonna be a little bit easier to redirect good talent from here to other groups in a cash. So if you have an idea or maybe some cool Dynamic that we can do to recruit people from Seeley and make sure they do other things on a cash. Let me know some missions we have done are about being a provider on a loy persistent storage on a cache. + +Robert Del Rey: And some other missions those two are paid but that I'm gonna mention now are not paid. One is about making people go to GitHub and open up a discussion. that mission it's on paid, but we just want to Teach people. How is the process whether it's a listing proposal or just a marketing collaboration? There is a process that needs to be followed. So we made that mission about taking it to GitHub. That's the name of the mission. I miss if I can show you to your real quick. That's one. + +Robert Del Rey: It's Another one that it's on paid. It's the Akash Bounty space. We have a channel on this core which is been Super Active. That's amazing. But Benji and I decided to do this as a mission so people can go into here. And see a little context why we're doing this and where they need to go to make this happen. This The one for the bounties is here. Did you say I can't bounties? So yeah people can go here click on the link and see what is in it for them through silly because I know that I noticed that there are some people that are members on Sealy. + +Robert Del Rey: But they're not very active on this core so they might not see when we post something on a cache Discord that is unrelated to silly so through City. They can see more things in case they are not on Discord. I've seen some members that ask question and they're super new they started animation and then they join a cash GitHub. then they join a cache the score to ask their questions. something to think about the last of the missions that is on paid. I believe Zach is gonna like this one. It's Join, the newsletter subscriber here is the type of form for a cash. So if people want to subscribe to the newsletter + +00:35:00 + +Robert Del Rey: They can do it from here. They click on that and Seeley lets me know if people do it and I believe Zach can see if people sign up to that newsletter. These three missions are on paid and we believe it's gonna bring some. + +Robert Del Rey: Different flavors, I guess because we only had paid missions in the past. So during the first month we had lots of tractions because we had more missions but on the second month, we had lower engagement I believe because we try to do harder missions and people were expecting easier missions. So we didn't get much engagement on month number two. So on month number three, we're kind of doing a combination between harder missions and on paid missions. So, let's see how that goes. So, yeah. you saw that you saw the stats then analytics My concern is about retention I know and I already told you about what we're gonna do next. + +Robert Del Rey: In regards on this current campaign if we're gonna continue or not. I'm waiting on till these Sprint ends and Banking and I are gonna have a talk and we're gonna decide if we're gonna continue In the meantime, I'm already speaking with the guys from Galaxy Galaxy. It's another tools similar to silly. However, they're offering is a bit more robust. They offer more ways to create missions and their analytics. Also it's ghosts deeper. This is what I have besides this. I have the missions that people do and the countries where people are coming from which is it's okay, but I wanted more information. + +Robert Del Rey: so yeah, let's see what galaxy offers and in any case what we do anything we're gonna open up a discussion on GitHub and we're gonna share the links and hopefully you can guys join the discussion and let us know what you think. So maybe I said more that I thought I was gonna set but let me know you have any questions concerned regrets or any comments. Overall. You want to share with me? + +Tyler Wright: Thank you, Robert. All Right Moving On + +Tyler Wright: Is there anything else on the community and marketing initiatives that anybody wants to discuss? + +Tyler Wright: They're actually two things. I'll move these up. There was some planning issue yesterday, but around proposal 242 creating an automated auditor with open source. I know that the pi 3 team led by Benji has been working on this they gave an update an hour ago. And I think we'll reschedule a meeting for next week where they can demo. So again, feel free to track what's going on there. And then I know that joao Luna just joined the call Luna discussion a little bit about donating the terraform provider to the cost Network, which will include a transfer of ownership to the Akash Network organization so much appreciate Luna for that. We'll have a discussion at the main upgrade happens where again a member of the core team. We'll just connect with Luna to transfer some keys. But again, + +Tyler Wright: Much appreciate Luna for doing that and I'll add that to the board that's tracked in the community issues. I'll make sure it gets added to the sports of folks can track it. But is there anything else on this board in progress up next or otherwise anybody wants to talk about right now? + +Tyler Wright: We'll do. I saw your message. I'll move it to the product board. + +00:40:00 + +Tyler Wright: All right, if there's nothing else on the projects list, then we can continue on with The next part of the agenda is around discussions. + +Tyler Wright: So again, the GitHub discussions is a place where folks can suggest ideas to talk about things that they want. + +Tyler Wright: Potentially community pool funding for that they want to put on up for a governance proposal or again just general conversations. So what we try to do is we try to gauge discussions that we'll talk about during steering committee around those that are here and those discussions that are getting a lot of traction. I would ask again that anybody that has any thoughts or concerns or questions about any of these items can leave comments in the discussion can upvote but just get involved so that again as we head towards the steering committee's or as we're tracking these things add them to potential roadmap. We're getting Community feedback and Community thought so that would be terrific. I saw that + +Tyler Wright: There was potentially a couple of discussions I wanted to talk about today. I know that there was a member. From the doubtout team that joins Sig economics yesterday and gave a really good update on all the work that they're doing over at Dao down how they would like to work more closely with the cash. He started General discussion with no necessarily called action, but just again discussion for people to get involved in in terms of about down just potential opportunities. So feel free to get involved in that discussion. I know he was here at the beginning in the meeting has been getting more involved in six and working groups. So again, please feel free to get involved in that discussion. + +Tyler Wright: Another discussion that I will just talk about real quick is I know that piyush and the human HQ team have been working with the netted out team to develop a streamline and more automated pipeline for deploying applications and they want to do this on cloudmose or console. + +Tyler Wright: This is something that they've been working very closely with the Anil and the Max's on they have recently dropped in a link to a PR that they've dropped into and they shared that did a demo at the most recent sick client that has something that's going to be added to awesome Akash that makes it easier for people to doctorize and maintain images that's phase one at this plan. I would ask that anybody at once that gets merged. I asked that folks from the community start to mess around with where they see anybody in the community that is looking to deploy on Akash, but doesn't understand the containerization or the docker piece. They can point them in a direction of that sdl and get folks and from the community interacting with it and then getting them involved in this discussion. + +Tyler Wright: but is there anything that you want to add there? I know we're just talking about this and I'll make sure that gets added to the product and Engineering roadmap as well. + +Tyler Wright: oops + +00:45:00 + +Tyler Wright: Perfect. Thank you very much Anil. + +Tyler Wright: I want to make sure again we take time for any discussions that have happened since the last meeting that again are getting a lot of attention. Is there anybody here that wants it to talk about a discussion that they brought forth and they want to hear from the steering committee on + +Tyler Wright: All right. If not, then again, I'll continue to ask people on this call and people listen to this recording later to get involved in these discussions again make your voice heard of something doesn't make sense. That's all right to say that as well because it doesn't push forward the goals of again the cash network. But again, please please feel free to get involved. Especially if you have strong views on any of these items. + +Tyler Wright: Cool, if there's no further discussion that anybody wants to have around any of the open discussions, then we can move on to the last part of the agenda around which is an open discussion. Is there anything that anybody wants to talk about and in front of the steering committee right now or in front of the community? + +Tyler Wright: It's a good question. I know that we have a semi-formal program. I can follow up Andrew with details offline in terms of operational plan for… + +Tyler Wright: Again, I know there's been a lot going on this week with the provider upgrades as well so much appreciated again everybody in the community for staying involved in discussions for being attentive up for updating and… + +Tyler Wright: where you push people what we've historically have had to do is when somebody submits a bug we will have to bet it and in many more cases than not the thing that they are proposing is not actually a bug… + +Tyler Wright: upgrading their nodes and… + +Tyler Wright: but again,… + +Tyler Wright: their again,… + +Tyler Wright: I will follow up with a operational procedure over the next 24 hours so that we can at least push people in a Direction. + +Tyler Wright: they're providers if they have them. Please feel free to stay in tune between meetings by looking at the various roadmaps leaving questions comments Etc,… + +Andrew Gnatyuk: Yep. Thanks. + +Tyler Wright: please if anybody wants to get more involved in the core code base, there's a six support weekly that happens where again members of the core team triage any issues of waiting triage and then we discuss any open support tickets. So if you have questions about an open issue, or if you want to get involved involving an open issue, feel free Andrew. I see your hand up. So feel free to speak. Awesome, are there any other questions or discussions that anybody wants to talk about related to Akash at this time? + +Tyler Wright: again, please feel free to get involved in some of the working groups some of the special interest groups happening over the next month again. Look out in Discord and Elsewhere for more announcements related to the network provider upgrade and next steps there again, appreciate all the work from members of the core team validators providers everybody in the community for continuing to stay in sync and again continuing to work together. So got people representing and passionate about a cost on all continents all over the world. And so it's great to see again folks stay connected and Akash continuing to grow. So appreciate everybody's time and energy today again. I'll follow up with notes trance the transcript and the recording a very soon and draw a follow up with you on that operational plan for those that + +Andrew Gnatyuk: Thanks guys. + +Tyler Wright: Say they have bugs and… + +Andrew Gnatyuk: Bye. Have a nice day. + +Tyler Wright: then we'll just continue to stay connected between meetings. + +Cheng Wang: Thank everyone. Thanks. + +Robert Del Rey: Thanks guys. Stay safe everybody. Bye. + +Tyler Wright: And again, feel free to look at their network website under the development tab in the calendar to stay up to date on all cigs and working group meetings, and please feel free to join. Can I hope everyone has a great rest of their day? Thank you to all that gave updates today and will continue to stay linked up on Discord Telegram and elsewhere but much appreciate everybody. Hope everyone has a great rest of the day. + +Meeting ended after 00:51:21 👋 + + From f7ffbc392eda20be8b69daec91df4687d60e9a29 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 6 Jun 2024 08:49:00 -0400 Subject: [PATCH 069/138] steering committee Update 015-2024-05-02.md updated the meeting number Signed-off-by: Drinkwater --- committee-steering/meetings/015-2024-05-02.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/meetings/015-2024-05-02.md b/committee-steering/meetings/015-2024-05-02.md index 2e91b4c5..c930b276 100644 --- a/committee-steering/meetings/015-2024-05-02.md +++ b/committee-steering/meetings/015-2024-05-02.md @@ -1,5 +1,5 @@ -# Akash Network - Steering Committee - Meeting #14 +# Akash Network - Steering Committee - Meeting #15 ## Agenda From 7b2af29a8f35e89877c1b1f7d802f8a77b7475c0 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 6 Jun 2024 08:49:29 -0400 Subject: [PATCH 070/138] steering committee Update README.md update readme table Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index 9c97b688..01e570af 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -28,7 +28,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, January 25, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md#transcript) |[Link](https://uh4qrdp5wsvzihnnh7m7conzwkllrei4xawnfsohgjmp5qpjberq.arweave.net/ofkIjf20q5QdrT_Z8Tm5spa4kRy4LNLJxzJY_sHpCSM) | Thursday, March 7th, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md#transcript) |[Link](https://aqjulyegruxs4xdwltfkkxqieagkmqc7dcbewovdw2wk7tj72hka.arweave.net/BBNF4IaNLy5cdlzKpV4IIAymQF8Ygks6o7asr80_0dQ) | Thursday, March 28, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md#transcript)|[Link](https://4wprt5kys3oxjr7ihtu2jgx6mshwts7gzsiv2pfr4qypgrp2xywa.arweave.net/5Z8Z9ViW3XTH6DzppJr-ZI9py-bMkV08seQw80X6viw) -| Thursday, May 02, 2024 11:00 AM PT (Pacific Time) | Coming Soon |Coming Soon |[Link](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) +| Thursday, May 02, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md#transcript) |[Link](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) | Thursday, June 06, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, July 25, 2024 11:00 AM PT (Pacific Time) | | | From 53bd1d11d66395f37d0c44bd18f69f584b958dc9 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 6 Jun 2024 08:51:16 -0400 Subject: [PATCH 071/138] sig-support Update README.md update links for meeting table Signed-off-by: Drinkwater --- sig-support/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-support/README.md b/sig-support/README.md index a7dc5dc9..1e5422b1 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -47,7 +47,7 @@ sig-support is responsible for defining mechanics of how support works at Akash | #29 | Wed, March 20, 2024 08:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon | #30 | Wed, April 30, 2024 08:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon | #31 | Wed, April 17, 2024 08:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon -| #32 | Wed, May 01, 2024 08:00 AM PT (Pacific Time) |[Link](https://www.altcoinbuzz.io/cryptocurrency-news/ionet-airdrops-5-to-strengthen-community/) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/032-2024-05-01.md#transcript) |[Link](https://fp4bufbowjh5thinihsyy52ddcyesjk2yofv4fgjmrhnkahxg5ua.arweave.net/K_gaFC6yT9mdDUHljHdDGLBJJVrDi14UyWRO1QD3N2g) +| #32 | Wed, May 01, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/032-2024-05-01.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/032-2024-05-01.md#transcript) |[Link](https://fp4bufbowjh5thinihsyy52ddcyesjk2yofv4fgjmrhnkahxg5ua.arweave.net/K_gaFC6yT9mdDUHljHdDGLBJJVrDi14UyWRO1QD3N2g) | #33 | Wed, May 15, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/033-2024-05-15.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/033-2024-05-15.md#transcript) |[Link](https://qc3gxtikakjsqoqohkver467q5u675nuwy7ovtc6j4ajicy7vwna.arweave.net/gLZrzQoCkyg6DjqqSPPfh2nv9bS2PurMXk8AlAsfrZo) | #34 | Wed, June 05, 2024 08:00 AM PT (Pacific Time) | | | | #35 | Wed, June 12, 2024 08:00 AM PT (Pacific Time) | | | From c3dfd281bb5b7d93254536c53fc704ddaa15bd7d Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 13 Jun 2024 12:00:58 -0400 Subject: [PATCH 072/138] wg-provider-audits Update README.md update the meeting table. Signed-off-by: Drinkwater --- wg-provider-audit/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/wg-provider-audit/README.md b/wg-provider-audit/README.md index 74f68390..a2389f54 100644 --- a/wg-provider-audit/README.md +++ b/wg-provider-audit/README.md @@ -15,8 +15,8 @@ This working group is for developing an open source auditor tool for providers. | Meeting | Time | Notes | Transcript | Recording | --- | --- | --- | --- | --- | | #1 | Wed, Feb 21, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/wg-provider-audit/001-2024-02-21.md) | [Link](https://github.com/akash-network/community/blob/main/wg-provider-audit/001-2024-02-21.md#transcript) | Coming Soon -| #2 | Wed, May 1st, 2024 09:00 AM PT (Pacific Time) | | | -| #3 | Wed, June 19, 2024 10:00 AM PT (Pacific Time) | | | +| #2 | Wed, May 1st, 2024 09:00 AM PT (Pacific Time) | No meeting | No meeting | No Meeting +| #3 | Thursday, June 13, 2024 10:00 AM PT (Pacific Time) | | | | #4 | Wed, July 17, 2024 10:00 AM PT (Pacific Time) | | | From 8451630759d05c2bb0ae1766e29f84ffbecccaf1 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 18 Jun 2024 14:00:13 +0000 Subject: [PATCH 073/138] Create meeting notes for sig-clients #14 (#600) * Create meeting notes for sig-clients #14 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 014-2024-03-27.md add transcript to the meeting notes Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-clients/meetings/014-2024-03-27.md | 531 +++++++++++++++++++++++++ 1 file changed, 531 insertions(+) create mode 100644 sig-clients/meetings/014-2024-03-27.md diff --git a/sig-clients/meetings/014-2024-03-27.md b/sig-clients/meetings/014-2024-03-27.md new file mode 100644 index 00000000..5603cdd6 --- /dev/null +++ b/sig-clients/meetings/014-2024-03-27.md @@ -0,0 +1,531 @@ +# Akash Network - Clients Special Interest Group (SIG) - Meeting #14 + +## Agenda +- Updates from the Cloudmos team, represented by Maxime Beauchamp. +- Discussion on Terraform provider by Joao Luna +- Demos from teams collaborating with the Neta DAO team and Piyush Choudhary. +- Demo by Lukas Meilhammer on his current ideas. + +## Meeting Details +- Date: Wednesday, March 27, 2024 +- Time: 08:30 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + +## Participants +- Anil Murty +- B S +- Cheng Wang +- Envy | Neta DAO +- Fire:ies.ai Notetaker Nicolas +- Joao Luna +- Lukas Meilhammer +- Massv +- Maury De Jesus +- Maxime Beauchamp +- Piyush Choudhary +- Scott Carruthers +- Tyler Wright +- Zach Horn + +## Meetings notes +- **Tyler Wright** + - Welcomed participants to the March 2024 SIG (Special Interest Group) for clients. + - Noted the focus of the SIG on tools built on top of Akash to aid client-facing projects. + - Mentioned a busy agenda with updates from various teams building on Akash. + - Tyler Wright emphasized the importance of active participation and feedback during the demos. + - Noted the lack of traction on Piyush's LLM tool demo from the last meeting, suggesting community disinterest might indicate the project’s limited potential to grow the Akash Network. + - Encouraged attendees to provide feedback to help guide next steps for the presented ideas. + +- **Maxime Beauchamp (Cloudmos Team)** + - Provided a brief update on ongoing projects: + - Working on the GPU endpoint for the pricing page, coming online soon. + - Refactoring the ELBs (Elastic Load Balancers) in the Akash Console. + - Implementing provider monitoring for the new Provider Discovery endpoint, currently rolling out. + - Confirmed recent updates: + - New feature: Deployment details now show the GPU model being leased, improving GPU visibility. + +- **Q&A Session on Cloudmos Team Update** + - Tyler Wright invited questions or thoughts on Cloudmos updates from the participants before moving on with the agenda. + - Acknowledged the busy schedule of the Cloudmos team and their recent accomplishments. + - Encouraged participants to track Cloudmos updates via the project roadmap and engage with the team on Discord. + - Mentioned the regular participation of teams building on Akash. + - Noted a missing presenter but decided to continue with the agenda. + - Introduced Joao Luna to discuss making the Terraform provider more accessible. + +- **Joao Luna (Terraform Provider Update)** + - Provided background on the Terraform provider, developed about a year and a half ago. + - Explained that the provider is stable but underdeveloped, currently using the Akash binary. + - Initiated a discussion to open source components developed at Quasarch. + - Proposed moving the Terraform provider from his profile to the Akash Network organization to improve discoverability and trust. + - Planned to publish the provider to the official Terraform registry under the Akash Network. + - Detailed the next steps, including the open-sourcing of client libraries and improvements to the Terraform provider. + - Emphasized the need for secure generation and configuration of a GPG key by someone from Overclock Labs. + - Offered to assist with the process but stressed security concerns. + +- **Tyler Wright** + - Thanked Luna and opened the floor for questions. + - No questions were raised, so Tyler agreed to coordinate a meeting between Luna and the appropriate person from the core team to handle the GPG key setup. + - Confirmed the transfer process should take one to two days. + - Highlighted the importance of security to prevent malicious access. + - Proceeded with the agenda, noting two scheduled demos from present participants. + +### Piyush Choudhary (Neta DAO Project Demo) + - Introduced himself and the project aimed at reducing friction in onboarding developers to the Akash Network. + - Identified the pain points in the current process of deploying GitHub repositories to Akash. + - Proposed a streamlined process, similar to Vercel, to deploy applications from GitHub to Akash without manual Docker and SDL file creation. + - Showcased a POC (proof of concept) that automates deployment scripts. + - Emphasized that the solution will support multiple languages and frameworks, not limited to JavaScript. + - Demonstrated the automated deployment script detecting changes in the repository and redeploying without manual intervention. + - Mentioned ongoing discussions and proposals for this concept. + +#### Q&A Session on Piyush Demo +- Anil Commented on private repo support being code complete and asked about Piyush's webhooks depending on container image tags. +- Joao Luna asked if the deployed image actively monitors the repository for changes. +- Joao Luna Piyush confirmed that the image checks for updates every five minutes, with plans to use GitHub APIs for real-time updates. +- Scott Sought clarification on the goal of Piyush's solution: +- Whether it eliminates the need to customize an SDL. +- Whether users need to be knowledgeable about SDL as part of the deployment process. +- Scott confirmed understanding of the Docker file automation. +- Scott inquired if the solution also removes the need for manual SDL customization. +- Scott Suggested a feature to auto-populate SDL with appropriate resource settings for AI models, reducing cognitive load on users. +##### Piyush Choudhary: +- Clarified that the solution does not depend on version tags in the SDL. +- Explained that the environment builds are managed by background scripts that handle framework detection and deployment commands. +- Explained the solution's goal to simplify deploying applications from GitHub to Akash: +- Eliminates the need to create Docker files manually. +- The solution manages the deployment process and updates. +- A GUI will allow users to log in with GitHub, select repositories, and deploy without creating an SDL manually. +- Users can see a preview of the SDL, but it is auto-generated based on the repository and environment variables. + +#### Demo by Lukas Meilhammer +- Noted that there were 22 minutes left and handed the floor to Lukas and Maury. +- Mentioned that Lukas's team had been active on Discord, addressing technical challenges while deploying on Akash. +- Lukas introduced their project, a data and knowledge marketplace allowing users to monetize or control access to their data. +- Lukas highlighted key features such as private or public databases, token-based access, and infrastructure for reward distribution. +- Explained the integration with decentralized cloud services like Store J. +- Presented a demo of the platform, emphasizing the user interface for database management and access control. + +**Integration with Akash** +##### Lukas Meilhammer: +- Tyler requested clarification on how Akash is being utilized in their deployment, focusing on practical implementation and related issues. +- Described their current deployment architecture, with different providers handling different components: + - Frontend on one provider. + - S3 storage gateway on another. + - Backend and database on a third provider. +- Mentioned challenges with Docker images and potential solutions. +- Expressed interest in integrating solutions discussed earlier in the meeting to streamline their deployment process. +- Invited feedback from the community and highlighted the need for deployment best practices and clearer roadmaps to reduce friction and redundancy in resolving issues. +#### Maury De Jesus: +- Added details about the current deployment status on Akash: + - Entire platform is running on Akash. + - Database is stored on Store J. + - Frontend, backend, and S3 gateway are integrated with the Akash network. +- Opened the floor for questions. + +**Questions and Discussions on Lukas Demo** +- Anil Murty asked about specific issues faced during deployment and how they were addressed. +- Scott Inquired about the user experience for managing databases on the platform and how Akash improves this process. +- Piyush Choudhary asked about backing up deployments that go down by the providers. +##### Lukas Meilhammer: +- Elaborated on deployment challenges: + - Inconsistent performance across different providers. + - Difficulties with Docker image management and redeployment. +- Acknowledged that the solutions discussed by Piyush might help address these issues. +- Emphasized the need for an API to streamline deployment and update processes. +- Explained that Akash provides a decentralized, scalable infrastructure for their platform, enhancing data security and availability. +- Mentioned that using Akash eliminates reliance on a single cloud provider, thus reducing risks and improving uptime +- Acknowledged the need for regular backups. +- Mentioned they have POC clients and partners looking to launch or update data. +- Expressed willingness to schedule calls for further discussion and technical collaboration. +**Next Steps:** +- Lukas and Maury's team to explore integrating solutions presented by Piyush to enhance their deployment process. +- Community members to provide feedback and suggestions for best practices in deploying on Akash. +- Continued discussions on Discord to address challenges and share updates. +- Tyler highlighted the availability of a private Discord channel for technical discussions with Lukas and the team. + +### Backup and Data Management Discussion +#### Piyush Choudhary: +Asked about solutions for backing up data and whether Lukas' team has implemented any backup routines. +#### Lukas Meilhammer: +- Mentioned ongoing efforts to identify errors and the absence of a backup routine earlier. +- Invited collaboration and technical discussions to expedite solutions. +#### Anil Murty: +- Clarified that the front end and backend are running on Akash, while data is stored on Storj. +- Emphasized the need for regular data backups since persistent storage on Akash does not automatically backup data. +- Suggested implementing a backup solution on their side. +- Emphasized the importance of backing up data from persistent storage on Akash. +- Suggested regular backups to Storj or another solution. +- Offered to connect Lukas with reliable providers on Akash for further discussion. + +## Action Items +- Tyler Wright to set up a conversation between Joao Luna and the appropriate person from the core team for secure GPG key handling. +- Follow-up discussions between Piyush Choudhary and Anil Murty on private repository deployments. +- Lukas Meilhammer and Maury De Jesus to potentially collaborate with Piyush Choudhary on deployment automation and best practices. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: A Wright welcome everybody to the March 2020 for addition of big clients. This special interest group for clients is focus on all things related to those that are building clients facing tools on top of Akash. I know there are a number of projects that are being built on top of clients to make it easy for people to use a cash and so again, That allows people added to their workflow. so much appreciated everyone's participation and constant participation during this sig. + +Tyler Wright: There is a pretty good size agenda happening for today. So just out of the last meeting usually during these Sig clients meetings. We get updates from various teams that are currently building on top of Akash. We can update from the cloud most team take Max is here representing that team on all the stuff that they've been doing. Following that update. I know that Luna has been working on terraform provider and put a discussion number 502 which I'll drop in the chat. + +Tyler Wright: To make that more accessibly open source, and so we'll talk a little bit about that. Following that conversation there are a couple of teams that I've asked to join this call to give short demos on ideas that they've been thinking about inclusive Concepts that they've been working on one. Those teams is part of the Dao team working together with piyush and so they have an idea to go again give a high level demo on and talk about and then Lukas who's also the call has been working on some ideas and so he will give a demo as well. So again out of the last + +Tyler Wright: Said clients' meeting. There was a demo given by a Pearson is his team related to an llm tool. There was not much traction on that discussion afterward. So we're hoping that people on this call can participate actively it does not much attraction on idea. I had to imagine that means that it's something that should not be pushed forward because the community doesn't see much need for its Late as it stands to grow the Akash Network. So again the folks that are participating and sharing some of those ideas later today in the agenda are certainly looking for feedback to take necessary next steps. So just want to throw that out there. + +Tyler Wright: So kicking off the agenda. I'll hand it over to Max who will give us some updates from the cloud most team so max feel free to take it away. + +Maxime Beauchamp: It's gonna be a brief update. We are working on a lot of stuff currently. But yeah, we'll be working on the GPU endpoint for the pricing page which will be coming online soon. We are. Continuing our work to refactor the elbows deeply into the cash console. Which will also come in the coming weeks and + +Maxime Beauchamp: a bunch of stuff for provider monitoring for the new provider Discovery endpoint, which is a rolling out as we speak. So yeah. That's pretty much it. + +Tyler Wright: Over the last month as well Max. I know they caught up in the thick of all I think they're working on right now. But over the last month you all have had a couple of new items in terms of how people could view gpus on the clubhouse web app that correct. + +Maxime Beauchamp: Yeah, we released on the deployment detail you can see which GPU model you are currently leasing, which was not possible. previously So, yeah, it's a big Improvement for GPU visibility. + +Maxime Beauchamp: Thanks for the reminder. + +Tyler Wright: + +Maxime Beauchamp: Probably something else that I forgot about just the rush right now. + +00:05:00 + +Tyler Wright: yeah, no, no worries. Again, a lot of the work of the clubhouse team does is on the project road map for the product and engineering team so you can kind of track a number of those releases. The clubhouse team is also quite accessible at Discord a number of channels. But if you have anything related to something you want to build on top of Cloud most or questions specific to Cloud most in general the ecosystem Cloud most channels a great place where again anything that's like an issue currently with the cloud most tool you could drop in there and then an issue will be created inside the + +Tyler Wright: Was repo and GitHub and the Really responsive about solving those issues as well as ideas or questions about the tool anything else. You can certainly ask in that channel amongst many other channels. Does anyone have any thoughts or questions about Cloud most or anything? They want to ask Max about related to Cloud most updates at this point before we continue on with the agenda. + +Tyler Wright: All Again, there are a number of other teams that are currently building on top of Akash every month I ask those teams to join and happy to move this meeting around to accommodate folks schedule. There was somebody that was scheduled to come to talk about status of their project but has not attended quite yet. So we'll continue on with the agenda. as mentioned at the top Luna who's on the call here had previously been working on terraform provider for a while and I think Is talking about making it more accessible for other people to contribute to the growth Luna. I'll hand it over to you and then we can talk about any next steps if necessary to make it available. + +Joao Luna: Yeah, So for those that don't know the perform provider it was about like it and year and a half ago since then it has been. quite stable and one of the reasons and it's kind of ironic one of the reasons that's that stable is because it's not that Developed so at the time there were really no clients. So we use The cash binary in the system and as long as the binary works and the people in the users keep it updated the provider will keep running with no problem. This has some challenges in the maintainability as well. So + +Joao Luna: the discussion that I started is the first step in a series of efforts that will be doing to open source some of the components that we developed at quasarc that make our platform that we're developing possible. But there are also benefit the Frog community and we think makes sense open sourcing the terraform provider is already open source, but it's under my own profile. The idea of these first step is to move it to the + +Joao Luna: Cache Network organization and then as part of the process moving to That official terraform registry, but under the cache Network organization instead of my username. So it will improve discoverability and Trust as users do find it weird to download an official. Let's say package from terraform. That's not under the official organization. So this is a step towards the debt. And then the next steps will be the kai libraries that's been due for a long time. It's just that we haven't had that Focus yet to open source it's a coupled to our project and we've been decoupling and might soon be ready to open source, and then as part of these efforts, there'll be an effort to further effects that are from provider using that client library that we will release + +Joao Luna: so the code base gets overall more structured and better. And these are the three next steps on that list being the first one that donation of the terraform provider and it will consist basically of moving the terraform provider to the cash organization and then some technical stuff to actually publish it to the terraform registry through the GitHub actions. So what we'll need will be to generate a gpg key. I assume this should be done. Securely by someone from the overclock team that will be able to generate this key. I can walk you through the process pretty easy. But yeah, then this will have to be configured in the repository this gpg key and then GitHub actions will automatically + +00:10:00 + +Joao Luna: publish the artifacts into the registry. But yeah this process I'm available to do it, but I think I should have someone from the overclock really lab team. to actually Configure the gpg key securely, so I don't have access and things can be published more securely. and I think this is the overview of that discussion and the further ones that will arrive in the near future + +Tyler Wright: Perfect. Thank you Luna for that context. + +Joao Luna: any questions + +Tyler Wright: Yeah. Does anyone have any specific questions or concerns about next steps that Luna's Outland? + +Tyler Wright: Cool. If not, then I'll set up some conversations and private conversation between Luna and the appropriate party from the core team to handle that. + +Joao Luna: This process shouldn't take more than one day. So just for context what no more than one two days and… + +Tyler Wright: Okay. + +Joao Luna: we can have this transitioned. It's just that it should be done securely because whoever has that private key can publish an artifact and we don't want that key to fall into malicious ends and publish something malicious in name of the Akash Network. + +Tyler Wright: No, that makes Much appreciate that. So I have an action item that again. I'll set up a conversation with the appropriate person to get that handled between meetings. But thank you very much. And if anyone has any questions comments again, it'll be announcement made. What's the transfer is done for people to access and contribute. + +Tyler Wright: Cool, if there's no questions there then we'll continue on with the agenda. Cool. I know that there again two scheduled demos. I see from folks that are currently here. + +Tyler Wright: I will hand it over to P issues been working with the net of Dao team on a project and PSU can share your screen. If you need to I'm hoping that these demos can be as discussed less than five minutes, talk about what you're trying to solve at the highest level again If you have one how this will improve the accost Network and then we can get into more of the nitty-gritty be at some questions because there's many folks on this. Call that our combination of Technical and non-technical. So again, if we can keep it high level and fairly focus with these demos, then we can get into the nitty gritty and questions and elsewhere, but I'll hand over to you piyush. + +Piyush Choudhary: Yeah. Yeah, thanks for the introduction Ty So those who don't know me so I'm pierced from digital. So we have both for official question networks, exactly so we have been exploring how we can reduce the fictions in onboarding the developers on the So one of the major pinpoint in Akash network is to deploy the GitHub River State I click on GitHub onto Akash. So there is a normal process of getting Dr. Files then creating an HDL then going over to Cloud models and depending it over to the cost and also to update the deployment of nakash first even to get abusive getting to work close the image gets belt and then the user have to go to the console again and updated plan and basically so there is a lot of predictions in between the process and applying applications. when we compare this with the complete first ourselves and + +Piyush Choudhary: London Network, so they have a clear pipeline where they can log in with GitHub select a repositories and they have kind of template or you can see the basic steps which takes care of all the requirement process in case of versatile. They use AWS and the sales and they just run all the scripts automatically without worrying about creating the docker files or basically HDL Etc. So this is what the idea is. Basically we are trying to streamline the process of deploying and applications from GitHub without cash without worrying about the dog creating Docker images or writing Industries. So people have graphical user interface on the cloud moves which will have the single features and then we can have the multiple Spirits for example, in case of versus limited to deploying JavaScript libraries, but with our concept as a POC we can do this for python Library. She can do this for JavaScript anything. We just have to write a proper that's behind the scenes that take years that it takes the Frameworks and basically + +Piyush Choudhary: States there of the deployment commands in the loss. So these quick POC. I would like to Showcase and also for more information says can go through the discussions or drop discussion that I have pushed. and I have a quick POC. This is a quick PRC to get around the idea slowly drive and more updates will be sure to the proposals. So I'm going to like them okay minutes, so Let's say so right now we are going to the steel and in the docker image. We have kind of created a scripts that takes place of everything. So let's say if I want to deploy this so this will take some time as it's big. Let's deploy this + +00:15:00 + +Piyush Choudhary: So some instance there are some errors in this as it's a POC but as we work around so it will be more beer. So as you can see this is the documents that we are created in which it takes care of all the scripting detection commands that runs in the locks and whenever also in case of course, right so we talk about the computer whenever we make the changes to the data presentation. I always thought comes in the GitHub that says the deployment has been triggered on Versa and it automatically pulls the changes and deployed onto the worst. But in case of the car it's an animal process. So this will also solve this. So as soon as the genius something push the greater purpose Jesus origin to I learned that the deployment has been trigger on the cloud most or it's Akash and once successful we have a techno. This is all going to be done to get out and if this + +Piyush Choudhary: So feedback Also suggestions are more than welcome. And I hope this will bring solve the major friction that the current system have maybe Act has an additional layer which will solve the deployments of repository from you don't want to a cost and it will also allow to deploy private repositories as well. Likely from GitHub to cost to get So this is a foundational structural that we have made and the drop proposal is also being pushed. for discussion + +Piyush Choudhary: So till this can deploys anyone have any questions. + +Tyler Wright: I know there's a couple of questions in the chat about private repo. I know that that's something that is actually code complete from the core team and is going to live as it's a core feature to the Akash network over the next week or so. But anyway, I saw your hand up Anil. Do you have a specific question or a comment that + +Anil Murty: Yeah, comment was same as what he just said Tyler. So the core team has been working on supporting Data Bridges fees so we should have a discussion about that and see which solution we ultimately take. so that's number one and then the second does Your Web book essentially depend on being able to utilize a tag on the container image. So I noticed in the STL you have a version tag new depend on that + +Piyush Choudhary: so basically the tag it's not dependent on this. So if you check the STL so we have the environment belt. So whatever you say that goes into goes in the environment third and the image that is being assigned as still is nothing but the background scripts that takes care of the detection and also runs the proper commands of detecting the proper Frameworks similar to what versus + +Anil Murty: Got it here. The reason is mentioning that is because we generally don't recommend people use version tags in the sdl… + +Piyush Choudhary: we have + +Anil Murty: because of the way that we have configured kubernetes. + +Piyush Choudhary: so I think there is probably + +Tyler Wright: That's Luna. Did you ever your hand up? + +Joao Luna: Yeah, it's just a quick question. Perhaps I didn't catch that. Super Mario understood what you do is deploying an image, right and that image will be actively looking for it link repository that you have there. and basically Have your application running right that repository running? is Sorry. + +Piyush Choudhary: So you could check that. Yeah, you can continue. + +Joao Luna: Is that image actively looking for that repo? + +Piyush Choudhary: Yep. + +Joao Luna: So when I make changes? Okay, cool. + +Piyush Choudhary: So we have a timeline set right now it's five minutes. So every five minutes check all the changes but as we implement the GitHub API six will be able to detect as soon as The Pusher are being made to the represents. + +00:20:00 + +Piyush Choudhary: As well the demo. I think it's failing for some reason. I think it's building we don't need. As you can see the script. + +Tyler Wright: Anil I know you had it + +Tyler Wright: I'll go ahead to Sorry, I know Anil has his hands up and I'm not really sure if you answered his previous question about versioning, but go ahead and then I'll hand over to Anil again. + +Piyush Choudhary: So as you can see the script was able to detect that it was very clone the reposites and on the appropriate commands. And as far as we explode computer computers also to the similarities. Yeah, but in short it will not be just about The Versatile thing it will be about any type of things like we can also get a pipeline to deploy button applications. for example, right now aawpers uses python libraries a lot, right so we can have a direct a pipelines which can deploy the python based. applications directly from get one to across without worrying about meeting the local fire or SQL. It's Okay, so this is being deployed as you can see I can just go to. + +Piyush Choudhary: Okay, so this is being declared without creating the sdo 5 so as small questions. Right now the image is just for the POC. So this will Is behind this is nothing but a static or wait a script which takes care of all the deployment by clients. It's kind of automated feature. You can say additional layer which acts as a manager which takes care of all deployment pipelines. And as soon as the dates are getting pushed to the reposites, it keeps on if it keeps a watch and then really deploys the thing in the locks. So yeah. + +Tyler Wright: I see anil's hand up and then Lukas following. So no you go. + +Anil Murty: Hey, Yeah, so a couple of questions one is So then would each clients essentially be deploying this along with their images and pointing it to their repositories or how would so that we want clients per provider. So let's say there's 10 workloads running on providers. There were 10 versions of this running or how this work. + +Piyush Choudhary: So basically, of course the 10 version of this will be running. So right now it says deal so instead of STL we will have a GUI. So in the GI, we will have to options login with GitHub which through Earth we will load all the requests into the platform and say it deploy and The children will not be visible to the users standpoint, but behind the scene as Akash Independence completely on their steel what we are doing through GUI is we are just creating the STL. Under the hood with the repositories URLs and whatever you said, so let's say 10 are trying to use the stool. So basically those 10 users will be deploying the 10 SQL files. So yeah, I think that runs your question. + +Anil Murty: Okay, got it. And then you talked about in supporting private Registries is a privateer GitHub repositories as well. not Registries. Where are you passing the auth information to? + +Piyush Choudhary: So basically now all information should be passed into the logs. It's a + +Anil Murty: How that works. So, ultimately how does your specific app get the auth information + +Piyush Choudhary: So basically when you create a login with get a brighter so that through GitHub apis we can all the represents into the platform. + +Anil Murty: always + +Piyush Choudhary: Yeah, so yeah, yeah. + +Piyush Choudhary: Yeah. + +Piyush Choudhary: Yeah, so we got the key as the login with get up through Earth. We get access to the repositories as there are permissions that we can control through GitHub apis. And as this is the best basically is a manager of all the things when it starts running the commands in here so it takes care of the old Logan it can deploy the private depository as well in that way. So we have to research a bit around this as we have just started working on it. So it was just a POC. So as the foundation gets more clear. We will have more clarity on how the things to look. + +Tyler Wright: Lukas, I see your hand up you have a question. + +lukas meilhammer: Yeah. Hi This sounds like it's touching on a problem that we also had there was a unexpected downtime and in some cases. We didn't know why our application was down. So I mean we have the back end in the database in one rep in one provider and then store J Gateway and front and on another provider, maybe generally Our architecture could be reviewed but we also had the problem that the provider had to then actually do some node maintenance and one time in our developer Maury in the call. First of all, we will have to review your project to you. And then we might also want to get back to you or… + +00:25:00 + +Piyush Choudhary: Yeah. + +lukas meilhammer: jump on the call if that's needed. But + +lukas meilhammer: Lovely to hear that private repositories. I mean coming into the priority a little bit of prioritize a little bit more and… + +Piyush Choudhary: simply + +lukas meilhammer: maybe we wanted to instead of deploying the application via cloudmoss. We wanted to just do it via CLI as So it's the console that you are talking about I bet yeah. + +Piyush Choudhary: so I think of course. Yeah, you can continue that I would. + +lukas meilhammer: Sorry. + +lukas meilhammer: No, please and Maury has actually got more insights on that and maybe it's something for another call for more. Let's say special interest group, but let's please get together on that because we were thinking of let's say collaborating on these kind of things. because we're going Into a phase… + +Piyush Choudhary: if shows + +lukas meilhammer: where we want to do a private or even soon a public data of our platform, which is a data management and data curation and moderation platform. That can be used for many things. So one proposal was actually to do a best practice knowledge base on our platform for Akash users in general. + +lukas meilhammer: Then maybe to have moderators actually changing things in the knowledge base. which could be really a documentation and additional one. And generally maybe I would like to showcase the platform. But let's first finish this topic off and I wanted to just say that we're working on a solution. We have a script to redeploy on the app if it's down and we want to automate the process and figure out where exactly a problem. The occurring from to actually maybe just issue and automatically restart containers and all that. So Maury do you have any thing to add right now related to this discussion here? + +Tyler Wright: Before you all go because I want to give you all some time real fast to talk. + +lukas meilhammer: Yeah. + +Tyler Wright: It's either introduce yourselves a little bit and talk about what you're looking to build a pH. I see your hand up. But real quick. Does anyone else have any other questions or comments at this time about? What piyush just presented? + +Tyler Wright: Go ahead Scott. + +Scott Carruthers: Appears to be you bring up the STL again. + +Piyush Choudhary: If so, yeah, give me two minutes. + +Piyush Choudhary: says nothing visible + +Scott Carruthers: Yes, and then can you so let me make sure that I understand the intense. I understand the removal of the need to create a container image. is a solution also trying to negate the need to customize an sdl. Or so I thought I heard that maybe in the beginning in the presentation, but maybe I'm up. So in order for a user to be able to use this service. Will they need to be? Knowledgeable about a Nicolas sdl as a part of this process to negate the need for a user to have to manually manipulate a sdl. + +Piyush Choudhary: So yeah, so I will take on that. So basically what we have done here is in short the image is the steal anything but a step that is acting as a manager deploy the bit of applications from get up to Akash and also running the commands in locks right after closing the equal States now the thing is like + +00:30:00 + +Piyush Choudhary: Users will always be able to see so we have a te So if I go to the templates not downloads. So as you're going right in case of azure, but we have the first to basically manipulate their skills. GUI, and then we can preview the stove right and single case. We will also have the thing right now here the users do they do this with their own images instead of the images. So the documentation it will not be there with our solution because we see the docker images something that is automatically the things so here we will have the GitHub reposition and if they login with GitHub, then they will have the access to basically whichever it was Jesus. They want to learn to a car and then all these things will be like again, I think the memory and then also they can add things and then what will happen is in the preview for the image will be ours that is + +Piyush Choudhary: you solve which is nothing but you can say a script that is taking care of all the things and then We have the GitHub Registries the environment variables related to the bit of the pastries similar to if you go to the person there is a fair to add environment So yeah, this is something that is eliminating the need for the users if they want to deploy the applications directly from GitHub to Akash. Our solution is eliminating the need to basically create a Docker file and then + +Piyush Choudhary: to go through the process of getting your local file and then deploy you don't do a cost by creating SQL file. And for example, whenever we make the updates to the GitHub Webster's creates a new image who either work close or by manual then to update that employment on We have to come here and basically change the image. Tag and then he deploy to update the deployment. But in our case our script is speaking of what's on the reversies as soon as the push has changes it automatically schools the changes to logs and then they deploys the thing about the latest update. + +lukas meilhammer: So it shortens the seconds and eases the updating General and Autumn is basically actually giving us the option to great. + +Scott Carruthers: Yes, I understood the piece of taking the authoring of the dockerfile. So I understood that when I talked about the sdl What I was curious about is this also taking the needs. I understand you could arrive at a club must screen where you can manipulate the sdl and manipulate the amount of resources that you're throwing at a deployment. I was wondering if this was trying to solve taking that cognitive load off of the user as well. So if I was going to deploy a AI model onto a caution, I was using this service that it would automopulate the sdl with appropriate GPU models and appropriate CPU and RAM and storage. Is that part of this or is it just taking off the load of creating the docker image? But the user would still be responsible for authoring the sdl appropriately. + +Piyush Choudhary: So basically we can consider yourself around this I think this is a possible to this daily prefill the resources that is required to plan applications from getting one to Akash. So we have to research a little bit on this right now. + +Scott Carruthers: Okay. Yeah. + +Piyush Choudhary: It was not a part of this but we will do some research together on this. Yeah. + +Scott Carruthers: Yeah, that makes sense. Yeah, I mean it's very powerful just reducing the cognitive load of not having to create a Docker file. So there's a myths value in that in and of itself. I was just wondering if I was also trying to reduce the cognitive load of being familiar with the sdl but understand that's not part of this current version but maybe something that you would Implement and… + +Piyush Choudhary: Yeah. + +Scott Carruthers: Future versions are research there. Okay. + +Tyler Wright: All right, it seems like again it's been great discussion around this. I know next steps are not a doubt team in piyush are gonna put a discussion around this I would urge that people could get involved in that discussion and give feedback ask questions poke holes so that again those teams can answering those cars and make everybody feel comfortable but before taking any other steps beyond that looks like a discussion is already live. Thank you very much. So again, + +Tyler Wright: I want to make sure and I'll continue to share this but hopefully the net a Dao team and piyush can continue to share this across Discord get feedback from members of the community in general Chad and all channels and just continue a lively discussion around this. That would be very impactful. But again much appreciate the time that you took today the work that went into this and thank you everyone for those questions. + +00:35:00 + +Tyler Wright: All I know we only have about 22 minutes left. I wanted to give a Lukas and Maury some time to talk. This is a group and talking to a bit Discord and Elsewhere for a little while and they're a very technical group. That's again building their own Solutions based in Europe. I want to In the platform to talk about some other they've already been deploying on a caution. It's found some issues and again and working to solve those issues. So I want to hand over the floor to Lukas to talk at a high level, about themselves what they're building the advantages to the Akash Network and then we'll open up to questions and get into the weeds. + +lukas meilhammer: Yeah, hi everyone and here in the Juventus touring. No trickle one of our code developers Maury our city hall can join how today but We are basically building and I'm just going to bring it up probably almost directly. We're basically building a data and knowledge Marketplace. We're trying to let the user decide how they want to monetize their data or how they want to give access to it. So whether it may be token holding having an Nifty and basically paying a subscription doesn't really matter too much for us because we are basically building a little bit of instruction infrastructure around this. + +lukas meilhammer: Taking contracts to issue rewards at some point all that. So it's a no-code database built on a decentralized cloud storing the data on store J. + +Piyush Choudhary: let's + +lukas meilhammer: It's been quite a bit of a built so far, but we're slowly moving ahead and We are in the process of actually launching a public or private data or I mean databases can basically be entirely private protected or public so I will just show the platform quickly + +lukas meilhammer: I hope to just gain some attention and get some people on board that want to build with our platform. So. I would say. I'll just walk you through the different top level panels here. You have a profile you can browse users in the next version profile can also be private so that you don't see the actual wallet hash that someone logged into then you have incoming requests for the database so that you can basically add someone's use a hash and give him access that usages something for later. + +lukas meilhammer: And then you have incoming outgoing and you have changed requests because basically in each database, let's just open one up quickly. This is a protected database which basically means everyone can see this page. Everyone can see. The criteria the description everything of the database and there should actually be the data schema down below here. So the data schema is public the metrics on how the platform is used here. We see an error already which sometimes we don't know exactly where it's coming from. And then basically it's more related to its. Hope that opens at least now. okay so I can basically make inputs in this field private with a right click + +lukas meilhammer: And then it's going to appear gray. And for the user that is not the owner. It will just be empty and empty field. you have all the filters that you usually have. You can set up a form you can change the form. So it's basically like an air table on a decentralized cloud with giving everyone the options to monetize the data day as they wish. Tyler you have a question already. + +Tyler Wright: Yeah, I appreciate you showing us this I just want to make sure because again many of these folks on this call are focus on Akash. + +lukas meilhammer: Yeah. + +Tyler Wright: I just want to see where the implementation of their cash network is and I remember you talking about redeploy tools as you were leveraging a car. So I just wanted to make sure we got to that part because I'm sure there'll be some questions and yeah. + +lukas meilhammer: Yeah. + +lukas meilhammer: So I'm not a CTO but let me try to summarize this a little bit. So as I said, we have the deployment a little bit split between providers front banners on one S3 storage Gateway is on the other on another one and the database and the back and is on another provider so correct me if I'm wrong here Maury. + +00:40:00 + +lukas meilhammer: But generally we were facing some problems also with the docker images and all that and we just have to maybe review the solution that was presented here today to figure out whether this already solves our need but going into a public beta in we might want to have that iron out and we're happy to wait a little bit. But generally I'm here to get some feedback ask people on whether they want to build something with us and maybe generally also try to let's say summarize these calls sometimes a little bit because + +lukas meilhammer: there is a little bit of friction and maybe questions that are answered multiple times in the Discord. So thinking about a deployment best practices or maybe even a more let's say open roadmap on what's about to come To just actually not worry about stuff that you don't have to be worried about because there's an update in one week. For example, that was one approach where we thought we can use the platform as it is, but that would of course have to be discussed in terms of what else would we need an API that pulls data from other repositories where you document stuff so thank you for now born in first intro call. This was really helpful and all basically. + +lukas meilhammer: so what's running on Akash, everything is running on a cash and the database is on storage a doll the backend the front end and S3 Gateway for + +lukas meilhammer: For the storage integration that the S3 store there was this code. Yes, please go ahead with questions. + +Piyush Choudhary: Yeah, so I have a question. + +Tyler Wright: Go ahead. Peace. + +Piyush Choudhary: So it's an initiative talk about backing up the deployments that caused town by the providers. So I would like to ask where is that thing going on? And also you talk about you lost all the data and the deployment goes down from one of the providers. So are you obviously teaching the solutions that backs of the data or is it something else? + +lukas meilhammer: My meeting already came out for this but there was no backup routine. we have definitely in the process of identifying the errors somehow or in any way. We are also happy to share the insights. And if there's really something and that you already working on and we were of course to know a little bit ahead of time then when it's uploaded or maybe take some part into the actual definition or scripting or work and then this could all move ahead a little bit quicker and I'm generally a very big believer in decentralization. So happy for any collaboration that pops out of this calls here. Anil + +Piyush Choudhary: Yeah, sure Yeah, so I will bring you upon Discord to see if you can call them collaborate on some things type you're working on and other hand over 200. + +lukas meilhammer: Perfect. No, please let's schedule a call latest next week or so Maury. Do you have anything else to say and before Anil? Maybe + +Maury De Jesus: For now and it's okay. Yes. + +lukas meilhammer: Anil + +Anil Murty: Yeah, so this is cool. And I didn't realize I only heard storage in S3. So I wasn't sure if something was running on So it seems like the front end in the backend are running on Akash and all the data is actually stored on store Jesus. Is that right? Okay. + +lukas meilhammer: And it's only data. + +Maury De Jesus: Yes. + +lukas meilhammer: So there's not a lot of data traffic and all that. I'll just basically forward you because someone was asking me for the provider. I don't think that there's any Critical information just post the whole thing into the chat. Really you quickly know just + +Anil Murty: Got it aakash proba Okay, so I was mostly curious about which providers you're using because I think so. There's a couple of things I don't know if you're familiar, but essentially Even if you're using persistent storage on a cash today meaning stories that person essentially still have to make sure that you back up your data somewhere else. + +lukas meilhammer: Yeah. + +Anil Murty: So whether it's true or just something and there is no really backup solution today that's available and that's potentially something for Either the core team or somebody in the community to look at I've been on our list of things but just haven't gotten to it but it's a very common request that most customers have the recommendation because you implement something on your side backup your data regularly because when the lease closes you lose it. so that's basically so as long as you're backing up the data to storage it should be okay and then + +00:45:00 + +Anil Murty: At least from what I understand today, you don't have active users on this product,… + +lukas meilhammer: Yeah. Yes,… + +Anil Murty: right? It's still in. + +lukas meilhammer: no, no, our puc clients Partners actually looking to launching or updating some data. I don't necessarily see them because they are not shared with me or… + +Anil Murty: Sorry, yeah. + +lukas meilhammer: whatever, but basically if you have a database you can keep it private. Then you make it protected so that people see the data schema you get maybe initial requests for Access and maybe some more insights. + +Piyush Choudhary: just + +lukas meilhammer: Yeah, and then basically at some point maybe you want to put it public because it's got some marketing value what not. So generally, we really happy to also please also add me on LinkedIn. Maybe we can just schedule a call also a deaf call or Tech call for anyone my class interested in,… + +Anil Murty: Yeah, sure. + +lukas meilhammer: Idaho. all that + +Anil Murty: It didn't actually just to preserve time on this call. I'll just have you LinkedIn and we can have a conversation about this and see we can help it in terms of,… + +lukas meilhammer: Perfect. + +Anil Murty: giving you better providers or looking at connecting with providers that have been on the network for a long time and then we're gonna have a user confidence. So you want to talk about your solution there to the greatest. + +lukas meilhammer: If you don't mind, I found a few of you guys on LinkedIn already. I will just maybe make a connect request. + +Maury De Jesus: Try again to connecting in French changing Lukas. + +lukas meilhammer: … + +Tyler Wright: and we also private Channel. + +lukas meilhammer: because the net that + +Maury De Jesus: Is refresh the fish. + +Tyler Wright: We also have a private Channel with Lukas and the team on Discord for admins that we can also talk in so much appreciate. + +lukas meilhammer: Yeah, what we do invite you guys there if it's for technical technically related stuff refreshed refresh this page. Yes. Now it's not so super important. I think everyone gets the platform and I mean eventually on the long run we would really like to rather make it a easy interface just like Google you search instead of websites, you get databases stuff like that. and then maybe you don't have access you still need to request or maybe you perform a quest or whatever how you want to monetize your data and I think with Jesus we will find a way to monetize and I'm really happy to have people meeting their own platform. I'm not really keen on offering white labeled versions of it at the moment just so that our brand and our project just gets more known out there but happy to we're working on the API actually pulling data in so that eventually you could have more like cryptocurrency. + +lukas meilhammer: Analysis dashboards with the market cap updating and all that stuff. Yeah, that's a very common request at the moment because we're in a bull market. So yeah. Yeah, I see that. Yeah. Yeah all good guys. Thank you for the flowers. + +Tyler Wright: this all right. + +lukas meilhammer: up just by the way, so + +Tyler Wright: excellent + +lukas meilhammer: Really? Excellent. I thank you for the time already and happy to invite you all to a group or start some I tell telegram Channel. Just shoot me a message on LinkedIn. I've been sending some requests. I'll just now. + +Tyler Wright: Excellent. All… + +lukas meilhammer: through joao zip + +Tyler Wright: I know we only have a couple of minutes left much appreciate again the demos from piyush and the net a Dao team as well as from Lucas Maury and the folks over at ipal again. We try to take these Sid clients meetings and I will adjust the schedule to make sure that more beings like this are available. But this is a great opportunity for teams to connect with one another for folks to talk about ideas that they're building and still they can get feedback from members of the community and members of the core team as early as possible so that we can continue to push. + +Tyler Wright: Or it's again demand driving usage on the network. Those being the main Theses that again everybody from the community hearing committee and elsewhere is agreed on how we continue to push forward the Akash Network, especially through clients. Cool. Is there any other questions comments or any other discussion points that anybody wants to bring up with just a couple minutes we have left. + +Tyler Wright: If not, then again, I'm sure they'll be following conversations with the ipal team. I thank you for joining. If you have any other thoughts, please feel free to drop them in the Sig clients' Channel, again or one of the other channels but said clients is a great place to put things so that everybody from the community can interact and give feedback because again there's a number of great teams individuals that have been around for many many years almond are very technical and can provide a lot of support So as much can be done in public would be great. But again, we'll continue to have conversations again. Thank you to Pearson that a doubt team if anybody had any feedback thoughts about their proposal, please drop it inside the discussion that will spur more conversation. + +00:50:00 + +Tyler Wright: The community and that's what we're looking to do. That'll help drive next steps there. So please ask any questions even if something seems like it may be a dumb question. Feel free to ask and you'll get clarity from the netted out team in peace and we can continue to push that process forward and as always thanks for the updates Max and all the things that you and the cloud most slash console team are working on there's a couple other teams that again we're going to continue to push to join these meetings. So for those that are new Feel free to reach out to me. If you just want to be added to the meeting every month. Again. There's a number of teams based all over the world that are solving a number of problems. So this is usually a very Lively special interest group on a monthly basis. + +Tyler Wright: All right, I hope everyone has a great rest of their day. Unless anybody has anything else. I'm gonna let you go and we'll talk more online. Cool. Thank you everyone. + +lukas meilhammer: Thank you everyone the pleasure. + +Tyler Wright: Bye-bye. + +Anil Murty: it's kind of + +Piyush Choudhary: more than about + +Meeting ended after 01:04:16 👋 + From 38080c586f73349e5be1e7aa03fc60c86d187d6a Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 18 Jun 2024 10:31:08 -0400 Subject: [PATCH 074/138] sig-clients Update README.md updated meeting table with bimonthly schedule chore: add meeting 15 and 16 notes when available. Signed-off-by: Drinkwater --- sig-clients/README.md | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/sig-clients/README.md b/sig-clients/README.md index 22aa65e5..16b719c6 100644 --- a/sig-clients/README.md +++ b/sig-clients/README.md @@ -46,17 +46,13 @@ The goal of this SIG is to foster a community around each of these clients that | #11 | Monday, December 18th, 2023 08:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/011-2023-12-18.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/011-2023-12-18.md#transcript) |[Link](https://msr577epylf5qgo6aexm2xbblsreurfi2pgy5ed5ssdw6ztgkxwq.arweave.net/ZKPf_I_Cy9gZ3gEuzVwhXKJKRKjTzY6QfZSHb2ZmVe0) | #12 | Wednesday, January 17, 2024 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/012-2024-01-17.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/012-2024-01-17.md#transcript) |[Link](https://75iuscsrjioekyahvk6vad3taa5ikpweibvxs2rf4amjvzvj6gfa.arweave.net/_1FJClFKHEVgB6q9UA9zADqFPsRAa3lqJeAYmuap8Yo) | #13 | Thursday, February 22nd, 2024 09:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/013-2024-02-22.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/013-2024-02-22.md#transcript) |[Link](https://x5g5djwxzxixepgqsmxl6rupiipshcicdmq5bf2tjac35fjv5f6q.arweave.net/v03RptfN0XI80JMuv0aPQh8jiQIbIdCXU0gFvpU16X0) -| #14| March 27th, 2024 09:00 AM PT (Pacific Time) | | | +| #14| March 27th, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/014-2024-03-27.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/014-2024-03-27.md#transcript) | Coming Soon | #15| April 24th, 2024 09:00 AM PT (Pacific Time) | | | -| #16| May, 2024 10:30 AM PT (Pacific Time) | | | -| #17| June, 2024 10:30 AM PT (Pacific Time) | | | -| #18| July, 2024 10:30 AM PT (Pacific Time) | | | -| #19| August, 2024 10:30 AM PT (Pacific Time) | | | -| #20| September, 2024 10:30 AM PT (Pacific Time) | | | -| #21| October 2024 10:30 AM PT (Pacific Time) | | | -| #22| November, 2024 10:30 AM PT (Pacific Time) | | | -| #23| December, 2024 10:30 AM PT (Pacific Time) | | | -| #24| January, 2025 10:30 AM PT (Pacific Time) | | | +| #16| June 18th, 2024 10:30 AM PT (Pacific Time) | | | +| #17| August, 2024 10:30 AM PT (Pacific Time) | | | +| #18| October 2024 10:30 AM PT (Pacific Time) | | | +| #19| December, 2024 10:30 AM PT (Pacific Time) | | | +| #20| January, 2025 10:30 AM PT (Pacific Time) | | | ## Leadership From 1727624f6256774e9097b272e11e8127edf1ab83 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 18 Jun 2024 15:51:40 +0000 Subject: [PATCH 075/138] update readme tables (#594) Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Co-authored-by: Drinkwater --- sig-design/README.md | 6 +++--- sig-documentation/README.md | 6 +++--- sig-support/README.md | 10 ++++------ .../meetings/{029-2024-03-06.md => 029-2024-03-20.md} | 0 wg-akash-website/README.md | 2 +- 5 files changed, 11 insertions(+), 13 deletions(-) rename sig-support/meetings/{029-2024-03-06.md => 029-2024-03-20.md} (100%) diff --git a/sig-design/README.md b/sig-design/README.md index 145cd180..c206565f 100644 --- a/sig-design/README.md +++ b/sig-design/README.md @@ -29,9 +29,9 @@ date: 2023-1-09T00:19:20-08:00 | #12| Wednesday, December 13, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/012-2023-12-13.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/012-2023-12-13.md#transcript) | [Link](https://une76rieq3cvbtrnjv3gxaw6kbxaay3tnzqsangya2lfe6ionpva.arweave.net/o0n_RQSGxVDOLU12a4LeUG4AY3NuYSA02AaWUnkOa-o) | #13| Wednesday, January 10, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md#transcript) | [Link](https://zao4urnjuqb6ncx2vacwjuqiyqnucl2ifcfm33blijhw6v6owzla.arweave.net/yB3KRamkA-aK-qgFZNIIxBtBL0gois3sK0JPb1fOtlY) | #14| Wednesday, February 21, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/014-2024-02-21.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/014-2024-02-21.md#transcript) | Coming Soon -| #15| March 13th, 2024 08:00 AM PT (Pacific Time) | | | -| #16| May, 2024 08:00 AM PT (Pacific Time) | | | -| #17| June, 2024 08:00 AM PT (Pacific Time) | | | +| #15| March 13th, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/015-2024-03-13.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/015-2024-03-13.md#transcript) |[Link](https://nnq3ufkztaw2lqjhzhftmlaxw3rt7c3x6hotvsz7gjm2pf7jbgtq.arweave.net/a2G6FVmYLaXBJ8nLNiwXtuM_i3fx3TrLPzJZp5fpCac) +| #16| April 2024 08:00 AM PT (Pacific Time) | | | +| #17| June, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/016-2024-05-08.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/016-2024-05-08.md#transcript) |[Link](https://utgdid3tyicjsjmgvznzalfhes33oqqzoytow53oaqvlgg6nbmlq.arweave.net/pMw0D3PCBJklhq5bkCynJLe3Qhl2Jut3bgQqsxvNCxc) | #18| July, 2024 08:00 AM PT (Pacific Time) | | | | #19| August, 2024 08:00 AM PT (Pacific Time) | | | | #20| September, 2024 08:00 AM PT (Pacific Time) | | | diff --git a/sig-documentation/README.md b/sig-documentation/README.md index d4550253..ed17b4ce 100644 --- a/sig-documentation/README.md +++ b/sig-documentation/README.md @@ -29,9 +29,9 @@ The goal of this SIG is to foster a community around the creation and maintenanc | #11 | Tuesday, November 28, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/011-2023-11-28.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/011-2023-11-28.md#transcript) |[Link](https://na7gjhjowrrxc37tzk76rixczxf4st6b3rjpfjrzktiln7yxuckq.arweave.net/aD5knS60Y3Fv88q_6KLizcvJT8HcUvKmOVTQtv8XoJU) | #12 | Tuesday, December 19, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/012-2023-12-19.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/012-2023-12-19.md#transcript)|[Link](https://w3evlgbcqz4g4b4kicipe3gxrblirj4f2czs3eutaibrqrp7xtva.arweave.net/tslVmCKGeG4HikCQ8mzXiFaIp4XQsy2SkwIDGEX_vOo) | #13 | Tuesday, January 23, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/013-2024-01-23.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/013-2024-01-23.md#transcript) |[Link](https://ggtsa72sjsvu3yph245qmj6zvpy7uyys7jerkj72heitmyoiv2na.arweave.net/Macgf1JMq03h59c7BifZq_H6YxL6SRUn-jkRNmHIrpo) -| #14 | Tuesday, February 27, 2024 07:00 AM PT (Pacific Time) | | | -| #15| March, 2024 07:00 AM PT (Pacific Time) | | | -| #16| April 23, 2024 07:00 AM PT (Pacific Time) | | | +| #14 | Tuesday February 27, 2024 07:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/014-2024-02-27.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/014-2024-02-27.md#transcript)|Coming Soon +| #15| March 26, 2024 07:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/015-2024-03-26.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/015-2024-03-26.md#transcript) |[Link](https://7lvvy6qbe6wq3tzg3zl2vbxvamshk5ibb3bi32m6fbt5vwdlonpa.arweave.net/-utcegEnrQ3PJt5Xqob1AyR1dQEOwo3pnihn2thrc14) +| #16| April 23, 2024 07:00 AM PT (Pacific Time) | | | | #17| May, 2024 07:00 AM PT (Pacific Time) | | | | #18| June, 2024 07:00 AM PT (Pacific Time) | | | | #19| July, 2024 07:00 AM PT (Pacific Time) | | | diff --git a/sig-support/README.md b/sig-support/README.md index 1e5422b1..92d3bfb6 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -44,14 +44,12 @@ sig-support is responsible for defining mechanics of how support works at Akash | #26 | Wed, January 24, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/026-2024-01-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/026-2024-01-24.md#transcript) |[Link](https://47vntytp4ni2s5p2h2qyh5nuqywowtwne2fx4ddudv7iyl3hu5rq.arweave.net/5-rZ4m_jUal1-j6hg_W0hizrTs0mi34MdB1-jC9np2M) | #27 | Wed, February 21, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/027-2024-02-21.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/027-2024-02-21.md#transcript) |[Link](https://cwya3qcl4ejhb75ct5d4vgcoyhsce46zvv2q42khi6kc76qhsxpq.arweave.net/FbANwEvhEnD_op9HyphOweQic9mtdQ5pR0eUL_oHld8) | #28 | Wed, March 06, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/028-2024-03-06.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/028-2024-03-06.md#transcript) |[Link](https://xut7rmdqwninrlvm75t7cxmmpgrt4tyboramnw3b2rcpaa6gy76a.arweave.net/vSf4sHCzUNiurP9n8V2MeaM-TwF0QMbbYdRE8APGx_w) -| #29 | Wed, March 20, 2024 08:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon +| #29 | Wed, March 20, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/029-2024-03-06.md) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/029-2024-03-06.md) | Coming Soon | #30 | Wed, April 30, 2024 08:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon | #31 | Wed, April 17, 2024 08:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon -| #32 | Wed, May 01, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/032-2024-05-01.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/032-2024-05-01.md#transcript) |[Link](https://fp4bufbowjh5thinihsyy52ddcyesjk2yofv4fgjmrhnkahxg5ua.arweave.net/K_gaFC6yT9mdDUHljHdDGLBJJVrDi14UyWRO1QD3N2g) -| #33 | Wed, May 15, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/033-2024-05-15.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/033-2024-05-15.md#transcript) |[Link](https://qc3gxtikakjsqoqohkver467q5u675nuwy7ovtc6j4ajicy7vwna.arweave.net/gLZrzQoCkyg6DjqqSPPfh2nv9bS2PurMXk8AlAsfrZo) -| #34 | Wed, June 05, 2024 08:00 AM PT (Pacific Time) | | | -| #35 | Wed, June 12, 2024 08:00 AM PT (Pacific Time) | | | - +| #32 | Wed, May 01, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/032-2024-05-01.md) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/032-2024-05-01.md#transcript)|[Link](https://fp4bufbowjh5thinihsyy52ddcyesjk2yofv4fgjmrhnkahxg5ua.arweave.net/K_gaFC6yT9mdDUHljHdDGLBJJVrDi14UyWRO1QD3N2g) +| #33 | Wed, May 15, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/033-2024-05-15.md)|[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/033-2024-05-15.md#transcript)|[Link](https://qc3gxtikakjsqoqohkver467q5u675nuwy7ovtc6j4ajicy7vwna.arweave.net/gLZrzQoCkyg6DjqqSPPfh2nv9bS2PurMXk8AlAsfrZo) +| #34 | Wed, May 29, 2024 08:00 AM PT (Pacific Time) | | | ## Leadership diff --git a/sig-support/meetings/029-2024-03-06.md b/sig-support/meetings/029-2024-03-20.md similarity index 100% rename from sig-support/meetings/029-2024-03-06.md rename to sig-support/meetings/029-2024-03-20.md diff --git a/wg-akash-website/README.md b/wg-akash-website/README.md index 0ff6bcba..482e8012 100644 --- a/wg-akash-website/README.md +++ b/wg-akash-website/README.md @@ -33,7 +33,7 @@ This working group is responsible for managing and improving the Akash Network W | #21 | Wednesday, January 03, 2023 06:30 AM PT (Pacific Time)| Coming soon | Coming soon| Coming Soon | #22 | Thursday, January 04, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/022-2024-01-04.md)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/022-2024-01-04.md#Transcript)| [Link](https://ebt6smszfxnrsafl35ae3krholqikfmckktlj6rw2tpk26lxcmgq.arweave.net/IGfpMlkt2xkAq99ATaoncuCFFYJSprT6NtTerXl3Ew0) | #23 | Friday, January 05, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/023-2024-01-05.md)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/023-2024-01-05.md#Transcript)| [Link](https://5vpr5a76zkbuulfpmj7mtg24vkn6vpli5zlmcvqd3uupea3bxgva.arweave.net/7V8eg_7Kg0osr2J-yZtcqpvqvWjuVsFWA90o8gNhuao) - +| #29 | Friday, April 04, 2024 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/029-2024-04-04.md)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/029-2024-04-04.md#Transcript)| [Link](https://yiwmcmmelchqik2ii4s7yt2wzvjy55gwxnpe2uekrwv6rv552sgq.arweave.net/wizBMYRYjwQrSEcl_E9WzVOO9Na7Xk1Qio2r6Ne91I0) ## Leads From 37de4246e04f8a1fc28ff8b035293ccd744308e3 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 25 Jun 2024 11:50:05 -0400 Subject: [PATCH 076/138] sig-clients Update README.md update readme Signed-off-by: Drinkwater --- sig-clients/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/sig-clients/README.md b/sig-clients/README.md index 16b719c6..dcb68118 100644 --- a/sig-clients/README.md +++ b/sig-clients/README.md @@ -48,7 +48,7 @@ The goal of this SIG is to foster a community around each of these clients that | #13 | Thursday, February 22nd, 2024 09:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/013-2024-02-22.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/013-2024-02-22.md#transcript) |[Link](https://x5g5djwxzxixepgqsmxl6rupiipshcicdmq5bf2tjac35fjv5f6q.arweave.net/v03RptfN0XI80JMuv0aPQh8jiQIbIdCXU0gFvpU16X0) | #14| March 27th, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/014-2024-03-27.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/014-2024-03-27.md#transcript) | Coming Soon | #15| April 24th, 2024 09:00 AM PT (Pacific Time) | | | -| #16| June 18th, 2024 10:30 AM PT (Pacific Time) | | | +| #16| June 25th, 2024 10:00 AM PT (Pacific Time) | | | | #17| August, 2024 10:30 AM PT (Pacific Time) | | | | #18| October 2024 10:30 AM PT (Pacific Time) | | | | #19| December, 2024 10:30 AM PT (Pacific Time) | | | @@ -61,9 +61,9 @@ The goal of this SIG is to foster a community around each of these clients that - Anil Murty, Overclock Labs (@anilmurty) - Akash Console - Greg Osuri, Overclock Labs (@gosuri) - Akash CLI - Joao Luna, Quasarch (@cloud-j-luna) - Terraform Provider, Client Libraries -- Maxime Beauchamp, Cloudmos (baktun14) - Cloudmos Deploy -- Prashant Maurya, Spheron Network () - Spheron -- Jigar Patel, Praetor (jigar-arc10) - Praetor App +- Maxime Beauchamp, Cloudmos (baktun14) - Akash Console +- Jigar Patel, Praetor (jigar-arc10) - Akash Console +- Deval Patel, Praetor - Akash Console ### Tech Lead(s) From 707842cbecc7b8d79b0aecfca65a6bd00ba1d3b9 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 25 Jun 2024 11:50:29 -0400 Subject: [PATCH 077/138] Update README.md Signed-off-by: Drinkwater --- sig-clients/README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/sig-clients/README.md b/sig-clients/README.md index dcb68118..62aee27e 100644 --- a/sig-clients/README.md +++ b/sig-clients/README.md @@ -15,7 +15,6 @@ Akash Network Clients are software and services that make it easier for tenants - [Client Libraries](client-libraries/README.md) (for various programming languages) - [Cloudmos Deploy](cloudmos-deploy/README.md) - [Fleek](fleek/README.md) -- [Spheron](spheron/README.md) - [Terraform Provider](terraform-provider/README.md) ## Provider Onboarding Clients From d89c4794e2d1ffba517d891f0e7cd6a2fe4062d5 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Wed, 26 Jun 2024 14:12:31 +0000 Subject: [PATCH 078/138] Create meeting notes for sig providers #16 (#592) * Create meeting notes for sig providers #16 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 016-2024-04-24.md add transcript chore: add video recording link Signed-off-by: Drinkwater * Update 016-2024-04-24.md Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-providers/meetings/016-2024-04-24.md | 286 +++++++++++++++++++++++ 1 file changed, 286 insertions(+) create mode 100644 sig-providers/meetings/016-2024-04-24.md diff --git a/sig-providers/meetings/016-2024-04-24.md b/sig-providers/meetings/016-2024-04-24.md new file mode 100644 index 00000000..45a48e3f --- /dev/null +++ b/sig-providers/meetings/016-2024-04-24.md @@ -0,0 +1,286 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #16 + +## Agenda +- Update from Praetor on all of the work that they have been doing. +- Open Discussion on all things related to Akash Providers. +- Provider Build Process and Stability +- Bid Engine Updates + +## Meeting Details +- Date: Wednesday, April 24, 2024 +- Time: 08:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + +## Participants +- Andrew Hare +- Andrey Arapov +- Damir Simpovic +- Deval Patel +- Jigar Patel +- Lukas Meilhammer +- Nathan Ward +- Scott Carruthers +- Tyler Wright + +## Meeting notes +#### Tyler Wright: +- Welcomed everyone to the providers monthly meeting. +- Emphasized the importance of the community repo for provider audits. Providers should follow the template available for audits. +- Acknowledged Andrey Arapov's efforts in keeping the provider announcements updated on Discord. +- Praetor’s role in facilitating upgrades for those who prefer an easier path than direct documentation. +- Mentioned efforts to ensure providers stay updated, noting some providers had outdated versions and incorrect contact information. +- Encouraged checking the provider announcements channel regularly for updates on versions and upgrade instructions. +- Weekly SIG meetings are led by Scott Carruthers with support from Andrew Hare and Andrey Arapov. +- They discuss support issues related to the Akash codebase. +- Providers are encouraged to track issues labeled "provider" in the support repo of the Akash Network organization. +- Tyler urged providers to participate in the weekly SIG meetings or leave comments on relevant issues. + +**Praetor Team Updates:** +- Tyler Wright announced the successful acquisition of the Praetor team by Overclock Labs. Praetor will soon be open-sourced, enabling community contributions and collaborative improvements. +- Jigar Patel highlighted the Praetor team's journey and expressed gratitude for the community's support. He outlined the steps being taken to open-source Praetor's three microservices. +- **Key Updates from Jigar Patel:** + - Praetor tooling will be open-sourced, with three microservices to be available for community contributions. + - Recently provided a one-click update for version 5.13 for providers. + - Active development on open-sourcing Praetor's microservices is ongoing. + +**Roadmap and Project Tracking:** +- Tyler Wright emphasized the importance of the public-facing roadmap available on GitHub in the project section. It will show ongoing and upcoming tasks, including contributions from the Praetor team. +- Providers and community members are encouraged to track progress and participate by leaving comments and suggestions. + +**Network Upgrade Information:** + - A network upgrade is scheduled for next Thursday, pending validator votes. + - Validators are encouraged to vote on the upgrade, which aims to enhance usability and unlock new functionalities such as private repositories. + - Post-upgrade, validators will test for stability on Mainnet before notifying providers to upgrade their nodes. + +**Provider Build Process and Stability:** +- Tyler Wright discussed efforts to improve provider stability and build processes. +- Scott Carruthers introduced a new automated Akash provider build process, currently in beta: + - Automated build process using K3s for Kubernetes clusters. + - Significant reduction in build time to 10-15 minutes. + - Current status: In beta, suitable for lab builds and testnet builds. + - Community and core team are invited to test and provide feedback. + - Documentation available at [Akashengineers.xyz](http://akashengineers.xyz). + +**Bid Engine Updates:** +- Scott Carruthers updated on the progress of converting the bid engine script from Bash to Go: + - Reverse engineering of the Bash script to Go is largely complete. + - Testing ongoing to ensure identical pricing outputs between Bash and Go versions. + - Discussion on supporting customization of the bid script for providers with specific needs. + - Andrey Arapov suggested maintaining support for both Bash and Go scripts temporarily. + - Consideration for an approach where providers can specify the script path to a custom binary or script. + +**Closing Remarks:** +- Tyler Wright invited additional provider-related discussions. +- Emphasis on staying engaged in discussions on Discord and GitHub. +- Reminded attendees about the upcoming SIG client call and the rescheduled steering committee meeting on May 2nd. +## Action Items +- Praetor to continue the process of open-sourcing Praetor’s microservices. +- Praetor to keep the community updated on progress and any issues via GitHub. +- Core Engineering Team to focus on improving provider stability and refining the build process. +- Core Engineering Team to Continue testing and developing the automated build process. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the providers monthly meeting for April It's April 24th, 2024 this special interest group for providers meets monthly to discuss all things related to the Akash provider. Usually have conversations have been around issues to the cost provider upgrades. There's been discussions on Those updates from the play tour team, which is a preferred and easy way to build a provider on Akash for those that are slightly less Technical and don't want to use the documentation. We've gone over the documentation in previous meetings related to the cost provider. + +Tyler Wright: There'll be a couple of announcements that I will go through before we might talk about a couple of things and then I open it up to any questions. couple things again as we talk about every month if anybody is looking to have to provide our audited please use the community repo. There is a template for those that are looking to have their provider audited Andrey Andy on Discord does a great job of keeping the announcements in the provider announcements tab updated for folks so that they can know again upgrades versions how to upgrade Etc. I know that pretor has historically followed behind with allowing those that use their path to upgrade. So again, please look out for those announcements. + +Tyler Wright: We are trying to keep people informed obviously. There's some folks that don't always check Discord as often as they are. So there are some workarounds that are being discussed to make sure that again providers upgrading because there were a group of providers that were previously audited that were running very very old versions didn't have proper contact information. So again, Andy is made announcements multiple times in the provider announcements Channel keeping people up to date and all things related to Providers and provider upgrades. + +Tyler Wright: Continuing on since our last meeting there has been a fair amount of work that's been going on related to the provider. There is a six weekly meeting that happens where usually led by Scott Arthur and with support from Andrew and Andre we go over any support issues that are in relation to the court code base in the support repo and the cash Network organization. Any issues that are related to the provider or tagged provider. And again, we have discussions about those issues during that time. So if anybody has any questions or comments about anything related to the provider any issues that they brought forth whether it be in the community or again Made issues directly, please. + +Tyler Wright: please track this repo and you can look by a track this issue the issues and the support repo and you can look by the label of report provider. And again, if you have any comments questions concerns, feel free to join that weekly meeting or feel free to drop a comment inside this relevant issue + +Tyler Wright: continuing to move on one of the big items that has happened on chain. I think it was beginning to talk about it was the community funding for prey tour to make it open source and to bring the pray to our team who was on the call today under overclock. Again, there's been some items that have been added to the roadmap. That will indicate some of the work that the Prater team will be doing on their roadmap. There will be some issues that will be created that can be tracked by folks. But again, I think the first thing is obviously there's got a lot of hard work that the prior team has done over. + +Tyler Wright: maybe two years at this point even longer to again allow another path for folks to easily build the provider. I know that when there's been issues with the prey tour app. The prior team has been very responsive and made changes as quickly as possible. They've worked very very closely with the core team on upgrades on again changing their structure to accommodate Helm charts. And again now is acquisition is now complete pray for will be open source in the near future so that it can be Community contributions. I know there's a whole plan that's pertains that provided microservices and just like a good improving the provider experience in general. + +00:05:00 + +Tyler Wright: It's going to be great to be working even more closely together on what that looks like. I do want to give Jigger and dabal a little bit of time if they want to talk because usually again during these providers they give an update on all things pray to our but again, it's a new day new age. So they'll continue to get updates on all the work that they're doing during these meetings, and it will continue to grow into more of a collaborative effort, especially as again provider microservices are broken out and The pretor cooling becomes more open source, and we get more contributions from the community. So again much. Congratulations to all the hard work and pray to our team. Go ahead. Jigar. + +Jigar Patel: Yeah, thanks Yeah, and thanks to everybody who supported us throughout our journey. we are very excited to continue work on Twitter with the work lab teams and all the family faces God Andrew and everybody actually right who supported us in our journey. And our past excellent. Now all the formalities are done. We started working on making Twitter an open source right now. And then in the meantime, we also gave one click update for 5.13 that recently updated in a provider. So that's on this road out and it's available for providers to update and + +Jigar Patel: yes, we are working currently on open sourcing all over three microservices. So our Predator is based on three microservices. So it'll be open source soon. And then obviously we will add more issues into all those data papers and we'll track and continue our work on working on those issues. + +Tyler Wright: excellent Again, the public facing roadmap for product and Engineering is in GitHub in the project section. We talked about it during the steering committee, which will happen next Thursday, May 2nd. But this is available to anybody anybody can leave comments at any time again Against this board as jigar just mentioned as they continue open source, and they have those three specific microservices that have become reposed. They will create issues inside of those repos that will then again get shown up on this board. So you can track all the work that they'll be doing amongst many other things. + +Tyler Wright: there's a number of items that kind of touch the provider. Some are More ux facing in terms of pricing and provider availability and inventory. So again, we' can always look inside this project roadmap for the product and engineering and again if you have any questions comments we can go from there. + +Tyler Wright: Besides the work that's going to be added from the parade tour team and again you'll see a reflected over the next couple of weeks on this roadmap. There are some other items that will be added to the roadmap soon. But two items that I want to call out today as many have seen on chain. There's a network upgrade that is planned for next Thursday pending boats that is open for voting right now. So if you're validator one of voting in general, please vote, on that Network upgrade functionality and I'll be unlocked. It's just like again more usability for all C. So as I can main reason for the upgrade, but there will be some other things related to again private repos that will be unlocked after the upgrade. + +00:10:00 + +Tyler Wright: As always the validator will go through the network upgrade process first. It'll be tested and make sure that it's stable. It's already been going through testing and sandbox and just a number of members of the core team have done testing. But again, once and made that upgrade happens next Thursday, and there will be a period of just making sure it's stable on Main net after that period has ended there will be a message that will be sent out to Providers to upgrade their nodes. So again, please wait for that announcement before Or doing anything next week. + +Tyler Wright: Outside of that there is one other thing that I think we kind of have touched on previously, but I want to give Scott the opportunity to talk a little bit more about this today. You can see it in testing on the product and Engineering roadmap, but one of the big task S of the core engineering team over the last three weeks has been around build product process updates as well as providers stability in general obviously with the provider incentives and the Akash Network continuing to grow. We're at the point where it's + +Tyler Wright: We've seen growing pains with the provider and stability and working through those growing pains. And we appreciate all the providers that have been helping to again do quick upgrades notice problems. But one of the things that the core team is trying to do at the highest level is just decrease the number of General problems, whether it be through testing which is continued to prove improve, month over month as well as just Figuring out at the highest level, because so much has changed with the provider so much ashamed of the network over the last few years just like going back over and spending a couple of times dedicated a couple of Cycles rather dedicated to really looking at build process really looking at the provider providers stability and fine-tuning any, technical debt. + +Tyler Wright: So again one thing that you see Andre Scott and others working on is around that provider stability. As well as provider Bill process Scott has been working with members of the community to test a new provider build process. And I know that the pretor team is also in line as to what's going on. But Scott, did you want to talk at all about provider Bill processing where it is? Just so this group on this call and those that are listening in later can get update on everything you're working on. + +Scott Carruthers: Sure, so, I guess I'm trying to remember if I have covered this in providers before I may have actually been since our last session that I started to work on this so. Sure my screen here for a second. + +Scott Carruthers: Maybe for some reason + +Tyler Wright: Not yet. + +Tyler Wright: it's popping up. Now we could hit you up now just went away. + +Scott Carruthers: Yeah, okay. Okay. + +Tyler Wright: At least for me. + +Scott Carruthers: I don't know what's going on with me. I mean, I'll try one more time. + +Scott Carruthers: about now + +Andrey Arapov: granted + +Scott Carruthers: are you able to see? + +Tyler Wright: meaning and now it's popular now it's coming up right now. Okay. Yes. + +Scott Carruthers: Yeah, mate seems to be very. unresponsive that okay,… + +Andrey Arapov: Yeah, it works. + +Scott Carruthers: so I'm not sure if there's Okay, I'm not sure if there's a little bit of a delay as I'm going through this but it should be fine either way. so as Tyler said so basically we've created a process that + +Scott Carruthers: allows a lot less friction and they provide a bill process and I would say that this is still in beta. right now and I think this can be heavily used today for lab builds or testnet builds and things of that nature and then we'll announce and also populate and the production documentation when this is ready for Primetime use so this is a engineering site that I Maintain, so this is ta.network. This is very developer focused and probably most in the audience are familiar with this from when I've This site before for different topics. But specifically for what we're talking about today. If you go to Engineers a costume Engineers that XYZ and you go to a cost provider automated build. + +00:15:00 + +Scott Carruthers: you can just read through this document yourself, but there's basically a series of install scripts that will and I describe this in the very Beginning portion or actually, it might be in the provider build section of everything that These scripts will conduct so essentially this is using 3s as the kubernetes cluster and essentially through pre scripts. We can install the characteries cluster along with and then on the worker nodes, we can install the case raise and join it to the cluster and then install persistent storage and GPU drivers and things of that nature and then finally the final build script actually builds the Akash provider, so + +Scott Carruthers: I build a large number of providers as I'm doing code testing. And so using this heavily myself. We've not been able to take the Akash provider Bill process down to a 10 or 15 minute install process. So for any of those that go through the traditional Cube spray. + +Scott Carruthers: methodology you can appreciate being a bill of cluster and 10 or 15 minutes is very powerful. And again, we look forward to being able to use this in production as well to take some of the friction away. So obviously the Prater team is very much focused on this as well and going through a Prater build. It removes a lot of the complexity and s tower mentioned earlier the Prater team and what I'm doing here in the scripts were very much in lockstep in the prettier team is looking at these scripts and are going to implement the same procedures and if they find a cause in their procedures to edit any of these processes then again, we'll be unlocked up and I can + +Scott Carruthers: Modify any of the build processes or the prayer team can modify their bill processes, but we'll ensure that we're in lockstep, but from a very high level we would love for people in the community to experiment with this. I've announced this to a caution ciders and hoping and know that I've got a response from a couple providers that have gone through this without any issues. So yeah, feel free to explore this documentation yourself, but from a very high level, this is a Automated a cost provider Bill process that with the execution of three scripts you can. build the Renaissance cluster you can install GPU persistent storage and any of those ancillary features and then build the actual cost provider itself and it Really extracts away a lot of the complex today. So no for example for GPU providers instead of having to go through. + +Scott Carruthers: And video driver installs and the runtime tool kits and things of that nature that's all abstracted and included within the build script processes. So again, we'll be testing this. Much more thoroughly over the coming. Days and weeks and then eventually release it into production. So yeah, that's basically the intent of this project and this current status. The guy heard a Pam go up. + +Andrey Arapov: Yeah, Scott. + +Scott Carruthers: I'm not looking at the meeting. + +Andrey Arapov: Thank you very much for presentation. It can hear me. + +Scott Carruthers: Yes. Yeah, I can hear you. + +Andrey Arapov: Operation looks very nice this is something that I've been like and we're beginning to join the capture something. I didn't also advocating for the beginning but there are a couple of things we need to focus really on if we want to get it to the production is the upgradeability that we can keep upgrading the cluster result impacts and the availability of such as the etcd database. That is the main ingredient of the kubernetes cluster. You need to check how it's done there in k3s so that in the event if one note is down or their moment laid down the etcd the database where all this information is stored about all config Maps secrets and so on so that there are ways to either restore it so we need to make it up somewhere. + +00:20:00 + +Andrey Arapov: Or that it has, What base of it running somewhere on different notes as well? + +Scott Carruthers: Yeah, and so to that point, I initially built this again to be able to do a code review and as we're writing new go code and the core code base. the other tests are very easily. So that's initially where we're building in and then we'll start to build on top of it as we move this to a production build. Strategy, so as we're going through that I'm adding more and more functionality to this one of the most recent updates that I just announced over the last few days is I've also now added a script to do cluster upgrades. So to be at an upgrade the k3's control plane nodes and worker nodes. This scripts will go through and basically does a analysis of the current version. + +Scott Carruthers: Running in a cost provider and then we'll look at the latest stable version and the k3's GitHub repository. And then if there's a diff between current version and latest stable the script will execute the upgrade. So I've started going through that and that works. Very well as well. So again, this is taking the kubernetes Procedure down to a 10 or 15 second procedure per node. But yeah to Andy's playing obviously that's the whole reason that we want both internal to the core team and within the community why we want this to be more thoroughly tested. We're not going to release this for production use until we've gone through all those Possible concerns so I think we're rapidly approaching that but I'm still some things that we want the community and the core team to test before we recommend this for production use. + +Tyler Wright: Go ahead Deval. + +Scott Carruthers: I'm gonna + +Deval Patel: Yeah, without wanted to add one point here there is a focus on skill ability on our side as well. Right? So when we Use the k3s are focus is on the scalability of the So basically they should be able to go from one node to I mean single note to multiple nodes are easily. + +Scott Carruthers: Yeah, absolutely. And I know that jigar in the fall and I have talked about this sum as well. So that's again something that I'm interested in The Predator team and others within the community testing as well. I think. we're probably all where k3's use over the last couple years as really started to Gain, an adoption and not just for our single node deployments but there's a lot of large Enterprise organizations that are now using k3s and multiple control plane nodes and multiple worker nodes whenever I'm using this is certainly in a multi-node environment, at least with isolated control plane and dedicated worker nodes. So any of the tests I'm doing and this is multi-node. I know the prayer team that shared possible issues that they faced in the past with k3's when it goes beyond a all-in-one node provider. So yeah, I'm + +Scott Carruthers: definitely interested in seeing the prater's teams testing of this over time and hopefully, with some of the advents and You continue to work in the k3's project As I said, I think a lot of those concerns have gone away just based on the amount that I'm seeing K3 is used in Enterprise use, but for a cost provider use specifically obviously very interested in seeing this used in large multinode clusters as well. So yeah, that's definitely one more element that we'll want to more thoroughly test before releasing to production and maybe I could even be a staged approach I think for a long time even going back A couple years ago Andy and I remember a conversation a year and a half ago where we've talked about using k3's for all-in-one node. a cost provider use so this could even be a phased rollout or possibly we + +Scott Carruthers: Recommend, the skirt build process for all-in-one providers, which is somewhat prevalent within our community. So possibly we'll roll this out and recommend this initially for small cluster use and then recommend it for larger. Cluster use as we've tested more thoroughly. + +00:25:00 + +Scott Carruthers: I'm gonna stop sharing now just so that can go back to the meet screen. But again, this will be part of production documentation initially. But if there's anyone on the call or listen to this recording that would like to play around and build a cost provider and 10 minutes and try to put this service Paces. You can currently get to this in a caution Engineers that XYZ and A automated build Tab and go from there. + +Tyler Wright: Thank you very much, Scott. That is actually a great segue to just quickly talk about. + +Tyler Wright: Docs We had a Sig documentation meeting last week or excuse me, a couple days ago during that same documentation meeting. I just want to let everybody that's here. Make sure that they're aware the documentation and this is not the documentation. It's got just reference. That's just an alpha that you all have for a cash cord engineering documentation before it makes it into again the official Doc sites for super experimental stuff with your class that Network slash docs is now + +Tyler Wright: Again under the website repo if anybody had sees any provider related documentation issues or any inconsistencies or anything that the one improve please go to the website repo you can make an issue inside the website repo and tag it documentation and again folks contributors from the community is also from the core team actively look at those issues and look to solve them. I know that recently. And I'll give you an example right now share my screen real real fast. + +Tyler Wright: So again, if you go inside the website repo you can see how to contribute to docs how to change shocks how to add new files. inside of the issues you can see issues that are tagged documentation. Here's an issue as an example that Andre saw where the documentation or Prater build was old and somebody from the community updated this yesterday and this will be merged very soon. So again, if anybody sees any provider related documentation issues where there be related or otherwise, feel free to Get involved inside that website repo again create an issue. You can create a PR if you want or just drop something in sick documentation or providers that references the issue and we'll look to get that in address as soon as possible. + +Tyler Wright: cool Real quick. One other thing. I know that Scott's been working on that touches. A provider is around bid engine scripts. I believe that now going to go as opposed to where it was historically and that's something that again Scott has shared a little bit of alpha in Akash insiders and it is currently on the projects road map. I'm trying to find it real + +Tyler Wright: But Scott, while I'm looking to find this? Is there anything that you want to give an update on as it pertains to the bid engine work? + +Tyler Wright: There we go. + +Scott Carruthers: I'm sure just briefly so as Tyler described this is a providers in the community are very familiar with the current Bachelor script that we use for dedicated or customized bit engine. So basically we're taking the current best shell script and converted to go so + +Scott Carruthers: Largely been complete for several weeks and I just needed a test environment to be able to test it against them. So just some current internal. Dev environment work that needed to be completed so that's now complete and so basically over the last couple of weeks I've had a development environment the new go logic running in parallel with the current Bachelor script and just doing an analysis to ensure that the price derived is identical. So basically just represent engineering the current best health script and along with one minor hiccup with GPU interfaces and the pricing around those which isn't really a go issue but something that currently the scripts DP on + +00:30:00 + +Scott Carruthers: for some technical reasons, but other than that anything that I throw at the new go Logic equates the exact same pricing as the current best shell script. So there's still some things that we need to work through. I'm very confident and they price derived out of the go logic so that reverse engineering is essentially done. There's still some things that we need to answer on. How people would customize that script and also I've done some testing of white listing and the ability for providers to get dedicated pricing based on the deployment address all that's working. But I think there's the core pieces of actually driving the price. I think we're perfectly in our now all converted to go and could go into production in the very near future and there's just some ancillary cases that we need to software or maybe look for their into so that's basically the effort is taking. + +Scott Carruthers: The logic that previously existed in best shell scripts and converting into go which I think is far easier to reason about especially for anyone. Familiar would go personally. I think the logic of it just and this is anything against the current bash Health script. I think it's work written excellently for what it is. But I just think they logic within the go code is a lot cleaner to look at. So yeah, that's the effort coning. They best sell script in the bid price Go logic. So yeah, hopefully we'll be able to introduce that in the very near future. + +Tyler Wright: Go ahead Andrew. + +Andrey Arapov: Yeah. do you guys want to remove a bit Script support entirely or still there will be this option kept for whoever still wants to customize with engine script because I know there are some providers that they use their own with scripts for instance. I know one provider who sets it so that it doesn't beat on really low CPU or the requests. Let's say minimum 1,000 recourse units and something like that. + +Scott Carruthers: Yeah, so that's what I was referring to and some of those. Cases that I'm very confident that the price derived out of the new go logic is identical to the pricing derived out of the previous shell script. But for those that want to actually customize the scripts we're going to have to solve for that. This hasn't really been discussed. these gray haven't happened yet, but personally I wouldn't see a future where we're going to support both the shell script and they go code. I think alternatively we need to come up with a strategy that would allow for the same type of customization. However, we do that I think it would probably involve them. + +Scott Carruthers: some variable entries are something like that that would so I understand the need and I'm very familiar with the fact that there's some providers that are customizing the bid price script and not bid on a very low resource like point one Bid, so yeah, that's something that we're definitely going to need to solve for but I believe the future would be that this would all be supported in go and then we need to solve for those educes instead of simultaneously about the bachelor script and the code logic, but yes, I'm not really something that has been solve for yet, but I obviously will be sell for before we convert to the go logic. + +Andrey Arapov: Yeah, thanks. I think the easiest to be to just keep the support for the whatever bit script people want to run just in case if they have Corner cases. I don't think it's expensive to just keep this option for the Provider Services that bit script path usually timeout options. It's just my wish and of course it can be discussed. But this is how I view things because there's a lot another point. maybe it's deserves for the engineering discussion of the providers, but the insurance is the apis because they can change but I believe the provider service will be supporting this environment variables anyway, so I guess we are good. Thank you. + +00:35:00 + +Scott Carruthers: yeah, I mean we can definitely have discussions about continuing to support both the shell script and the go logic so yeah. let's have those discussions that my personal preference would be to be able to solve for any of those needs within the go code. However, we need to do that. So for that customization where a user doesn't want to bid on. A sdl that only has 0.1. CPU to be able to solve for that and they Go logic, but yeah, we can have that discussion and maybe we will arrive at the decision that it makes sense to support both. Yeah, we'll have to say + +Andrey Arapov: Yeah, in the beginning at least here's one month. We support both and then we can cut it off something like that. It's in the worst case and if you don't gather enough information from the providers because some kind of keep running their providers and forget about or just not painted enough intention on these things being changed and then when suddenly they realized that something changed, so All right. + +Scott Carruthers: Yeah, yeah, that might be an idea as well to support both for just an intern basis. Yeah, I make sense. + +Andrey Arapov: Open that it's sort of the expensive just to let the provider run a simple script give all the data and script. I understand that it's a bash script not everyone is familiar with bash. But if it's about the structure how things look like there. It's quite easy to shape it into a better look as well, but nevertheless. + +Andrey Arapov: Yes, I don't have any specific point to that except for that. I just like love that, some things that you can really use basically I use the script is a kind of plug-in extension. So, there are a lot of software that you can use different plugins in different languages could be not necessarily a shell script. I think it actually even supports the python or whatever you specify there environment shell as well. So maybe actually if I'm not mistaken, I think it even supports you can just hide the past and you can put the binary in go link compiled and it's plugging and I think it will work because all it does it executes today or script or the binary? It's the standard input and it makes the calculations and just it's out the rate in your kitty per block and I think + +Andrey Arapov: Actually Scott, so I just hit right now this idea so that I don't miss it. Sorry if I take much time, but I think it was checking this out because maybe you can even like your go logic you can create the extension itself that would basically compile it and specify it is a bit script path to a binary and see if it works. I think or maybe a mistaken but just an idea + +Scott Carruthers: That's very much. I'm the see so to summarize just make sure that I understand you correctly the ability to update the go Logic on the same as we would be able to update the bachelor script because it's calling an external go file that… + +Andrey Arapov: Yeah. + +Scott Carruthers: what you mean? Yeah, yeah, so yeah. No, I think I did definitely that's feasible. I literally have not looked into that at all. But yeah, I think that probably would be one path is a continuing to allow. The customization of the script but it's now just in go and set of a bachelor script. So yeah, definitely think that's feasible. + +Andrey Arapov: Yeah, because I think is that then you can just here is a goal Inc version or people don't even need to care about looking into it because then I think we nearly haven't received any Community commits to the big pricing script but what I'm saying, my point is that hey you can either use that or you can use goal link implementation and you will not see any difference except which language you prefer. All you need to set is the proper bus to this binary or JavaScript. Basically, that's it. + +Scott Carruthers: Yeah, that makes sense. + +Tyler Wright: Excellent love that discussion. And did bring up another thing that I just want to touch on and I think damir has done a great job of this in the past. He will start conversations in Discord about specific features and then he will push some of those features over to discussions to get more input from the general Community. If anybody sees I would ask anybody on this call and I asked us with everybody across all calls make your voice is heard on some of these conversations. + +00:40:00 + +Tyler Wright: Whether it be for new features again related to provider just experiences. I know that we were talking I think damir had previously put feature requests around multiple bids on the same single order. I know this is something that Scott's been working on in terms of for the new go bit engine logic. But again, there was also an issue created around this as being tracked. So for those that Again have any thoughts ideas. Please get involved in some of these discussions and this will help drive, + +Tyler Wright: Priority on some of these things, along with just constant conversation in these meetings, because I know that Scott the pre-tor team other members of community often in time attendees meetings here feedback from data center providers smaller community-based providers and then take those insights back into their work. So again, feel free to get involved or stay involved in somebody's discussions and s***, but thank you very much. For the work that you do to start some of these discussions. + +Tyler Wright: All right. We talked about a number of things today doing the providers call. I wanted to see if there's anything else that anybody wants to discuss provide a related. + +Tyler Wright: again, look out for some announcements related to the main net upgrade and how it affects providers. Again. If you have the ability to vote, please vote on the main upgrade. It is planned for next Thursday. If you are looking for a provider audits, please go the community repo and said they cost that work organization and follow the template there. There will be a provider audits working group call. I know that Piper Dev and the team have been working on an automated tool and there will be a call next week Wednesday, I believe. So again, please add that to your calendar. + +Tyler Wright: And yeah, we'll just continue to work together between meetings again if anybody wants to test upgraded way that Scott has built for again building provider, please go to Akash engineering that XYZ and follow documentation. There are reach out in providers for more details. + +Tyler Wright: Both much appreciate everyone's time and about 14 minutes. We will have the Sig client calls where again folks that are building clients on top of Akash Cloud most there are a number of other teams that sometimes join that meeting. But again, feel free to get involved in the state clients call which is happening in again a little under 14 minutes and then steering committee, which is usually the last Thursday the month has been moved to again next Thursday May 2nd following the network upgrade just for timing Much appreciate everyone's time. Let's stay connected in Discord and on GitHub again. Look at the roadmap. If you have any questions about anything we talked about today, but we'll just continue to work together online much appreciate y'all. Talk soon. + +Andrey Arapov: Thank you all. Have a good one. Bye. + +Tyler Wright: Bye. + +Scott Carruthers: Thanks, everyone. + +lukas meilhammer: Dubai + +Jigar Patel: nice guys + +Meeting ended after 00:44:12 👋 + From 0a7f03558f87c94dca542feb620a94770a97e9ed Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Wed, 26 Jun 2024 14:13:24 +0000 Subject: [PATCH 079/138] Create meeting notes for Sig-providers #15 (#591) * Create meeting notes for Sig-providers #15 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 015-2024-03-27.md add transcript chore: add recording Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-providers/meetings/015-2024-03-27.md | 188 +++++++++++++++++++++++ 1 file changed, 188 insertions(+) create mode 100644 sig-providers/meetings/015-2024-03-27.md diff --git a/sig-providers/meetings/015-2024-03-27.md b/sig-providers/meetings/015-2024-03-27.md new file mode 100644 index 00000000..50c0683c --- /dev/null +++ b/sig-providers/meetings/015-2024-03-27.md @@ -0,0 +1,188 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #14 + +## Agenda +- Update from Praetor on all of the work that they have been doing. +- Open Discussion on all things related to Akash Providers. +- Update from Scott on provider feature discovery +- Discussion on provider feature discovery +- Provider Audits Updates + +## Meeting Details +- Date: Wednesday, March 27, 2024 +- Time: 08:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + +## Participants +- Andrew Hare +- Andrey Arapov +- Anil Murty +- B S +- Damir Simpovic +- Dani +- Deathless +- Deval Patel +- Jigar Patel +- Nathan Ward +- Rodrigo Rochin +- Scott Carruthers +- Thomas Greco +- Tyler Wright + +## Meeting notes +- **Welcome and Previous Meeting Recap**: + - Recap of lively discussions from the last meeting on gas fees and provider audits. + - Update on the creation of a working group for provider audits and implementation of provider incentives. + +- **Provider Announcements**: + - **Scott Carruthers**: + - Recent announcements on updating provider attributes to include RAM and interface specifications. + - Importance of updating these attributes to ensure compatibility and accurate bid responses. + - Documentation updates to reflect these changes. + +- **Provider Attributes Updates**: + - **Scott Carruthers**: + - Providers should include RAM and interface tokens in their attributes for better bid specifications. + - Updated the bid price script to accommodate pricing differentiation based on GPU interface. + - **Damir Simpovic**: + - Suggested applying similar logic to processor, memory, and storage attributes. + - **Anil Murty**: + - Explanation of efforts to standardize provider attributes and automate their update through provider inventory service. + - Importance of displaying GPU pricing to potential customers and ongoing work to make this information available. + +- **Provider Audits**: + - **Tyler Wright**: + - Reminder for audited providers to update their contact information. + - Importance of community members spreading this information to ensure all providers are up-to-date. + +- **Praetor Team Update**: + - **Jigar Patel**: + - Ongoing work on feature discovery and addressing provider issues. + - Busy with roadmap tasks and provider support. + +- **Open Discussion**: + - **Tyler Wright**: + - Network upgrades and parameter changes positively impacting gas fees and provider operations. + - Call for community assistance in spreading the word about updates and upgrades. + +- **Closing Remarks**: + - **Tyler Wright**: + - Encouraged attendees to share provider announcements and updates with their networks. + - Mentioned upcoming meetings: Sig clients monthly meeting and steering committee meeting. + +## Action Items +- All Providers to update RAM and interface attributes in their configurations. +- All Providers to Ensure contact information is current for provider audits. +- Core Team to Continue working on GPU pricing page and automation of provider attribute updates. +- Praetor Team to continue support and updates for feature discovery. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to providers monthly meeting number 15 during the provider special interest group folks come from the community come together to talk about all things related to being a provider on We get updates from the page war team, which is a tool that many folks in the community use to build and manage their providers. We talk about any provider related documentation or announcements that have been made over at the last monthly meeting number 14. There was some Lively discussion around some gas fees related to r attributes. There was some conversation about provider audits in general and there has since been a working group created around that + +Tyler Wright: there was some discussion around the provider incentives that is since gone chain passed on chain, and there's a number of folks that have already come on board. I think a nearly even hinted at some of those things at the last six providers meeting were at a meeting since then about some of those relationships. So there's again been a lot of action over the last month in terms. So what's thing going on related to their cash provider? I know that there's been a number of announcements that have been made recently as well related to + +Tyler Wright: Related to the provider. So I know that at the part of today's agenda we could touch on any of the things I talked about the top of a call. We'll check in with the page war team. to see if they have any updates on anything they're in but I do want to start to see if Scott or Andrey want to talk about anything specific related to some of the provider announcements. They've thrown in the chat over the last couple of days. So I will hand it over to Scott Andrey to get us kicked off. We're talking about some of those announcements and then we'll go into the typical agenda. + +Scott Carruthers: Yes, I'll just briefly cover I think the last couple of announcements have been related to attribute So several days ago. We announced to providers that they should begin including. They Ram token and their provider attributes and the reason for that is so if you look at an sdl and you're wants gpus in your bid you define the model and then the deploy or else has the ability to specify a Token or a RAM amount. So the reason that we sent out an announcement recommending that all providers update their attributes would they the ram token? + +Scott Carruthers: Is before that if a deployer decided to include Ram in the sdl and the provider didn't have that attribute defined then the one embed. So we had one announcement to please update mirror. So we had a number of providers that were already using those kind of attributes, but they were typically Only providers that had GPU models that had different ramp specs. So as an example some of our providers that are sourcing a0 Nvidia a100s would have already included those type of attributes because they need to specify if the a100 had 40 or 80 gigs of memory. But then if you had a RTX 30 70 or something like that, that only had one ram footprint providers typically weren't including those attributes. + +Scott Carruthers: But again, we want all the providers to update with the ram token and attributes because if I deployer decides to include that they're deploying with an RTX 37 day, but they find some value including Ram in the dly. So that was one provider attribute update and then last night yesterday we had. a request to request how providers to update their attributes an additional iteration in this time is to include the interface attribute or token, so + +Scott Carruthers: The sdl supports the ability again. This is all GPU related. The sdl allows the ability to include interface model So currently is that's just pcie or xxm. So if a deployer decides to include the interface in their sdl again the provider Like that on that if they have a attribute that includes C interface specification. So those are just a lot there. You can follow the announcements in the Jeep in the provider announcement Channel, but that's been the most significant updates and announcements over the last weekly as all related to provider attributes and ensuring that providers bid when certain specs are included in the sdl some tangential. + +00:05:00 + +Scott Carruthers: I'm updates in those regards and yesterday or this morning included the interface for GPU specifications. if I interface is included in the bid price script now has the logic to do pricing differentiation depending on the interface. So again, you could have a 100 and it could have a pcie bus or interface or I could have a xxm and we should have the ability to do pricing differentiation if they Tenant, or the deployer includes the interface and the sdl so not only do we have the announcement out to Providers to update their attributes, but bid price script has also been updated to again do pricing differentiation based on the interface of the GPU that's included in the STL. so off the top of my head. Those are the most significant announcements also. + +Scott Carruthers: everything that I just talked about from a sdl perspective has been updated and documentation. So we've also had a number of Provider documentation. updates see how the top of my head. Those are the most significant updates. + +Tyler Wright: Thank you very much, Scott. + +Scott Carruthers: does anybody any other providers in the audience have any questions and those regards? + +Scott Carruthers: Okay. + +Tyler Wright: I had damir. + +Damir Simpovic: Hello, everyone. I do have + +Damir Simpovic: I don't know. how important it is to have it implemented right now, but + +Damir Simpovic: I think the same logic would be. really prudent to apply to processor memory + +Damir Simpovic: storage, Etc. So, yeah. just for me. Yeah. + +Scott Carruthers: Yeah, yeah Yeah, so I think there's gonna be a lot of announcements and updates that are Generally in the umbrella feature Discovery. So the other thing. that is very top of mind right now as we want to take out How much manual actions are necessary in this process so feature brought us light years ahead and that you don't have to manually label your nodes any longer for gpus or other We no longer have to specify what type of menuing label nodes for persistent storage type in GPU types, and it's certainly Our intention that we're going to bring those feature discovery. + +Scott Carruthers: Aspects into attributes as So providers won't have to manually Define these attributes. So we're going to be using feature Discovery in the near future to update that and then simply to your point Not only would that be applicable to gpus but it would also be applicable to CPU and memory and so yeah, I think there's going to be a significant amount of feature Discovery related introductions in the outcome in few months + +Scott Carruthers: so that you had your hand raised did you have + +Anil Murty: I think I was going to say some of the things that you said already So yeah, as wrest Scott said basically we've had discussions about standardizing on provider attributes for a really long time. I think I may have included you on some of those discussions as well. There was a document that we started working on a while back trying to collect all the possible attributes that we could think of and come up with a standard naming convention for them as well as a structure in terms of where they sit in the IRT. So we started thinking about that a while back. We never got to actually + +Anil Murty: Implementing and enforcing that across the providers and as we were trying as we were working through and thinking on how we want to do that the provider inventory service came about and so the thinking was rather than having the updated. It'll be really nice if the inventory service could read. the capabilities on the provider automatically and updated for the providers rather than relying on people having to do it manually. So that's basically what the story of this whole thing is and so the reason why this kind of became a little bit of an urgent request this week was Driven privately by as needing to us wanting to come up with a pricing page for gpus. So one of the pieces of feedback we have gotten from a lot of customers in the last few weeks is it's great that you guys have a lot of gpus and when we get on conversations with these customers we show them. Hey robot all these gpus you can know submit a bit request you can get + +00:10:00 + +Anil Murty: a bunch of bids from whole bunch of providers on the network and they're very impressed by all that but the problem is that if somebody comes to the web page, there is no way of knowing that we have all these gpus on the network and they're available for such amazing prices, So what we realized is that we need some way of displaying what the prices specifically of the gpus but in general compute resources on the network are for anybody that comes to the network and typically anybody that comes to a web page, so It's kind of a little bit of an image not emergency. But a kind of an urgent request that we're handling one off just to deal with being able to surface up pricing on gpus and then when you talk about pricing of gpus + +Anil Murty: The type of interface that the cluster has typically PCI versus S6 and 5 or 6 and 4 that makes a significant difference on the price that the provider charges. So that's where these requests are coming in so just to provide a little more context and why number one we decided to handle just these two attributes one off And what's kind of the overall plan going forward, hopefully. Thanks. + +Tyler Wright: I had the ball. + +Deval Patel: Then that would be good for us because then from the provider side we do manage pricing at this point of time, but we do it hard way we store those in database and things and if they do it, let's say if they update their pricing directly on the price script and we don't have track of that. So that's always one issue from our side as well. + +Anil Murty: Yeah, so I think we'll have to check with the Maxi on whether he's able to expose it as an API. He's actually working On that API right now whether it becomes a public API, I think most likely it will be either way. We'll figure out a way to get it to you guys. But one of the challenges essentially just to go a little bit deeper on that is that there is no way today to extract specifically the GPU pricing from a provider directly because number one we don't actually get pricing from the pricing script directly. We only find it out when the provider responds to a big request and when the provider responds to a better request, there's quantifically to the Entire CPU of this memory storage. so max C has been working on a workaround to that he's trying to figure out the lowest. + +Anil Murty: bid request that has gone in with mostly a GPU request and then use the responses to that to figure out what the price of GPS maybe so it's not like a super accurate solution right now and we have improve it but that's kind of where + +Tyler Wright: Excellent. Does anyone have any other questions? Related to what Scott was just talking about. + +Tyler Wright: Cool kind of a natural segue before we again talk again update from the pray to our team. I know that Andy Andrew Andre, excuse me, had put a message in provider announcements about r attributes and excuse me about provider Audits and asking folks to update at least email or an organization if they have So if you have seen that in your audited provider, please look to update or if you're an Insider or somebody's active in the community, please let folks know again. We just want to make sure for things like this. There's a number of folks that go through the upgrades may not be as active and Discord, so they're hard to get a hold of and they may not know what's going on. And so we want to make sure that again folks that are in the community on this call or + +00:15:00 + +Tyler Wright: any other providers that they know or see around Discord or elsewhere know about the most recent information related to upgrades so that again all providers are as up to date as possible and then making sure that there is at least a contact information for audited providers. So that's been added recently to documentation as well as to the provider audit process moving forward Andres or anything specific you want to talk about that or + +Andrey Arapov: I guess nothing from my end. + +Tyler Wright: like other RF + +Andrey Arapov: I put it in announcement. I think it's quite clear there and people already started deleting their provider attributes. So if anyone has any additional questions, they can find me on this card or just Drop messaging providers Channel tag me or some other core member of the team. + +Tyler Wright: Thank you. All right, continuing to move along with the agenda. And again, if anybody has anything they want to talk about feel free to drop it in the chat or we'll talk to the prey to our team real fast. And then feel free to raise your hand after that. But I do want to hand it over to the Creator team. They usually give us an update on a monthly basis on things that they've been working on or just things that they're seeing related to a cost provider so printer team take it away. + +Jigar Patel: Hey guys, good morning. So from the last month as we discussed in last meeting, we are updating all the latest provider update that has the feature Discovery portion it So we gave that update with the recent Sergeant providers. We are very very busy with all the providers solving their issues plus working towards our roadmap as well. So yeah, that's a short update from us and I think so at this point of time, but we'll continue work on it. Thank you. + +Tyler Wright: Thank Again presentation does a great job of answering questions? They see inside the ecosystem pray to our Channel inside of Discord as well as in other channels. So I know that the crater team is very active all over Discord. So Much appreciated feel free to reach out to them or anybody from the core team if you have any questions there. + +Tyler Wright: Again out of the last meeting. We talked a little bit about some of the gas fees some of the things related to provider. I think it was a great Lively discussion on that. There was a network upgrade that happened March 13th that I believed stalls many of those issues as well as there was a parameter change I think came on the network March for 11th that lowered a bit amounts from five akt to 0.5. Akt so some of the Lively discussion that went on at the last providers meeting went into direct actions that have positively affect the network so much appreciated everyone's participation here. + +Tyler Wright: Is there anything that anybody wants to talk about related to the account provider that has been talked about? Quite yet on this call today. + +Tyler Wright: cool + +Tyler Wright: all right, if not then obviously everyone here is very busy. So I don't want to hold you. I know there will be a number of updates that will continue to happen and provider announcements in the providers Channel. I think aniluded to a GPU pricing page that will be added via the working group that cost website very soon. So there'll be announcements. I'm sure there again providers are continuing to come on to the network via provider incentives phase one and more relationships have been had since I know there was event set Nvidia GTC and a cubecon in Paris where conversations continued with various data centers all over that are looking to provide resource on the car. So again conversations are continuing there. as just a general + +00:20:00 + +Tyler Wright: All out and I think we've talked about this previously. But if anybody has any relationships with data centers in Latin America, Australia areas like that where you see kind of less folks generally on the map, even though again the map is continuing to get dots on it all over the world day by day. Please feel free to reach out to myself or somebody from the court team. We're actively always looking for kind of three tier four data centers in amongst many other regions, but certainly in those regions + +Tyler Wright: Cool, there's nothing else that anybody wants to talk about provider related then again. I'll certainly let you go. I would ask that everybody continue to push these messages that you see and provide our announcements out to again various providers that you have relationships with or connections with just to make sure that everybody is using the most up-to-date kind of upgrades and experiences. So again much appreciate everyone's time if anybody has any questions or comments, so they want to feel free to drop those in providers Discord Channel and we could talk about those at the next monthly meeting or between meetings. We'll have the Sig clients monthly meeting is following this in about 36 minutes, or we'll get some updates from + +Tyler Wright: the Maxes and some other folks that are looking to build tools on top of Akash, and then steering committee is planned for tomorrow. It's a normal end of months during committee. So just look after those couple of things. But much appreciate everyone's time today. Hope everyone has a great rest of their day and hope to talk to you all soon. Thank you very much. + +Andrey Arapov: Guitar lesson here on a good one. + +Scott Carruthers: Etc + +Jigar Patel: Thank you so much. + +Rodrigo Rochin: You guys. + +Meeting ended after 00:46:58 👋 + From 9982a12e6ffc8114e46cf4441e1bb35aee957d57 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 26 Jun 2024 10:48:19 -0400 Subject: [PATCH 080/138] sig-providers Update README.md Signed-off-by: Drinkwater --- sig-providers/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sig-providers/README.md b/sig-providers/README.md index f42318dd..08e7b94c 100644 --- a/sig-providers/README.md +++ b/sig-providers/README.md @@ -29,10 +29,10 @@ Provider SIG covers everything pertinent to Providers on Akash Network. This inc | #12 | Wednesday, December 13, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/012-2023-12-13.md)|[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/012-2023-12-13.md#transcript)|[Link](https://ro5kevc2mbgfpzyb7ufa5bor6thecu23sbzrqrham53ivpiljp2q.arweave.net/i7qiVFpgTFfnAf0KDoXR9M5BU1uQcxhE4Gd2ir0LS_U) | #13 | Wednesday, January 24, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/013-2024-01-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/013-2024-01-24.md#transcript) |[Link](https://7jnmboxzie2zlrw5nrmwu7ddgmzxiaywbjvmbx2xpr5qmfss7s3a.arweave.net/-lrAuvlBNZXG3WxZanxjMzN0AxYKasDfV3x7BhZS_LY) | #14 | Wednesday, February 28, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/014-2024-02-28.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/014-2024-02-28.md#transcript) | Coming Soon -| #15| March 27, 2024 08:00 AM PT (Pacific Time) | | | -| #16| April, 2024 08:00 AM PT (Pacific Time) | | | +| #15| March 27, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/015-2024-03-27.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/015-2024-03-27.md#transcript) | Coming Soon +| #16| April, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/016-2024-04-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/016-2024-04-24.md#transcript) | Coming Soon | #17| May, 2024 08:00 AM PT (Pacific Time) | | | -| #18| June, 2024 08:00 AM PT (Pacific Time) | | | +| #18| June 26, 2024 08:00 AM PT (Pacific Time) | | | | #19| July, 2024 08:00 AM PT (Pacific Time) | | | | #20| August, 2024 08:00 AM PT (Pacific Time) | | | | #21| September, 2024 08:00 AM PT (Pacific Time) | | | From 43dec9419d5e0f7da1b5578077378d048c102d90 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 27 Jun 2024 12:40:44 -0400 Subject: [PATCH 081/138] steering committee Create 016-2024-05-06.md (#613) * steering committee Create 016-2024-05-06.md Signed-off-by: Drinkwater * Update 016-2024-05-06.md add recording for meeting Signed-off-by: Drinkwater * Update 016-2024-05-06.md add participants and transcript Signed-off-by: Drinkwater * Update 016-2024-05-06.md add meeting notes and action items Signed-off-by: Drinkwater --------- Signed-off-by: Drinkwater --- committee-steering/meetings/016-2024-05-06.md | 450 ++++++++++++++++++ 1 file changed, 450 insertions(+) create mode 100644 committee-steering/meetings/016-2024-05-06.md diff --git a/committee-steering/meetings/016-2024-05-06.md b/committee-steering/meetings/016-2024-05-06.md new file mode 100644 index 00000000..8ba58472 --- /dev/null +++ b/committee-steering/meetings/016-2024-05-06.md @@ -0,0 +1,450 @@ + +# Akash Network - Steering Committee - Meeting #16 + +## Agenda + +- Review / discuss / address any community feedback, grievances, or conflicts. +- Review [projects list](../projects-list/README.md), prioritize / add / remove if necessary. +- A look at open discussions in [Github Discussions](https://github.com/orgs/akash-network/discussions). +- Open up to any other questions from the community. + +## Meeting Details + +- Date: Thursday, June 6th, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://capv32vqn7vrb5u3qvsjn3n6y6swnjkba32ukvydflmqqhrxbswa.arweave.net/EB9d6rBv6xD2m4Vklu2-x6VmpUEG9UVXAyrZCB43DKw) +- [Transcript](#transcript) + +## Committee + +- Anil Murty, Overclock Labs +- Artur Troian, Overclock Labs +- Greg Osuri, Overclock Labs +- Scott Caruthers, Overclock Labs + +## Participants + +- Amanda Keay +- Andrew Gnatyuk +- Anil Murty +- Artur Troian +- B S +- Bold Panther +- Deval Patel +- Dominikus Brian +- Hiroyuki Kumazawa +- Jigar Patel +- Joao Luna +- Joe +- Julius Haus +- Maxime Beauchamp +- Robert Del Rey +- Rodri R +- Scott Carruthers +- Tyler Wright +- Zach Horn +- Zeke E + + +# Meeting Notes: + +* Tyler talked about the change in schedule for the Steering Committee over the next months +* Tyler went through the agenda for the meetings. The agenda can be found on the Steering Committee readme. + + +### [Product and Engineering Board / Community + Marketing Board](https://github.com/orgs/akash-network/projects) + +- Tyler talked at a high level about the Mainnet 12 Upgrade. +- Artur shared some details around the Mainnet 12 upgrade including unlock of the fee grant module that will fully enable functionality. +- There are no API or state changes. +- Artur talked about transition to Cosmos SDK 47. This is a big item, with many steps. The core engineering team discussed plans and roadmap. +- Artur talked about the Akash SDK, which will be coming in the future. There will be documentation changes to improve process around Akash API, including examples. The new SDK will be defined in multiple steps, after Cosmos SDK 47. +- Cosmos SDK 47 upgrade is planned for end of summer or early fall. There will be many updates coming over the summer. Please come to sig-chain to learn more. +- Artur mentioned that the core engineering team is continuing to work on stability of the provider. +- Scott talked about the Provider Build improvements. Core engineering team have been testing new k3s provider build path. Feel free to test this new path, if you desire. Please join the providers discord channel for more information. +- Anil mentioned that the Console 2.0 effort is being kicked off. Cloudmos is rebranded to Console, and there are a number of features that are being worked on. +- Anil mentioned that the user experience for people to get started is a big focus. +- Anil mentioned that other focuses include a VM like experience for developers that are used to that experience. +- Anil talked about the HoomanHQ team which is working on the CI/CD solution for Console. +- Updates will happen in the sig-clients bi monthly meeting. +- Tyler talked about the wg-provider-audits meeting around the work from Piber Dev and his team for the automated auditor. +- Tyler also talked about the work from Mystic Labs around the metamask cosmokit integration. + +#### [Community and Marketing](https://github.com/orgs/akash-network/projects/6): + +- Tyler reminded everyone that Adam Wozney, Head of Community, is out for paternity leave. Amanda will be leading efforts on the events side. +- Tyler and Zach talked about Akash Accelerate 2024 and Consensus 2024, which have happenned since the last Akash Steering Committee meeting. +- 1400 signups for Akash Accelerate 2024. Over 400 people showed. There were great speakers and great connections made. +- Consensus 2024 was also a success. There were a lot of great connections. There were a number of side events at Consensus 2024. +- Tyler talked about the Hackathon as well. Results can be found here: https://dorahacks.io/hackathon/akashathon2/detail +- Rodri asked if there was any news on Brussels? +- Akash will have a large presence in Brussels. Akash is hosting a number of side events, and Greg will be speaking all over Brussels. +- Tyler talked about bounties highlighting documentation, website, and design as key areas for participation thus far. +- Robert gave a Zealy update. + + +### Github Discussions: + +- Tyler asked the Akash Community to get involved in discussions and make their voices heard. + + +### Open Discussion + +- Domi asked about some of the longer term goals for Console 2.0. + +### Action Items: + +- Follow up around Cosmos SDK 47 upgrade plan. +- Continue prep for events in Brussels. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the steering committee monthly meeting. It's June 6 2024 Usually the steering committee monthly meetings are at the end of each month, but with so much going on in terms of events. Again. The last two have been pushed out to the beginning of the following month. For those that are trying to track all things related to the steering committee again the notes and the transcripts and the recordings can be found in GitHub inside the community repo with specific links relative to each meeting. You can also find the agenda or again the steering committee, which we will go through here today. + +Tyler Wright: If anybody has any specific items that they want to add to the open discussions at the end of the agenda again, feel free to drop those in chat. If anybody wants to talk about a discussion that they've brought forth in the GitHub discussions again, feel free to drop that GitHub discussion in chat as well so that we can make sure that we touch on it. + +Tyler Wright: cool Her usual, we always start off the agenda trying to see if there's any review discussion or do we want to address anything Community feedback Credence to grievances or conflicts related to the cigs and working group structure. Does anybody from the community on this call have anything related to cigs or working groups that they want to discuss here today? + +Tyler Wright: Real quick for me, and I've already started to address this with some of the cigs and working groups. + +Tyler Wright: Because of participation in some cigs being very small and updates kind of being the same month over month. one of the things that I've been thinking about with other members of overclock and other members of the community is a slight restructure to the states and working groups. They've been very successful over the Inception purse for bringing people together for transparency across ideas that members of the core team are working on as well as project members of the community are working on but again from a Cadence standpoint. We are going to change a Cadence of some states and working groups and there might also be a merger of some things and working groups. So again, look out for messages in Discord, if anybody wants to get involved in a specific working group and needs more information, feel free to reach out to myself or just again, there's an entire section in the Cosh Discord where a lot of conversations + +Tyler Wright: ongoing + +Tyler Wright: So again, look out for announcements there. The one thing I'll always remind folks of is if anybody is looking for information on timing for cigs and working groups. The best source of Truth is always the website where again on the calendars page. There is a Akash Network Community groups kind of a calendar section and you can track all the specific events that are happening across six and working groups as items move again announcements will be made in specific channels. But again, that's a great source of Truth for anybody that's looking to get involved. It's there to date on all things special description working groups. Anyone have any questions on that before I continue on with the rest of the steering committee agenda? + +00:05:00 + +Tyler Wright: Much appreciate all those that have attended and contributed to discussions and get involved. So again, it goes a long way in keeping folks within the core team other teams that are building on top of a cost Network in just a general Community aligned on, goals missions projects Etc so much appreciate all those that watch the videos read the transcripts. Look at the notes attend the meeting Etc. + +Tyler Wright: All right moving on the next item that gets worked on. I guess just discussed during these meetings is the projects list inside the Akash Network organization and projects. There's two projects boards one for product and Engineering which has a roadmap across again. All things being worked on by the overclock product team as well as overclock engineering team and other members of the community that have community pool support or just generally working on things that get added to that board as well as the Akash community and marketing initiative sport. So as we normally do I'm going to because I want to spend a little more time talking about all the community and marketing initiatives. We can start off with the product and Engineering roadmap to begin with one big item that I will touch on before. + +Tyler Wright: I handed over to Archer is around the main net 12 upgrade as many of that are active participants in voters. there's a proposal rather on chain for Mania twelve upgrade. I let Archer discuss a little bit more about what that upgrade entails. + +Artur Troian: To Cosmos sdk47. + +Tyler Wright: But if you have the ability to vote and… + +Artur Troian: So this is quite substantial change as well as pretty big item in terms of work that needs to be done here team has mats two weeks ago to discussion plans… + +Tyler Wright: haven't yet, please do vote again. I'll drop the proposal in chat. I'll pass it over to Artur. Scott's to if they want to talk a little bit about the main Network upgrade and where things are today. + +Artur Troian: what we're gonna do how you're gonna do and + +Artur Troian: roadmap to this part and we have a couple items that we're still cleaning up and we should be able to update all the issue. I think the support to four about all through the work that needs to be done. But summarize it. First of all you have the entire stack to the Social Security bring us quite a few nice features like that was proposals and so forth. It brings the ABC to most updated versions and believe seven, but the biggest change from perspective World Akash is we are transitioning to allow more developers ease of use of the eye which + +Artur Troian: One word is we are trying to create I know many people don't like this abbreviation by SDK. So right now imagine a cost to cars from third-party services is a little bit hard due to documentation is I would say + +Artur Troian: Creators focused I mean core team instead of developers focused. so what we are doing the stage is + +Artur Troian: identifying what are the complex entry points into a cautious Decay and how we can fix them and then we're gonna buy the presentation a lot of that. So we're not saying the documentation is going to be changed significantly, but we are just, construction needs making sure that all the aspects of the API are covered document as well have examples and so forth. They're not a big items related to that is we are switching to vanity URLs for going modules. So for example, actually Pi report reminds their GitHub, but actual go more goes gonna be having different names purchase dedicated to mind for that and it's all been already working and you can track all the progress related to this particular transition in support issue. + +00:10:00 + +Artur Troian: the SDK for too much I would say. The stage of development of that is going to be defined in multiple Steps step. Number one is as soon as we wrap all the requirements up and have put above generation migrated to the cosmos SDK for seven. You're gonna talk to a couple clients that use API and + +Artur Troian: Ask for their feedback as soon as we get that then we transition to upgrades actual blockchain codebase or the responsnet and let everyone tested. Did you take a few weeks maybe a month? And as soon as we got all the Box make sure that the actual upgrade is fine and the API is stable. You're gonna upgrade sandbox, let it tests one more time and then move one to prepare for the actual minute. I'm great. So that's because multiplication migration as a main ad is going to happen. No earlier than end of the summer maybe even actually + +Artur Troian: Autumn time so it's still trying to figure out when but as this entire task is quite complicated. It's really hard to do some predictions on when we gonna do our clone. Right as this is going to be massive State migration. We need to develop your guidelines for especially validators to make sure that they are prepared in terms of Hardware. So the size of the ramp for example is really crucial for this before think. We gonna try to keep you updated on the actual steps and the milestones in regards of this transition. Hopefully next couple weeks. We wrap everything up and the next six chain will be able to move on. + +Artur Troian: I think it's from the location perspective and the provider side is you continue to work on which machine pro instantility of the provider and making sure that it is ready for SDK immigration as well. As the immigration brings quite a lot of API changes obviously affects provider as well as the manufact parts. So that means you're gonna have to have implemented migration for the provider side as well. And we don't have clear definition of that yet. We will be Taking this to action as soon as we please. Look at freeze on the SDK any questions + +Artur Troian: Right Tyler back to you. + +Tyler Wright: Thank you Archer. And again, I think that's a great shout out to all those that are looking to get more involved and understanding, the migration to a customer specific k47 or however that route continues to evolve. Please feel free to join the same chain meetings are a couple of new folks from other Cosmos projects that again are getting involved trying to understand and trying to support so if anybody wants to help with testing wants to help with ideation again, feel free to drop a message in Sig chain, that'll be the main focus of those discussions around again, making sure validators are tuned up and making sure that the migration is properly tested. So if you want to be involved in that process Sig chain, it's a place to get involved as we look forward in the next couple of months. So look out for updates there. + +Tyler Wright: Again, I know Artur just touched on and we've been touching on this both in sick providers in a previous steering committee readings around all the work that Scott Jigger Deval Andrea and… + +Scott Carruthers: yeah, and so for anyone that's not familiar we came up with as Tyler alluded to some build scripts that can take the Akash provider Bill process from a matter of a two-hour build down to a 10 to 15 minute build and… + +Tyler Wright: others are doing around provider build process and supporting the testing. There's also been members of the community both here on the call seek providers and… + +Scott Carruthers: that includes even… + +Tyler Wright: elsewhere that have also been testing this new provider Bill process Scott. + +Scott Carruthers: if you're have a GPU provider with a GPU driver installs… + +00:15:00 + +Tyler Wright: Don't feel oblige. + +Scott Carruthers: runtime environments and… + +Tyler Wright: You could just thumbs up… + +Scott Carruthers: all that is boiled down to a 10 or… + +Tyler Wright: if you want but is there anything specific that you want to call out? + +Scott Carruthers: 15 minute process has been tested essentially by the core team as we Build providers and… + +Tyler Wright: That might be an update on all things provided build processes still in testing? + +Scott Carruthers: clusters for code testing. So it's very well tested and now the Prater team jigarh and Deval have been testing. Thoroughly as well. So we're now in the stage of testing, durability of ensuring the STD cluster and things like that remain stable and I key threes build. So this is using these build scripts use k3's instead of our traditional Cube spray AIDS methodology. So yeah, we definitely encourage the community to engage in testing and let us know if there's any features that you would like added or if you run into any issues. + +Tyler Wright: If anybody has any questions, feel free to get active in the providers Channel as well as sick providers Channel where again a number of folks in the community are continuing to test and again as announcements. I'm getting made about Creator again. Look out for the ecosystem Predator Channel and all the work that Jigger and Deval also the provided build process and then obviously all the work they're doing on the Predator tool. + +Tyler Wright: Cool, that is a little bit of a natural segue. I don't want to call out all the things that the product team has been working on, but I did want to see if there's anything again the product team has done a great job. + +Tyler Wright: The max is jigarette the ball and Neil arm and everybody else that's working on Everything console related row. There's other again members of the community as well. I don't want to call out everybody Go ahead and Neil. + +Anil Murty: yeah, so the big thing that people need to be aware of is that We're kicking off… + +Tyler Wright: but it's a big team of folks that are consistently working on Console a number of other efforts and… + +Anil Murty: what we're calling essentially the console 2.0. + +Tyler Wright: have been doing a great job of sharing some of those updates and… + +Anil Murty: Effort and roadmap. So what that is is basically Cloud Moses obviously now rebranded to console. + +Tyler Wright: sharing some of the backlog and adding to the roadmap. I just want to see if there's anything that anybody wanted to call out that is currently working on product. + +Anil Murty: And there's a bunch of significant initiatives that we're going forward to summarize it broadly around. + +Tyler Wright: Obviously again, people can stay up to date on all things product and the road map here, but I just want to see… + +Tyler Wright: if anybody from Max or… + +Anil Murty: Improve or… + +Anil Murty: reducing fiction the people getting started on Console. + +Tyler Wright: anybody else want to call it anything specifically here today. + +Anil Murty: So that includes eliminating the need for or… + +Tyler Wright: Do not feel a blast… + +Anil Murty: giving people the option to use credit cards instead of wallets will always be supported… + +Tyler Wright: if you don't want to. + +Anil Murty: but offering the options credit cards alongside wallets is the second big initiatives around improving developer experience for people wanting to transition from using some other service to using Akash and that typically falls under sort of two or three buckets of developers so developers are coming from Traditional cloud services like gcp Azure and need a device. + +00:20:00 + +Tyler Wright: Thank you very much, India. Again, if anybody has any questions, feel free to drop those in the Sig clients Discord channel marker calendars for the sick clients meeting. I think we change a Cadence of that to buy every other month. So again, feel free to mark your calendars and make sure you join this one where we're talking. I'm sure they'll be a lot of conversation about console 2.0 the roadmap in specifics and then again ways for other people to get involved. So look out for that coming soon. + +Tyler Wright: I know there's a number of initiatives that are being worked on by folks in the community as well as by folks in the core team. I will call out to know Piper dev has been working on the automated auditor with open source tooling. There is a working group session for that on June 13th next Thursday, I believe. So again that's on the working that's on the Akash community group calendar. There's also another team Mystic Labs that previously was working on some Cosmo kit meta mask work on they got some community pool funding that team has been diligently letting folks in the community and letting folks from overclock know of their progress they are currently in testing right now and again once they're finished testing and they will get the rest of those funds but they have been again great stewards of those funds making sure that all the work is done and + +Tyler Wright: live before claiming fun. So again, those are also being tracked as well. Is there anything else on the product and Engineering roadmap that anybody wants to discuss right here while we're alive? + +Tyler Wright: cool If not, then we can jump ahead to the community and marketing initiatives. There's a number of things that I want to talk about and I'll pass it over to Zach and others to talk a little bit more detail. One thing. I will remind folks here on the call is Adam bossney who's ahead of community is? + +Tyler Wright: That one more time. I'm sorry. + +Tyler Wright: Yes, we'll talk about that actually in a brief second because that's actually in progress column if there's not an update here during the call because I don't think Amanda's here. She's traveling to some live events that are happening today in this upcoming weekend. We'll get an update soon. But before we jump into Brussels were ECC and a number of other events where we'll have a cash wrapper presentation set. I do want to go back… + +Tyler Wright: Going on fraternity leave and… + +Tyler Wright: since our last steering committee meeting Akash,… + +Tyler Wright: so he will be significantly less responsive than he normally is. + +Tyler Wright: accelerate 2024 has happened as well as consensus 2024. + +Tyler Wright: I think he's made announcements in Discord and… + +Tyler Wright: We touch a little bit about consensus 2024 and… + +Tyler Wright: other channels again to help with the vents Amanda who's been helping out significantly with the cost accelerate consensus and… + +Tyler Wright: the State Community or inside our office hours. I do want to kick it over to Zach to talk a little bit about a costume… + +Tyler Wright: will continue to support events through the summer while Adam is out is going to be managing and… + +Tyler Wright: because I know and again anybody else that was live there feel free to chime in… + +Tyler Wright: owning those efforts in terms of community efforts. + +Tyler Wright: but again,… + +Tyler Wright: Again, the Insiders are doing such a great job of almost being self-sufficient. there was so much that went into cost accelerator. We're going to continue on with the inside our office hours and there'll be a collective effort between myself Zach Scott Scott both Scott's and many others on the overclock team to try to serve as the poorest version of Adam Watson. 24 and so I just want to highlight what's happened and where we are today. So ach. If you have a second feel free to talk about our cost accelerating consensus if you don't mind. + +Tyler Wright: + +Tyler Wright: + +00:25:00 + +Zach Horn: Yeah, of course. So just a quick update on how Akash accelerate went and… + +Tyler Wright: So again while he's gone, + +Zach Horn: how consensus went because we did pull Community fundings for those things across accelerate was great. + +Tyler Wright: if you have any questions, feel free to reach out to any one of us, + +Zach Horn: I mean, it's our first event of that size that we posted,… + +Tyler Wright: but again, we'll look to keep + +Zach Horn: with full production and… + +Tyler Wright: You thriving while he's gone. + +Zach Horn: promoting it to that degree. + +Tyler Wright: And again if anybody has any thoughts or… + +Zach Horn: We had hundreds of people show up. + +Tyler Wright: questions about anything whether it be teacher events Etc. + +Zach Horn: I mean, I think the total signups were about 1400 we had about 400 or… + +Tyler Wright: Feel free to reach up. Go ahead rodri. + +Zach Horn: so that actually showed up roughly in that 25% plus range attendance. And overall, I mean it was great. there's a lot of learnings that go into these things and getting over the road bumps and putting everything together. But largely the consensus among everyone that was there. No pun intended on consensus is That it was really good. The connections were high quality. The turnout was excellent. I'm sure you guys saw some of the footage that we got from the speakers. Obviously, Eric Voorhees SRI Ram is a professor at UT Austin some really really high quality content came out of it. That's on the on the consensus side. we had the booth of the main venue. That was really great. We had the Insiders who were there, the folks from crador who know the overclock team. Lots of great connections there. I mean the Highlight in my mind from consensus was + +Zach Horn: simply that we had this booth and we had people coming up to the booth. Lots of people wanted to connect and we could have a minute to walk people through the network and really engage on a deeper level. I thought that was excellent. We also did a number of side events, around consensus. That was run by Amanda for the large part. Those went really well too. So, I mean we hosted I think five or so for five around consensus turn out for those was equally as quality as accelerate was so On the whole I would say it was a really excellent outing for us. Accelerate was excellent consensus was excellent the side events were So Really positive on the whole. I know there's a couple people on this call who were there as well. If you guys want to jump in What did you guys think? I know Anil was there? You want to jump in quickly? + +Zach Horn: And if not, no worries. + +Tyler Wright: Yeah, as I was I was there myself and… + +Zach Horn: Yeah. + +Tyler Wright: I think one thing besides obviously meeting members to the core members of the community that I hadn't met in real life but have been working with for so long was great. But again the venue and there were three venues total for a Kash accelerate all three were filled up at one point, and again it was great to see so many people in real life that took time out of their day to make sure that they were at the Cox accelerated event again consensus was great. I was only there for half of a day but on the Cox accelerated front so many people knew about it. There's some engaged with so many people that are looking to build on top of it and it's just great to connect with them in person because then you can see the excitement in their eye and you can pass some resources and you have a direct line to them which sometimes they've lost when folks are just in Discord and maybe too shy to ask + +Tyler Wright: Specific questions, but again, I think there's going to be a lot of positives that come out to a cost accelerating consensus very similar to what's happened out of eat them for some of the other more recent events. + +Tyler Wright: Thank you very much Zach again. I'm sure there will be a number of follow-up pieces of the content. I know that Dennis's not here at this meeting. I don't think because he's not allowed to go outside until he does some initial edits Robert we might be calling upon you to help support that as well. But again, there will be a lot of content that comes out of a classic celebrate as well as consensus both from the community members of the core team as well as the AV teams that was tasked with working on it. So look out for more content and follow coming soon. + +Tyler Wright: And I do want to shout out all the people that attended and hosted watch parties broadcast accelerate for the live stream. I know there was watch parties. I think all over the world, which is really exciting to see and just witness so major shout out to all the people that hosted and attended those events. And again as we can continue to push as many of those people into Discord and then into various conversations with insiders vanguards and members of the core team to get folks contributing as quickly as possible. It's just gonna further improve and improve the community. So shout out to all + +00:30:00 + +Tyler Wright: All Next up is the akashathon one thing that has happened. I believe the cash packathon happened ended on. May 17th judging took place there was a demo where again a bunch of participants that wanted to show off their work. We're able to Showcase it live to the judges. + +Tyler Wright: winners have been chosen and have been paid out. I'll drop in the link to the results in the track for people but I can't speak very much for Adam but speaking for myself again. I know there was a number of folks that have reached out to me about wanting to participate in this hackathon leading up to the last few days. It didn't seem like there were that many entries but it was very exciting to see so many different teams in individuals working on projects if anybody here was working on anything for the cops upon and wants to talk about next that's how they move forward again. Feel free to reach out to me but there were so many interesting hackathon projects again, feel free to look at the Biddle and look at door hacks to learn a little bit more about some of the projects. I know some people are continuing to develop those products even after the hackathon but again major, + +Tyler Wright: Out to all those that were involved in managing the meetups and events during the hackathon shout out Robert. I know who was also doing that both that got judges. Thank you to all the judges that quickly turned around looking at all the hackathon projects. But again, I think there was a number of interesting projects and there's a lot to look forward to as we continue to move forward. So just want to shout that out real fast. + +Tyler Wright: All right, continuing to move along Roger kind of alluded to it. One of the big events. Next up on the calendar is happening ECC and Brussels believe there's a number of side events that are also going to be happening Greg. I think as a number of speaking opportunities laws out there and their class network will do be doing a number of side events and hosting some of the other supporting events that are going on there if anybody wants to get involved in attending whether it's inside or otherwise again, there is a form in inside of his Discord channel for those that may want to attend live those decisions will be made over the next couple of days. Okay, perfect. + +Tyler Wright: One thing that again out I'll call out is a number of bounties. We try to put as many of these Bounties in the bounty hunters areas possible,… + +Tyler Wright: I think that was just talked about and inside our office hours. But again, + +Tyler Wright: but you can see some of these in progress tasks that are being worked on by members of the community and Ben's happening… + +Tyler Wright: there will be a significant more information following around all + +Tyler Wright: + +Tyler Wright: happening… + +Tyler Wright: members of the core team around against Sig documentation happening in Brussels for ECC and… + +Tyler Wright: documentation and some of these other projects that there are some Community Support rewards for those that want to participate happening some of those other Summits that are happening in that area around the same week. I don't have any more details right now. Amanda will provide some more information when she lands I think later today or tomorrow, but just that may not be a good enough to answer for your question Roger. Do you have anything specific that you want to know at this time or is anything that I can pass on to Amanda to make sure she adds in her update? So again, if anybody's looking for a way to participate, please look at the bounty Look at these project boards, feel free to leave a comment under specific issues. And then again join a cigar working group where you can talk live to the team get to know some other folks that are working on things and we can go from there. + +Tyler Wright: Is there anything else on the community or marketing initiatives board that anybody wants to discuss here live today? + +00:35:00 + +Tyler Wright: Go ahead Robert. + +Robert Del Rey: Hi everybody. I'm gonna be a little short. I'm feeling a bit under the weather today. I don't know what happened. But The silly campaign was officially over on June 1st. When you and I reviewed the submissions and we are right now in the process of Distributing the rewards. I also shared yesterday. Some summer stats about the project like how many unique users we got how many submissions? and other stuff + +Robert Del Rey: so by tomorrow we should publish the whole ceiling recap so you can have more data about the Deep if we made our goal if we reach our budget Target and what's the future gonna look like from this campaign? So yeah, expect the post tomorrow and next week actually I wanted to tell you that if it's possible to call off the call for next week, Benji, and I agreed that During the discussion period maybe we can chat in the telegram Channel, but it's not necessarily to join in a biopical at least four for one month. + +Robert Del Rey: and yeah, that's what I want to say about the hackathon. I didn't shining in these about that the hackathon and that we are waiting for Dora hacks to complete some of the payments. Or I also took delivered to arrange a call with George from Dora so we can seek about how the hackathon end. And what are the next step after this? So that's my updates. Yeah. + +Tyler Wright: Thank you very much. Robert. besides throwing those updates and Discord, if you could drop updates around zeely in this marketing ticket number 29 and an updates around the akashathon in community ticket number four 66 that would be greatly appreciated just for transparency across the organization. So that would be again much appreciated and thank you for all the work that you do. + +Tyler Wright: All Is there anything else that anybody wants to discuss discuss related to community and marketing initiatives? Again, take a look at this board in your free time to get updates. I'm sure there will be a number of more updates coming soon from Amanda and other members of the team. + +Tyler Wright: All right, if there's nothing else then again continuing on with the agenda at this point. We're at the part of the agenda. where we review any new GitHub discussions because there are a number of GitHub discussions. We want to make sure that there's a proper vetting process. We've discussed this every month at this point. We do want to ask that anybody that's made discussion and wants to talk about in more detail and is here, please feel free to raise your hand again a number of these discussions. Had come up and GitHub or a student have come up in special interest groups and working groups. We asked that the owner of discussions do their best to try to get folks from the community to participate. But again, there are + +Tyler Wright: not that many new discussions that we are having already. Talked about in some detail. I believe bold Panther is here. + +Tyler Wright: No, he's not here. Are there any discussions that anybody wants to bring up with this group here today? + +00:40:00 + +Tyler Wright: Go ahead Anil. + +Tyler Wright: Robert thank you Anil again. If anybody wants to track the conversations, there's a final proposal that again will get updated as just mentioned by a nail. There's a draft proposal that start off these conversations as well. As a number of Sig clients meetings that you can watch recordings to see demos. There's also a version in awesome It's like a scaled down version and a company blog that should be out soon for folks that one easier way to doctorize some of their stuff. But yeah again, there are more discussions in the draft proposal comments. So again, feel free to look at this train proposals and get up to speed and all think the human HQ game has been talking about and doing with the core product team over the last couple of months. + +Tyler Wright: Terrific. All right, are there any other discussions that anybody wants to bring up right now? + +Tyler Wright: Again, I ask that anybody on this call get please feel free to get involved in discussions make your thoughts and… + +Dominikus Brian: All Thank you. Tyler. Have fun questions about this console 2.0. + +Tyler Wright: opinions here and… + +Dominikus Brian: So originally in the product strategy oracas,… + +Tyler Wright: feel free to ask any questions. I'm sure there's many people in the community that have the same sort of questions,… + +Dominikus Brian: I saw there is this idea of having HPC kind of environment. + +Tyler Wright: but may not have the time or maybe two uncomfortable to ask. + +Dominikus Brian: Onto akas. + +Tyler Wright: So it does a great deal good to again speak up. + +Dominikus Brian: Will that be something still Beyond? far ahead or… + +Tyler Wright: Go ahead dummy. + +Dominikus Brian: consult 0.0 will start, toward the direction something like work manager like slurm or other stuff. it's what we usually use in the high performance Computing environment. Will that be a In the console 2.0 maybe at the end of it or something like that. Yeah, that's the question. + +Tyler Wright: Thank you. Dummy, go ahead and + +Anil Murty: Yeah, I can take that one hit only so that's a great question. + +Dominikus Brian: Yeah. + +Anil Murty: So we haven't gotten as far as looking into slurm specifically but console 2.0 at least initial goals are like I said before is to privately solve the friction around onboarding crypto as well as non crypto users that are not native to Cosmos so solving The wallet in token problem as well as the developer experience problem for somebody coming from AWS or versatile products today. the only thing we've done really from if you want to call it HPC perspective is Adding support for deploying rate clusters to So there's a blog post for that as well as a template for it. We will look to build something that is more. + +Anil Murty: Native or custom for Rey in the future. I'm talking with the developer that actually worked on that initial template. But if you have ideas around what we can do with learn. I would love to discuss those with you or if you want we can start a discussion on the discussion board as well. I think it's a great idea. + +Dominikus Brian: Thank So in my view, perhaps will come a bit later. But for a time being I'll try to explore what there is this a kubernetes are pretty good enough. I mean for you have a worker note must not and things like that, but for heavier job, there will be tough because you need to keep shuffling information here and there and it's not good, but I'll try first and when will + +Dominikus Brian: I mean the kind of things that doesn't work in this current environment and let's see whether things can be improved later on. But for now, I think this planning for this console 2.0 is exciting one more question before we end perhaps is whether in the 2.0 fashion will still pretty much stuck with Docker or is there other options that you can deploy directly bypassing the need of having a instance public docker. + +00:45:00 + +Anil Murty: Yeah, I can take that one as So yes for now. We'll just stick with Docker we have in the past at some discussions around the idea of micro VMS, but that doesn't progress very far. If you have some thoughts again around that happy to have a discussion about it as well. But now just Docker and what we're trying to do is one of the issues you'll see in the product roadmap is trying to give people experience but with Docker containers by essentially. Taking their public SSH Keys including them in the docker image and then letting them SSH into it, but there's no plans to actually get micro VMS in the near-term world map. And part of the reason is because we just have enough things just to solve from a basic, Reliability and redundancy perspective. So for example + +Anil Murty: outside of the developer experience stuff that we talked about We also have to work on the provider side of things. So one of the things as part of console 2.0 is going to be the pretor team they will and jigar they're going to work on implementing a new front-end for greater and they're going to implement that inside console. and then once that is done, we're going to look at things like + +Anil Murty: being able to select a backup provider that we can redeploy onto if the primary provider was down or the least closest for some reason. looking at pulling in data from automated audits that different team fiber Dev and Benjamin are working on things like that. So some more low-hanging fruits before we go and look at something like micro VMS. But again, if you have ideas or you spent more time researching that area you can certainly have a conversation about it. + +Anil Murty: Yep, and appreciative bringing these up. + +Tyler Wright: Thank you Domi. + +Tyler Wright: Last part of the agenda is around open discussion. Does anybody here on the call have any questions or anything? They want to discuss with the last nine minutes. We have a lot of for this call. + +Tyler Wright: All right. One thing that I can briefly talk about is again just a quick look ahead. Obviously, we have the steering committee here today, which is usually at the end of the month, but again has been moved to the beginning a month the zealing meeting for next week will be removed. But as we look ahead there are a number of items to look forward to obviously Sig chain. we might be postponing this big chain because we just had a recent change where we talked about. Somebody's Network up great things. Look out for announcements there. That will be the same days the main net 12 upgrade as well as sick Community which will be talking about events and all things related to the community think support which we just have last week, but it was postponent week before which is probably a quick meeting during six support meetings the group gets together to look at all things that are awaiting triage. + +Tyler Wright: For support repo is where all things related to the court code base are so again if anybody has want to get involved in understanding the core code base of The max is usually attend that event as well and anybody has anything related to console issues that they want to get involved in or need solving again. We discuss those during six support. A couple other call-outs again Anil mentioned what's going on sick clients of anybody wants to get involved in console 2.0 and learn a little bit more in-depth about what's going on there. Sick clients will be happening. + +00:50:00 + +Tyler Wright: Big economics is another one that has been moved back because the number of stakeholders weren't available this past week, but there's a number of topics that have been shared in a number and there's great active discussion happening in the Sig economics Discord Channel and we'll look to have the most discussions and has some action items kind of that meeting on the 18. So if anybody cares about all economics, staking some of those discussions that you can kind of see in sick economics, feel free to get involved there and then again per usual we have sick providers again analytics, which is a buy monthly meeting and then the steering committee which will happen. + +Tyler Wright: Off Thursday, June 27th. So there may be a couple more sessions that get added for a website working group and some other things. But again, feel free to get involved in a number of these signaling working groups where again we'll be going depth on number of things in real decisions are made and we look to get the community involved. There's committee support rewards in terms of akt available to those that are help that happen to get the time to help. So thank you to all those that are contributing already. Is there anything else that go ahead and deal? + +Tyler Wright: excellent All right, we've come to the end of our agenda again. I'm opened up to General discussion from those here. I appreciate everybody joining here today to know there's been a number of meetings and we're coming off of Kash accelerating consensus. So it's been a very busy period again, if you are a validator slash at voting power, please vote on The Proposal on chain right now as he's Quorum and it did schedule this. + +Tyler Wright: And with that being said the main net 12 upgrade is most likely going to be happening June 11th next Tuesday around 1600 UTC. So please mark your calendar so that we can again continue to have smooth upgraded validators or upgrade first, then we'll make announcements for exchanges and other providers to just upgrade their RPC node. But again, please mark your calendars for June 11th, especially if you're about data. + +Tyler Wright: Again much appreciate everyone's time and energy today again,… + +Robert Del Rey: Thank you, Tyler. Bye. + +Tyler Wright: feel free to get involved in significant working groups between these monthly meetings. Look out for discussion to get involved in discussions and GitHub and will continue to get ready for the meeting upgrade as well as all the other things that we're working on so much appreciate everybody here on the call today everybody listening in and look at the notes later. Hope everyone has a great rest of the day and we will talk online soon as our good friend. Adam says see you in the metaverse. Have a good day everybody. + +Meeting ended after 01:05:46 👋 + From f23d7b387ae1ece569e039d88dcfb10f09f9f092 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 27 Jun 2024 12:41:20 -0400 Subject: [PATCH 082/138] Rename 016-2024-05-06.md to 016-2024-06-06.md Signed-off-by: Drinkwater --- .../meetings/{016-2024-05-06.md => 016-2024-06-06.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename committee-steering/meetings/{016-2024-05-06.md => 016-2024-06-06.md} (100%) diff --git a/committee-steering/meetings/016-2024-05-06.md b/committee-steering/meetings/016-2024-06-06.md similarity index 100% rename from committee-steering/meetings/016-2024-05-06.md rename to committee-steering/meetings/016-2024-06-06.md From e00fb5f80f3e03389f990d1828bd5a2d7d4c5aa1 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 27 Jun 2024 12:41:57 -0400 Subject: [PATCH 083/138] Update 015-2024-05-02.md update date for meeting Signed-off-by: Drinkwater --- committee-steering/meetings/015-2024-05-02.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/meetings/015-2024-05-02.md b/committee-steering/meetings/015-2024-05-02.md index c930b276..cd765861 100644 --- a/committee-steering/meetings/015-2024-05-02.md +++ b/committee-steering/meetings/015-2024-05-02.md @@ -10,7 +10,7 @@ ## Meeting Details -- Date: Thursday, March 28th, 2024 +- Date: Thursday, May 2nd, 2024 - Time: 11:00 AM PT (Pacific Time) - [Recording](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) - [Transcript](#transcript) From a2228dd03b5fedbc61e09017e4a3ad1eb0e7a643 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 27 Jun 2024 12:43:43 -0400 Subject: [PATCH 084/138] Update steering committee README.md add meeting 16 details to the table. Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index 01e570af..f52cb991 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -29,7 +29,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, March 7th, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md#transcript) |[Link](https://aqjulyegruxs4xdwltfkkxqieagkmqc7dcbewovdw2wk7tj72hka.arweave.net/BBNF4IaNLy5cdlzKpV4IIAymQF8Ygks6o7asr80_0dQ) | Thursday, March 28, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md#transcript)|[Link](https://4wprt5kys3oxjr7ihtu2jgx6mshwts7gzsiv2pfr4qypgrp2xywa.arweave.net/5Z8Z9ViW3XTH6DzppJr-ZI9py-bMkV08seQw80X6viw) | Thursday, May 02, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md#transcript) |[Link](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) -| Thursday, June 06, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, June 06, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md) |{link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md#transcript) |[Link](https://capv32vqn7vrb5u3qvsjn3n6y6swnjkba32ukvydflmqqhrxbswa.arweave.net/EB9d6rBv6xD2m4Vklu2-x6VmpUEG9UVXAyrZCB43DKw) | Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, July 25, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, August 29, 2024 11:00 AM PT (Pacific Time) | | | From 766ea3c5a9b8816077e2d3425c337f7210399c26 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 27 Jun 2024 12:44:34 -0400 Subject: [PATCH 085/138] Update steering committee README.md Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index f52cb991..e25967d6 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -29,7 +29,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, March 7th, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md#transcript) |[Link](https://aqjulyegruxs4xdwltfkkxqieagkmqc7dcbewovdw2wk7tj72hka.arweave.net/BBNF4IaNLy5cdlzKpV4IIAymQF8Ygks6o7asr80_0dQ) | Thursday, March 28, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md#transcript)|[Link](https://4wprt5kys3oxjr7ihtu2jgx6mshwts7gzsiv2pfr4qypgrp2xywa.arweave.net/5Z8Z9ViW3XTH6DzppJr-ZI9py-bMkV08seQw80X6viw) | Thursday, May 02, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md#transcript) |[Link](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) -| Thursday, June 06, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md) |{link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md#transcript) |[Link](https://capv32vqn7vrb5u3qvsjn3n6y6swnjkba32ukvydflmqqhrxbswa.arweave.net/EB9d6rBv6xD2m4Vklu2-x6VmpUEG9UVXAyrZCB43DKw) +| Thursday, June 06, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md#transcript) |[Link](https://capv32vqn7vrb5u3qvsjn3n6y6swnjkba32ukvydflmqqhrxbswa.arweave.net/EB9d6rBv6xD2m4Vklu2-x6VmpUEG9UVXAyrZCB43DKw) | Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, July 25, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, August 29, 2024 11:00 AM PT (Pacific Time) | | | From 25295aab461c9056fa68eae40d4bae1f68e00964 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 27 Jun 2024 12:49:49 -0400 Subject: [PATCH 086/138] Update steering committee README.md add items to the agenda Signed-off-by: Drinkwater --- committee-steering/README.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index e25967d6..b721509c 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -40,8 +40,8 @@ The Steering Committee is a special SIG that periodically evaluates the list of ### Typical Agenda -- Review/ discuss/ address any community feedback, greviances or conflicts -- Review [projects list](../projects-list/README.md), prioritize/ add/ remove if necessary +- Review/ discuss/ address any community feedback, greviances or conflicts. +- Review [Akash Project Boards](https://github.com/orgs/akash-network/projects) and prioritize/ add/ remove if necessary. - Review any new [Github Discussions](https://github.com/orgs/akash-network/discussions). - Since we're limited on time, discussion topics and proposals will be chosen based on the following criteria: 1. When was the discussion topic created? (older ones that have not been discussed in SC yet get priority) @@ -49,9 +49,10 @@ The Steering Committee is a special SIG that periodically evaluates the list of 3. What level of engagement has there been on the discussion thread itself? (ones with higher engagement should be prioritized over others). 4. Is the champion of the initiative on this call? (not being there to talk about your proposal means we don't spend time on it). 5. Is the champion someone who is currently active in the community? (generally priority to people that actively participate in other discussions as well is discord and sig/ wg calls) -- Open up to any other questions from the participants +- Open up the floor to any other questions from the participants. +- Look ahead at special interests groups (sigs) and working groups (wgs) for the following month. -## Leadership +## Steering Committee The Steering Commitee is initially comprised of the following members who have the most familiarity with Akash Network but the meetings are public and anyone is welcome to attend and listen-in. From 51e20b70478c72ce44105dfe54c12d16e0988571 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 2 Jul 2024 14:44:56 +0000 Subject: [PATCH 087/138] Create meeting notes for sig-economics #17 (#616) * Create meeting notes for sig-economics #17 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 017-2024-06-18.md add meeting recording and transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-economics/meetings/017-2024-06-18.md | 410 +++++++++++++++++++++++ 1 file changed, 410 insertions(+) create mode 100644 sig-economics/meetings/017-2024-06-18.md diff --git a/sig-economics/meetings/017-2024-06-18.md b/sig-economics/meetings/017-2024-06-18.md new file mode 100644 index 00000000..9836d1b3 --- /dev/null +++ b/sig-economics/meetings/017-2024-06-18.md @@ -0,0 +1,410 @@ +# Akash Network - Economics Special Interest Group (SIG) - Meeting #17 + +## Agenda +- Recap of the previous call (early May) +- Provider incentives update +- Coinbase Learn progress +- Tenant incentives discussion +- DAODAO and Cosmos Wasm integration +- Inflation and staking percentages discussion + +## Meeting Details +- Date: Wednesday, June 18, 2024 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://camg45yyujtsslq5bwquh3pybr3ugqzi27rkdbhxfk3bgej5v5yq.arweave.net/EBhudxiiZykuHQ2hQ-34DHdDQyjX4qGE9yq2ExE9r3E) +- [Transcript](#transcript) + +## Participants +- Andrew Gnatyuk +- Joao Luna +- Robert Del Rey +- Robert Hochmayr +- Robert Koschig +- Rodri R +- Scott Hewitson +- Sean Morris +- Tyler Wright + +## Meeting Notes + +- **Provider Incentives Update:** + - Scott mentioned the progress on the provider incentives dashboard, which is almost complete. + - Action item: Scott to finalize the dashboard in the next few days. + +- **Coinbase Learn:** + - Over 500,000 activations achieved. + - Current budget is still substantial, with future campaigns and quests planned. + - Discussion on the translation of these activations on-chain and the strategy to encourage long-term holding through a staking quest with the Keplr team. + +- **Tenant Incentives:** + - No significant progress on tenant and Sonos. + - Discussion on potential pilot programs to incentivize tenant deployment. + - Update on oWce fixing, allowing for easier deployment. + +- **DAODAO and Cosmos Wasm Integration:** + - Nick Merrill's proposal to add Cosmos Wasm to Akash for community pool tokens vesting and other functionalities. + - Current focus on core functionality; smart contracts integration is a lower priority. + +- **Inflation and Staking Percentages:** + - Discussion about recent Discord discussions on inflation and staking percentages. + - Current APR is approximately 20%, with inflation around 19%. + - Props 240 and 241 adjusted inflation parameters and increased the community pool tax. + - Concerns about high inflation leading to sell pressure and negative price action. + - Scott to run some numbers and continue the discussion in Discord and the next call. + - Discussion on estimated time to reach market cap with current inflation parameters. + - Current projection: September 2030 at 344 million tokens, cap at 388 million. + - Community pool tax (40% of inflation) ensures tokens are locked and released only through governance proposals. + - Emphasis on maintaining a decentralized approach to managing the community pool for long-term health. + +- **Proposal Discussion:** + - Jeremy from Shade Protocol suggested funding a pool on Shade to enable secret AKT transactions. + - Rodri shared his experience with AKT transactions on the Secret dashboard, which were not working in December. + - Scott emphasized the importance of community input and thorough testing before moving forward with proposals. + - Encouragement for Rodri to share his experience in the discussion for better context. + +- **Inflation and Token Dynamics:** + - Sean Morris raised a question about the average tenant lease period, which led to a broader discussion about the need for more detailed metrics to understand token economics better. + - Scott mentioned the importance of tracking lease periods to understand the market dynamics and stickiness of tenant leases. + - Sean was advised to check Sig Analytics for any existing metrics and potentially raise the question there for further analysis. + +- **Additional Listings for AKT:** + - Andrew Gnatyuk asked about the strategy for additional listings of AKT on exchanges. + - Scott emphasized the trade-offs involved in paying for listings and the focus on organic growth. + - Scott mentioned that paying for listings is generally not prioritized, focusing on organic growth and meaningful integrations. + - Major centralized exchanges like Kraken have listed AKT without solicitation, showing organic interest. + - Dex listings are considered case by case, with emphasis on meaningful integrations that provide real value to the ecosystem. + +- **Proposals and Community Involvement:** + - Tyler Wright highlighted the importance of community input in discussions around inflation and staking percentages. + - Acknowledged the global nature of the community and the challenge of aligning meeting times across different time zones. + - Encouraged ongoing discussions in Discord and Sig Analytics for broader community engagement. + +**Closing Remarks:** +- Scott invited any final comments or questions from the attendees. +- Tyler Wright noted the importance of following up on inflation discussions in Discord to ensure inclusivity of community members in different time zones. +- Reminder that meeting notes and recordings are available on GitHub for review and continued discussion. +- Meeting concluded with a reminder to engage in Discord for any ongoing or new discussions. + +## Action Items +**Scott Hewitson:** + - Finalize and share the provider incentives dashboard within the next few days. + - Continue work on future Coinbase Learn campaigns and quests, including the staking quest with the Keplr team. + - Follow up on tenant incentives and potential pilot programs. + - Run numbers on inflation parameters and share in Discord for further discussion. + +**Rodri R:** + - Share experience with AKT transactions on Secret dashboard in the Github discussion thread for better context. + +**Group:** + - Consider Nick Merrill's proposal for Cosmos Wasm integration in future roadmap discussions. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Scott Hewitson: All right, gmgm everybody. Today, we've got the monthly Sig economics call for June 2024. And typically how we run through these is a kind of talk some recap from the last call and then talk through any discussions either and GitHub discussions or in Discord in the cigar economics Channel. We'll talk about any props that have gone up and then touch on any items that anybody else from the community wants to bring up any ideas. literally anything at all becomes an open room. So with that + +Scott Hewitson: so last call. Was early May so it's been a month and a half since we talked a little bit about provider incentives the status on that I said, I was gonna have a dashboard up and ready to go by this call. I've got something built out that a few more things. I wanted to add to it so that I'm gonna take that as action item. I should have that and the next couple days kind of just reporting on what's been committed what's been spent and any full of funds or any context that can give + +Scott Hewitson: I think someone asked a little bit about coinbase learn and any progress on that or data points on that. And again, there's been over 500,000 Activation. So that's 500,000 people who have gone through the flow to learn about it's a good number. and it's still quite a bit of budget left. I think we've suspended one of The learn for now, we're going to do some quests and some future campaigns so that big prop that happened a while ago as being used there. What else we got? So I talked a little bit about tenant and Sonos haven't really made any significant. Movement on that there's been quite a few other things I've been dealing with. + +Scott Hewitson: But the idea essentially is we have this provider centers up. we have these committed pools and for gpus and other resources and then on the other side just like any two-sided Marketplace that incentivize a behavior having some tenant incentives to allow folks to deploy for free test out just an easier way to onboard and get people see in the power of that's unlocked now because of the update to office Basically we fixed it so that we can do it now. But if that does come I anticipate that to be a smaller pilot just to start small and then expand from there. + +Scott Hewitson: Another thing talked about last call Nick Merrill from dowdow came on you talking about adding cosmoism to Akash maybe to help with the vesting of community pool tokens or various other functionality that it would add. I know it requires entertaining accounts and that is not something that we currently have implemented on Akash and it's say it's on the road map, but it's lower priority. I think core team is, focused on the core functionality of Akash before adding kind of the flare to it with smart contracts + +Scott Hewitson: Let's see. What else we talk about. I don't think Andrew is here last time so it didn't get his great five questions that he always asked which we always appreciate and always gets the brain going a little bit. But yeah, that was last call. + +Scott Hewitson: So moving Going into the discussions just the channel and Discord. Yeah, Robert go ahead and anyone feel free to interrupt me at any time. I kind of just had this natural progression, but feel free to stop me at any time. + +Robert Del Rey: All right, I will keep betting All right. So you mentioned a cash has. 500,000 sign up in the coinbase learn but I hear the right beautiful 500,000. + +Scott Hewitson: Yes, yeah. Yeah, they call on activations. Basically it means Yeah. + +Robert Del Rey: Activation. I'm sorry. Wow. + +Scott Hewitson: And that might not translate on chain, because you do that you do it and then you get your tokens on and these are three dollar. This first one was a three dollar quizzes. So about 1.5 million and spend But I said, it might not translate on chain because it's just, three dollars worth of akt and someone's coinbase account. + +00:05:00 + +Robert Del Rey: I can imagine and I would say that not only that. I'm sure that in case they get any ATP. It's gonna happen through coinbase, this home base… + +Scott Hewitson: Sorry. + +Robert Del Rey: who holds the ponds of those learners? + +Scott Hewitson: Correct, correct. + +Robert Del Rey: so that also… + +Scott Hewitson: Yeah, so Immediately. + +Robert Del Rey: what that + +Scott Hewitson: Yeah, so when that prop passed funds were released and those are immediately transferred to coinbase. So they hold a remainder of funds. I have to talk to get an exact amount to see how much is left but there's still Sizable amount for future campaigns and quests. One of them is going to be a staking Quest. I know we've been talking with Kepler team to help with that. So basically it's like hey you get these tokens and you withdraw it and stake and you get more tokens. So incentivizing long-term holding versus just do this and dump. + +Robert Del Rey: Really cool night. Thanks. + +Scott Hewitson: Yeah. + +Scott Hewitson: all right, so going back to so Discord chat since the last call there's a few folks and I don't see any of them. Here is Camille Bob or Sith Lord? No, there's some discussions about inflation and staking percentages. I think right now we're at 20% APR ish in 19 and change on inflation. So there was a prop proposal 240 and 241 changed some inflation parameters on Akash and along with adding, or stepping up the community pool tax. So higher portion of that inflation going to the community pool that can be used for governance proposals for all sorts of different things. So when I did that the idea was to + +Scott Hewitson: by increasing the tax We also increased inflation and that was just to make sure that the actual economics and validators. stayed net even what's happened since I think so that was back in cember. So six months ago what happened has happened since is the ratio bottom number of tokens bonded has gone down. So The inflation amount It's gone higher because how it's set up is basically you have a Target and Target bonded ratio of 67% and when it's below that inflation is higher and then as you reach that and go over it and then inflation goes down so current parameters are 13. The Min is 13% and the max is 20% + +Scott Hewitson: So I know some folks have been concerned about that from the standpoint of price action and people say hey Cosmos tokens. They just have high inflation just cause people to dump I know, the past week. Price action has not been as favorable and there's kind of an overall Market Trend down but it's definitely a concern I wanted to address and if you go back to the original Genesis and unlock schedule, so three four years ago the original calculations. We're supposed to buy this time. We were supposed to have 245 million and tokens and supply. + +Scott Hewitson: Circulating Supply. It's like 240 when we ran the calculations last December it was showing 234 so I say that all Say the original schedule. We're still under This updated one. We're a little over it. I talked with Chang a little bit offline and + +Scott Hewitson: without us saying hey we want to reduce inflation. it's definitely something we're thinking about and if there's concerns broadly, it can be changed with the governance proposal. Anyone can put up that proposal if you need help putting it up. By all means over at this point. I don't know if overclock will we may but yeah, if there's concerns or folks who want to explore that more run the numbers more. I'm happy to help assist in any way. or none of the folks that were talking about that in Discord are here. Is there anyone want to talk about it at all? So inflation parameters or any questions about it. Just want to give anyone an opportunity to voice concerns or bring up ideas or anything else. + +00:10:00 + +Scott Hewitson: Yeah, Robert, go ahead. + +Scott Hewitson: No, definitely appreciate that and it's really been recent within the past year and change that we've had the community pool tax and we weren't really working with the community pool for a while. So the 240 and 241 were put into place kind of, open the faucet a little bit for the community pool. And if you look at the proposals that have passed I mean it's all things that are progressing the network. So yeah, I'm a firm believer of having a healthy community pool. But I also do realize inflation is a little high maybe we feel around a point where the community pool is, sufficient we can dial it back and the other thing you could do too is, reduce inflation and increase tax a little bit more to kind of even things out if people are worried about seeing a 20 + +Scott Hewitson: and staking APR, I know anything over 10 people serve people are it's just I don't know if it's a mental thing or not. But I know some folks don't like to see those high percentage staking aprs and then it also can contribute to some cell pressure as well because they're all right. I've got my tokens and this is all just cherry on the top so I can just sell those and be good. But no, I definitely definitely appreciate the perspective Robert and I tend to agree with you at a healthy community pool is good for the ecosystem at Large. + +Scott Hewitson: All right, if anyone has anything else they want to talk about from inflation. I'll take an action to kind of run some numbers and put it into Discord and we talked about a little bit more next call as well. Andrew what's going on man? + +Andrew Gnatyuk: Yeah. Hey guys, what's up? Hey Hey My to say just a question about the inflation do we have estimated that time when we will reach market cap on our tokens full open Supply with this inflation … + +Scott Hewitson: Hey, hey. + +Andrew Gnatyuk: if going to be like + +Scott Hewitson: Yeah. yeah, let me so I'm going I'm looking at the original Genesis unlock schedule and + +Scott Hewitson: In how that was set up as it has the APR starts high and it gets lower over time there. this one that I'm showing shows September 2030 is at 344. I think we have a cap of 388. So it would be + +Andrew Gnatyuk: Yeah. + +Scott Hewitson: seven eight nine years from now. Depending on they're all parameter changes so you could put inflation to 75% and if it passed governance, it would be at that. But yeah as of right now. we're actually under what the original. the supply estimates were + +00:15:00 + +Andrew Gnatyuk: Got it. Yeah, it's a problem with that. + +Scott Hewitson: yeah. + +Andrew Gnatyuk: Thanks. Thanks. + +Scott Hewitson: but to say it again, I think it's something to look at and we should definitely try to make sure that that is that there's a supply estimates are kind of staying closest to what we were originally intending. + +Andrew Gnatyuk: Yeah, I agree actually think that we have quick decent community pool for now. That's just a concern about basically for the price actions just right because for example the seedlord and this guys are coming from price group. So yeah, eventually they invest in can they just wanted to make sure that not many talking are going into the market on the monster basis. basically look + +Scott Hewitson: Yeah. Yeah. No, I mean, because the community tax of 40% going of that inflation going to the community pool. I mean that's tokens that are not in the open market, right? they to become into the open market. They ask, someone has to put up a community support or Community spend prop that would release those tokens into the market. So even though it's high it's going into a locked pool that can only be unlocked by governance. + +Andrew Gnatyuk: Yep, you got it. + +Scott Hewitson: Which actually I think it's for long term. I know overclock is, we help Steward things, but a community pool. That's the centralized and you can only release funds through governance and the community, I think that's better than having, a bunch of tokens that someone controls so we have,… + +Andrew Gnatyuk: agree + +Scott Hewitson: a bunch of tokens that everybody controls and if you look at the proposals that have passed or not passed as a community at large, I think we did a pretty good job of snuffing out things when it doesn't make sense and pushing things through when it does make sense. + +Scott Hewitson: all right, I'm gonna is anyone have anything else they want to say from the inflation standpoint. If not looking at proposals, so there's been software upgrade proposals but no community pool. there is one right now. So yeah, if you haven't voted on that go vote looks like it went up today actually. + +Scott Hewitson: Yeah, rodri, go ahead. + +Scott Hewitson: Yeah, Thanks for keeping me honest. Time go for it. + +Scott Hewitson: Thank you for that context. I know this is a prop for sixty thousand dollars. talking about the inflation. So this is community pool funds this is something that's going to help the network and the community gets to vote on it. So I think it's a cool thing we have going. It's a really way of operating so yeah. What else we got? Let's see. So yeah, other than that and I don't see any major proposals. + +00:20:00 + +Scott Hewitson: if there's anything else I wanted to chat about. I know. Jeremy from shade protocol. He posted and say economics five minutes before this call has been talking about asking for funds to fund a pool on shade which is built on secret and the rationale is so that people can get akt in a secret manner. Because there is no so you go to secret and then you could buy akt there and it would all happen secretly. + +Scott Hewitson: my opinions on that are I'm open to seeing open it's see things test things out, I try to play Switzerland quite a bit with the proposals, but we'll see maybe Ty we can if he's been waiting for a while. He's been doing all the diligent things that we ask folks before putting up proposals. Maybe we can get him, a minute or two and steering committee to try to propose his idea at the larger community. + +Scott Hewitson: Rodri what's going on? + +Rodri R: just wanted to add to that that I tried buying akt on secret dashboard a few months ago and it was not working. I even posted it in one of our channels. And try to contact the secret team, but I haven't tried it again and didn't receive a confirmation that they made it work. So maybe someone wants to have that too that discussion or if not all at it and if it's already working because I think it was in December or something like that, and it was not working. + +Scott Hewitson: Interesting was that on shade protocol built on a secret or… + +Rodri R: What it was not a shape protocol. + +Scott Hewitson: is it some other decks on speaker? + +Rodri R: It was on secret dashboard. But yeah,… + +Scott Hewitson: Okay. + +Rodri R: maybe on shade is working. I haven't tried it. Maybe I'll give it a try. But I don't think it's available yet. + +Scott Hewitson: Yeah, that's what this proposal is to do is basically take some community pool funds to help see to liquidity pool on shade so that folks can do that. + +Scott Hewitson: But yeah, that would be great. If you could at the very least drop your experience into there because into that discussion, that's discussion 543 because that just helps folks with more context saying hey, I wanted to do this I couldn't so this helps unlock that… + +Rodri R: So for I think shade protocol and… + +Scott Hewitson: then that would be good. + +Rodri R: the secret dashboard they complement each other. So that's why I was sharing this here. + +Scott Hewitson: No, Really? Appreciate that. All That's all I had from a plan standpoint. + +Scott Hewitson: Is there anybody wants to bring up anything at Large? Thai go ahead + +Tyler Wright: I don't have the answer on hand to this. But Sean Morris did drop a question in the chat that was unrelated asking was curious… + +Scott Hewitson: + +Tyler Wright: what the average tenant lease period is + +Scott Hewitson: I don't know that I'm sure there's some stats. I'm like the cloud on the skies. I know because I mean all the data is indexed. But yeah, that would be a good question and Sig analytics and maybe that question has been asked and sea Analytics. + +Sean Morris: Okay, I'll take a look. Thanks. + +Scott Hewitson: Yeah, no worries. + +Scott Hewitson: Yeah, because I do know that Lisa's are being indexed with the cloud listen to indexer. + +Sean Morris: That's sort of my yeah,… + +Scott Hewitson: So if it's not shown and… + +Sean Morris: so that I think the stats stackboard tracks like total outstanding leases,… + +00:25:00 + +Scott Hewitson: stats that network and… + +Sean Morris: but it doesn't do anything about sharing… + +Scott Hewitson: you… + +Sean Morris: which is sort of what I'm more curious about. + +Scott Hewitson: It would be a good metric to track because it shows to the sticking power, if there's leases that are years long versus, there's leases that are five days. Nobody goes past five days. It's probably not a good thing. + +Andrew Gnatyuk: Yeah, yeah client point of discussion as the distance alive community and… + +Scott Hewitson: yeah, no, that's definitely be an interesting metric to check. + +Andrew Gnatyuk: with lots of listings already for akt are we still looking for additional access to list akt to find the pools for that or… + +Scott Hewitson: All Does anyone have any other questions related to Sig economics or tokens or… + +Andrew Gnatyuk: something like that or… + +Scott Hewitson: anything at all, Andrew? my question man. + +Andrew Gnatyuk: additional listings at all, except the major Exchange. That we don't talk about. + +Scott Hewitson: yeah, I'd say I mean no, I mean, yeah, that there's definitely a part of exchange it having exposure right where there's more avenues for people to buy the token. that's better. It's kind of just the trade off of All right, this small exchange and this area wants to charge 300 Grand to have akt listed and you might get a hundred thousand and volume or something from it. So I know from I'll say the core teams focus and kind of like, everything's open source anyone can add it. we're happy to help with any kind of technical integration and technical support but really paying listing fees is not really what we're trying to do at the moment. + +Scott Hewitson: I know there's a few major centralized exchanges that are left that we're not listed on. always trying to see what we can do about those but in general, the pay to play stuff. We haven't really + +Scott Hewitson: entertained as much and then from the deck side. So seating pools with liquidity. It's like this, shade protocol discussion. And I think the question to ask is anytime like something comes in to me. It's like I'll look and All right. This Dex it's built on this chain or that, is it what kind of volume are they doing? it's funny when akt is pumping. Everybody wants to list it like hey, we want to when it's not people aren't trying to list it so I think a lot of these deckses they tried to + +Scott Hewitson: they try to ride the waves as things are going up. + +Scott Hewitson: That being said if there's something more than just liquidity like the shade one because you can't get akt secretly anywhere else and… + +Andrew Gnatyuk: Yep. Got it. + +Scott Hewitson: that would be a more compelling story for me. I'm just one person and just one person on the team. But yeah, I mean if it's a Decks that has, a million BBL and they're asking for a hundred grand of Liquidity, it's like all right, is that using those tokens there? + +Scott Hewitson: I don't know. But yeah, I think yeah in general. We haven't been paying for listings, which I think is a good thing and Dex is kind of case by case. Yeah. + +Scott Hewitson: All Yeah, I know it's like, we all get hit up all the time. Hey, We want to list here and kind of say yeah go for it. + +00:30:00 + +Scott Hewitson: Yeah. + +Scott Hewitson: Yeah, and realistically too it's some of the I think Kraken listed us without even telling anybody so, it does happen. So + +Scott Hewitson: does it really like dex's are exchanges they're making money off of volume. So special if akt volume is going up and there's a lot of trading volume. That's where they can get their trading fee. But yeah as volume goes down, they're not as + +Scott Hewitson: I guess incentivized to Add tokens. + +Tyler Wright: Here real quick. I was just gonna follow up to the question is Sean have anybody has any questions like that? + +Scott Hewitson: Already, does anyone else want to bring up anything at all any ideas any comments? + +Tyler Wright: Feel free to drop them and sick analytics and… + +Scott Hewitson: And … + +Tyler Wright: then members of the core team. + +Scott Hewitson: you could say hey,… + +Tyler Wright: I think Scott you mentioned this… + +Scott Hewitson: we're not running Sig economics. + +Tyler Wright: but members of the core team that are working on the indexer can help with scripts or… + +Scott Hewitson: We could do it better, always looking for ways to improve try to make these very open and… + +Tyler Wright: queries to look for that kind of stuff. + +Scott Hewitson: and welcoming,… + +Tyler Wright: So if there's any other questions on that front again,… + +Scott Hewitson: anyone who is new I think yeah anyone who's new… + +Tyler Wright: feel free to drop in the sick and let us out that Sig meets every other month. So feel free to get engaged there. + +Scott Hewitson: if anyone wants to talk or you… + +Sean Morris: Awesome. Thanks Tyler. + +Scott Hewitson: bring up anything at all. The floor is open. And if not, we can catching the cut things short. We've got another 25 minutes, but if there's not a lot of chatter than we don't have to go the full time. So I'll leave it open One Last Time Ty. + +Scott Hewitson: All I think with that we can conclude today's meeting. I'll give one last chance anybody want to say anything. Doing once go in twice. + +Tyler Wright: Yes, sorry. One thing I will add is I know that a couple of people that were having those discussions around inflation. They are based in parts of the world… + +Scott Hewitson: I saw a hand raise. + +Tyler Wright: where I think it's three o'clock in the morning for them right now. + +Scott Hewitson: I don't know if you were clapping or trying to raise a hand. + +Tyler Wright: So maybe we can follow up with these discussions in the chat and… + +Scott Hewitson: It happens I do that all the… + +Tyler Wright: Discord to make sure that they know that we talked about them and… + +Scott Hewitson: All righty. + +Tyler Wright: we can continue discussion there… + +Scott Hewitson: All thank you everyone for joining we'll have these notes up in there on GitHub on these as a reminder. + +Tyler Wright: because I think again some of these six have participants from all over the planet. So it's hard to get everybody aligned to come to the same meeting time. So again,… + +Scott Hewitson: All these calls are recorded and… + +Tyler Wright: especially Sig economics… + +Scott Hewitson: transcribed and… + +Tyler Wright: if anybody + +Scott Hewitson: we have notes taken for them. + +Tyler Wright: Want to bring up any conversations between meetings in a Discord cut,… + +Scott Hewitson: So if there's anything you want to free review go for it. + +Tyler Wright: that would go a long way. + +Scott Hewitson: And if there's anything you want to drop into Sig economics, feel free can tag whoever I feel like we do pretty good job of getting back to folks. + +Andrew Gnatyuk: Smile right my guys. + +Robert Del Rey: guys + +Scott Hewitson: no, that's a great call out and I'll make sure to post and say economics that we talked about it and they can review the video and ask any other questions. + +Scott Hewitson: Alrighty, I hope everyone has a great rest of your day, and we'll talk soon. Appreciate y'all. + +Meeting ended after 00:33:40 👋 + From 0cc01b855de30dab2f9c63ec03703c2364e35d83 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 2 Jul 2024 14:04:33 -0400 Subject: [PATCH 088/138] sig-economics Update README.md update meeting table to add notes and recording for June meeting Signed-off-by: Drinkwater --- sig-economics/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sig-economics/README.md b/sig-economics/README.md index 1f6d5fef..5e80050c 100644 --- a/sig-economics/README.md +++ b/sig-economics/README.md @@ -26,10 +26,10 @@ Meetings happen every [First Wednesday of the Month](https://calendar.google.com | #12| Wednesday, January 10, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/012-2024-01-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/012-2024-01-10.md#transcript) | [Link](https://gbxszp7zaubg3dskphdcgwpqkjtz3mb3zgtq46ka2yyzzkfij7na.arweave.net/MG8sv_kFAm2OSnnGI1nwUmedsDvJpw55QNYxnKioT9o) | #13| Wednesday, February 07, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/013-2024-02-07.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/013-2024-02-07.md#transcript) | [Link](https://6rzdyy2kxzn4qpilczq7vdvfd52kxb65rk4cnhor32f4cibhkqmq.arweave.net/9HI8Y0q-W8g9CxZh-o6lH3Srh92KuCad0d6LwSAnVBk) | #14| Wednesday, March 06, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/014-2024-03-06.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/014-2024-03-06.md#transcript) | [Link](https://l7relb4v4vhxhw4shqui4iyoyyeqdt6ogwpx2thybmneridemfnq.arweave.net/X-JFh5XlT3PbkjwojiMOxgkBz841n31M-AsaSKBkYVs) -| #15| April 3rd, 2024 10:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/015-2024-04-03.md) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/015-2024-04-03.md#transcript) | Coming Soon +| #15| April 3rd, 2024 10:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/015-2024-04-03.md) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/015-2024-04-03.md#transcript) |[Link](https://445y2d4z2tii6zb3mgio36s2cgvrem3ghe7qjvjtmwfpwsgwzbjq.arweave.net/5zuND5nU0I9kO2GQ7fpaEasSM2Y5PwTVM2WK-0jWyFM) | #16| May 1st, 2024 10:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/016-2024-05-01.md) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/016-2024-05-01.md#transcript) |[Link](https://w6djeix4uozea7pt7fdzqmhenlvt6jf72c4x26cz3brkuboazjsa.arweave.net/t4aSIvyjskB98_lHmDDkaus_JL_QuX14WdhiqgXAymQ) -| #17| June 18th, 2024 10:00 AM PT (Pacific Time) | | | -| #18| July, 2024 10:00 AM PT (Pacific Time) | | | +| #17| June 18th, 2024 10:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/017-2024-06-18.md) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/017-2024-06-18.md#transcript) |[Link](https://camg45yyujtsslq5bwquh3pybr3ugqzi27rkdbhxfk3bgej5v5yq.arweave.net/EBhudxiiZykuHQ2hQ-34DHdDQyjX4qGE9yq2ExE9r3E) +| #18| July 3rd, 2024 10:00 AM PT (Pacific Time) | | | | #19| August, 2024 10:00 AM PT (Pacific Time) | | | | #20| September, 2024 10:00 AM PT (Pacific Time) | | | | #21| October 2024 10:00 AM PT (Pacific Time) | | | From 2c5516d3b99f8a40b252bbe9e8ee18e22870180a Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 2 Jul 2024 17:27:03 -0400 Subject: [PATCH 089/138] community-pool-spend-reporting Create README.md work in progress repo for individuals and teams to report on funds from Akash Community Pool. Signed-off-by: Drinkwater --- community-pool-spend-reporting/README.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 community-pool-spend-reporting/README.md diff --git a/community-pool-spend-reporting/README.md b/community-pool-spend-reporting/README.md new file mode 100644 index 00000000..0d5f41cf --- /dev/null +++ b/community-pool-spend-reporting/README.md @@ -0,0 +1,15 @@ + + +# Akash Network Community Pool Spend Reporting + + +### The Community Pool Spend Reporting Repo is an area where individuals share reporting for all intiatives that have used funds from the Akash Community Pool. + + +## Community Pool Reporting Table + +| Proposal Number | Name | Link to Proposal | Link to Report +| --- | --- | --- | --- | +| --- | --- | --- | --- | +| --- | --- | --- | --- | +| --- | --- | --- | --- | From 3ae0c45030c9021e3cbb4c3cdd2521ba2c14dfe9 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 2 Jul 2024 17:55:08 -0400 Subject: [PATCH 090/138] Update README.md Signed-off-by: Drinkwater --- community-pool-spend-reporting/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community-pool-spend-reporting/README.md b/community-pool-spend-reporting/README.md index 0d5f41cf..3de6a25c 100644 --- a/community-pool-spend-reporting/README.md +++ b/community-pool-spend-reporting/README.md @@ -3,7 +3,7 @@ # Akash Network Community Pool Spend Reporting -### The Community Pool Spend Reporting Repo is an area where individuals share reporting for all intiatives that have used funds from the Akash Community Pool. +### The Community Pool Spend Reporting Repo is an area where individuals / team share reports for all proposals that have used funds from the Akash Network community pool. ## Community Pool Reporting Table From 574b6e123ab394bbfdf3b8016efe1fc14cbe78f4 Mon Sep 17 00:00:00 2001 From: Hewi <121134490+heyhewi@users.noreply.github.com> Date: Tue, 2 Jul 2024 23:02:27 -0500 Subject: [PATCH 091/138] community-pool-spend-reporting Update README.md (#619) --- community-pool-spend-reporting/README.md | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/community-pool-spend-reporting/README.md b/community-pool-spend-reporting/README.md index 3de6a25c..5c2d8181 100644 --- a/community-pool-spend-reporting/README.md +++ b/community-pool-spend-reporting/README.md @@ -3,13 +3,18 @@ # Akash Network Community Pool Spend Reporting -### The Community Pool Spend Reporting Repo is an area where individuals / team share reports for all proposals that have used funds from the Akash Network community pool. +### The Community Pool Spend Reporting Repo is an area where individuals / teams can share reports for all proposals that have used funds from the Akash Network community pool. - -## Community Pool Reporting Table - -| Proposal Number | Name | Link to Proposal | Link to Report -| --- | --- | --- | --- | -| --- | --- | --- | --- | -| --- | --- | --- | --- | -| --- | --- | --- | --- | +## Community Pool Spend Reporting Table +| Proposal Number | Pass Date | Name | Link to Discussions | Link to Proposal | Link to Report | +| --- | --- | --- | --- | --- | --- | +| 260 | July 01 2024 | 2024 Q3 Events Resourcing Proposal | [Link](https://github.com/orgs/akash-network/discussions/380) | [Link](https://www.mintscan.io/akash/proposals/260) | [Link](https://lookerstudio.google.com/u/1/reporting/96c38594-7ec4-4a4f-9128-3feaf3b82ac8/page/BIUND) | +| 259 | July 01 2024 | 2024 Q3 Community Support Proposal | [Link](https://github.com/orgs/akash-network/discussions/394) | [Link](https://www.mintscan.io/akash/proposals/259) | [Link](https://lookerstudio.google.com/u/1/reporting/f12da20a-b5bf-4f80-8a45-ff8861a1473e/page/BIUND) | +| 254 | April 05 2024 | 2024 Q2 Events Resourcing Proposal | [Link](https://github.com/orgs/akash-network/discussions/380) | [Link](https://www.mintscan.io/akash/proposals/254) | [Link](https://lookerstudio.google.com/u/1/reporting/96c38594-7ec4-4a4f-9128-3feaf3b82ac8/page/BIUND) | +| 250 | March 15 2024 | Akash Accelerate 2024 | [Link](https://github.com/orgs/akash-network/discussions/499) | [Link](https://www.mintscan.io/akash/proposals/250) | [Link](https://lookerstudio.google.com/u/1/reporting/b321bc26-970e-4f1a-9863-3200164b0cee/page/BIUND) | +| 246 | February 09 2024 | Akash Network Provider Incentive Pilot | [Link](https://github.com/orgs/akash-network/discussions/448) | [Link](https://www.mintscan.io/akash/proposals/246) | [Link](https://lookerstudio.google.com/u/1/reporting/f2f8fe80-97cd-45cd-bbd0-17826eab5ae5/page/BIUND) | +| 245 | January 23 2024 | 2024 Akash Hackathons Proposal | [Link](https://github.com/orgs/akash-network/discussions/415) | [Link](https://www.mintscan.io/akash/proposals/245) | --- | +| 244 | January 15 2024 | 2024 Q1 Events Resourcing Proposal | [Link](https://github.com/orgs/akash-network/discussions/380) | [Link](https://www.mintscan.io/akash/proposals/244) | [Link](https://lookerstudio.google.com/u/1/reporting/96c38594-7ec4-4a4f-9128-3feaf3b82ac8/page/BIUND) | +| 243 | January 10 2024 | 2024 Q1 Community Support Proposal | [Link](https://github.com/orgs/akash-network/discussions/394) | [Link](https://www.mintscan.io/akash/proposals/243) | [Link](https://lookerstudio.google.com/u/1/reporting/f12da20a-b5bf-4f80-8a45-ff8861a1473e/page/BIUND) | +| --- | --- | --- | --- | --- | --- | +| --- | --- | --- | --- | --- | --- | From 26baa8527beabde0199d9defac492c4576b28290 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Sun, 7 Jul 2024 15:44:47 +0000 Subject: [PATCH 092/138] Create meeting notes for wg-provider-audits #2 (#618) * Create meeting notes for wg-provider-audits #2 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 002-2024-06-13.md add transcript and recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-provider-audit/meetings/002-2024-06-13.md | 411 +++++++++++++++++++ 1 file changed, 411 insertions(+) create mode 100644 wg-provider-audit/meetings/002-2024-06-13.md diff --git a/wg-provider-audit/meetings/002-2024-06-13.md b/wg-provider-audit/meetings/002-2024-06-13.md new file mode 100644 index 00000000..f93bf797 --- /dev/null +++ b/wg-provider-audit/meetings/002-2024-06-13.md @@ -0,0 +1,411 @@ +# Akash Network - Akash Network Provider Attributes Working Group-Meeting #2 + +## Agenda +- Welcome and Introduction +- Project Updates +- Demo of Benchmarking Tool +- High-Level Overview of Provider Auditing +- Next Steps and Planning + +## Meeting Details +- Date: Wednesday, June 13, 2024 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://nergf5caumt4yjgrcif4bb6yxjrq6ftqaj52ge3l63ggj3qqlqaa.arweave.net/aSJi9ECjJ8wk0RILwIfYumMPFnACe6MTa_bMZO4QXAA) +- [Transcript](#transcript) + +## Participants +- Anil Murty +- Benjamin B +- Deathless +- Deval Patel +- Jigar Patel +- Maxime Beauchamp +- oïclid +- Rodri R +- rUqeRT +- Scott Carruthers +- Tyler Wright + +## Meeting Notes + +**Introduction:** +- Tyler Wright welcomed everyone and provided background on the group’s formation. +- Noted issues with previous meeting timings and the availability of meeting notes and transcripts post-meeting. + + + +**Demo of Benchmarking Tool:** +- Benjamin B provided an update and introduced the upcoming demo by Sebastian (rUqeRT). +- The benchmarking tool consists of four main parts: + 1. Indexer - Deploys to various providers. + 2. Benchmark - Runs the actual benchmarks. + 3. Database - Stores the data (using PostgreSQL). + 4. API - Gathers data from the database. +- Demo showcased the deployment process, running benchmarks, storing results, and accessing data via API. +- Example API call to fetch benchmark data for providers was demonstrated. + +**High-Level Overview of Provider Auditing:** +- **Scott Carruthers:** Requested an overview of the provider auditing process and its integration with Cloudmos. +- **rUqeRT:** Explained the use of API for accessing benchmark data and potential for expansion. +- **Benjamin B:** Discussed plans to integrate benchmark results directly on the blockchain and signing benchmarks on-chain. + +**Q&A Session:** +- **Anil Murty:** Asked about the benchmark comparison to a Raspberry Pi and its swappability. + - **rUqeRT:** Confirmed it's possible to swap out the baseline comparison and provided rationale for using Raspberry Pi as a familiar baseline. +- **Deval Patel:** Inquired about the frequency of running benchmarks, handling hardware changes, and displaying benchmark results on provider status pages. + - **Benjamin B:** Confirmed the capability to run benchmarks more frequently and discussed the potential for additional attributes. +- **Tyler Wright:** Clarified the goal of open-sourcing the auditing tools. + - **Benjamin B:** Affirmed the plan to open source the tools and allow others to run them independently. +- **Deval Patel:** Suggested integrating the benchmarking tool as an optional part of core platform engineering for continuous data capture. + - **Benjamin B:** Supported the idea for smaller benchmarks and uptime checks but highlighted challenges with more complex benchmarks like GPUs. + +**Next Steps and Planning:** +- **Benjamin B:** Acknowledged the need for partnerships between auditors and providers for cost-effective benchmarking. +- **KYC Integration:** + - Addressed the withdrawal of the KYC idea in favor of a decentralized trust system inspired by a hackathon submission. + - Suggested multiple trusted entities could sign off on KYC, improving the trust system. + - Discussed implementation strategies and the need for feedback from Scott regarding the best way to enable address-to-address trust sign-offs. +- **Console Integration:** + - Mentioned the plan to either send back funds to the community pool or extend the deadline for integration. + - Clarified the goal of integrating benchmarking results into Cloudmos and console for filtering and selection based on verified attributes and KYC status. +- **Uptime Indicator Clarification:** + - Benjamin B clarified the current uptime indicator in the provider dashboards is based on the provider's ability to interact with the service rather than lease uptime. +- **Future Directions:** + - Anil Murty suggested building a service that runs periodically to increase the number of variables available for users to select providers, considering both price and uptime history. +- **Next Session Planning:** + - **Tyler Wright:** Asked about the timeline for the next demo and narrowing down the direction moving forward. + - **Benjamin B:** Estimated a timeline of 14 to 20 days for the next demo. + - **Tyler Wright:** Agreed to follow up offline to finalize the schedule for the next session. + +**Closing Remarks:** +- Tyler Wright encouraged everyone to continue discussions in the working group for provider audit channel or the specific project tile. +- Benjamin B requested notes and transcript to be sent privately as an additional reference. +- Tyler Wright agreed to share the notes later in the day. + +## Action Items +- **Benjamin B:** Share [links](https://github.com/luxas/benchmark) to the actual benchmark being used in the WG provider channel on Discord. +- **Tyler Wright:** Ensure meeting notes and transcript are posted in the repo for this working group and shared privately with Benjamin B. +- **rUqeRT:** Explore and document how to swap benchmark baselines for future flexibility. +- **All Members:** Review the shared benchmark links and provide feedback or suggestions on potential improvements or additional benchmarks to consider. +- **Benjamin B and Deval Patel:** Discuss the integration of benchmarking tools into the core platform engineering for continuous data capture and notification. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the working group for provider audits. This group came out of a proposal that was put on Chain by piber Dev after conversations in Sig providers pi overdev and the pi 3 team puts together po a discussion that went on GitHub and then proposal that passed on chain for a automated auditing tool and then some other support work that was going into the cloud most indexer. There's been a couple of issues around timing for past meetings. But again, we're here to day to get update to all the work that has gone on since the inaugural meeting. I think which was in early April if anybody wants to track what's been going on again. There is a repo for this working group for provider Audits and you can see + +Tyler Wright: After this meeting the notes and transcripts in the video will be available. Just like the first meeting and just continue to track moving forward. With that said again, there's a couple of members of the community and this has been shared wider. But I do want to kick it over to Benjamin to give us an update. I think since the last update that they provided in on the engineering project board, but Benjamin, I'll kick it over to you and you feel free to share screen and we'll just go from there. + +Benjamin B: Thank you I don't have anything a concise yet. If you want me to make some notes off to this meeting I can write something there. But we have some few points. We want to share with you guys today. And the first one is actually with Sebastian who's going to present the demo of the benchmarking tool. + +Benjamin B: Are you ready for that supposed to? + +rUqeRT: Yeah. So person contacts into … + +Benjamin B: also + +rUqeRT: how the thing is structured. So it's comprised of four different parts like you got. An indexed as we call it. That's the one that actually deploys all of the to the different providers then when you have the actual Benchmark itself. Then we got the database to store everything in we decided on postgresql. and then just an API to that later gather all of the data from the database to let's see, where's the button for sharing screen? + +rUqeRT: Yeah. I found it. + +Tyler Wright: assuming that if you can see there's a ation, perfect + +rUqeRT: So can everyone see this? + +Benjamin B: Yes. + +Tyler Wright: Yes. + +rUqeRT: Yeah, so the main program that is deploying all of the benchmarks Brittany go. it doesn't And basic stuff to just set it up. + +rUqeRT: later finds all of the things it needs. to the provider we have currently on the run it against the testnet. since we've just been developing and don't want to pay all the money that is involved in starting up and taking down deployments all the time. So it sets up the deployment then it waits for the benchmarks to run and then just the file from the image. And close the deployment then we push it over to the database. It takes a while to run this thing. So here we have an example all the logs. And don't worry about the credentials there. They're all just for the sandbox environment. + +rUqeRT: So let's say it starts opinion. Yeah, so this is just the config needed to start it up. + +Tyler Wright: Sebastian while you're doing that. There's a question in the chat. What image is this deploying the benchmarking Scripts? + +rUqeRT: so we found a bench called Lucas Benchmark That we're using. can go into We made it sunlight modifications to it. + +Tyler Wright: Go ahead Benjamin. + +rUqeRT: So it's Benjamin pie better. Who's Has rear published the image. I could send you a link to the original benchmark. + +00:05:00 + +Anil Murty: Okay, I think I drop the links to the actual Benchmark that you're using in the WG provider channel. That will be great. + +rUqeRT: Yeah, could you fix that Benjamin? I'm doing this. + +Benjamin B: Yeah to the district Channel. + +Anil Murty: Yes, please. + +Benjamin B: Sure. + +rUqeRT: Yeah, so then that's all that waits for the Results come in and then this is the actual Benchmark that comes in. the summer part is The relative performance compared to a Raspberry Pi 1 model B. And this is just the actual raw data that it's performing against + +rUqeRT: so then we just push this into the database we got. can + +rUqeRT: show these are the different tables because to store the data. We got the actual Benchmark results. That's this first part. Yeah, overall the CPU RAM and real. this is then linked to these two which we call the bench specifications + +rUqeRT: and then we just have providers that are unique records that all of these benchmarks are linked to and we also have a run log just to keep track of everything and make sure that things are running. + +rUqeRT: Then on the API side once again, it's written in go and what you do is basically you run. This carol command. + +rUqeRT: Where you ask for the different providers? And you get back all of the benchmarks for that provider? + +rUqeRT: and that is basically + +rUqeRT: that is how this thing works in a nutshell. + +rUqeRT: Yeah, Benjamin. + +Benjamin B: Yeah, I just want to start here. That's the benchmarker we have right now. Could easily be swapped out for anything else. This is just so we can show something if there's demand to + +Benjamin B: to Benjamin's Market gpus to Benjamin smart networking anything else that could easily just be built. Basically. We just have to add more of the stls right now. We just made that single one, but we could just add more of them. + +Benjamin B: Try other things. Is there any questions for this demo? + +Anil Murty: Yeah. Yeah, this is great. Thank you for the demo. Could you dig a little bit deeper into the and I think you said this a little bit in class and I didn't catch it. But could you talk a little bit about the use you mentioned something about a Raspberry Pi and + +rUqeRT: Yeah, just There's some part of them. And Mark data is compared to how much better it is than a Raspberry model 1B + +rUqeRT: that is just something that is part of the benchmarket that we text. + +Anil Murty: got it. + +Anil Murty: Is that something that is? Swappable meaning can you replace who you're comparing against? + +rUqeRT: That should be possible. Yeah. It's just that this gives you a nice kind of Baseline. So, because most people have at some point interactive with a Raspberry Pi Wright. Then you get that goes, Because oftentimes benchmark scores are quite abstract. So you don't really know what the Baseline is. just This is my machine and it's better than that machine or worse. but if you have a concrete point to measure it against gets a little bit easier to think about + +rUqeRT: No, not yet. But Benjamin said Benchmark is quite easy to swap. Because it is just we change what image with deploy and we create some new models. + +00:10:00 + +Tyler Wright: Go ahead Scott. + +Scott Carruthers: so then if I don't want to distract from the current demo of benchmarking, so if We'd rather. Stick with that specific topic and then revisit this later. Let me know. I don't want to. be disruptive to this specific demo, but possibly just because it's been a period of time since we last met and there may be some people in the call that don't know these details at all. Is it possible also I wonder if this would be helpful for how everyone is conceptualizing this to provide a high level overview of the entire + +Scott Carruthers: accounts of what provider auditing from your tools is going to look like and so in other words, I appreciate that. We're currently looking at benchmarking statistics and that it's ready to a database. Is this the entirety of the Focus right now and I also saw some updates that you're not currently looking at the integration with Cloud most. So I'm just wondering you go out and you do this benchmarking against different providers you write to a database and then how does that holistically fit in? + +Scott Carruthers: and even how if we were going to include these benchmarks within provider attributes, how is that information getting into a providers attributes is the entire extent of the service at this point that we're just benchmarking writing it to a database and then it would be incumbent on other tools to bring that into it's + +rUqeRT: You would probably use the API that we could expand in whatever way you'd like. it has one endpoint to get this but you could easily expand upon it do some processing and expose that as well. but just as a starting point,… + +Scott Carruthers: okay. + +rUqeRT: you can ask for the provider from this API and then you get the benchmarks for the API for the provider + +Scott Carruthers: Okay, I see that has a hand raised as well. So might have some thoughts. + +Benjamin B: Yeah, I have some more things to speak on this matter. I think this was actually a perfect time to break up from the demo on this and what has any more questions. You can leave the screen share of Sebastian. But otherwise, what's the last I mentioned about the API? It's true for console usage for other usage. Just having the API would probably be enough. But we still have some more things. And that we're going to talk about today. And we're still planning to release it. So that it's not just their Internet. It's also the blockchain directly the other assigned by fields. We will speak a little bit more on this circuit that we see. Actually, I can take that right now. + +Benjamin B: So the idea is that when we have all the benchmarks and The Benchmark stls ready. And we just want to look at what is important for people to know is it up time? Is it CPU score? It's this and as soon as we have everything established here what people actually want to know. we can start signing people on chain for one address for everything that They want to know so if uptime being over 90% of this we can sign people that factor. If it's important to know if they have a CPU score I don't know over 500. We can sign people that as We don't have the demo for that today. but is that what you're asking? + +Benjamin B: Yeah, so we would use the API from the other service later on to do all this and before I speak on some other points like How we wanted to do kyc and other things we still have planned and I want to let them all and Anil speak. So please go ahead and de. + +00:15:00 + +Deval Patel: And so my question around is how frequently do you run this page practice and can we run more frequently than what we anticipate and I raised this question in discussions. sometimes what happens is that provider the hardware and change underneath changes right and that can change the Audited attributes in terms of CPUs and RAM and is there a way to and know that and how do we know those things on our side? + +Deval Patel: As a dashboard or we have the provided status page what we want to show those things there as well. So yeah my questions around that as well as we do + +Deval Patel: Right now in auditing the audit each attributes whatever the providers actually do are provide. + +Benjamin B: Yeah, I will start 50 second question whether or not we can do more attributes than this and… + +Deval Patel: So do you guys have that kind of capacity to do that? + +Benjamin B: the answer is yes. We just have to include some more benchmarkers like we mentioned this one is really simple,… + +Deval Patel: Let's say even the bandwidth they say what they have right like we manage and… + +Benjamin B: but this one can be more advanced or… + +Deval Patel: we sign that particular attributor as well. + +Benjamin B: we can just create new ones. of how often we run it. I think this depends not of the software but rather how we make the business model later on we can definitely make sure that anyone can run it and it can be triggered in other way, but it would depend how would we make this self-sustainable? We'll do it and create a business model where people pay for Benjamin smarts when we get to network to sponsor it what we do our own benchmarks. + +Benjamin B: so how much could we afford and that's a dependent north of that question so we could probably build so that regardless of who hosts the services. it's possible to choose how often you do it or if it fails if you want to retry And if you see any changes if you want to retry the benchmarks. + +Benjamin B: It's this what you're asking or was there anything else as well? + +Deval Patel: yeah, I think that's + +Tyler Wright: Jigar, did you ever end up? + +Benjamin B: awesome + +Benjamin B: yeah, I think again this depends some providers could probably try to have some sort of limitations in their bidding Scripts if they don't want to be done our benchmarks. That's kind of up to them. if they don't pay down benchmarks, and maybe we don't have super expensive benchmarks. Some providers have a minimum amount to USD per month for them to accept it. maybe we won't be able to reach maybe those on the opposite side of the spectrum where They have super expensive a million akt per per block. We couldn't pay for those either. Of course. But other than that the plan is to a bunch work everyone. Yes, but again, it depends a little of + +Benjamin B: at them go like how will the business model look like that kind of? makes a big difference was that's everything. + +Tyler Wright: I had a quick question. I think Deval has a question after that. I understand the idea around the business model. And I think that's something we talked about during the steering committee and trying to make sure this is self-sustainable. But as I understand that the main component was an open source automated auditor that anybody could use to audit a provider. Is that still the plan? Because again I think that's the main product requirement. So I just want to make sure I understand the business component, but it's very much till the plan to open sources so that any other cool client Etc can also use the provider audit and benchmarking tools. Is that correct? + +00:20:00 + +Benjamin B: This is correct. We want to make sure that anyone can run it themselves. If we can't host it ourselves. We're going to have everything open source for anyone to run. and the plan is that we were going to try to run it ourselves. But how long we can do that totally depends on other factors, but the main goal is the development of the open source tools. Yes. Please go ahead. + +Deval Patel: So to say same thing, and that goes with the Tyler side, open source. Let's say if you open source, and we really, make this part of a core platform engineering thing then and we have four I mean pods running let's say inventory part is running to notify the inventory and stuff like that can we not make part of this as an optional tool there? They can deploy this part as in + +Deval Patel: independent part and we basically capture the api's from that particular part and we showcase that to the providers are to the provided dashboard and provider status page? So, that way if we don't have to constantly ask for the beads rather than asking for bids like we can catch directly the data from the API. + +Benjamin B: Yeah, I think that's a good idea. So basically we're skipping the deploying on a cost process and the providers can just willingly allocate some of their resources to us like to always other and this is a good idea it kind of Doesn't make sense. If you want to scale it, if you want to test the gpus, I'm sure that a lot of providers don't want to rent out one entire GPU or least that for free to the auditor indefinitely. but for a smaller benchmarks and for uptime checks and Things checks everything like that this talk to make sense. and then + +Benjamin B: there's also the question of if you have this way of running it will provide us try to cheat it if they don't really know where it's coming from. and the last thing + +Benjamin B: was one more thing therefore Yeah, if we want to update the benchmarks to do something else. It also might be hard to ultimately update that but the idea is good and it could work for some of the benchmarks for sure. please + +Deval Patel: But I think what you can do with that part, is that whenever you want to run the Benchmark and frequency, You can grab the GPU at that point of time and then release it right and let's say all the gpus gets field right then we show the last status of the GPU what we had right stuff like that can be done and let's say even in your case, if you want to run a benchmark on a GPU and if the gpus are not available for that particular provider than what you're gonna do, right you will not be able to fetch that data at that point of time. + +Benjamin B: This total makes sense. It could also be so that something like this would be a triggered as soon as some resources gets Freedom that you want to Benchmark and The Benchmark could run. So if you're renting all the gpus at once and then someone closes at least that could be the trigger to say. Yeah, we're ready to Benchmark now. I don't think we're going to and keep this in the current scope, but we would definitely be happy to help out and discuss how to further build results because right now our system is built on a completely different way. But we could probably figure out some way where we create the proper Integrations to our systems. + +00:25:00 + +Benjamin B: Yeah, we did have some meetings in the past. I think one or two and this is a good thing to keep in mind for a future reference. Unfortunately, we can't really do anything about it now and I still think it's really valuable to do this via bidding. for making it cheaper. This will totally work. But then for this to work. You would have to need some Partnerships between the Auditors and the providers. If you're able to get that, it's not really certain whereas with bidding as long as the auditor wants to pay for the benchmarks or the provider wants to pay it or the networks. You can get it to work. Whereas the solution you're proposing. It will definitely work. But everyone would have to want to be involved. please go ahead and + +Benjamin B: Also, thanks for that to know I can definitely cover that right now and let me have to go through my points really quickly and we can have all the questions later because this was already on the agenda. I just didn't make it clear enough. First of all, I want to quickly mention that for the benchmarker while we are going to continue developing it and making it for a moment Posh. We are going to make withdrawal for This Milestone the kyc idea. + +Benjamin B: And that were going to work with. Different kyc providers but this is a very centralized way of doing it. If one kyc provider gets shot down. It really didn't work like all the development efforts will be done for in vain. and we had some internal discussion me and some other battle guards just a few days ago and we were talking about how to best to kyc not really kyc there. We were talking about a general trust system that we also want to help develop. Along with the kyc. + +Benjamin B: we still are discussing what the best way of doing. This is Basically, what we wanted to do is start. + +Benjamin B: Just like the services that we develop the open source tooling. + +Benjamin B: And where everyone will be able to run we want everyone to be able to be able to kc hold on or what? It's on in a different way. basically We want to have different people and if you trust maybe overclock clubs, you can trust their Senators if you trust us for our science, you can trust us and we would prefer to keep everything here on Shane similar to how we are going to sign by the attributes. This will be done for kyc. Preferably and other questions like Imagine if overclock Labs were to sign everyone. At one of their employees have met at a convention. + +00:30:00 + +Benjamin B: Maybe that's not a full proof way of trusting someone but it could definitely improve their trust if they're an Insider. Signed by overclock Labs. Maybe that's another thing that as you would trust. The list goes on. rotary sit important or ICU to cure handout I would prefer to keep the questions off through these points. If possible. + +Benjamin B: We are not going to develop something like that, but we were actually inspired by one of the hackathons submissions where they implemented a way to pay with credit cards to get akt. We saw how they did their kyc and we're probably going to create our kosc system in a different way or in a similar way rather and also have some other things that you can sign by to create this cross system that anyone can get involved in. we're also trying to get some value like there's some other people right now too getting involved in this and as soon as we have the best way of the creating and implementing the system and we're going to work with a simple to beta test this + +Benjamin B: the one thing that we were wondering when we had our discussion in the vanguard's chat is what could be the best way so that we can search of all of this. Or we're going to just create transactions with memos. We're going to create new transaction types or what would be the best I think this is a question maybe best. For Scott's to answer what we wanted to do here is we want any address to be able to sign other addresses? so that + +Benjamin B: We want to make it clear. what one person thinks of another address? I don't trust this one. I've met this personally real life. This is an Insider. you can have any amount of questions and answers in this memory transaction. And we also want to find it very easily when picking out the provider or + +Benjamin B: Or going to opposite way of which people do this person Go ahead Tyler. + +Benjamin B: Thank you that the last thing on the agenda. Is the console integration? We were thinking of just not doing any work and sending back to the funds to the community pool. but we can definitely keep discussion open to continue working or continue with some sort of integration. We're going to make the API public. Either if you want to continue on that and maybe we can send the funds to you in some way or if you want us to continue. We would probably want to increase the deadline if that wouldn't be a problem with everyone else here. + +Benjamin B: Yeah, but otherwise if nothing else like our original plan was just to send it back and not do anything, but we're open for ideas. Go ahead Scott. + +Scott Carruthers: It is just to make sure that everyone is on the same page. What exactly would they integration with Cloud most look like or where would there be? Value I would assume that it would be in Claude most implementation of recommended attributes. But could make sure we're on this same page with what it integration with cloudmus would entail. + +00:35:00 + +Benjamin B: And yes, just give me one second to open the proposal page. + +Benjamin B: Yeah, so the idea I start we could include filtering for that for cloudmaster now console. So if you wanted to find the + +Benjamin B: provider that has successfully shown that I'm capable being having this up time having these attributes verified or anything else you can just And quickly select what you need or if you need them to be from a certain region you can just filter that and to be able to only find those providers the assigned by the other API from us now. It's + +Benjamin B: Yeah, and I lost the thing that we want to have here as well is the kyc thing. So if you only want to now we have the non audited providers. Another very important thing is having a versus non-ky seed provider. I think this should be enough for this answer, please go ahead Anil. + +Anil Murty: Yeah, just going to the list of things contributions related benchmarking providers testing RPC know the tracking of time sort of these. It seems like what you've gotten so far and correct me if I'm wrong is. A portion of the benchmarking tool Is that correct? So track testing and no tracking of uptime. but + +Benjamin B: this is correct we have not done in a contributions to the indexer and we don't Have the API or Benchmark to work on the RPC quite Jets? and we also haven't done the + +Benjamin B: The filtering contribution on cloud nodes or console. and the rest while it's close, we actually have the last Point like half of that one right now what otherwise Pilates being worked on and It's quite close. We don't have it quite yet this meeting. No. I see some questions in the shortest world or some messages rather. And the kyc is not important for the benchmarking, but could be important. If you want to be able to trust their provider. It's a separate thing just like deathless basically if you want to run from a random Provider on the Internet or… + +Anil Murty: Got it. + +Benjamin B: if you want to run from a trusted company or person that kind of what we want to separate here. + +Anil Murty: but it makes sense and then really quick Tyler one other question is so think just in my head right? I think what I was thinking and maybe other people jump in if they don't agree with this, but today we have a uptime indicator in the provided dashboards when somebody goes to deploy something. There's a similar uptime history just when you go to the details of Provider that available on both the pre-order dashboard as well as a cloud most dashboard. I think ultimately what will be cool to do is to build something that adds to that. So meaning today more than when people try to pick a provider the primary things. They try to decide please is based on the location the price and the uptime indicator integral. That's it. So I think ultimately we want to add something that increases the number of variables that people get to pick from and so this would have to be + +Anil Murty: I think a service that runs periodically. + +00:40:00 + +Anil Murty: Ideally, it would be something that gets deployed onto each provider. And it has to be small enough that it doesn't consume a whole lot of resources. There is the problem of how to be deal with this on the GPU side because it's an all or nothing outside of gpus, I think it's the way I was thinking about this. So to answer your question about what you should do next. I feel like this is early enough that there isn't that much that has been done. that it makes sense to potentially go in a different direction with this, but that's just kind of I thinking on this + +Benjamin B: I think we're on the same page in kind of what we want to show on the console. I just want to make one thing clear here. Is that the uptime show unless something else has changed since I lost checked the uptime is not based of. How the leases are online or it's not based of that uptime. It's rather based of is the service running. They provider pulled or can the provider bid can they provider and do all of those things. Can you interact with the least shell All of those things is… + +Anil Murty: That's correct. + +Benjamin B: what is already being tracked and then something super small could just be tracked to get the actual uptime. I'm guessing. + +Anil Murty: That's great. + +Benjamin B: Yeah, and then for the other benchmarking things you mentioned. That makes sense. Yeah. + +Benjamin B: Did you have anything else or should we leave it to Tyler? + +Anil Murty: No, that is it. I think so. Overall. what I'm saying is I think if all you've gotten is one third of bullet number one, it makes sense for us to just revisit how we want to be doing. This periodic auditing, separate session and think about how you want to proceed from there. + +Benjamin B: All right, I'll leave it to you Tyler. + +Tyler Wright: Yeah, that was actually just my follow-up point because it seems like based upon these four General deliverables that are outlined. You're still fairly early in a number of these. So I was wondering to deval's point maybe obviously we're a little bit behind schedule. But do we have the ability to kind of direct how we're going to move forward from here to get these across the finish line so that they can be used by console and other members of the community. So it sounds like a near was talking about maybe doing another session where we can talk through some of these in a little bit more detail, but Benjamin, I just want to follow up with you about is that correct in terms of + +Tyler Wright: these four deliverables and percentage done probably across the board is less than 25% for each of them. And so again, we have some time to shape the direction move forward and determine From a Time standpoint if you can get all these things done or the order of operations and getting those things done. That's just sounds like we saw some time to make some decisions as a group and kind of just narrow down where we're going from here. is that fair to say? + +Benjamin B: No, I think. for most of this we're going to be able to finish them within the deadline, but then everything related to the + +Benjamin B: contributions to console and the cloud loss. We're not quite sure if we're going to have much time to dedicate that it's cool. We could look into increasing the deadline or we can return the community funds for those things. But everything else should be able to be done within a month, hopefully. + +Benjamin B: I'm open towards having more sessions to discussing more of these things. especially if you want to increase the deadline and do the Council integration in some other way But otherwise we haven't under control. + +Tyler Wright: Got I'm reading your chat. And can you speak to this a little bit more if you can? I'm just trying to + +00:45:00 + +Benjamin B: Yeah, I think especially for the council integration we can leave that. Just being a nullified but for the other things as I mentioned, we're developing it and should be done within the end of the month, even though we don't have the demos today to show everything. but those 100 hours For filtering and API usage of the clouds front end. We can definitely just return to the community pool. + +Tyler Wright: Okay, perfect. Thank you for that clarification and in terms of I guess implementation of the automation of the auditor. I know you said you don't have a demo today. Do you know have a timeline when we can set up another session to have to demo that and then get feedback from the community and then again narrow down getting that to production as quickly as possible. + +Benjamin B: I think the best thing here would be if we could shoot next time offline. So that we have the time to look at our schedules. Does that work for you guys? + +Tyler Wright: Do you have a range of when you think that demo will be ready? Just so I can map out some time for us to have a loose schedule and then we can narrow it down from there. We're thinking seven days from having a demo or more 14 days. + +Benjamin B: Selection what you think about roughly two weeks a few days before the deadline. It's + +rUqeRT: I'd say maybe. 14 20 days + +Benjamin B: at 14 to 20 days So the deadline is set the end of this month… + +rUqeRT: Yeah, something like that maybe. + +Benjamin B: if I'm not mistake 20 days. It's just a little bit into the next month. You start something that you guys are concerned with. + +Tyler Wright: slightly concerned but I think whatever gets us to the point where again we can share it get some feedback and then Get this share with a larger Community would be ideal, so I understand that you all have other things. So it is what it is. + +Benjamin B: Okay, so somewhere around there and 14 and 20 days and we should be able to meeting them. + +Tyler Wright: Come here follow up with you offline over the next a week or… + +Benjamin B: also + +Tyler Wright: I know we have 10 minutes left. Is there any other questions that anybody has about where we are and some of the next steps? + +Tyler Wright: All right. Benjamin I know you mentioned this at the top of the call, if you could drop in some notes when you get a chance on the product board in the issue that's created around this on the parking engineering board. That would be great. I'll make sure the notes transcript and recording are available as quickly as possible to share with other folks that maybe couldn't make it here today and then I will follow up with you over next seven to 14 days to get a better timeline of when we can get a demo so that folks on this call and in the community have enough time to plan and make sure that sound like a great next course of action. + +Benjamin B: Yeah, that sounds like a good plan. Please also send me the notes in a private deal. So I'm able to have that as an additional reference… + +Tyler Wright: Yes. + +Benjamin B: if I forgot anything. + +Tyler Wright: I'll do that later today when they're available. Thank you all for the demo. + +Benjamin B: Thank you so much. + +Tyler Wright: We'll follow up in the working group for provider audience Channel. If anybody has any questions again, feel free to reach out there or in the specific product that again, project tile that created around this that I'll drop in the chat again for folks. But again Benjamin Sebastian, Thank you all for all the questions and joining here today. I hope everyone has a great rest of the day. + +00:50:00 + +Benjamin B: Thank everyone. Bye. + +Scott Carruthers: Thanks guys. + +Tyler Wright: thank + +Jigar Patel: Thanks. + +Rodri R: that + +Deval Patel: Thank you guys. + +Meeting ended after 00:50:16 👋 + From 6d0870cdf1640b0228a6737767bcc2fb46d005be Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Sun, 7 Jul 2024 16:11:10 +0000 Subject: [PATCH 093/138] Create meeting notes for Sig-chain #17 (#611) * Create meeting notes for Sig-chain #17 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 017-2024-06-11.md add transcript and recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-chain/meetings/017-2024-06-11.md | 146 +++++++++++++++++++++++++++ 1 file changed, 146 insertions(+) create mode 100644 sig-chain/meetings/017-2024-06-11.md diff --git a/sig-chain/meetings/017-2024-06-11.md b/sig-chain/meetings/017-2024-06-11.md new file mode 100644 index 00000000..9997acc5 --- /dev/null +++ b/sig-chain/meetings/017-2024-06-11.md @@ -0,0 +1,146 @@ +# Akash Network - Chain Special Interest Group (SIG) - Meeting #17 + +## Agenda +- Discussion on Cosmos SDK Upgrade +- Details on Akash Mainnet 12 Upgrade +- Discussion on Akash DAO and Overclock +- Tooling and Snapshots + +## Meeting Details +- Date: Tuesday, June 11th, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://g6qelhldnaj52ry4xc56kge2wjrswqfgxrqs4iduth4cpqpndlfq.arweave.net/N6BFnWNoE91HHLi75RiasmMrQKa8YS4gdJn4J8HtGss) +- [Transcript](#transcript) + + +## Participants +- Artur Troian +- Dimokus +- Gabriel Li +- Julius Haus +- Marc +- Trigs +- Tyler Wright +- Zeke E + + +## Meeting Notes +- **Welcome and Introduction** + - Tyler Wright welcomed attendees and reviewed the purpose of the monthly meetings. + +- **Discussion on Cosmos SDK Upgrade** + - Recap of potential upgrade paths for Cosmos SDK (version 47 or potentially 50). + - The core team is conducting research on the next steps. + - Community members interested in the process are encouraged to participate in discussions and the next Sig Chain meeting. + +- **Details on Akash Mainnet 12 Upgrade** + - An upgrade is scheduled to occur in the next couple of hours. + - A countdown to the upgrade is available in the chat. + - The upgrade addresses an issue around fee grants. + - Proposal which resolves this issue, has passed and the upgrade is scheduled for block height 16708237. + - Attendees were invited to ask questions about the upcoming upgrade. + - [Documentation and resources](https://akash.network/docs/mainnet-12-upgrade/node-upgrade-guide/) were shared in the chat for validators. + +- **Upgrade Process Overview** + - Validators will upgrade first. + - Once the chain is stable and blocks are being made, RPC node upgrades by providers and exchanges will follow. + - Stability checks will be conducted post-upgrade. + +- **Support for Validators** + - Validators and insiders were advised to support others during and after the upgrade. + - The validators' channel on Discord will be closely monitored. + +- **Discussion on Akash DAO and Overclock** + - Marc was acknowledged for his contributions to recent discussions about Akash DAO. + - Ongoing conversations about the evolution of Overclock and the creation of Akash DAO were highlighted. + - Tyler emphasized the community-driven approach and the goal to move towards a more formalized DAO governance structure. + - Discussions about DAO governance continue to be active, with contributions welcomed from all community members. + - Tyler invited Artur and Gabriel to share any additional thoughts on the network upgrade before moving on. + +- **Tooling and Snapshots** + - Zeke discussed a new snapshot tool for Overclock, aimed at creating a more accessible sandbox environment. + - The community can expect pre- and post-upgrade snapshots and further tooling improvements in future meetings. + +- **Upcoming Meetings and Participation** + - Tyler encouraged attendees to mark their calendars for the next Sig Chain meeting. + - He emphasized the importance of community involvement in discussions about Cosmos SDK upgrades and Akash DAO. + +- **Closing Remarks** + - Tyler invited any final topics for discussion. + - He noted that Scott Carruthers, a key team member, is on vacation, so additional community support is needed. + - Tyler thanked attendees for their participation and encouraged them to stay engaged for the upcoming network upgrade. + - The meeting ended with a note of appreciation for everyone's contributions and a wish for a successful network upgrade. + - Tyler emphasized the importance of community support and participation. + - He looked forward to a successful network upgrade and continued discussions post-upgrade. + +## Action Items +- All Validators to upgrade to the new mainnet version at the specified block height. +- Insiders and Vanguards to support validators during and after the upgrade. +- Community Members to participate in ongoing discussions about [Akash DAO on GitHub](https://github.com/orgs/akash-network/discussions/601) and provide feedback. +- Zeke to Continue development and communication about the snapshot tool for Overclock. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: Welcome everybody to Sig chain monthly meeting The date is June 11th, 20 During the special interest group for the Akash blockchain that meets every month. Sometimes has been meeting every other month. The group mostly of validators and other just interested members of talk about everything from Network upgrades to Cosmos SDK previously. We've been talking about the upcoming upgrade to Cosmos SDK 47 from 45 where we are right now again, there's also some exploring around going to ask Cosmos SDK 50, but we've had plenty conversations about that during this meeting this week or this meeting. + +Tyler Wright: I know there's a planned upgrade happening now in the next couple of hours again, there's a countdown that you can all get access to drop in the chat for folks, but we're about an hour again 32 maybe a little bit less because this is an approximate timer, but we're a little bit out from Akash main net 12 again. There was a proposal that went on chain last week that helped for version. 0.36 that solves an issue around fee Grant. I'll drop down the chat for folks as well that proposal passed on today. Thank you everyone who voted and got themselves ready? And again with the proposal passing formally on chain yesterday. The upgrade is planned for on the block height that you see in chat 16708. + +Tyler Wright: Two three seven again. We're a little bit out from the upgrade right now. If anybody has any questions about the upgrade and how to upgrade again, feel free to drop them in the chat here today drop in the validators channel if you're a validator. You're not a validator if you are about there, but not about their Channel again. Feel free to ping me and I can give you that validator's role for those in the active set again. I've dropped the documentation in chat. and again people that are using Cosmic advisor should be ready to go and should just be waiting for the block height. Does anyone here have any specific questions about the Akash main net 12 upgrade that is happening sometime soon. + +Tyler Wright: did All right again, I know there's some insiders in vanguards currently. I was call if you see anybody in the validators channel that needs leading up to the upgrade or after the upgrade, Please support them. Again. The changes have been reviewed and are actively in sandbox right now. So there are teams that are working on it. So again much appreciate supporting all those that may need it. + +Tyler Wright: The goal is that again the validators were upgrade first, once the validators have upgraded and the chain is making blocks again. wait a couple minutes like we do check the stability of the network and then we'll have providers do an RPC node upgrade and then we'll just have again exchanges do the same. So that'll be the process as we move through the day. Anyone have any questions there? + +Tyler Wright: All right moving along with the agenda. I know that there's been a couple of conversations that have been happening in sick chain, as of recently, I believe Marc who's one person that's on this call today had actually been having some of those conversations. There's been a discussion that's had around basically in a cash down. I know that there's a member Of the overclock core team that has previously been talking about. + +00:05:00 + +Tyler Wright: + +Tyler Wright: The evolution of overclock and the creation of akashdow, so he's not currently here, but I know he would love to get involved and have them get involved in the GitHub discussion. He actually on paternity leave so that may be less than happening. I saw Archer just during this call. I want to manage his time a little bit Artur. We talked a little bit at the top of the call about the network upgrade Gabriel the documentation said the time with everybody there was no questions at that point. Do you have anything that you want to talk about in terms of network upgrade before we move on you can feel free to drop after we talked about Network upgrade Anyone have any questions for Artur? again, if anybody has any questions until they get closer to the network upgrade, feel free to drop those in the validator channel and Discord that channel will be closely monitored leading up to and directly following the network upgrade like we tend to do. + +Tyler Wright: I will chat out Zeke. + +Tyler Wright: because I think there's gonna be just a quick discussion around Akash Dow + +Tyler Wright: Also again Pikachu will have some staff shots,… + +Tyler Wright: which is an idea that's been floated by a member of the community. + +Tyler Wright: but Zeke has been working on an overclock related snapshot tool to have for again easier sandbox environment the number of easier upgrades and topics topics… + +Tyler Wright: So I just want to see if there's anything that you want to talk specifically about the main Network upgrade before we continue on with + +Tyler Wright: just like a topics An official overclock snapshots cool that can be used by The Wider community in addition to all the work that poked you and others do in providing snapshots. So again, there will be pre and post snapshots available. And then again look out for that tooling that will probably talk about in future meetings. + +Tyler Wright: + +Tyler Wright: Cool leading back to the conversation. We were just talking about around the cast Dow again. I want to make sure Mark did you want to talk about that very briefly about what you're looking or what you're thinking about. One thing. I will say is the idea as a Akash Community continues to grow and mature is that we move in the direction of a cost down. + +Tyler Wright: Really The Specialist groups groups and open group structure that we have here currently is a version of trying to be as transparent and trying to guide the community as much as possible. I think overclock is trying to be a steward in again trying to get as many Community contributions to everybody moving the similar Direction because there's so many things that need to get done but I do want to give you some time to talk briefly about a cost down your mind and I know that there is already been some comments, related to again, there's no smart contracts currently on So just want to let you speak high level if you're able to and then we can continue talking discussions. No worries, Marc different not able to talk. Either way, there is a active discussion that I've dropped in the chat again, feel free to get involved in that discussion. I will give my own viewpoints but again high level I think Dow governance is a great idea. low level, I think that + +Tyler Wright: we're overclock and really the cash Community is trying to accomplish this via The Specialist Group and working group structure in lieu of again, just formalizing a dab, but there's a number of ways for people to get involved to contribute to make the voices heard. It's very decentralized and Democratic and again as we continue to push forward, I think the idea to move in a general direction towards and Akash dab that does a little bit more management and governance over some of these things. If anybody else has any thoughts. Feel free to drop them in the discussion to give feedback to Marc but much appreciate the discussion started. + +Tyler Wright: one other thing I want to mention is again. I talked about a little bit about at the top of the call around Cosmos Upgrade to version 47 or potentially 50 again. There's been a lot of research and work from the core team into what's next there. There's so many features that again will be unlocked via customer SDK upgrade if anybody wants to get involved in that process I ask that + +00:10:00 + +Tyler Wright: your calendars for the next Sig chain meeting and look to get involved in the channel before that. There's already a couple of folks that have been working on other Cosmos projects that have already gone through this process. They're looking to get involved. And so we're looking again as a community looking to get all those people in the same room talk about these things maybe in a working group session or maybe just in the next 16 meeting. But again, if you want to be involved in that process, feel free to just make your voice heard and sick chain, and then we can take next steps there. + +Tyler Wright: does anyone else have any other topics that they wanted to discuss on this call here today? + +Tyler Wright: Again, I imagine this call will be a little bit shorter because folks should be if they're not already getting themselves ready for the network upgrade. But is anything else anybody wants to discuss here today? + +Tyler Wright: if not, thank you all for joining. I'll see many of you all in validators Channel. Sometimes shortly again. Feel free to reach out to me or support each other invalidated channel. If anybody needs help with anything that actually see a couple of comments that may need support the core teams a little bit short-handed this week. We have backup support and obviously a number of people are computer ready but as mentioned In Discord Scott Carruthers who usually is a very Hands-On with upgrades. It's been Hands-On leading up to upgrade and documentation testing all that kind of stuff, but it's currently on vacation. So if anybody else from vanguards insiders can with some help the community, that would be greatly appreciated. + +Tyler Wright: again, we're Again. This is a rough approximate countdown. So please stay close to your computers over the next couple hours knock on wood for another successful Network upgrade to Akash main net 12. And again, we'll continue to talk async about a number of things related to sick chain, but much appreciate everyone's time and energy today Mark much appreciate the discussion. I hope people get involved that discussion and look forward to a successful Network upgrade and then talking to you all post upgrade. But thank you all very much for voting and all the things that y'all do. + +Zeke E: I think everybody. + +Tyler Wright: Have a great day. talk y'all soon. + +Meeting ended after 00:13:04 👋 + + From c1dacfc7de79206acb9e298c7da2c520310ee3fc Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Sun, 7 Jul 2024 16:18:29 +0000 Subject: [PATCH 094/138] Create meeting notes for sig-chain #16 (#610) * Create meeting notes for sig-chain #16 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 016-2024-05-21.md add transcript and recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-chain/meetings/016-2024-05-21.md | 132 +++++++++++++++++++++++++++ 1 file changed, 132 insertions(+) create mode 100644 sig-chain/meetings/016-2024-05-21.md diff --git a/sig-chain/meetings/016-2024-05-21.md b/sig-chain/meetings/016-2024-05-21.md new file mode 100644 index 00000000..8830f94d --- /dev/null +++ b/sig-chain/meetings/016-2024-05-21.md @@ -0,0 +1,132 @@ +# Akash Network - Chain Special Interest Group (SIG) - Meeting #16 + +## Agenda +- Introduction and overview of recent activities (Tyler Wright) +- Mainnet 11 upgrade discussion +- Validator engagement and communication channels +- Project tracking on GitHub +- Upcoming Cosmos SDK 47 upgrade (Artur Troian) +- Open floor for additional topics + +## Meeting Details + +- Date: Tuesday, May 21, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://t7vun4ttnoelbnwkis4rf7eacagljw7a5tsobsuujmsiycgjdpna.arweave.net/n-tG8nNriLC2ykS5EvyAEAy02-Ds5ODKlEskjAjJG9o) +- [Transcript](#transcript) + + +## Participants +- Artur Troian +- B S +- Javier Su +- Maxime Beauchamp +- Rodri R +- Scott Carruthers +- Tyler Wright + +### Meeting Notes +- **Introduction and Overview:** + - Tyler Wright welcomed everyone to the 16th Sig Chain monthly meeting. + - Overview of the group's purpose: discussing validator operations and network upgrades for the Akash blockchain. + - Recent upgrade to Mainnet 11 was successful. + +- **Mainnet 11 Upgrade:** + - Shout out to all validators for a seamless upgrade process. + - Validators encouraged to stay engaged through Discord, GitHub, or email. + - Emphasis on responsiveness during upgrade processes. + +- **Validator Engagement and Communication Channels:** + - Validators can join a private Discord group for detailed communication. + - Tyler Wright is available to add validators to communication channels. + +- **Project Tracking on GitHub:** + - Projects board in the Akash Network organization tracks ongoing efforts. + - Roadmaps available for product and engineering, as well as community and marketing. + - Bounties and ongoing projects are visible for contributors. + +- **Upcoming Cosmos SDK 47 Upgrade:** + - Artur Troian discussed expedited governance proposals, allowing execution within 24 hours if consensus over 66% is reached. + - Realization that Cosmos SDK 47 already includes this feature led to the decision to migrate to SDK 47. + - Historical usage of a single codebase in the node group now being split into multiple parts (provider and Akash API). + - Migration plan includes: + - Migrating Akash API to the new Cosmos SDK. + - Ensuring proper conversion of data types and implementation of migration. + - Working on blockchain parts and starting testnet to assist clients. + - Significant breaking changes include state, APIs, transaction, and query messages. + - Target timeline: aiming for completion by end of summer, with actual upgrade likely in autumn. + - Preparations for future SDK 50 upgrades also discussed. + - Emphasis on providing reference designs in GoLang and TypeScript for developers. + +- **Additional Updates and Open Floor:** + - Tyler Wright emphasized that updates will continue to be made available via Discord and other channels. + - Opportunities for community involvement in testing will be available. + - Smaller upgrades planned for the end of the year will be on hold. + - Significant post-upgrade improvements expected. + - Encouragement to use the product and engineering roadmap for tracking and communication. + - Monthly meetings will continue, with the duration depending on the updates available. + - Final call for any additional topics or questions. + +## Action Items +1. **Tyler Wright:** + - Add any validators not currently in the Discord group to the validator role. + - Ensure all validators are added to the email list for updates. + +2. **Artur Troian:** + - Provide more specific details on the Cosmos SDK 47 upgrade. + - Outline the prep work and testing plans for the upcoming upgrade. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to Sig chain monthly meeting number 16. During the special interest group for the blockchain of a cost. This group gets together to talk all things related to validator operations things related to network upgrades, but everything related to the class blockchain believe since our last meeting. We've had a upgrade to main net 11. + +Tyler Wright: And so again, this has been a lot going on. Shout out to all the validators that made that upgrade very very seamless. + +Tyler Wright: If anybody here is a validator. There's a number of ways that you can stay engaged. If you do not want to be in Discord. You can feel free to message me or put a message in GitHub or email me and I can add you to an email list, but you have to make sure you stay up to date there. And then there's also a Discord group that has a validator role that's a private group specifically for validators where again, we manage all things related to network upgrades and just being a cash validator. So if anybody's not in those channels and needs to be again, feel free to reach out to me Tyler, I'll make sure that you're there. But again, thank you to all those that are very responsive leading up to upgrades with voting and also on upgrade day again, please upgrades have been happening faster and faster. So shout out the core team for all the prep that they do on getting those upgrades reading all testing and then again, shout out to the + +Tyler Wright: daters for all the work that they do during the upgrade So we're on Main Network 11 now and again just want to shout out all the work there. + +Tyler Wright: One thing that I believe will be talking about a little bit today. Everybody can go to GitHub. And then again on the projects board in the Akash Network organization. You can track what's going on and many of the efforts that are going on across the organization, especially on the product and Engineering roadmap. They're also is a roadmap for community and marketing you could also see bounties there. I think one thing that we will be talking about at length. Maybe not a link today, but we've already been talking about it for something chain meetings is around the upgrade to Cosmos sdk47 to be a big project that will be worked on by members of the core team throughout the next couple of months. I know what's 47 is up 4 So good number of unlocks that will happen after that. + +Tyler Wright: So again, it's an exciting time, but it is a massive upgrade. So there's a lot of prep work and then testing that will go into this. + +Tyler Wright: If there's anything else that anybody wants to talk about feel free to drop in and an item into the chat that we could talk about as an identity topic. But again, I kind of talked a little bit about that GitHub issue, but I will pass it over to Archer to see if there's anything more specifically he wants to talk about Cosmos sdk47 or anything else chain related. So Artur, I'll take it over to you. + +Artur Troian: Part of the blockchain and a couple of things for example expedited governance proposals. That you would like to have which allows us to execute governance proposal is saying 24 hours if we reach consensus over 66% and sometimes that's quite important, especially for parameters or emergency upgrades and we sort of implementing that and then realize that causes seven does already have it. and we just sort of postponed it for later on and Decided pretty much quite a few weeks ago that we going to move to + +00:05:00 + +Artur Troian: execute migration to sdk47 another decision that sort of maybe to actually directed us towards the upgrade is improvements on the Akash as the SDK + +Artur Troian: historically we used to use All the code base in the nodegroupon that we started splitting it off into multiple Parts. One of them is a provider in the second one is a cash API actually Pi is still a little bit on my side which we are cleaning up quite quickly. + +Artur Troian: The plan is going to be as following because the sdk47 is quite a breaking change and that includes not only state but as well as the apis, I mean the transaction and the query messages. So what we are going to do is we're going to call for Akash SDK and cautious decade very first part will meet my great Akashi API. To the new cosmosis Decay and make sure that all of the data types are properly converted and we have migration implemented. Once we do that, we will start working on the blockchain parts, which is not and as soon as we have blockchain part up and running we will be starting testnet with that will allow us to help clients. + +Artur Troian: That using Cosmos I actually Pi quite significantly and that we have quite a few of them. To pass and start implementing migration on their side that process will be going for probably month or so. So the amount of things you bring into cosmosis Decay is pretty much whatever we have as the business Decay 47 brings itself. That's for example, each store will have our own parameter storage. And as I mentioned earlier, it's going to proposals and IBC upgrade. For example, you will be migrating ABC to V7. Maybe at the time of a great it will be V8. So it's still being discussed. And that will allow us also to prepare for future. + +Artur Troian: SDK 50 I don't know if you're gonna executed this year, but maybe next one. So in terms of timeline, I think this stage we targeting towards and all the summer. and it was like, that's a lot of time but the change itself is massive and once again, Cost of downtime is quite significant. So we have to be really careful on what we are doing and number two is since probably this new year the Akash API is being used by other developers. So we have to Enough time to perform migration. So that means we have to give them reference design for both languages and in golang as well as typescript. And give them a time to test all of the changes. + +Artur Troian: So most likely actual upgrade will be in Autumn time, but I'm not saying that out loud. I'm just trying to give some sort of prospective that time of actual upgrade and that Varian can be quite significant. so this is then probably the biggest massive change for the next few months. and all of the other things related to the blockchain itself, it will be postponent until we get cosmosis Upgrade done and that includes packet forward in and there were some other changes. I don't recall unfortunately, but I believe there are in the sports. So I think that covers it. Anybody have any questions? + +Tyler Wright: Thank you Artur again. As time goes on there will be more updates made available via Discord and other channels. There'll be a number of opportunities for testing Again by The Core team and maybe even bringing in some folks for the community to potentially help with some testing and number of different environments. So again, this is be very much a focus of the core team and we'll make sure that folks in the community are involved when needed and up to date on all things happening there. But again as Artur mentioned some of the other smaller upgrades that we have planned at the end of the year will now be on hold while we just handle this bigger upgrade. We'll have significant post upgrade Improvement to the network usage Etc. + +00:10:00 + +Tyler Wright: Does anyone have any questions about the upgrade again, feel free to drop any questions or comments or thoughts inside of the specific ticket product and Engineering roadmap? That's the best way to kind of track this and again, there will be a number of other smaller issues that I'm sure will be added to the product and Engineering roadmap as well as potential announcements. Where when available. + +Tyler Wright: Are there any other topics of discussion that anybody wants to just talk about related to the blockchain or related to validated on Akash? + +Tyler Wright: If not, then we can certainly end this a little bit earlier again as details become more available. We will keep this a monthly meeting if there's no real updates we can have it be we are in 10 to 15 minutes like we had today if there is a need for folks to talk about some of the things happening as we're testing Costless sdk47 and we can take this time as well. So again, we'll continue to keep this as a monthly meeting to just check in and all things related to the upgrade especially as it is such a massive upgrade again will be the focus of the core engineering team open next few months. So we'll just track it with the state chain meeting on a monthly basis. + +Tyler Wright: All if there's nothing else that anybody wants to talk about again, feel free to ask any questions to have about being in a cash validator and the validator channel and Discord again, if anybody wants me updates via email and they're validator feel free to reach out to me and I'll add you to an email list where we let Val there is know about boats that they should be participating in upgrades Etc. + +Scott Carruthers: Thanks, everyone. + +Tyler Wright: But again much appreciated everyone's participation much appreciate the core team for all to do and again being present here to let the community know what they're working on and we'll continue to talk online. Thank you all very much. Hope everyone has a great rest of their day. + +Tyler Wright: but + +Meeting ended after 00:13:34 👋 + From 7a32a5e85698ee29be651a9b3f949c8039eac788 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Sun, 7 Jul 2024 16:22:33 +0000 Subject: [PATCH 095/138] Create meeting notes for Sig-design #17 (#604) * Create meeting notes for Sig-design #17 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 017-2024-06-12.md add transcript and recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-design/meetings/017-2024-06-12.md | 378 ++++++++++++++++++++++++++ 1 file changed, 378 insertions(+) create mode 100644 sig-design/meetings/017-2024-06-12.md diff --git a/sig-design/meetings/017-2024-06-12.md b/sig-design/meetings/017-2024-06-12.md new file mode 100644 index 00000000..52c67956 --- /dev/null +++ b/sig-design/meetings/017-2024-06-12.md @@ -0,0 +1,378 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #17 + +## Agenda +- Welcome and Introduction +- Updates from Denis Lelic +- Follow-up from Akash Accelerate +- Need for Additional Design Support +- Website Overhaul and New Features +- Content Contributions +- Project Management and Deliverables +- Open Discussion and Q&A + +## Meeting details +- Date: Wednesday, June 12, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://ifqou2kkf6gqtmise2kelunxe2wc4xrcssgptlx3oh25flm7tcea.arweave.net/QWDqaUovjQmxEiaURdG3JqwuXiKUjPmu-3H10q2fmIg) +- [Transcript](#transcript) + +## Participants +- Denis Lelic +- Gabriel ReyesOrdeix +- Tyler Wright +- Zach Horn + +## Meeting Notes + +**Welcome and Introduction:** +- Tyler Wright welcomed attendees to the monthly SIG design meeting. +- Overview of the meeting’s focus on visual communications, swag, merch design, and marketing materials. + +**Updates from Denis Lelic:** +- Denis provided updates on current design projects. +- Emphasis on the need for additional design support. +- Discussion of efforts around the Akash Accelerate event. + +**Follow-up from Akash Accelerate:** +- Introduction of new t-shirts, stickers, backpacks, and other swag at the event. +- Plans to create a dedicated swag page on the Akash website for better representation and launch planning. + +**Need for Additional Design Support:** +- Tyler highlighted the need for community support to assist Denis. +- Encouragement for community members to get involved in various design and marketing activities. + +**Website Overhaul and New Features:** +- Denis discussed plans to redesign the providers page for a unified experience. +- Proposal to create a unified pricing page to compare Akash costs with other providers. +- Pending redesign of the Community page due to time constraints. +- Recap of work done for Akash Accelerate, including venue branding, giveaways, and a landing page. +- Post-event focus on editing and rolling out video clips from the event sessions. +- Acknowledgment of Gabriel’s portfolio and his potential contributions to various design tasks. +- Mention of product design work related to the merger between Cloudmos and Console, aiming for a seamless user experience with new features in the pipeline. + +**Content Contributions:** +- Zach joined the meeting and discussed content contributions. +- Emphasis on technical blogs, use cases, and case studies. +- Encouragement for community members to contribute written content via the community contributions page or the website. +- Discussion about the brand guide availability for Gabriel and other contributors, with Denis mentioning the basic brand guide available in the footer section of the website. + +**Project Management and Deliverables:** +- Gabriel inquired about the list of deliverables and the organizational structure for project management. +- Denis clarified that needs vary based on events and other requirements, such as graphics for social media and swag for upcoming events like ETHCC in Brussels. +- Tyler explained the process: specific items are documented in GitHub issues, discussed in Discord, and assigned based on availability and deadlines. +- The structure is flexible, accommodating quick turnarounds and allowing for creative contributions. +- Emphasis on a collaborative approach with contributors discussing and deciding on tasks in a democratic manner. + +**Open Discussion and Q&A:** +- Gabriel expressed understanding and readiness to work within the provided structure. +- Tyler and Denis reiterated the importance of GitHub and Discord for project coordination. +- Encouragement for Gabriel to get involved and help scale contributions as the community grows. +- Gabriel clarified his expertise in branding and editorial design, stating he is less interested in web design and video. +- Tyler suggested Gabriel take a look at the marketing repo for ideas and contribute his own suggestions. + +**Closing Remarks:** +- Denis invited Gabriel to connect on Discord for further discussion and to set up a separate meeting if needed. +- Tyler emphasized the importance of community involvement and encouraged Gabriel to bring in any friends or colleagues who might be interested in contributing to Akash. + +### Action Items +**Denis Lelic:** +- Follow up on creating a dedicated swag page on the Akash website. +- Coordinate with Gabriel on upcoming design tasks and clarify any additional questions on Discord. +- Ensure the updated brand guide is accessible to contributors. + +**Tyler Wright:** +- Document specific marketing and design needs in GitHub issues for better project management. + +**Gabriel ReyesOrdeix:** +- Connect with Denis on Discord and set up a meeting if needed. +- Review the marketing repo and contribute suggestions for new projects. +- Consider inviting other potential contributors to join the community efforts. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to Sig design monthly meeting for It's June 12 2024 during the special interest group for design the Akash Community gets together to discuss all things related to Visual Communications swag Merc design marketing materials Etc. There's been a number of people that have helped support specific swag ideas and brought those live to the store. There's people that have helped with marketing materials that have gone on in real life events and Beyond Denis here is the head of design at overclock labs and has been leading this group and has been again doing a fair amount of design up to this point with support from the community. + +Tyler Wright: Denis has a number of items that he's been working on that. I think he'll share or at least get some progress on today as well as follow-up from Acosta accelerate where there was a number of marketing materials and swagged I think has been shown during steering committee and other meetings. + +Tyler Wright: One action item that I want to bring up is again with denis' time only having 24 hours like the rest of us and there's a number of things that Denis works on across marketing across design as well as across product design for console and other products there was an effort to try to trap Denis in a closet and make him work 24 hours a day his family got in the way and so there's a desire to get some additional support from the community, paid in akt to help with marketing materials, whether it be again in swag social media assets other marketing materials in real life events and digital events. So again, if anybody has any desire to get more involved in the cash and has the background and graphic design or Visual Communications, whether it be animation again, a graphic design or elsewhere there are brand. + +Tyler Wright: Isability we use these meetings as well as conversations in Discord to hopefully bring on some more folks that can help out with some of those Endeavors. So I just wanted to drop that line out there. I think put a message in chat and Gabriel who's on the calls already… + +Denis Lelic: Thanks, Tyler,… + +Tyler Wright: but summoned by Robert Delray Shadow Robert Delray,… + +Denis Lelic: welcome to Sikh design from my and… + +Tyler Wright: but again looking for folks that want to get more involved and… + +Denis Lelic: as well, so just to cover a couple of touch points from our previous sessions. + +Tyler Wright: earn some akt to help with marketing materials and other design deliverables in support of Denis and… + +Denis Lelic: So as Tyler mentioned we've Tried to overhaul the whole Akash swag. + +Tyler Wright: other members of the community. Without further Ado. I'll kick it over to Dennis to see… + +Denis Lelic: So if anyone was at Akash accelerated in Austin through three weeks ago. + +Tyler Wright: if there's anything that he wants to discuss or if there's any question and then we can talk about any questions beyond that. So Denis feel free to take it away. + +Denis Lelic: You probably saw a bunch of new t-shirts stickers. + +Denis Lelic: Backpacks, so there was plenty of new items. and of course one of the + +Denis Lelic: Touchpoints we want to overhaul. Is this what SWAG and the swag + +Denis Lelic: page on the network website. So at the moment we only have a button which leads to our Akash shop, but I feel we could do a dedicated page just to have a better representation of all the swag items out there and all the swag items. We're planning to Launch. So yeah. + +Denis Lelic: Touched the website a little bit. So there's a plenty of new. Issues created there. So besides and having a dedicated swag page. I think we have to rethink and redesign the providers page. We talked about it during the website meetings, and there's another one happening tomorrow so we can continue that because discussion there. so just basically have a unified. providers page where we could talk about all the stats about it like the network capacity and so on because also list all the providers there. + +00:05:00 + +Denis Lelic: all of these Are already alive we just have to make sure. We bring them together. So it's kind of unified experience for providers and it's going to be easier to grasp all this data and information for the users again. Another thing we could rethink and redesign would be the pricing page. Now we have pricing in two different locations one was just like a dedicated pricing page where you can calculate the cost of bringing your deployments to a cash. But then later on we added GPU pricing. So I was just thinking having one unified page where users could easily switch and compare. + +Denis Lelic: between different providers meaning if you want to calculate your cost and compare them to AVS Google Microsoft and there should be an easy switch where users could just have a look at the gpus and GPU listings and GPU price. pricing + +Denis Lelic: one additional point on the website would be the Community page. That's something Tyler has a brought up multiple times, but unfortunately we didn't add time to tackle this issue. So + +Denis Lelic: But hopefully soon trademark + +Denis Lelic: Yeah, there was plenty of work done. and the last month especially around accelerate so there was plenty of Touch points we had to create From the venue branding to all the giveaways. We had a landing page on the website as well. And now after the accelerate we wrapped it up. which means we have to On the business side. Everyone has to take care of the lead and on the marketing side and the design side we have to take care of mostly videos. So the whole stream was about seven hours long, so we chopped it up bring it down to four hours and now we're rolling out all the clips. + +Denis Lelic: For each session. So anyone who's interested can just have a look at one presentation or panel or Q&A and so on. so + +Denis Lelic: Yeah as Tyler mentioned. I just want to welcome Gabriel again for being here. Thanks for sharing your portfolio. So as Tyler mentioned we were looking at bringing someone who's gonna help us out in creating. different kind of Graphics basically everything design related that comes in so It's not going to be like one alley. design, there's gonna be plenty of different kind of designs coming, so from video to social media Graphics blog graphics infographics. + +Denis Lelic: So what else do we have? We have website, of course as I've mentioned so and again. as Tyler mentioned I'm planning to work a bit more on the product side as most of community members are aware a merger happened in the background between Cloud modes and console and we had a new addition of Prater apps which we're just gonna try to unify. all that product experience to make it feel like + +Denis Lelic: seamless and hopefully easy to use for our users next to that. There's plenty of new features in the pipeline like credit card payments adding new templates or redefining the flow of the whole app. So there's going to be plenty of work there. + +00:10:00 + +Denis Lelic: from a very high level. I think I covered pretty much everything. we're planning to do and some of the stuff we did in the past month. + +Denis Lelic: Ty do you want to add anything here? I know Zach's not around but maybe something on the content side because usually on sick design we cover content as well. + +Tyler Wright: Yeah, I know that there's a couple of blogs that have gone out recently. There are a number of teams that are developing content materials like written content. And I know that Zach is always looking for Content contributions. So folks that confined specific ways to contribute to writing blogs. I think it's less so about high level what a cost does. I think there's been a number of pieces to this point that cover that but really some deep dies and how people are using Akash technical Again contributions whether it be to the docs or just again pieces that showcase different use cases case studies all that kind of stuff if anybody wants to contribute in that way. There's a number of ways to contribute both on the community contributions page as well as more formally on the website. + +Tyler Wright: Denis one thing I want to see and I was looking for very briefly. But do you have a brand guide that's available that we can drop in the chat for Gabriel + +Denis Lelic: Yeah, there's one in the footer section. It's called Brandon press and there's download logo kit since the last brand guide with updated couple of things. So. In this logo kit, there's just basic information included. + +Denis Lelic: which all everyone who's willing to work on Akash as a brand there's basic information there basically logo set and I think it's enough for everyone to get started and totally depends. what the task is looking from designer, but + +Denis Lelic: I think it's a good starting point. + +Tyler Wright: Excellent, and then I would also reference a number of the touch points that you can see on social media really like even some of the banners that you see for the special interest groups in working groups about, tight faces and other elements of style that are used across the brand. So if anybody has any questions Gabriel, if you have any specific questions again, feel free to drop those in sick design or you can ping Denis and I Denis I privately but don't feel like anything's off limits and… + +Denis Lelic: Yeah, yeah, that's true. I mean as I said in this page here,… + +Tyler Wright: questions. I know Dennis is done a great job of establishing and continuing to develop a brand around Akash,… + +Denis Lelic: there's basing basic components of Akash as a brand… + +Tyler Wright: I think is professional very very clean and… + +Denis Lelic: but there's some wiggle room where designers can have Some creative canvas to express themselves,… + +Tyler Wright: fairly modern. But again, there is still at the part of brand elements and Denis correct me from wrong, but there is still room and… + +Denis Lelic: but of course they need to consider. + +Tyler Wright: Holiday for elements of style from different designers. + +Denis Lelic: a communicated Akash as a brand and… + +Tyler Wright: That's Again Play up some of the structure that's already in the brand but They're still creative elements,… + +Tyler Wright: + +Denis Lelic: in a cohesive manner,… + +Denis Lelic: so we're just trying to make sure that + +Tyler Wright: and in coordination with a lot of structure as well. + +Denis Lelic: there's a red line between all different touch points that are produced from our side Red Line meaning. I'm not sure if that's used in English. + +00:15:00 + +Denis Lelic: I helped me out. What was the way is that something that's been used in English like red line meaning all the touch points are kind of connecting and unified brand experience. Maybe that's the better expression. yeah. + +Tyler Wright: I don't know the red line expression that context but I like it, but I think it makes sense a lot of sense. + +Denis Lelic: So yeah. Yeah. yeah doesn't matter who works on what item it at the end of the day should somehow feel connected and that it's coming from + +Denis Lelic: one brand Yeah,… + +Tyler Wright: Yeah. + +Denis Lelic: get Gabriel. Go ahead. + +Gabriel ReyesOrdeix: Okay, so I do have a question. Do you have a list of needs slash deliverables that you're looking for or is this effort is it left to whatever the designer wants to contribute with? Zach I from… + +Denis Lelic: Yeah on. + +Gabriel ReyesOrdeix: what I'm hearing there are a lot of needs in even different disciplines video or video editing Graphic Signs Stills social media content Etc. So can you clarify a little bit on what exactly your meeting contributions with? + +Denis Lelic: Yeah on the marketing side everything. Happens sometimes quite fast. So totally depends on the events and stuff that's happening. So let's say there's ease CC happening in one month in Brussels, which means we would need graphics. for social media, And graphics for side events that are happening at the same time and along with that. We always have to think about what team is going to bring with them in what kind of merch so what kind of Swag are they bringing with them and we have to design all of those and + +Denis Lelic: the end of or the video part it's not that specific per event, but it's more like + +Denis Lelic: editing a video for a guide and stuff like that. So We don't usually record all the events in only happened at our own event for Akash accelerate. but it's always great if one person can handle. Just multiple disciplines at the same time. So we don't have to switch between two three people. + +Tyler Wright: Gabriel this for also from a structural standpoint. What we'll do a better job of is putting all the issues as with specific and specs in marketing and GitHub. It's like a public place to put those in will drop those inside of Discord so we can talk about them at a high level of Discord, but really probably be best to drop information inside the GitHub issues if you're familiar with that little structure and again, But the idea is as Denis mentioned there might be specific items that are needed for specific events, like leading up into Brussels. There's number side events and we need + +Tyler Wright: Six different Graphics leading up to and then we'll put a speck in there. We'll drop it in there. We'll see if you have time and then we'll put a deadline around it how long it'll take you and we just move as quickly as possible because sometimes these have a quick turnaround. There might be other times where you're like, hey, I think that we should do some more videos for this kind of audience and then you can just create or hey, I saw some really cool swag. I want to add some items to the Akash store that I know some people would like really like to wear so it's a combination of deliverables that might be time-based versus more ended creative ideas that you can explore. + +Gabriel ReyesOrdeix: That's what I was referring to. maybe a better way of The question I asked is what does the organizational structure looks like with regards to project management? Because I'm starting in zero today today is zero for me. So I want to know how does the team contributors looks like and who gets how quick a turnaround are projects so that helps I'll look into the GitHub. + +00:20:00 + +Tyler Wright: Yeah, and again, there's been an Howie it has to store historically happened is there's been a number of contributors that have been involved at various points depending on their availability with their day job or if they're in between gigs that have had more time and a lot of those conversations have happened in Discord as we look to get more contributions. The idea is again, there will be a contribution might come from overclock Labs might come from a conversation from the Community member might be something you evaluate. The first order of business is to create an issue inside of + +Tyler Wright: GitHub we'll talk about a live if there's not enough time then we'll drop that issue and Discord and we could talk about an async and be like, hey, I think it's really important. This is why I think it's really important or hey, this is something that's needed and there's a specific spec around it. Once that's spec is determined. What if it's coming from overclock Labs. There will be a deadline on it. And if that's something that you can meet you can say hey, this is something that I will look like I like to take and then once you take it then we'll just coordinate with you. either async or we can set up some time to talk a lot to just make sure that everything is line in the right format in the right,… + +Denis Lelic: Yeah a good point. if you're like coming from an agency or… + +Tyler Wright: sizing Etc to be delivered and… + +Denis Lelic: something like design agency or marketing agency the structure here is a bit different. + +Tyler Wright: then again, if you don't want to take it there might be another Community member say,… + +Denis Lelic: So there's a project manager would usually reach out and… + +Tyler Wright: hey, I have the time and availability to take it and we'll kind of work as Democratic group to kind of determine… + +Denis Lelic: brief you about things and here are the deliverables and… + +Tyler Wright: who should take… + +Denis Lelic: here's the deadline so pretty much everything works through GitHub is Tyler mentioned so It's a bit bit of a different structure than usually is in the design world. + +Tyler Wright: what if we get to the point where there's 15 people trying to go for the same issue, which is a good problem to have then we'll determine a little bit better structure. But right now we've had One person here, maybe two or three people here that are contributed one-off thing. + +Gabriel ReyesOrdeix: Yeah, I understand. + +Tyler Wright: So this is something that we're looking to grow and… + +Gabriel ReyesOrdeix: I am I've worked in the sign agencies,… + +Tyler Wright: evolve and you can help us do that as it continues to scale with more creative contributors. + +Gabriel ReyesOrdeix: but I am not coming from design agency. So I have worked quite a bit within the crypto industry. So I'm familiar with GitHub and Discord as the platforms for project requests. So I just wanted to understand the way this particular. project Works Thank you for clarifying. + +Denis Lelic: Hey Zach. Thanks for joining. So we just covered a couple of design related things anything you would want to talk about on the content side. + +Zach Horn: Hey, yeah, so sorry guys. I was jumping over from another meeting. No, there's nothing pressing on content nice to meet you. I caught the cut the tail end of the conversation. nothing. + +Gabriel ReyesOrdeix: likewise + +Zach Horn: Nothing pressing on my side anything else Denis from a Content design standpoint? + +Denis Lelic: I think not really. Yeah, pretty much everything is covered. So + +Denis Lelic: we only had a couple of contributions in the previous month or a month before that. On the blog, but hopefully we'll see more in the future. + +Zach Horn: most definitely + +Denis Lelic: Okay, cool. Gabriel you can. + +Denis Lelic: D and me or send a friend request on Discord so we can have a conversation there. We can also set up a separate meeting if you want to talk about anything. Just unrelated. + +Gabriel ReyesOrdeix: first thing that will do right away. + +Denis Lelic: Okay. cool + +Tyler Wright: And I'll start to drop a couple of ideas in the marketing repo in the issues for some things that I know have been requested by different members to overclock Labs team on behalf of the community just to have a criteria. But again Gabriel as you start to do a little bit auditing exploring before connecting more with Denis, feel free to suggest anything and add an issues there one other element and again, this will be more of a collective but we'll lean on Denis just because he's done a great job of developing the visual components of the brand is from a creative Direction standpoint again, we try to have guidelines, but I think we'll try to be as Democratic with maybe Denis having the final Hammer if you got to the point of whether we want to move forward with something that might be the only caveat that might be a little bit different than traditional. + +00:25:00 + +Tyler Wright: Like agencies or organizations, but that's how we'll try to do it. all of us are Critical thinkers and receptive to constructive feedback. So it should be fairly open and constructive if designs maybe aren't quite where they need to be yet, and we can just talk about that as a group but maybe have Denis have the final say during these Sig design meetings. + +Denis Lelic: Yeah. I agree. I mean everyone can. bring + +Denis Lelic: their own ideas, but we're going to try try to kind of keep it I know Zach is sometimes the brand Shepherd as well so I know he's gonna Have some thoughts there as well, which are welcome. Of course. + +Zach Horn: It seems like every week I get a new title. I got in content King. What was this one brand Shepherd my business. + +Denis Lelic: brand Shepherd + +Zach Horn: I'm gonna need extended length the business cards. + +Denis Lelic: You can just have a whole set with just different titles. + +Zach Horn: But that's Yeah, we'll do a mix, random for each person. + +Tyler Wright: All right, you just like a bookmark. It just like is a long long-ass card. she can't even want. + +Zach Horn: It's funny. + +Denis Lelic: a flyer basically + +Tyler Wright: exactly Gabriel and + +Zach Horn: Have arrived you have your own custom. Collateral for your business card flyers and… + +Denis Lelic: or just a Roll-Up. + +Zach Horn: there's and all that. + +Zach Horn: exactly + +Tyler Wright: This is scroll. He just unwinds it. + +Denis Lelic: Okay. + +Zach Horn: very cool + +Denis Lelic: we covered everything for today I think so it might be time to wrap it up. So Gabriel, I'll talk to you on Discord and thanks again for joining and I'll see you in a month or if you're interested and web design. And website so our cars.network there's another meaning a meeting happening tomorrow. So feel free to join. + +Tyler Wright: Yeah, I was going to say. Okay. + +Gabriel ReyesOrdeix: I am not interested in that. + +Gabriel ReyesOrdeix: Honestly not and maybe I can provide a little bit of background but the areas in which I feel more comfortable with are branding and editorial but web design and video either or animation. So I'm sorry I can't help with that. + +Denis Lelic: Okay. + +Gabriel ReyesOrdeix: But I'm eager to contribute. I really believe in Akash as a project. And as a designer, I want to put whatever I can to help so I'm eager to contribute. + +Denis Lelic: Good to know and thanks for clarifying. I think it's To know what people are interested in and of course. It's good. You're pursuing that direction. + +Gabriel ReyesOrdeix: Yeah, good. + +Tyler Wright: Absolutely. + +Gabriel ReyesOrdeix: You can take a look at my portfolio that's not everything I've done but it's a little bit of how my stuff looks like. But thank you. + +Denis Lelic: cool + +Gabriel ReyesOrdeix: Thank you for the opportunity. + +Tyler Wright: No, thank you Gabriel. + +Denis Lelic: first major + +Tyler Wright: And again, you have friends that are doing content to to write or to do video. I know we already put Robert to work as well. He's a great member of the Akash community and he does a number of things. So if you have anybody else that is top of mind that you can think of that would be a great addition to helping with content. Feel free to send them to me or just send them to Sig design and we can just get to know them a little bit more and connect with them. + +00:30:00 + +Gabriel ReyesOrdeix: I will always think about it. + +Denis Lelic: Cool Thanks for joining again, and we'll see each other soon. + +Gabriel ReyesOrdeix: Okay. Bye. + +Denis Lelic: Bye. Thank you. + +Zach Horn: to address + +Tyler Wright: maybe but + +Meeting ended after 00:30:36 👋 + From f51088bcf555b69b31fa8a826f212a8c7b2045a1 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Sun, 7 Jul 2024 16:23:57 +0000 Subject: [PATCH 096/138] Create meeting notes for Sig-providers #17 (#615) * Create meeting notes for Sig-providers #17 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 017-2024-05-22.md add transcript chore: add recording link Signed-off-by: Drinkwater * Update 017-2024-05-22.md add transcript and recording linl Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-providers/meetings/017-2024-05-22.md | 210 +++++++++++++++++++++++ 1 file changed, 210 insertions(+) create mode 100644 sig-providers/meetings/017-2024-05-22.md diff --git a/sig-providers/meetings/017-2024-05-22.md b/sig-providers/meetings/017-2024-05-22.md new file mode 100644 index 00000000..2b33df77 --- /dev/null +++ b/sig-providers/meetings/017-2024-05-22.md @@ -0,0 +1,210 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #17 + +## Agenda +- Update on Provider Features +- Praetor Team Updates +- Discussion on Updated Bid Scripts +- Provider Upgrades to Version 6.2 +- Special Interest Group Participation +- Presentation on Provider Build Path + +## Meeting Details +- Date: Wednesday, May 22, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://a6qm5qjrbhmjkmbmsfldmoqzdspsaxypsgfq26wfw6ysnw3xp7cq.arweave.net/B6DOwTEJ2JUwLJFWNjoZHJ8gXw-Riw16xbexJtt3f8U) +- [Transcript](#transcript) + +## Participants +- Andrew Hare +- Anil Murty +- Deathless +- Deval Patel +- Jigar Patel +- Scott Carruthers +- Tyler Wright + +## Meeting notes + +**Introduction:** +- Tyler Wright welcomed everyone to the providers' monthly meeting number 17. + +**Update on Provider Features:** +- Discussion on provider features following the open-sourcing of Praetor. +- Jigar and Deval gave updates on their work post-acquisition. +- Recent hackathon focused on provider contributions. + +**Praetor Team Updates:** +- Repositories are now open source. +- Recent hackathon encouraged provider side contributions. +- Update on the progress and next steps. + +**Discussion on Updated Bid Scripts:** +- Scott Carruthers working on [updated bid scripts](https://akashengineers.xyz/provider-build-scripts/) in Go. +- Lively discussion on the impact of these scripts on providers. +- Encouragement to follow updates and participate in discussions. + +**Provider Upgrades to Version 6.2:** +- Recent upgrade to provider version 6.2. +- Importance of upgrading to the latest version. +- Instructions and support available for the upgrade process. + +**Special Interest Group Participation:** +- Encouragement to get more involved in specific projects. +- Opportunities to participate in special interest group meetings. + +**Presentation on Provider Build Path:** +- Scott Carruthers has been working on simplifying and speeding up provider builds on Akash. +- Presentation and internal documentation shared for feedback and testing. +- Active community engagement for feedback on the provider build path. + +**Additional Updates:** +- Discussion around the new bid scripts. +- Two new provider horizon upgrades to version 6.1 and 6.2 rolled out. +- Testing K8s multi-node products for improved provider stability. +- Encouragement to contribute to open-source repositories. + +**Hackathon:** +- Hackathon ended on May 17th with a focus on provider tooling and monitoring. +- Judging of projects is ongoing, with more information to be released soon. + +**Provider Reliability and Reputation:** +- Discussion on reputation and provider reliability, initially on Discord and now on [GitHub](https://github.com/orgs/akash-network/discussions/576). +- Encouragement for community involvement in ongoing discussions. + +**Praetor Strategy:** +- [Document](https://github.com/akash-network/community/blob/main/product-strategy/praetor-akash-provider-console-strategy.md) outlining the next steps for the open-source Praetor tooling shared for community review and feedback. + +**Cosmos SDK Upgrade:** +- Ongoing upgrade to Cosmos SDK 47 from 45. +- Significant impact on the codebase requiring extensive testing. +- Community involvement in testing will be sought as the upgrade progresses. + +**Other Announcements:** +- Andrey is on vacation, so please reach out to other team members if needed. +- Akash Accelerate event on May 28th in Austin, with presentations on various parts of the Akash ecosystem, including the provider. + +## Action Items +- Scott Carruthers Continue to work on the provider build path and gather feedback from the community. +- Jigar Patel and Deval to support testing and contributions to open-source repositories. +- Tyler Wright to ensure the [product and engineering roadmap](https://github.com/orgs/akash-network/projects/5/views/1) is shared and accessible. +- Review of Praetor cloud provider console strategy document and provide feedback. +- All Attendees prepare for testing the new Cosmos SDK and provide feedback when requested. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: Just all right, welcome everybody to providers monthly meeting number 16. + +Tyler Wright: During these providers on the network. We talked about provider features at the last meeting. We got an update because it was the first meeting after Craig tour was open source, and the pray to our team was acquired by Jigarette and Deval gate a little update. We talked a bit about next steps as we continue to move forward. I will give jigar into all a bit time to give an updates and all the things that they've been working on because I know again the repos are now open source, and there was a recent hackathon where again folks just starting to think about ways to contribute on the provider side. + +Tyler Wright: Also at the last meeting there was a lively discussion around the updated bid scripts. I know that Scott who's here on the call has been working on updated bid scripts and changing the structures. So, I believe it's in go and it's just Lively discussion about how that affect providers. So again a great participation from the group on that last call. Since the last meeting, there's been I believe a couple of Provider upgrades. I believe now. We're on provider versus 6.2 again. If you're not on that most recent version, please look for messages in the provider announcements Channel. And if you have any questions on how to upgrade again, feel free to reach out to somebody or just follow the Specific Instructions that have been outlined by Scott and Andre. + +Tyler Wright: Before I kick it over to the prior team to give it update or really the overclock team now, but to give an update on all things related to Predator. I do want to see Scott if there's anything that you wanted to talk about the bitage and script that the follow-up the last call. + +Tyler Wright: Don't kill obliged. I know that you might be moving around. + +Tyler Wright: excellent + +Tyler Wright: many of these issues are trapped in the product and Engineering roadmap, which I've attached or I've shared in the chat and I'll make sure it's in the notes as well. If anybody has any questions or comments or wants to get more involved in any specific projects again, feel free to drop a comment obviously take this time during the special interest grouper provider and other special interest group meetings to get more involved live one other thing that I want to call out and I believe This is something that jigarette and Deval have been working in tandem along with their prayer related efforts is around Scott has been working with members of the community but has been working for the last couple of months on making it easier for and faster or individuals to build providers on a cash. He's been sharing do + +00:05:00 + +Tyler Wright: presentation which I'll drop in + +Tyler Wright: I'll drop in the chapter folks. That's very Alpha and just like some core engineering Internal Documentation. It's been used again. He's been connecting with members of the community to test out this provider build path get feedback from the community get feedback on documentation. This is something that's being actively worked on by the core team and I know that jigargar and Deval had been supporting with testing again, they'll talk a little bit about it a little bit later… + +Jigar Patel: I sure so to start from the last meeting… + +Tyler Wright: but there is a ticket that Andre Jigger and Deval have all been testing against… + +Jigar Patel: since then. + +Tyler Wright: which I've dropped in the chat right there. + +Jigar Patel: We open source all of our repository in the GitHub. + +Tyler Wright: So again across the provider, there's been a recent upgrade to provider version 6.2 that's been tested and… + +Jigar Patel: So now all the new features… + +Tyler Wright: number of providers have been upgraded to that version again,… + +Jigar Patel: if anyone wants to contribute, it's welcome there. + +Tyler Wright: there was discussion around the big scripts and… + +Jigar Patel: So that's a great thing. And since then we also added two new provider Horizon upgrade the one and… + +Tyler Wright: others at Go version. That is Scott mentioned this quote complete and there will be more information. + +Tyler Wright: Made a relative to the community coming soon and… + +Jigar Patel: Sorry the 6.1 and… + +Tyler Wright: then again something that's been a focus of the core engineering team has been provider stability and… + +Jigar Patel: 6.2 that's also rolled out on the public. + +Tyler Wright: making the provider build process more efficient and… + +Jigar Patel: Currently. We are testing k3 a visibility of the q3s multinode into products and… + +Tyler Wright: that is in testing phases right now with members of the core team as well as a community to get that over the line. So look out for updates there soon. + +Jigar Patel: environment. So once that's done put those into + +Tyler Wright: Jigar, I know I might have stolen a little bit of Thunder from all the updates that you have,… + +Jigar Patel: Basically change the way… + +Tyler Wright: but I want to pass the floor off to you… + +Jigar Patel: how okay3s or… + +Tyler Wright: because you usually do a great job of giving updates and… + +Jigar Patel: sorry all the multinode provider build happens in Predator from K. + +Tyler Wright: all things related to the greater provider cooling. So I just want to see… + +Jigar Patel: Its to k3s because we are already using k3s in a single node. + +Tyler Wright: if there's anything that she wanted to update the community on here today. + +Jigar Patel: That I understand. + +Tyler Wright: Thank you very much again. I believe there's three repos that I've been added by the prior team that now all open source. I dropped in they're all in the constant Network organization. I believe one's p back in prayer front end and then the last one I believe is a greater security. So again as jigar just mentioned if anybody wants to get feel free to chime in and Discord channel for ecosystem Predator again, you can start getting involved and see looking around and specific issues that might be in those repo or feel free to again start a conversation and providers and we'll make sure that the necessary people are tagged and we can continue conversations between meetings there. + +Tyler Wright: thank you very much for that update. + +Tyler Wright: Again, I just want to mention on the hackathon just ended May 17th. There was a track related to provider Cooling and monitoring tooling. So again, there's some projects that are being judged right now. So look out for some more information as time goes on if any of those continue to mature, but again, there was a number of great entries across the hackathon. So again really excited for all those that participated to all of that participated. Thank you to all those that helped people that were to participating in the hackathon and looked out for more information there coming very very soon. + +00:10:00 + +Tyler Wright: Russia all Other than that, we always go through the + +Tyler Wright: Discussions and see if there's any discussions happening. I know that there was a discussion happening around reputation and provide a reliability. It started off in Discord and it ended up in GitHub discussion. I know this is something that's been previously discussed a while back. We didn't move forward with at that time, but I would just ask if anybody has any thoughts opinions here again, feel free to get involved in this discussion. I know Anil has already done. thank you Anil for doing so but if anybody else wants to get involved or again. Please please get involved in those discussions and just get feedback. Just keep those conversations going. + +Tyler Wright: Her anil's response. I do want to drop this in the chat here today. We talked about this at the last meeting, but there is a document that's been put together by jigarette Duvall Anil and the core team around the pratera cloud provider console strategy next steps. If anybody wants to understand at the highest level kind of what the core team is thinking about in terms of next steps for the open source Trader cooling. Please feel free to look at this document. And then again, we can have discussions about this either async in Discord or if anybody has any questions we can have that as an agenda item as we continue to move forward month over month. I'm sure they'll be a lot of progress and updates coming very soon there. + +Tyler Wright: Before I continue on does anyone have any questions about anything that's been discussed thus far. + +Tyler Wright: Does anyone have any additional agenda topics that they want to talk about here today, but haven't added them to the agenda yet. + +Tyler Wright: One thing I will note just because it's been something that it's come up in the past. I know that Andre who's usually on these calls and is usually supporting a number of providers along with Scott Jigger Deval many others in the community. He's taking some personal time. He's on vacation. So if you see less availability from Andy recently, I know in the past people thought, was he sick with the injured? No, because how responsive he is. He's just taking some personal time. So he should be back in a couple weeks or so. I'm more available with more availability. It does have his computer on with him, but I would ask that folks that usually connect with them again. Feel free to reach out to myself and Insider or somebody else in the community over the next a week or so. Andy's on vacation. + +Tyler Wright: those are all of the topics that I wanted to cover for this week against sometimes you have longer meetings where there's a number of folks that are asking specific questions and this month and I might just be a quick update and then we can continue to talk async. Before I let y'all go is there any other topics of discussion that anybody wants to discuss here today? + +00:15:00 + +Tyler Wright: all if not, then I'll let you all go today. I'll make the recording and notes available shortly. And then again if anybody has any questions or comments between meetings, please feel free to drop those in Discord and we will look to get those solved as previously mentioned in the Sig chain meeting yesterday. One of the bigger items for members of the core engineering team is around the continued upgrade to 47 from 45 where we are right now again, that's going to touch all parts of the code base. So on the provider side again, there will be a fair amount of testing over next couple of months. So if anybody, I know some folks on this call certainly have helped with testing the past. So again, we'll be looking to reach out to you as we get closer to testing the new Cosmos SDK and some of the features. + +Tyler Wright: So again, thank you to all those that help out that testing but look out for that coming soon as well. + +Tyler Wright: All Y'all have a great rest of the day again. If you have any questions for me, please feel free to reach out but we will close out this meeting for this month. And then again, I'll see you all next month Akash accelerate is happening a week from yesterday, May 28th. So again, please feel free to join us live in Austin. There will be a number of presentation. I'm sure related to all parts of the Acosta ecosystem including the provider. But again, really looking forward to collaborating and connecting between meetings. And again, if anybody has any questions or comments about anything provider related, please feel free to drop them in the state provider Discord Channel. Hope everyone has a great rest of their day. Thank you very much for joining. We'll talk soon. + +Tyler Wright: Goodbye. + +Meeting ended after 00:15:30 👋 + From 8d521f131a27e7df6462ec7edb845699b04a02c5 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Sun, 7 Jul 2024 16:27:22 +0000 Subject: [PATCH 097/138] Create meeting notes for sig-community #16 (#603) * Create meeting notes for sig-community #16 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 016-2024-06-11.md update formatting, add transcript, and recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-community/meetings/016-2024-06-11.md | 243 +++++++++++++++++++++++ 1 file changed, 243 insertions(+) create mode 100644 sig-community/meetings/016-2024-06-11.md diff --git a/sig-community/meetings/016-2024-06-11.md b/sig-community/meetings/016-2024-06-11.md new file mode 100644 index 00000000..c6cc43c8 --- /dev/null +++ b/sig-community/meetings/016-2024-06-11.md @@ -0,0 +1,243 @@ +# Akash Network - Community Special Interest Group (SIG) - Meeting #16 + +## Agenda +- Overview and updates on community initiatives. +- Discussion on recent events: Akash Accelerate and Consensus 2024. +- Q3 events proposal and planning, including ETHCC. +- GitHub discussions and community involvement. +- Hackathon updates and future planning. +- Developer onboarding program update. + +## Meeting Details +- Date: Tuesday, June 11, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://nl4ez6metcnz3sdkdgvxj6b2opl74ywekhhfqfj3smj6m4in3e2a.arweave.net/avhM-YSYm53IahmrdPg6c9f-YsRRzlgVO5MT5nEN2TQ) +- [Transcript](#Transcript) + +## Participants + +- Amanda Keay +- Andrew Gnatyuk +- Joao Luna +- Robert Del Rey +- Tyler Wright +- Zeke E + +## Meeting Notes +**Introduction and Welcome:** +- Tyler Wright welcomed all attendees and introduced the meeting in the absence of Adam Wozni, who is on paternity leave. +- The focus was on discussing community efforts, including hackathons, events, and other initiatives. +- Attendees were encouraged to add agenda items in the chat if they had specific topics to discuss. +- Tyler noted the detailed discussions during the steering committee about Akash Accelerate and Consensus 2024. + +**Q3 Events Proposal:** +- Tyler highlighted that the Q3 events proposal would soon be up for discussion. +- Several events for Q3 and Q4 2024 have been agreed upon by the SIG Community. +- Participants were encouraged to share event ideas in Discord, either in the SIG Community channel or the working group for events 2024. + +**ETHCC Presence:** +- Amanda Keay provided updates on the planned participation in ETHCC in Brussels. +- Akash will have a significant presence, participating in nine separate events. +- Akash will host three of their own events, with Greg and Neil speaking at eight other events. +- Amanda is waiting to hear if Greg's talk was accepted for the main ETHCC conference. +- Akash did not get a sponsorship for the main event but will actively participate by visiting booths and engaging with attendees. +- The goal is to have Akash represented in at least two locations simultaneously during the event period, starting from July 7th. +- Amanda offered to share a document detailing all planned side events. + +**Insider Support for Events:** +- Tyler mentioned that some insiders have applied to support the events, and the finalization of this group is pending. +- Even those without tickets to ETHCC might be able to support side events and programming. +- Announcements will be made in the Insiders channel soon. + +**SIG Economics Announcement:** +- Tyler announced that SIG Economics, usually held the first week of the month, will take place next Tuesday, June 18th. +- Encouraged participation from key stakeholders and community members for discussions on AKT and related topics. + +**GitHub Discussions and Community Involvement:** +- Tyler encouraged attendees to participate in ongoing discussions on GitHub. +- Shout out to Roger and others for their active participation and valuable questions. +- Discussions include topics related to Sig chain cost reduction and an upcoming hackathon opportunity in India. +- Members of the Overclock Labs team and Insiders are coordinating to represent Akash at the hackathon in India. +- Follow-up conversations from the Akash hackathon were also mentioned, with winners announced on Dora Hacks. + +**Hackathon Updates and Future Planning:** +- Tyler and Robert Del Rey discussed the recent hackathon and future opportunities, including a quadratic funding round proposed by Dora Hacks. +- Overclock Labs aims to support smaller hackathons leading up to larger events in the fall/winter. +- Discussion about using community pool funds for hackathons and spreading awareness among builders globally. +- Planning for the next major hackathon should start before late August, with a committee to be formed during the next SIG Community monthly meeting. +- Suggestions for hackathon tracks are encouraged and can be shared in the hackathon channel on Discord. + +**Developer Onboarding Program Update:** +- Tyler gave a shout out to Robert and Piber for their work on the developer onboarding program. +- The wrap-up for the program was shared, and no new missions are currently being opened until discussions are complete. +- Collaborations with other projects like Galaxy 2 are in progress, and future missions might be seen through this collaboration. +- Robert confirmed that most rewards have been paid, with the remaining claims closing by Friday, June 14th. + +**Closing Remarks** +- Attendees were encouraged to drop track suggestions in the SIG Community or Hackathon channels in Discord for discussion. +- Tyler mentioned postponing some of the Zealy meetings for June and highlighted upcoming working group sessions and SIG Economics discussions. +- The next SIG Community call might be adjusted to accommodate those attending Brussels events. + +## Action Items +- All Participants to Suggest additional events for Q3 and Q4 2024 in Discord, either in the SIG Community channel or the working group for events 2024. +- Amanda Keay and Team to coordinate the inclusion of any new event suggestions into the Q3 proposal. +- Tyler Wright to Facilitate ongoing discussions about the Q3 events proposal and ensure all contributions are considered. +- Robert Del Rey to finalize pending reward claims for the developer onboarding program by June 14th. +- Tyler Wright to follow up with hackathon winners via email to discuss next steps and future involvement. +- Tyler Wright and Amanda Keay to finalize the group of insiders supporting the events in Brussels. +- All Participants encourage to start thinking about potential tracks for the next hackathon and drop suggestions in the SIG Community or Hackathon channels. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to Sig Community on June 11 2024 again this special interest group for Community needs to discuss all things related to Akash Community efforts. I think there's discussions about insiders here around the hackathons around events and a number of other community facing initiatives. If anybody has any agenda items that they want to discuss here, feel free to drop them in the chat. Usually this meeting is led by Adam wozni head of community for overclock labs and really + +Tyler Wright: one of the main Community Builders and the cash ecosystem for some time program of a number of other programs. He is currently on paternity leave while he is out myself and the events lead at overclock Labs. Amanda will do our best to try to fill in give updates on all things events hackathons and all of things going on in the community side again, if anybody has any specific items that they want to discuss here today. Feel free to drop them in the agenda. the last meeting there was a lot of discussion leading up into Akash accelerate and consensus 2024 again, there's been a lot that's gone on. + +Tyler Wright: At those events and obviously you talked in great detail about it during the steering committee. Is there anything that anybody wants to discuss again? That hasn't been discussed on the Akash accelerate or the consensus 2024 said + +Tyler Wright: One thing to look out for and I know there's been a lot of planning in this sig Community around it is Q3 events proposal is going to go up for discussion soon. I know there's been a number of events that have been agreed upon here as a part of the Sig Community for Q3 and Q fuel Q4 2024. And then I'm sure there's the discussions beyond that as well. + +Tyler Wright: again, look out for a discussion happening soon. And please feel free to get involved if there's any events in Q3 or Q4 that have not been talked about that folks want to add potentially to listen and discuss in Discord again, feel free to go into Discord and either in sick Community or the working group for events 2024 to drop in any of those events. I know there's a number of opportunities all over the world that people bring to our cash. So feel free to drop anything that makes sense for there to be representation whether by insiders members of overclock Labs core team or combination of both feel free to drop those in State Community or working group for events. + +Tyler Wright: Cool again, as a part of that Q3 events proposal. I know that there is a lot going on as it pertains to ECC and… + +Amanda Keay: Yeah, thanks Tyler to say we're having a big presence is an understatement. + +Tyler Wright: all the events going on in Brussels during that week the neglers some of those number of other things going on. + +Amanda Keay: I feel we are participating in nine separate events. + +Tyler Wright: I do want to pass it over to Amanda to talk about all the work that's been going on there. + +Amanda Keay: We are hosting three of our own and Greg between Greg and… + +Tyler Wright: I know that there is a huge presence expected in Brussels. + +Amanda Keay: a Neil speaking at the events. + +Tyler Wright: So I'll hand over to Amanda to talk a little bit about what's going on. + +Amanda Keay: We have eight separate events that we're going to be speaking at that's what I should say still waiting to hear on whether or not Greg. + +Amanda Keay: And his talk was accepted for the main CC conference. We will also be walking around that we didn't get a sponsorship for the main event, but we'll be hitting up everyone's booths and stuff at the main conference as well. So I think we're in a good place right now. Our goal is to be everywhere all at once. So at any given time I think a cautious represented in at least two locations. So most of us are gonna be landing on the sixth and then events start ramping up on July 7th. So if anyone is interested in seeing all of the events that we're planning on being at during that day side events wise, I'm happy to share a little document that I put together just pretty much + +00:05:00 + +Tyler Wright: Thank you very much. Does anyone have any questions they want to talk about here right now in terms of anything. Amanda just talked about. + +Tyler Wright: One thing that I will add just for transparency sake is I think Amanda might have alluded to us but there's a number of insiders or not a number but there's some insiders that have applied to support all of these events. We are looking to finalize that group in the next very soon. I know that's waiting on me. And I know Amanda's pushing his harsh as possibly can to get this finalized. One thing that I am trying to see because there are so many events if there's a possibility even if some folks may not be able to go to ECC because a tickets only allocated for certain amount of tickets, but if folks can be there to support in other ways all the side events and programming so again, look for announcements in the Insiders channel for all those that have applied and look to finalize that very shortly following the same process at + +Tyler Wright: Us thank you very much Amanda for that update. Again, look out for that Q3 events proposal that will be going on upper discussion and people can give feedback make sure that everyone's aligned and then go on change shortly after that. + +Tyler Wright: I see Andrew in the crowd here today. I do want to shout out Sig economics, which will be happening next week. I know it normally happens the first week of the month that I know there's a number of topics that are worth discussing. I've seen some of that stuff in general chat as well as in the Sig economics Channel, again want to make sure that number of key stakeholders both in the community and some folks in overclock Labs tea team are able to join and have some Lively discussions there. So I'm doing a Shameless plug for Sig economics, which is moves from again the first week of the month to it'll be happening next week. The date is + +Tyler Wright: Next Tuesday the 18th. So I just want to get put that on people's radar and I'm hoping that Andrew can be there like you normally is to participate in some of those discussions as we continue to move forward things on the akt side as well. + +Tyler Wright: No problem. + +Tyler Wright: Again, there's a couple other things that I specifically wanted to cover. There's a couple of conversations that have been happening around and GitHub discussions. Again, if anybody here on this call can continue to get involved in those discussions. Shout out to Roger and number of other people the community that are, asking great questions and getting some feedback from people that would be great to continue to push and that direction. There's a number of + +Tyler Wright: Conversations we talked about wondering Sig chain around the cost down, but I would love for folks to get involved in that. I know something that Adam is looking to push forward with in the future as the cost Community continues to grow and evolve. But again, there's a number of conversations there on the hackathon side. There is a hack of opportunity in India around with some college students that they've talked about, wanting some Akash representation there. So please get involved in that conversation again members of the overclock lab team has been talking because it is a small amount that they're looking for besides just the presence there and there is a member of the Insiders that currently a couple folks in the Insiders that are currently in India region. And so again, it's a potentially small output + +00:10:00 + +Tyler Wright: that there is a hackathon funds from the community pool available for potentially a number of builders that again could be exposed to Akash with members of the Insiders that can represent Akash there live and in person, so that's something that live in GitHub right now. + +Tyler Wright: As well as I believe that there was some follow-up conversation from the Akash hackathon and obviously those winners have been chosen you can go to Dora hacks to learn more. I'll drop that in the chat for anybody that wants to follow up are about to results. I know that one thing that I want to do is from overclock side is just get to get together with all the people that won or place with any track. So again, I will look to follow up with people via email just to see what their next steps are with various hackathon projects and see how they can get more involved. So again, that's something that I will be doing with some other folks. + +Robert Del Rey: Thanks, and you're human, right? + +Tyler Wright: Robert I know that you are very Hands-On in the hackathon and… + +Robert Del Rey: awesome So here we go. Yes, as you say yesterday. I spoke with George from Dora hacks we discuss. + +Tyler Wright: provided a great summation follow up after talking to Joy from the door hacks team. + +Robert Del Rey: how the hackathon went on their side And yeah. + +Tyler Wright: Did you want to talk about anything here today, or do you want to save it for just online conversation again? + +Robert Del Rey: What I want to give you some context about is that they suggested us a cash. + +Tyler Wright: Feel free to Take the mic and… + +Robert Del Rey: To do a quadratic funding round. + +Tyler Wright: talk a little bit if you so desire. + +Robert Del Rey: That's something that thorax has going on and they asked us… + +Tyler Wright: Yes, I can. + +Robert Del Rey: if you want to do that. We just gotta let them know and yeah. + +Robert Del Rey: basically with the quadratic funding it's like a second chance or hackathon participants to submit their reels and + +Tyler Wright: Thank you very much, again For me, there were a number of great projects and great entries that came through the hackathon. I think Adam mentioned this during steering committee, but there was some reservations about the turnout but in typical, just life. There are a number of entries that came in at the last minute and again, There are a number of entries actually came in after the deadline. So yeah, just something to think about From the overclock side. We want to continue to push the forward some of these smaller hackathons. I think was a number of events happening leading up to + +Tyler Wright: leading up to ECC and all the stuff in Brussels as well as India hack upon we're talking about and then do something significantly larger in the fall slash winter. But again, I would love to have open discussion around what door hacks is offering and just hear from the community. I mention the following up with Pope folks that have participated to see what their thoughts and path forward is so that also potentially going to decision. I saw a hand up, but now it's down. + +00:15:00 + +Tyler Wright: Yeah, so there is an opportunity. I think much of the available community pool spend will be available for the bigger hackathon and September October November maybe that even gets broken up into two smaller hackathons or meet the three criteria again. There are some funds from that pool that can be used for some of these smaller hackathon efforts some hacker events that will be involved in don't even require any funding from us just like spreading the word and awareness but as the Indian hackathon as an example, + +Tyler Wright: The idea as I've thought about it with Huey and some other members of the community is to use, small amounts of money from that larger pool of hackathon funding to support some of these smaller hackathons and spread awareness to builders all around the world. So, again very much up for discussion, but that was a thought process. That I've been thinking about with Huey for some of the available community pool spend used for hackathons. + +Tyler Wright: I believe Zeke put a question in the chat, when will planning start for the big hackathon at the end of the year? It has a great question. I think the idea was to initially wait until late August to start planning. I do think we should start playing a little bit before that and then when potentially Adam comes back there's some things in place. + +Tyler Wright: I would vote that going into the next Sig Community monthly meeting. Maybe we have that and talking point and we can start to put together a committee and start to think about what and end of 2024 or a Q3 or Q4 hackathon to look like and start to put some of the items in place that we know have been successful from the previous two hackathons Zeke. What do you think about that or others on this? Call Robert? I know you've been active in both hackathons. Do you think we should wait until September to get started or do you think there's some planning can start earlier than that? + +Robert Del Rey: pay Tyler + +Tyler Wright: Yes. Yeah, go ahead Robert. + +Robert Del Rey: there was gonna say I agree with you. Maybe we can start it as we can install talking in the next Community monthly call. And from there we can start working on the hackathon. + +Tyler Wright: Excellent. I think Zeke breaks up a good point that I would like the community to be thinking about a little bit more especially insiders in vanguards is what are some tracks that you see that maybe folks aren't building around right now that would add events value to the constant Network whether it be user experience standpoint or just tooling + +Tyler Wright: or anything else, if we can start to think about tracks going into next meeting and then again start to think about a committee and just refining some of those tracks or ideating around some of those tracks. I think that would go a long way because I know historically that's been the most challenging part and the most time consuming part is determining which tracks make the most sense so again if there's anything that you all see on the community side, whether it be tooling or themes on the provider side deployment or elsewhere that you think kids are worthy of a track. Please start to drop those in sick community and we can start to talk about those going into next month. + +Tyler Wright: excellent All Is there anything else that anybody wants to discuss I would someone asking chat. Where do we suggest attracts? I believe there is a hackathon channel. If not, you can also drop them in the Sig Community Channel and then we can start having discussions. I do see a hackathon channel here in Discord again, feel free to drop into Community or hackathon. And what's the threat has begun then we can just continue that thread dropping in tracks. Preferably the working group for their cash hackathon makes the most sense. + +00:20:00 + +Tyler Wright: One other thing and again, we talked about it during the steering committee. shout out to Robert and piber for all the work that they did around the developer onboarding program. They dropped a wrap up yesterday again. I'll drop that in the chat for anybody. there's no more missions at this point. I believe everyone's been paid out. But this is a program that I would like to see continue. I know that again many of the Milestones were hit I know that there's been new members that come in through these kinds of programs of For lack of a better word like mercenary types that are independent contributors are looking for projects where they can earn. + +Tyler Wright: Rewards for their time there have been a number of developers that I have. No at least heard about a class dsili and then have come in shut off their abilities and have been connected as Builders and looking to build again is more building opportunities present themselves, whether it be the maturity of the core code base or whether it be maturity of console 2.0 and other tools, I believe there's gonna be more opportunities for people to contribute. So again, I would love to see this program continue, but I do want to see if Robert has anything he wants to mention here, after the wrap up went out just yesterday, so Robert take it away. + +Robert Del Rey: Sure, just one thing. Yeah, we are not opening new missions for now until we finish the discussions. However, we are working on join collaborations with other projects on C and on Galaxy 2. So maybe the community will be able to see approximations about a cash and missions about other communities through City. So yeah, I just wanted to drop that. yeah. + +Tyler Wright: excellent I know that Again, is there anything else you want to highlight as you continue move forward? We're gonna postpone some of the zealy meetings currently that working group. and then again, I'm sure they'll be further discussions after the wrap up and next steps. But Robert, is there anything that you want to highlight on this call today? + +Robert Del Rey: Thanks, Yeah, that's a great point. We won't be having the weekly call at least during the month of June. And the other thing I wanted to say is that most of the rewards have been paying have been paid however, a few people still have and playing their rewards in the claim window will close this Friday 14. Just wanted to say to + +Tyler Wright: Thank you very much. cool again. Is there anything else that anybody wants to discuss here live? + +Tyler Wright: If not, then I believe prior to the next call many folks including Amanda and others will be in Brussels. If from the time conflicts, we might move this call back a little bit to accommodate that but again as we continue to look forward, I'll be following up with some of the folks related to the hackathon. If anybody has any thoughts or opinions about the quadratic funding from Dora hacks, please make those opinions hurt and sick community. We're going to talk to think about the next That's big Akash hackathon and folks can start to think about tracks and going into our next meeting. we'll spend some time, putting together a committee and getting as much as we can ready in anticipation for again another successful hackathon. + +Tyler Wright: Other than that again, there's a number of things going on the Insiders front again, appreciate all the folks that had watch parties. We talked about that during the steering committee. But again, feel free to get involved. There was a successful update upgrade rather to a cash main net 12. So shout out to all the validators. There will be some more messaging available soon to the providers to upgrade their home charge. So look out for that. But again much appreciated everyone's time. Thank you Amanda for walking us through all the work you've been doing leading up to Brussels. If anybody wants to get it more information on there, please again, drop Amanda message and see Community or elsewhere. Thank you Robert for all the work that you've been doing and pibber as well around. + +00:25:00 + +Tyler Wright: The developer onboarding program as well as a follow-up from the Cosh hackathon. And again, we'll continue to stay up to date in Discord lookout for a number of meetings as a working group for provider audits that's happening this week. I know hybrid def I got some money for his team to do from the community pool spend and so you can track that on product and Engineering road map, but there is a working group session this week as well as again a number of other working group sessions and sigs that you can come to with also highlighting the Sig economics,… + +Robert Del Rey: Thank you so… + +Tyler Wright: which will be very Lively next week with a number of conversations. + +Andrew Gnatyuk: he + +Robert Del Rey: Tyler. Stay safe. + +Tyler Wright: so again We'll be in touch with those that will be going to Brussels very very soon much appreciate everyone's time today. + +oo o: prosper + +Tyler Wright: I hope everyone has a great rest of their day and great rest of the week and we'll talk online. And there's Adam always and she's calls. + +Tyler Wright: Luna I'll follow up with you offline about who's going to Brussels that's still being decided we talked about that the top of the call, but again, I'll follow you online but is Adam always says See you in the metaverse. whatever + +Meeting ended after 00:26:52 👋 + From 3a631c68520b1ef786c9cbfa0ed0afa162083a28 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 8 Jul 2024 23:03:54 +0000 Subject: [PATCH 098/138] Create meeting notes for sig-support #34 (#622) * Create meeting notes for sig-support #34 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 034-2024-06-26.md add video recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-support/meetings/034-2024-06-26.md | 375 +++++++++++++++++++++++++ 1 file changed, 375 insertions(+) create mode 100644 sig-support/meetings/034-2024-06-26.md diff --git a/sig-support/meetings/034-2024-06-26.md b/sig-support/meetings/034-2024-06-26.md new file mode 100644 index 00000000..a785f4ac --- /dev/null +++ b/sig-support/meetings/034-2024-06-26.md @@ -0,0 +1,375 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #34 + +## Agenda +- Triaging issues in the support and console repositories. +- Discussing support feedback from Vanguard insiders and community members. +- Restructure of the meeting format. + +## Meeting Details +- Date: Wednesday, June 26th, 2024 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://edy24xoc5isqb4ilutntgush3jmsnlcnfjaajdnsr2f5d34caktq.arweave.net/IPGuXcLqJQDxC6TbM1JH2lkmrE0qQASNso6L0e-CAqc) +- [Transcript](#transcript) + +## Participants +- Tyler Wright +- Scott Carruthers +- Andrey Arapov +- Damir Simpovic +- Rodri R + +## Meeting Notes + +- **Introduction:** + - Tyler Wright welcomed everyone to the biweekly support meeting. + - Overview of the agenda items: + - Triage issues in the support repo and console repo. + - Gather feedback from Vanguard insiders and community members to improve support documentation and identify recurring themes. + - Discussion on the restructure of the meeting. + +- **Issue Triage:** + - Scott Carruthers took over to triage issues. + - Only one issue was awaiting triage: + - **Issue:** Kubernetes concern for providers spawning too many processes within a container, affecting the host and potentially crashing it. + - **Discussion:** + - Scott asked if Andrey Arapov had seen the issue before. + - Andrey confirmed it was the first time he saw the issue. + - Scott provided a brief overview and suggested some testing to understand the problem better. + - Andrey agreed to review and test the issue further. + - The issue was assigned to Andrey for initial review and labeled as P2. + +- **Feedback from Discord and Other Channels:** + - Tyler Wright opened the discussion on feedback from active Discord members. + - **Damir Simpovic:** + - Mentioned an increase in new, unknown accounts asking directly for partnerships without proper introduction. + - Suggested a filtering mechanism to avoid tagging core team members without proper context. + - **Tyler Wright:** + - Agreed with Damir and suggested training insiders and community members to ask follow-up questions to filter legitimate requests. + - Highlighted the importance of understanding what the person is looking to do with the Akash Network before tagging core team members. + - **Rodri R:** + - Agreed with the need for a filtering mechanism. + - Mentioned issues with bots starting conversations and sharing scam links. + - **Scott Carruthers:** + - Suggested creating a dedicated channel for new partnerships and integrations. + - Emphasized the need for a structured approach to handle partnership requests. + - **Tyler Wright:** + - Proposed training insiders to ask specific questions to filter out non-serious requests. + - Suggested using a standardized set of questions to streamline the process. + +- **Discussion on Uptick in Activity:** + - Tyler Wright asked if there was an uptick or downtick in provider activities and deployments within the ecosystem. + - Requested continued monitoring of this trend to see if documentation improvements are reducing the number of questions or changing the types of questions being asked. + +- **Meeting Restructure Proposal:** + - Tyler Wright discussed a preliminary idea to combine the support and documentation meetings due to their overlap. + - Proposed having a monthly SIG engineering core meeting focused on blockchain and technical issues, reducing the frequency of the SIG support meeting. + - Emphasized the importance of triaging issues transparently to encourage community participation. + - Acknowledged the learning curve for new contributors and suggested streamlining the process for more effective engagement. + - Asked for initial thoughts, concerns, and feedback on the proposed restructure. + +- **Sig Clients and Console 2.0:** + - Tyler Wright mentioned discussions in the Sig clients meeting about Console 2.0 and its impact on the Praetor team. + - Scott Carruthers has been refining provider build upgrade paths with ongoing internal discussions and community feedback. + - Testing remains a key next step for finalizing these upgrades. + +- **Upcoming Meetings and Working Groups:** + - Tyler reminded attendees of several upcoming meetings: + - Sig Providers meeting in 29 minutes. + - Akash website and documentation working group meeting tomorrow. + - Steering committee meeting tomorrow afternoon. + +- **Documentation and Sig Website Meeting:** + - Scott Carruthers raised concerns about the overlap and relevance of documentation discussions within the Sig website meeting. + - Tyler clarified the hierarchical process for merging documentation items, which involves checks from Scott or Andrey. + - There is no expectation for Scott or Andrey to join every Sig website meeting unless there is a specific agenda item relevant to documentation. + - Tyler emphasized efficient use of core team members' time, ensuring agenda items relevant to them are prioritized. + +**Clarifications:** +- **Participation in Sig Website Meeting:** + - Scott and Andrey are not required to join every Sig website meeting. + - They will join only if there is a specific documentation-related agenda item. + - Tyler will ensure relevant items are scheduled early in the agenda to optimize time management. + + +- **Handling Documentation Updates:** + - Scott Carruthers raised a concern about managing documentation updates, especially when the core team is busy. + - Tyler Wright suggested that if a core team member has the time and willingness, they should handle the updates directly for efficiency. + - If the core team is unable to handle it, creating an issue in the appropriate channel is recommended, allowing community members to pick it up. + - There is a need to ensure community contributions are encouraged without overburdening the core team. + +- **Engaging the Community:** + - Tyler emphasized the importance of community contributions to manage the workload. + - If core team members are too busy, they should still ensure issues are created for community tracking. + - Tyler acknowledged Hero's proactive contributions and encouraged others to follow suit. + - Scott agreed but expressed slight concern over issues potentially falling through the cracks if neither the core team nor the community takes immediate action. + +- **Next Steps:** + - Tyler proposed discussing this further in the working group for the website and documentation meeting tomorrow. + - Emphasized the importance of creating issues for tracking any undocumented discussions or updates in the Insiders chat. +**Closing Remarks:** +- Tyler thanked everyone for their time and contributions, emphasizing the importance of efficient collaboration between the core team and the community. + +## Action Items +- Tyler Wright to add the restructure of the meeting format to the next meeting's agenda. +- Tyler to follow up on creating a standardized set of questions for insiders to use when handling partnership requests. +- Damir Simpovic and Rodri to monitor Discord for partnership requests and apply the filtering mechanism by asking follow-up questions. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to six support biweekly the support special interest group goes over. any issues that are in the support repo sometimes in the console repo triage is any issues that are awaiting triage and then the second agenda item is to talk to members of vanguards insiders and other members of the community that are active in Discord and other channels to see how support is generally going to determine if there's anything that needs to get changed in terms of documentation or any themes anybody sees across different support channels I will add an agenda item just about again the restructure of this meeting as we move forward, but I'll save that for the end. + +Tyler Wright: We'll start off by handing over to Scott and Scott will go through any issues that may be awaiting triage. And then again if anybody wants to talk about any issues, feel free to jump in after Scott has done triashing issues. So Scott, I'll kick it over to you. + +Scott Carruthers: All right, so just start is everyone able to hear my audio? I feel I can get in some network degradation is My coming through Okay, I'm gonna thumbs up. + +Tyler Wright: Yes. + +Andrey Arapov: long and clear + +Scott Carruthers: Okay, so the next step is let's see if I Share my screen without any degradation. + +Scott Carruthers: Okay, is everyone able to see my screen? + +Tyler Wright: Yes. + +Scott Carruthers: Okay, so for the purpose of triage issues, this should be very quick today. So as everyone is aware that open issues are created on the Akash Network support repository, and we usually go through an exercise of just going through. items that are away in triage and of course afterwards we can also take any questions on any other issues that are not covered, but currently we only have a single Issue, that's a waiting triage. So I'm going to go into this. Andy, Come across this issue. Previously, have you read through this or is this the first time that you're seeing this issue? + +Andrey Arapov: Let's give some foregone. I think I have never seen this before. + +Scott Carruthers: Yeah, I haven't seen this until I was just some prep for this meeting. I was wondering if maybe initially and I don't know. I don't want to put you on the spot of having to read through this in real time, but Luna opened up a kubernetes concern for providers and spawning. Too many processes within a container and affecting the host and possibly crashing the host. So whether this is a Terraria or not, obviously we could do some testing it. Maybe you can have some initial thoughts. But I was wondering if we could maybe initially take this out of waiting tree out. I'll send it as a P2 and assign to yourself for initial review. + +Scott Carruthers: Yeah. + +Scott Carruthers: Yeah. + +Scott Carruthers: Yeah. + +Scott Carruthers: Yeah I agree with everything that you just said,… + +Andrey Arapov: Yeah, yeah,… + +Scott Carruthers: I doubt based on our limits. + +Andrey Arapov: definitely I can review… + +Scott Carruthers: This is actually a concern. + +Andrey Arapov: but briefly I just explained through it while we were talking. + +Scott Carruthers: But yeah, if we want to go through some testing and… + +Andrey Arapov: So basically it's like,… + +Scott Carruthers: then maybe we can quickly come in and… + +Andrey Arapov: if you deploy some script that like a pork cell or… + +Scott Carruthers: close of the Great. + +Andrey Arapov: something some bump plots they are limited by the amount of memory they are being limited by so basically they like memory it's not only constraints… + +Scott Carruthers: And with that as I said, that was the only thing awaiting triage. So definitely. + +Andrey Arapov: if you neither the only is a process space so that kind of thing we can definitely test… + +Scott Carruthers: Pepito open up the floor and any of the issues that we said that was the only one that we needed to. + +Andrey Arapov: but by default. there I don't remember the number on top of my head,… + +Scott Carruthers: Make assignment and do proper labeling but more than happy to discuss any of the other open issues as well. + +Andrey Arapov: but there is some limited parameter for that so we can just basically run some tests. + +Scott Carruthers: Is there anyone in the audience that would like to discuss any other issues? + +Andrey Arapov: I can count on my provider different assignment for me things. + +Scott Carruthers: that was quick and easy if there's no other questions and that's all we have today. + +Tyler Wright: Thank you Cool, continuing to move along with the agenda. I did want to see could we do have some? Folks that are fairly active in Discord here have there been any themes that anybody wants to call out in Discord or is there any behavior and to score that anybody thinks might be worth sharing related to support here on this call? + +00:05:00 + +Tyler Wright: I'll go ahead damir first and then rodri after. + +Damir Simpovic: so the only thing It's actually like to. mention is there's a lot of completely unknown brand new accounts on Discord asking directly to talk to somebody about my partnership and then there's a number of people specifically. Okay, I don't want to bring up names. It doesn't matter. But they immediately point to Adam or to I don't know you Tyler or somebody else from the core Team without actually even knowing who this person is what they want, brand new account. I mean If you guys are cool with it, I'm cool too. But I think it's a waste of people should really not tag. + +Damir Simpovic: our members of the core team just because somebody is asking, there should be some kind of + +Damir Simpovic: let's say a filter. Yeah. Just yeah my opinion. + +Tyler Wright: I would just chime in before we head over to rodri. I would completely agree with that. + +Tyler Wright: In many cases when I get tagged in something or I see somebody from the core team has been tagged in something and they haven't responded yet because probably there's no been filter process. What I try to do is I try to ask that person in that public Channel what exactly they're looking for that is a filtering mechanism that again people will identify themselves or not and just disappear, but to your point and this is something that maybe we should talk about in the inside or office hours and just in general, I would ask that anybody that sees those kinds of conversations happening instead of again adding specific members of the core team, especially members that are not even online right now, but instead ask them because again Akash network is open source, what they're looking to do with the Akash Network and then from there, those responses can help dictate what next steps may be. so to me, I think you're dead on that and then again, that's something that + +Tyler Wright: If I forget please remind me to bring up in the proper channels moving forward. + +Tyler Wright: Go ahead rodri. + +Rodri R: Yeah, thanks a mirror. Totally agree with him. And with you I've seen those two and I wasn't sure how to handle those either but recently all the music don't want to point any names. But yeah, some people just attack work team. And filter would be great. And besides that also for the last two weeks, there's been these new kinds of bots that they start like, they're all so new accounts and they started conversation between each other. And then they share links which obviously or most likely are leading to scam websites. Not sure how we can get rid of those because they just start a compass conversation between them. + +Tyler Wright: Go ahead, damir. + +00:10:00 + +Rodri R: Perfectly, I'll do that. + +Tyler Wright: Is there anything else that anybody is seeing? Inside Discord or other channels that might be worth sharing go ahead Scott. + +Scott Carruthers: and maybe I missed possible suggestion here, but regarding the overall point of people being integrated interested in integrating with Akash or forming a partnership with so I like the idea of + +Scott Carruthers: filtering out people that are tagging the core team as well, I guess and this is the part that maybe I miss what are we suggesting as a solution to this though is so Discord is If there's a partner in the ecosystem out there that is internet interested in working with Akash a partnership or integration. Discord is probably most likely they're easiest way to initially get in touch with us. So What is the solution and so even if we disallowed them tagging the core team initially and then we allowed insiders to review it. I would think it would end up in the same place. the Insiders would probably have to reach out to Tyler or anneal and ask if this is a partnership that we're interested in so I've just wondering what the solution is here. So the only thing I can think of is we create a partners. + +Scott Carruthers: I don't know what it would be called because obviously we want existing Partners to end up in this channel, but it like new partners or Integrations Channel and then when someone tries to tag the core team we direct them to that channel and then we just release our controlling it all and then one channel, but yeah overall obviously love the idea of disallowing they tagging of core team members, but how do we solve this and allow people that are interested in new Partnerships and Integrations initiate that contact + +Tyler Wright: So my thought process wasn't like actually doing a setting inside Discord that would not allow them to do it, but the thought process was. Up training insiders and other members of the community that maybe don't know what to do right now and give them in Specific Instructions to follow-up questions to that person that said that's asking for the partnership. So instead of just saying instead of Company XYZ coming in Discord hey, I want to partner with Akash and somebody just tagging. Myself a meal or Adam that's the person you need to talk to. + +Tyler Wright: That person that sees it that is actively as active and Discord says what are you looking to do? And if they say I'm looking to integrate, Akash into our company or hey, I'm looking to do a marketing partnership. Then at least that follow-up will allow me to better direct the conversation. I'm still going to have to be speaking for myself. I'm still gonna have to be Hands-On and Discord to read many of these conversations, but there's initial step of just and many times people just blindly say hey, it's mostly a marketing partnership. I want to It's all right, cool. What's the partnership? I don't know. We'll figure out later. But let's start with the Tweet. We can immediately filter those things out, that was the idea. + +Scott Carruthers: All Yeah, yeah. So yeah, the solution that we're suggesting is coming up with a can list of questions so that when you review a Tyler a nail tester review it that one step had a okay. Yeah, that makes sense. + +Tyler Wright: Yeah. + +Tyler Wright: Go ahead rodri. + +Rodri R: Yeah agree with you all what I usually try to do with those is Tyler says ask them about what they want to partner with. But then I'm 60 to 70 percent of people who are asking for a partnership. at least in my Opinion they just looking to do. this listing akt and some decks some other place. And then I just don't Point them out. But if it's a legit company then I'll take someone but yeah. + +Tyler Wright: yeah, I would just Go ahead, damir. + +Damir Simpovic: What I was thinking. Okay, sorry. when I was why I'm pointing in out because people immediately jump, they don't want to put any effort into even introducing themselves. So these are the ones that I'm already on the verge of banning them. I mean immediately when I see, I don't even want to ask when they don't even take the effort to say, I am decent that and we are doing this and that and you would really be nice if we could talk to somebody, if they don't even take that amount of effort that requires just a bit of copy and pasting. + +00:15:00 + +Damir Simpovic: But just immediately jump to who could I talk to from the management about the partnership for instance and that's their first message, ever they just joined. And then there's a number of people that immediately respond to messages like that. ging Adam tagging Tyler tagging anneal tagging Scott's, I mean, it could be an actual legitimate request. + +Damir Simpovic: But 99% of the time those messages are just either scams or waste of time or asking for money or whatever. So what I was thinking was just kind of a higher archetical approach to this a filter. Okay, please introduce yourself, please If you have a request or you want to get in touch with somebody from the core team, that's fine. Just please, introduce your project. Make it so that we don't actually need to so that it doesn't immediately to I don't know. whoever + +Damir Simpovic: so that there's a little bit of effort requires, to actually reach somebody at least some amount of effort that Tells me for instance that this person. is not after just a quick Buck or something, that's + +Tyler Wright: No, I agree with you wholeheartedly. And again Akash is open source. So while a member of the core team is maybe just working in and it's well positioned to provide an answer this is a entire Akash Community that's making these decisions, someone like many cases special with the dexes. We try to point those people to Sig economics and starting conversation, right because they're not just gonna be like, hey, who do we talk to and a member of overclock is going to make a decision? Yes or no. so I agree with the mere wholeheartedly and we'll talk about this more again an appropriate meetings, but I think it's a good thing to call out and the good thing that I know we're seeing a lot more of which is again speaks to the kind of project akashes, but also speaks to some of my general frustration with the space where people just think + +Tyler Wright: tweeting something is a partnership and I think our expectation here as a group of Builders, actually trying to build something real is far beyond that and we need to filter those people out. So A great point damir and again, we'll follow up on that as an action item. Go ahead rodri. + +Tyler Wright: Absolutely. + +Tyler Wright: All Real quick. I'll follow up with that later. + +Tyler Wright: I did want to see maybe this is not something we could take offline, but I did want to see if I know there's been an uptick in potential scammers. I did want to see if you all saw more providers coming into the ecosystem or more people and deployments channel more people looking to get involved. I seen a number of more contributions as of the last couple of months and people looking to contribute to the cash project, but I wanted to see if you all seen an uptick downtick or any sort of + +00:20:00 + +Tyler Wright: Any sort of understanding of what's been happening in terms of folks deploying or providers and have you seen more than in months pass or less than a month's past. But again, we can feel free to take that offline. If you don't have an accurate figure, but that's something I would ask that folks here continue to monitor as we continue to move forward to see if documentation is continuing to improve and so people have less questions because they're getting everything that they need or people are asking different kinds of questions that maybe again should Be answered elsewhere. And I guess that is a good segue into the last agenda item that I was going to talk about it again, if anybody has any open discussion items related to support that they want to talk about here today. Feel free, but one thing that + +Tyler Wright: That this is kind of alpha that want to talk about in terms of the structure of this group. I know that originally this was a monthly meeting and it changed to a biweekly meeting as we were looking to get more folks to see again the triage process and then hopefully get involved in contributing to the core code base. Obviously anybody can contribute to the core code base and the repos are open, but we have found over time that there's just been a learning curve with people getting up to date and helping to solve some of these support issues in the support repo. + +Tyler Wright: There has been an idea basically to have a monthly again. This is just a preliminary idea that's been floated. a monthly like a Sig engineering core meeting which would be a combination of support and chain, where conversation would happen about, blockchain next steps, there's a cosmos SDK upgrade to 47 or 50. There's a lot of work that happens there. So again that will be talked about in addition to issues and it'll be a chance for any member of the community to remember to meet with members of the core engineering team and talk about anything and that would happen on a monthly basis and that would mean that this six support me meeting would not have to meet as frequently and the goal of this meeting would be to focus on support in the community how insiders and vanguards are doing that kind of stuff. + +Tyler Wright: I may actually be thinking about combining the support and the documentation meeting because again + +Tyler Wright: Much of what goes on with the documentation has been turned into the working group for the website and documentation. because the docs are under the website folks that are contributing to the documentation we'll meet biweekly to talk about anything related to docs working group for the Akash website and documentation. And then there's a separate special interest group around documentation as looking to meet less frequently and that's just to check in on all things going on with the working group all things related to documentation and seeing if we need to meet more frequently. My thought process was to combine six support and Sig documentation because they are very similar and a lot of things that we see potentially in support might have an effect on documentation. But the idea is that these meetings will meet less frequently. We hope that more insiders and vanguards and members of community can come and talk about what's going on and Discord telegram other channels as well. As things that maybe they've seen from the + +Tyler Wright: in terms of updates needed to documentation pain points frequently asked questions Etc, but it would meet less frequently and then + +Tyler Wright: There'd be again another meeting. That would be more engineering focused that would bring in people that of They're asking more technical questions. So I just wanted to float that idea to this group as we continue to refine and fine-tune, these six and working groups. The goal is that there's as many participants and as much Lively conversation when we do I know some of these meetings where we might be meeting very frequently, but again, very people are very busy. So there might be less active participation on a regular basis. We just want to make sure we're maximizing everyone's time. So I just wanted to float that to the community. I'm of the belief that there's still a great deal of importance in triaging issues transparently so that people from the community can ask questions people could look to get involved because again, there is a goal over time that there go developers out there that will want to contribute whether it's teams or individual. + +00:25:00 + +Tyler Wright: companies that say I really believe in It is in our best interest to help with the core product and they look to get involved in some of these conversations. But again to this point we found that number of people have come to these meetings. Try to get involved with support issues, but then whether or not they read the engineering documentation, they're is just learning curve. That folks. have had an issues with especially as they make a living doing other things with a nine to five job so Just want to see if there was any initial thoughts concerns about. This idea again. I'll float it again in Discord, but I just want to see if there's any thing that anybody want to talk about live in terms of objections the grill thoughts questions Etc. + +Tyler Wright: I see a bunch of thumbs up. So it sounds like everyone's kind of on the same page. And again, this is not yet determined and finalized but it will continue out to continue to talk to members of the community and then also members of engineering team and we'll take next steps from there. + +Damir Simpovic: I have a sorry to steal your show. Andrey there's a number of providers that can be signed. + +Tyler Wright: Cool that there's nothing else then again. I'll remind folks that there's Sig providers meeting happening in 29 minutes damir's got some stuff that I know he wants to talk about. + +Tyler Wright: + +Damir Simpovic: And tagging you. But you probably missed it. + +Tyler Wright: We'll have some follow-up discussions related to you… + +Damir Simpovic: So just that's a reminder. + +Tyler Wright: some discussion happened Sig clients yesterday around console 2.0 and… + +Damir Simpovic: That's all. + +Tyler Wright: what that looks like for the prior team and I know Scott has been refining the provider build upgrade paths and there's been some talks internally and… + +Damir Simpovic: Should I like the Emmy or? + +Tyler Wright: again with members of community about just some finalized testing that needs to get done as Next Step. So we'll talk about that during sick providers and then tomorrow again, there's a working group for the Akash website as well as documentation. So if anybody wants to contribute to the website contribute to documentation, feel free to join that working group tomorrow, and then they're also as a steering committee which will meet again at tomorrow afternoon. Go ahead Scott. + +Scott Carruthers: Yeah, just sorry since we have some time Tower. I know that we've talked about this before but I wonder… + +Tyler Wright: So a couple meetings to + +Scott Carruthers: if it is useful for the people on this call to have a clear understanding about this as well this so it documentation. + +Tyler Wright: For but much appreciate the conversation today much appreciate everyone's time. And again, we'll follow up with some of these conversations online. + +Scott Carruthers: Kind of focus so much support related. So again people I candy and… + +Tyler Wright: all thank you Scott. Go ahead damir. + +Scott Carruthers: Damir, and in rodri and probably others on the call that are involved in documentation. + +Tyler Wright: You're good. + +Scott Carruthers: I know that we talked about this before and you also just said that maybe some of this is influx of as well. Maybe there would be an idea of combining the six support and Sig documentation meeting. So I also understand that again, it could be influx, but I'm still not sure that I'm clear. And so I want to make sure that everyone else on the call is clear with the idea of getting rid of the Sig documentation. Biweekly or monthly meeting. However, frequently that met in a lot of those discussions are under Sig website, which makes sense that documentation is now on the Akash website, but they're Seemingly very different topics of so a lot of the conversation and the website Sigma made in. + +Scott Carruthers: a majority of the people on this call. Don't join that because a lot of it is design discussion and other things with the actual functioning of the website. and it sounds like right now because documentation is under the website where possibly any documentation conversation of Interest would happen in that Sig. So I guess I'm still not clear and maybe for the other members of the call is people that are involved in documentation at this point should be joining the Sig website or only On request. So again, my overall concern is that probably a majority of that meeting isn't really relevant to us, but If a documentation topic comes up then obviously we need representation or we should be involved. So I'm just want to make sure that everyone is clear on how to navigate that based on the current meeting structures. + +00:30:00 + +Tyler Wright: Yeah, so it is very much again in flux. What we found is there's been a number of community contributions from folks that are looking to do both, contribute to documentation and the website from a hierarchical standpoint. the idea is before any documentation items get merged. there is a check from either Andrey or Scott and so that can be done async if we start to find that there's a number of Actual discussions that need to happen then I will ask Scott Andre to join the meeting and we can talk about as an agenda item as we prepare, but that's not something that I would require. + +Tyler Wright: either of you to join I would ask an obviously anybody from the community is welcome to join but + +Tyler Wright: Before there is a hierarchy. Between members of that working group and piyush about how documentation PRS are merged and that involves again in most cases a member of Scott either you are Andre, but as we move forward we can look to fine-tune the idea. The goal is that again members of the core team who are very busy don't have to feel like they have to join three or four sigs and working groups. But again, there's + +Tyler Wright: So much going on and so much that the core team is involved in that. We just have to figure it out as we go along I guess in the short term. + +Scott Carruthers: Yeah, definitely fine figuring out as we go along and again understand that some of its influx so I think Maybe the number one thing I was looking for there is and you've set this in the past. I'm just making sure that everyone is clear you want to really expect. people Andy and myself, who are Responsible for documentation specifically to join the Sig website call and would probably only join it if there's a request interesting item that's going to be discussing that session so we'll join on request. But again, I just want to make sure that there wasn't any expectation that we're going to start joining the sick website meeting and it doesn't sound like there is that expectation, so + +Tyler Wright: No expectation. And again, we'll make sure that an agenda is set out for every meeting and there's anything specific that might call upon you then I'll coordinate with you all to make sure that you're available and then make sure that your time is utilized. and as an example, if We have a number of items to cover. I'll make sure that documentation item is on the earlier side the agenda so that you're not helping to spend time working on things that maybe are less interest to you. I'll make it clear prior to the meeting. + +Scott Carruthers: Yeah, sounds good. And I want to turn this into a documentation made in but just another item that I think possibly could be of interest as entire I'm sure you have some thoughts on this and I don't think it's anything. Like severe that I think we're handling this all very well reasonably. at this point but Sometimes there's things that come up in documentation like this morning. There was a Insider conversation about provider Audits and if we have that process docume So the thing I think is interesting in here as it's just by my nature. I instantly think I'm just gonna go into documentation and make that update. But if we should be relying more on the + +Scott Carruthers: Community like what that's going to look like over time. Sometimes it just happens naturally and somebody will raise their hand within the Discord discussion saying yeah, I'll take that on but short of that. Yeah, how do we not navigate that should we? Lean towards in that circumstance if I want to handle it. I'll just handle it myself or is a way for the community become more involved in documentation. We shouldn't lean that way and if we don't lean that way how to win something comes up in Discord. So obviously create an issue I suppose. But yeah, I'm just wondering how we navigate that going forward and making sure that items of Interest are handled without the core team necessary paneling them themselves. + +00:35:00 + +Tyler Wright: I mean, yes, my two cents on this is if a member of the core team has the time and the desire knock it out, and what and we could just keep it moving. Other than that, I would ask that and we'll talk about more about this in entire calls and other calls is have those people take the appropriate measures to make an issues and then I know that there's members of the community. There's one on this call hero that does a great job of identifying issues and solving those issues as quickly as possible. So there's a number of people that are waiting in the wings to help contribute, but I would say in order of operation standpoint. I think the idea is + +Tyler Wright: Obviously, there's so much going on with the Akash Network that there needs to be Community contributions and we need to push people to contributing more but there's already plenty of places for people to contribute. So I don't want that to be a deterrent for you maybe I shouldn't do this because somebody from the community should do this, but if it makes sense and it's efficient for you to do it, then I would say do it. Otherwise again, you can just stay heads down and we can make sure that an issues created by somebody else and then it gets solved. There's plenty to get solved so I would say short answer. If you want to do it, if you don't and you have the time to make an issue and we'll go from there, but don't feel like you're taking contributions away from somebody else because again, there's plenty for folks to get involved in. + +Scott Carruthers: Yeah, sounds good. I don't think that's any great concern. I have a little bit of a concern in that circumstance today in the Insiders. So if I am busy Doing devworker or other things. And I don't handle it myself and I don't create an issue and then nobody opens an issue for it. So, like I said, I don't bring this up as a severe concern, but I think there's that possibility that exists. + +Tyler Wright: Yeah. + +Tyler Wright: No, I think it's a good point in something. We can continue to monitor. We'll talk about that in the working group for the website and docs tomorrow and then also on the Insiders call. + +Scott Carruthers: Yeah, and it could just be as simple as the people that were in the discussion this morning our default response that is please open an issue for tracking. + +Tyler Wright: Yes, exactly. + +Scott Carruthers: Okay, sounds good. + +Tyler Wright: Is there anything else that anybody wants to talk about on the support front? + +Tyler Wright: If not then all I appreciate conversation again. I'll follow up with next steps in terms of the structure of these meetings be a Discord but much appreciate the Hope to see many of you and Sig providers. Thank you all very much. + +Andrey Arapov: Thank you. everyone + +Scott Carruthers: Thanks. + +Rodri R: Thank you. + +oo o: lived on a prosp + +Meeting ended after 00:38:50 👋 + From 761dddcc5273a2289697474145e1309233b60e5c Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 12 Jul 2024 20:50:57 +0000 Subject: [PATCH 099/138] Create meeting notes for sig client #15 (#627) * Create meeting m=notes for sig client #15 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 015-2024-04-24.md add recording link and transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-clients/meetings/015-2024-04-24.md | 298 +++++++++++++++++++++++++ 1 file changed, 298 insertions(+) create mode 100644 sig-clients/meetings/015-2024-04-24.md diff --git a/sig-clients/meetings/015-2024-04-24.md b/sig-clients/meetings/015-2024-04-24.md new file mode 100644 index 00000000..e15e229e --- /dev/null +++ b/sig-clients/meetings/015-2024-04-24.md @@ -0,0 +1,298 @@ +# Akash Network - Clients Special Interest Group (SIG) - Meeting #15 + +## Agenda +1. Welcome and Introduction +2. Updates on Akash Clients and Projects +3. Discussion on Meeting Cadence +4. Updates on Terraform Open Sourcing +5. Cloudmos Updates +6. Human HQ Team's Automated Pipeline Project +7. Demo by Chaitanya Rai +8. Open Floor for Questions and Comments +9. Overview of Console 2.0 Plans by Anil Murty + + +## Meeting Details +- Date: Wednesday, April 24, 2024 +- Time: 08:30 AM PT (Pacific Time) +- [Recording](https://j3gehsinfdsmtozvozl7ne3dv2w255mnewbmwe3unblpiayao3ya.arweave.net/TsxDyQ0o5Mm7NXZX9pNjrq2u9Y0lgssTdGhW9AMAdvA) +- [Transcript](#transcript) + +## Participants +- Anil Murty +- Bold Panther +- Chaitanya Rai +- envy | Neta DAO +- Nicolas +- Maxime Beauchamp +- Scott Carruthers +- Tyler Wright + +## Meetings notes + +- **Tyler Wright:** + - Welcomed everyone to the SIG Clients monthly meeting for April 2024. + - Mentioned the group focuses on anything related to Akash clients or those building solutions on top of Akash. + - Proposed changing the meeting cadence from monthly to every two months to improve attendance and participation. + - Requested feedback on the proposed change in meeting cadence. + - Highlighted the ongoing coordination with Luna to open source Terraform, which is expected to be completed soon. + - Mentioned the efforts to push teams into public channels for better visibility and communication. + - Discussed the Human HQ team's work on an automated pipeline project in collaboration with Neta DAO, Cloudmos, and Overclock Labs. + +- **Maxime Beauchamp:** + - Provided updates on Cloudmos, including the refactor and rebrand from Cloudmos to Console. + - Mentioned the work on improving features based on new chain additions, such as storage classes for AI workloads and private registry support. + - Discussed improvements in TypeScript type generation in the Akash API to streamline JavaScript client operations. + - Announced the onboarding of a new team member, Yarrow. + +- **Bold Panther:** + - Updated on the progress of the Human HQ team's automated pipeline project. + - Mentioned meetings with the Overclock Labs team and Cloudmos team to define the project scope. + - Described the implementation of the base container to handle automated deployments and integration with GitHub webhooks. + - Offered to provide a demo of the project's current progress and requested feedback and participation from other teams. + +- **Chaitanya Rai:** + - Demonstrated the automated pipeline project by showing the SDL file configuration. + - Explained how the SDL file includes image, environment variables, repository, port number, node version, build command, and build directory. + - Demonstrated the process of cloning a repository, building it on the provider's machine, and deploying the application. + - Showed a diagram explaining the workflow: cloning the repo, installing dependencies, running the build command, transferring build artifacts, and serving the application. + - Emphasized the use of a lightweight Alpine Linux container image to minimize overhead and costs. + +- **Anil Murty:** + - Commented on the code commits related to the core repositories and network upgrade scheduled for next week, enabling data people inside services. + - Mentioned a draft document on workflow improvements and offered to share it with the team for feedback and collaboration. + - Provided a quick overview of plans for Console 2.0, which will start once the rebrand and support for private registries are completed. + - Encouraged the Human HQ team to continue developing and integrating their work with Cloudmos and Akash Console. + +**Discussion on Console 2.0 Plans:** + +- **Anil Murty:** + - Presented a draft document on the Console 2.0 project, highlighting several key goals: + - Eliminate the need for interacting with crypto or obtaining AKT. + - Allow users to try Akash services without spending money, similar to free trials offered by public clouds. + - Simplify provider selection by offering instance-based selections. + - Improve notifications for lease closures, low funds, and billing. + - Enhance log and event management by saving historical logs. + - Enable SSH access to VM instances similar to public cloud services, with reliable connection and command line access. + - Provide pre-built Linux images for common distributions and versions, allowing easy customization. + - Automate HTTPS setup and custom domain configuration. + - Explained the proposed workflow, including login options via Kepler Wallet or GitHub, and the creation of custodial wallets for users. + - Mentioned an existing solution involving a Telegram bot for notifications and expressed interest in exploring its integration. + +- **Bold Panther:** + - Offered to share information on the Telegram bot project for notifications. + +- **Tyler Wright:** + - Thanked Anil for the overview and expressed excitement for the upcoming Console 2.0 features. + - Encouraged continued tracking and discussion of these features as they are developed. +### Clossing Remarks +- **Tyler Wright:** + - Expressed gratitude for the updates from Max, Anil, and the Human HQ team. + - Confirmed work with Luna next week to finalize the open sourcing of Terraform, with an announcement to follow. + - Noted Human HQ team will add more information to their discussion, and he will supplement it with the meeting video. + - Reminded everyone about the ongoing Akashathon hackathon, ending on May 17th with over $200,000 in prizes. + - Shared the link to the hackathon for those interested in participating. + - Announced the rescheduling of the steering committee meeting to May 2nd and the planned network upgrade also set for May 2nd, pending a vote. + - Invited everyone to stay engaged via public roadmaps and Discord for any questions or further involvement. + +## Action Items +1. **Tyler Wright:** + - Post the question regarding changing the meeting cadence to the SIG Clients Discord Channel. + - Collect and review feedback from the Discord Channel on the proposed cadence change. + - Announce the final decision on the meeting cadence based on the collected feedback. + - Coordinate with Luna and Andrey to ensure the open sourcing of Terraform is completed before the next SIG Clients meeting. + +2. **Group:** + - Provide updates and announcements in the SIG Clients Discord Channel if unable to attend the bi-monthly meetings. + - Participate in the discussion on the proposed change of meeting cadence in the Discord Channel. + - Report any Cloudmos-related issues in the Cloudmos repo issues area or the Cloudmos channel in Discord. + +3. **Maxime Beauchamp:** + - Continue to provide updates on Cloudmos/Console development and new features in the relevant public channels and meetings. + +4. **Bold Panther:** + - Share a detailed update and next steps for the automated pipeline project in the SIG Clients discussion and Discord Channel. + - Provide a demo of the project's progress and invite feedback and participation from other teams. + - Share information on the Telegram bot project for notifications. + +5. **Chaitanya Rai:** + - Share the demo details and workflow diagram in the SIG Clients discussion and Discord Channel for further feedback and collaboration. + +6. **Anil Murty:** + - Share the draft document on workflow improvements in the communication channel for feedback and collaboration. + - Provide updates on the network upgrade and its implications for the project in the next meeting. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to say clients monthly meeting for April 2024. During the special interest group for clients. The group goes over anything related to Akash clients or those that are Building Solutions on top inside the sick clients repo you can track various teams that are working on again various initiative building on top of Akash. Usually we get updates from teams that join this call and we ask all other teams to leave a message in sick clients. + +Tyler Wright: I know that folks have been very busy and It has been difficult to get folks to join these meetings. I know there's teams building all over the world. And so again a number of people have historically said, yeah, I can make it and then have not been able to make it for various reasons. The plan potentially for this sig is to maybe change a Cadence of it instead of it being every month. There is some discussion and I want to pose it to this group to change it to every two months similarly to Sig analytics. Hopefully with slightly less than a Cadence it'll drive people to take the time every two months to get updates and then we can continue to attract. again other updates via a announcements from those various teams or again updates inside of Discord before we move on with the agenda. Does anybody have any issue with? + +Tyler Wright: And I'll post this question also in the state clients Discord Channel, but does anyone have any issue at this time with lessening the Cadence for this meeting? + +Tyler Wright: I'll take that silence is nobody has any issue. One thing that we talked about last meeting that is still not done. I'm trying to coordinate with Luna is the open sourcing of terraform. There was a discussion that Luna brought forth. He did receive some community pool funding for + +Tyler Wright: Terraform provider and again, I believe his work is completing. He's going to open source that and add that to the Akash Network organization. I will add it as an action item and I work with Andre offline to make sure this is done before the next state clients' meeting. And then again, we'll make an announcement in Sid clients and in Discord in general just where the new app is and how people can use it. So that's one thing that again Luna and I have talked about offline but need to get over the finish line. + +Tyler Wright: Again, there are a number of teams that I try to push into public channels, but I know that myself Anil and others have been talking to various teams that are building clients that building their own Solutions on top of a cost. + +Tyler Wright: cool one person that we usually get update from is from Max who just joined the call. you can also track updates many of the updates happening on the cloud most public road map inside the product and Engineering roadmap again any issues that are in the cloud both repo that are public facing or our actively being worked on rather get added to this roadmap. I know that Max and the most team had been working diligently on the cloud most deploy refactor and Rebrand from voice Cloud most console. + +Tyler Wright: I'll give Max a little bit of time to give an update on all the work that they've already done. But again, I know that he has been working consistently to refactor a number of items that are available in Cloud most that will now be a part of console and part and as a part of that reason. Max don't feel like to go in detail because I know that you give an updates often and various other special interest group calls and as well as steering committee, but do you want to give a short update on some of the wins from cloud most of our last month? And what's next? + +Maxime Beauchamp: Yeah, we've been working on a lot of different issues that I mentioned in this board. So yeah, like you mentioned I've been working on the refactoring Rebrand. It's a very close to being done and So that's gonna be rolled out in the coming months. We are also improving in or adding features based on what is being added on the Chain. So the storage around class that is to support. + +00:05:00 + +Maxime Beauchamp: some AI workload that need to have this type of storage class. So we have also private registry. Support that is gonna come out soon. We're improving the typescript per above types generation in a cache API. So that will make it. better streamline for a Cassius or any clients just doing stuff with JavaScript. So yeah, that's the stuff going on and I think everything's going in the decent pace and we have the new team member that we onboarded yarrow you can see the board. + +Tyler Wright: Thank you Max. Again, if anybody has any Cloud most related issues as we're leading up into that transition, you can always drop them inside of the cloud most repo in the issues area as well as in the ecosystem Cloud most Channel inside a Discord the max it do a great job of being very responsive. + +Tyler Wright: Max one other thing we talked about the top of the call is and I'd much appreciate the time that you take there are a number of other teams, as you know that are building on top of Akash. They have an open invite and many of them are invited literally on the event to these meetings and between meetings tell me that they're going to come but when it comes time for the meeting for whatever reason or not able to join. There was discussion around changing the Cadence of the sick clients meeting to every two months. So maybe that with lots of vacations folks will be more driven to join that meeting and give updates every two months. just continue to update folks more regularly inside a Discord. Did you have any initial concern with changing the Cadence? + +Tyler Wright: If you do have concerns feel free to speak. Otherwise, you can just thumbs up or stay muted. + +Maxime Beauchamp: I think it's fine. I mean currently today other than how those clients who else is here to talk about clients. + +Tyler Wright: No, nobody. + +Maxime Beauchamp: So yeah, I guess that makes sense to move it to every two months. I'll see an issue there. + +Tyler Wright: Again, we'll still look to track updates and obviously the updates on the cloud on the side are reflected in this roadmap, but I'll still look to track updates from other teams and happen put them in a public place. If not, I'll start throwing them in a public place and protagon people to correct me. + +Tyler Wright: in addition. to those Cloud most efforts at the last declines meeting there was discussion around some work that the human HQ team wanted to do around again making easy for people to deploy and create an Implement to blind automated pipeline. I know the human HQ team has been working with the net of Dao team on this kind of work. + +Tyler Wright: Homemade HQ team was able to meet with the cloud most team as well as the overclock Labs core team and you can track the discussion on where progress has gone since those conversations. I know that members of the human HQ team are here today. if anybody wants to get involved since discussion, please get involved, but I do want to see if anyone from the human HQ team wants to talk about progress made since those meetings with the clouds and over with the clients clean on next steps here. + +00:10:00 + +Bold Panther: Yeah, so yeah, thank you for the interest. So I saw the last meeting the last six clients. We are made with the world clock lab screen as well as the Carlos team. So complete the scope that is defined in our proposal was to ask that I would have required some changes in the code base of console, but + +Bold Panther: To test out the plan that we have invented. So we have been guided into basically first implement the less Scott person of and he will be building and still Park and behind the scenes with the base container of we will be handling the guitar presentation that the Deploy on the cloud onto the cost. So the base continuous will have the capabilities of other handling obviously able to fetch the wheels like George using and automate the process of building onto the providers machine. + +Bold Panther: Yeah, I thank you so much for a great. Yeah, so obviously basically you can Bachelors about what all the JavaScript Frameworks and also ash as soon as the new pull requests or new push happens on to GitHub web books. We will figure the really deployments of respect or the guitars of this case to the pride and machine. so yeah, that's the plan and we have progressing good. So we were writing some test cases. So if anyone wants to see the demo that we have made I would love to presentation. + +Tyler Wright: Thank you Pierce if you're able to drop a note because you were speaking a little bit fast. I got 85% of it and I believe I got the gist but if you can drop a quick comment inside this discussion on next steps, that would be great. And then maybe even drop the demo in there too. Just so we're all aligned. + +Bold Panther: Yeah, so to conclude the things that I said, so the movement is we were testing some test cases which can basically fetch all retails about the guitarists that has been provided by the users to be deployed on Akash and our basically script all the base container industrial power will be able to get what JavaScript framework sorry post is using and it can deploy and grown and run the scripts directly onto the provider machines. And as soon as the new push happens on the guitar proposes, this logic is being reaching basically redeployed applications onto the provider machines being push to the main branch. So we also take it some good quality demo, so Of Japanese to share the skin and presentation. + +Chaitanya Rai: Yeah, thank you for handing it over. So I'll be showing you guys the demo. So I'm sharing my screen. + +Chaitanya Rai: Yeah, I hope I'm Audible and my screen is visible. + +Tyler Wright: You are Audible and your screen is coming up right now. Your screen is visible. + +Chaitanya Rai: Thank you for confirming so we have created an SGL file which has the image. So you just go in here upload this sdl file. And so this is how it looks so it has this image and in the environment variables you can specify the repository that you want to deploy the port number the node version as well. Some people might be using different node version than our base image and then a build command and then a bill directory but these three options are not necessary. You can even go ahead and omit them. If you don't need them. We have the most commonly used things as the default settings for them. So the idea is just we can get this Rippling from the environment variables and we do the container and it will just deploy + +Chaitanya Rai: So it will keep on rechecking whether some changes have been made if the changes have been made it is going to pull them and show the new changes show the new version. So I'll go ahead and quickly show the demo. + +Chaitanya Rai: So currently our idea is just making this sdl file as good as possible and as good in handling as possible and I'm using only a single one to basically be enough for all the JavaScript Frameworks out there Because we're giving them so many options of what node version to use if they have a different build directory or if they have a different build command, so by using this we will be able to mimic a render kind of experience on a cash. + +00:15:00 + +Chaitanya Rai: Yeah, so one started container service one. We can go ahead in the logs Yeah, so you can see that it is cloning. Okay, so it was a relatively small Ripple so it's done so it clone the o. It build it here on the providers machine only and then it ran the serve package that we have in here. And if I go in here and I do this you'll be able to see the library. Yeah, so that is kind of the vision that we have and I would quickly also like to show you the quick diagram that I made for how this thing is working. So basically we have a GitH remote repo and we are using first and foremost is going to do a good clone using this shell script. So basically + +Chaitanya Rai: All we are doing is running this shell script inside this Docker container. And as soon as the change is found it pulls the change The needed nbm packages runs the build command transfer build artifacts into the directory to be served and we are serving using G server HTT server, whatever is best suited and the image is Alpine is the container image the node images and Alpine version of Linux, which is very light. So we don't think that is going to create that much extra overhead over the hardware of the provider and it will keep the cost as minimal and as minimal as possible and with all the functionalities So yeah, this was all. + +Bold Panther: ation + +Chaitanya Rai: Thank you. + +Tyler Wright: Thank you very much as much as you can share of that inside of the discussion would be great for folks and I'll drop in the link to this client meeting. So folks can also have access to live demo. Does anyone here have any questions or initial thoughts about the demo just put forth by whom an HQ team go ahead and deal. + +Anil Murty: Yeah, chaitanya and MPS. That's Very cool. I guess just one or maybe two comments one is if you follow Some of the code commits on the core repositories you may have noticed that there was a code Commitment Report Industries So I just pasted the link to that as well. that's in the code, but it requires us to do the network upgrade which is scheduled for next week. So once that is done, then you'll be able to specify the credentials for the data people inside the services and it'll be awesome for you guys to test that out once it's in the code along with your cloning sdl + +Bold Panther: Yeah, I think that looks cool and it can be great. step forward + +Anil Murty: Yeah, and then the other thing I was going to mention was I know last time when we spoke about this after you posted the discussion we talked about making sure that any workflow that you build subsequent to this. So this is obviously just a template but they eventually goes I have a workflow in console itself. one of the actions on us was to discuss with you the workflow that we are thinking about in terms of other things that we want to solve. I have a draft document on that I can share with you on the channel that you have communication. and we can certainly take it from there. But if you want I can just provide a quick overview of that as well. + +Bold Panther: Yeah, yeah for sure. You can share I think this is the first question that we are developing and as we progress more I think that problem stream as well as a period team to build things tightly on the ground most or maybe and now gosh console and I think that would be cool like that. I use other signing into GitHub and justifying that application style to the cash without having to worry about right industry fights. So I think that can be a dedicated clone on cloud nodes or console. Which the data. + +Bold Panther: Atmos and us are together can Implement if and the version that we had everything is a success for all the JavaScript Frameworks. So we are still writing some of the test cases where it has the L handling capacities and also can detect what jobs can pay books are using and we were all six exploring your suggestions about build packs. how we can build a systems are directly to get actions build artifacts on YouTube actions and then use those artifacts directly to plan to the party emissions. So the exploring multiple waste so our proposal and I hope to push the proposal regarding this what we actually are related to the first versions pretty soon. + +00:20:00 + +Anil Murty: specifically if we have time, I'm happy to give a really quick update on what we're thinking in terms of the new experience for Various calling it console 2.0 which is something that we hope to start working on. Once the Rebrand and the support for secret money or support for private Registries is done. I'm happy to do that as well. + +Tyler Wright: Sorry Anil. Are you suggesting doing that right now during this call or doing it at a later time? Yes,… + +Anil Murty: right now if this thing + +Tyler Wright: is there any before we jump into? + +Tyler Wright: Just update from Anil. Is there any other thoughts on? the presentation from the human HQ team + +Tyler Wright: again If you all can just add to that discussion much appreciate all the efforts that you all are putting in and pushing this forward and really excited for you connecting with the net of Dao team coming up with the idea sharing it getting some feedback and continuing to fight soon. So appreciate you all. + +Tyler Wright: cool + +Bold Panther: Thank you. + +Anil Murty: Yeah, so this is understate this document. It's not complete at this point. It's still a draft and I've also drop this in the communication channel that we have with you guys. But our goal essentially with this console 2.0 is to solve a bunch of problems. We may not solve all of these in the very first go in the MVP version of this but ultimately the goal is to try to solve a bunch of problems the main problems. We have identified so far a kind of called out in this list here. Most of these should be pretty obvious. I think a lot of people have thought about these problems that are thinking about building clients. So, the first two are eliminating the need for interacting with crypto. basically obtaining it with the wallet or having to obtain akt the third one is be able to try the service or try a cash without having to spend any money. So, being able to basically get a free trial similar to what? + +Anil Murty: Public clouds to give you a hundred dollars or two hundred dollars of money that you can use to stand on AWS or gcp Etc. The fourth is not needing to select a bunch of providers from a list of providers if you don't want to so, offering people the concept of an instance if you will and just being able to Say I want to get one of these instances as opposed to saying here's a bunch of providers and pick your own. So that's kind of number four. notifications for when at least is closed or when you're running low and funds or if there's billing then when you get build here. + +Anil Murty: Dealing with logs and events better. So today if you have a bunch of logs and even said came out and then you release closed. There's no way for you to go inspect those later. So having some sort of historical saving of logs will probably go a long way because we hear from customers all the time that they have no idea what happened and why a certain thing closed and then the seventh one is probably the most relevant here, which is one of the biggest problems today is that customers that are coming from public clouds like AWS so gcp they're used to the mode of being able to just get a VM instance and get an SSH into that. We have instance and the expect to be able to do the same thing in And there's two challenges there one is while we do have that lease shell in console today. + +Anil Murty: The least Channel because of a bug that exists in core code base is not reliable every time the Provider Services restart, you lose a connection to the least yet. And then also in general developers want to be able to just SSH from their own command line. So right now the thinking is we can potentially solve this one of two ways or offer essentially both the ways. One is follow what the public clouds do which is Linux images for the most common Linux distros as well as versions. So if you go for example do gcp or AWS, you might find you wouldn't do sync OS Susie, maybe another the next favor and you will do NTS 22 or something and then one version older one version you are then that And you can pick those and give you a vanilla Linux image that you can then install anything. You want to? + +00:25:00 + +Anil Murty: so that's one option is to build refer these images and have them available that are user can select from and be able to have that instance file along with dropping Their public key so that we can load that on into the Container as well. And then the second one is what you guys are working towards which is building that custom image from the user's GitHub repository in case the user happens to be reactive or a JavaScript user and is informative with infrastructure. And then the last one here is once the services fun up then dealing with the issue of setting up https and a custom domain which today requires a lot of interactions outside of the core workflow. + +Anil Murty: a lot of understanding of other services typically configured in cloudflare and stuff like that. So those are kind of main problems. This probably other ones that will come up with as well. But the ultimate goal here is to be able to get from the GPA pricing page on our cash Network slash GPU. Use the clicks on that and then ultimately ends up with their own command line SSH into the running container instance. That is either a plane Linux instance or their own custom build application of Any questions so far on that? + +Anil Murty: but I think that you + +Bold Panther: in the directly email logins + +Anil Murty: Yeah, great question. So you jumped a little bit ahead in the dark. So basically the share the workflow that again this is not hundred percent second stone or final but this kind of the general thinking right now is we would have both of these options. So everything on the right side is what is supported already in consoles Nationals today. The one on the left is what we would have to implement. So you comes in and we give them the option of logging in with Kepler. Wallet or with GitHub And I didn't get up Then we would create a wallet on the user. We have essentially a custodial wallet and manage it for them and take it. Both options would be supportive. + +Bold Panther: and there is a fourth point where you said the lack of notifications. So if I remember in last it's on there was one participant who kind of solve this problem by creating a telegram board. which was kind of notifying anything what's happening with their deployments if they are running on low, if you on the fundings they can get a notification library on the telegram. So if I clearly remember there was a one project I was getting that on because they could notification itself and I think I can search about that and share with + +Anil Murty: Yeah, that'd be great. Would love to learn what they have and how we can potentially use that if we can. + +Bold Panther: Here it shows. + +Anil Murty: Yeah, I just want to give you kind of a preview of what we were thinking in terms of this. I'll share this document with you on the channel that we have established with you. + +Bold Panther: Yes, sure. + +Anil Murty: Thanks. + +Tyler Wright: Thank you very much Anil for walking us through that a little bit again. I'm sure a number of those items will get added to a pack and Engineering roadmap over time which continued track them and talk about them as I get bills, but very exciting things ahead for cloud. Most less console console 2.0. + +Tyler Wright: Is there anything else that anybody wants to discuss that hasn't been discussed already? + +Tyler Wright: again much appreciate the updates from Max from Anil from the human HQ team. I think we have a number of action items all around. I know that Luna is traveling right now going to work with Luna over next week to make sure to terraform is open source. And again announcement will come out there soon. Human HQ team will drop a comment in the discussion that they're created with some additional information. I'll add to that with again video from this Sid clients meeting. + +00:30:00 + +Tyler Wright: + +Tyler Wright: But yeah, I get much appreciated everyone's time and effort today. And then again, we'll talk over the next maybe 10 to 15 days about changing the Cadence. It sounds like nobody on this call currently has any issue with that said I again Mo most likely change the Cadence, but I'll reach out to a couple more folks and get some more input again much appreciative once time today in the update. + +Bold Panther: But They said yeah,… + +Tyler Wright: Go ahead pierced. + +Bold Panther: I found the notification Bell that was submitted in the last of town. So this is the bill that is being created by I think Nicki Harper. So there's something like kind of notifications that we can. Think of using it and also each other anyways interested to contribute. + +Tyler Wright: Yes, Feel free to reach out to ping me if you need any support there. + +Tyler Wright: That's a great shout to that if anybody here or anybody listening to is called later the akashathon the hackathon is underway believe it ends in the middle of May. So there's still a number of weeks to get involved. I will drop the link to the hackathon in the chat and I'll drop in the notes for people. But again, it ends May 17th with over 200,000 in prices in akt, so I'll drop that link in but again much appreciated from time the updates today and we'll talk online again. No steering committee meeting tomorrow steering committee meeting has been moved to next Thursday May 2nd. There is also a planned Network upgrade. that's up for both right now that is scheduled for May 2nd pending that vote, but we'll just stay in tune online. And again, please feel free to look at the public roadmaps or get involved in Discord if you have any additional questions in between + +Tyler Wright: Thank you all have a great rest of the day. + +Bold Panther: And I would never buy. + +Anil Murty: Thanks, sir. + +Tyler Wright: Bye. + +Maxime Beauchamp: Thank you. + +Meeting ended after 00:34:04 👋 + From 333025ef2c4dcc7e68d454a9070d5220eef69a8b Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 12 Jul 2024 20:55:40 +0000 Subject: [PATCH 100/138] Create meeting notes for wg-website #31 (#607) * Create meeting notes for wg-website #31 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 031-2024-06-13.md add video recording link and transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-akash-website/meetings/031-2024-06-13.md | 434 ++++++++++++++++++++ 1 file changed, 434 insertions(+) create mode 100644 wg-akash-website/meetings/031-2024-06-13.md diff --git a/wg-akash-website/meetings/031-2024-06-13.md b/wg-akash-website/meetings/031-2024-06-13.md new file mode 100644 index 00000000..9f6ff260 --- /dev/null +++ b/wg-akash-website/meetings/031-2024-06-13.md @@ -0,0 +1,434 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #31 + +## Agenda +- Review issues in the GitHub website repository. +- Open discussion for any website-related topics. +- Discuss the proposal to combine Akash website working group with SIG documentation. + +## Meeting Details +- Date: Friday, June 13, 2024 +- Time: 6:30 AM PT (Pacific Time) +- [Recording](https://urav5nq4ipj2qxxrryzspu67zqhcsvxc7iuv6mk7wkniixznkkmq.arweave.net/pEFethxD06he8Y4zJ9PfzA4pVuL6KV8xX7KahF8tUpk) +- [Transcript](#Transcript) + +## Participants + +- Bold Panther +- Denis Lelic +- Fenil Modi +- Hiroyuki's AI Notetaker (from Otter.ai) +- Rodri R +- Tyler Wright +- Zach Horn + +## Meeting Notes + +- **Introduction** + - Tyler Wright welcomed attendees and set the agenda for the meeting. + +- **GitHub Website Repository Issues** + - Tyler shared his screen to review current issues in the website repo. + - Tyler emphasized the importance of closing resolved issues. + - Bold Panther confirmed there are no unnecessary open issues and will monitor for any that need closing. + - Issues related to documentation are labeled for easy tracking. + - Insiders and Akash Community members have shown interest in contributing to documentation. + +- **Discussion on Combining Working Groups** + - Tyler Wright proposed combining the Akash website working group with SIG documentation. + - The combined group would meet weekly to discuss high-level documentation items and contributions to the documentation site and website. + - The goal is to have a more cohesive approach to managing both website and documentation updates. + - The new combined meeting would be called the "Akash Website and Docs Working Group." + - The purpose is to streamline discussions and encourage more participation. + - Tyler noted that the current working group has good participation and sees potential for more involvement from those who couldn't attend today. + +- **Praetor App Documentation** + - Discussion on the Praetor app documentation, which is not currently on the Akash Network docs. + - Plans to integrate Praetor app documentation with upcoming changes in the Console 2.0 product strategy. + - Denis Lelic will connect with relevant team members to discuss migrating or adapting Praetor docs. + +- **New and Ongoing Issues** + - New issues mainly concern documentation. + - Tyler and Denis highlighted the importance of addressing older issues as well. + - Encouragement for community members to get involved in resolving these issues. + - Denis is available on Discord to assist anyone interested in contributing. +- **Community Involvement** + - Tyler and Denis reiterated the call for more community contributions. + - Denis is available on Discord to assist anyone interested in contributing. + - Information will be divided into development and community pages. + - Bold Panther offered to take on the implementation. + + - **Provider Page Experience and Pricing Page:** + - Denis will revive the issue on provider pages and provide solutions. + - Key views: provider grid map and locality map need to be more accessible. + - Denis and Zach will work on improving the website navigation to make these views easily reachable. + - Combine general pricing and GPU pricing into a single page. + - Utilize hashtag functionality to direct users to specific sections. + - Zach emphasized the importance of clear pricing information, especially for comparison with other cloud providers. + - Bold Panther will mock up the combined pricing page on a staging site for review. + +- **Website Content Updates and Analytics:** + - Zach plans to make copy updates directly through PRs. + - This will not affect MPS as changes will sync with the main website before contributing. + - Bold Panther to discuss with Zach offline about cleaning up data sources. + - Focus on pulling active data sources from active properties and structuring GA. + +- **GPU Announcements and Contact Page:** + - Consider adding 4090 GPUs to the announcement bar due to high demand. + - Zach noted the rule of three for the announcement bar and suggested integrating 4090s if it doesn't disrupt the existing structure. + - Tyler and Zach discussed the flow and support for a contact page. + - Agreement to mock up a defined modal for the contact page and test it on a staging site. + + - **Ongoing Pull Requests:** + - Piyush mentioned an issue needing icon names for menu items. + - Denis to provide the necessary names. + - A new PR from a community member to add instructions for importing existing wallets needs minor fixes before merging. + - Piyush emphasized maintaining high-quality contributions to the website and is open to fixing issues himself if contributors are unable to. + - Tyler mentioned an influx of new contributors from the community. + - Emphasized maintaining the website's high standards and providing constructive feedback. + +**Action Items:** +- Tyler Wright to send a reminder message on Discord about the new combined meeting structure. +- Denis Lelic to follow up with the team about migrating Praetor app documentation. +- Denis Lelic and Bold Panther to work on streamlining information between development and community pages. +- Denis Lelic to revisit and improve the unified experience for providers and pricing page, with input from Zach Horn. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the working group for the Akashi website. This is a weekly working group. Today is June 13th, 20.4. Thank you to all that have joined. + +Tyler Wright: There's a couple of agenda items that I want to discuss today. Usually we go through the issues in the GitHub website repo folks can bring up anything that they want to discuss rage the website and then we can continue on one thing that I wanted to discuss and people can show thumbs up or thumbs down if they want but there's been recent discussion in save documentation about combining the working group for their class website and the working and elements of sync documentation. So I think the idea is that we would have is say documentation meeting once every other month to talk about high level documentation items. But anything related to the doc site and contributions to docs would be a part of the working group for the class website. So maybe we change a name to work and go for their cost website and docs being now all the work that bold Panther. + +Tyler Wright: Team have done on the website revamp and being at the Docks are under the website. The idea was to have a combined weekly meeting where we talked about all things cs and website related. If we need more than the hour, then we would figure out what that looks like. But again, this will be a time for people to talk about contributions. They want to make to documentation site to the website in general. So this is idea that was floated in sync documentation. I would like to move forward with this idea because again, I think this working group has a lot of participation. There's a number of people that are looking to get more involved and may not be able to make this meeting today but want to get more involved in supporting the website. So again, I think there's a lot of participation here and should be meeting every other week so we can stay as up to date on all things website and documentation related as possible does anyone + +Tyler Wright: Concerned about having some folks from the documentation working or a Sig going this weekly meeting and just having a combined website and documentation meeting. + +Tyler Wright: Okay, I see one So I don't see any thumbs down that's leading to believe that nobody has any issue with that. Cool starting in two weeks again. I'll drop a message and Discord just to remind folks but I think starting in two weeks. We'll start to have more folks in the documentation side here as well to go over documentation updates improvements Etc. + +Tyler Wright: continuing to move along. I know this is something that we use as a source of Truth. So I'm happy to share my screen actually real fast, but there are a number of issues in the website repo. I've tried my best to close issues that I believe are done, but does anybody see any issues In the website repo that do not need to be here anymore or is there any issues that are live right now that? Anybody wants to discuss. + +Tyler Wright: Here's I know that you are talking to me about closing some of these issues. Is there any issues if you still see here a close a couple recently that I saw PR's were already merged for and reference but for some of these other issues, I didn't see any PRS attached so led me to believe in the work hasn't been done, but I could be wrong about that. + +Bold Panther: setting it's fine so far. I don't see any issues That are pending to be closed. So I think everything is closed and all the issues that are open right now are open issues. So if I find any I will close the ones later + +Tyler Wright: Okay, excellent. there are a couple of issues that have been added again. I've been for issues that are related to docs. I've been trying to put a label or documentation just so it's easier for people to see and track. + +00:05:00 + +Tyler Wright: Are an Insider and Akash Community member has been talking to me about ways. They want to get involved with documentation. + +Bold Panther: Okay. + +Tyler Wright: I think they've already submitted a PR and we'll continue to submit more PRS. There's a couple of actually insiders that have showed interest as of recently and getting involved with documentation. So again, there are a number of people that'll look to get involved with documentation the website but one of the issues is around the Prater act with the acquisition the Prater app documentation isn't currently on the constant Network docs. I know there's going to be significant changes to the way the Prager app looks and feels in the future as a part of the console 2.0 product strategy, but there is some thought about at least having their current state today. Just so people can find a documentation one place. Does anyone have any thoughts concerns about this particular issue? Go ahead Denis. + +Tyler Wright: + +Denis Lelic: Thanks, I've briefly talked about greater dogs with the voluntar. + +Tyler Wright: Before we look to continue to assign it to somebody and get the work done. + +Denis Lelic: I'm just gonna connect again with them to see if they have any plans to migrate those dogs or at least adopt those dogs to match the console So we have a clear Direction on this thing. + +Tyler Wright: Yeah, if you could show them this issue and let them know that there is a team member willing to do it if they feel like it might be too difficult. Then we can have this Community member work on something else. There's also another member of the parade or team that's not part of the overclock team. that is an Insider about Saul that may be able to help with this as well because I believe he's previously done ux work and continue to do ux work for Crater. So there's something to also talk about but if you can Follow up with bigger and default I'd be amazing. + +Denis Lelic: Cool. Yeah. + +Denis Lelic: Yeah, so there's a bunch of new issues mostly regarding the docs. + +Denis Lelic: Just going through them. Yeah. + +Tyler Wright: There's also a couple of old issues that I would love to see. worked on I know that Denis is working on 9 million things. + +Denis Lelic: the number one + +Tyler Wright: Just the number one. + +Tyler Wright: But there are a number issues. And again, in Sig design, we had some conversations about folks that want to get more involved with helping again design some of these experiences so that they can be implemented. But yeah, I just want to shout out that again. There's anybody wants to get involved and some of these things that feel free to + +Denis Lelic: Yeah. Thanks time anyone who's interested can also M me on Discord. I'll be happy to take you through all this stuff. We've been working on and continue to work on. + +Bold Panther: So I think at this point we should address the number one issues that is about streamlining. That's the information related to the community and development. So we divide the problem information between these two pages a development or related content being in development page and the community related things in being in the community page. So I think this is something if the otms busy this is something that I can. Data ui4 and can start taking it forward for the implementations. + +Denis Lelic: Yeah from my side tie. I feel let me I'll just go back as well to couple of other issues. + +Denis Lelic: One is like this unified experience for providers. I think that was created by Zach so in the next couple of days + +Denis Lelic: I'll try to. Bring that issue back to life and just provide some ideas Solutions there. I think I already did a couple of weeks ago, but I'll just go through it again to see what other options there and how can we improve that? page and the same goes for + +00:10:00 + +Denis Lelic: Pricing I know Zach I think after accelerate happened, we should do something about the pricing page. The information is a bit kind of scattered and behind a couple of curtains. So just try to bring that up front. So it's informational easy to reach and so on and so on so maybe from top of my head just like those two issues. And of course the community number one issue as well always on my mind. + +Zach Horn: Yeah, both of those would be great… + +Bold Panther: Yeah. + +Zach Horn: which is the provider issue you're mentioning is that the old issue that was created a long time ago kind of towards the bottom of the list. + +Denis Lelic: Yeah, I just found it. + +Bold Panther: No. So no,… + +Denis Lelic: Here it is. + +Bold Panther: so it's related to the issue that's been created by one of the community members. I think yesterday. It's extreme in the information about the provider on the tops. + +Denis Lelic: not + +Denis Lelic: No, no, it's not the docs related this one. It was created by Zach. So yeah you're right. It was way back in February, so what we kind of discussed this in the comment section here in the GitHub and in the threads and so on but I'll just try to keep this thing alive until we reach something. Everyone is happy with and it's ready to implement. + +Zach Horn: Yeah, I would love to move on this and just at least put some work behind it. And Denis you're not gonna chat offline if you need anything for me on it because there's two main things one is we need to streamline the provider pages. So essentially when somebody lands on the website, they should be able to easily see who are the providers on the network and if you jump into that issue the one that tennis linked these two screens are the most important by long way. So we just need to make sure that people can get to these two visualizations as quickly as possible because this is what people want to see it's like ing. This provider map with the grid which is excellent. And then the locality map you can see where the providers are around the world. So they're a little buried at this point and that's I mean we did a lot of work to just get the website off the ground. Yeah. Thanks time. + +Zach Horn: We did a ton of work to get the website off the ground, but my one piece of feedback is the things are a little bit scattered at this point, things are buried behind layers of navigation. So some of that's okay in certain instances, but I do think for some of these very important views that people want to see right away. We should just bring them closer to the surface. so yeah, I'm with you Dennis. let's move on this and just get it done. What was the other issue that you brought up? There was a provider streamlining and then the pricing right? right + +Denis Lelic: Pricing we kind of talked through mostly DMS and I think there was no yeah,… + +Bold Panther: slide + +Denis Lelic: I think Pierce was involved there as well. So + +Zach Horn: I'll Do you mind Denis by just give you my one piece of the context of why that even came up at all? So I was at consensus with a couple weeks ago Greg did a presentation. + +Denis Lelic: Yeah. + +Zach Horn: On one of the side stages and he was doing a workshop and he ran into the same issue that I've actually run into a couple times, which is you're looking for not the GPU pricing page. That's obviously in the nav that's very easy to find but the one that compares to the other large Cloud providers, the one I'm talking about where you can enter your resources and it shows that it's 85% less or whatever the percentage is. that one is pretty hard to find on the website and Greg was having trouble finding it. I've actually had done the same thing when I'm talking to somebody. I just can't find it. So anyway, those are the three. + +Zach Horn: The provider grid map the locality map and then the GPU pricing Pages obviously very important. But also that other one that's gonna be one that we should lean into strongly going forward because I can just tell you from talking to a ton of people at these events. That's the thing that catches people's eyes. They're like, okay, I can tell you kind of resources. I want to run. How do you compare on price? So All that to say I'm with you Denis, let's move on this and just claim this huge. + +Bold Panther: Yeah, so I have a thought on how we can tackle this issues while also keeping the GPU pricing CPA top of the network. + +Zach Horn: Okay. + +Bold Panther: So what we can do is we can combine both the sections in first talk. We keep the general pricing in the second half we can keep the GPU pricing whenever the user clicks on GPU pricing. We have the hashtag functionality. which takes them to the pricing phase and automatically scroll down to the chipazing section. So I think this is something that we can do from the ux perspective. This will solve all the issues accessing the general pricing ways. Also the GPU pricing at the same time. + +00:15:00 + +Zach Horn: Okay, that sounds great. let's move forward and just mock it up on a staging site and then I'll get that In front of Greg because he feels very strongly about the GPU pricing page. So I just want to make sure he's aware of any changes that we're gonna make to it. But that sounds great to me. I think one place makes a lot of sense. + +Bold Panther: And in that case we can like in the pricing base. + +Denis Lelic: yeah, I + +Bold Panther: What we can do is as well be combining both the sections into a single page and it's going to be a dedicated page. We will not keep the site navigation that is present about which so it will be a complete pricing page in the first half days of pricing comparisons in the second update is GPU price. So it will also make it visually more appealing and also it will not break the Aesthetics about the current price in Pages if someone clicks on HP pricing City + +Zach Horn: That sounds good to me. let's mock it up, but it on a staging site and go from there. + +Bold Panther: Yes, sure. + +Zach Horn: The other thing views that I'm just gonna run by you this shouldn't affect anybody but for some of these pages, I think I'm just gonna jump in and do some PRS that they copy. Is that going to affect anything on your MPS just in there updating stuff. I think I can navigate the code base well enough, so I think there's some of this that I can just do as opposed to, having us to coordinate. + +Bold Panther: So can you elaborate a bit when someone contributes and copies to PR or something like? + +Zach Horn: No, no, I mean update the copy the words on the page for some of these. I want to go and I just change some of the language around. + +Bold Panther: Yeah, no worries. you can change it. So whenever we contribute to the website we first sync in with the main website and then only we start Computing so it will not create an issues for a scale. + +Zach Horn: Okay, sounds good. + +Bold Panther: + +Denis Lelic: Yeah, I agree with you guys. I would only suggest we kind of create an issue for this. So we just have something everyone can track or visit to see What are we working on and… + +Zach Horn: Yeah, great. + +Denis Lelic: so on and so on? + +Zach Horn: It's a tire you sharing screen right now. If so, could you scroll down and just put the price comparison on screen? The one right above it. That's action right there. + +Zach Horn: Is this okay? So it's funny that we're talking about this now. is this the one I'm thinking of I thought there was a modal where you could enter your Resource information, is that a different one or is That's okay. + +Denis Lelic: Yeah, it's this one at the top. + +Zach Horn: I see got It was offer a second. Okay, perfect. Yeah, this is great. I mean you could use a little bit of a redesign but + +Denis Lelic: Yeah, I agree with that. We actually had pierced… + +Zach Horn: Yeah. + +Denis Lelic: you remember we had a design with sliders but at the moment. back then Let me just try to recall it. I think it was not possible with the API. + +Denis Lelic: so the slider meaning CPUs memory and storage would be just with a slider so you can just easily change the number so you don't have to so it would go 1 to 100 really fast or thousand whatever we limit. each of the + +Bold Panther: It's possible. I think we did within discussed about this. I can't recall but I think there is no issue with the API. Even if you remember the slider we have nothing but change a bit slider. We are nothing but changing the numbers behind the scenes. So there is no limitations of the API. We can implement the slightest. It's required. + +Denis Lelic: Okay, cool. Yeah, I have some ideas here. So maybe we just continued this discussion and + +Denis Lelic: And the issue we're about to create. + +Tyler Wright: Yeah, that would be great. + +Denis Lelic: stupendous + +Zach Horn: come on Ty give us an adjective. You got a one-up student on this. + +Tyler Wright: I can't it's too good. + +Zach Horn: alright. + +Tyler Wright: I'm not the content King Zach. + +Zach Horn: that prayer + +Tyler Wright: I don't have that ability, + +Zach Horn: It was my title from yesterday. I have content King and was the other one. the branch. + +Denis Lelic: Brian Shepherd + +Zach Horn: My business card gets longer every day. + +00:20:00 + +Denis Lelic: Yes. I mean we gotta collect those. + +Zach Horn: Okay. + +Denis Lelic: Yeah back to the website. + +Zach Horn: I think for microspective if we get those two views, in the first issue plus this pricing model integrated with the GPU pricing page and then we get all of that surfaced. That to me is the highest priority thing we can do with the website. There's some things on the content side that we need to do as well. But that's more of my plate than anybody else's. + +Zach Horn: But what really an ideating just a little bit that we can move on. is if we surface those views the ones we just mentioned. We can get to a place where we're actually starting to address really tangible pain points for people and this comes from talking to people at events. it all comes back to how many providers do you have on the network? Where are those providers in the world? What is your pricing? can I see my pricing on Akash relative to some of these other Cloud providers? So we start to build all that out and we can even do some work on the homepage of the site to lead people through that flow that we're essentially checking against people prospects when we're talking to them in person. I think we're in a different place a better place. + +Bold Panther: if I + +Denis Lelic: Yeah, I agree. + +Zach Horn: That's it for my side on that we can move along. + +Tyler Wright: I think these are all great points. I just want to confirm Denis. Are you gonna own creating the issues that we just discussed here so we can continue to track them or was it Peter? She was gonna do it. I just want to see who's gonna own. It just go we can continue tracking because I think we're on the same page as what the priority and the next order of operations for is for and I appreciate exactly talking about The Real World experience and how these things play out during events and elsewhere, but I just want to make sure we're continuing to crack it and then deliver on it, + +Denis Lelic: Yeah. I can create it. So no worries. + +Denis Lelic: Okay. + +Bold Panther: So I have a question for So as a Zach shared the data sheet about the website analytics. So I just have a few questions. So as I share I dropped in the link where we can have a visual saw the general website analytics the users Etc training more refined manner. As Jack pointed out. So I just want to ask what you want specifically what modifications to invade in the default version of it. + +Zach Horn: So let's chat offline about that. There are some. + +Bold Panther: Yes. + +Zach Horn: There's some thoughts there. They're going a couple of different directions basically at the highest level. all that we need for the first phase of what I was mentioning the other day is That we just need to clean up some of our data sources so that everything is current. We're only pulling active data sources from active properties and then just start to structure out GA and then we have some of these liquor reports that need to reflect the accurate information. it's not too much like technical GA work. It's really just data cleanup more than anything for this first phase,… + +Bold Panther: that + +Zach Horn: but I'll drop you a note right after this weekend get into that. + +Tyler Wright: Cool, are there any other? Website items that anybody wants to discuss this might be actually small time small fries. And I know this is something that we could change but I was wondering if it makes sense to add 40 90s to this announcement bar at the top being that they get so much traction on the network even relatives to the a6000s again. I was just looking for the website for two seconds and just thought about that. So it may not be anything that anybody cares about or may not be that necessary, but just want to shout it out in the website. + +Zach Horn: Yeah, the only on a technical level the utility absolutely we're getting crazy demand for forty nineties. I mean really like shocking demand. On the copy side. it's just the rule of three so you have to either a place one of those or break the rule. Not opposed to it. you'd have to go h100 a100 a6000 and 40 90 which is kind of clunky, but from the utility of it should be surface 4090s that absolutely + +Tyler Wright: I think that's a good point content King. So I was just again putting out that however, we decided to move forward I'm fine with but as we mentioned 40 90s are Hot Springs. + +00:25:00 + +Zach Horn: They are they are. + +Denis Lelic: Yeah, just content King. Zach here one of those Game of Thrones guys where when they introduced them and they go with a bunch of names like + +Zach Horn: man, that's too funny. Yeah, exactly. that's precisely going for some Lord of Westeros ruler of the whatever. Yeah content King ever. + +Denis Lelic: the branch Shepherd + +Denis Lelic: Okay. + +Zach Horn: Yeah. + +Tyler Wright: here something actually an issue that know. The hero was looking at as well and talking about but I know we've moved it down the priority list so we can keep it there is around contact page. I know they actually hero is going to be helping contribute to console as well and how getting acclimated there. But I just want to say if that's something this issue the contact page is still something that's on hold obviously is with the priority than the GPU provider. + +Tyler Wright: Stuff that we're talking about earlier, but I just wanted to see if there's something that can be moved forward Tandem with all the stuff that's being done. Maybe hero could take us on or if this is something that we should just continue to put on pause for the time being. + +Zach Horn: What Tyler can you scroll down to Heroes lower in the thread here the mock-up. Yeah. + +Zach Horn: So the two questions one, where does this go? I probably took a catch all email. + +Denis Lelic: Yeah. + +Zach Horn: Type, okay. + +Tyler Wright: Believe that's the intent. Yeah, or I believe there's an option where you can have a number of emails you can have a BD email billing email whatever and… + +Zach Horn: right + +Tyler Wright: then it'll go to the respective email. + +Zach Horn: we can continue this in the discussion. If we want to, idea async on this. + +Zach Horn: Entire unit talked about this little bit offline. I'm not opposed to this in any way. + +Tyler Wright: Yeah, yeah. + +Zach Horn: The only question is what is the flow? So I do understand there's lots of people, that they're used to the kind of web to it for lack of a better term flow where they land on a website. They want to see a contact page. They're just used to doing this and dealing an On the flip side. The question is support for that email address and I think you felt strongly that that's not going to be an issue. you'll fail that way? + +Tyler Wright: Yeah, I do still feel that way. And if we find that any of these become an issue, then we can I remove it from this contact page. I think for now if there's more than one point of failure, so if it's going with the email is going to one person. I think that would be less than optimal. But I think in many cases these will be going for a number of different people can make sure that everything followed up on… + +Zach Horn: You sure. + +Tyler Wright: but I do understand your hesitancy because then they'll be another touch point that has to be managed and maybe things get lost in. but it's a set of balancing act of to your other point. Some people are used to doing this and then may not be even willing to do the Discord telegram route, … + +Zach Horn: Right. Yeah. + +Tyler Wright: or get home. + +Zach Horn: I don't disagree with that in any way. I would say s similar to the other thing. What's mock up like a defined modal for this figure out where we want to put it on the site get it in staging and set up the infrastructure for it and then go from there and see if we can buy-in from that for folks internally. + +Tyler Wright: cool that makes it I'll drop a comment in there and hero maybe just keep on looking at it when you have some time. + +Tyler Wright: That's all I had of things on issues. And again the structure of the working group as we move forward that I wanted to discuss. Is there anything Pearce in terms of pull requests that haven't been merged yet that you want to talk about are there some of these that just need additional notes or have you given comments and just waiting for people to follow up? + +00:30:00 + +Bold Panther: So there is one issue like that is open for quite some type. So as you can see the second we are at icons to the menu item networks. So The second pair so I just want the next to just provide the name of the icons that are present in the UI. So hero can just edit those icons in this. Yeah. + +Denis Lelic: And I consider the menu. Okay, I see. Yeah, sure. + +Denis Lelic: Sounds good. + +Bold Panther: That's all and this is one new issue. There's been created by things engine and the pr is being created by one of the community members at the dogs with the instructions to import the existing wallets the latest fear. So it's just a small mistake. So I have permitted the town domestic to fix once it is fixed. I will just most of you. + +Denis Lelic: cool + +Tyler Wright: Thank Again peers, there's a number of people that reached out to me publicly and privately from the inside of just generally new community members that want to get involved with the docs and the website. I push them towards a readme file. So they learn how to contribute and they're doing it the right way, but I believe is going to be a number of new contributions from people that will start joining this meeting sometime a next couple of weeks. So again, feel free to continue to give the constructive quality feedback as we've all talked about with the website revamp. We want to keep it to the same standard is right now, so if people aren't meeting that standard just continually comments until they follow through and exactly where they need to before merging. I think Hero has done a good job of that. I think there's other people in the community and then a good job of that and that's why there's their PR so that merge so we'll keep that consistent. + +Bold Panther: If I always make sure that the priests are coming to the websites are of high quality. If there are issues with the code or implementations all the pr might fail and if the pr creators or the contributors weren't able to fix the issues. So in some of the cases I do myself and then most of yours if they are of high quality and great additions to the website, but yeah, this is the process. I follow before Modi any of the peers to the website. + +Denis Lelic: Sounds good. + +Tyler Wright: Excellent. Thank you. + +Denis Lelic: So I think Pretty much went through all of the issues and we got some new coming up. So. The pricing issue I'll create that one and I'll follow up on the providers issue Zach created a while ago. So those are mine two action items. + +Denis Lelic: yeah, that's it for my side I guess so if anyone else has Something at least. Yeah, we still have some time. So if anyone else has some many questions or would like to know something about the website or the working group. Feel free. to ask or to talk + +Denis Lelic: Okay video just drop. Yes, not so. + +Denis Lelic: Yeah, but I think we can wrap it up for today. + +Tyler Wright: Yeah, think we're good. But I think it's a very productive meeting and we'll take next steps on those priorities for the website that Zach had mentioned and continue to go from there. + +Denis Lelic: + +Denis Lelic: So thanks everyone for joining today. I think we'll see each other in two weeks from now in a slightly different format. It's actually the same we're just adding a topic of Akash talks. So we'll see how that goes. Maybe we split the meeting first everything about docs content and so on and the other half we can talk about the UI ux + +Denis Lelic: Yeah bold instant action item pricing and provider. Yeah, that's right. Yeah, so we'll see each other in two weeks. So thanks again for joining today. + +Tyler Wright: Thank… + +Bold Panther: thanks. + +Tyler Wright: Talk to you guys soon. + +Zach Horn: thanks guys take + +Denis Lelic: Thanks. Bye. + +00:35:00 + +Rodri R: bye guys + +Meeting ended after 00:46:25 👋 + + + + + From 61c58fda62be56844b9b814c23b942badf731819 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 12 Jul 2024 21:01:55 +0000 Subject: [PATCH 101/138] Create meeting notes for wg-website #30 (#596) * Create meeting notes for wg-website #30 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 030-2024-05-16.md add transcript and video recording Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-akash-website/meetings/030-2024-05-16.md | 627 ++++++++++++++++++++ 1 file changed, 627 insertions(+) create mode 100644 wg-akash-website/meetings/030-2024-05-16.md diff --git a/wg-akash-website/meetings/030-2024-05-16.md b/wg-akash-website/meetings/030-2024-05-16.md new file mode 100644 index 00000000..85e11b4f --- /dev/null +++ b/wg-akash-website/meetings/030-2024-05-16.md @@ -0,0 +1,627 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #30 + +## Agenda +- Akash Accelerate Page and Speaker Order +- Visual Updates and Accessibility Improvements +- New Issue: Contact Page Feedback +- Documentation Issues and Improvements +- Additional Issues and Assignments + + +## Meeting details +- Date: Tuesday, May 16, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://dpisfxnpneb3dvtssughllgmsyn6a7qasqh62lwtpuvm3xaomcnq.arweave.net/G9Ei3a9pA7HWcpUMdazMlhvgfgCUD-0u030qzdwOYJs) +- [Transcript](#transcript) + +## Participants +- Bold Panther +- Denis Lelic +- Tyler Wright +- Zach Horn + +## Meeting Note + +- **Introduction:** + - Tyler Wright welcomed everyone to the bi-weekly working group session for the Akash website. + - Emphasized the importance of these sessions for discussing and improving the website. + - Encouraged participation through the Akash website channel on Discord. + +- **Speaker Order for Akash Accelerate Page:** + - Denis Lelic brought up the need to order the speakers on the Akash Accelerate page. + - Suggested Eric and Greg should be prioritized but asked for further input. + - Zach Horn offered to rank the names and send the list to Denis for adjustments. + +- **Updates on Portraits and Titles:** + - Denis mentioned ongoing corrections to new portraits, with some specific issues highlighted. + - Missing title for David Johnson noted; a placeholder title "CEO of bread Dev" used temporarily. + - Zach stressed the importance of confirming titles directly with individuals and avoiding assumptions. + - Amanda is actively verifying speaker information via emails. + +- **Feedback on Team Titles:** + - Zach proposed a title change for Neo and Chang to "VP of Product and Engineering" with an ampersand. + - Suggested the title "Core Team Akash Network" over "Creators of Akash Network" for consistency. + - Sought external feedback from Bold Panther, who confirmed "Core Team Akash Network" is clear and appropriate. + +- **Design and Update Process for Akash Accelerate Page:** + - Denis updated Piyush on the timeline for receiving updated information and illustrations. + - Discussed the need to finalize the run of show and suggested it might be ready by the end of the week. + - Zach agreed on the importance of updating the schedule and ensuring it's visible, even if it changes later. + - Confirmed Amanda as the MC for the day. + +- **New Issue: Contact Page for the Website:** + - Denis mentioned a new issue raised about the difficulty of contacting the core team through the website. + - Piyush suggested implementing a simple contact form accessible from the footer, allowing messages to be sent to different departments. + - Zach expressed concerns about the potential for spam and the complexity of managing emails, suggesting Discord as a more responsive channel. + - Tyler proposed a contact page with dropdowns for specific queries (e.g., Business Development) that could send emails, while technical support queries could be redirected to Discord. + - Bold Panther suggested a common contact page with sections for different types of support and outreach, integrating existing support elements and social profiles. + - Agreement to map out the contact page more thoroughly and prioritize it lower for now, considering the other ongoing high-priority tasks. +- **Presentation of New Visuals for Documentation Integration:** + - Bold Panther presented visuals for two new documentation issues: Quick start section for "How to integrate with the Akash Network" and "Deploy Hello World in five minutes or less." + - Tyler emphasized the need for a clear and accessible guide for projects to integrate with Akash Network. + - Zach supported the importance of case studies and prioritizing them in documentation. + - Discussion on managing bandwidth and prioritizing tasks. + +- **Discussion on Quick Start Guide for Deployment:** + - Tyler emphasized the need for a one-pager or video guide on deploying via CLI and console. + - Zach agreed on the importance of a simple and quick guide for new users. + - Bold Panther suggested having someone with experience in Akash create the content. + - Tyler proposed assigning the task and prioritizing it higher than the contact page. + - Agreement to possibly add the quick start guide to the Essentials tab on the website. + +**Implementation of New Effects on Icons:** +- Hero initiated changes to icon hover effects, making the color change to red. +- Denis appreciated the initiative, confirming that the changes are pending final approval and merge. +- Bold Panther is addressing bugs noticed in Hero's pull request before merging. + +**Documentation Issues and Improvements:** +- Bold Panther discussed improvements to the documentation pages, such as auto-opening the first page when clicking on sections. +- Noted a bug where refreshing the page defaults to the homepage, which is being fixed. +- Hero’s pull request is under testing before being merged. Bold Panther is ensuring all issues are resolved. + +**Additional Issues and Assignments:** +- Tyler proposed inviting Hero to these meetings for better coordination, despite language barriers. +- Bold Panther emphasized Hero's daily contributions and active engagement in resolving issues. +- Tyler mentioned a new issue regarding updates to the console page, to be created and managed on Discord. If Thomas cannot handle it, the task will be outsourced to the community. +- Denis, Zach, and Bold Panther confirmed there were no additional issues to discuss. + +## Action Items +**Denis Lelic:** +- Review and finalize the speaker order based on Zach's rankings. +- Follow up on portraits and titles for Akash Accelerate speakers. +- Provide Piyush with the necessary information and illustrations for the Akash Accelerate page. +- Continue improving accessibility graphics for the Engineer Docs. + +**Zach Horn:** +- Assist Denis with the ranked list of speakers. +- Help finalize the run of show and ensure it is updated. +- Provide feedback on the contact page idea and help map it out. + +**Tyler Wright:** +- Create a new issue for the console page updates and manage it via Discord. +- Discuss the new issue with Thomas and reassign if necessary. +- Ensure consistent use of "Core Team Akash Network" in all documents. +- Invite Hero to future meetings and ensure he is informed about meeting schedules. + +**Bold Panther:** +- Continue addressing bugs in Hero's pull request and ensure it is merged after thorough testing. +- Work on visual updates and accessibility improvements for the documentation. +- Coordinate with Hero on daily contributions and ensure all issues are properly addressed before merging. +- Develop and refine the quick start guide for deployment with input from experienced team members. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the working group for the Akash website. It is May 16th 2024 during these working group sessions that happened by weekly the group gets together to go over any issues in the website talk about anything that needs to be improved or updated. Again. The website is the main Hub past that Network for all things related to Akashi Network the docs also live under this website repo. So again, if anybody wants to participate in finding issues or helping improve the website, feel free to join this working group session that meets weekly around this time as well as get involved in Discord the working group of cost website Channel. There's a number of issues that I would like to discuss today, but I'm going to kick it over. + +Tyler Wright: To boss man Denis to see if there's anything he wants to covered agenda wise before we get into some of these issues. + +Denis Lelic: Yeah. Thanks one thing really quickly + +Denis Lelic: regarding the page Akash accelerate. So I was just wondering about the speakers And what order should we present? So I didn't really put much thought so I was just thinking like Eric. + +Denis Lelic: Probably should be on top somewhere like the first line maybe Greg but For the rest of them. maybe Zach you have the most awareness who's the I don't want to say most important but Who do we want to present first Maybe? + +Zach Horn: Yeah, that's right. I mean we do have to order these. Would it be easiest if I just rank the names and then you can adjust? Okay. + +Denis Lelic: Yeah, maybe you can just DM me the list. So we got the first batch of these portraits. + +Zach Horn: Yep. + +Denis Lelic: There's an extra round of Corrections going on at probably now as we speak or so + +Zach Horn: I was going to mention that as well do we know which ones are being worked on? + +Denis Lelic: Pretty much all of them. from The New Batch, so Maybe Lexus Some of them I have two thick limes and stuff like that. + +Zach Horn: Yeah. + +Denis Lelic: So David needs some work here. + +Denis Lelic: Yeah, so I just forgotten name The illustrator to make thing Corrections, so I'm hoping I'll receive those today next to that I have. I'm missing a title for David Johnson. And we're still kind of waiting for a couple of them. So another I just put CEO of bread Dev. but we're still waiting for his information + +Zach Horn: Yeah. That is correct. But yes, we do need to confirm. And just while we're on the topic. going forward for these just know assumptions on titles. I had to talk with Greg about that the other day we just have to confirm with these people directly. It's a little bit of a pain because we have to go through and contact people if we don't know, but we just have to do it if you need me for anything on that. Just let me know. I can push things along. + +Denis Lelic: Yeah, Great. Yeah, I know Amanda has been sending emails and stuff like that or the speakers Just to verify all the information we got from them. So yeah. + +Zach Horn: One which is what we're looking at this page one quick change we could make is for our team titles. So a Neo and Chang title titles are correct a Neil's preferred as a VP of product and… + +Denis Lelic: Yeah. + +Zach Horn: Engineering so you can just do VPN product and Engineering overclock Labs do an ampersand for hand. + +Zach Horn: And then this is the tricky part. I would suggest core team Akash Network. Like we're doing for the business cards that whole the hype in creators of I just don't love but this is minor we can talk about it. Later. Just thinking out loud while I'm looking at the page. + +00:05:00 + +Zach Horn: I don't want to derail at all but huge while we have you just a little feedback. I'm honestly curious when you see core team Akash Network like that. does that make sense to you? do you think that'll make sense to people that aren't us, like what that means. + +Bold Panther: Can you repeat the first word? what did you say when you say Decap? + +Zach Horn: Yeah. Yeah, you see where it says core team Akash Network in a title there. + +Bold Panther: mmm + +Zach Horn: I'm curious. does that make sense to you and you think it'll make sense to people outside of the overclock Labs team? That's what something we've been talking about. I'm just looking for a little outside feedback. + +Bold Panther: So yeah, I think that's pretty clear. when we say creators of team Akash Network. It doesn't make sense these request belongs like These are the speakers who are the gold team of Akash, and then we are mentioning the roles of others as well in a particular organization. + +Zach Horn: Yeah. + +Bold Panther: So, I think it just makes sense you For me, both were dealings make sense, either creators of core team Akash network, but as we are mentioning core team everywhere. So I think coding doesn't make no sense as compared to creators of akashion. + +Zach Horn: Okay, perfect. Yeah, but I feel better. At least we have one point of a outside feedback. + +Denis Lelic: yeah, it's Yeah,… + +Zach Horn: Alright, so sorry Denis back to you take it away. + +Denis Lelic: so Pierce, I know you've been waiting. + +Denis Lelic: On this design just to update the page. So as soon as I have all the information regarding, titles and updating those updated illustrations all dmu. It's not probably going to take much effort in time to do the update. + +Bold Panther: Yeah. + +Denis Lelic: Everything is pretty much there. So we just need to populate with proper and… + +Bold Panther: Yeah. + +Denis Lelic: correct information. + +Denis Lelic: Yeah. + +Bold Panther: So I as soon as I get it will be hardly truths of daily thing. So just driving on the film and + +Denis Lelic: Okay, Yeah. The other thing is we don't have the final. Run of show yet. So I was just thinking if we should leave it. this kind of blurred a little bit because we're still kind of trying to figure out the + +Denis Lelic: Who's going to talk at which time and so on and so on and so on? So, what do you guys think? we can do first batch updating the speakers and second batch. I'm not sure if this is gonna happen this week, but in the beginning of the next week, we should update the Run of show. + +Denis Lelic: What do you think guys? + +Denis Lelic: Zach I know you've been involved in all of this stuff + +Zach Horn: Yeah for what I would say Is that there's some changes going on currently, so I'm in two minds about it one. We can update as it comes in and just understand that it may change and that's probably fine. I do agree that we can't have a coming soon forever. yeah, I'm Exactly. + +Denis Lelic: Yeah, I mean next week. + +Zach Horn: Yeah coming soon until the day before. + +Zach Horn: Yeah, let me do this because there's some conversations going in the background around what the order of some of these things are going to be and there's some shifts happening at the moment. Let's see if we can get to a roughly finalize schedule by the end of today. Let's call it the end of the week. Just be safe under the day tomorrow and… + +Denis Lelic: Yeah. + +Zach Horn: then if some of the major things that we're working on now get sorted we can just update and make it visible is if it has to shift from there. that's probably fine. I don't think anyone's gonna be like, keeping receipts on this or anything so + +Denis Lelic: Yeah. Okay, cool. + +Zach Horn: One quick thing for MC of the day that's going to be Amanda and… + +Denis Lelic: Yeah. + +Zach Horn: that's locked in so we can just update that. So that's an easy one we could switch. + +00:10:00 + +Denis Lelic: Okay, cool, so, I think that's everything and that's happening on this front of Akash accelerate so I think that. next action items are updating all of the information portraits illustration and so on and hopefully tomorrow we're gonna have a run of show + +Denis Lelic: And some shape or form maybe not final but yeah. getting that + +Denis Lelic: one sack + +Denis Lelic: just want to run through the latest. issues so website repo + +Denis Lelic: Okay, the new issue has been created by fresh 44 minutes ago. So users have mentioned that it's difficult to contact the core team through the website was wondering if we can add a simple contact page to send messages to different departments. This would be a quick thing. It can be a page accessible from the footer. We can Implement and we got Piers here replying. we can Implement a functionality that allows users to send messages to record via email through a simple forms Mission. We do also have a support page to reach out. Okay. + +Zach Horn: Okay, let me jump in. + +Denis Lelic: Yeah. + +Zach Horn: I was waiting for this one. I was stretching and prepping. + +Zach Horn: so good feedback. + +Zach Horn: Here are the two issues. one I get that some people are more comfortable with email than with this chord or Twitter and all that. that said those channels are gonna be 1,000 times more responsive than catch all email addresses the obvious thing that's gonna happen with this is we're going to put in a bunch of emails and they're gonna get unlimited much spam. And there will be some legitimate messages in there, but then it comes down to our people checking the email who's owning the threads in the email. So what we're proposing here is going to create a ton of fractionalization of Outreach. I've been of the mind up to this point that although we're forcing some people who would rather email to go to Discord that keeps it in one place and we have support there. So that's my feeling on it. I'm not. + +Zach Horn: I'm not going to throw all my weight against this but it's not quite as simple as it was made out in the internal discussions and here. I'm open to finding a solution but I go ahead because I'm clear. I'm curious what you guys think. + +Tyler Wright: I agree with many of your points. So here's how I have it going, in my mind. Basically have a contact page that has a couple of drop-downs some of those being Business Development, and then it lends you lets you send an email if you're looking for technical support. It won't let you send an email and it pushes you into Discord. + +Bold Panther: actually just + +Tyler Wright: So it would be specific things and then on the email front like we do with a number of different emails. What I think should happen is these emails whether it be Business Development or whatever other ones we let people send messages through it goes to a number of people within the core team. + +Tyler Wright: and then as an ownership standpoint again, we could either this is something that I would see I'm always looking at those emails anyway, and I can continue to push those forward in different directions or somebody else could but I understand exactly what you're saying My only pushback is there are a number of web2 folks that don't seem to be able to hop over that hurdle as easy as it is, and if there's a way to catch some more of those and to your point about spam if there's a way to kind of Filter that out through some sort of a simple robot system or something. That would be great because I do think that would be an issue. But I'm of the mind that it may just be worth it for that web to audience that I know. + +00:15:00 + +Tyler Wright: Many people within the Cosh Community have talked about trying to capture and I think it's a challenge, I mean, it's not technically speaking. It's not a challenge for somebody big. Alright, I just got to go and Discord and then I can get my question answered in two seconds, but it seems to be a hurdle that people from traditional web to can't seem to hop over. + +Zach Horn: I'm with you on that. I mean obviously it is but here's the thing. if that's the cohort that we're talking about that is going to be the first of 50 hurdles. so it's like okay, we're going to get them over the first hurdle and then 49 more hurdles. So I agree with you. none of this is me be doing this but We do. + +Tyler Wright: Yeah. + +Zach Horn: The way it's being presented at this point. It's just not that simple and I don't + +Zach Horn: I don't want to take us down a path where? We put this in place and it just creates a ton of complexity that we've already done a great job of Outsourcing to the community via the vanguards. So What I would say is let's not rush on this one. Frankly. This is not priority to me. especially in the next two weeks we Call it 10 other things that are priority. This is not one of them. + +Zach Horn: The other thing that we will run into with this is the Evergreen issue of it's a decentralized network So when you say contact us, who are you contacting? You could get around that by saying the core team. But then that needs to be defined so if you land on Akash Network and you say you're contacting the core team, who is that? So that's an issue that's been on the table for quite a while. + +Tyler Wright: I agree with that point. + +Tyler Wright: I'm fine to slow this down for a couple of weeks. I just want to at least think about the problem. + +Zach Horn: Yeah. + +Bold Panther: out there Yeah. + +Tyler Wright: I know it's like a challenging problem Zach. I've not disagreeing with any of the points that you're saying, but I would just argue. Yes, it's gonna be 49 other hurdles. + +Bold Panther: of + +Tyler Wright: I agree with that wholeheartedly, but If we can eliminate the first one to at least we can get talking to them. And we can carry them over those hurdles or right now. It seems like they can't even carry themselves or understand to move around into discourse, and again,… + +Zach Horn: Yeah. right + +Tyler Wright: I'm only talking about some of that audience that we seem like we want to get everybody in the community like web 2 do you think come over the web 3 everybody seems to be talking about that same thing and then + +Tyler Wright: Yeah not. + +Zach Horn: Yeah, I got it. But an email address is not going to solve that although I do feel strongly about it as well. + +Tyler Wright: Yeah. + +Bold Panther: first + +Denis Lelic: Yeah. + +Zach Horn: Okay, let's do this because this go ahead push and I'm curious what you think as well. + +Bold Panther: So I think there is a lot of our lab between the support page and the contact page that we are thinking. So what here we can do is we can create a common contact us page which has all the support elements like we mentioned with proper cards for reaching out on Discord. There is an explanations and also another social profiles and for business developments as Tyler said we can have a small section where people are looking for business development Partnerships and all the form. So the state we can have a dedicated page for reaching out on socials and more like dedicated things. We can have small sections in here we can have just business development for the needs technical support and all we can just mention the socials that we already have and by inside this and gods + +Tyler Wright: Fish I think that makes sense to Zach's point. Maybe we should just spend a little bit of time mapping it out in the comments section here. I know that Denis has been busy and I know that have the structure of the site down. So maybe this is something that you can like kind of loosely again. This is probably gonna fall lower priorities and some of the other issues I have in here, but when the time is right, you can kind of map it out and we can have a discussion here. My only feedback is I believe that currently is a form and there was push back on the form is too many questions, So again like to Zach's point, maybe this is not something that we should be trying to prioritize because there's so many + +00:20:00 + +Tyler Wright: Something that seems seemingly is so easy to overcome things to be like a challenge for the audience that we're going after. + +Zach Horn: One thing… + +Denis Lelic: better but + +Bold Panther: should + +Zach Horn: what type form is even being referred to here. I'm on the home page of the website now. + +Tyler Wright: So this might be something we have to think through a little bit more over a period of time. So that I was trying to look for that last night. + +Zach Horn: Good. Yeah. + +Tyler Wright: would say if you have any thoughts about But yeah,… + +Tyler Wright: the support page and maybe the contact page come together drop those in here and I don't know. + +Tyler Wright: + +Zach Horn: So let's do this. + +Zach Horn: Let me take a run at this internally… + +Tyler Wright: maybe even do support some with some figma files… + +Zach Horn: because … + +Tyler Wright: because I know that again you have design resources on your team. + +Zach Horn: it's not getting into it on this call. But anyway, I'm not even sure what type form is being referred to here. + +Tyler Wright: I think Denis is working nine million things ahead of Akash accelerate… + +Zach Horn: And if you look on the home page. + +Tyler Wright: but unhappy to slow this down over next couple of weeks and… + +Zach Horn: We have joined the community with four links to channels to contact us. So yeah,… + +Tyler Wright: think it through more fully and… + +Zach Horn: let's just vet this internally a little bit. Let's slow it down for the moment. + +Tyler Wright: just have more time to think about it. Yeah. + +Zach Horn: It's a good idea, but we need to just be clear about how it gets implemented. + +Denis Lelic: Yeah, one thing regarding that feedback, I kind of laughed because whoever said that we've been trying to reach you for months, + +Zach Horn: Right, right. That was my thought as well. It's like, you've been trying to reach us for months and there's multiple contact channels right here. I mean that speaks to let me stop myself before I go too far. Yeah. + +Tyler Wright: Yes that I were all the same page there. That's why I keep on saying the web 2 audience seems to not be able to hop over a simple hurdle or… + +Zach Horn: Yeah. + +Zach Horn: … + +Tyler Wright: at least some folks that we heard from + +Zach Horn: web 2 but here's a link to Twitter right here. Do you know what the DM feature is, have you heard of that and want to anyway,… + +Tyler Wright: Yeah, yeah. + +Zach Horn: let's table it. + +Denis Lelic: Wait until they hear about crypto wallets. + +Zach Horn: Yeah, I'm with just it's a good idea. I do get that some people are just more comfortable with email and that's totally valid. We should solve for it, but This is I mean man, we have some high priority things on the table. So it let's just slow roll it for a couple weeks. And once we get back from a consensus, let's figure out how to do it. + +Denis Lelic: Agree, and I agree with Tyler and maybe we just keep this discussion alive here and under this issue If you have time in research to drop some ideas, I'm gonna have a look at this thing as well. + +Bold Panther: If you guys don't mind can I so I'm pretty much aware about … + +Denis Lelic: + +Bold Panther: the issues so it could be great if I can share other CNN share some of the study paid for the other issues. Welcome. + +Denis Lelic: Yeah, sure. + +Bold Panther: So yeah, I'm sharing machine. + +Bold Panther: So these are the two issues that is being opened by a type one is related to a little relevantages of shares for streamlining the first language understanding of integration with Akash Network. Another is a simple yet meaningful explanation could apply hello Industrial in five minutes or less with Some mentions on the blocks. So accordingly I prepared some visuals like how we can implement this. So on the docks on page we could have this quick start section where we just create two tiles how to integrate with the cost Network referencing a cost. Yes, and secondly deploy hello world is still in five minutes or less. So with the explanations, so I just want to get something back on this what you guys think about this. + +Tyler Wright: I start menu. I don't know how it differs from Essentials. But I guess it's faster. I can give some perspective on these if anybody needs those and why I created them if that helps. + +Tyler Wright: Okay, on how to integrate with Akash, there's a number of projects that reach out to us all the time and say that they've looked at our documentation and our Akashi, s is a repo and that's how a number of folks are integrating with Akash are also using Akash API. But it's not readily accessible on how they can integrate so that they have to have a conversation with us and then they find out about Akash and then they have to go back and do some due diligence to get up to speed and usually it's everything that they need. So we have a number of projects that are building or integrating with the Class via that way I'm not sure this necessarily needs to be on the home page. I actually liked what PS is put together. So I'll say that my personal opinion is I like those two tiles on the home page, but my thought process for this page was + +00:25:00 + +Tyler Wright: + +Tyler Wright: Just a page and documentation that somebody can see and… + +Bold Panther: just + +Tyler Wright: it's just simple copy, we kind of talked about some documentation where we have some header Pages. Whereas it's like if you want to be a provider and this is something more rely on Zach for just a higher level copy that leads into more technical copy, but it'd be great to have a page and documentation. That's just like if you are a project that's looking to integrate with Akash and leverage, deploy or be able to build providers. Here's how a number of projects are doing. They're using akashias repo. Here's They're using Akash API. Here's how you access it. And so now we maybe don't follow up with us. They just know they can go to documentation and This is the next steps and then they can go into specific channels and Discord or they can reach out to us for further help. So that was my thought process on the first one. So I'll stop there and then we can talk about the scl and five minutes. + +Tyler Wright: Less Dynasty I have questions. + +Tyler Wright: I love the idea of a case study as I talked to individuals. + +Zach Horn: Yeah. + +Tyler Wright: I always try to push them to. once you're done with the integration, it would be great to do a case study and then obviously our connect on the Zach as soon as possible, but just from a user experience standpoint. I do think a number of Engineers go to the documentation first before they go to other sections of the website to look for this kind of information. So I'm not saying you're just saying it shouldn't live there but at the very least I think some of these elements should live pretty high up in cumeation. easily searchable + +Denis Lelic: Yeah, I think I saw handwren up. + +Tyler Wright: I don't know if Zach had something. + +Zach Horn: No, I didn't but I end up. Yeah, which one of the four of us this gigantic crowd? Yeah. + +Tyler Wright: Okay. + +Denis Lelic: Maybe it was my hand. + +Tyler Wright: Yeah. + +Zach Horn: Yeah, I love I mean just real quick. + +Tyler Wright: and then + +Zach Horn: I case studies are great. I mean that is absolutely something we should be doing on the website even with sections on the website. how other unnamed large Cloud providers do it where they basically service people that are using, their resources and how they're using them and make it super easy to see who's building that's fantastic to be quite honest. It comes down a little bit to a band with issue, but that can be reprioritized. So I would say if we want to get into that. we just need to decide how that's what the team. Because everyone's just pressed for time. + +Denis Lelic: Yeah. + +Tyler Wright: Yeah. + +Denis Lelic: If you want to share anything else. + +00:30:00 + +Bold Panther: No, I don't have anything specific right now. + +Tyler Wright: I + +Tyler Wright: So this is the second issue based upon I guess feedback that members of the core team have talked about previously again. I think there's a number of on the website, but it'd be great to have a one-pager and maybe that also has a video in it. That's just like here's how you deploy and it will give you how to deploy via CLI with a couple of commands and then also give you how to deploy via the console maybe with a video and hopefully I'll make it very very easy for new users to in a couple of clicks be able to at least deploy hello world, and then they can just + +Tyler Wright: Scale up from there. I know it's something we previously had on the website. We previously talked about in five minutes or less. I don't know if we want to use that language. I leave that up to the content King Zach, but this is just an idea that I think should just be more prevalent and just an easier guide for new users. Just here's how to do the simplest thing. And quit very quickly and then people can scale up from there. + +Zach Horn: I agree with that. Yes, we should do that aside on a lighter note with all these titles, content King, not to derail, but kings an ancient way back Louie the 15th or whatever they'd have 15 titles. That's a little bit what I feel like it's like head of marketing content King, give me some more I'll take as many titles as I can get. + +Tyler Wright: Will do. + +Zach Horn: anyway Yeah. + +Tyler Wright: Good. + +Zach Horn: No, I agree with that point. + +Tyler Wright: Peers I would say this is higher priority than that contact page by a significant margin, + +Bold Panther: So yeah,… + +Zach Horn: Yeah. + +Bold Panther: this looks great. So for Hello World Series or something that we can do for the cost. Yes. I need someone who is working with akashias for long so will be easier basically we need a proper explanations of how to integrate with the cost using and all if someone is working with the costumes And can create something a proper content would be great for this section. + +Tyler Wright: but Yeah, I will have so maybe one the first one to yourself and I'll sign the second one to somebody else. assign the second one to me, I guess and then I will sign to somebody else. But if you can assign that one to yourself and prioritize this page, that would be stupendous because again, I know this is something that works members of internal team if we can update this and make it quite easy. Yeah. There we go, then yeah, that'd be great. And I have no problem with that quick start menu, but it may be if you're very Fast in being able to make those changes which would be great. Maybe we could just add it to the essentials tab for now because it seems like there's one area that's open. + +Tyler Wright: And maybe we could put what is Akash Network and then move the sdl down to and with tokens and wallets and then we can just move how to deploy in five minutes or less, to that top block. I wasn't preparing my screen the entire time,… + +Bold Panther: yeah, + +Tyler Wright: but I think you know what I'm talking about. + +Bold Panther: Yeah. + +Bold Panther: purpose Then we have this issue. + +Tyler Wright: I'll go ahead. + +Bold Panther: So it's all here for the past issues. + +Tyler Wright: Yes. I was gonna bring up a new issue that I'm gonna create but we talked about previously so you go ahead and I'll just add that issue. + +Bold Panther: So this is something that is created by 0 so, implemented some more effects on we have the taste. So I requested the feedback from him. He also provided the link probably so. The holy we affects are previously we had the red as you can see when I over it becomes said it was not there for the state say implemented the thing for this year. So + +Bold Panther: so probably as link is not on the latest one but implemented the whole effect for these three icons and also the icons for the putter. So this is something that will be more. So when I work as you can see the color is not changing to red as some like this one so it will be something that is implemented. So it will be most soon to the + +00:35:00 + +Denis Lelic: Is that something he just? done self-initiated + +Bold Panther: Yeah, he initiated this thing. Yeah. Then this is something that is spending from Tom. + +Denis Lelic: Okay, that's nice. + +Bold Panther: So accessibility that is So it's also pending so we will just have to provide the graphics. So as we can see. in it + +Bold Panther: So engineer dogs, there are some graphics which are not that great. the text can be improved a bit to increase the visualization issues. So yeah, I'm working on it. I will provide the graphics to you update it. so I think We did it here for one. + +Denis Lelic: an article + +Bold Panther: So yeah, I will check over it. + +Denis Lelic: cool + +Bold Panther: This is something that is on the discussion. So this is something that has been created by so the issue was this + +Bold Panther: When we go to the docs and when we click over it, it's not opening any of the pages. So the solution was this which is being a bring up by Tom that when we click over this it should open up the first page automatically like this. So when I click on get started Edition automatically open the cost of the first page similarly when I open up the drop of any of these drop down, let's say providers. It should automatically open the first page that is this instead of clicking on sale drops around that we have so I think this is a great improvements and the US governments and I think hero worked on this issue and there are few books that I noticed in history. So I'm fixing those issues. There are issues in each the other day not least one of the issue was like When we are on this page. and when we will clicking the refresh button it was + +Bold Panther: Making the dogfish widely for it was taking the dog space to the default version that is homepage, which is not the case in the current version. So these are few shoes to they were two books in his PR. So I'm just fixing those books and most accordingly As you can see this is the pr that has been created. So it's under testing and we are testing internally before merging it to the official site. now other issues are kind of like Okay, this is something that is also being updated by Hero. + +Tyler Wright: I think that would be a great Improvement. + +Bold Panther: As you can see like it… + +Tyler Wright: I know we talked about it here and… + +Bold Panther: what they show us stated by energy to add this traffic. + +Tyler Wright: cs. thank you pierce and… + +Bold Panther: So he created the pr And I requested the feedback from Android and Yeah. + +Tyler Wright: let us know if you need anything before merging that would be amazing. + +Bold Panther: he provided some of the feedbacks and… + +Denis Lelic: A one more thing. + +Bold Panther: accordingly hero iterated. + +Denis Lelic: Would it make sense to invite hero to these meetings? + +Bold Panther: so I think + +Bold Panther: Right now I also requested few of the changes that. He probably just fixed and I will just recheck the issues and after finalizing things that we have will be much so, Yes, probably he missed out on meeting. I notified in that meeting is happening. So, let me see the message again. + +Bold Panther: + +Tyler Wright: Here previously and… + +Bold Panther: that's all. + +Tyler Wright: he knows that they exist. I think he's sometimes doing some other stuff… + +Bold Panther: son + +Tyler Wright: but I keep in contact with them a number of times during the week and… + +Denis Lelic: cool + +Tyler Wright: I know I can continue to get more involved so We'll make sure that if he can he comes to Future meetings. I know he' Maybe has a couple of languages. There's a maybe better able to communicate via messaging, but I'll ask them to join. + +Denis Lelic: Cool, It's just nice to see people getting involved in these issues and + +00:40:00 + +Denis Lelic: communities growing cool + +Bold Panther: yeah, so yes also here is everyday brings me up in the morning. So because about the issues that are pending so I don't guide them that you can work on this issues and all and then after he creates a PR there is a constructive feedback within our team also the court sometimes in this case, so I try to make sure that everything is properly done before getting it most of the site. So yeah, I'm also I would all say Heroes predictive a daily in contributing to the cost Network site or possible weeks. + +Denis Lelic: Okay. + +Denis Lelic: I think with touched some of these issues in our previous sessions, so hopefully when this accelerate thing is behind us, I'm gonna find some more time to go through this issues and just provide assets and whatever it's necessary. so + +Denis Lelic: yeah, I think we went pretty much through the whole thing. Unless you want to talk about something else. + +Zach Horn: Nothing on my side. I think we're pretty good. + +Bold Panther: just + +Denis Lelic: cool Okay, cool. + +Tyler Wright: Me too. Thank you all. + +Bold Panther: So there was no issues. So that was talking about we will create an issues. + +Tyler Wright: Yeah, I'll create Offline and then I'll drop it in Discord. It's just an issue we talked about previously related to making updates to the console page. I believe Thomas is going to work on that. But if Thomas doesn't have the bandwidth and I'm just gonna Outsource it to somebody else in the community. And again, we just have to pull images from + +Tyler Wright: a new beta version which I'll give folks access to but should be very quick and easy. And that's his life right now. But I'll create an issue for that and I thought with Thomas if Thomas can't handle it then again. I will see if anybody else from the community can handle it, but we'll look to get that done over the next couple of days. + +Denis Lelic: I was good. + +Tyler Wright: All… + +Denis Lelic: Okay, cool. + +Tyler Wright: y'all. Yeah,… + +Denis Lelic: Thanks for joining. + +Tyler Wright: thank you very much. Enjoy these meetings. I'll talk to you all in two weeks. If not before async,… + +Bold Panther: have + +Tyler Wright: but let me know. If you have any questions about the deploy in five minutes, and we can just keep that pushing. + +Bold Panther: So yeah, I will let you know. + +Tyler Wright: awesome Thank you. + +Denis Lelic: Thanks guys. + +Zach Horn: Thanks guys. Take care. + +Bold Panther: Thank you. + +00:45:00 + +Tyler Wright: We're getting a tourism. + +Tyler Wright: Thank you. + +Tyler Wright: Boy owner has something to say. Good. + +Tyler Wright: for seven years ago, but he was setting what your deal so + +Tyler Wright: in a salary so retain ing Bird, right but after this agent also representing Kevin Garnett baptisms He is full condition from that contract and that is how the contract Behavior. As a result the commission. ER David sturt to spend a typical + +00:50:00 + +Tyler Wright: art one year. He also find the team. 3.5 million dollars and most importantly presentation of or other next five first round draft picks completing the franchise building a championship and around that just as he was entering the proud of his. + +Tyler Wright: I + +Tyler Wright: put the savior. + +Meeting ended after 00:53:23 👋 + From 9ea6e1694d084742a74b7b3c7edcf2102138fb73 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 12 Jul 2024 21:10:57 +0000 Subject: [PATCH 102/138] Create meeting notes for wg-zealy #12 (#593) * Create meeting notes for wg-zealy #12 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 012-2024-04-29.md add recording link and transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-zealy/meetings/012-2024-04-29.md | 268 ++++++++++++++++++++++++++++ 1 file changed, 268 insertions(+) create mode 100644 wg-zealy/meetings/012-2024-04-29.md diff --git a/wg-zealy/meetings/012-2024-04-29.md b/wg-zealy/meetings/012-2024-04-29.md new file mode 100644 index 00000000..6ec58acd --- /dev/null +++ b/wg-zealy/meetings/012-2024-04-29.md @@ -0,0 +1,268 @@ +# Akash Network - Zealy Working Group (WG) - Meeting #12 + +## Agenda +- Discuss current and upcoming missions. +- Resources for mission creation. +- Share some analytics and community growth data. +- Discussions on potential continuation of the program and the process for securing further funding. + +## Meeting Details +- Date: Monday, April 29, 2024 +- Time: 6:00 AM PT (Pacific Time) +- [Recording](https://rfo5d4qnnddwhhwyncat6u6gjone7ohuotiv6op3rvzu3va5glpq.arweave.net/iV3R8g1ox2Oe2GiBP1PGS5pPuPR00V85-41zTdQdMt8) +- [Transcript](#transcript) + +## Participants +- Benjamin B. +- Robert Del Rey +- Tyler Wright + +## Meeting Notes +- The meeting focused on the progress of Sprint #2, plans for Sprint #3, and existing missions rolling over. + +**Key Points:** +- **Sprint #2 Recap:** + - Sprint #2 ended on April 27th. + - Benjamin will review and export the leaderboard data to determine the winners. + - Sprint #2 had fewer missions, resulting in fewer points compared to Sprint #1. + +- **Sprint #3 Overview:** + - This will be the final month of the initial campaign. + - Decision to extend or end the campaign will depend on the results. + +- **New Missions for Sprint #3:** + - **Text-to-Speech (TTS) Solution on Akash:** + - Inspired by a question on Akash Discord. + - Similar to the deployment of Lama 3 on Akash Network. + - Encourages users to deploy TTS solutions for rewards. + - **Content Creation Mission:** + - Create a 10-15 minute video on the history of cloud computing and Akash's role. + - Only one winner, potential to feature the video on Akash EDU. + - **GitHub Discussions:** + - Unpaid mission to teach users how to create discussions on Akash GitHub. + - **Akash Bounties:** + - Overview mission to direct users to Akash bounties on Discord. + - Unpaid mission. + - **Newsletter Subscription:** + - Template mission to subscribe to the Akash newsletter. + - Unpaid but offers XP points. + +- **Existing Missions Rolling Over to Sprint #3:** + - **Deploy Persistent Storage on Akash:** + - Helps users interact with Akash using any available hardware. + - Initially launched in Sprint #1, rolled over due to time constraints. + - Some providers have not set up correctly and are not approved. + - **Provide Compute on Akash:** + - Similar purpose and feedback as the Persistent Storage mission. + - **Join Akash Insiders:** + - Unpaid mission to join Akash Insiders, with 7 people clicking the link. + - **Invite Friends to Akash Zealy:** + - Unpaid mission, rewards XP points, involves inviting friends to join Akash Zealy. + +#### Community Growth and Feedback +##### Robert: + - In the last three months, nearly 300 new members joined. + - After removing initial pilot members, 208 new members were acquired. + - Positive growth trend since March, with increasing community engagement. + - Feedback to Zealy: Improve the quality of analytics provided. + +**Feedback on Program Success:** +- The meeting continued with discussions the success of the initial sprints, the potential continuation of the program, and feedback on program performance. +- Tyler Wright highlighted the success of the pilot and the first two sprints, noting the growth and positive reception. +- Tyler expressed support for continuing the program, suggesting a new funding proposal if necessary. + +**Discussion on Program Continuation:** +- Benjamin B. mentioned previous discussions with Robert Del Rey about continuing the program and seeking additional community funding. +- Robert Del Rey asked about the process of reopening threads on GitHub for proposal discussions. +- Tyler Wright confirmed that new proposals should be made for each new period and suggested referencing the old proposals in new threads. + +**Community and Leadership Support:** +- Tyler Wright conveyed strong community support for the program and endorsed the leadership's efforts. +- Robert Del Rey and Benjamin B. appreciated the support and expressed their satisfaction with the program's progress and their collaboration. + +#### AI Video Submission: +- Robert Del Rey shared a short AI video submitted to YouTube, promoting Akash Network. +- The video highlighted the concept and benefits of the Akash Network, presenting it as a revolutionary decentralized cloud solution. +- Tyler Wright and others reacted positively to the video, finding it exciting and effective in promoting Akash Network. + +**Budget Allocation for Sprint #3:** +- Benjamin B. suggested allocating additional funds for larger missions due to an unexpected donation from Greg. +- Estimated spending for Sprint #2 is around 300-350 AKT, final review pending. +- Robert Del Rey agreed to include the equity paid in rewards in the next community update. + +**Mission Ideas and Branding:** +- Tyler Wright suggested incorporating the "super cloud" concept more prominently in missions, especially in video content. +- Tyler highlighted the importance of clear branding to differentiate Akash's offerings beyond just GPUs. + +**Next Steps:** +- Tyler proposed discussing the leftover funds and potential mission extensions in future meetings. +- Tyler will follow up online and be available for further discussions in the Zealy channel. +- Tyler will participate in future discussions and provide further input on mission extensions and budget allocation. + +**Conclusion:** +- The meeting concluded with positive feedback on the program's progress and a commitment to further discussions and improvements. +- Participants expressed satisfaction with the direction of the campaign and the collaborative efforts involved. + +**Action Items:** +- Benjamin B to review and export the leaderboard data for Sprint #2. +- Robert Del Rey to finalize and publish the new missions for Sprint #3. +- Robert Del Rey to coordinate with Adam to review potential content for Akash EDU. +- Benjamin B. & Robert Del Rey to discuss and finalize the details for a new proposal to continue the program. +- Benjamin B. & Robert Del Rey to consider creating a new GitHub thread for the proposal, referencing previous proposals for context. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Robert Del Rey: All Happy Monday and happy labor day at least in Latin America. Thank you so much for joining to this cold life and those listening to the recording later. This is the cash silly working group. by weekly call So here we discuss all things silly. + +Robert Del Rey: and yeah, what's next about really? So, let me jump right into it a sprint number two. Just end it last 27th of April. I haven't seen any of the results, but we have time to check that out. So Benjamin, I will go ahead and go over the leaderboard export the data and see what were the winners for Sprint number two. Yes, I will add now a sprint number two was a bit different than a sprint. Number one, I guess with the fewer missions and that's why you see fewer points than then then the first Sprint. That's okay. You live and learn as I say. + +Robert Del Rey: And today's agenda. I would like to go over the missions. We are thinking about for a sprint number three the third and last month of this initial campaign. Let's see. after this campaign we continue with a few more months or if we just settle this down and move forward with something else. Let's see. The results are gonna speak on that. So let me share my screen real quickly. + +Robert Del Rey: That's quite important people join these calls because you get access to early Alpha. And maybe we prepare for what's coming. So Let's go half a cash, Great. Let me know if you can see my screen Benjamin you. + +Robert Del Rey: awesome Sold the offering we have for these upcoming Sprint It's a combination of New Missions. And existing missions rolling over to this Sprint. + +Robert Del Rey: Dimensions of the top there was a little hype with them during I would say the last week. lo Texas speech Solution on a cache. This one came up for a question that I saw on a cash Discord and I wanted to turn it into a mission and it's very similar to Lama 3 on a cash Network. For those listening now, I'm sure and for those listening to the recording later, maybe you might know you might not know. + +Robert Del Rey: Last week Lama 3 was deployed on a cash Network and CJ. One of the Akash insiders great guy props to him. He posted a small threat guy on how to deploy Lama Tree on a cache and I was impressed man that tweet got over 12,000 impressions. which is huge, so I'm trying to take not some Advantage but Try to use that. + +Robert Del Rey: Try to use that reach and that impression and maybe try to bring some people to deploy Lama Tree on a cache. through silly They come to Seeley. They see the mission deploy Elementary on a cash. They do the mission and they will get reward for it. That's the main difference between the Seagate post and these ghosts people that did it using the CJ guide didn't get anything. So on a cash silly people will be able to get some prices to the employer TTS solution and deployment through on a cash Network, which is almost the same as kind of two for one mission in my opinion. let me see here some people join the call. Hey, Tyler welcome and happy Monday. + +00:05:00 + +Robert Del Rey: Literally good man. No worries. Thanks for joining. We are just wrapping up the Sprint number two, and now going over the missions available for a spring number three just to give too long didn't read. So let me continue then this mission is cool. This is the attached document or this is the only content creation mission that we're gonna have during a sprint number three. and this one is about content this one is about creating a long 10 to 15 minute video. Talking about the history of cloud computing and what is the role of a cash Network in this market the cloud computing Market? + +Robert Del Rey: There is only going to be one winner for this mission. Which I believe is going to help us getting the best content. Hopefully the winners submission. + +Robert Del Rey: Hopefully know what I'm planning to do with the winner besides giving akt price. I also wanted to talk with Adam to see if the video is good enough. Maybe we can use that same video to add it to a cash EDU. Used to give a little context. I cash edu. It's like a beer tall platform. So people can get education about a cash and having a video about the history of cloud computing and a cash role in it. I think it's a pretty nice piece of information depends on the submitters. Let's see what the submitters come with. So moving on take it to GitHub. This mission is on paid. No rewards for this mission. + +Robert Del Rey: Because I want people to learn what is the process of creating a discussion on a cash GitHub? how the mission look like Is that you have the link you have the best practices and the mission tells you you want to create a listing proposal. You want to Market in proposal you want a funding proposal you want an x y c proposal take it to GitHub. And in the mission, the people will see the steps to create a discussion that's gonna be an unpaid Mission, but hopefully we can Teach people coming to see how to open up discussions and get involved in their cash GitHub. + +Robert Del Rey: And the last of the New Missions is the Akash bounties. This one has the question mark. Because I haven't done it yet. It's just like an idea. And it similar to take it to GitHub. It's gonna be on paid but it's gonna have an overview about the cash bounties and where people can find those bounties. I see it as a complement to the cash Bounty Hunter's channel on Discord. In the last one. Sorry, I jumped over this one. It's the newsletter subscriber. this one is a template that silly has in their page. And you just add the link. So people can subscribe and people just add the link and they subscribe to whatever newsletter you want them to subscribe. So I added the cash newsletter link to the mission. + +Robert Del Rey: and people that want to get up to speed on a cash can subscribe from the newsletter and do this Mission? It's gonna be unpaid but it's still people gonna get XP points to do them missions. And yeah, those are the new offering we're gonna have on a Sprint number three before I go to the existing missions rolling over to a Sprint number three, are there any questions so far? + +Robert Del Rey: All right. I see a thumbs down. I'm gonna take that as I know. Give me one second guys. + +Robert Del Rey: All right. so existing missions rolling over to a Sprint number three These two are very popular in my opinion deploy persistent storage on a cash and provide compute on a cash. Yeah, we know a cash is trying to get of the best test hard work. So people bring those to a cash market place, but there are some people that don't have The Best of the Best Equipment, but still they want to get involved in a cash. They want to connect whatever resource they have just to get their feet on the water. so I think this missions + +00:10:00 + +Robert Del Rey: help people get involved without having to think much about the hard work. They need to be a super serious and super profitable provider. so this gives the chance to people to interact on a cache with whatever Hardware they have get some XP points and Main I get paid we launched this mission on a Sprint number one the feedback we have Is that people didn't have much time to do this mission? So that's why we decided to roll it over to In a month number two, if I'm not mistaken, maybe Benji can help me a little bit in this area more people did the mission and actually get to spend a longer time. + +Robert Del Rey: Providing on a cash and having a persistent storage on a cash. I messed up a quick second. Maybe when you want to add something about these two missions that be amazing just for the recording. If not, that's okay. + +Benjamin B: Now I've been looking a little bit on this right now and we've had some providers trying to start. I'm not going to name many people here. But the last person I checked and where they have set up to provider. They haven't done it correctly. So they will not be approved in this Mission. I'm not sure if we've seen money and you providers here, but we've seen quite a few people and crying. + +Robert Del Rey: Got it, Thank you so much. let's see. We have the third and last month. Hopefully more people jumped in. And the other two are on paid missions to it's during the cash insiders so far seven people have click on this link. I don't know if they did the application. I will need to ask Adam. And they invite three friends to a cash silly this one. It's unpaid it gives you XP points though, but doesn't pay you any akt and some people have done it too and not just decided. It doesn't hurt to leave these two open for the remaining of the campaign. + +Robert Del Rey: I have here reminder for the steering monthly call all this I'm just practicing now, right because all this information I'm planning on sharing in the steering monthly call which is gonna happen these Thursday if I'm not mistaken. So the broader Community can know more about what we are doing in the cash, And some stats that I wanted to share with you here. It says the last three months. We had almost 300 members, which I find amazing. If you remove the people we got from the first pilot we did on November December. If you remove that people. you left us with 208. + +Robert Del Rey: members so on month number three a month number two We were able to get 208 new members in a cash City. You can see the graphic here. This is the beginning of March when we started the first Sprint, that's where you can see this we went parabolic, right? And then you can see how we slowly are still increasing in community members. We shall find really cool one very big feedback that I gave Sealy. I was able to speak with them two three weeks ago. And is that this analytics is too poor in my opinion? I've been able to see other kinds of Analytics. + +Robert Del Rey: and I feel somewhat limited with this. So that's something to keep in mind for future discussions the quality of the analytics that we get from Seeley. That's just a personal thought that I'm sharing right now. So yeah, this is the members amount and the top countries where most of the members are based. Which I find really cool. The last time we saw this we had five members from India But now you can see we have nine members from France ate from the Six from Indian Russia and many more this one maybe doesn't say much but I like to see that we are. + +00:15:00 + +Robert Del Rey: How Global this is honestly, sometimes we are in the chat and you cannot believe everybody it's space either on Europe or in the US. and it's cool to see this information. That's why I added here. And some submissions I wanted to share with you and this is too close it out and then we can open up to comments or questions if you have any let me stop present in here. Wow, okay. let me + +Robert Del Rey: I can wear life. Go ahead time. + +Tyler Wright: my only question is it seems like the pilot was very successful. the first three or the first two sprints have been successful and there seems to be a fair amount of growth. I believe we're coming up correct me from wrong, but I believe that we might be coming up on the last or towards the end of this program. if that is in fact the case I would be of the thought process that this is something that should continue on. Have you all thought about Hosting another discussion or just going back to community pool for some more funding or what? That kind of looks like go ahead Benjamin. + +Benjamin B: Thank We discussed this me in Robert's per for you joined them before we started recording. We don't have any details yet, but we can definitely start talking about this topic now and we have plans to Trying to ask the community pool to continue this program, but for the details. We have yet to discuss if you want to make an enlarger changes or anything. Maybe Robert has some ideas. + +Robert Del Rey: Yeah, just to add to that. We were discussing exactly that Tyler before you jumped in like Benji said and something we were discussing is that if we should open up a new thread on GitHub and add the information we have or if we should reopen the original Thread about this campaign that original thread it's close already. Honestly don't know if you can reopen close threats. So I'm honestly asking you. + +Tyler Wright: Yes. Yes, you can I would say maybe make a new thread,… + +Robert Del Rey: Okay. + +Tyler Wright: somewhere away in the past overclock has done proposals for events, and every time it's a new quarter a new period they just make a new proposal. So I just think you can make a new proposal and reference the old proposal. + +Robert Del Rey: Got it. okay. Thank you so much. + +Tyler Wright: But at the highest level I and… + +Robert Del Rey: All right. + +Tyler Wright: many other people within the community that I've talked to and overclock Labs have been very happy with the leadership and with the progress of this program, so I would put one vote in representing Tyler to have you all continue this program. + +Robert Del Rey: Thank you that's great to hear and your support your escort and everybody else has been Super Paramount. Honestly, honestly, Benji and I are super happy. We both learned a lot on this we learned about the work and we also learned about each other and yeah, I'm happy to hear that. You guys liked it and would support in case we want to continue. So amazing man amazing. + +Robert Del Rey: Thank you for your endorsement menu. So the last thing I want to share is just one submission. This is an AI video that someone did. and uploaded to YouTube. It doesn't have many views But just wanted to share it. It's a few seconds long. Let me know if you can see it. + +Benjamin B: I can see. + +Robert Del Rey's Presentation: in the realm of digital Innovation the Future is already here. + +Robert Del Rey: Can you hear to? + +00:20:00 + +Robert Del Rey's Presentation: It's called the Akash Network. + +Benjamin B: Yes. + +Robert Del Rey's Presentation: Imagine a super cloud infrastructure. That's not just a service but a revolution it's about time. We started thinking bigger dreaming Bolder. Our world is becoming increasingly interconnected. And with that comes the need for more powerful decentralized Cloud Solutions. Enter a cash Network a game changer a disrupter. It's the world's first decentralized open source cloud, and it's here to redefine the future of cloud computing imagine. Having the power to run any application anywhere anytime. This is the promise of a cash Network get ready to unlock a world of possibilities where the sky is not the limit, but the starting point Welcome to a cash Network. + +Tyler Wright: Damn, that seemed like a hype video. + +Robert Del Rey: All right. + +Tyler Wright: I got me excited. + +Robert Del Rey: Yeah, yeah, you do feeling me I saw this on Saturday and I was super happy about the video because It goes straight to the point. But at the same time it kind of promotes a cash Network. so yeah, just gonna take sure that with you that is one of the submissions we got in the Sprint number two. So yeah. Yeah, that's all I have for the agenda. We did an overview of the offering we're gonna have for the Communist Sprint number three. The screen number three is going to happen. It's going to start on Wednesday first and go all the way on to I believe it was Monday 27. I got to check that one out. But yeah, we shared the missions. We share some analytics and we also spoke about + +Robert Del Rey: The future of this campaign with that being said, is there anything else you want to add to the conversation guys or any questions comment? + +Robert Del Rey: Go ahead Benjamin. + +Benjamin B: Yeah, I want to say that for the third month. Maybe we should consider having some larger missions we got. a big donation from Greg for their High School, which I'm guessing we're gonna send back to the community pool. unless we use it and we can really try to figure out some great missions we can use that money on because right now the first Sprint we spend approximately the calculator This print I think we spent a little less. and then this third month, I think we should try to overspend a little just because we got some extra funds within calculate for I think we're about 300 to 350 Katie for this Sprint, but I'm not quite sure yet. We haven't + +Benjamin B: reviewed everything yet. + +Robert Del Rey: Yeah, okay. Let's check that out. And if you can… + +Benjamin B: Yeah. + +Robert Del Rey: then just me that info so we can share it in the city in comedical. That is another metric that is good to share the equity paid in Rewards. + +Benjamin B: Yeah. + +Robert Del Rey: So yeah, thanks for bringing that nice catch 30 forgot about it. + +Benjamin B: The Tyler is the other thing, please go ahead. + +Tyler Wright: I have to run to another meeting but I can follow up with you all online again. I think this is moving and the right direction. let's have a sink if there is extra spend left over we can talk about either adding a discussion to say that hey can we extended we'll just keep these tokens and then we can go discussion after that, but I'll follow up with you offline. And there's other one thing I want to talk about is if we can include some Mission especially if it's a video because I really like the way that video is going back. We talked about super cloud. I do think that we need to + +Tyler Wright: mention that more, from a branding perspective. I think it's something that folks that don't understand the caution is called compute Marketing in general and think you got this just have gpus it's a lot more than that. So if we can start to incorporate super cloud, I think that would go a long way. But just hit me up in the zealy channel. If you need me and we can continue to talk there between now and the next meeting but much appreciate you all and I'll follow up with some of you about other items and I'll see you all at steering committee. If not before but let me know if you need anything prior to steering committee, but I'll leave some time for you all as a part of the projects list to talk about zealy. + +00:25:00 + +Robert Del Rey: Thank you so much that you sure Have a nice day, too. + +Benjamin B: Thank you so much for joining. + +Robert Del Rey: All… + +Benjamin B: And with that,… + +Robert Del Rey: All right. + +Benjamin B: I think this meeting is concluded or do you have anything else? + +Robert Del Rey: I don't have anything else to add bro. I'm just the Stoke about how things are going and it's great to hear when a third party like an outsider like Tyler say that things are going good from their perspective. So I think that says a lot about what we're doing All right. + +Benjamin B: Yeah. Super happy to work on this. + +Robert Del Rey: Absolutely, So Benjamin, we're gonna catch up later this week, but for now you see you on the other side. Alright? + +Benjamin B: Yeah. Have a nice rest of your day Robert. See you around. Bye. + +Robert Del Rey: YouTuber stay safe + +Meeting ended after 00:26:03 👋 + From 1c772845dc3e921a026eb9c609483ebd17e0ae7a Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 12 Jul 2024 21:26:05 +0000 Subject: [PATCH 103/138] Create meeting notes for Wg-Zealy #11 (#565) * Create meeting notes for Wg-Zealy #11 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 011-2024-04-15.md add transcript Signed-off-by: Drinkwater * Update 011-2024-04-15.md add recording link and transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-zealy/meetings/011-2024-04-15.md | 171 ++++++++++++++++++++++++++++ 1 file changed, 171 insertions(+) create mode 100644 wg-zealy/meetings/011-2024-04-15.md diff --git a/wg-zealy/meetings/011-2024-04-15.md b/wg-zealy/meetings/011-2024-04-15.md new file mode 100644 index 00000000..26f93a89 --- /dev/null +++ b/wg-zealy/meetings/011-2024-04-15.md @@ -0,0 +1,171 @@ +# Akash Network - Zealy Working Group (WG) - Meeting #11 + +## Agenda +- Zealy Updates +- Sprint #2 Progress and New Mission Brainstorming +- Zealy Q&A Session Recap +- Collaboration with Ahara and Zealy API Integration +- Platform Feedback and Suggestions + +## Meeting Details +- Date: Monday, April 15, 2024 +- Time: 6:00 AM PT (Pacific Time) +- [Recording](https://bddlwy5cp5qgwpvbfyvqq255oa6uprp2xtxdhpplr5k7syqvd2qa.arweave.net/CMa7Y6J_YGs-oS4rCGu9cD1Hxfq87jO9649V-WIVHqA) +- [Transcript](#transcript) + +## Participants +- Robert Del Rey +- Tyler Wright + +## Meeting Notes + +### Discussion Points: + + +#### Robert +- Zealy Rewards for Sprint #1: + - 97% of rewards paid out, reminder to claim by the deadline. +- Sprint #2 Progress: + - Review of current missions and brainstorming new ideas. +- Zealy Q&A Session: + - Positive feedback received, suggestions for new missions. +- Collaboration with Ahara: + - Discussion on Zealy API integration for community apps. + - Requirement to complete at least one Zealy API Quest for feature. +- Platform Feedback: + - Request for analytics by Sprint and mission-specific stats. + - Suggestions well received, awaiting updates from Zealy. +- Mission Suggestions: + - Consideration for more complex Python-based web app missions. +- Newsletter Mission Template: + - Template available for newsletter sign-up mission. + - Zack may find this mission beneficial. +- Next Working Group Call: + - Scheduled for April 29th before the start of the second Sprint. +- Zealy Feedback: + - Waiting for response on platform feedback provided. + - Focusing on new missions for upcoming Sprint. +- Clarification on Zealy Quest vs. Hackathon Track: + - Quest seeks prototype for Fiat to Akash conversion. + - Hackathon track has specific guidelines for Fiat on-ramp. + - Emphasized differences in objectives and rewards between the two. + +**Tyler Wright's Input:** +- Acknowledged the progress and momentum in the program. +- Suggested getting an update on activities for the upcoming steering committee meeting, possibly rescheduled to May. +- Encouraged promoting hackathon participation, including from the Zealy community. +- Expressed satisfaction with the Zealy program's direction and eagerness to increase community engagement. + +**Robert Del Rey's Response:** +- Agreed to provide a comprehensive report for the steering committee and monthly community calls. +- Committed to sharing data on community growth and Sprint results. +- Appreciated Tyler's input and commitment to community engagement. +- Encouraged further questions and discussions through the Akash Silly Working Group chat or direct messages. +- Wished everyone a productive week and urged to continue the momentum. + +## Action Items: +- Robert to prepare comprehensive report for upcoming steering committee and monthly community calls. +- Robert to follow up with Zealy regarding requested platform updates. +- Further discussion needed on implementing more complex Python missions. +- Consider recording future meetings for reference. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Robert Del Rey: Happy Monday. a cash community I hope your weekend was fine. And welcome to the Akash silly working group call. Today's agenda is a picture. Mostly we'll cover some updates about things we did last week. Things we want to do for the remaining of the month. + +Robert Del Rey: and yeah in our objects about silly. + +Robert Del Rey: Since this school is going to be short and Only me. The good thing is we're gonna have the recording and transcript or everybody to catch up later. + +Robert Del Rey: So silly updates the rewards for the first Sprint. Have been paid. I believe only three four winners playing their rewards yet. They claim window and that last Friday the 12th. so if you didn't claim suddenly you will lose those Rewards. + +Robert Del Rey: So the claiming window is close. Hey Ty GM. + +Tyler Wright: M how are you? + +Robert Del Rey: I'm doing good. I just started the recording honestly and was just covering silly updates. So you haven't missed. + +Robert Del Rey: How you doing? How was your weekend? + +Tyler Wright: Not bad at all. Yeah, but real complaints. How about you? + +Robert Del Rey: Awesome, That's good to hear my weekend. I changed the office today as you can see. I'm sitting in the living room now. But my weekend was okay. + +Tyler Wright: excellent + +Robert Del Rey: Man, I went to the groceries. And I bought some more lamps to the house. Hopefully I get them installed this week, but not much action, honestly. Besides that as far as my personal life goes,… + +Tyler Wright: + +Robert Del Rey: right the crypto Market was full of action this weekend as I can see lots of volatility, But yeah man happy we live to fire another day. + +Tyler Wright: Yeah, yeah exactly. + +Tyler Wright: exactly + +Robert Del Rey: So yeah, as I was covering rewards for versus Sprints were paid 97% of the rewards were paid only for people playing their Rewards. moving on a Sprint number two Benji and I shot it this last week about how the current missions are doing. And we also bring storms some ideas for upcoming missions. + +Robert Del Rey: Last week we did something new. We had the first silly Q&A session. We had a last Friday and we wanted to have a space where people can come in and ask questions and overall sure the experience they have with Sealy. We had some inputs by recommunity members some of them suggested New Missions some of them wanted missions from the first months to be in this month. and overall. It was really cool here in them and how they feel about this. so yeah. We're working on getting some more New Missions So That's it. Again, it was very fruitful at first. It was only Benji and I but then more people trickle in. + +Robert Del Rey: And it was fruitful for all of us. Some things we got sorted out list this last week ahara called with the silly team. To ask some questions about collaboration between communities. And they provide us some things we can do. They have the silly API documents. and in a nutshell basically you can integrate Seeley with your apps how in a way that you can make people interact with your apps and I will give them XP points and stuff. So basically they tell us if we want silly to feature us we have to do at least one Seeley API Quest + +00:05:00 + +Robert Del Rey: Showy case showcasing how we are using silly in our community. So Benji and I are still shaping that up. Let's see how that goes. But that's the main update we got from Seeley. I also share some feedbacks about using the platform. For example. One is the Analytics. I can see all the analytics all time the last three months the last 30 days and the last seven days. But I'm not able to see the information by a Sprint. For example, if we did the first Sprint and we want to see the analytics only for that first Sprint that is not possible in the current analytics settings. So I share that feedback with them they liked it and they told me they will get back to me on this… + +Tyler Wright: What? + +Robert Del Rey: but they really like that feedback seems nobody suggested it before. + +Tyler Wright: how are you? + +Robert Del Rey: How am I? + +Robert Del Rey: it's okay. I thought you were asking me how am I I'm good, by the way, I'm good. + +Robert Del Rey: But yeah, as I was saying seems nobody suggested it before hopefully they get back with me this week. another feedback that I had is that when we click on the missions to have a specific info on the missions. It's not possible to see how many people did Mission In detail, I'm not able to see that I only can see all the people that did all the missions but I'm not able to see a stats by missions neither. So that was another feedback that I gave them and they were kind of surprised of that. But yeah, yeah still lots of learning even though we're almost two months in these official campaign. I still were learning by we're doing this. anyway + +Robert Del Rey: So that's all I have for the agenda. Honestly the updates we did the catch-up calls. We had last week the Q&A session. We had the last week. and the guidance about current missions and getting some ideas for New Missions and existence. For example, one of the missions that people want us to bring back is create web app using python. The first mission in the first Sprint was really Just create a simple web app, but two guys in the community were asking for something more complex to do but I still + +Robert Del Rey: up They wanted something more complex to do is still on python. So they still want to try things on python but a bit more complex than just creating the web application and deploying it on a cache. So we're still trying to figure out how is that going to look like? But yeah again, it was a really nice call. initially. We wanted to be 30 minutes in the call and we extended it for an hour and five minutes. We didn't record it sadly. But maybe next time. So yeah, yeah. yeah, that's all I have for now. I was chatting with Benji sadly. He won't be able to join this meeting. He is actually getting super busy with the providers audit stuff. + +Robert Del Rey: I'm also super easy with the cash hackathon that is going full esteem. So yeah, yeah. that's that on the silly GitHub. I was able to speak with George Tyler and I believe he's been helping me updating the calls and adding the call notes in the silly GitHub repo, which is super welcome. Thank you George for your help. And by the way, Sac were asking about the emails and the newsletter and stuff. There is a mission template to request just that sign up to our newsletter. and it's information with a text box where people just need to input their email and + +Robert Del Rey: and we can see that email and sign them up in whatever newsletter. We're offering but they have a mission specific for that. I believe Zach is gonna like that mission. Other than that, yeah, that's all I have again really short maybe for the attendance, but still I'm happy we're recording this so people can catch up with this later on. The next working group call we're gonna have it's right before we and the second Sprint and that's gonna happen this month April 29th the the same place. + +00:10:00 + +Robert Del Rey: So with that being said Tyler if you don't have any questions, I don't have any other update to give what I will work in this quick. Like I said is if silly comes back to me with this feedback I gave them. If not, that's okay, working in the New Missions for the third and last Sprint we're gonna have a combination from Miss. We had in the first Sprint and meet a new missions ideas we plan to do on this. Third coming up Sprint one thing I want to clarify and this is a bit of topic. This is something I was sharing with Adam offline because we have a silly Quest that is kind of similar to one of the hackathon tracks. There is a Fiat. + +Robert Del Rey: Sorry Sorry Fiat wakash on ramp track on the hackathon. and we have a Fiat to a cash silly Mission. So I thought I add them the main difference is that In the silly Quest we are just asking for a prototype. Doesn't matter how you do it. If you find a way to do a Fiat on ramp that helps people buy akt using your credit card. Doesn't matter if it looks ugly if it looks good. + +Robert Del Rey: If it works that is what we're looking for in the Q&A session, actually, we clarify to the participants that it's open to them how they want to reach that goal. However, the difference with the hackathon is that you have some very clear guidelines on how the cash Community wants distract to be completed on the hackathon. So I believe that that is the main difference. That is what I explained He understood completely so if you thought there was conflict in those missions there is not They are similar in name, but they're requesting two different results, honestly, and also the required it's way low in the hackathon. You have three rewards, I believe it's 5,000 10,015,000 for the Sealy. It's gonna be only one winner and it's gonna be only 250 akt + +Robert Del Rey: which is like + +Robert Del Rey: like a thousand something dollars with today's prices. So yeah. and I believe that is the last meaningful of date I can give you right now. I don't know if you have any extra comment or something outside the topic you want to share with me. If not, I guess we can call it a call for today. I should say. + +Tyler Wright: Yeah, no. No, I think you're doing a great job. It sounds like there's a lot of momentum. The only thing I would say is maybe as we prep for the next steering committee meeting. It'd be great to get an update on all thank you all doing that might get moved from the last week of April to the first week of May. But again, other than that, it's just you all are doing a great job. So Yes, many people as we can push towards the hackathon even from zealy would be great because it's like additional opportunities to get involved. But overall. I know I'm very happy with how the zealy program is being run and how it's moving forward. So excited to continue to get some of those folks from zealy more active in the community and more engaged. + +Robert Del Rey: Thank you so much I'll make sure I have a good report for you guys in the steering Community called in the monthly sitting Community called because it's good that Maybe I can bring to you The total amount of community members, we have the new community members we have after we started the Sprint so we can get the pile of the pilot data out because we shared that I believe one or two months ago and I can just share with you the results from a sprint number one and a sprint number two. And you can stay up to speed on that one. + +Tyler Wright: That would be perfect. + +Robert Del Rey: So that's gonna be my homework from this call. Okay? + +Tyler Wright: But that would be perfect. + +Robert Del Rey: Awesome Thai thank you for sharing this time with me And also for those listening to the recording if you have any questions, remember, the place is their cash silly working group chat. If not, you can also send me at the end directly having more than happy to answer all your questions. And with that being said I just wish you an excellent start of the week. And yeah, let's keep on hunting. All right. + +00:15:00 + +Tyler Wright: Thank you, Robert. + +Robert Del Rey: Thank you. Bye. Okay. See you around man. + +Tyler Wright: All right. See you around. + +Meeting ended after 00:15:44 👋 + From e40163f26e74ef55bf5828f8377795bc6a0af434 Mon Sep 17 00:00:00 2001 From: Robert Del Rey <97957244+instafinanzas@users.noreply.github.com> Date: Fri, 12 Jul 2024 17:28:15 -0400 Subject: [PATCH 104/138] Create Zealy WG Call 2024-03-04 (#509) * Create Zealy WG Call 2024-03-04 Signed-off-by: Robert Del Rey <97957244+instafinanzas@users.noreply.github.com> * Update 2024-03-04 update structure of transcript. Signed-off-by: Drinkwater * Update 2024-03-04 Signed-off-by: Drinkwater * Update 2024-03-04 update date. Signed-off-by: Drinkwater --------- Signed-off-by: Robert Del Rey <97957244+instafinanzas@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-zealy/meetings/2024-03-04 | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 wg-zealy/meetings/2024-03-04 diff --git a/wg-zealy/meetings/2024-03-04 b/wg-zealy/meetings/2024-03-04 new file mode 100644 index 00000000..12a76098 --- /dev/null +++ b/wg-zealy/meetings/2024-03-04 @@ -0,0 +1,25 @@ +Akash Network - Zealy Working Group (WG) + +# Agenda + +- Mission prize rebalance +- Extra funding +- Campaign stats +- Social Media outreach and posts + +## Meeting Details +Date: Monday, March 4th, 2024 +Time: 6:00 AM PT (Pacific Time) +[Recording]) +[Transcript](#transcript) + +## Attendees + +Benjamin B, Joe Deng, Robert Del Rey, Rodrigo Rochin + + +# **Transcript** + + + + From 71df56c07a6b6acb7faf84b4089d15fdcdaf308f Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Thu, 18 Jul 2024 13:51:32 +0000 Subject: [PATCH 105/138] update readme tables (#628) July-readme --- sig-chain/README.md | 8 ++++---- sig-clients/README.md | 2 +- sig-community/README.md | 8 ++++---- sig-design/README.md | 13 +++++++------ .../{016-2024-05-08.md => 017-2024-05-08.md} | 0 .../{017-2024-06-12.md => 018-2024-06-12.md} | 0 sig-providers/README.md | 2 +- sig-support/README.md | 2 +- wg-akash-website/README.md | 4 +++- wg-provider-audit/README.md | 2 +- wg-provider-audit/meetings/001-2024-02-21.md | 4 ++-- wg-zealy/README.md | 10 ++++++---- 12 files changed, 30 insertions(+), 25 deletions(-) rename sig-design/meetings/{016-2024-05-08.md => 017-2024-05-08.md} (100%) rename sig-design/meetings/{017-2024-06-12.md => 018-2024-06-12.md} (100%) diff --git a/sig-chain/README.md b/sig-chain/README.md index 7dd3da89..ff40c2a9 100644 --- a/sig-chain/README.md +++ b/sig-chain/README.md @@ -26,10 +26,10 @@ date: 2023-1-09T00:19:20-08:00 | #11| Tuesday, December 05, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/011-2023-12-05.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/011-2023-12-05.md#transcript) |[Link](https://ak4u4umlhafhkfu5jjckivcgokrrwkzzitwtwpoy5axl6soc5paq.arweave.net/ArlOUYs4CnUWnUpEpFRGcqMbKzlE7Ts92Oguv0nC68E) | #12| Tuesday, January 09, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/012-2024-01-09.md)|[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/012-2024-01-09.md#transcript) |[Link](https://p2eg6ctrzmvcgqmibhpnvtje32gi3rt3nzdyjocfohwt6kiddsma.arweave.net/fohvCnHLKiNBiAne2s0k3oyNxntuR4S4RXHtPykDHJg) | #13| Tuesday, February 13, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/013-2024-02-13.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/013-2024-02-13.md#transcript) |[Link](https://swcn57cpu3ttvpgaf7e52xsv5wil57wtyredtvnd6bprntawwl3a.arweave.net/lYTe_E-m5zq8wC_J3V5V7ZC-_tPESDnVo_BfFswWsvY) -| #14| March 12, 2024 08:00 AM PT (Pacific Time) | | | -| #15| April 09, 2024 08:00 AM PT (Pacific Time) | | | -| #16| May, 2024 09:00 AM PT (Pacific Time) | | | -| #17| June, 2024 09:00 AM PT (Pacific Time) | | | +| #14| March 12, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/014-2024-03-12.md)|[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/014-2024-03-12.md#transcript) |[Link](https://bwp7ef3o435ht3azllxhma3vbj4u4x4zgtlx3tfc44gjnjkanyqa.arweave.net/DZ_yF27m-nnsGVrudgN1CnlOX5k0133MoucMlqVAbiA) +| #15| April 09, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/015-2024-04-09.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/015-2024-04-09.md#transcript) |[Link](https://qv5qbltorrogit5i3qvsihngxzevuweduyauwodu5rk3yhysu3xq.arweave.net/hXsArm6MXGRPqNwrJB2mvklaWIOmAUs4dOxVvB8Spu8) +| #16| May 21, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/016-2024-05-21.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/016-2024-05-21.md#transcript) |[Link](https://t7vun4ttnoelbnwkis4rf7eacagljw7a5tsobsuujmsiycgjdpna.arweave.net/n-tG8nNriLC2ykS5EvyAEAy02-Ds5ODKlEskjAjJG9o) +| #17| June 11, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/017-2024-06-11.md)| [Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/017-2024-06-11.md#transcript)|[Link](https://g6qelhldnaj52ry4xc56kge2wjrswqfgxrqs4iduth4cpqpndlfq.arweave.net/N6BFnWNoE91HHLi75RiasmMrQKa8YS4gdJn4J8HtGss) | #18| July, 2024 09:00 AM PT (Pacific Time) | | | | #19| August, 2024 09:00 AM PT (Pacific Time) | | | | #20| September, 2024 09:00 AM PT (Pacific Time) | | | diff --git a/sig-clients/README.md b/sig-clients/README.md index 62aee27e..340d00eb 100644 --- a/sig-clients/README.md +++ b/sig-clients/README.md @@ -46,7 +46,7 @@ The goal of this SIG is to foster a community around each of these clients that | #12 | Wednesday, January 17, 2024 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/012-2024-01-17.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/012-2024-01-17.md#transcript) |[Link](https://75iuscsrjioekyahvk6vad3taa5ikpweibvxs2rf4amjvzvj6gfa.arweave.net/_1FJClFKHEVgB6q9UA9zADqFPsRAa3lqJeAYmuap8Yo) | #13 | Thursday, February 22nd, 2024 09:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/013-2024-02-22.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/013-2024-02-22.md#transcript) |[Link](https://x5g5djwxzxixepgqsmxl6rupiipshcicdmq5bf2tjac35fjv5f6q.arweave.net/v03RptfN0XI80JMuv0aPQh8jiQIbIdCXU0gFvpU16X0) | #14| March 27th, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/014-2024-03-27.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/014-2024-03-27.md#transcript) | Coming Soon -| #15| April 24th, 2024 09:00 AM PT (Pacific Time) | | | +| #15| April 24th, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/015-2024-04-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/015-2024-04-24.md#transcript) |[Link](https://j3gehsinfdsmtozvozl7ne3dv2w255mnewbmwe3unblpiayao3ya.arweave.net/TsxDyQ0o5Mm7NXZX9pNjrq2u9Y0lgssTdGhW9AMAdvA) | #16| June 25th, 2024 10:00 AM PT (Pacific Time) | | | | #17| August, 2024 10:30 AM PT (Pacific Time) | | | | #18| October 2024 10:30 AM PT (Pacific Time) | | | diff --git a/sig-community/README.md b/sig-community/README.md index a07722ab..0c7b4397 100644 --- a/sig-community/README.md +++ b/sig-community/README.md @@ -28,10 +28,10 @@ This SIG (Special Interest Group) is designed for Akash community members to pro | #10| Tuesday, December 12, 2023 11:00 AM PT (Pacific Time) | Coming Soon | Coming Soon | Coming Soon | #11| Tuesday, January 09, 2024 11:00 AM PT (Pacific Time) | Coming Soon | Coming Soon| Coming Soon | #12| Tuesday, February 13, 2024 11:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/012-2024-02-13.md) |[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/012-2024-02-13.md#Transcript) | Coming Soon -| #13| March, 2024 11:00 AM PT (Pacific Time) | | | -| #14| April, 2024 11:00 AM PT (Pacific Time) | | | -| #15| May, 2024 11:00 AM PT (Pacific Time) | | | -| #16| June, 2024 11:00 AM PT (Pacific Time) | | | +| #13| March, 2024 11:00 AM PT (Pacific Time) | Coming Soon |Coming Soon |Coming Soon +| #14| April, 2024 11:00 AM PT (Pacific Time) | Coming Soon |Coming Soon |Coming Soon +| #15| May, 2024 11:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon +| #16| June 11, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/016-2024-06-11.md)|[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/016-2024-06-11.md#Transcript)|[Link](https://nl4ez6metcnz3sdkdgvxj6b2opl74ywekhhfqfj3smj6m4in3e2a.arweave.net/avhM-YSYm53IahmrdPg6c9f-YsRRzlgVO5MT5nEN2TQ) | #17| July, 2024 11:00 AM PT (Pacific Time) | | | | #18| August, 2024 11:00 AM PT (Pacific Time) | | | | #19| September, 2024 11:00 AM PT (Pacific Time) | | | diff --git a/sig-design/README.md b/sig-design/README.md index c206565f..98c6b8e2 100644 --- a/sig-design/README.md +++ b/sig-design/README.md @@ -30,12 +30,13 @@ date: 2023-1-09T00:19:20-08:00 | #13| Wednesday, January 10, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md#transcript) | [Link](https://zao4urnjuqb6ncx2vacwjuqiyqnucl2ifcfm33blijhw6v6owzla.arweave.net/yB3KRamkA-aK-qgFZNIIxBtBL0gois3sK0JPb1fOtlY) | #14| Wednesday, February 21, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/014-2024-02-21.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/014-2024-02-21.md#transcript) | Coming Soon | #15| March 13th, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/015-2024-03-13.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/015-2024-03-13.md#transcript) |[Link](https://nnq3ufkztaw2lqjhzhftmlaxw3rt7c3x6hotvsz7gjm2pf7jbgtq.arweave.net/a2G6FVmYLaXBJ8nLNiwXtuM_i3fx3TrLPzJZp5fpCac) -| #16| April 2024 08:00 AM PT (Pacific Time) | | | -| #17| June, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/016-2024-05-08.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/016-2024-05-08.md#transcript) |[Link](https://utgdid3tyicjsjmgvznzalfhes33oqqzoytow53oaqvlgg6nbmlq.arweave.net/pMw0D3PCBJklhq5bkCynJLe3Qhl2Jut3bgQqsxvNCxc) -| #18| July, 2024 08:00 AM PT (Pacific Time) | | | -| #19| August, 2024 08:00 AM PT (Pacific Time) | | | -| #20| September, 2024 08:00 AM PT (Pacific Time) | | | -| #21| October 2024 08:00 AM PT (Pacific Time) | | | +| #16| April 13, 2024 08:00 AM PT (Pacific Time) | | | +| #17| May 08, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/016-2024-05-08.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/016-2024-05-08.md#transcript) |[Link](https://utgdid3tyicjsjmgvznzalfhes33oqqzoytow53oaqvlgg6nbmlq.arweave.net/pMw0D3PCBJklhq5bkCynJLe3Qhl2Jut3bgQqsxvNCxc) +| #18| June 12, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/017-2024-06-12.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/017-2024-06-12.md#transcript) |[Link](https://ifqou2kkf6gqtmise2kelunxe2wc4xrcssgptlx3oh25flm7tcea.arweave.net/QWDqaUovjQmxEiaURdG3JqwuXiKUjPmu-3H10q2fmIg) +| #19| July, 2024 08:00 AM PT (Pacific Time) | | | +| #20| August, 2024 08:00 AM PT (Pacific Time) | | | +| #21| September, 2024 08:00 AM PT (Pacific Time) | | | +| #22| October 2024 08:00 AM PT (Pacific Time) | | | | #22| November, 2024 08:00 AM PT (Pacific Time) | | | | #23| December, 2024 08:00 AM PT (Pacific Time) | | | | #24| January, 2025 08:00 AM PT (Pacific Time) | | | diff --git a/sig-design/meetings/016-2024-05-08.md b/sig-design/meetings/017-2024-05-08.md similarity index 100% rename from sig-design/meetings/016-2024-05-08.md rename to sig-design/meetings/017-2024-05-08.md diff --git a/sig-design/meetings/017-2024-06-12.md b/sig-design/meetings/018-2024-06-12.md similarity index 100% rename from sig-design/meetings/017-2024-06-12.md rename to sig-design/meetings/018-2024-06-12.md diff --git a/sig-providers/README.md b/sig-providers/README.md index 08e7b94c..efb95dd3 100644 --- a/sig-providers/README.md +++ b/sig-providers/README.md @@ -31,7 +31,7 @@ Provider SIG covers everything pertinent to Providers on Akash Network. This inc | #14 | Wednesday, February 28, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/014-2024-02-28.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/014-2024-02-28.md#transcript) | Coming Soon | #15| March 27, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/015-2024-03-27.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/015-2024-03-27.md#transcript) | Coming Soon | #16| April, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/016-2024-04-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/016-2024-04-24.md#transcript) | Coming Soon -| #17| May, 2024 08:00 AM PT (Pacific Time) | | | +| #17| May 22, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/017-2024-05-22.md)|[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/017-2024-05-22.md#transcript) |[Link](https://a6qm5qjrbhmjkmbmsfldmoqzdspsaxypsgfq26wfw6ysnw3xp7cq.arweave.net/B6DOwTEJ2JUwLJFWNjoZHJ8gXw-Riw16xbexJtt3f8U) | #18| June 26, 2024 08:00 AM PT (Pacific Time) | | | | #19| July, 2024 08:00 AM PT (Pacific Time) | | | | #20| August, 2024 08:00 AM PT (Pacific Time) | | | diff --git a/sig-support/README.md b/sig-support/README.md index 92d3bfb6..547b4e75 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -49,7 +49,7 @@ sig-support is responsible for defining mechanics of how support works at Akash | #31 | Wed, April 17, 2024 08:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon | #32 | Wed, May 01, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/032-2024-05-01.md) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/032-2024-05-01.md#transcript)|[Link](https://fp4bufbowjh5thinihsyy52ddcyesjk2yofv4fgjmrhnkahxg5ua.arweave.net/K_gaFC6yT9mdDUHljHdDGLBJJVrDi14UyWRO1QD3N2g) | #33 | Wed, May 15, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/033-2024-05-15.md)|[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/033-2024-05-15.md#transcript)|[Link](https://qc3gxtikakjsqoqohkver467q5u675nuwy7ovtc6j4ajicy7vwna.arweave.net/gLZrzQoCkyg6DjqqSPPfh2nv9bS2PurMXk8AlAsfrZo) -| #34 | Wed, May 29, 2024 08:00 AM PT (Pacific Time) | | | +| #34 | Wed, June 26, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/034-2024-06-26.md) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/034-2024-06-26.md#transcript) |[Link](https://edy24xoc5isqb4ilutntgush3jmsnlcnfjaajdnsr2f5d34caktq.arweave.net/IPGuXcLqJQDxC6TbM1JH2lkmrE0qQASNso6L0e-CAqc) ## Leadership diff --git a/wg-akash-website/README.md b/wg-akash-website/README.md index 482e8012..d6d4f2f2 100644 --- a/wg-akash-website/README.md +++ b/wg-akash-website/README.md @@ -33,7 +33,9 @@ This working group is responsible for managing and improving the Akash Network W | #21 | Wednesday, January 03, 2023 06:30 AM PT (Pacific Time)| Coming soon | Coming soon| Coming Soon | #22 | Thursday, January 04, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/022-2024-01-04.md)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/022-2024-01-04.md#Transcript)| [Link](https://ebt6smszfxnrsafl35ae3krholqikfmckktlj6rw2tpk26lxcmgq.arweave.net/IGfpMlkt2xkAq99ATaoncuCFFYJSprT6NtTerXl3Ew0) | #23 | Friday, January 05, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/023-2024-01-05.md)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/023-2024-01-05.md#Transcript)| [Link](https://5vpr5a76zkbuulfpmj7mtg24vkn6vpli5zlmcvqd3uupea3bxgva.arweave.net/7V8eg_7Kg0osr2J-yZtcqpvqvWjuVsFWA90o8gNhuao) -| #29 | Friday, April 04, 2024 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/029-2024-04-04.md)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/029-2024-04-04.md#Transcript)| [Link](https://yiwmcmmelchqik2ii4s7yt2wzvjy55gwxnpe2uekrwv6rv552sgq.arweave.net/wizBMYRYjwQrSEcl_E9WzVOO9Na7Xk1Qio2r6Ne91I0) +| #29 | Thursday, April 04, 2024 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/029-2024-04-04.md)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/029-2024-04-04.md#Transcript)| [Link](https://yiwmcmmelchqik2ii4s7yt2wzvjy55gwxnpe2uekrwv6rv552sgq.arweave.net/wizBMYRYjwQrSEcl_E9WzVOO9Na7Xk1Qio2r6Ne91I0) +| #30 | Thursday, May 16, 2024 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/030-2024-05-16.md)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/030-2024-05-16.md#transcript)| [Link](https://dpisfxnpneb3dvtssughllgmsyn6a7qasqh62lwtpuvm3xaomcnq.arweave.net/G9Ei3a9pA7HWcpUMdazMlhvgfgCUD-0u030qzdwOYJs) +| #30 | Thursday, June 13, 2024 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/031-2024-06-13.md)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/031-2024-06-13.md#Transcript)| [Link](https://urav5nq4ipj2qxxrryzspu67zqhcsvxc7iuv6mk7wkniixznkkmq.arweave.net/pEFethxD06he8Y4zJ9PfzA4pVuL6KV8xX7KahF8tUpk) ## Leads diff --git a/wg-provider-audit/README.md b/wg-provider-audit/README.md index a2389f54..ab4bd8b9 100644 --- a/wg-provider-audit/README.md +++ b/wg-provider-audit/README.md @@ -16,7 +16,7 @@ This working group is for developing an open source auditor tool for providers. | --- | --- | --- | --- | --- | | #1 | Wed, Feb 21, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/wg-provider-audit/001-2024-02-21.md) | [Link](https://github.com/akash-network/community/blob/main/wg-provider-audit/001-2024-02-21.md#transcript) | Coming Soon | #2 | Wed, May 1st, 2024 09:00 AM PT (Pacific Time) | No meeting | No meeting | No Meeting -| #3 | Thursday, June 13, 2024 10:00 AM PT (Pacific Time) | | | +| #3 | Thursday, June 13, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/wg-provider-audit/meetings/002-2024-06-13.md) | [Link](https://github.com/akash-network/community/blob/main/wg-provider-audit/meetings/002-2024-06-13.md#transcript) | [Link](https://nergf5caumt4yjgrcif4bb6yxjrq6ftqaj52ge3l63ggj3qqlqaa.arweave.net/aSJi9ECjJ8wk0RILwIfYumMPFnACe6MTa_bMZO4QXAA) | #4 | Wed, July 17, 2024 10:00 AM PT (Pacific Time) | | | diff --git a/wg-provider-audit/meetings/001-2024-02-21.md b/wg-provider-audit/meetings/001-2024-02-21.md index 7bf6e9a0..4daffe45 100644 --- a/wg-provider-audit/meetings/001-2024-02-21.md +++ b/wg-provider-audit/meetings/001-2024-02-21.md @@ -8,8 +8,8 @@ ## Meeting Details - Date: Wednesday, February 21, 2024 - Time: 10:00 AM PT (Pacific Time) -- Recording -- Transcript +- Recording: Coming Soon +- [Transcript](#transcript) ## Participants - Alani Kuye diff --git a/wg-zealy/README.md b/wg-zealy/README.md index 70f1b0d2..115b27bb 100644 --- a/wg-zealy/README.md +++ b/wg-zealy/README.md @@ -16,10 +16,12 @@ The working group is created to work on the proposal to see what support is need | #4 | Monday, December 04, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/004-2023-12-04.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/004-2023-12-04.md#transcript)|[Link](https://sq2ysituuvyyyeuuw7eawkdlbmvqpwtlkqkpogujyh5jfoxexosq.arweave.net/lDWJInSlcYwSlLfICyhrCysH2mtUFPcaicH6krrku6U) | #5 | Monday, December 11, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/005-2023-12-11.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/005-2023-12-11.md#transcript)|[Link](https://hp5novctzn3y56mrqix5wq3knexy4w24tk2ugahmstq2ofxzp57a.arweave.net/O_rXVFPLd475kYIv20NqaS-OW1yatUMA7JThpxb5f34) | #6 | Monday, December 18, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/006-2023-12-18.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/006-2023-12-18.md#transcript)|[Link](https://efn65ve3e5sebv7bhpgilvvzv23zx3ln6goskfwwrhj5rsmbludq.arweave.net/IVvu1JsnZEDX4TvMhda5rreb7W3xnSUW1onT2MmBXQc) -| #7| Monday, January 15, 2023 06:30 AM PT (Pacific Time)|coming soon| coming soon | Coming soon -| #8 | Monday, January 22, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/008-2024-01-22.md)| [Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/008-2024-01-22.md#transcript) | [Link](https://4dq4pkkqqmljo2ukbfplejfpdjw2itvunyzo3hf24zra73afipwa.arweave.net/4OHHqVCDFpdqiglesiSvGm2kTrRuMu2cuuZiD-wFQ-w) -| #9 | Monday, February 12, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/009-2024-02-12.md)| [Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/009-2024-02-12.md#transcript) | Coming Soon -| #10 | Monday, March 03, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/010-2024-03-18.md)| [Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/010-2024-03-18.md#transcript) | Coming Soon +| #7| Monday, January 15, 2024 06:30 AM PT (Pacific Time)|coming soon| coming soon | Coming soon +| #8 | Monday, January 22, 2024 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/008-2024-01-22.md)| [Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/008-2024-01-22.md#transcript) | [Link](https://4dq4pkkqqmljo2ukbfplejfpdjw2itvunyzo3hf24zra73afipwa.arweave.net/4OHHqVCDFpdqiglesiSvGm2kTrRuMu2cuuZiD-wFQ-w) +| #9 | Monday, February 12, 2024 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/009-2024-02-12.md)| [Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/009-2024-02-12.md#transcript) | Coming Soon +| #10 | Monday, March 18, 2024 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/010-2024-03-18.md)| [Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/010-2024-03-18.md#transcript) | Coming Soon +| #11 | Monday, April 15, 2024 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/011-2024-04-15.md)| [Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/011-2024-04-15.md#transcript) | [Link](https://bddlwy5cp5qgwpvbfyvqq255oa6uprp2xtxdhpplr5k7syqvd2qa.arweave.net/CMa7Y6J_YGs-oS4rCGu9cD1Hxfq87jO9649V-WIVHqA) +| #11 | Monday, April 29, 2024 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/012-2024-04-29.md)| [Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/012-2024-04-29.md#transcript) | [Link](https://rfo5d4qnnddwhhwyncat6u6gjone7ohuotiv6op3rvzu3va5glpq.arweave.net/iV3R8g1ox2Oe2GiBP1PGS5pPuPR00V85-41zTdQdMt8) ## Leads - Piber Dev From f904d17544069c71f4a108d0f0757c2da6fee2d0 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 19 Jul 2024 12:50:59 +0000 Subject: [PATCH 106/138] Create meeting notes for Sig-Community #17 (#631) * Create meeting notes for Sig-Community #17 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Create meeting notes Sig-Community #17 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 017-2024-07-09.md added transcript chore: add recording link Signed-off-by: Drinkwater * Update 017-2024-07-09.md added recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-community/meetings/017-2024-07-09.md | 234 +++++++++++++++++++++++ 1 file changed, 234 insertions(+) create mode 100644 sig-community/meetings/017-2024-07-09.md diff --git a/sig-community/meetings/017-2024-07-09.md b/sig-community/meetings/017-2024-07-09.md new file mode 100644 index 00000000..3cbe6c7a --- /dev/null +++ b/sig-community/meetings/017-2024-07-09.md @@ -0,0 +1,234 @@ +# Akash Network - Community Special Interest Group (SIG) - Meeting #17 + +## Agenda +- Review of Previous Meeting Topics +- Q3 Events Proposal +- Community Support Proposal +- ETHCC Events Update +- Bounties and Community Engagement +- Zealy developer Onboarding campaign Updates +- Discord Security and Spam Monitoring + +## Meeting Details +- Date: Tuesday, July 09, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://x6pq6krlnowidy2qpsxdgyrnx7gz5i4ypuxxeemqsynsvipvhoaa.arweave.net/v58PKitrrIHjUHyuM2Itv82eo5h9L3IRkJYbKqH1O4A) +- [Transcript](#Transcript) + +## Participants +- Dinobi Udeh (Stanley) +- Robert Del Rey +- Rodri R +- Tyler Wright + +## Metting Notes +- **Welcome and Introduction:** + - Tyler Wright chaired the meeting in Adam's absence. + - Discussed Q3 events proposal and community support proposal which both passed on chain. + - Details about the passed proposal. + - Link to the proposal to be shared in the chat. + +- **Community Support Proposal:** + - Passed on chain and will help continue programs moving forward. + - Link to the proposal to be shared in the chat. + - Emphasis on activating contributions from community members. + - Bounties available for contributions; link to bounty board and bounty hunter's area on Discord to be shared. + - Encouragement for insiders and general members to participate in bounties. + - Insiders urged to join working groups and Specialist Groups to foster contributions. + +- **ETHCC Events Update:** + - Several community members are in Brussels for ETHCC. + - Akash is participating in 14+ events. + - Greg and Anil are giving multiple talks. + +- **Zealy developer Onboarding campaign Updates:** + - Robert and Piber working on updates for Zealy. + - Testing other platforms to compare with Zealy for developer onboarding campaign. + - New GitHub discussion to go live this week. + - Focus on developer and non-developer missions, including documentation. + +- **Hackathons and Funding Opportunities:** + - Discussion of hackathons and funding opportunities, including quadratic funding from DoraHacks. + - Smaller hackathon opportunities available; links to be shared. + - Encouragement to notify the community of any hackathons over the summer. + +- **Discord Security and Spam Monitoring:** + - Monitoring and addressing spam and scams in the Akash Network Discord server. + - Community members and insiders encouraged to report spam and suggest words for autobot filtering. + - Efforts to funnel out spammy partnership inquiries by asking specific questions about the organization and partnership type. + - Continuous monitoring and improvement of Discord security. + +- **Validator Proposal:** + - Reminder for validators to vote on the on-chain proposal. + - Continued monitoring of Discord channels to remove scammers and spam. + +- **Event Planning:** + - Encouragement to start planning for Q3 and Q4 events. + - Information on how to get involved in documentation and website projects. + - Invitation to join Sig design and other working groups. + - Master schedule for sigs and working groups available at Akash.Network/development. + +- **Final Remarks:** + - Tyler Wright to continue leading meetings in Adam's absence. + - Acknowledgment of efforts and support from community members. + - Encouragement to continue participating in discussions and proposals. + +## Action Items: +1. **Tyler Wright:** + - Share links to [Q3 events proposal](https://www.mintscan.io/akash/proposals/260), [community support proposal](https://www.mintscan.io/akash/proposals/259), bounty board, and bounty hunter's area in chat. + - Share link to [community pool](https://github.com/akash-network/community/tree/main/community-pool-spend-reporting) spend reporting dashboard in chat. + - Share information on hackathons and funding opportunities. + - Monitor and reiterate guidelines for filtering partnership inquiries on Discord. + +2. **Rodri R:** + - Continue reaching out to community members regarding Discord engagement and spam monitoring. + - Assist in funneling partnership inquiries by asking specific questions. + +3. **Robert Del Rey:** + - Publish new GitHub discussion on developer onboarding program. + - Share findings on Zealy and other platforms. + - Announce new missions and upcoming phases on Discord and GitHub. + +4. **All Participants:** + - Participate in upcoming Q3 and Q4 events. + - Notify the community of any upcoming events for initial planning for 2025 events. + - Report any spam or scam activity in the Discord server. + - Suggest terms for autobot filtering to combat spam and scams. + - Engage in GitHub discussions and provide feedback on proposals. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to Sig Community monthly meeting number 17. It is June or student July 9th. 2024. Usually The Specialist Group for Community is run by Adam wasley is currently out on paternity leave. So while he's out, I will be supporting and helping to run these meetings at the last. + +Tyler Wright: Sig community meeting the group talked about a number of topics including Q3 events proposal which I believe just passed on chains last week. I'm so thank you to all those that voted on that proposal again. It has passed I'll drop a link in chat for those as well as the Community Support proposal that has also passed on chain. So again, if anybody thank you to all the voted again and that'll just help continue some of those programs moving forward Q3 and then again, there'll be another proposal going on. + +Tyler Wright: We also talked about ECC a bit a number of folks that usually this call are currently out on the ground in Brussels again akashes hosting or participating and I think over 14 events including the main ECC event in a couple other larger events or happening in Brussels as well. So there's a large presence in Brussels. I believe Greg has a number of talks as well as a Neil the head of product and VP of engineering at the number of talks happening in Brussels. So the whole slate of events, I'm sure we'll talk about those in more detail during the steering committee. But if anybody has any additional questions again following those events, feel free to drop those in Sig community. + +Tyler Wright: again, just as a reminder, there's an action item from the last Sig Community monthly meeting around getting folks to participate in any events that they have upcoming for Q3 or Q4. We're also started to put together again. I'm sure a working group around the 2025 events. again look after that over next couple of months, but if folks can start to put together events that they see or getting notified about that would be very helpful to the Greater Community to start to and do some initial planning. + +Tyler Wright: on top of that again this proposals that passed on chain number 260 and 259 the Q3 Community Support proposal. I will drop those in the chat for folks just as a reference points if they don't already have it one additional item that was discussed at Sig economics, but it's a newer item is just from a transparency sake again anything that is currently being managed by overclock. When we ask that all groups do this. There is a + +Tyler Wright: A public reporting dashboard that's available to folks. It's called community pool spend reporting. I'll drop it in the chapter folks, but it's just another reference point. I know Huey has traditionally put all transparent reporting for all past events inside the specific GitHub discussions. But now there is again a reporting board for those that want to understand how funds are spent from some of these proposals out of news community pool spend. So again, if anybody has any questions or comments, feel free to drop those in sick Community, but again also reports are available to larger community. + +Tyler Wright: cool related to the Community Support proposal again one of the things that we try to do with insiders as well as just general members of the community is activate contributions from everywhere to get to the Cloud parody and to continue to build their caution Network that it takes more than + +Tyler Wright: Just a few individuals and teams again. Overclock Labs is just one of the many teams that it's working on the acost network open source project with that said there are a number of bounties opportunities for folks that want to get involved. It's a bounty board that I'll drop a link in the chat but there's also a bounty hunter's area on Discord where again if folks as get involved there they can also again get access or it had the Insiders connect them to some of the items and then I can see where they can contribute I would also ask insiders to again if they can join The Specialist Group are working group to do so because that send individuals are looking to contribute to one of those groups that is a great way and easy way to get involved where people can just get to know you during a meeting. Even if you don't have much just saying just listening we can introd + +00:05:00 + +Tyler Wright: Yourself and then here live about things that are being worked on and figure out where you can add value. So I'll continue to ask insiders to push that as well. But if there's another opportunity that you see looking to get involved again, please feel free to reach out. There's both non-technical and Technical ways to get involved. + +Tyler Wright: very quickly and I want to open up to see if there's anybody else that has any agenda items. I know at the last meeting also talked about the development platform Robert gave us an update on. some of the work that he's been doing along with Fiverr for zealy. And so maybe we can get update there. The only other items that I wanted to cover today were around hackathons we talked about last week. there are a couple of hackathon opportunities as a quadratic funding opportunity from door hacks that they've pitch to us following their cost hackathon that just ended in end of May. There's also a small hackathon where they put a proposal on chain. + +Tyler Wright: And there was some hackathon funds available. because there's no hack upon happening over the summer, and it's a small dollar amount and remember the community and remember the Insiders available to go in person. We're backing this hackathon. So again, I'll drop in information for that hackathon there. But again, this is something that has been paid and again shared for folks. + +Tyler Wright: So again, if anybody has any other small hackathon opportunities that you see over the next couple of months, especially while Adam is out. Please feel free to send them the drop a note in Sig Community get folks involved in the discussion. I know there are some again Akash hackathon, akt available based upon a proposal. I went out the top of the year. So again, we're I think the ideas to save a large portion of those funds for a fall or winter hackathon. I'll be run by Adam and members of the community but leading up to that again if there's any small opportunities that you see to try to drive Demand with new users or existing users that leverage it costs compute again, feel free to drop a note in sick community and we can look to support those hackathons. You can start a discussion similarly to what + +Tyler Wright: that team spark hackathon did or again. You can just start a discussion in Discord and then see where it leads from there. + +Tyler Wright: all Other than that, the only other item I was going to touch on was this General Discord. We take some time during the six support to talk about this in detail as well. But I know that some members of insiders have called out some spam activity that they've seen and some scams that they've seen leveraging certain words like server announcement Etc. If anybody from the larger Community or Insider specifically see any beams in terms of + +00:10:00 + +Tyler Wright: content or words that should be caught by an Autobot tool, to cut down on scamming and spam and the cost Network Discord server. Feel free to drop those in Sig Community. or if you're an Insider and The Insider Channel again, we'll use time during this sick Community call to just checking on just general scamming and spam inside Discord and make sure that we can continue to monitor it and remove it as often as we can. Any other terms or any other behaviors that anybody here is seen in the Discord or other channels that might be worth sharing. + +Tyler Wright: Go ahead. + +Rodri R: Why do people want to do with that? Because it happened more now. + +Tyler Wright: yeah, I say that's a good call. Rodri we can do if you can continue to reach out to people let them know I will do that as well because I think I know some of the folks that you're talking about. That's actually a good call out one of the things that we're trying to do and we talked about this in six support meeting is as new people join. The Discord many folks are because of the growth of the cash Network project over the last few years. There's a number of people that want to by themselves to the cache of our actual functioning web 3 projects that works and has utility. and so they just look for partnership opportunities that are + +Tyler Wright: Kind of just a waste of time and energy. What we've asked folks to do inside especially is start to ask some specific questions to funnel out some of these General inquiries that come in through Discord. So, if they don't say what kind of organization they're from or what kind of partnership they're looking to have, asking those specific information from pieces of information in the public to try to again get more information out of them or feel throughout some of the people are just looking to spam the Discord and I'm never looking to come back. That's a great way to again. That's some of these opportunities prior to tagging a From there. Again. The member of the core team will be looking but you always look to. + +Tyler Wright: have an Insider reach out to remember the core team if there's an opportunity that makes sense. But again, this is an open community. So anybody from the community can get involved and kind of pushing these hope opportunities forward and assessing what next steps need to be done. So I will continue to reiterate that to folks and I'll ask insiders or anybody listening to this call to be a steward and again help push newer folks in the right direction and get as much information out of them as possible. + +00:15:00 + +Tyler Wright: thank you Roger for calling about + +Tyler Wright: yeah I appreciate. + +Tyler Wright: all right again, we'll continue to monitor some of those terms as well that we see in Discord and continue to just monitor just general behavior in Discord and see where we need improvements as we head into next g. Community monthly meeting + +Robert Del Rey: Thank you, Yes, let me quickly say that. from last month to here piver, and we've been working on the next phase on the developer onboarding campaign right… + +Tyler Wright: Robert don't feel obliged to talk,… + +Robert Del Rey: It's on Sealy on the past few weeks. + +Tyler Wright: but I know that there's been some work happening around the developer onboarding program one of the action items from the last meeting was to update the discussion that has happened. + +Robert Del Rey: We've been testing other platforms. just so we can have Info to compare those platforms to ceiling and see where it makes more sense to relaunch this campaign about this cautions. + +Tyler Wright: So again, if anybody wants to get involved and I think you're going again,… + +Tyler Wright: please get involved in discussion pyber and Robert had put a lot of time and effort into the program. And again, it's been I think successful and… + +Robert Del Rey: The new GitHub discussion should go live this week. + +Robert Del Rey: Yesterday and… + +Tyler Wright: just getting new developers into the ecosystem. + +Robert Del Rey: today we've been getting some more details that it's beneficial to add to the proposal. + +Tyler Wright: I think as a community continues to grow and projects continue to present themselves will be more opportunities for people to contribute… + +Robert Del Rey: So yeah everything it's coming together really cool. + +Tyler Wright: but again as an onboarding funnel led by Robert and… + +Robert Del Rey: And we are ready for the next phase. + +Tyler Wright: Robert, there's been a lot of successes there. + +Robert Del Rey: So this week you can expect. + +Tyler Wright: Robert, did you have any Thing that you want to talk about for people that listen to this later or… + +Tyler Wright: + +Robert Del Rey: The new threat up on GitHub,… + +Robert Del Rey: you will expect messages on Discord learning people know that this is up for discussion. + +Tyler Wright: people or think that we can reference online. I'll handle mic over to. + +Robert Del Rey: We're gonna share some of our findings on Sealy and on other platforms. And also we will share some of the New Missions that we want to bring in these new face. We're gonna go heavy in deployments. We're gonna go heavy in + +Robert Del Rey: in Cross collaboration with other related death pin products and AI products and yeah that the government's the same try to embar as many deaths as we can to attach. Although we're also going to have a very decent amount of non-developer missions. It was suggested to us that we should also have documentation missions. And we're gonna have a pretty solid offering for the next phase. Yeah, after we discussing GitHub then the proposal goes unchain. Hopefully we can start the new face by the beginning of August. But let's see what the comments say and how the community feels about this old one feel very confident about where we're doing and it's good to see that. + +Tyler Wright: No, no, you are a man of great words, much appreciate the update again. Look after that discussion becoming soon. I'm sure we'll be for some follow-up discussions live after that GitHub discussion goes up and then again look to see the boat on chain or look to see the proposal and chain up for To Natural segue real fast to a couple of proposals that I just wanted to shout out again, through the structure if anybody has an ideas, they want to pitch again. We have folks talk about those ideas and Discord and then during some of the sigm working groups and also in GitHub discussions are some active discussions going on. I would ask that folks on the Community College just in general just continue to get involved in some of these discussions. + +00:20:00 + +Tyler Wright: But I would love to again. Get folks involved when the discussion from Robert live again. Feel free Robert to drop it in number channels and then get some feedback from folks, but I much appreciate those. They are already getting involved in this discussion. + +Tyler Wright: After anything else that anybody wants to talk about on the community side that hasn't been talked about. + +Tyler Wright: if you're a validator there is one proposal on chain for boat. So again, please vote if you have not already. Thank you to all those that have voted. We'll look out for again some continued monitoring of Discord channels and other channels to optimize for again people's time and optimized to remove scammers and spam from those channels. Robert talked a bit about what's going on to developer onboarding program and so the next step so we'll look out there many of the folks on this call are currently either involved on their own time and energy or again from the core team supporting what's going on in Brussels with ECC and number of other events. So again, we'll get an update. I'm sure during the steering committee and future Sig Community meetings about all the events anybody has any + +Tyler Wright: Any additional events for 2024 q3q4 starts to put those together right now the Q3 2024 proposal. It's on chain as well as the support proposal. So again just continuing to push many of those Community contribution programs forward to get more folks involved in with console helping with documentation website Etc. I know there's a number of other projects that are going to be underway soon. + +Tyler Wright: Please feel free to join Sig design tomorrow, and I got a number of other working groups that will be made available. Again, the master for six and working groups is available at the link. I will drop in the chat, but Akasha Network slash development, and there's a calendar link again. There's continuing updates on the six and working group structure. Not too much for people's times and energy. But again, there's just been a lot of great updates happening. So thank you to everybody. Go ahead Roger. I see your hand. + +Rodri R: The square. + +Tyler Wright: Yeah, drop them in the Sig Community Discord Channel. There is a working group for the events 2024 Channel, but feel free to drop them in either Channel and then we can continue discussions in those threads. + +Tyler Wright: Cool any other topics anybody wants to discuss? + +Tyler Wright: If not, then again much appreciate everyone's time and energy today. Adam should be back in maybe not next month, but the following month in the meantime again, you're stuck with me and we'll continue to talk about all things hackathon events developer onboarding and anything else Community related so much. Appreciate everyone that's here. Thank you Roger as always for your support. Thank you to those. I'll be listening later. Hope everyone that's in Brussels is enjoying themselves and looking forward to updates there as well. hope everyone has a great rest of their day and the recording will be available soon. Thank you all. + +Robert Del Rey: Thank you Tyler,… + +Rodri R: Thank you. Have a nice day. + +Robert Del Rey: right? Bye Robert. + +Tyler Wright: It's me, too. + +Meeting ended after 00:24:34 👋 + From 3be98149f0b7c0188eacf57fcc4571d360d7ed2e Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 23 Jul 2024 17:56:23 +0000 Subject: [PATCH 107/138] Create meeting notes for Sig-economics #18 (#630) * Create meeting notes for Sig-economics #18 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 018-2024-07-03.md added transcript chore: add recording link Signed-off-by: Drinkwater * Update 018-2024-07-03.md add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-economics/meetings/018-2024-07-03.md | 217 +++++++++++++++++++++++ 1 file changed, 217 insertions(+) create mode 100644 sig-economics/meetings/018-2024-07-03.md diff --git a/sig-economics/meetings/018-2024-07-03.md b/sig-economics/meetings/018-2024-07-03.md new file mode 100644 index 00000000..8856adcc --- /dev/null +++ b/sig-economics/meetings/018-2024-07-03.md @@ -0,0 +1,217 @@ +# Akash Network - Economics Special Interest Group (SIG) - Meeting #18 + +## Agenda +- Discussion on Inflation and Staking APR (Cheng Wang) +- Community Pool Liquidity on Shade Protocol +- Proposals Update +- Transparency Reports for Community Pool Funding +- Dashboard for Provider Incentives + +## Meeting Details +- Date: Wednesday, July 03, 2024 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://gtkqa2srpm2ve37fgnzh4bvk2ajdzxzdh5owwd3vaqvtg5pncdaa.arweave.net/NNUAalF7NVJv5TNyfgaq0BI83yM_XWsPdQQrM3XtEMA) +- [Transcript](#transcript) + +## Participants +- Cheng Wang +- Julius Haus +- Maxime Beauchamp +- Poroburu +- Scott Hewitson +- Tolguy Ture +- Tyler Wright +- Zach Horn + +## Meeting Notes +- **Welcome and Overview:** +- **Scott Hewitson** + - The last meeting was rescheduled to a couple of weeks ago, leading to fewer updates this month. + - Scott Hewitson introduced the agenda and mentioned that Cheng Wang had topics to discuss. + - Previous meeting had discussions on inflation and the current staking APR being over 20%. + - Concerns were raised about the high APR, and Cheng Wang was asked to discuss it further. + - Previous chatter about using the community pool as liquidity on Shade Protocol was mentioned. + - The Shade Protocol presentation was noted, though Scott was not present for it. + - The deployment from GitHub/GitLab to Akash Network on Console was discussed. + - This proposal had been through many talks in special interest groups and steering committees and has now passed. + +- **Proposals Update:** + - Since the last call, several proposals have gone up, including Q3 events and community support. + - Dashboards showing the status of these proposals are available. + +- **Transparency Reports for Community Pool Funding:** + - A new [repository](https://github.com/akash-network/community/tree/main/community-pool-spend-reporting) in the community allows anyone receiving community pool funding to add transparency reports. + - Scott mentioned adding Overclock’s 2024 reports and plans to add more historical data. + +- **Dashboard for Provider Incentives:** + - Scott mentioned creating a dashboard for provider incentives, with a direct link to be provided later. + - Details about the amount of AKT off-ramped, liquidated, committed, and expended are tracked. + +- **Further Discussion by Cheng Wang:** + - Emphasized the importance of accountability and transparency for every unit of AKT spent. + - Mentioned plans to formalize the core team and engineering contributions, with more details to come in the next quarter. + - Discussed the inflation issue, proposing to lower inflation and increase the community pool tax from 40% to 50%. + - Suggested reducing the inflation max parameters from 20% to 15% and the min from 13% to 10%. + - Emphasized the need for provider incentives and the formalization of these programs. + - Discussed the timeline for circulating the proposal and gathering community feedback. + - Addressed future considerations for the community pool tax rate, with potential adjustments based on network needs and AKT value. + - Mentioned that APR projections will be circulated for community review before submitting the proposal. + +- **Community Pool Size Context:** + - Scott provided context on the current sizes of other community pools: 52 million ATOMs, 37 million OSMO, and 26 million AKT. + - Highlighted the importance of funding the community pool for future Akash network needs and incentives. + +- **Provider Incentives and Verified Compute:** + - Discussed the importance of provider incentives and the upcoming proposal for verified compute. + - Encouraged community members to review and provide feedback on the GitHub discussion regarding [verified compute](https://github.com/orgs/akash-network/discussions/614). + +- **Open Floor for Questions and Comments:** + - Maxime Beauchamp asked about the long-term plan for the community pool tax rate. + - Cheng Wang explained that while 50% is the target for the foreseeable future, the rate could be adjusted based on network needs and AKT value. + - Maxime also inquired about the projection of APR, to which Cheng confirmed that projections will be circulated for community review. + +- **Closing Remarks:** + - Scott thanked everyone for joining and encouraged them to participate in discussions on Discord and GitHub. + - Cheng wished everyone a happy Fourth of July and signed off. + +## Action Items +1. **Scott Hewitson:** + - Provide the correct link to the dashboard for provider incentives. + - Continue updating Overclock’s transparency reports and add historical data. + - Post meeting notes on GitHub and monitor for any further discussion in the community channels. + - Follow up on the community pool liquidity usage on Shade Protocol and provide updates. + +2. **Cheng Wang:** + - Discuss the inflation and staking APR concerns in more detail in the next meeting. + - Circulate the proposal on GitHub and gather community feedback before submitting the governance proposal. + +3. **All Attendees:** + - Review the new repository for transparency reports and add any relevant reports. + - Check the dashboards for the status of ongoing proposals and provider incentives. + - Provide feedback on the verified compute proposal on GitHub. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Scott Hewitson: All right, m everybody. Welcome to this month's installment of Sig economics economics and the last month was rescheduled. So it was only a couple weeks ago. So there may not be a ton of updates, but I know Cheng has a few things he'd like to talk about as So let's start with last time. We had some questions about there's some chatter about inflation, current staking APR is over 20% Some people are concerned that that's too high and I think change, discuss that a little bit as well because we put some thought into it as well. + +Scott Hewitson: And then I know last time there's some chatter about using some of the community pool as liquidity on shade protocol. I know they presented at steering committee actually wasn't present for it, but we'll see how that goes. Then from The Proposal side, so we since the last call couple proposals. had gone up the Q3 events and Community Support, those are ongoing programs. There's just the quarterly requests and we have a dashboards that kind of show the status of all those Actually, I'm on that point here is a link to we created a little repo and community that is just an area for anyone who receives. + +Scott Hewitson: Community pool funding basically you can do a PR and add, if any transparency reports anything you want to report from the money side. I went ahead and added some stuff from overclock side for 2024 probably add a few more things going back further, but just to get it kicked off a little bit. So anyone who's receiving funding and wants to report on Feel free to add that there. + +Scott Hewitson: and then what else passed so there was the deployment from GitHub gitlab that bucket to caution Network on Console. I know that one passed as well and that one had been in many talks in Special interest groups working groups and went to the steering committee. So that one passed. And I don't think there's any other major things since the last call. Yeah, I think that's about it. So I'm gonna kick it over to Cheng. I'd like to first talk about quick recap on pit because we have a dashboard off for that and then the inflation discussion and then anything else you'd like to touch on chain. + +Cheng Wang: Yeah, did you want me to touch on the PIP stuff first or sorry, I wasn't clear. + +Scott Hewitson: I'll just give a quick synopsis. So the past call I said I would be making a dashboard for provider incentives on That page I sent earlier as well. But here's the direct link to it. no, that's the wrong one. + +Scott Hewitson: I'll get that truck then but basically, there's a certain amount of akt that have been off ramps liquidated. there's certain amount that's been committed and expended. So it's just going to be tracked there. And you can take a look at it yourself and have any questions feel free to Cheng go ahead. You can go ahead with the other stuff I'll get the correct link for the dashboard. Yes. + +Cheng Wang: Sounds good. Yeah, so just a quickly reiterate there the reporting Link in the + +Cheng Wang: Akash Network repo there just to kind of put in front of everyone and I want to I think celebrate this really big I think not really miles somebody we said we would obviously the core team and this is the standard that we want to uphold right for the open network and just be responsible accountable for every unit of akt that comes out of the pool should be reported because it is a public good fun and essentially right and so it should be reported as such and we kind of want to lead and we do rather want to lead in this effort and show that this is the sander we want to adhere to in a standard we want to set and all the protocols out there, we can name them everywhere and there's a little lot of fun coming out of a big protocol that we all know, I think last yesterday or regarding Community spend and all that kind of stuff. So it's important to highlight especially now like accountability and ensuring that we are spending and a very responsible way and manners that directly or indirectly. + +00:05:00 + +Cheng Wang: Benefit the network in the most obviously responsible fashion possible. And of course reporting against that + +Cheng Wang: So if there are any thoughts questions, please comment here or in any single working group that you feel is appropriate the other thing like dovetailing from this is as we kind of move forward and as the scope of what everything we're working on continues to expand and build we will be formalizing the core team in concert, of course with the community contributors a little bit more as far as engineering contributions, right? I think Julius on the call Max obviously part of the core team now formally, directly part the community came in this way is from lasting a lot of the engineering and product contributions there for as far as they reporting against the community pool and drawing from the community pool to continue to fund development. So we're going to formalize that a bit more going forward probably in the next quarter. I want to thank you for but definitely rolling into 2025 something really front and center. + +Cheng Wang: to really + +Cheng Wang: put structure look forward to details around that so that's for community pool spend as far as engineering resources specifically to look forward to the second item is as far as the inflation that Huey touched on Wright currently the market though is doing well / sideways at some points in time. We definitely understand. The inflation rate is a little bit high. So We put together quite a bit of thought on already and we'll of course circulate the spreadsheets that we've historically have circulated modeling out what ultimate look like, but will probably look somewhere in the vein to fold two kind of components. Right one is lowering inflation is increasing community pool to the desired level of 50% So currently that parameter sits at so 40% and inflation and currently goes to the community pool and I think every bit of money that's been spent out of + +Cheng Wang: That has been extremely successful. I would say we're all relative to what their goals were right from events to Community Support to development of different features capabilities and just the cloudnos team Predator team Acquisitions all that kind of stuff. + +Cheng Wang: So we're gonna propose increasing community pool tax from 40% up to 50% That's one and then two is going to be changing the inflation max parameters. I think currently men sits at 13% and Max it's at 20% And what we'd like to do is probably reduce Min down from 13 to 10% and then Max from 20 to something like 15% And so that should bring down inflation. Just the notch. We don't want to obviously over Justin do something too crazy, So that's the I think initial proposal here and hopefully there's a good amount of support I think to support is already there as far as contributors that have chimed in the last economics, which I wasn't able to make but yeah, that's as far as inflation as well as community pool goes and I think funding the community pool, of course. + +Scott Hewitson: This put it up. Obviously. We'll throw. The tax code. Yeah, that's Max's question tax. Go to 50% Cheng. + +Cheng Wang: Yeah, that's right. + +Scott Hewitson: Is there a reason why 40% versus 50% or what's the rational there? + +00:10:00 + +Cheng Wang: Yeah, so the reason for 50% that's the marker we think we want to get to and then we talked about in Greg's talked about it and I forget we in which calls I probably a Syrian committee here or there to get it to 50% and that'll be the ongoing rate going forward to well. + +Cheng Wang: Kind of answers itself, We've been finding the pool for a little bit and… + +Cheng Wang: It does a couple things one continues to ensure the pool as well funded for all the issues. + +Cheng Wang: everything we've done has been through the public eye in a lot of people… + +Cheng Wang: We've done plus additional ones that are going that will be pushed in a future that we can't even in Envision now,… + +Cheng Wang: who I think push and human HQ, right submitting proposals on their own to get funded for various initiatives. + +Cheng Wang: right? So one of the biggest things that I forgot to mention is provided incentives programs comes out of this right and… + +Cheng Wang: So the community pool I think is doing an outstanding job and… + +Cheng Wang: then 10 and… + +Cheng Wang: it's currently quite well funded at this point in time. + +Cheng Wang: incentives that's not something we've yet put forward. + +Cheng Wang: So we want to definitely continue to build that I know there was a little bit of hand ringing when we did some marketing initiatives with coinbase that the pool would deplete… + +Cheng Wang: Yeah, we've done little scattered things here and there but we want to formalize that a lot more of course going forward. That's one bit. So the … + +Cheng Wang: but as we noted historically that wouldn't come close to the pleading and… + +Cheng Wang: so 50% is the marker we want to hit. I think that's kind of a good point to be at a 50/50 split between inflation emissions to stakers. simply by virtue of emissions as well as the increased Slash validators, of course and then 50% to the community pool to continue to fund that effort. + +Cheng Wang: + +Cheng Wang: and in terms of sorry timeline wise I think probably next couple of weeks. We'll circulate of course as is the discussion on GitHub and then have that circulate for maybe a week or so gather Community feedback and then ultimately submit the governance proposal incorporating feedback from the community. + +Scott Hewitson: Yeah, go ahead next. + +Maxime Beauchamp: Thanks for the explanation and I guess Is the plan to stay at 50% forever or is there a plan to eventually drop it or make it? higher + +Cheng Wang: That's a good question. The short answer here is we don't know what the future holds I think 50% in the foreseeable future. Let's just say call it the next year or so, right and don't hold my feet to the fire. There is probably somewhere we want to be of course. These are all governors parameters that can be changed if let's just say the community pool gets funded to akt goes to 100 bucks. I'm sure everyone love that and the community pools like a billion dollars or something like that. I'm sure we could bring that right down a little bit right especially if the use cases for the community pool aren't necessarily eating into the balance in any significant way. Obviously, we all of us right not just the core team but every single Akash token holder and then definitely stake her has a literal, stake and say in this doesn't want the pool to just sit there idle without generating some sort of return. + +Cheng Wang: To the network ultimately, So I think it's ultimately going to be a bit of a balance and we'll have to see how the community pool is used going forward. Obviously all that stuff will be super public and undergo the same level of scrutiny. it's always been on there and relative to what a lot of factors. I'm sorry to kind of give you a cop on answer, but I'll say for the year. Probably stay at that rate going forward between emissions between what the macro is doing between what the micro needs specifically of the network are other things that we can't really forecast. these things are presents for reason and it can be adjusted as such. + +Maxime Beauchamp: Yeah makes sense. And do you have a projection of the APR? That would go. + +Cheng Wang: Yeah, we're putting that together. it'll be circulated Huey or Scott and… + +Maxime Beauchamp: Okay. + +Cheng Wang: I are putting that together and that'll be circulating. So yeah, don't worry. It's not like we're discuss it here and then we'll put The Proposal on chain. + +Maxime Beauchamp: I know you did that in the past you put a proposal it would projection and stuff. So. I will. Thanks. + +Cheng Wang: Exactly. It'll all be there 100% good questions. + +Scott Hewitson: And I dropped in the messages just to give people a rough idea of community pool sides of silly atoms right now is worth 52 million Osmos were set 37 million. We're done at 26 million. So I think at some point. We probably don't need to keep filling it. But yeah, those are just like cops in the space to give people an idea. + +Cheng Wang: yeah, and then just to + +Cheng Wang: Put it into a little bit of person. Thank you for that here. That's extremely helpful and in additional bit of context as we look forward is the rate at which we were requesting or the core team and the community at large has been requesting funds through a caution Network. It's hard to say that's going to be the status quo. Let's just say for 2025 and 2026. Let's just say right because as the network continues to grow as it attains further adoption further notoriety and as tool sets expand right there will be additional needs to expand that and of course that's just gonna require more funding from the network, right and provider incentives. That's not forget. This is literally two phase three hadn't yet been rolled out for various different reasons of technical capabilities right verified compute stuff like that by the way went on GitHub discussions. I think was it? last week Wednesday, and we're looking to + +00:15:00 + +Cheng Wang: Push that on chain sometime today right here. Correct me if I'm wrong there. So there are a lot of things. + +Scott Hewitson: Yeah the next day. + +Cheng Wang: Yeah, a lot of things coming down the pike that the community pool will be required to ask to fund and provide an incentives especially as we kind of in this phase one right is really an initiative to help us learn. what chipsets are in demand which providers and kind of start to chip away at that and we've gained a lot of know-how and an education quite frankly around how that process work. So we'll be in phase but phase two pit zero three going forward. Those will obviously require additional resource from the community pool to build up the resources available in the network. + +Scott Hewitson: awesome Thank you for all that flavor and color on all things. Yeah, I was gonna say I was gonna ask about the verifiable compute. I dropped it in. Here's a discussion 614 and since coming from Surah from University of Texas. So it feel free to put in any notes comments. It's been up for a little over a week, I believe and they spoke it steering committee. But yeah, if you have anything you'd like to add to it, please please do. Let's see. I think that's all I had from my side on items that I'd like to touch on or for you to touch on chains. Right? Do you have anything else you'd like to add? in general + +Cheng Wang: Yeah, I mean any questions that anyone has regarding the GitHub discussion on verified compute, this is a good place to ask any initiatives that you think might be on the horizon or not, or if you have any ideas right for the community pool for everyone here and also anyone reading or listening to this afterwards because I know it's just the lot of us here. Please chime in let us know make your voices heard. + +Scott Hewitson: We don't have Andrew G here to ask my token question, All Okay, so I anything I think we can probably cut things short. I'll give one more chance if anyone wants to bring up anything at all. Stay it now or wait till next month. + +Scott Hewitson: All thank you everyone who joined in today and those that'll be watching this at a later time. I'll make sure to have notes up on GitHub and let us know in the meantime between calls and see economics and Discord if we can got anything that pops up or you don't feel comfortable talking about it Alrighty with that. I'm going to end the call or in the recording and we'll see everyone later. + +Cheng Wang: All right, see everyone in the metaverse. Enjoy your fourth of July for everyone. + +Meeting ended after 00:18:48 👋 + + From 548297e7c15dbde128281ad54e57d012cba10464 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Wed, 24 Jul 2024 16:34:57 +0000 Subject: [PATCH 108/138] Create meeting notes for sig -providers #18 (#635) * Create meeting notes for sig -providers #18 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 018-2024-06-26.md added transcript chore: add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-providers/meetings/018-2024-06-26.md | 204 +++++++++++++++++++++++ 1 file changed, 204 insertions(+) create mode 100644 sig-providers/meetings/018-2024-06-26.md diff --git a/sig-providers/meetings/018-2024-06-26.md b/sig-providers/meetings/018-2024-06-26.md new file mode 100644 index 00000000..ce247a82 --- /dev/null +++ b/sig-providers/meetings/018-2024-06-26.md @@ -0,0 +1,204 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #18 + +## Agenda +- Welcome and Introductions +- Follow-up on Praetor Acquisition and Integration with Akash Console +- Provider Builds and Upgrades +- Damir Simpovic's Presentation + ## Meeting Details +- Date: Wednesday, June 26, 2024 +- Time: 08:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + +## Participants +- Andrew Mello +- Andrey Arapov +- B S +- Damir Simpovic +- Deval Patel +- Jigar Patel +- Rodri R +- Scott Carruthers +- Tyler Wright + +## Meeting notes +- **Welcome and Introductions** + - Tyler Wright opened the meeting and welcomed attendees. + - Recap of last month's discussions on the Praetor acquisition and next steps for integration with Akash Console. + +- **Follow-up on Praetor Acquisition and Integration** + - Tyler Wright discussed ongoing work and next steps involving Jigar Patel and Deval Patel around console 2.0. + - Encouraged attendees to watch the detailed video from the SIG clients meeting for more information. + +- **Provider Builds and Upgrades** + - Tyler Wright mentioned Scott Carruthers' major changes to provider builds and the ongoing testing involving community and core team members. + - Andrey's testing contributions were highlighted. + - Action items related to provider build upgrades and specific testing were noted. + +- **Console 2.0 Updates** + - Encouragement to review the SIG clients video for detailed insights into console 2.0 and its short-term focus areas. + +- **Damir Simpovic's Presentation** + - Damir Simpovic shared progress on deploying Prometheus and Grafana using Helm charts on the Akash provider. + - Demonstrated the current functionality of the dashboards and monitoring tools. + - Discussed the overutilization of memory by some Akash services. + - Mentioned plans to clean up unnecessary features and improve deployment. + - Invited community contributions and offered to start a GitHub repository for collaboration. + +- **Feedback on Damir's Presentation** + - Andrew Mello provided feedback emphasizing the importance of having both internal and external monitoring solutions. + - Highlighted the need for external checks to ensure cluster accessibility even during outages. + +- **Additional Updates and Discussions** + - Andrew Mello discussed the Akash mining project and the deployment queue, which has been finalized and finished. + - Mentioned that some providers might experience full CPU utilization as part of the testing and deployment process. + - Encouraged providers to participate in GitHub discussions to voice their thoughts and feedback. + +- **Open Floor for Discussion** + - Damir Simpovic mentioned that the user facing issues is learning Kubernetes and is receiving step-by-step help from the community. + - Tyler Wright discussed ongoing updates to documentation for clarity on provider audits and support. + - Encouraged attendees to look forward to upcoming working group meetings for the Akash website and documentation, as well as the steering committee meeting. + +## Action Items: +- Track provider build upgrades and ongoing testing via the product and engineering project board. +- Attendees to review detailed updates from the SIG clients meeting. +- Damir to create a GitHub repository for the Prometheus and Grafana deployment project. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to providers monthly meeting number 18. It is June 26 2024 During the special interest group for providers the Akash Community discusses anything related to the provider on Akash, at the last month's meeting there was a discussion following up on all things happening with the Predator acquisition and next steps as an integrate with console. + +Tyler Wright: There was some follow-up discussion around the work on that. Jigarette and Deval are doing around console 2.0 during sick clients yesterday. So again, there was much detail that went into next steps and how Prater is going to be involved there. I'll give some time to the Prater team to talk a little bit about it here. But again, I urge anybody that wants to go into the details to watch the video that will be available shortly from sick clients just yesterday. After that damir had something that he wanted to share and then I wanted to open it up to any other discussions that anybody wanted to have. + +Tyler Wright: But again, I'll just get it started Digger if there's anything that you wanted to mention in terms of how things are going greater as it stands today and some of the next steps, or Deval feel free to chime in. + +Tyler Wright: Thank I'm gonna drop in the issue that's been created as of tracking around. Some of the provider builds upgrades have been happening. I know that again Scott made some major changes to how providers are built and has connected members of the community as well as members of the core team to test these things out. There's also again, I'll drop in the chat. + +Tyler Wright: A number of items. I've been put together by Andre over a little while in terms of testing that is now underway and this testing that jigar just mentioned. So feel free to continue to track a number of items in the product and engineering project board related to this. I think there's one in testing around the provider build upgrades and then again there's a company issue that lays out all the specific testing that's going on related to that issue. + +Tyler Wright: Cool again, I would urge anybody that wants to dive deep because Jigar, the ball the Maxes spent some time yesterday during sick clients. I'm going through what's going on next in a little bit more detail and more detail around console 2.0 and some of the five main areas of focus in the short term. + +Tyler Wright: Cool, if there's no questions there then we'll continue on with the agenda. I know damir had mentioned wanting to spend some time to discuss something. So I will hand the floor over to damir to talk a little bit about something that he's been working on. + +Damir Simpovic: All right. Thanks y So share my not screen, but just say + +Damir Simpovic: just the window. + +00:05:00 + +Damir Simpovic: can you guys see my window all… + +Tyler Wright: Yes. + +Damir Simpovic: so I just started working on it maybe a few days ago. So basically what I found was that there's a Prometheus and grafana Community film charts already available for deployment on the kubernetes cluster. And I toyed around with it and managed to deploy it on your cash provider. so not everything is working yet I just basically started working on it, but most of the features do work, so if you want to + +Damir Simpovic: Actually, let me show you grafana dots Euro. - ai.net so basically yeah, it's running on my test provider Euro ai.net. And the dashboards are already created basically, so they have been pulled by Helm charts and they've been automatically installed. + +Damir Simpovic: Yeah, I will work on cleaning this up a bit because we don't need all of them. But yeah. most of the stuff already works + +Damir Simpovic: it's super simple and Yeah. For instance I don't know the networking. Stuff already works you can sort by. + +Damir Simpovic: by namespace and see which pods actually Consumes what amount of traffic is being consumed but by which pod I don't know. Some stuff doesn't work some of these dashboards doesn't work yet. But yeah, I will clean this up. So yeah, if you want to test it I made you can go to this URL. I will leave it running. And I created the test user which is username and Both are test user. So you can see for yourself. So yeah, there you go. + +Damir Simpovic: Yeah, if anybody has any desire to help. And contribute. Yeah, please do. I think it would be. A very efficient way of Basic monitoring tools for providers. There's also the alert manager here. It's also automatically installed basically can be configured to send alerts about provider. basically whatever we configure it to ert. So yeah on Discord on email. wherever So yeah, there you go. Not much to show yet. But yeah, it does. + +Damir Simpovic: It does work. So yeah, there you go. Thank you. + +Damir Simpovic: it's actually very good that you brought this up… + +Andrey Arapov: Thank you. + +Damir Simpovic: because I didn't know this until I actually tested this but some of the Akash Services provided pods are actually over utilizing the memory. So basically let me see where they find that. + +Damir Simpovic: memory utilization 1800 percent so basically some of the ports are basically over utilizing the memory. So yeah. I think it's a Akash node. That's all utilizing. So yeah. + +Andrey Arapov: It's interesting and interesting coach something definitely dig into and we could install it in more providers perhaps just to compare, the behavioral and it's also good to track it whenever we released a newer version of node software kind of compared with previous traffic instrument that previously we had the issue open by Andrew Mello and he's in the goal accident Thanks for opening it up that he noticed, the traffic Spike. So it's definitely good thing to have things. + +00:10:00 + +Damir Simpovic: Yeah, I'll start a GitHub repo for this so. Basically on my own GitHub if anyone wants to take a look or whatever. feel free + +Andrey Arapov: Yeah, cool. I think I'll just take some provider probably try to deploy there. + +Damir Simpovic: I'll deploy first on your plots. Basically, I'll test on this provider on this which it's production but nobody's using it intentionally. or the first Production really? Let's call it version room. I'll test it on europods and go from there. + +Andrey Arapov: Yeah, in the end of the day, it's just in all the metric so it's easy to kill it because I think it's been deployed this whole chart namespace you can just destroy it anytime, right? + +Damir Simpovic: Yes, exactly. The helm charts is actually being maintained by the Prometheus community. And they're open source. You can just take them and modify them. we like but they work as they are. I only change a few things. I added the English controller. And yeah not a lot of work has been done from on my part yet, but + +Andrew Mello: Hi guys, and hi damir. Thanks for taking a look at that. I have a little bit of feedback just from some experience with this. It's a question of really what is the problem the dashboards are looking to solve if you're looking to make a public dashboard for the cluster that's going to be available on a domain name. That is a good solve for it. However, if the cluster goes down, right or there's no network connectivity, then it doesn't really solve the problem for the user checking the status of the cluster. Right so you can look at that as a partial solve for kind of uptime and status but it still is really important to have an external public check basically of your accessibility on your ports and your endpoints for your cluster as So doing that against eight four four three, for example from an external check it's + +Andrew Mello: Really important and that's something you should still definitely think about and kind of think through here as you're thinking through the solution because the dashboard you have worked great when the Clusters alive, but if the cluster is not accessible or there's an outage or the power goes out or the internet goes down. Then that is not gonna really do much or help from the outside perspective of… + +Damir Simpovic: There are no absolutely I agree. + +Andrew Mello: what your provider looks like. So I was just sharing this… + +Damir Simpovic: Totally I think there is no dual be all solution,… + +Andrew Mello: because again on my clusters, for example,… + +Damir Simpovic: honestly, so this part would actually be Just a part of a providers monitoring. + +Andrew Mello: there's always public dashboard. And then also again there are solutions for that kind of more local dashboard that would show if the cluster is up and running that is a nice to have… + +Damir Simpovic: Let's call it the stack. + +Andrew Mello: but you can't always rely on it basically and… + +Damir Simpovic: And it will be completely optional,… + +Andrew Mello: you can always rely on the external check. + +Damir Simpovic: . + +Andrew Mello: So just something for you to think through as you continue to develop that Sure. Yep. Got some feedback. + +00:15:00 + +Damir Simpovic: I mean, yeah. Thank you. + +Andrew Mello: Just some thoughts. Yeah again great great job. + +Damir Simpovic: Thank you. Definitely. I agree with everything he said. + +Tyler Wright: Excellent. + +Tyler Wright: Yeah, our message in the chat. Thank you for that. Damir. Are there any other questions or comments and Andrew? Thanks for that feedback. + +Tyler Wright: All I wanted to see if there's anything else on the provider side that anybody want to discuss or share again. We got an update in depth yesterday in Sig clients about console 2.0 and some of the work that will be involved from prador in that console 2.0 work and then we got again another update from jigar today damir gave a demo on some work that he's been doing around cluster monitoring, but I want to see if there's anything else that anybody wanted to discuss on the provider side. Go ahead Andrew. + +Andrew Mello: Yeah, hi guys. So since we all last spoke or you heard from me one of the things that would affect basically everybody on this call and you may have noticed that a couple weeks ago, but a cost mining is well underway, and in the process of building that I have finalized and finished the deployment queue and what that means is some of your providers you may have noticed at one time or another were becoming completely full topped off and that's one of the actual effects and benefits of the queue is that it can size and right-size deployments to the available resources on a given provider. So again, some of you may have noticed every CPU getting full, that was by Design in the testing of the queue. So again, just a heads up to the providers that + +Andrew Mello: when that Q runs you can expect a lot of deployments usage and leases basically coming from it. So I just a heads up there and normal activity from my end. + +Tyler Wright: Excellent. Does anyone have any questions on that from Andrew? + +Tyler Wright: All there's no active discussions that I see that affects providers again. I would ask that anybody that wants to get involved in discussions on GitHub do so to make your thoughts heard, but there's nothing that I can generally see it seems like everything is fairly business as usual on the provider side. I have seen this one user and MF having some real issues, but getting some support from the community and members the Insiders. Go ahead damir. + +Damir Simpovic: Yeah about this user. He's basically learning kubernetes. So yeah, don't take it too seriously. + +Tyler Wright: Yeah. Yeah. No, I know that documentation. Can you get reference? I think he's just getting literally step by step help hand holding from the community. So again, I do appreciate that. I did want to see if there's anything else on the provider side that anybody wants to discuss. We did talk a little bit on the six support call about updating documentation to make it very clear in terms of where some of the provider audits should go. That's something that is continuing to be handled. Again. There's another way that'll pass through soon. But again, we talked about that already during Sig supports a lookout for just some documentation updates as well as those that are insiders at the next meeting. We'll just do some clarification to make sure that it's very clear on where to send people for various things. + +Tyler Wright: Outside of those topics. Is there anything else that anybody wants to just discuss? Otherwise again, I'll let you all go and we have the working group for the cash website in docs to look forward to tomorrow as well as the steering committee, but Anything else anybody wants to discuss before I let y'all go. + +Tyler Wright: Terrific. again much appreciate the updates from Jigger Deval damier Andrew appreciate everyone's time on this call today. yeah take some time back and I'll drop in the notes here shortly, but please feel free to join in providers or the providers Discord channels if you have any questions between meetings, Much appreciate everyone's time today. Hope everyone has a great rest of the day. Thank you. + +00:20:00 + +Andrey Arapov: They go. + +Andrew Mello: Yeah. + +Rodri R: you guys + +Jigar Patel: Thanks guys. + +Andrey Arapov: right + +Meeting ended after 00:20:26 👋 + + From 0d698541eabd24cb89db3d440f57639bac7621f7 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 24 Jul 2024 13:36:20 -0400 Subject: [PATCH 109/138] Update steering committee README.md added video recording link for June 2024 meeting to table. Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index b721509c..0a38d85b 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -30,7 +30,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, March 28, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md#transcript)|[Link](https://4wprt5kys3oxjr7ihtu2jgx6mshwts7gzsiv2pfr4qypgrp2xywa.arweave.net/5Z8Z9ViW3XTH6DzppJr-ZI9py-bMkV08seQw80X6viw) | Thursday, May 02, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md#transcript) |[Link](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) | Thursday, June 06, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md#transcript) |[Link](https://capv32vqn7vrb5u3qvsjn3n6y6swnjkba32ukvydflmqqhrxbswa.arweave.net/EB9d6rBv6xD2m4Vklu2-x6VmpUEG9UVXAyrZCB43DKw) -| Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | |[Link](https://upv27tytyope2fseqvgnnre2au6nmmo65bs2c2fvuxtohsr5bpjq.arweave.net/o-uvzxPDnk0WRIVM1sSaBTzWMd7oZaFotaXm48o9C9M) | Thursday, July 25, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, August 29, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, September 26, 2024 11:00 AM PT (Pacific Time) | | | From fa22fe6a404aaa27c10214db01fa4816128fd606 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 25 Jul 2024 12:51:02 -0400 Subject: [PATCH 110/138] steering committee Create 017-2024-06-27.md (#643) * steering committee Create 017-2024-06-27.md chore: add notes and action items Signed-off-by: Drinkwater * Update 017-2024-06-27.md added meeting notes. Signed-off-by: Drinkwater --------- Signed-off-by: Drinkwater --- committee-steering/meetings/017-2024-06-27.md | 276 ++++++++++++++++++ 1 file changed, 276 insertions(+) create mode 100644 committee-steering/meetings/017-2024-06-27.md diff --git a/committee-steering/meetings/017-2024-06-27.md b/committee-steering/meetings/017-2024-06-27.md new file mode 100644 index 00000000..3cc1548b --- /dev/null +++ b/committee-steering/meetings/017-2024-06-27.md @@ -0,0 +1,276 @@ +# Akash Network - Steering Committee - Meeting #17 + +## Agenda + +- Review / discuss / address any community feedback, grievances, or conflicts. +- Review [projects list](../projects-list/README.md), prioritize / add / remove if necessary. +- A look at open discussions in [Github Discussions](https://github.com/orgs/akash-network/discussions). +- Open up to any other questions from the community. + +## Meeting Details + +- Date: Thursday, June 27th, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://upv27tytyope2fseqvgnnre2au6nmmo65bs2c2fvuxtohsr5bpjq.arweave.net/o-uvzxPDnk0WRIVM1sSaBTzWMd7oZaFotaXm48o9C9M) +- [Transcript](#transcript) + +## Committee + +- Anil Murty, Overclock Labs +- Artur Troian, Overclock Labs +- Greg Osuri, Overclock Labs +- Scott Caruthers, Overclock Labs + +## Participants + +- Adam Bozanich +- Allwyn Dk +- Amanda Keay +- Andrew Gnatyuk +- Anil Murty +- Artur Troian +- B S +- Cheng Wang +- Damir Simpovic +- Denis Lelic +- Deval Patel +- Greg Osuri +- Jeremy Schipper +- Jigar Patel +- Joao Luna +- Joe D +- Maxime Beauchamp +- Poroburu +- Rodri R +- Samson Thomas +- Scott Carruthers +- Sriram Vishwanath +- Tyler Wright +- Zach Horn + + +# Meeting Notes: + +* Tyler talked about the change in schedule for the Steering Committee over the next months +* Tyler went through the agenda for the meetings. The agenda can be found on the Steering Committee readme. + + +### [Product and Engineering Board / Community + Marketing Board](https://github.com/orgs/akash-network/projects) + +- Tyler mentioned that there was a lot of detailed discussion about Console 2.0 and the roadmap during the sig-clients bi monthly meeting. Tyler urged the community to take a look a the recording, as well as look a the product + engineering roadmap for additional updates on the product side. +- Since the last Steering Committee meeting there has been a network upgrade to Mainnet 12. The upgrade was a success. Thank you to all of the Akash Validators. +- Artur reiterated that the upgrade was smooth, and +- Tyler talked about the work from the Mystic Labs team. There is a cosmoskit bug that is a blocker right now, but Mystic Labs team is working to rectify. +- Tyler also briefly talked about the provider build upgrade. This was covered in sig-providers. Testing continues. +- Anil shared some notes in the chat around all of the work around Console 2.0: " I summarized few of the near term console initiatives publicly, here as well https://twitter.com/_Anil_Murty_/status/1804616363769819185 --- all these are tracked in individual tasks on the board Tyler is presenting here." +- Anil mentioned there are 5 themes for the next 2-3 months for Console 2.0. Themes include user experience for onboarding new users (including a custody layer to attract non crypto users); a provider console; and beyond. +- Hooman HQ team will contribute to Console 2.0. The proposal passed on chain. The work can be tracked [here](https://github.com/orgs/akash-network/projects/5?pane=issue&itemId=66078743). +- Tyler touched on Cosmos SDK 47 which is a major upgrade. Look out for announcements in sig-chain. +- Tyler opened it up to questions from the community. + + + +#### [Community and Marketing](https://github.com/orgs/akash-network/projects/6): + +- Tyler talked about ETHCC and all the events happening in Brussels. +- Amanda mentioned that Akash has a full slate of events from July 5th, 2024 +- Akash sponsored 15 different events. Greg and Anil have over 15 speaking engagements between them. +- Many of the events are AI and DePin focused. +- Tyler asked if there were any questions related to Marketing + Community Project Board. +- Zach talked about the Akash Chat API. There will be a permissionsless version available to the public soon. +- Anil mentioned that Akash and Flock.io are doing a hackathon leading up to EthCC. +- Tyler mentioned the Flock.io blog found [here](https://akash.network/blog/decentralized-ai-model-training-on-akash-with-flockio/) +- Amanda mentioned that the first DePin Summer Series kicks off tonight in NYC. It is a 4 part series, with the finale during Messari Mainnet 2024. + + +### Github Discussions: + +- Tyler asked the Akash Community to get involved in discussions and make their voices heard. +- Jeremy talked about his discussion: https://github.com/orgs/akash-network/discussions/543 +- Shade protocol wants to expand DEX liquidity for projects. +- AKT token can be acquired privately via secret. Discussions in sig-economics have been around 50K - 75k tokens. +- Greg asked some questions to Jeremy about how the pool works. The logistics are a challenge. +- Greg mentioned that historically the community pool hasnt been used for liquidity needs. + +- Next discussion from Sriram was brought up. Greg provided context on Sriram, a professor at U of Texas. Sriram spoke at Akash Accelerate 2024. +- Greg also talked about the problem around [verifiable compute](https://github.com/orgs/akash-network/discussions/614). +- Sriram mentioned that the goal is to hardward and software verifiable compute. Software verifiable compute is more challenging. +- The proposal is to use a dongle. +- Sriram went through the discussion with people on the call. +- The plan will be a 2 semester plan (4 quarters). +- Sriram and his team are looking forward to working with the Akash Community. + +- Tyler asked if there were any other discussions to talk about live today? + +### Open Discussion + +- There was no open discussion. + +### Action Items: + +- Brussels Events coming up July 5th, 2024 - July 13th, 2024 +- Please look at the calendar for future sigs and working groups found [here](https://akash.network/development/welcome/#calendar) +- Sig - design has seem a lot of participation from graphic designers that want to help with marketing materials and swag. Give feedback on designs. +- Wg-website and docs is a biweekly meeting for those that want to help with the open source website and the docs. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the Akash steering committee. This is a 17th edition of the Akash monthly steering committee meeting during the steering committee. The group goes over many of the things that happen across the various six and working groups. There's a typical agenda that we go through starting with again reviewing discussion an addressing any Community feedback from there your View Community. We review some of the project boards, including the product and Engineering board as well as a community and marketing board following that we'll review any new GitHub discussions. Usually we try to focus on discussion from folks out to be there. Come to a previous meeting or are here here today to the discussion a little bit more detail. + +Tyler Wright: After that, we'll open up the floor to any other questions. So if anybody has any questions that they want or any topics, they want to discuss today. Feel free to drop in the chat. I'll add them to the agenda during the open discussion portion and then we'll wrap up with just a look ahead at some of the special interest groups and working groups for the upcoming month. we recently had a steering committee at the top of this month because of all the action that happened around the cost accelerate and consensus 2024. So again, this is the second time we're meeting in June but there's certainly been a lot that's been going on this past month. Again, I'll start with the typical agenda. I want to see if there's anything on the community side relates to six working groups or just a committee instruction in general that anybody wants to get feedback on or talk about in more detail. + +Tyler Wright: All If not, then we can move on to the second item on the agenda, which is around the project boards again previously last year. We were using project We've done a lot of the work around those projects lists, and now have these boards that get updated in Fairly real time again, you can track what's going on in terms of what's been released. What's in testing progress again, what's on the roadmap and Beyond both for the product and Engineering side of the org as well as what's going on in the community and marketing front as well. + +Tyler Wright: couple things that I wanted to talk about, we'll start off with the product and Engineering roadmap. We can talk about this at a high level because there were a number of cigs and working groups that have happened over the last week during the Sig clients monthly meeting a Neil did a great job with the Maxes and some of the folks Jigger Deval to talk about all the stuff that's happening in console 2.0 and Neil gave a short presentation on some of the bigger efforts that are happening over the next couple of months. So again, I'll give Anil some time to talk about it if you want to later, but I would urge anybody when the notes are available in next day or so for sick clients to take a look there because again, it was a great meeting. + +Tyler Wright: One of the big items that has happened since the last steering committee was the mainnet twelve upgrade. It was a success and happened very quickly much appreciate to all the validators that were online and again helps with the node upgrade Artur. Is there anything that you wanted to mention in terms of the upgrade here today? Don't feel a blast. + +Tyler Wright: Absolutely. + +Tyler Wright: All right, continuing to move along there's a couple of items that are in testing right now one is around and we talked about this at the last hearing committee monthly meetings Around The Meta mask work from the Mystic Labs team. Thank you to the Maxes who have been working to incorporate cosmokid into console for getting on a call with the Mystic Labs team. I believe the error that there's an issue a bug right now. That's a Cosmo kid bug that the Mystic Labs team is working through and again the product and engineering team is continuing to monitor that so we can get this Mystic Labs met a mask work over the line and get this into released. So again, there will be some more information over the next day or so, but just do want to shout out Max C and Max B for taking the time to connect with the Mystic Labs team get them everything that they needed in terms of environment set up. And again the Mystic Labs team should be delivering and solution. + +Tyler Wright: On the metamask cosmo kit integration very very soon. + +00:05:00 + +Tyler Wright: When other item that I won't go into too much detail on is updated provider build we talked about this at length yesterday during the Sig providers meeting Jigger and Deval talked about some of the testing that they're going to do. If anybody has any questions about this issue again, you can look inside the notes. You can find out where the instructions are. If anybody from the community wants to continue to test you can track where some of the testing is going on and where that currently stands at this point. But again, this is something that in regards to just general providers stability and Improvement of the provider build process is something that Scott Carruthers has been working on with the rest of the engineering team and the product team to again do some testing and this as discussed in sick providers yesterday. We'll continue to be tested and then we'll look to be integrated into the work that the prey to our team is doing around. + +Tyler Wright: So 2.0. So again, if anybody wants to go into more detail about the provider build improvements, feel free to comment on these specific issues or listen to the sick providers monthly meeting call the recording look at the notes and feel free to join as a future sick providers call if you so desire. + +Tyler Wright: All right, covering both the stuff in testing and in release again during the Sig clients call yesterday and you'll gave an update on all the work that kind of see here related to consult 2.0. He just dropped an additional note that gives more clarity inside of the chat. So again, shout out to the product team that's been working diligently and being transparent about all the things that are being worked on where they stand Etc. And I know that more members of the just general Akash Community are getting involved and… + +Anil Murty: Yeah, not a whole lot to act or… + +Tyler Wright: supporting developing some of these features and… + +Anil Murty: what we talked about in three clients yesterday, but just to summarize things there's kind of five initiators that we're pursuing in the near term under basically the console 2.0 umbrella and… + +Tyler Wright: getting engaged with the products core team so major shout out there Anil or anybody else. Is there anything that you wanted to discuss in more detail that was discussed in Sid clients yesterday,… + +Anil Murty: keep in mind that these are just for the next, two to three months and… + +Tyler Wright: go ahead and deal. + +Anil Murty: there's a lot longer roadmap for console beyond that as well that we presented it accelerate Greg talk to a lot of that as well. But I dropped the link to four of those those are primarily focused around improving developer experience for people getting started with Akash, whether it's people coming from public clouds like AWS or people coming from platform as a service products like versaille or nicholify all of those types of users are going to be supported in much better within our caution within console. And then separately we're also going to work on a custodial experience for people that are not crypto native. So those are kind of the main things in terms of the developer experience and improving adoption of forecast site and then separate from all that. We are working on a provider console. So this will be a console for people that want to set up a provider. + +Tyler Wright: Thank you very much I think Anil also touched a touch on it and it was covered a lot during a classic accelerate but + +00:10:00 + +Tyler Wright: there was a proposal around some work that the human HQ team will do to contribute to again console. Thank you to all those that contributed in discussions again human HQ team gave discussions at Sid clients. They had discussions on GitHub a pre-draft discussion to Gage interest from the community that seem to be interest. They then continue to connect with members of the core product team and say clients and other meetings to get more feedback on the best approach went through a number of cases. And then again when it made sense, they put a proposal on chain which pass so thank you to all the validators at voter all the proposal and then again, they'll start to integrate their work into all that's going on with console under again Neil's guide and so again much appreciate to all those that participated in any part of that process. And again, we'll provide more updates on all their work in future steering committee. + +Tyler Wright: All right continuing to move along again. I know that during Sig chain as well as in the last steering committee Archer went into great detail about all the work that's happening on the engineering side regarding the upgrade to Cosmos 47. I know artur's been working with the rest of the engineering team on Next Step strategy roadmap for what again that upgrade will look like because it is a major event. The timeline is pending testing is scheduled for end of summer early fall, but please look out for future announcements whether it be through Sig chain or another special interest group. We're working group for folks that want to get involved in testing get involved and understanding the process how it will affect other parts of the Akashi ecosystem. So again, please take a listen. + +Tyler Wright: to Sig chain the last steering committee to go in depth on all the stuff that Archer covered with related to the cosmos 47 upgrade and then again, look out for announcements whether it be on the website or in Discord about next steps there for those that want to get involved. There's an item on this board where you can also track what's going on there. + +Tyler Wright: Does anyone have any questions on anything on the product and Engineering roadmap again, we discussed this in great detail a number of special interest group and working groups as of recently, but I do want to see if there's anything else that anybody on this call wants to discuss in more detail before we move on. + +Tyler Wright: All right. If not, then again next up is the community and marking initiatives one of the big things that I'll hand over the mic to Amanda Zach is around East CC there's a number of events going on in Brussels. So I want to hand over to Amanda who wasn't able to join the last year and committee, but I know that they're getting ready for all the events happening in Brussels. Amanda Zach do you want to spend a minute or so talking about what's coming up in Brussels and Beyond? + +Tyler Wright: Thank you nda. Again as the Akash team touches down in Brussels, insiders members of the core team alike. I'm sure there will be a lot of content that gets created and shared out of that to look out for, updates there from folks. That'll be on the ground. + +00:15:00 + +Tyler Wright: I know there's a number of other initiatives that are going on the community and marketing side. I wanted to see if there's anything that anybody wanted to discuss or had more questions regarding any Community or marketing initiatives. + +Tyler Wright: Go ahead. + +Tyler Wright: Thank you very much Zach. And Neil I saw your hand up and I saw you drop a message in the chat. Do you want to speak to it? Or I know people can read. + +Tyler Wright: And thank you very much while we're on the topic of flock. I will shamelessly plug a Blog written by Zach and a member of the flock team Matt Burke. That was just recently released So for anybody that has not seen that yet and wants to take a read again. Feel free. + +Tyler Wright: Cool, is there anything else on the community or marketing projects board that anybody wants to discuss? + +Tyler Wright: Go ahead Amanda. + +Tyler Wright: Thank you Amanda for that update. Anything else that anybody wants to discuss related to community or marketing initiatives or any of the project boards before we continue on with the agenda? + +Tyler Wright: cool + +Tyler Wright: All right. If not, then next up on the agenda is discussions. Again. There's a number of discussions that are happening. I would ask anybody that here. I know there's a number of people and I talk about this all the time, please look to get involved in discussions when you can. I know there's a number of people that reach out to me and talk about their opinions on discussions. I would ask that you make those public so that folks can hear your opinions get involved give feedback Etc. So again, thank you to all those I get involved in this discussions. There's a couple that I want to touch on. I know that there's a new discussion that went in there and we will discuss that I believe the person that put that forth is here today, but quickly before we do that there was one prior discuss + +Tyler Wright: And that participant has come to Sig economics a number of times and is just looking to connect and get some feedback from The Wider Community looking for that discussion right now. Pardon me. Perfect. But is Jeremy here? believe + +Tyler Wright: cool Excellent Jeremy. + +Jeremy Schipper: Yes, I am. + +Tyler Wright: I know that you have come to sick economics on number of occasions and put this discussion forth. I believe April 10th. Do you want to take a minute to just go over the discussion and look for again called action from the community to give feedback? + +00:20:00 + +Jeremy Schipper: Yeah, for Thank you Hi everyone. My name is Jeremy schipper. I'm coming over from shade protocol over on secret Network. Hope you're all doing well. I put up a proposal a while ago shade right now is going around to different really high quality Cosmos projects and seeing which community pools want to work with us. If any of you have read it essentially the entire idea is we would ask for proposal from your community pool and ours and we paired up on liquidity on our decks. Essentially we want to be able to expand a lot of people's specs liquidity for a lot of different teams. The biggest thing for Akash that we have seen based on feedback and a lot of the stuff that we do on secret network is the fact that all the transactions are private on secret Network. So essentially would allow for people to have + +Jeremy Schipper: entire setups and acquire their Akito a KT tokens highly privately because of secret networks decc privacy technology. And we're very open to doing this essentially whenever and whatever size a lot of people have suggested 50 to $75,000 worth and we're just looking for more feedback essentially on that. So happy to discuss it with anyone. + +Tyler Wright: Excellent again, if anybody has any specific questions or comments, I urge folks to get involved in discussions. But does anyone have any thing that they want to ask of Jeremy was here live with us today? + +Greg Osuri: So this also means you got acquired shd tokens. + +Jeremy Schipper: No, we would on Shd tokens from our community pool. And then you would do yours and then repair them against each other. So we would be on the other side of that and we're open to doing any sort of liquidity holding custody that you guys would suggest whether you have a liquidity Council trusted actors or just setting up a multi-date on speaker network, but we would be the other side of that pool. + +Greg Osuri: We got to figure out the logistics of this is interesting to the community. I don't have any particular comments generally speaking. historically we haven't used Community for liquidity needs. there is challenges of that approach from a legal standpoint from decent relation or not. And also because it's purely liquidity. It's not really enhancing the value of the product per se they're challenges as well as to how to handle this, logistically. Those would be my concerns. I don't really have any other further or the comments on it. + +Greg Osuri: Thank you. + +Tyler Wright: But again, there's been consistent conversation happening in the Sig economics Discord Channel as well as in sick economics monthly meeting. So I believe the next one is in a couple weeks, but I asked that if anybody has any other questions concerns or what wants to move forward with this idea and discuss it more feel free to drop those opinions and thoughts inside the discussion, please thank you very much Jeremy. + +Tyler Wright: Right continuing to move along again. I know that there is another discussion that is just submitted in the person that create that discussion is here. I wanted to see if sriram you want to talk a little bit about Russian in more detail. + +Sriram Vishwanath: Yes. Yes, thank you for the opportunity. Hello everybody. + +Greg Osuri: Before Shri Ramos. I want to give a little context for this proposal. So sriram is a professor at University, Texas. is a very well known and very much loved professor and he give a talk at accelerate which we just received very well by the community. And we also doing quite a lot of work and one of the big challenges for Akash to enable incentives is verification of compute. We all know what happens when you don't know how many of them paid attention to what's happening with several other networks where some networks took a very naive approach of not verifying actual compute the proviron and given incentive. So you guys civil attack, right? So verification is foundationally + +Greg Osuri: Important aspect for giving out incentives especially in permissionless or trust minimized environment and we couldn't find a better person to work on than someone and sriramically is he's gonna incredible experience and his resume speaks So for himself, and we're really honored at Shri decided to make a proposal to work on this very high level computer for So great. + +00:25:00 + +Sriram Vishwanath: Thank you Greg for that. It's very kind introduction. So folks. It's my pleasure to be here after having the opportunity to meet Greg in Anil in Cheng. I'm a big fan of not just that harsh but just the culture that you have. I think you have an amazing culture so very welcoming and open and I think how do I put this? I'm naturally very drawn to collaborating and working with you. So + +Sriram Vishwanath: Quickly on this. I think the goal ultimately is to do both hardware and software verifiable Computing software is a longer course. especially real-time I think is a substantial effort. But I think the good news is on the hardware front we can get started right away. The proposal here is to use an external what's called a secular enclave and a dongle. So standard USB interface a or c to be able to build verifiable hardware provisioning and essentially manage both identification and secure provisioning. To quickly summarize the approach here through a secure Enclave which has something called a physically and clonable function or path. You must have seen this in a ledger wallet or any Slim. It's the same concept. + +Sriram Vishwanath: you can actually both identify and check on the provisioning of particular a set of Hardware looking beautiful on one downloads enough for the whole cluster. We first plant to Select a set of Tes that would be compatible with the whole variety of operating systems and then to be able to build the mechanism and mechanism itself will be a pseudo random way of essentially making sure that the GPU is Benchmark correctly. So we'd give it a benchmarking task and if it matches the Benchmark for example RTX, 40 90 or similar, then it's currently identified as that particular type of hardware. + +Sriram Vishwanath: And then this certification is then securely signed within the te. And then provided to the Akash Network. So that's the plan we plan to do this at the university project. So I'm the professor, but they'll be graduate students and some undergraduates as well. But mainly led by graduate students. In the plan is to kick the surface AP. So that's the good news is that we'll get to hopefully not just excited bunch of young minds that hopefully involve them at much deeper level within our Network. + +Sriram Vishwanath: So the university is prepared a budget for it, which is also linked and the plan we'd like to do this as aggressively as possible. But we put down a two semester which is roughly for quarters plan here, but you'll see in terms of deliverables. We should be able to provide both the specification and a prototype pretty quickly and then hopefully, after sufficient testing we can handle this over to the a team perfect. So that's it in a nutshell. It's a very interesting project for me because both from a similar attack. And ultimately from a overall network security perspective, I think. It enables us to contribute to our cash Network, which makes me feel really good. So I'm looking forward to doing that. + +Tyler Wright: Thank you very much for putting together this very thorough Proposal with again deliverables budget team how you're looking to solve the problem. Does anybody have any initial questions that they want to talk to you about right now while we're all live. + +Tyler Wright: If not again, I know this proposal just went up but I would ask that everybody continue to read through the entire proposal. They have any follow-up questions that can drop those in as comments in the proposal and then I'm sure we'll get back and forth using the proposal using this as a way to go back and forth on next steps from there. + +00:30:00 + +Sriram Vishwanath: Perfect. thank you. for having me + +Tyler Wright: And please thank you. + +Tyler Wright: All right, if there's no questions on that proposal then again, we can go back to General discussions. I wanted to see if there's any other discussions from anybody that's here today that they want to talk about live. + +Tyler Wright: All then we'll continue to move along again. I would ask that everybody here and all insiders vanguards can continue to get involved in discussions or ask those that are looking to contribute to a class to get involved in some of these discussions and make their voices All right continuing to move along. Next portion is around open discussion. I don't see anybody that dropped anything in chat, but I want to see if there's anybody that has anything that they wanted to discuss with the group here today live. + +Tyler Wright: All right, I will take that as a no. All right, last portion is again the look forward. + +Tyler Wright: As previously mentioned there will be some continued changes to the schedule for the cigs and the working groups coming soon. But as previously mentioned the Sig economics working Sega economics is going to be happening July 3rd, next Wednesday following that there's a couple of other that'll be happening the following week sick chain and sick Community again as mentioned there might be some changes to the structure of Sig chain the formation of potential another Sig that we talked about in six support which will involve more members of the core engineering team. So look out for updates on Discord and then again continue to use his calendar on the Akash website as your source of Truth for all future things and working group meetings couple other things to call out are Sig design. There's a couple of folks that have been getting more involved in I sharing designs for swag. + +Tyler Wright: During designs for other marketing materials and some folks have been coming to the meeting some more graphic designers and visual communicators. Again, if anybody from the community knows anybody that's looking to get involved in Akash and is a designer have them again. Feel free to join the Sig design. And again, there's some folks that are either dropping in designs or have already dropped in designs to Sig design Discord Channel. Feel free to give your feedback on those designs so that we can either Look to add them to the store or have them for future events or give feedback for some of these newer community members are looking to contribute. + +Tyler Wright: Again, the cost website working group is continuing to move along. There's a number of contributions that happen there on a monthly basis or me on a biweekly basis. So again, if anybody wants to get involved in supporting the website or documentation, which is under the website feel free to get involved in that weekly working group. And then again, you can check out the rest of the addenda. + +Tyler Wright: Sid clients will most likely be removed because that is a monthly meeting and we just most recently met with a change of schedule just yesterday. But again, if anybody has any questions about console again, we talked about those things and steering committee or you can feel free to get involved in Sid clients Luna who was also very active with corsage his team and does a number of Open Source efforts with Akash also gave a demo of some work that he's been doing with his team for some time. So again, feel free to take a look at the state clients or recording in the notes which will be available in the next day or so to see a demo from corsage and then see all the work that again the console 2.0 the console team is working on for latest to console 2.0. + +Tyler Wright: There any other questions about anything that anybody wants to discuss related to Akash? + +00:35:00 + +Tyler Wright: If not, then again, I know this is a quicker steering committee than usual. But again, we just had one maybe 20 days ago appreciate everybody's time and effort today. Appreciate everybody that's been joining the Sig clients to enjoying a number of these cigs and getting involved again damir gave a presentation a demo of some work that he's been doing around grafana and Prometheus in sick providers just yesterday and also in the Akash insiders office hours today. So if anybody wants to get involved there, please take a look at the demo that he gave in sick providers and then reach out to him in the providers Channel or… + +Anil Murty: Thanks everybody. + +Tyler Wright: the sick providers Channel about next steps. + +Tyler Wright: But again much appreciative on time and effort today. Thank you to all though all that pitch their discussions. Please get involved in the discussions and we'll continue to connect online and look forward to all the events going on in Brussels and safe travels all those that are attending but I'll see you all in the Midwest. Have a great day everybody. All right. Bye. + +Meeting ended after 00:47:08 👋 From 3914c9fa286f108c7e7451ceaaf28f0d0928b28a Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Thu, 25 Jul 2024 16:52:47 +0000 Subject: [PATCH 111/138] Create meeting notes for Sig-Design #19 (#638) * Create meeting notes for Sig-Design #19 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 019-2024-07-17.md add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-design/meetings/019-2024-07-17.md | 75 +++++++++++++++++++++++++++ 1 file changed, 75 insertions(+) create mode 100644 sig-design/meetings/019-2024-07-17.md diff --git a/sig-design/meetings/019-2024-07-17.md b/sig-design/meetings/019-2024-07-17.md new file mode 100644 index 00000000..7e598608 --- /dev/null +++ b/sig-design/meetings/019-2024-07-17.md @@ -0,0 +1,75 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #19 + +## Agenda +- Introduction and agenda overview by Denis Lelic +- Presentation by Robert Del Rey on swag design ideas +- Discussion on Zealy platform and designer community engagement +- Presentation by Tyler Wright on YouTube strategy + +## Meeting details +- Date: Wednesday, July 17, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://ifqou2kkf6gqtmise2kelunxe2wc4xrcssgptlx3oh25flm7tcea.arweave.net/QWDqaUovjQmxEiaURdG3JqwuXiKUjPmu-3H10q2fmIg) +- [Transcript](#transcript) + +## Participants +- B S +- Denis Lelic +- Jigar Patel +- Robert Del Rey +- Tyler Wright + +## Meeting Notes +#### Introduction and Agenda Overview +- Monthly SIG design meetings cover design-related topics and marketing initiatives. +- Focus on event-related design elements such as booth and swag design. +- Plan to update and gather ideas for swag items and explore new marketing strategies. + +#### Swag Ideas Presentation +- **Robert Del Rey** shared a dashboard for Zealy, a platform for community builders to engage with members through customizable missions. +- Introduced the "Akash Designer" mission to create unique designs for Akash community swag. +- Discussed guidelines and requirements for the mission, including proper licensing for stock images. +- Sought feedback on structuring the mission and incorporating community feedback. + +#### Zealy Platform and Designer Community Engagement +- Consideration of designer community engagement through Zealy to create new swag designs. +- **Denis Lelic** expressed the importance of ensuring proper licensing for any stock images used. +- **Tyler Wright** suggested reaching out to design communities and tracking the performance of the Zealy mission over a few months to evaluate its effectiveness. +- Agreement to provide examples of mock-ups to maintain consistency in design submissions. + +#### YouTube Strategy Presentation +- **Tyler Wright** emphasized the need to improve Akash Network's YouTube presence, which currently has 3.6K followers. +- Proposed a two-phase approach for YouTube improvement: + - **Phase 1:** General cleanup of the YouTube channel, improving descriptions with calls to action, and creating playlists. + - **Phase 2:** Regular updates and content management, leveraging community support. +- Suggested forming a working group to handle the YouTube overhaul. +- Discussed setting goals for the YouTube channel, such as increasing subscribers and producing YouTube Shorts from existing videos. +- Highlighted the importance of collaborating with content writers and leveraging past branding elements. + +#### Wrap-Up and Next Steps +- Continued discussions on both swag and YouTube improvement items will take place on Discord. +- Upcoming website meetings next week to discuss product design and other issues. +- Encouraged attendees to join future meetings and contribute to ongoing initiatives. + +## Action Items + +1. **Robert Del Rey:** + - Finalize the "Akash Designer" mission on Zealy, incorporating feedback from the meeting. + - Ensure proper guidelines and disclaimers are included for design submissions. + - Coordinate with Denis Lelic on Discord to complete the mission setup. + - Lead the reorganization efforts for the Akash Network YouTube channel based on the working group's decisions. + +2. **Denis Lelic:** + - Assist Robert Del Rey with the implementation of the "Akash Designer" mission. + - Provide examples of mock-ups and ensure consistency in design submissions. + - Coordinate with Tyler Wright to establish a working group for the YouTube channel overhaul. + - Revisit past documents and branding elements with Joe to identify useful content for the YouTube channel. + +3. **Tyler Wright:** + - Track the performance of the Zealy mission over a few months to evaluate its effectiveness. + - Organize and participate in the working group sessions for the YouTube channel overhaul. + - Set up a dedicated YouTube working group channel on Discord. + - Schedule weekly sync meetings for the next three weeks to ideate and plan YouTube strategies. + - Invite Joe to participate in the working group sessions and leverage his previous work on YouTube content. + +## Transcript From 26dc5564c6b0837664aa050c51d9c85cc818085a Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Thu, 25 Jul 2024 16:54:57 +0000 Subject: [PATCH 112/138] Create meeting notes for sig-client #16 (#629) * Create meeting notes for sig-client #16 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 016-2024-06-25.md added transcript chore: add recording link Signed-off-by: Drinkwater * Update 016-2024-06-25.md added recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-clients/meetings/016-2024-06-25.md | 600 +++++++++++++++++++++++++ 1 file changed, 600 insertions(+) create mode 100644 sig-clients/meetings/016-2024-06-25.md diff --git a/sig-clients/meetings/016-2024-06-25.md b/sig-clients/meetings/016-2024-06-25.md new file mode 100644 index 00000000..6ecd5373 --- /dev/null +++ b/sig-clients/meetings/016-2024-06-25.md @@ -0,0 +1,600 @@ +# Akash Network - Clients Special Interest Group (SIG) - Meeting #16 + +## Agenda +- Updates on Human HQ Team's Work +- Updates on Console Activities +- Presentation on Go Client Libraries by Joao Luna +- Demo by Joao Luna on Web3 Platform +- Summary of Near-term Plans for Console Improvements by Anil Murty + + +## Meeting Details +- Date: Wednesday, June 25, 2024 +- Time: 08:30 AM PT (Pacific Time) +- [Recording](https://g4sync4igp5y56x5cxfhh45vo4elgdzmcptwja4z33gcjhzkkoqq.arweave.net/NyWGi4gz-476_RXKc_O1dwizDywT52SDmd7MJJ8qU6E) +- [Transcript](#transcript) + +## Participants +- Anil Murty +- B S +- Deval Patel +- Dominikus Brian +- Jannick H +- Jigar Patel +- Joao Luna +- Julius Haus +- Maxime Beauchamp +- Maxime Cyr +- Scott Carruthers +- Tyler Wright + +## Meetings notes +- **Welcome and Meeting Overview** +- **Tyler Wright:** + - Tyler Wright welcomed everyone and explained the change from a monthly to a bi-monthly meeting. + - Emphasis on updates from various clients and their work. + - Recap of the Human HQ team's demo and their transition to on-chain deployment from GitHub to Akash network. + - Collaboration with the console team, proposal passed on-chain. + - Recognition of the Human HQ team's efforts. + - Tyler mentioned potential changes to the meeting day and time to accommodate global participants. + - Appreciation for attendees joining despite time zone challenges. + - Availability of updates on the product and engineering project board. + - Representatives from the console team (Maxime Beauchamp, Jigar Patel, Deval Patel) available for in-depth updates. + + +- **Presentation on Go Client Libraries by Joao Luna**: + - Joao Luna has been working on the client library for some time. + - The library is part of the core codebase at Akash and is accessible for deeper exploration. + - The goal is to make the library open source, allowing broad accessibility. + - Demonstrated the usage of the Go client library with Akash API, focusing on fee grants. + - Highlighted the benefits of the library in abstracting complexities for developers. + - Provided an example of a deployment using fee grants, shared a URL for demonstration. + - Discussed the potential for integrating memory keychains and other improvements. + +- **Discussion on Leveraging Go Client Work for Akash API by Scott**: + - Scott Carruthers is interested in using the Go client work for further development around Akash API. + - Joao Luna explained how the library simplifies interactions with Akash API and supports various integrations. + - Discussion on managing deployment with different depositors and leveraging fee grants programmatically. + - Scott and Joao discussed potential methods for sharing code and collaborating on documentation. + +- **Demo by Joao Luna on Web3 Platform**: + - Joao Luna presented a live demo of a Web3 platform he has been building for over a year. + - The platform aims to provide a cloud experience using decentralized protocols, offering features similar to traditional cloud platforms like AWS or Google Cloud. + - Users can create their own cloud with high availability setups, select data centers globally, and integrate storage with Akash compute. + - The platform is currently live in a beta state and is open for beta testers to help scale and identify bugs. + +- **Platform Features**: + - Login options include standard login or GitHub integration. + - Users can add credits to their accounts with straightforward billing; no surprise bills as users set a budget limit. + - Marketplace (to be renamed Templating) allows users to create deployments with a user-friendly interface without needing to understand SDL. + - Users can configure ports, container commands, arguments, environment variables, and GPUs. + - Deployment status can be monitored in real-time, with access to logs, billing information, events, and revisions. + +- **Deployment Example**: + - Joao demonstrated creating a deployment using the platform. + - Highlighted the ability to deploy services like Grafana on Akash network. + - Deployment management includes choosing trusted providers and maintaining high availability by redeploying to other providers if one goes down. + +- **Q&A and Discussion**: + - **User's Balance**: Balance is held in USD, not tied to any cryptocurrency. + - **Custodial Wallets**: The platform uses a mix of individual and special wallets to manage deployments. + - **Fee Grants**: With the latest network upgrade, fee grants are utilized to streamline token and wallet management, enhancing operational efficiency. + - **Currency Pools**: There's potential to support stable currencies like USDC for more stability and equilibrium-based systems in the future. + - Joao Luna completed his demo, emphasizing the platform's ability to manage decentralized cloud services efficiently. + - Joao highlighted the upcoming use of fee grants to improve operational efficiency. + +- **Anil Murty's Summary of Near-term Plans for Console Improvements**: + - Anil shared a summary on Twitter and detailed plans on GitHub. + - **Feedback-driven Improvements**: + - **Private Container Registries**: Essential for AI/ML developers who prefer keeping their container images private. This feature has already been shipped. + - **Support for Standard Linux Images**: Mimicking AWS/GCP/Google experiences by allowing users to SSH into VMs with standard Linux images. This will be integrated into Akash to simplify user experience. + - **Automatic Build and Deploy**: Targeting web developers from platforms like Vercel or Netlify who are not infrastructure-focused. This will streamline the process from code to deployment. + - **Custodial and Non-Custodial Wallets**: Supporting both custodial and non-custodial experiences to attract non-crypto users, providing a seamless, non-wallet-based interface. + - **Praetor Integration**: + - **Unified Frontend**: Integrating Praetor’s functionality within the Console to simplify provider management and improve user experience. + - **Storage Solutions**: Exploring integrations with StoreJ, Filecoin, etc., and making these accessible through a user-friendly UI. + +- **Open Discussion**: + - **Questions and Feedback**: + - Questions were raised about the implications and rollout of these new features. + - Anil emphasized the importance of these improvements in removing current barriers to Akash adoption and enhancing the overall user experience. + +- **Further Discussion by Anil Murty**: + - **Periodic Data Backups**: Emphasized the importance of enabling users to easily back up their data periodically, particularly for users who host services that require persistent storage. + - **VM Access Concerns**: Addressed a query from Dominikus Brian about SSH access to VMs. Anil clarified that due to Akash's reliance on Kubernetes, direct VM access isn't feasible. Instead, users can SSH into containers. + - **Micro VMs**: Mentioned the potential future exploration of micro VMs, although it would require significant effort to implement. + +- **Joao Luna's Feedback and Discussion**: + - **User Experience with VMs**: Joao raised concerns about the user perception of running VMs on Akash. He noted that users might face limitations when running Kubernetes clusters within containers, which could lead to confusion. + - **Messaging and Expectations**: Anil agreed that clear messaging is crucial. The primary objective is to provide users with a familiar experience by allowing easy SSH access from their terminals. + +- **Open Discussion and Questions**: + - **Dominikus Brian**: Asked about SSH access and its limitations. + - **Joao Luna**: Suggested exploring alternative solutions for VM-like experiences, considering the constraints of running containers within virtualized environments. + +- **Joao Luna's Final Question**: + - **SSH vs. Shell Connection**: + - Joao Luna: Asked why shell connection isn't an option currently. + - Anil Murty: Explained that users prefer using their own terminals, and there's a bug in the current shell causing session breaks when the provider restarts. It's on the core team's roadmap to fix this issue. + - Maxime Beauchamp: Added that users generally prefer SSH through their own terminal. + +- **Unrelated Query from Jannick H**: + - **Ledger Amino Sign for Akash JS**: + - Jannick: Asked if signing transactions on the Akash console frontend with a ledger is planned. + - Anil Murty: Stated it's not currently planned as it's the first request. Akash JS is open source, and contributions are welcome. + - Tyler Wright: Encouraged discussion on this topic in the Akash JS Channel on Discord for further feedback. + +- **Discussion on Awesome Akash Repo Cleanup**: + - Tyler Wright: Mentioned ongoing cleanup work by PiberDev on the Awesome Akash repo, seeking feedback from the Sig clients. + +- **Closing Remarks**: + - Tyler Wright: Thanked participants, highlighted upcoming meetings (Sig support, Sig providers, and the working group for Akash website and documentation), and urged continued engagement on Discord. + +## Action Items +1. **Joao Luna**: + - Continue refining the platform based on beta testing feedback. + - Explore additional currency support and further integration with Akash's latest features like fee grants. + - Collaborate with Scott Carruthers on leveraging the Go client library for Akash API development and documentation. + - Plan for making the Go client library open source and provide initial access to interested parties. + +2. **Scott Carruthers**: + - Develop engineering documentation for integrators, incorporating examples from Joao's work. + - Coordinate with Joao Luna on code sharing and collaboration. + +3. **Tyler Wright**: + - Continue facilitating discussions and collaborations within the group. + - Consider adjusting the meeting schedule to better fit global time zones and accommodate more participants. + +4. **Console Team**: + - Continue providing real-time updates on the product and engineering project board. + +5. **Anil Murty**: + - Oversee the implementation of new features and ensure they align with user feedback. + - Continue updating the community on progress via Twitter and GitHub. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: Alright, welcome everybody to Sid clients. This is now a monthly meeting. It's June 25th. 2024 again this meeting used to be a monthly meeting but due to some teams at some clients that are currently building not having the time to meet and a number of things have been happening with around console the folks at the meeting in April. Talked and we've had some gender more General discussions that we've changed this meeting to being every other month during these meetings. We'll get updates from various clients and all the work that they're doing. + +Tyler Wright: At the last meeting, we got a demo from the human HQ team on the work that they has since been gone on chain for the effortless deployment from GitHub to the Akash network via the cash console. Again, human HQ team led by piersch went through a number of different steps. They gave a couple of presentation's at various sick clients meetings had some pre-draft and just draft discussions got some input from the community met with the console team. + +Tyler Wright: And got some input on how they would make some changes added to awesome Akash as a repo and then again most recently put a proposal on chain for the work that they'll be undertaking over the next six months along with the console team that proposal passed on chain this morning. So again, shout out to all the work on the human HQ team led by Peach and I'm sure there'll be further updates on all the work that they'll be doing with. console team moving forward + +Tyler Wright: Cool, in addition to that again, there's a number of items that I've put on the agenda for folks. So again, thank you to those at had some issue with Discord events much appreciate everyone's time moving forward. I will try to adjust the time and most likely the day of this meeting. Tuesdays is just quite a busy day for members of the product team and core team. So I may change the date of this meeting on a monthly basis and then move the time a little bit earlier because I know some folks that are based in Europe Asia and elsewhere. It's quite late for so I appreciate those folks taking the time to join us today. + +Tyler Wright: All So again I know we have a full agenda one of the things that we'll talk about a little bit later is get an update on all things happening with console for folks that want to see what's going on. I know the console team when we have a number of Representatives here today the Max's here today as well as jigar and Deval if you want to see what's going on again, we'll get some updates. In depth today, you can always track all the various items being worked on the product and engineering project board. Again. The console team does a great job of updating this board in real time. + +Tyler Wright: But before we get to updates on the console again, if anybody has any other agenda items that they want to add please feel free to drop those in chat. One thing I wanted to discuss at the top was go client libraries. This is work that Luna has been doing for for some time and it's been implementing it into some tooling that he'll give a demo on later. But I know that Scott is looking to leverage some of that go client work as he continues to do some work around their cache API. + +Joao Luna: Yeah, thank you. So, yeah, I've been working on the client virus for quite some time. + +Tyler Wright: So I just wanted to see Luna there's an update that you had on go client Library. + +Joao Luna: It's part of our core codebase at Kozak and… + +Tyler Wright: It's accessibility for folks that want to take a deeper dive and… + +Joao Luna: it's something that Indian goal is to be open source. And for everyone I did a demo I think a couple months ago. + +Tyler Wright: then maybe like a quick demo or… + +Joao Luna: I think it's not the one year yet. + +Tyler Wright: quick update all things there. And then I think the next agenda item that we want to talk about is maybe Luna some work that you've been doing on in regards to heart as you maybe want to share. + +00:05:00 + +Joao Luna: It was some time ago since then we've evolved it now. We are using the cash API. So it's something that takes full advantage on the cash API and… + +Tyler Wright: + +Tyler Wright: A Passover. + +Joao Luna: it's compliant with everything there. + +Tyler Wright: Do you Luna to give an update on the go client libraries? And then Scott if there's any initial questions that you had outside of just general access we can take some time here today. + +Joao Luna: and as of the latest Network upgrades with the frequents, our newest features is obviously the support for the fee Grant and… + +Tyler Wright: So Luna, I'll kick it over to you. + +Joao Luna: obviously which allows for A limitless list of Integrations to happen and you can build all sorts of backends and have all these. + +Joao Luna: management of the points much more easily and they are quite thrilled about it. I have a couple of examples on the repository that's using sandbox and I can show you how it works and then we can ask questions. We can enter a little bit of detail and regarding access to the code and all that. Can then discuss further. + +Tyler Wright: Yes. + +Joao Luna: Okay, so this is gold code. Let me know if you're not familiar, but I'll try to get this easier to understand. So as you can see here on the left side, these are all examples of Snippets of code that you can run and test the library is working. As I said, this is combined with a cash API. I know there's plans to build an SDK around the cache API in generate all these apis for different languages. What we are trying here to do here is to have semantic way of using those apis more user friendly for the developer and more focused on the actual. + +Joao Luna: Use cases of the cache Network so users of this API don't really care that we are sending transactions to a blockchain what they want to be able to do is I want to quickly deployment. I want to check my list and have we often interface for them that allows them to do this programmatically without having to worry about Cosmos SDK transactions signing gas fees, whatever. We try to obstruct the most that we can that lead that's possible. Of course. + +Joao Luna: So yeah, we have a bunch of examples. I've shown you before to get deployments or get providers. where you can actually run and get a provider what I want to you to show you today is our latest example, which is basically a full deployment. This goes through the full process of deploying but using the feed grants, so we actually have to accounts on Sandbox one will be the grantor which will basically Grant access and permissions for a deployer to perform actions on it's the health basically a deployed with no way KT will be able to use the APT of the grantor to perform actions and here we do like publishing a certificate creating a deployment and the lease and manifest and also finding the department account. + +Joao Luna: And so before typing is the code what I can show you is basically running the example. This will take a couple of seconds, but we'll have a bunch of logs and at the end you'll see an URL and we'll access and see that it's deployed. And then we can go a little bit through the code just for you to see the structures and what interface looks like to interact with this. + +Joao Luna: Should take a while. + +Joao Luna: Okay, so here we have a transaction. Keep going. + +Joao Luna: I have a bunch of sleeps here. So this is why it takes some time because I'm waiting for the deployments. But now we do get all these and we get a URL I'll share with you and you can check that. It's working. Let me just put we HTTP so you can click it. And you should be able to click and see a deployment. That's basically an nginx. Hello world deployment. As you can see I've also added funds to this deployment and if you want to further check, you can go to the deployer address on Sandbox. I'll share with you and you can check the transactions being done. + +00:10:00 + +Joao Luna: Yeah, so this was all done with basically the funds from a grinder, which was the latest feature that was introduced on the latest Network upgrade. before diving into the code any questions and we want to say + +Tyler Wright: Go ahead. Don't me. I see your hand. + +Dominikus Brian: Okay, I have one. So with the latest features in console, we can choose which Grant right in this case of yours. We can also choose. By giving these different string. + +Joao Luna: of course. exactly, so + +Dominikus Brian: And can you have a list of them and then just pick? + +Joao Luna: basically you say for instance. Let's say here when you are finding a deployment. One of the things that you say you have to pass the positor so you can't really have a list what you can do is have your own list and then accordingly just choose a depositor based on that. So you can do that programmatically. It's not supported by the API with something that perhaps doesn't make sense for everyone. So we try to offer an equilibrium between what's simple and makes sense. And what's useful. + +Dominikus Brian: nice probably + +Joao Luna: But you can specify a depositor, of course on the funding of the deployment and on the deployment creation as well. You basically do let me see here as well. So the create deployment options also added a depositor address. + +Joao Luna: Yeah. Yeah, So this depositor don't need to be the same as long as you have you have for the address that's deploying. It's all fine. And that can be seen being done here somewhere Health secrets basically are saying that we have this granted address this the point address and we are setting a spend limit of 1880 and with an expiration of one year. + +Joao Luna: from today + +Joao Luna: That's our goal. Yeah. Thank you. + +Tyler Wright: Thank again access I know this is something that is currently not open source, but there is an intent to make it open source of more people that can interact with it. Is there a plan for that or can we take initial steps to give some people access a Scott and then I just want to follow up Scott that you have any questions that you had at this time? + +Scott Carruthers: Yeah, no, I don't have any questions + +Joao Luna: I saw your message about the access. My only concern is that because it's a private organization. I don't know if I have to pay for a seat to give access to someone to do that private, but that's something we can take offline and discuss and in the limits of things we can just go through the code on a call run share the ID and have a remote developing session where Scott can try. Yeah, I'm open for finding kind of solution. + +Scott Carruthers: yeah, so as the more I think about it Luna I could just reach out to you directly and it could probably just be as simple as if you just wanted to share something and adjust or Even just in Discord provided to me directly. So let me Take a step back just to give you some insight. The reason for my current interest is. I'm going to start developing. More engineering documentation for integrators. So we want to make it very frictionalist to Interact with a cash card base and Akash API. So this won't be a matter of creating a client Library. It would more be a matter of bringing them through examples of how they would interact with the API and I just want to as I go through constructing some of that if we were using some more strategies than some of that documentation would + +00:15:00 + +Scott Carruthers: Yes, some of that documentation would also speak into what you so it just said as an example of creating a deployment. I'm sure we would use very similar techniques but it would be good. If I just had inspection of the code that you're using and what I would suggest then documentation and try to get some cohesity there. So as I'm going through that and I'm going through a creative deployment example, I can just reach out to you and maybe you could just share with me directly. They create deployment example, and that's probably fine for now. + +Joao Luna: Yeah, trying to make sense. Some of the problems that we solved are also not really related to Akash, but more on the cosmos SDK and how we can import Keys all these keychains because we are not using operating system keychains. We are using in memory and those have some quirks when you are Building Services. You don't really want to use the OS ones you perhaps want to use the memory keychain. There's some quick works that we need we had to do to get it working some importing methods that we needed and we solve those problems or perhaps we can cooperate that and then if it's open source, it's just like the standard way of doing things we can agree on. + +Joao Luna: But yeah, so this is that the more complex example, then I can also just show you running something very simple you can do is just for instance querying providers as you can see. This is the cache API. So it's fully compatible with the cash API. We didn't want to introduce more complexity because if we think that we want to open source this and move this to the cache Network organization. We don't want to offer a different API with a different set of data interfaces than the developers of the Akash Network people that use the API will be used to so we decided to keep the same abstractions, but just offer more semantic way of interacting with the network some way that's cleaner makes more sense and has no blockchain quirks here and there so we try to abstract not just possible. So for instance getting a specific provider is + +Joao Luna: creating a request and then just get provider with the request. This is very very simple example and books very clean. And gets you Another thing that I want to point out is that this is a go Library that they're not really code generated from a set of protobufs. We have some control over the interfaces that we provide and we can do some useful or some more like standard or cleaner way of doing things. So for instance when you are creating a deployment. + +Joao Luna: One of the things that we do is accept IO reader when we are building the deposit the message. So what this allows is, we are offering a standard Library interface our Channel way of using this library and this sdl reader can come from any kind of IO reader. This can be a file Network socket a stream whatever you can basically deploy as long as it's respect this interface, which is standard gold length stuff. So it opens a lot of possibilities. So inside of reading a nasty out from string and passing it through + +Joao Luna: Is just whatever you have a reader is supported so you could be receiving streams of sdls and creating the partners. Theoretically if that's your use case, but this is the design that we had in mind is that's make this the go way and… + +Dominikus Brian: I have one last one. Perhaps pretty simple,… + +Joao Luna: then interact with the cash networking that go away. Kind of thing. + +Dominikus Brian: but when we have several of this clients for instance trying to deploy using the same address and… + +Joao Luna: And yeah, that's pretty much it. + +Dominikus Brian: everything parallel operations will there be conflict? + +Joao Luna: There's one limitation but that's solved in the new Akash API and solved in this scope client. So basically imagine you sent two different. Operations to the network not queries, but transactions programmatically in parallel. They would to be two different transactions with basically the same sequence number and… + +00:20:00 + +Dominikus Brian: I see but in the case of deployments for instance. I want to deploy us the hello world example you have… + +Joao Luna: that's not allowed you can only send one per + +Dominikus Brian: but to three people instead of one,… + +Joao Luna: One per block. + +Dominikus Brian: so I'll want to deploy three times together. + +Joao Luna: What you can do is basically send an aggregate operations and… + +Dominikus Brian: You could and… + +Joao Luna: then send multiple messages on that same transaction,… + +Dominikus Brian: you do it better inside, one program or… + +Joao Luna: and that's currently support. + +Dominikus Brian: you run several of them together. Because running several might be problematic right because they're using the same address. They are trying to + +Joao Luna: You could. + +Dominikus Brian: + +Joao Luna: As long as you keep when here I'm not sure we are entering a realm where you have these parallel or concurrent stuff. It's not clear for me. + +Dominikus Brian: The first option I guess safer. + +Joao Luna: Perhaps Scott has more experience or… + +Dominikus Brian: Yeah. if just looping together and… + +Joao Luna: has dealt with this because I did multiple transactions,… + +Dominikus Brian: then deploying one by one because from your demo just a few seconds,… + +Joao Luna: but I never did multiple deployments. And I think makes sense. + +Dominikus Brian: so you can actually + +Joao Luna: It would work as long as you're sending the messages in the sanction transaction. There's no problem. You don't have to wait for another block. To be able to do that. So I can't see that happen again. + +Joao Luna: Yeah, but It What you ask makes sense and I got into the issue on the terraform provider client as well because I was deploying my infrastructure with the telephone provider and at some point I was doing parallel just to optimize and we were entering conflicts because we are doing many transactions on the same block which was allowed. + +Joao Luna: But that's something that initially you can encounter… + +Tyler Wright: I do want to leave some time for again a short demo from Luna on… + +Joao Luna: but it solves here because the transaction support multiple messages and it's pretty easy to do that now. + +Tyler Wright: what he's been building and then dive into all the work that has been going on around the console 2.0. + +Joao Luna: And that's thanks to the new Akash API code base. + +Tyler Wright: Does anyone have any additional questions here I saw that you were unmuted for quick second. + +Joao Luna: nice + +Tyler Wright: Didn't know if you wanted to chime in or if we just want to move on. + +Tyler Wright: Perfect. Thank you. + +Tyler Wright: Yeah, yeah. + +Joao Luna: Okay, I guess then it's the other demo. I'll try to be quick about this one and hopefully it works. It's a live demo. So I'll share my screen. + +Joao Luna: Yeah. + +Joao Luna: Yeah. + +Joao Luna: So very quick very briefly. This was a platform that I was building for one year I think on my free time but things will just accelerate and we were having fun with it. So we kept building the idea overall is to have a platform that increase a bunch of web free on the deep in protocols and offer the regional experience traditional Cloud platform experience, but where you and your Enterprise can build your own cloud kind of thing. + +Joao Luna: and that their own called platform tailored to your needs where you can have your high availability setups. You can have your nodes or your data centers that you choose across the globe. You can integrate storage with cash computes in various ways. That's kind of the vision is you build your own cloud and you have your traditional Cloud platform that you're used to AWS Google but using all these decentralized protocols and basically have it more like educative and so Enterprise grade kind of features such as high availability load balancing and all that. so yeah, currently it's + +00:25:00 + +Joao Luna: I'm running this on a local environment it is life, but it's open for better testers because we don't want to have many people accessing. just yet just to scale properly and not planning to many issues right away and + +Joao Luna: and ruin the user experience. So it kind of like uncovering a bugs here and there are experiences that are not that great. But this is like a brief landing page, but what's really interesting here that can basically log in or you could use GitHub as well. It's already supported. It's quite the easiest way to + +Joao Luna: to go about it, but I already have my account. I also already have balanced. So I'm not going through the process but we want to have the most straightforward way of adding credits to your account. You basically pay as you go you have your credits. You don't get surprise bills like you have to pay $1,000 because you left the deployment here. It's like you reached your limit that you set from the budget. Then the deployment gets close you get of course warnings, but it's close. You don't pay overpay or whatever but the billing page we are still building. This is very better but I can show you here creating a department basically and this kind of like Marketplace Michael places that name we are trying to change to templating and one of the things that we have currently is basically and hello world engine X is the same example that I did before so why it does he's kind of prayer feels these four basically have a + +Joao Luna: Choices here you can go for your ports. It can have container command arguments. Let's start our stuff that you are used to add variables the gpus with and as you can see it's a very traditional experience. So forget the sdl that's not something everyone we want users to worry about is you are kind of like in Google Cloud platform or Hefner and they're creating your own server. So you feel this and you basically just create. And you have your deployment then we just need to wait for it to the point. So it shouldn't take long. I'll just keep refreshing and see and we can see. + +Joao Luna: In the meantime, what I can do is show you this page, which is basically the page that will allow you to overview what your D cloud looks like so basically the group of providers that you trust in shows for your own cloud and this is kind of like the page. So I chosen for the form for this demo and currently the Europe plots The Foundry digital this in North the overclock and the three Akash Cloud providers. Then I can have more details on the providers. it shows you a page with attributes. We have as Telemetry not in this environment. You'll have all sorts of data. This is these pages of course being worked in. It's kind of raw still. + +Joao Luna: But yeah, We have the points status. Let's see. Okay, I'll click logs. Hopefully this works. Sometimes it doesn't so you have access to your logs. You basically have a bill this is your active bill for that deployment. What it says basically is that how much you'll pay it pays every hour and this is wrong you pay every hour. And yeah, that's pretty much What can happen is if your deployment on your provider goes down. + +00:30:00 + +Joao Luna: you can choose for you to be automatically deployed to another one and you'll just have a new bill for that provider. So you can keep up to date with the pills. that are active at the moment. The other one would be inactive and the new one will be you then have events what happens so everything went smoothly revisions is the updates on deployments. So if you update your image, you'll be able to see when did you upgrade that image? And what's the current one? So this is what we call revisions. It's the same kind of language that you called platform uses Google Cloud. So it's deployed the four parts none. So we have where else and then I can click it's being hosted on your plots. And we're getting service department available. Not sure matter if it's + +Joao Luna: airport error. It's not there for 04. So, let's see if I delete it. I should see it 404 + +Joao Luna: eventually + +Joao Luna: Not sure if something's wrong with the robot provider. + +Joao Luna: it's offline now. they all need to check what I can try to do and I think that's pretty much You can ask questions different also have documentation. In the meantime. When you gather your questions. I'll try to show you an example deployment, but feel free to ask any questions. + +Joao Luna: JD is to have this as an enterprise-oriented solution for the point on a cache and other. Solutions it's currently we only support the cache and for compute that's our main focus really. We haven't considered any other options, but for storage we are looking for other networks and then offer a layer of integration between those networks and offer some Enterprise solutions that you can't get from being like let's say a layer one platform on a car. + +Tyler Wright: There's a question in the chat. + +Joao Luna: So for instance that some limitations that Make sense that a cache network has that can only be overcome… + +Tyler Wright: It's a user's balance in usdc or Akash on chain, or is it not and + +Joao Luna: if you have a platform built on top of it. that has the higher level set of features. So basically you kind of like sacrifice control. Over offering this features. What we want to do is give people the control to Be able to make the informed decisions on what they want to sacrifice in terms of. Fine-grained control and get good features like high availability. But yeah, that's kind of like the + +Joao Luna: the bridge that we are trying to build kind of thing. Let me just check if the funny is working. Okay, so the professional deployment is working perhaps it's the other image. + +Tyler Wright: go ahead and you? + +Joao Luna: So yeah. As you can see I can log in and I have graphana deployed on a cautionary. So wallets, just The traditional product experience you would expect from a cloud platform. + +Joao Luna: It's nothing it's our own. it's your dollars, basically. It's like having dollars in your bank account, I think. It's not tied to any cryptocurrency. We don't buy cryptocurrencies with your fans. So for instance. it's possible that if you purchase credits on our platform and for some reason it wanted to refund it's your dollars so it would be You don't purchase crypto. It's just you share this link with a friend. That's never heard. + +Joao Luna: What sorry what's used for the appointments underneath in your custodial wallet? It's the cash go client library that we are building. So these are being built and in. + +00:35:00 + +Joao Luna: Does that answer your question? + +Joao Luna: First thing is that we don't use just one wallet. So we have our own separation of + +Joao Luna: Deployments let's say the point agents or wallets what the currency that we are using we currently have a system where you have a bunch of pools of tokens. We currently have one active pool of akt but ye is to support whichever currency are supporting for us. I think it would even be better to have perhaps who DC. I don't know just have a more stable pool. Perhaps can do some equilibrium based something real developing. + +Joao Luna: a Deval + +Joao Luna: Okay, and you can leave your questions in the chat as well and I can still answer. + +Joao Luna: So currently what we have implemented is a mix so every user has its own wallet, yes, but then we have a couple of special walls that serve some purposes And one of the things that we are building now is because of the latest Network upgrade. We really want to take advantage of the feed grants. And that will help a lot on the operations that we do behind the scenes. We have a bunch of services that have to manage all these tokens and wallets and with this picture that's basically gone, which is great. So that's why I'm really happy for that feature. + +Anil Murty: Thanks, Hey everyone. So actually did a quick summary of this on Twitter. I don't also put a more detailed version of that in GitHub as well. But I kind of wanted to highlight what the near-term plans are as far as improving overall experiences and console is so the link that I put on Twitter. I just kind of summarize that in this document as well, but for the new term objectives everything that we're going to be doing is Driven by the feedback that we've gotten from many of the pocs that have done with customers. We have a whole bunch of videos. He's going on you probably heard about the integration of flock you've heard about the integration with neural AI with brev with the whole bunch of these customers and partners and what we've learned from that is four or five things. And so that's kind of summarized here. + +Anil Murty: The first thing that we learned was that a lot of AI and ml developers today. We just kind of the group of people that are driving a lot of demand for gpus right now. They like to be able to keep their container images private and so supporting private container Registries in the core of the product as well as within console for deployments was kind of number one and that's actually shipping now. So it's shipped in it's available. The second one we realized was many of the customers and partners that we speak with particularly on the web to side. They come from products like AWS or gcp or Azure Deputy public clouds, even tier one or two public clouds and the most common workflow there obviously is like if you're going to gcp today and you spinable VM what you get typically is the option to pick a given Osage. So typical Linux image, you're going to LTS 24 version 24 or + +00:40:00 + +Anil Murty: Your red hat Enterprise Linux or one of those and typically users are able to pick one of those options configure the hardware that they want in terms of CPUs memory storage all of that. And then what they end up getting is a way to SSH into that virtual machine and be able to download any of the applications are any code that they would like whether it's models or data or pytorch or anything really any Frameworks that they want to develop with. So people expect that sort of an experience when they come into our cash as well. But what they get is basically experience right now where we expect people to be able to containerize the image and put that and be able to work with that so offering something that is closer to, playing Linux images kind of number two, and so one of the things you'll see on the project board that I was talking about is we're going to be building your workflow where we offer, really build images for the most commonly. + +Anil Murty: Bistros and then give people the option of either dropping in their public keys or generating a public and privately combo and then using that public key to essentially give them access to SSH from their own terminals into this container image. That's a plane relax image and then the user canvas the access HT into that container image. They can download any applications. they can download by torch whatever they like. So that's kind of number two. + +Anil Murty: Number three is automatic build and deploy. so this was finally targeted towards people that are infrastructure Focus people coming from AWS and gcp and Azure. This next thing is targeted towards people who are coming from web to products but are not infrastructure focused. So these would be typically people that are fewer web developers who have never worked with direct infrastructure. I've never spun up, VM in AWS or gcp. They typically work with platform as a service products so past products like for sale or netlify that essentially abstract away. + +Anil Murty: The underlying infrastructure and let people just be able to deal with code. So if you're a web developer and you go into something like a versal experience What You Get There is the ability to just have your react application sitting in GitHub or gitlab or big Market or one of the Version Control Systems be able to just connect that to us and then have whistle pull all the code build it for you and then give you a deployed version of that application. So what you don't have to worry about is Bill process and the infrastructure has been a process. So this is kind of number three and this would be very key to attracting these specifically web developers who don't want to deal with such as so this work is all being done by the human HQ team and there's a proposal on chain that just passed this morning that they are going to work on implementing all of this gonna console as well. + +Anil Murty: The fourth one is the most obvious thing that we have talked about for a really long time, which is supporting both ial as well as a non-custodial experience for people that want to use So today everything is obviously + +00:45:00 + +Anil Murty: Non-custodial meaning everybody brings their own wallet and connects to console using that what we are going to be working on is a custodial experience where we would maintain multiple custodial wallets and have people use those for deployments or rather deploy, their workloads discuss your words, but what the ultimate user sees is a non-volent based experience meaning a non crypto experience. So that's number four and this is going to be key to driving adoption Beyond crypto audiences and… + +Tyler Wright: Perfect. Thank you Anil. Does anyone have any additional questions for Anil or… + +Anil Murty: then the fifth one which is sort of a little bit unrelated to deployment developer experience… + +Tyler Wright: some of the other folks here that are currently working on all this stuff related to console 2.0? + +Anil Murty: but is key to helping us brain into more cohesive experience a brand as well as utilizing a lot of the common functionality right now exists within two different apps. So obviously pretor is the app that many providers use today for spinning up a providers on Akash. + +Tyler Wright: Go ahead go don't mean you go first, and then we'll have Luna follow you. + +Anil Murty: Yeah, that's a really good question mi. So I said, this is very near term objectives, the prioritizing things that are causing people to not use our cash today, but once we get through these there's a bunch of other things that we want to look at in the future. + +Anil Murty: A few months ago, obviously the pretor team joined the overclock lab team. + +Anil Murty: So storage is definitely one serials… + +Anil Murty: And so what we're going to be working on is a new frontend for pretor that is going to decide inside console and… + +Anil Murty: where today it requires a significant amount of detailed technical understanding to be able to set up Akash to be using store J. + +Anil Murty: it's going to be available through some kind of a UI switch… + +Anil Murty: For example, or file coin or… + +Anil Murty: where given provided can come in can switch and… + +Anil Murty: SD. So the next step of this would be exactly that… + +Anil Murty: then, manage their provider and… + +Anil Murty: which is adding to the developer experience so that once somebody has set up or… + +Anil Murty: then switch back to the deployment console and then deploy so that same thing so it's a very similar user experience to something that you would see in other two-sided marketplaces. + +Anil Murty: has a workload deployed. We want to make it easy for them to be able to periodically back up their data… + +Anil Murty: So, if you take a B&B is example… + +Anil Murty: because … + +Anil Murty: if you're hosting a B&B and… + +Anil Murty: even if you have a student storage on a cash today,… + +Anil Murty: you want to … + +Anil Murty: which is supported in console today,… + +Anil Murty: go and Lease in AP yourself, you can do that from the same application. + +Anil Murty: you can figure persistent storage. + +Anil Murty: So very similar experience to that is going to be available within console and… + +Anil Murty: The challenge of course is that if your lease was too close for some reason then you lose all your data that store on the closest storage even the technically + +Anil Murty: any of the common features that exist between pretor and console today whether it's a provider dashboard whether it is the uptime checks,… + +Dominikus Brian: Okay, thank you. That's great a short one relating with the point number two on the vm1. + +Anil Murty: all of those will get merged together. + +Dominikus Brian: so Can we SSS Instead of to the docker… + +Anil Murty: No. that's right. + +Dominikus Brian: because that's more making sense. + +Anil Murty: Yeah, unfortunately So obviously because Akash is entirely dependent on kubernetes as the underlying orchestrator for workloads on a given provider and deciding which node runs on we can't provide people to pay medical VM access. There are certain Solutions like micro VMS that we have thought about in the past, but that's a significantly more lift for us to be able to operate on It's definitely something that we look at probably in the future. so those are kind of the five main things in terms of new term objectives. So these I'm talking about are probably in the next three four months the overall plan is to try to get in a experience But if you have any thoughts or ideas around it definitely open to discussing those. You… + +Anil Murty: + +Anil Murty: + +Dominikus Brian: Okay, great. Thank you. + +Anil Murty: experience that looks and thank you. + +Joao Luna: Yeah, my question was around that so I'm not sure… + +Anil Murty: what like this which is regardless of… + +Joao Luna: if I have much to have. + +Anil Murty: where the user comes from whether they're,… + +Joao Luna: I know I thought without the solutions such as cubert that could be used… + +Anil Murty: crypto user or non crypto user whether they're coming from a infrastructure as a service like AWS or… + +Joao Luna: but my concern was over the idea that we are kind of offering a VM experience. + +Anil Murty: gcp or… + +Joao Luna: That's not really a VMware still connecting to a container. + +Anil Murty: the coming from a platform as a service like versatile Phi all of them need to be able to work with Akash to be able to ultimately get a application deployed in SSH to be able to get into that specific container. + +Joao Luna: There are some limitations. And I was wondering if I wouldn't be a good strategy It start perhaps exploring that way of that new service to provide a jazz VMS. + +Anil Murty: And be able to do that both to a crypto wallet as well as an encrypt over it. + +Joao Luna: I think even for machine learning workloads. + +Anil Murty: So that's kind of the main near term objectives. I don't talk to a bunch over there. + +Joao Luna: It's better to have a VM running. + +Anil Murty: Happy to take any questions. + +Joao Luna: I'm not sure how that works with keywords. It's kind of still running it on a container, but I think it's kind of like a very modified container. That's basically a VM, but I'm not + +Joao Luna: 100% comfortable with saying it's a real VM. But I know as long as you're running on bare metal kubernetes cluster, it's basically the same as running APM things get complicated for running on a visualized environment like running your provider on a virtualized machine, then it would be running a VM over a VM and that's Not like the ideal. + +Joao Luna: But yeah, I mean, I think it's great that we offer that experience. it's Game Changer, but we are just kind of abstracting the problem right? You're still connecting to a container. + +00:50:00 + +Anil Murty: Yeah, you're absolutely Yeah. So this is definitely more of a short term or rather the first step solution for making people feel like they're getting a familiar experience. We have definitely had multiple instances of users who come in, they understand it and then the I can work with this part. Is there a way for me to just SSH into the Container rather than having to do it release shell and this at least Yeah,… + +Joao Luna: Yeah, I understand. The thing that is very interesting discussion. + +Anil Murty: pretty absolutely right. + +Joao Luna: Sorry because for instance what we can end up. discovering is someone saying Okay, I'm running this VM on a card, but I'm not actually able to run let's say a kubernetes cluster that because you can really have Corona kubernetes on a container so we can start running into this power problems if people are confident that they're running on a VM and then To start to work to want to deploy things on those VMS. So in Docker and stuff like that, but it's a very interesting problem. + +Anil Murty: That's Yeah, exactly and I think part of it is going to be our messaging also the primary, pain point to be solving here is not necessarily provide. a little bit of it is making it feel like they have a experience. But the primary objective here is to let people be able to easily SSH from their own terminals as opposed to having to use Alicia. So + +Joao Luna: That leads to me to one last question. It's kind of technical but perhaps what two million answer is enough. Why isn't the shell connection an auction? currently + +Anil Murty: two reasons one is people just like using the terminal and second there is actually a bug in the currently sell which basically causes delicious to session to be broken when the provider part restarts. + +Joao Luna: Okay. + +Anil Murty: There's actually an open issue for that as well. But yeah, it's on the core teams roadmap to fix but outside of that many people just don't want to have to do it. If you are time. There's different about terminal as well. Thank good. + +Maxime Beauchamp: Yeah, and also users prefer to connect to SSH through their own terminal. Or most of the users. Just wanted to add that on top of it. + +Anil Murty: Yep. That was the primary here as a primary. + +Joao Luna: That makes sense. + +Tyler Wright: For all right. I know we have about five minutes left jannick put a question unrelated, but with asking I know that currently it's not possible to sign transactions on the cash console front end with a ledger his Amino sign plan for a cost JS. I don't know if that's something we can answer now, but I just want to go ahead and + +Anil Murty: Yes, it's not currently planned simply because this is the first time anyone has asked for it. At least that I know of but akashias is an open source code base. So if somebody wants to take that on and if you feel strongly enough about implementing it then definitely, happy to support you online. + +Tyler Wright: Yeah, it please feel free to drop some discussion points around this in the cost JS Channel and Discord and then some folks that may not be here today will look to get back to you as well as some folks that are here today, but much appreciate you bringing that up. Any other discussion topics that anybody wants to talk about right now? related to Sid clients + +Tyler Wright: Cool, before we go again. We don't have to talk about it and I dropped it in Discord, but this is something just pybrid Dev was previously working on some cleaning up of awesome Akash repo. I just wanted to have people that at least take a couple seconds to look at it and get some feedback. I know that awesome akashes underlying for some of the work that happens inside the templates for console. So again, this is something that hybrid a did it on his own and I've just been getting some feedback from democus, but I want to get some feedback from people in the Sid clients, more publicly. So again, if you have any comments, feel free to drop them in Discord, and then we can just follow up there. + +Tyler Wright: Cool, if there's nothing else then again much appreciate everyone's time today Appreciate Luna and Anil both going over what's going on a console front as well as what's going on with go client libraries and some other work that Luna has been working on for a long time. + +00:55:00 + +Tyler Wright: One thing I'll also add again. I thank you to all those that bear with the issues of Discord. I please always use caution Network website is sorts of Truth. We have six support coming up tomorrow during that meeting where we might be talking about restructuring of six support and maybe a new Sig that may come from that. So again, feel free to join that. If you have anything that you want to talk about relate to the core product and some of the open issues whether they be related to again the core code base or console. We also have sick providers monthly meeting and then the working group for their cash website and documentation on Thursday and the steering committee as well. So again, we won't go into great detail about number of things that we talked about in detail today during this call, but much appreciate everyone's time today, and I hope everyone has a great rest of your day. Feel free to again stay engaged between meetings in Discord. + +Tyler Wright: Big clients to score Channel or jannick you can feel free to ask any questions related to akashias there and we'll continue to talk. + +Tyler Wright: excellent All right, Max. I'll follow up with you about a piper debt. But again, please feel free to drop any comments related to awesome Akash in there. And again, I hope everyone has a great rest of their day. Thank you all for your participation today. Talk to you all soon. Bye. + +Meeting ended after 00:58:42 👋 From eea8689ec674cb02167d1c10f55f0c8a79e60267 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Thu, 25 Jul 2024 16:57:56 +0000 Subject: [PATCH 113/138] Create meeting notes for sig-chain #18 (#637) * Create meeting notes for sig-chain #18 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 018-2024-07-17.md added recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-chain/meetings/018-2024-07-17.md | 133 +++++++++++++++++++++++++++ 1 file changed, 133 insertions(+) create mode 100644 sig-chain/meetings/018-2024-07-17.md diff --git a/sig-chain/meetings/018-2024-07-17.md b/sig-chain/meetings/018-2024-07-17.md new file mode 100644 index 00000000..6ad42f7f --- /dev/null +++ b/sig-chain/meetings/018-2024-07-17.md @@ -0,0 +1,133 @@ +# Akash Network - Chain Special Interest Group (SIG) - Meeting #18 + +## Agenda +- Discussion on Akash Network upgrade +- Updates on SDK 47 migration +- Parameter changes for stable tokens +- Inter-Chain Accounts(ICA) Implementation + +## Meeting Details +- Date: Tuesday, July 17th, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://556xxz5f7wcokgit5qlznxtkdvmdkcrafobpcwztrytgflmcifjq.arweave.net/731756X9hOUZE-wXlt5qHVg1CiArgvFbM44mYq2CQVM) +- [Transcript](#transcript) + +## Participants +- Alex N +- Artur Troian +- B S +- Gilad Penn +- Javier Su +- Robo McGobo +- Rodri R +- Scott Carruthers +- Tyler Wright + +**Meeting Notes:** +- **Tyler Wright** + - Welcomed everyone to the meeting. + - Mentioned the meeting covers topics related to the Akash blockchain. + - Discussed the possibility of changing the meeting cadence, especially between network upgrades. + - Noted that validators stay connected via the validators Discord channel. + - Provided a link to keep up-to-date with the Akash Network product and engineering roadmap. + - Introduced Javier Su, who would present his background and experience later in the meeting. + - Brought up the topic of adding specific stable tokens as payment methods. + - Clarified that some stable tokens only require a parameter change, while others might need additional technical work. + - Requested feedback and promised to follow up on the stable token integration question. + +- **Artur Troian** + - Acknowledged and greeted the attendees. + - Provided updates on the Akash Network, specifically related to the upgrade to the Cosmos SDK version 47 + - Mentioned that the SDK 47 migration is a significant task, involving creating a good SDK for customer developers. + - Stated that they are about 70% complete with the migration, excluding documentation. + - Highlighted ongoing efforts in migrating product types and actual stores. + - Noted that the migration can be tracked in the sdk47 branch on the Akash repo. + - Explained the integration and extension of simulations for certain modules. + - Aimed to have the initial alpha release of the Akash repo and SDK by next week. + - Planned for initial local testing, followed by a testnet for insiders and the community. + - Estimated the SDK upgrade completion by early autumn, with some flexibility for fixing small issues. + - Confirmed that integrating stable tokens requires both parameter changes and technical adjustments. + +- **Javier Su** + - Introduced himself and briefly discussed his background in leading core development on Terra. + - Shared experience with migrating to Cosmos SDK 45, 46, and 47, noting the significant changes involved. + - Described the integration tests written in TypeScript for their CI/CD flow. + - Demonstrated how they spin up a local net with three validating nodes for testing. + - Mentioned the benefits of integration tests in catching issues during chain upgrades. + - Offered to help with writing integration tests for Akash, emphasizing the need for both Go and TypeScript tests. + +- **Artur Troian** + - Appreciated Javier's insights and offered to collaborate on integration tests. + - Explained Akash's approach to testing, which includes Go-based tests for network upgrades. + - Mentioned that additional integration tests for clients and SDKs could be beneficial. + - Suggested Javier connect with a new core engineer at Overclock responsible for client and TypeScript integration. + +- **Tyler Wright** + - Took notes and committed to posting them after the meeting. + - Agreed to coordinate with Javier and the core engineer for further collaboration on testing. + - Asked if there were any additional questions before handing over to Alex. + +- **Alex N** + - Introduced himself and his team, highlighting their experience with Akash, Lit Protocol and Stride. + - Emphasized their goal to enable interchain accounts (ICA) for liquid staking of AKT. + - Shared his background in leading growth at Ocean Protocol and involvement in web3 infrastructure projects. + - Passed the introduction to Robo McGobo. + +- **Robo McGobo** + - Introduced himself, mentioning his role in leading growth at Stride Labs and involvement with Osmosis and UDX grants programs. + - Expressed excitement about discussing ICAs and understanding the roadmap and potential blockers. + + +- **Inter-Chain Accounts(ICA) Implementation:** +- **Alex N** + - Outlined their plan for ICA collaboration, including creating an issue on Akash Network support and eventually converting it into a governance proposal and chain upgrade. + - Asked about the current roadmap for ICA and its alignment with the SDK 47 upgrade. +- **Artur Troian** + - Appreciated the focus on ICA and shared the historical context of ICA in Akash. + - Confirmed that the priority is the SDK 47 upgrade, which needs to be completed and stabilized before incorporating ICA. + - Suggested starting the discussion on GitHub to outline the requirements for liquid staking on Akash. + - Highlighted the importance of specific requirements and messages needed for ICA. + - Mentioned the three major upgrades planned for the year: SDK 47, packet forwarding, and ICA, with the primary blocker being the SDK 47 upgrade. + - Estimated the SDK 47 upgrade to be completed by end of summer or early autumn, potentially in August, but flexible until end of September. + - Explained the historical context of ICA on Akash, highlighting that the previous implementation was rolled back due to technical flaws. + - Confirmed that the decision to roll back was not due to ICA itself but because of incorrect implementation on the Akash side. + - Stated that since then, there hasn't been a strong reason to reintroduce ICA until the need for liquid staking emerged. + - Emphasized the importance of correct implementation and thorough testing, stressing that the core team needs to ensure robust testing before rolling out ICA. + - Encouraged the community to start by writing clear requirements for ICA, particularly for liquid staking, to initiate the discussion and convert it into a formal issue. + - Highlighted that the actual implementation of ICA is not complex but the testing and integration process requires significant effort. + - Artur Troian discussed the importance of addressing all questions related to ICA requirements before finalizing the implementation. + - Emphasized that robust testing is crucial and that help from the community will be needed. + - Mentioned the current sandbox connections are limited, and additional IBC connections might be needed. +- **Alex N** + - Clarified the roadmap and steps moving forward, aligning with Artur's timeline and approach. + - Expressed understanding of the process and agreed to start with outlining requirements for ICA. + - Acknowledged the importance of thorough testing and the core team's involvement in the process. + +- **Discussion on Roadmap and Testing:** + - Alex N and Robo McGobo acknowledged the detailed context provided and expressed appreciation for the transparency. + - Artur Troian highlighted that once requirements are clear, they will determine how to incorporate ICA into the roadmap and testing phases. + - Emphasized the need for thorough and specific discussions on GitHub about liquid staking and ICA to ensure a complete understanding of requirements and implementation. + - **Tyler Wright** + - Responded to Alex N's query about the rollback of ICA and mentioned that the community is largely supportive of reintroducing ICA. + - Emphasized that the previous rollback was due to technical issues and lack of thorough implementation by the contributing group. + - Reiterated that there are no major community political issues with ICA, and the focus is mainly on resolving technical challenges and the ongoing SDK 47 + +- **Next Steps:** + - **Tyler Wright** emphasized the importance of creating a comprehensive GitHub discussion about ICA and liquid staking to engage with the community effectively. + - Agreed to push the ICA discussion up from the backlog to the next priority after the SDK 47 upgrade. + - Noted that both packet forwarding and ICA will be worked on concurrently, with a focus on moving them forward efficiently. + +- **Closing Remarks:** + - Tyler Wright thanked everyone for their participation and highlighted the importance of continued collaboration and timely updates. + - Agreed to follow up with notes, the transcript, and the recording of the meeting for reference and further discussion. + +## Action Items +- Artur Troian to provide further details on the upgrade to Cosmos SDK version 47. +- Tyler Wright to update the community via sig chain Discord Channel as the SDK 47 upgrade progresses. +- Tyler Wright to coordinate with interested attendees for testnet participation and future meetings. +- Tyler Wright to follow up on the integration of stable tokens as payment methods, including necessary parameter changes and technical adjustments. +- Artur Troian to connect Javier Su with the core engineer at Overclock for collaboration on integration tests. +- Alex N and Robo McGobo to start a discussion on GitHub outlining the requirements for ICA. +- Artur Troian to ensure the ICA discussion is aligned with the SDK 47 upgrade timeline and requirements. + +## Transcript From e98a4c2aac17f5f11524fd61339f5b27d11251ef Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 25 Jul 2024 12:59:26 -0400 Subject: [PATCH 114/138] steering committee Update README.md add meeting links for july 27th, 2024 meeting Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index 0a38d85b..dded03a4 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -30,7 +30,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, March 28, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md#transcript)|[Link](https://4wprt5kys3oxjr7ihtu2jgx6mshwts7gzsiv2pfr4qypgrp2xywa.arweave.net/5Z8Z9ViW3XTH6DzppJr-ZI9py-bMkV08seQw80X6viw) | Thursday, May 02, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md#transcript) |[Link](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) | Thursday, June 06, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md#transcript) |[Link](https://capv32vqn7vrb5u3qvsjn3n6y6swnjkba32ukvydflmqqhrxbswa.arweave.net/EB9d6rBv6xD2m4Vklu2-x6VmpUEG9UVXAyrZCB43DKw) -| Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | |[Link](https://upv27tytyope2fseqvgnnre2au6nmmo65bs2c2fvuxtohsr5bpjq.arweave.net/o-uvzxPDnk0WRIVM1sSaBTzWMd7oZaFotaXm48o9C9M) +| Thursday, June 27, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/017-2024-06-27.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/017-2024-06-27.md#transcript) |[Link](https://upv27tytyope2fseqvgnnre2au6nmmo65bs2c2fvuxtohsr5bpjq.arweave.net/o-uvzxPDnk0WRIVM1sSaBTzWMd7oZaFotaXm48o9C9M) | Thursday, July 25, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, August 29, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, September 26, 2024 11:00 AM PT (Pacific Time) | | | From d3e80cd31df7420e2dfdef5009290bbc8919b6f0 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Thu, 15 Aug 2024 20:27:36 +0000 Subject: [PATCH 115/138] Create meeting notes for Committee-Steering #18 (#649) --- committee-steering/meetings/018-2024-07-25.md | 251 ++++++++++++++++++ 1 file changed, 251 insertions(+) create mode 100644 committee-steering/meetings/018-2024-07-25.md diff --git a/committee-steering/meetings/018-2024-07-25.md b/committee-steering/meetings/018-2024-07-25.md new file mode 100644 index 00000000..5f84037f --- /dev/null +++ b/committee-steering/meetings/018-2024-07-25.md @@ -0,0 +1,251 @@ +# Akash Network - Steering Committee - Meeting #18 + +## Agenda + +- Review / discuss / address any community feedback, grievances, or conflicts. +- Review [projects list](../projects-list/README.md), prioritize / add / remove if necessary. +- A look at open discussions in [Github Discussions](https://github.com/orgs/akash-network/discussions). +- Community and Marketing Initiatives. +- Events and Conferences +- Zealy Developer Onboarding Proposal +- Open up to any other questions from the community. + +## Meeting Details + +- Date: Thursday, July 25th, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://vowukrgkuwsl7fdoune7kqruamcwsbhm7bh4aic6dse6vyussagq.arweave.net/q61FRMqlpL-UbqNJ9UI0AwVpBOz4T8AgXhyJ6uKSkA0) +- [Transcript](#transcript) + +## Committee + +- Anil Murty, Overclock Labs +- Artur Troian, Overclock Labs +- Greg Osuri, Overclock Labs +- Scott Caruthers, Overclock Labs + +## Participants + +- Amanda Keay +- Andrew Mello +- Anil Murty +- Artur Troian +- B S +- Denis Lelic +- Deval Patel +- Dominikus Brian +- Jannick H +- Jigar Patel +- Joao Luna +- Maxime Beauchamp +- Robert Del Rey +- Scott Carruthers +- Scott Hewitson +- Tyler Wright +- Zach Horn + +## Meeting Notes + +- **Community Feedback and Issues:** + - No specific grievances or conflicts raised during the meeting. +- **Project Board Review:** + - Overview of ongoing projects, with a focus on the SDK47 upgrade and discussions around console features. +- **Event Highlights:** + - Successful participation in EthCC and other events in Brussels. + - Greg's participation in 16 different events, including the Open AI Summit and Renaissance Meetup hosted by Uock. +- **Community and Marketing Initiatives:** + - Opportunities for community members to contribute to documentation, support, and development. + - Community support rewards in terms of AKT available for contributions. +- **Product and Engineering Roadmap:** + - Ongoing work with Mystic Labs on cosmo kit support and provider build process updates. + - Progress on Console 2.0, including Fiat payments and other features. +- **Developer Onboarding and Funding Proposal:** + - Robert Del Rey discussed the [Developer Onboarding Funding Proposal](https://github.com/orgs/akash-network/discussions/633) Number Two. + - Detailed the Zealy platform's role in engaging the community through missions and rewards. + - Encouraged community members to contribute ideas for new missions and integrations. +- **New Proposals and Discussions:** + - Discussion of a proposal to increase committee pool tax and decrease inflation. + - Further discussion deferred to SIG Economics when the author, Cheng, is present. + - Encouragement for community involvement in discussions and voting. + +#### Open Discussion +- **[YouTube Channel Revamp:](https://github.com/orgs/akash-network/projects/6/views/1?pane=issue&itemId=71953958)** + - Robert Del Rey discussed efforts to revamp the Akash YouTube channel, starting with optimizing video thumbnails, titles, and descriptions to improve discoverability. + - Plans to include calls to action in videos, linking to documentation and related content. + - Efforts to feature good community content, including tutorials and events. + - A working group has been formed on Discord to discuss these initiatives, with the first phase set to be evaluated next month. + +#### Additional Points +- **Future Meetings and Events:** + - Acknowledgment of a quieter event schedule in early August, with a notable event in Buenos Aires in mid-August. + - Focus on upcoming technical projects and preparations for a busy September and October. + - Encouragement to participate in the upcoming testnet for the SDK upgrade and other initiatives. + - Recognition of increased participation in SIGs and working groups, with a plan for more organized wrap-ups and summaries. + +#### Next Steps and Meeting Wrap-Up +- **Wrap-up and Acknowledgments:** + - Tyler Wright thanked attendees for their participation and efforts. + - Noted the availability of meeting notes and recordings, with thanks to community members who assist in creating them. + - Discussion of potential for more frequent wrap-ups of SIG and working group activities. + - Encouraged continued engagement and contributions from the community. + +## Action Items +- **Tyler Wright:** Continue to monitor and address community feedback and issues. +- **SIGs and Working Groups:** Provide detailed updates on SDK47 and other projects. +- **Amanda Keay and Zach Horn:** Compile a report on recent events and participation. +- **Tyler Wright:** Plan and prepare for upcoming events, including Buenos Aires. +- **Tyler Wright:** Promote opportunities for contributions in technical and non-technical areas. +- **Mystic Labs Team:** Monitor and update on cosmos kit support. +- **Console Team:** Provide updates on Console 2.0 features and progress. +- **Robert Del Rey:** Finalize and launch Developer Onboarding Proposal Number Two. Gather feedback on Zealy platform missions. +- **SIG Economics:** Engage in discussions around the proposal to increase committee pool tax and decrease inflation. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the steering committee monthly meeting it is. July 25th 2024 during the steering committee monthly meetings. This is a culmination of all the special interest groups and working groups that happen throughout the month on the Kash Network open source ecosystem. + +Tyler Wright: During this meeting. We have a typical agenda, which I will jump to right now. We will go through a number of these items and then from there we'll go open up to any General open discussion. If anybody has anything they want to discuss feel free to drop it inside the chat right now so that we can have it for the open discussion portion. + +Tyler Wright: cool with that said again, everybody here contracts steering committee notes that have happened since the stereo committee started in 2023 at the previous steering committee meeting we talked about we went to the typical agenda. There was a couple of interesting discussions that have since gone on chain in the past. So if anybody again wants to track any of the notes or recordings from previous meetings, feel free to do so in the steering committee read me file. + +Tyler Wright: The first thing we do as a part of the agenda is review discuss or address any Community feedback grievances or conflicts. Does anybody have anything that they want to share as it relates to just the cost ecosystem in general sigs working groups or anything of that matter they want to discuss and right now + +Tyler Wright: cool All right. Next part of the agenda is around review of project boards again, there is great detail that happens during very cigs and working groups throughout the month. I know we've talked in a great detail about what's going on as pertains to the Castle's 47 upgrade in sick chain, and I know there's a lot of discussion in previous clients about console. So again, if anybody wants real specifics, feel free to join those cigs and working groups throughout the month to talk about things in more detail with members that are working on it. But again, we'll go through the project boards at a high level today. We're actually will go in reverse order because I know that There is some events happening later today in New York City, which I'm sure we'll get talked about, but I wanted to first one of the big action items out of the last. + +Tyler Wright: Steering committee meeting was around prep for Brussels and all the events happening there. This is the first steering committee meeting… + +Amanda Keay: hey everyone Thanks for the time to talk about this. + +Tyler Wright: since ECC and all the events happening in Brussels. + +Amanda Keay: We had a lot of success in Brussels. + +Tyler Wright: So I did want to hand it over to Amanda and… + +Amanda Keay: I'm sure as many of you are aware Greg had a couple tweets about participating in 16 different events. + +Tyler Wright: Zach to talk a little bit about ECC and some other events as I moved this over to completed. + +Amanda Keay: I'm going to click just go through my list of events that we attended sponsored. + +Amanda Keay: yeah, very very quickly though. So we participated in the open AI Summit the chief I Summit which was also great. We participated and Greg was able to do a talk at the Renaissance. Meetup that was hosted by flock + +00:05:00 + +Tyler Wright: Thank you Zach. Does anyone have any questions or comments about anything a cost chat API related or about the events happening in Brussels or that happened in Brussels? Rather? + +Tyler Wright: additionally when we talk about this in various working groups, there are a number of opportunities for folks Technical and non-technical to continue to work on the Akash Network whether it's documentation or whether it's through support of the open source Akash Network website again, there's working groups and cigs where folks can audit create issues and then solve those issues and there's again Community Support rewards in terms of akt available for again merge contributions. So if anybody's looking to get involved or if anybody here is an Insider Vanguard and interfaces with folks in the general Community, they're looking to get more involved a good way to get started is certainly through the website and then again for more technical folks to dive into the documentation ask questions. See if there's anything needs to be fine tuned and then get up to speed with, some of the other stuff that will talk about later. + +Tyler Wright: All Continuing to move along. I just want to see if there's anything else on the community or marketing initiatives that anybody wants to discuss before we move on to product and Engineering initiatives. + +Tyler Wright: Go ahead Robert. + +Tyler Wright: Excellent, and we can spend a little bit more time during the discussion section going over any last minute points before we take next steps. for Cool anything else we want to discuss in the community or marketing project or before I move on to a product and Engineering roadmap? + +Tyler Wright: All right a couple of things again. We're still tracking with the Mystic Labs team on the cosmo kit supports. There's gonna cosmokit bug that is being resolved. And so again, the Mystic lab team is staying on top of it and we'll continue to Monitor and update this project as they look to finish across the finish line. There has been much discussion around updated provider build process during sick providers some other meetings. So again, please look at the notes and video that'll be available shortly on that meeting and get involved in the sick provider Discord Channel. If you want to learn more about what's going on there again, that's been an effort to talk about month over month or less three or four months. So again, please if you're one more information or if you see somebody in the community that wants more information push them towards the providers and then again we can discuss more there. + +Tyler Wright: I did want to see if there's anything in progress I get again. There was much discussion around consult 2.0 at the last steering committee meeting as well as in a couple of six throughout the month. I know there's a lot of great deal progress being made across the number of these items including Fiat payments and some others. I want to see if there's any questions from anybody in the community or if there's anything from the console team that they wanted to discuss on Console 2.0 efforts here today. + +00:10:00 + +Tyler Wright: no worries. + +Tyler Wright: Another again big effort that get talked about multiple times during the month is around the cosmos SDK upgrade to version 47 again as recently as I think a week ago, we got to update from Artur doing Sig chain and all the work that's getting done there. I know that there is a test net that is planned for sometimes soon where we'll include members on this call another members of The Insider Community to get involved in helping with the testing again, excellent + +Tyler Wright: + +Tyler Wright: Is there anybody here on the call that wants to discuss anything on the product and… + +Tyler Wright: there will be more information. I'll be shared in sick chain and + +Tyler Wright: Engineering roadmap that might need some more detail again. + +Tyler Wright: other announcements channels across Discord. So again, + +Tyler Wright: If you don't want to discuss it here today. + +Tyler Wright: if you want to get involved during that testing period Please look out for announcements over the next couple of weeks Archer. + +Tyler Wright: The product team does a great job of updating the specific projects with tasks and… + +Tyler Wright: I just want to see if there's anything that you wanted to cover with this group here today related to customer SDK, + +Tyler Wright: where things are on a pretty frequent basis. So again,… + +Tyler Wright: but don't feel obliged because they know again we talk about it a fair amount throughout the month. + +Tyler Wright: you can leave a comment in there or you can just read some of the comments as they come in from the product team as they're working on very items. + +Tyler Wright: You see on the board here. + +Tyler Wright: If not, then again, we can continue to move on with the agenda. + +Tyler Wright: terrific All right, moving along next thing that we usually cover during the steering committee is around discussions. We usually like to have participants that are here during the call talk about their discussions. We also look to have conversations that are getting a lot of traction where folks can talk about things. I know that Robert here is kind of alluded to the developer onboarding funding proposal that went on chain has gotten some discussion gotten some feedback over the last couple of weeks. So Robert I want to hand it over to you to see if there's anything you want to talk about with this group today about next steps for the developer onboarding funding proposal number two. + +Robert Del Rey: Thank you I went a little bit ahead earlier in the call. But yeah about the debt campaign. As I was saying were pretty much ready to go live Wendy and I been spending it last month. Assembly missions going over the Nations ourselves making sure they make sense. I also spoke with a few insiders privately to get their feedback and they were very helpful ascending the missions you're gonna notice when they go live that they format is improved instructions are gonna way more easy to understand and also the documentation is going to be very handy for everybody trying to + +Robert Del Rey: get started on a cash to give a little bit of context on silly. I'm sure many here are about it already, but just for the sake of the recording seal, its a platform similar to others in the space. Else Community people grow the community the way they do it is that it's like a game. the relation to missions and with those missions you hope you attract people and they do it and they level up they get experience. And they can get rewarded for it. I mean it's a way to create a funnel. Get somebody new to the ecosystem. Make sure we point them in the right direction and after they test out the network, they might get rewards for their participation. So that's a little bit of context on Sealy what I've been doing in this last week specifically + +00:15:00 + +Robert Del Rey: I've been working in some documentations. Just to make sure everything is documented like that tasks are doing how we are reviewing the missions and also Gathering. Some key insights that would be beneficial for people looking at this campaign in the future. let's say somebody it's new to this company and they are asking things like, How effective was this in the past we're working. all about documentation ready For everybody who is interested in that. yeah, what I wanted to ask please say is that in this season 2 we want to level it up. We want to push a cache to the limits. There are nations to deploy some stuff on a cash. + +Robert Del Rey: But there is gonna be one open mission that you can do basically anything. We're just gonna ask the participants that try to integrate a cache in any way to the other service or the other network. They're trying to integrate a cache and we're going to review that and hopefully get some good Integrations of That so I mean biting you insiders. If you have some crazy ideas on how we can push a cache into the limits reach out to me and we can maybe turn that into a mission. And maybe that mission can be a mission like you can do when you Ward it for it So yeah, I'm super open for discussions and make sure that these program. It's valuable and attracts the right people to the community. Something that you will notice. + +Robert Del Rey: Is that we don't have all of us on Give us a tweet. We're not looking for engagement Army where genuinely looking for people to come up to the network and start pushing some bottles in a cash. So yeah, I will leave it there. If you have questions guys now, it's a good time to discuss that if not my DMs are also that. + +Tyler Wright: And again, feel free to leave any questions comments inside of the discussion 633 and GitHub. So that's again any feedback can be taken into before the team takes next steps in the developer onboarding funding wholesal number two. + +Tyler Wright: + +Tyler Wright: Continuing to look at some of the newer proposals again. I know there's some proposals that have been out here, but some of the main participants aren't here today. I know there's a proposal to increase committee pool tax and decrease inflation again. There's been a great deal discussion here. And I think there'll be some additional feedback that will go into this. I don't know if you want to talk about this at all or again because Chang who author this is not here we can discuss this a little bit more and sick economics when he is available. + +Tyler Wright: Thank Again. If anybody has any feedback, please. Feel free to drop it inside the discussion again, this Spurs the kind of discussion. We like to make sure that we're all making the best decisions for the network. So again, please get involved in this discussion and all other discussions, especially because the number of people spent a fair amount of time to put them together. + +Tyler Wright: Again, there's a number of other discussions. Some of them have been talked about in sick providers. So we don't have to talk about them here and then folks aren't here. But please look to get involved and especially when there's ideas integration different concepts again, the more people participating voting commenting would be greatly appreciated. + +Tyler Wright: Any other discussions anybody wants to talk about right here right now? + +Tyler Wright: cool All right, moving along to the open discussion portion. I see that there's one item in chat around the Akash YouTube revamp those effort that was discussed in Sig design. And then again working group has been formed Robert. Do you want to talk about the YouTube revampital? + +00:20:00 + +Robert Del Rey: Absolutely, Tyler. Yes. + +Robert Del Rey: we want to make the cash Channel visible more easy to find to people and This effort started to adjust that in the first phase. We're gonna optimize the video thumbnails. We're gonna optimized the video titles. We're gonna optimize the words just to make sure that when people search for a cash Network, they can find the channel more easily. + +Robert Del Rey: We're also doing efforts to make sure that in the videos. They are a specifically called to actions to make sure that people can go to the documentation or to suggest them existing content in the cash Channel. There is very good content as far as tutorial goes deployments and also events that regular cash participate. So we're gonna try to highlight that more. also we're trying to have + +Robert Del Rey: there is good Community content out there, people me but validators like chilpa and in other persons in the community, they also have really good material. So hopefully we can get some of that in their cash page as well. So what in this face, we're just discussing how we're gonna go about it. There is a group chat in Discord about the YouTube working group. There is a call next Tuesday. if you want to join for free to join and if you see something interesting or due to something that got your attention and you think a cash can benefit of using that feel free to share that, the algorithm in YouTube it change like a lot so + +Robert Del Rey: It's good to have fresh and New Perspectives on what are the things that get our attention in YouTube. So that is something I will leave in the stage so you can think about it and if you have again ideas suggestions you want to get involved. Yeah, just go to that group chat and let's get it going. I don't know if I cover enough time or if I missed something free to call me out. + +Tyler Wright: No, I think that's good. Again. This is a working group that was formed as sick design last couple of meetings has been discussion around just YouTube efforts and I know again getting some help from this wider community on these efforts is going to go a long way. So this is an phase one I believe is going to be over next month and then we'll evaluate from there on what the next couple of faces look like. So again, feel free to get involved during the working group sessions on Tuesdays. + +Tyler Wright: Yes Domi, I see your question. Again. There's a lot of content that gets created from Greg Anil other members of the community and just being able to have that all in one area. So it's more easily accessible as all part of the mission for again the future of the YouTube channel. amongst many other things + +Tyler Wright: Cool, are there any other open discussions at anybody wants to have right now A cost-related? + +Tyler Wright: All right, looking ahead again. There's a number next week will be just the Akash website working group for the YouTube channel rather following that again. We'll go back into the regularly scheduled program. And the start of August will be a slower month on the event side. There will be at one event on some folks from the core team as well as the community would be going to in Buenos Aires in the middle of month. But again, the rest of the month will be focus on number of efforts that were discussed in the product and Engineering roadmap, especially as we get ready for quite a busy period in September and October on the event So again a number of opportunities to Showcase and connect with new people on all the work that's going on from the core team and other members of the community. So again, please please get involved in. + +00:25:00 + +Tyler Wright: Testnet that's coming soon for the cost of SDK upgrade a number of other efforts that again will be announced in various channels. Just look to get involved make your voices heard discussions and we'll continue to push the pace as we get into a very busy fall and winter period + +Tyler Wright: if there's nothing else then again, we can wrap a little bit early today much appreciate everybody's time and efforts especially over last month. There's been a lot more participation in various six and working groups. So again, there's a lot of detailed discussion a lot of great conversations happening there so much appreciate you all the notes and the recording will be available for this shortly. Shout out to George Who again from the community who helps out with that. I know that BS who's also was previously on the call that works on the net of Doubt team is going to be helping out a number of folks in the community who have day jobs want to participate more in the six and working groups. And so some folks have been asking about potentially monthly or weekly kind of wrap-ups of what's happening in specifics and working groups. So I know that members of netted out team of talked about helping out with some of those efforts taking the notes. + +Tyler Wright: I'm in video and just kind of doing a wrap up so much appreciate the efforts that are going on there and look out for more information there soon. Much appreciate everyone's time today. Look forward to seeing you all over the next couple of weeks. Again, if anybody has any questions comments concerns, feel free to drop them in Discord reach out to me privately. But again, thank you all for your time today. See you all soon. + +Robert Del Rey: Thanks Ty. + +Tyler Wright: Bye. + +Robert Del Rey: Thanks everybody. + +Scott Hewitson: Thanks. + +Zach Horn: guys, take care + +Meeting ended after 00:27:22 👋 From 59ba5a017acfc5d4d0dc35533da74c5bbc2bc564 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Thu, 15 Aug 2024 20:27:53 +0000 Subject: [PATCH 116/138] Update Readme table (#655) --- sig-chain/README.md | 2 +- sig-clients/README.md | 2 +- sig-community/README.md | 2 +- sig-design/README.md | 2 +- sig-economics/README.md | 2 +- sig-providers/README.md | 2 +- wg-Akash-youtube/README.md | 45 ++++++++++++++++++++++++++++++++++++++ 7 files changed, 51 insertions(+), 6 deletions(-) create mode 100644 wg-Akash-youtube/README.md diff --git a/sig-chain/README.md b/sig-chain/README.md index ff40c2a9..e9dbd75c 100644 --- a/sig-chain/README.md +++ b/sig-chain/README.md @@ -30,7 +30,7 @@ date: 2023-1-09T00:19:20-08:00 | #15| April 09, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/015-2024-04-09.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/015-2024-04-09.md#transcript) |[Link](https://qv5qbltorrogit5i3qvsihngxzevuweduyauwodu5rk3yhysu3xq.arweave.net/hXsArm6MXGRPqNwrJB2mvklaWIOmAUs4dOxVvB8Spu8) | #16| May 21, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/016-2024-05-21.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/016-2024-05-21.md#transcript) |[Link](https://t7vun4ttnoelbnwkis4rf7eacagljw7a5tsobsuujmsiycgjdpna.arweave.net/n-tG8nNriLC2ykS5EvyAEAy02-Ds5ODKlEskjAjJG9o) | #17| June 11, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/017-2024-06-11.md)| [Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/017-2024-06-11.md#transcript)|[Link](https://g6qelhldnaj52ry4xc56kge2wjrswqfgxrqs4iduth4cpqpndlfq.arweave.net/N6BFnWNoE91HHLi75RiasmMrQKa8YS4gdJn4J8HtGss) -| #18| July, 2024 09:00 AM PT (Pacific Time) | | | +| #18| July 17, 2024 09:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/018-2024-07-17.md) | [Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/018-2024-07-17.md#transcript) |[Link](https://556xxz5f7wcokgit5qlznxtkdvmdkcrafobpcwztrytgflmcifjq.arweave.net/731756X9hOUZE-wXlt5qHVg1CiArgvFbM44mYq2CQVM) | #19| August, 2024 09:00 AM PT (Pacific Time) | | | | #20| September, 2024 09:00 AM PT (Pacific Time) | | | | #21| October 2024 09:00 AM PT (Pacific Time) | | | diff --git a/sig-clients/README.md b/sig-clients/README.md index 340d00eb..cdec57ef 100644 --- a/sig-clients/README.md +++ b/sig-clients/README.md @@ -47,7 +47,7 @@ The goal of this SIG is to foster a community around each of these clients that | #13 | Thursday, February 22nd, 2024 09:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/013-2024-02-22.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/013-2024-02-22.md#transcript) |[Link](https://x5g5djwxzxixepgqsmxl6rupiipshcicdmq5bf2tjac35fjv5f6q.arweave.net/v03RptfN0XI80JMuv0aPQh8jiQIbIdCXU0gFvpU16X0) | #14| March 27th, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/014-2024-03-27.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/014-2024-03-27.md#transcript) | Coming Soon | #15| April 24th, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/015-2024-04-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/015-2024-04-24.md#transcript) |[Link](https://j3gehsinfdsmtozvozl7ne3dv2w255mnewbmwe3unblpiayao3ya.arweave.net/TsxDyQ0o5Mm7NXZX9pNjrq2u9Y0lgssTdGhW9AMAdvA) -| #16| June 25th, 2024 10:00 AM PT (Pacific Time) | | | +| #16| June 25th, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/016-2024-06-25.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/016-2024-06-25.md#transcript) |[Link](https://g4sync4igp5y56x5cxfhh45vo4elgdzmcptwja4z33gcjhzkkoqq.arweave.net/NyWGi4gz-476_RXKc_O1dwizDywT52SDmd7MJJ8qU6E) | #17| August, 2024 10:30 AM PT (Pacific Time) | | | | #18| October 2024 10:30 AM PT (Pacific Time) | | | | #19| December, 2024 10:30 AM PT (Pacific Time) | | | diff --git a/sig-community/README.md b/sig-community/README.md index 0c7b4397..3c92ff05 100644 --- a/sig-community/README.md +++ b/sig-community/README.md @@ -32,7 +32,7 @@ This SIG (Special Interest Group) is designed for Akash community members to pro | #14| April, 2024 11:00 AM PT (Pacific Time) | Coming Soon |Coming Soon |Coming Soon | #15| May, 2024 11:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon | #16| June 11, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/016-2024-06-11.md)|[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/016-2024-06-11.md#Transcript)|[Link](https://nl4ez6metcnz3sdkdgvxj6b2opl74ywekhhfqfj3smj6m4in3e2a.arweave.net/avhM-YSYm53IahmrdPg6c9f-YsRRzlgVO5MT5nEN2TQ) -| #17| July, 2024 11:00 AM PT (Pacific Time) | | | +| #17| July 09, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/017-2024-07-09.md) |[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/017-2024-07-09.md#Transcript) |[Link](https://x6pq6krlnowidy2qpsxdgyrnx7gz5i4ypuxxeemqsynsvipvhoaa.arweave.net/v58PKitrrIHjUHyuM2Itv82eo5h9L3IRkJYbKqH1O4A) | #18| August, 2024 11:00 AM PT (Pacific Time) | | | | #19| September, 2024 11:00 AM PT (Pacific Time) | | | | #20| October 2024 11:00 AM PT (Pacific Time) | | | diff --git a/sig-design/README.md b/sig-design/README.md index 98c6b8e2..67c53019 100644 --- a/sig-design/README.md +++ b/sig-design/README.md @@ -33,7 +33,7 @@ date: 2023-1-09T00:19:20-08:00 | #16| April 13, 2024 08:00 AM PT (Pacific Time) | | | | #17| May 08, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/016-2024-05-08.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/016-2024-05-08.md#transcript) |[Link](https://utgdid3tyicjsjmgvznzalfhes33oqqzoytow53oaqvlgg6nbmlq.arweave.net/pMw0D3PCBJklhq5bkCynJLe3Qhl2Jut3bgQqsxvNCxc) | #18| June 12, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/017-2024-06-12.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/017-2024-06-12.md#transcript) |[Link](https://ifqou2kkf6gqtmise2kelunxe2wc4xrcssgptlx3oh25flm7tcea.arweave.net/QWDqaUovjQmxEiaURdG3JqwuXiKUjPmu-3H10q2fmIg) -| #19| July, 2024 08:00 AM PT (Pacific Time) | | | +| #19| July 17, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/019-2024-07-17.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/019-2024-07-17.md#transcript)|[Link](https://ifqou2kkf6gqtmise2kelunxe2wc4xrcssgptlx3oh25flm7tcea.arweave.net/QWDqaUovjQmxEiaURdG3JqwuXiKUjPmu-3H10q2fmIg) | #20| August, 2024 08:00 AM PT (Pacific Time) | | | | #21| September, 2024 08:00 AM PT (Pacific Time) | | | | #22| October 2024 08:00 AM PT (Pacific Time) | | | diff --git a/sig-economics/README.md b/sig-economics/README.md index 5e80050c..3242bb66 100644 --- a/sig-economics/README.md +++ b/sig-economics/README.md @@ -29,7 +29,7 @@ Meetings happen every [First Wednesday of the Month](https://calendar.google.com | #15| April 3rd, 2024 10:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/015-2024-04-03.md) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/015-2024-04-03.md#transcript) |[Link](https://445y2d4z2tii6zb3mgio36s2cgvrem3ghe7qjvjtmwfpwsgwzbjq.arweave.net/5zuND5nU0I9kO2GQ7fpaEasSM2Y5PwTVM2WK-0jWyFM) | #16| May 1st, 2024 10:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/016-2024-05-01.md) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/016-2024-05-01.md#transcript) |[Link](https://w6djeix4uozea7pt7fdzqmhenlvt6jf72c4x26cz3brkuboazjsa.arweave.net/t4aSIvyjskB98_lHmDDkaus_JL_QuX14WdhiqgXAymQ) | #17| June 18th, 2024 10:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/017-2024-06-18.md) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/017-2024-06-18.md#transcript) |[Link](https://camg45yyujtsslq5bwquh3pybr3ugqzi27rkdbhxfk3bgej5v5yq.arweave.net/EBhudxiiZykuHQ2hQ-34DHdDQyjX4qGE9yq2ExE9r3E) -| #18| July 3rd, 2024 10:00 AM PT (Pacific Time) | | | +| #18| July 3rd, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/018-2024-07-03.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/018-2024-07-03.md#transcript) |[Link](https://gtkqa2srpm2ve37fgnzh4bvk2ajdzxzdh5owwd3vaqvtg5pncdaa.arweave.net/NNUAalF7NVJv5TNyfgaq0BI83yM_XWsPdQQrM3XtEMA) | #19| August, 2024 10:00 AM PT (Pacific Time) | | | | #20| September, 2024 10:00 AM PT (Pacific Time) | | | | #21| October 2024 10:00 AM PT (Pacific Time) | | | diff --git a/sig-providers/README.md b/sig-providers/README.md index efb95dd3..aa757fd6 100644 --- a/sig-providers/README.md +++ b/sig-providers/README.md @@ -32,7 +32,7 @@ Provider SIG covers everything pertinent to Providers on Akash Network. This inc | #15| March 27, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/015-2024-03-27.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/015-2024-03-27.md#transcript) | Coming Soon | #16| April, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/016-2024-04-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/016-2024-04-24.md#transcript) | Coming Soon | #17| May 22, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/017-2024-05-22.md)|[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/017-2024-05-22.md#transcript) |[Link](https://a6qm5qjrbhmjkmbmsfldmoqzdspsaxypsgfq26wfw6ysnw3xp7cq.arweave.net/B6DOwTEJ2JUwLJFWNjoZHJ8gXw-Riw16xbexJtt3f8U) -| #18| June 26, 2024 08:00 AM PT (Pacific Time) | | | +| #18| June 26, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/018-2024-06-26.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/018-2024-06-26.md#transcript) |Coming Soon | #19| July, 2024 08:00 AM PT (Pacific Time) | | | | #20| August, 2024 08:00 AM PT (Pacific Time) | | | | #21| September, 2024 08:00 AM PT (Pacific Time) | | | diff --git a/wg-Akash-youtube/README.md b/wg-Akash-youtube/README.md new file mode 100644 index 00000000..e7e16ab5 --- /dev/null +++ b/wg-Akash-youtube/README.md @@ -0,0 +1,45 @@ + +# Akash Network Website Working Group + +This working group is responsible for managing and improving the Akash youtube Channel. Thank you for wanting to contribute. The Akash youtube can be found [here](https://www.youtube.com/c/AkashNetwork). + +## Meetings + +* [To be scheduled as needed via Discord](https://discord.com/channels/747885925232672829/1070508098134999120/1071112381129834599) +* [Full Calendar for all Akash Working Groups (wg) and Special Interest Groups(sig)](https://calendar.google.com/calendar/u/0?cid=Y18yNWU1ZTM3NDhlNGM0YWI3YTU1ZjQxZmJjNWViZWJjYzBhMDNiNDBmYjAyODc4NWYxNDE1OWJmYWViZWExMmUyQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20) + + + +| Meeting | Time | Notes | Transcript | Recording +| --- | --- | --- | --- | --- | +| #1 | Tuesday, July 23, 2024 08:00 AM PT (Pacific Time)| Coming Soon | Coming Soon +| #2 | Tuesday, July 30, 2024 8:00 AM PT (Pacific Time) | Coming Soon | Coming Soon | coming soon +| #3 | Tuesday, August 6, 2024 8:00 AM PT (Pacific Time) | Coming Soon | Coming Soon | coming soon + + + +## Leads + +- Denis Lelic +- Tyler Wright +- Robert Del Rey + + +## Contacts + +- [Discord](https://discord.com/channels/747885925232672829/1111762354242338876/1144276254699298826) + +## Goals + + + +## PRDs and other documentation + +- [Code of Conduct](https://github.com/akash-network/website/blob/main/CODE_OF_CONDUCT.md) +- + + +## Related SIGs + +- [sig-community](https://github.com/akash-network/community/tree/main/sig-community) +- [sig-design](https://github.com/akash-network/community/tree/main/sig-design) From a6efde4e24593c195bed11cabd908b807f7a7507 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 16 Aug 2024 13:19:46 +0000 Subject: [PATCH 117/138] Create meeting notes for sig providers #19 (#646) --- sig-providers/meetings/019-2024-07-24.md | 328 +++++++++++++++++++++++ 1 file changed, 328 insertions(+) create mode 100644 sig-providers/meetings/019-2024-07-24.md diff --git a/sig-providers/meetings/019-2024-07-24.md b/sig-providers/meetings/019-2024-07-24.md new file mode 100644 index 00000000..f942feca --- /dev/null +++ b/sig-providers/meetings/019-2024-07-24.md @@ -0,0 +1,328 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #19 + +## Agenda +- Praetor Provider App Update +- Console 2.0 Updates +- Tooling Updates for Active Providers +- Provider Build Improvements +- Open Floor Discussion + +## Meeting Details +- Date: Wednesday, July 24, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://aa2i7ytftmtlehngryvt4m6jnaxvu5ku72e34u5akdetalzdimja.arweave.net/ADSP4mWbJrIdpo4rPjPJaC9adVT-ib5ToFDJMC8jQxI) +- [Transcript](#transcript) + +## Participants +- Andrew Mello +- Andrey Arapov +- Damir Simpovic +- Deval Patel +- Jigar Patel +- Rodri R +- Scott Carruthers +- Tyler Wright +- Zeke E + +## Meeting notes + +**Welcome and Introduction:** + - Tyler Wright opened the meeting, highlighting the purpose and past contributions of the group. + - Emphasis on the collaborative nature and outcomes from previous meetings. + +**Updates from Previous Meeting:** +- **Praetor Provider App Update:** + - Jigar Patel and Deval Patel provided updates on the Praetor provider app now integrated into the open-source console. + - Monthly updates on the app's development were mentioned. + +- **Console 2.0 Updates:** + - Continued development and integration into Console 2.0. + - Scott’s scripts for K3s multi-node setups were discussed and found promising after comprehensive testing. + +- **Tooling Updates for Active Providers:** + - Damir Simpovic discussed new tools for active providers. + - Updates and improvements on tooling from previous presentations. + +- **Provider Build Improvements:** + - Scott Carruthers provided updates on provider build scripts, their usage, and future plans. + - Community feedback on build script improvements was acknowledged. + +**Additional Discussion:** +- **Provider Build Scripts:** + - Scott Carruthers mentioned that the provider build scripts have been stable for the past 1.5 to 2 months. + - Jigar and Deval Patel, along with community members like Zeke and Andrey, have tested these scripts and provided feedback. + - Scripts are now being used more widely and tested for various setups (e.g., GPU providers, persistent storage). + - The next milestone is the Praetor team's implementation of these scripts within their Akash provider build process. + - Future steps include gathering community feedback and potentially making these scripts the default recommended provider build process. + - Scott shared the engineering documentation link for those interested in experimenting with the scripts. + +- **K8 vs. K3s Discussion:** + - Zeke E inquired about the differences between K8 and K3s, and any limitations of K3s. + - Scott Carruthers explained that K3s is a lightweight distribution of Kubernetes, making installation faster and management easier, especially in multi-node environments. + - No significant limitations were identified in K3s compared to K8, making it suitable for Akash providers. + - Andrey Arapov added that K3s simplifies the deployment process and saves time, though there are minor operational differences. + +**Additional Discussion Points:** +- **Andrew Mello's Concerns:** + - Andrew Mello joined the meeting late and expressed concerns about the new operator inventory. + - He highlighted issues with the operator inventory being unstable and heavily reliant on the Kubernetes cluster's availability. + - Specifically, he mentioned issues with using a database backend instead of local etcd, handling node state changes, and encountering errors leading to an empty status page. + - Andrew detailed a support issue regarding pod name length exceeding the 63-character limit and mentioned upcoming tickets related to etcd leader changes and other instability issues. + +**Scott Carruthers' Response:** + - Scott Carruthers acknowledged the concerns and explained the motivation behind the operator inventory updates. + - The updates aimed to improve GPU inspection and indexing, necessary for provider incentives. + - Scott emphasized the importance of discovering edge cases and encouraged Andrew to file detailed bug reports. + - He assured that an update regarding the hostname length issue would be provided by the end of the day. + +**Key Points from Andrew Mello:** + - The operator inventory's current architecture makes it fragile, especially in multi-node environments. + - Issues arise when nodes go offline, change state, or when the etcd leader changes. + - He stressed the need for more robust testing and handling of cluster state changes to ensure stability. + - The operator inventory currently opens a listening service on a specific port, which breaks if the port becomes unavailable, leading to the system not resetting itself properly. + +**Scott Carruthers' Clarification:** + - Scott provided context on the operator inventory's design, explaining the setup of a gRPC endpoint for constant GPU inspection. + - He acknowledged the need for validating and investigating the issues Andrew raised, particularly the etcd leader change. + - Scott reassured that the core team would address the issues as they are reported. + +**Closing Remarks:** +- Tyler Wright thanked Andrew Mello for raising his concerns and emphasized the importance of community feedback in improving the system. +- He reiterated the value of these calls for discussing updates, new tooling, and addressing provider-related issues on the Akash Network. +- The meeting concluded with an invitation for any additional agenda items or concerns from other participants. + +## Action Items +- Andrew Mello to file detailed bug reports regarding the operator inventory issues. +- Scott Carruthers to provide an update on the hostname length issue and investigate other reported problems. +- The core team to monitor and validate reported issues, providing timely updates and solutions. +- Encourage community members to report issues and provide feedback to improve the operator inventory and overall system stability. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to providers monthly meeting number. + +Tyler Wright: 19 it is July 24th, 2024 during these Specialist Group for providers the group anybody that cares about anything a cost provider related comes together to discuss tooling to discuss pain points any issues related to providing just general conversation in the past have been a number of discussions that have spurred out of here that turn into working groups of terms into governance proposals a number of folks who will get an update from today include folks like jigarette and Deval. Whoa previously been working on Predator provider app. Now it is going to be a part of the open source console. And so again, there's been some updates on a monthly basis from the page 14. We'll get some more updates today out of the last + +Tyler Wright: Special interest group session there was again some updates from the paid our team about console 2.0 and we'll get some more there. Damir gave a presentation on some tooling that he's been working on for active providers. We can potentially get an update there Andrew Mello and another Community member talked about some mining projects and some of the tools he's been working on and then again, there was some open floor discussion. I think we'll also get an update from Scott who has been working on provider build improvements. And I know that a number of people from the community had tested and used the provider build scripts that he's been working on. So again, we'll talk about a little bit of a future plan there. + +Tyler Wright: If anybody has any other agenda items that they want to cover during this special interest group monthly meeting. Feel free to drop those in the agenda. I'll also remind folks that there's any active discussions. + +Jigar Patel: Hey, thanks. + +Tyler Wright: I think there's a couple of discussions related to provider. + +Jigar Patel: Tyler. So currently we are still working on adding similar experience. + +Tyler Wright: But if anybody can get involved in discussions again,… + +Jigar Patel: What console has right now? + +Tyler Wright: this is a chance to make your voice heard,… + +Jigar Patel: So what we are actually building is similarious experience on provider side. + +Tyler Wright: so I'm feel free to do so. + +Tyler Wright: Cool with that said I will hand it over to jigarette… + +Jigar Patel: So you would see the similar user interface plus with the help of Scott's new scripts that enable us to make k3s multi note provided using Scott scrapes. + +Tyler Wright: Deval to give us just an monthly update as they usually do about some of the console 2.0 updates paid or Etc. and nobody else. + +Jigar Patel: We gonna simplify a lot of things on the provider side. So yeah, we are working on it right now. So hopefully that goes smoothly and yeah, that's specifically from our side. + +Jigar Patel: If you have any questions, please let us know. We did a comprehensive testing on K3 years multinode setup found really useful and found very promising right now. + +Tyler Wright: Excellent. Thank you. Jigar. I'm gonna drop in again a link to the product and… + +Jigar Patel: So looking forward to add that into Twitter replacing the old KS and… + +Tyler Wright: engineering project board there. You can track everything from again all the work that parade tour. + +Jigar Patel: civil script so that we were running from Twitter. + +Tyler Wright: The prayer team is done in around the console 2.0 some of the things that they've been working on including,… + +Jigar Patel: So yeah, it will simplify a lot of things on provider side simplifying. + +Tyler Wright: some of the things that jigar just mentioned around testing of the provider builds process Improvement to Scott has made as well as some of the next steps that they'll be working on for console 2.0. + +Jigar Patel: Support as well from our side as well. So yeah. + +Tyler Wright: So again, you can track everything and kind of real time and leave comments and questions inside the specific projects. We'll talk a little bit more in detail about that during the steering committee meeting happening. I don't know even what date is. Yes, today's Wednesday. So that means tomorrow is Thursday. but again much appreciate all the work that Jigger Deval and everyone else is doing around console 2.0 but especially their worker on the provider side. I won't go into too much detail, but I also want to shout out jigar. I know he's a new dad. I won't Docs. The baby or when it was born, but I know it was recent and so huge congratulations to jigar. I know sleep is a luxury now, but again still a lot of work happening on the Prater provider side Council 2.0. So huge shout out to jigar. + +00:05:00 + +Tyler Wright: ette excellent All right. Any other questions on what's going on with Prater and some of the next steps integrating into console 2.0? + +Tyler Wright: cool All right, next up. I want to see if Scott wanted to give a quick update. I know jigar kind of alluded to it in terms of incorporation of the provider build scripts into console 2.0 as well as the testing that's going on around again, the improvements to the provided Bill process Scott. I just want to see if there's anything you wanted to mention to this group. I know there's some insiders here some folks that interface a lot with people in the providers build Channel Etc. So I just want to see if there's anything that you want to share at this time. + +Scott Carruthers: Yeah, really? They provide a build scripts have Completed I really haven't touched those scripts and probably going on a month and a half to two months ago. So they're just being tested and used more and more efforts. I look at people in the audience for this call. I think just about everyone is very familiar with them. So shimpa is now built a test provider using those scripts and provided some minor feedback on that. We have already implemented obviously jigarh and Deval are very familiar with the scripts of use them many times Deval actually went through and maybe this is the most significant update Deval went through + +Scott Carruthers: A list of any concerns that we had around k3s, and in the providers that are built using these scripts. So, very granular things such as if we proceed any challenges with Calico or the cni used within k3s. at CD performance and things like that. So across those lists of possible concerns, we have Solutions and feel comfortable across all those items. So obviously jigarh and Deval are very familiar with these scripts. I know that Zeke who's also with us was one of the very first community members that test these scripts and this is probably at it I'll stop my head maybe three months ago Zeke tested these scripts and had Relatively, no issues, and I know that Andy is going to start using. Them and some of our overclock managed. + +Scott Carruthers: Providers. So yeah, I think the big updates are they just starting to get implemented more and more. I think obviously the big milestone will be when the printer team implements these scripts within their a cost provider Bill process, which I think has come in very soon. Now that they've done very thorough testing. So I think that's the next Milestone and then after that obviously we'll collect Community feedback on any issues that anyone has encountered and make any tweaks necessary and then the next step after that would be to it include them as our kind of default or recommended provider Bill process. and again, I think pretty much everyone on this call was already familiar with this, but I will just briefly share if anyone is not familiar with us or wants to + +Scott Carruthers: I'm just gonna share my entire screen for a second if anyone is not familiar or wants to experiment with these more right now, kind of my working engineering documentation as always as a caution Engineers that XYZ and if you go to the Akash provider automated build through they temporary repository that these scripts live in and then step by step. A series of events that you would go through to build a provider and these in this manner and there's a lot of different options here. So I think it's pretty robust at this point where if we're doing a all-on-one provider we have that we have options if it's a GPU provider to install the necessary NVIDIA drivers and + +00:10:00 + +Scott Carruthers: runtime and plugins. We also have options to enable persistent storage. So for anyone that's not familiar if you want to play around with this, but we'll have more people experiment and give us any possible feedback. So yeah, think So just in recap the scripts have been rather stable and available for some time. I think the next Milestone is the Prater team. Implementing those as part of their build process and then we'll go from there. + +Scott Carruthers: back to Utah + +Tyler Wright: Does that thank you. Anyone have any questions about provided Bill script next steps. + +Tyler Wright: I am going to drop a link to the Akash Engineers documentation. Just if anybody from the community or anybody that's maybe having problem with the traditional way wants to use this way. It is in beta, so remind folks of that. But again, we can start to share with more folks in the community. Go ahead Zeke. + +Zeke E: This may be more of a time of an offline question. But what are the main differences between K8 and K3? And is there anything? what's the worst part about using K3 that KS has a K3 doesn't? + +Scott Carruthers: Yes, I can answer Andy has some thoughts as So. we're not aware at this point of any limitations. That obviously K3 is a more lightweight. Distribution of kubernetes. So the install process is much faster, which is one of the reasons that the provider build scripts can build the underlying cluster so quickly even in a multi-node environment. So as far as they scale down version and anything in k3's that would be included in full kubernetes or K8. I'm not aware of this. Obviously. This is part of the validation testing that we wanted to go through but as far as a kubernetes cluster, and it's + +Scott Carruthers: Necessary capabilities to serve in a cost provider as the container scheduling mechanism for a cost providers. We're not aware of anything that is not available and the lightweight 3s that is available in K8. So, yeah, it's just a lighter weight distribution and something obviously can With K3 is the appeal of it to become more and more adopted in Enterprise environments. I think in the past 3s was used significantly in lab environments and also heavily in single node all in one node provider topologies, but it's starting to be adopted in Enterprises using multi-node configurations much more significantly. So yeah, it's just a much lighter weight version of kubernetes. And obviously that speeds they Install time and management Andy. I don't know if you have any other. thoughts on those regards + +Andrey Arapov: I guess not it's what you said is it basically allows easier and faster kubernetes and deployment. Because obviously keep spray. You basically spend a little bit more time on inventory preparation and mostly on cloning the git Club get a project of keep spraying making sure you have the latest version instead. You can just run E3 has comments and just install the latest greatest and they have great process is quite similarious pretty much one common close to it. And it's basically save time and in terms of presentation, they haven't found any yet. And if you find of course will what everyone know by adopted there will be some limitations. + +Andrey Arapov: Except maybe for operational standpoint a few where this keep spraying. You have more Standalone components such as tubelette and so on you can restart particular component separately and whiskey K3 as you would need to restart KJS entirely so it could impact on the API will do it if you're starting to control playing mode. So there are smaller drawbacks, but they're just like tiny ones and + +00:15:00 + +Tyler Wright: Excellent. I say a hand Go ahead Andrew. + +Andrew Mello: Hey guys. I'm sorry. I'm a bit late. I did have a question slash feedback that I want to give at some point. Don't know where you're at in your process, but just want to let that be known. + +Tyler Wright: Excellent cool. I'll add that to agenda. We've talked about console 2.0 and some of the work there we talked about provided build scripts. The only other agenda item I had was I know damir had started working on a project last month. I just want to see if there's any updates that damir wanted to share and then enter I can kick it over to you for your feedback. Such questions. Damir. Did anything you want to share? + +Tyler Wright: Yeah, No worries. I'm sure there'll be a continued updates between these meetings and then we can check in with you again next month. cool All right, again, if anybody has any agenda items that they want to cover they haven't been covered already. Feel free to drop them in the chat, but Andrew Mello, feel free to ask your questions / comment. + +Andrew Mello: Yeah, hi. Good morning. Everyone good evening, depending on where you are. So I just wanted to bring as kind of a point of order slash little feedback sessions today on the operator inventory specifically. I'm aware that at the beginning of the year there were some major updates to it and now a few months down the road across my providers. I have noticed some really unruly Behavior with this new operator inventory and kind of the way it's built and some of the experiences I've had with it are really less than ideal. there seems to be a heavy Reliance on the kubernetes cluster kind of always being perfectly available in a perfect state. So one of the first places that I had issues with it was when the k3s cluster I use did not use a local. + +Andrew Mello: Of etcd for example and instead use the database backend. So that was the first place that I noticed. it would have trouble finding and using the actual cluster and then I would get errors inside of the only mind again operator inventory only we're talking about here where I would get errors about, + +Andrew Mello: Unable to reach the cluster exiting failing exit, it seems like whatever happened with operator inventory. There were some pretty significant changes that have impacts and outcomes that were not fully necessarily investigated. So let me give you another example of that which is when nodes go offline or are removed or are added that also can trip up the operator inventory where when it's unable to talk to one of the nodes again, it does not always populate the entire inventory. So one of the consequences of when this operator inventory gets jammed up or stalled up or the cluster hiccups or something happens to the operator inventory where it's not very happy the end result is that the status page of the provider will show no inventory at all it + +Andrew Mello: Just go available and then two brackets right as though empty. And so I wanted to just a high level. If somebody who built that or could give kind of a high level explanation of what the architecture kind of layout is because something changed significantly where now if the cluster of the node or there's one thing kind of off the operator inventory is very unstable. + +00:20:00 + +Andrew Mello: + +Andrew Mello: Across, again, I have nine different clusters that I manage. I have a bunch of different environments some with local etcd without it some with nodes that are failing some without it. Right. So I've gone through and seen over time now, so I brought up yet a third just to again let somebody talk to this now after this third point but I did post my first support issue for this over two weeks ago regarding the length of the pods being created the name length. So once again showing that it didn't necessarily go through a really deep testing in an in-depth step with the way this was built… + +Tyler Wright: excellent I would say the best course of action would be to certainly follow up with those tickets issues on to other two education. + +Andrew Mello: but when the new operator inventory Hardware Discovery pods are being generated that name is so long that it's more than the 63 character limit on the Pod name. + +Tyler Wright: You just described here in this call as well and try to be a specific as possible. But that I believe there was already discussion around the character length in our six support call that just happened an hour ago. + +Andrew Mello: So that was my support ticket I open + +Tyler Wright: I think there's going to be investigation from the core team on next steps there and then we'll follow up with the ticket. But again, I think those go ahead. + +Andrew Mello: But honestly, there's two or three more tickets coming behind that I can document already one where it's failing when the etcd leader changes now, so that was the one I got two days ago where the leader of the cluster changed and that was enough to kill the entire operator inventory, which I found very very surprising. So those are my concerns I would love if somebody could tell me what is the expected operation and behavior? And why was it updated in this way? And then how do we get to a point of stability with it?'re kind some of these edge cases that I described are gonna get handled because the end results is instability right providers are depending on the status of the cluster, right if nodes are up down that operator inventory seems very fragile right now. So that's my first foray into operator inventory. Yeah. + +Andrew Mello: right Yeah, just scaling back right pulling back from that single ticket. + +Scott Carruthers: Yeah, so it was actually our care that did the primary code on this. + +Andrew Mello: I wanted to bring this to you… + +Scott Carruthers: So again,… + +Andrew Mello: Scott and… + +Scott Carruthers: I would suggest some… + +Andrew Mello: I think it was Scott who did the updates to the operating room I don't know I understand you guys want to do more complex stuff with gpus or… + +Scott Carruthers: what Tyler is suggesting that so we have a number of providers on this call. I and… + +Andrew Mello: the way you touch them… + +Scott Carruthers: edge cases are great and… + +Andrew Mello: but it looks like it's opening a listening service on some I think it's Port 801 or… + +Scott Carruthers: we want to discover edge cases and they maybe wouldn't even classify them as cases regardless. There's a number of providers on that. + +Andrew Mello: something. + +Scott Carruthers: I think they're has been relatively obviously we deal with them as they come up. + +Andrew Mello: and then if that listening service becomes and unavailable the whole thing goes and… + +Scott Carruthers: So I'm trying to think before you opened a issue on the hostname limitation. + +Andrew Mello: kind of as they say star T the bed it dies it falls off and… + +Scott Carruthers: I'm not sure the last time that we've had an issue opened against the inventory operator. + +Andrew Mello: and it doesn't reset itself. + +Scott Carruthers: So to answer your question generally so obviously the driver behind. + +Andrew Mello: So if it gets into an error state it just kind of stays there… + +Andrew Mello: until you pop the operator inventory pod, so + +Scott Carruthers: so the inventory operator was pre-existent,… + +Andrew Mello: I have not had a good time with it and… + +Scott Carruthers: but we initially Labeled entitled feature Discovery came about as we were doing provider incentives and… + +Andrew Mello: I did want to raise that in a call here because it's a much bigger issue than just that character limit. I've now seen at least three others that will just kill it by normal,… + +00:25:00 + +Scott Carruthers: we need the ability to have a constant inspection of gpus that are hosted on a providers in provider worker nodes so that we set up a grpc endpoint that allows I know that the cloud most team now is doing indexing against that so again that gives us the ability… + +Andrew Mello: cluster things that happen. + +Scott Carruthers: if we're incentivizing a provider we can provider our often necessary via that grpc on point. So theoretically we can pull every + +Andrew Mello: It may be Scott or Andrey. Just give me a high level of what the new operator and why it's written that way. But the listening port and setting up like a server client thing like what's going on there because I get it just came out of nowhere this spring. So I'm just kind of curious What is the expected behavior of all that why is it done that way? + +Andrew Mello: Wow, okay. + +Scott Carruthers: I come up but relatively haven't heard or seen of any of criticality in the last several months. + +Andrew Mello: Okay, that was very helpful to understand. I understand who built it and a bit more the context as I shared in my feedback. I think it needs significantly more testing specifically around managing state of the nodes and what's available because I mean you can have nodes that are not even running on a cluster and it's still trying to do Hardware discovery on them. Right the kind of the concept of round how it's maintaining that open port and connection and Reporting back what's available it needs more work. So I will file those bugs. I did want to raise it the bigger issue and kind of the high level before I filed those bugs to you guys. So you're kind of aware of what's coming. But yeah, that's my specific concern is that it's not battle tested yet and it's such a big change and the consequence is your provider does not bid and it does not show. + +Andrew Mello: So any inventory it will just show, two brackets for available and nothing inside of them. And that's what I've been seeing now for a few months and anyone's bring it up. So thank you so much Scott for filling in the detail there. Appreciate it. + +Scott Carruthers: Yeah, yeah, no problem. So again, when we have issues opened there will actually be an update on the issue regarding the hostname length later today and some validations that I've gone through for that. So, yeah, you'll have an update on that issue very shortly. I think by the end of the day today and some testing that I've done against it and if you open an issue for the STD leader change and we'll definitely validate and investigate that as well. + +Andrew Mello: yeah, and like I said, because of the way it's built right with that at CD leader change I kind of said it once so I just say it a second time before I finish here, which is + +Andrew Mello: the way that this monitoring is built is that if the cluster has any state change right? It's like to itself then that breaks the ability to monitor that colon 8001 or whatever Port that's always expecting a query and then it's kind of stupid. It doesn't do anything. It just breaks after that and exits out. It doesn't have the right condition set for the cluster, basically restarting itself, which it will do sometimes especially if you restart let's say, a leader Etc. So it needs a lot more robust testing when it expects to constantly have available one of these ports right on all the notes. So that's what I've been seeing now at scale over time and that again, if you're just running maybe one cluster if you're not gonna see this stuff and again, so that is + +00:30:00 + +Andrew Mello: Back, thank you guys so much appreciate the time. + +Tyler Wright: Thank you, Andrew and as you see these issues is always great to put them in the support repo. That's all issues where it's a core product go and then again members of the core team will look at those validate those so much appreciate the time that you put in there and thank you for bringing it up here. This is what these calls are for. We talked about updates. We talked about new tooling, but we also talk about issues related to provide her and then have discussions. So, thank you. Any other agenda items that anybody wants to cover here related to their providers or anything else provide a related on the Akash Network? + +Tyler Wright: If not, then again, we'll look for some updates potentially from damir at the next providers. If not before there are a couple of teams that have reached out to me to do some demos at the August. + +Tyler Wright: Providers meeting I'll follow up with some more details and Discord from those teams that are trying to again build microservices, I guess on top to support a cost providers. I let them explain themselves, but I know they've been reaching out to supervising the ecosystem for some feedback and testing again. We' Andrew will look to follow up and create some issues related to some of the subjects. I've… + +Andrey Arapov: Thank you. + +Andrew Mello: + +Tyler Wright: I've read goodbye. He talked about around… + +Scott Carruthers: Thanks, everyone. + +Tyler Wright: + +Tyler Wright: around the inventory operator. + +Jigar Patel: Thanks. + +Tyler Wright: And then again, we'll get some continued updates over the next month from jigarette and Deval and all the work that they're doing. If there's nothing else then again, feel free to take some time back. If anybody has any questions, feel free to drop them in the sick providers Channel and we will talk again next month. Thank you all very much for the time today much appreciate the conversation. + +Meeting ended after 00:32:28 👋 From 1f5dcd5361144538a710ac2a9a0085b6f30c261a Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 16 Aug 2024 13:20:04 +0000 Subject: [PATCH 118/138] Create meeting notes sig-support #35 (#647) --- sig-support/meetings/035-2024-07-24.md | 209 +++++++++++++++++++++++++ 1 file changed, 209 insertions(+) create mode 100644 sig-support/meetings/035-2024-07-24.md diff --git a/sig-support/meetings/035-2024-07-24.md b/sig-support/meetings/035-2024-07-24.md new file mode 100644 index 00000000..eb319c07 --- /dev/null +++ b/sig-support/meetings/035-2024-07-24.md @@ -0,0 +1,209 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #35 + +## Agenda +- Triaging issues in the support and console repositories. +- Discuss support feedback from Vanguard insiders and community members. +- Change in Meeting Cadence + +## Meeting Details +- Date: Wednesday, July 24th, 2024 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://aa2i7ytftmtlehngryvt4m6jnaxvu5ku72e34u5akdetalzdimja.arweave.net/ADSP4mWbJrIdpo4rPjPJaC9adVT-ib5ToFDJMC8jQxI) +- [Transcript](#transcript) + +## Participants +- Andrey Arapov +- Damir Simpovic +- Maxime Beauchamp +- Rodri R +- Scott Carruthers +- Tyler Wright + +## Meeting Notes +**Welcome and Introduction** +- **Speaker: Tyler Wright** +- Overview of SIG Support biweekly meetings led by core engineering team members from Overclock Labs, focusing on Akash Network issues. +- Main topics: Issues in support repo (core product) and console repo (open source console). + +**Change in Meeting Cadence** +- **Speaker: Tyler Wright** +- Proposal to change meeting frequency from biweekly to monthly. +- Focus less on issue triaging and more on general support in Discord, Telegram, and other channels. +- Formation of a new SIG for more engineering-focused discussions. +- Consensus reached to change meeting frequency to monthly. + +**Issue Triage and Discussion** +- **Speaker: Scott Carruthers** +- Reviewed open issues by sharing his screen. +- Identified only two issues awaiting triage. + +**Discussion on Inventory Operator Issue** +- **Speaker: Scott Carruthers** +- Detailed analysis of an issue related to the inventory operator when pod names exceed 63 characters. +- Found that while the DNS limitation was acknowledged, the issue did not break the inventory operator in testing. +- Suggested potential solutions: updating documentation to recommend shorter hostnames or adjusting the pod naming convention to reduce character count. +- Andrey Arapov questioned whether it was a real bug or just a cosmetic issue, agreeing to verify with the user. +- Action assigned to Scott Carruthers for further validation and user follow-up. + +**Discussion on Exposed Ports Issue** +- **Speaker: Scott Carruthers** +- Analysis of a request regarding programmatically querying exposed ports assigned within the container. +- Maxime Beauchamp clarified the request: customer needs to know the external port assigned to the internal port specified within the container without manual updates. +- Plan to investigate further with Artur's input. + +**Open Discussion on Discord Support** +- **Speaker: Tyler Wright** +- Encouraged attendees to drop questions as comments inside respective issues for async discussion. +- Shout-out to Maxime Beauchamp for handling console-related issues effectively. +- Mentioned that Discord is the main communication hub for developers using the Akash Network, with additional channels in Telegram and other platforms. +- Noted Damir Simpovic's work on improving auto-moderation in Discord. + +**Announcements and Closing Remarks** +- **Speaker: Tyler Wright** +- Reminded attendees of the upcoming SIG Provider monthly meeting. +- Noted a steering committee meeting happening the next day. +- Reiterated the change in cadence for SIG Support meetings to monthly. +- Encouraged continued engagement and feedback through respective issue comments. + +## Action Items: +- **Tyler Wright:** + - Announce the change in meeting frequency to monthly. + - Provide additional information about the new engineering-focused SIG. + +- **Scott Carruthers:** + - Review and triage any pending issues in the support and console repos. + - Validate the inventory operator issue and follow up with the user. + - Show validation steps and respond to the user about the DNS limitation impact. + - Investigate the exposed ports issue with Artur and Maxime Beauchamp. + +- **All Members:** + - Participate in the discussion of open issues. + - Monitor Discord, Telegram, and other channels for general support. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: all right, welcome everybody to six support biweekly on July 24th 2024 Historically during these six support biweekly meetings a group has been led by members of the core engineering team at overclock Labs the core contributors and creators of the Akash Network during the six support biweekly sessions a group has gone over any issues that are awaiting triage in the support repo inside the Akash Network GitHub organization. The support repo is where all issues related to the core product live. There's also another repo for a console where issues related to the open source console live and again usually one if not, Two of those repos and any issues related to the repos are discussed during the six support biweekly. + +Tyler Wright: We talked about it recently in the last six support meeting about changing the Cadence of this meeting to + +Tyler Wright: A monthly Cadence and just focusing Less on triaging of issues and more on just general support inside of Discord Telegram and other channels the goal is to again do move awaiting issues or waiting triage and have another potentially Sig that gets formed that is more engineering Focus where specific engineering discussions had again, but I think we talked about it last meeting and had a number of folks that agreed following this meeting. We will change the six support Cadence to biweekly me to monthly instead of biweekly and then look out for any additional information on a new Sig forming which will focus on more engineer and core engineering Focus endeavors. + +Tyler Wright: But today we will stick with the typical agenda. We will hand it over to Scott to see if there's any issues awaiting triage and then we can discuss any open issues anybody wants to discuss from there. Usually we have members of their cautions either such vanguards here to see… + +Scott Carruthers: okay, everyone is able to see the Open issues screen. + +Tyler Wright: if there's anything worth talking about as it pertains to support in disorder other channels. + +Scott Carruthers: I think there should be pretty quick today. + +Tyler Wright: So we'll talk about that. And then… + +Scott Carruthers: I think there's only two issues awaiting triage. + +Tyler Wright: if anybody has any other items related to support that they want to discuss today we can add those to the agenda. + +Scott Carruthers: so let's start with the one on the bottom inventory operator and when I Discovery pod name exceeds 63 character, so I actually did some testing of this. So the reports basically this is the regular DNS label limitation on 63 characters in the issue is when we spawn they inventory operator Discovery pods if this is the beginning of the Pod name We already have already starting with. What rather large amount of characters and then if we were to test and again I tested this myself and as we are expected because it's a DNS. guidance and limitation I was able to reproduce the issue if I + +Scott Carruthers: have a kubernetes worker node with that hostname and then it gets prepended by this it will exceed 63 characters and then they inventory operator will Have a log entry state in that. DNS possibly could be affected because of a name over 63 characters the interesting part about this is when I Tested this I think it may be something that we want to consider. So I'm not negating taking a look at But this issue this user reports that when you have a host name that it saves 63 characters that actually broke they inventory operator and that was not my experience. I use this exact same hostname on a worker node ahead. Gpus enabled and the inventory operator was picking up the gpus and of course all the other hardware specs as well. + +Scott Carruthers: So I think it is something that we possibly should consider but it's an interesting that so it possibly could have other Downstream effects like I didn't this was just on a test cluster. So. I can't say that there was exhaustive testing done to ensure that this doesn't have any other consequence and again, I think of something that we should look at but in my experience, it did not break the inventory Gathering. So I know that I'm both. Simply Andy are on the call. So you may have some opinions of this yourself. So to me, there's possibly two ways to go with us one would be. + +00:05:00 + +Scott Carruthers: A simple no and our documentation for a Akash kubernetes build that based on the number of characters were already dealing with here that a hostname cannot exceed whatever the remainder of that would be. So that could be a simple step or the other way to go with this and this is what this user suggested is. So this solution would still allow for the possibility of hitting this issue, but it would make it. probably far less likely and that would be an adjustment in our code so that these Inventory Hardware Discovery pods would not be spawned with a name inventory Hardware Discovery, but possibly just instead Hardware discovery. Then of course post-pended by the host name. So if we eliminated the pods whatever that would be like + +Scott Carruthers: Maybe possibly somewhere between 15 and 20 characters. We would be getting back to and then this particular host name was. 66 characters. So this example wouldn't have had an issue if we revised the Pod name in so yeah, we could and maybe there's some other suggestions as well. But off the top my head when I was looking at this we could either provide guidance and our documentation and leave or we could encode redo and edit they pod names that are assigned to again, maybe eliminate 15 to 20 characters making the issue far less likely. So, I don't know anything. I think I may have actually heard I'll somebody have there yet. Andy, go ahead. + +Andrey Arapov: Yeah. Thanks I was just wondering is there really a bug because it's just the recommendation message a warning letters to me doesn't really pose any real issue doesn't cause an issue. + +Scott Carruthers: Yeah, I agree whether it's a bug or just a suggestion and of getting what are the warning like again? If you read through this issue this user is reporting that This was actually causing an issue with the inventory operator. I didn't experience that so we could go back and I could reproduce it and show that the inventory operator and the inventory Discovery is not affected and then Go from there. + +Andrey Arapov: Yeah. Yeah. + +Scott Carruthers: But yeah to answer your question. the user claims of this introduces a bug, but that was not my experience. + +Andrey Arapov: There's nothing like he just described the bug as an inventory operator lock shows. So it just says the lock shows but doesn't mean that it doesn't work or something. It just was looking into the locks. Yeah, it's a good observation indeed just in terms of prioritization that if it doesn't really like you can ask him we can get back to him and ask him does it cause an issue besides that this warning letter if he confirms that it's just the Cosmetics then okay, we can put it as always ferric and then to think about the recommendation updates steps or because otherwise, yeah, we could also optimize the cold. Let's say call it like Opie inventory and instead of Hardware use There are many ways but people can have even longer host names. They can include the main names potentially which is not recommended but anything can be but yeah, we could recommend also those names that's what we actually do. I think in order to presentation I did not explicit. + +Andrey Arapov: Say it but in our examples you really have Node 1 or 2 in keep spraying inventory file. so + +Scott Carruthers: Yeah. Yeah, okay. Yes. I read through this. It must have been and other communication that this user suggested that the Sasha had an impact on the inventory operator so I can respond to it. I'll sign this to myself initially. I'm so good. + +Andrey Arapov: Okay. Thanks. + +Scott Carruthers: P2 and I'll just later today show the validations that I went through showing that this didn't seem to have any impact on the inventory operator. So it's basically just a warning and we could get rid of the warning by suggesting shorter post names and see how the user responds. But yeah, I definitely Don't think there's any doubt that this isn't an overly urgent matter any other questions or concerns about this item. + +Scott Carruthers: Okay, and then Going back to the other issues that are awaiting triage. + +00:10:00 + +Scott Carruthers: Just leads us one. So this Saturday I was wondering if Max was going to be on this call. I don't. see him on the call so I can definitely reach out to him and ask for further clarification or maybe some others as you read through this might have My provoke some thoughts that I didn't have but if you read through this, so obviously the title is exposed ports assigned within the container. And then Max was suggesting a customer wants to know the external Port assigned to the internal Port specified in within the container. It's currently impossible where the current For the current bit engine so find a way to prove a programmatically query the ports. + +Scott Carruthers: I assume that means exposed within the container, but I guess I had an again. I just go to Max and have some conversation about this to make sure that I understand but I wasn't exactly sure what he was requesting. Is this a request that we programmatically display all ports that are exposed within the container or is this talking about? That the user wants the ability to see the associated kubernetes nodeport for report to internal container which that is available. The least status so a user would be able to get that. So obviously in order to create status you would have to have the certificate so it's not. on chain information so I don't if you query + +Scott Carruthers: the deployment or you query the lease on chain, I definitely doesn't have that information but it is available and police status. I think I heard a hand ray. So I don't know maybe some others have some thoughts on exactly what they request is here. + +Scott Carruthers: You go ahead shampoo. + +Scott Carruthers: Yep. + +Scott Carruthers: Okay. + +Andrey Arapov: For assigned within the content assign using controlled I would even imagine not during the beat but when the container is open running so the application probably from the inside the container could just check and know which parts it's a map to because often you have some kind of minor or some kind of service that needs to know. what external Port it's Maps too. So to tell to the application locally, I remember there was case like this. Could do this. + +Scott Carruthers: yeah and after a good time in because Max just joined us so max. We're just going through issues that are awaiting triage and this is The last one in that status so we're just reading through this and I was just trying to ensure that we as a group understand what the request is here. So the node part assigned to a lease or a deployment is not available and on chain information within the appointment or ase. Data that's stored on chain. But of course you can get the assigned kubernetes node Port via lease status, but anybody can do that, but you would need to have this certificate for the deployment to be able to Get that information. So what exactly is the request here? Is it that others besides the person doing the deployment would be able to get the assignment part + +Maxime Beauchamp: So yeah, I don't remember. I need to look in this messages which customer exactly but I think it's Venice. Not sure need to look but they wanted to From the get- when creating these no. Which ports are assigned to? the port within the container itself without getting the ports assigned and then updating the deployment through environment variable and stuff. I see. doesn't make + +Scott Carruthers: okay, So That's something that they're deployment process would need to know knowledge of the assigned node part for I guess I'm just trying to understand the utility. + +Maxime Beauchamp: yeah, so within the container being able to Know which parts? Are being assigned to which part? + +00:15:00 + +Scott Carruthers: Okay, I have it now. So it's basically based on their application needs to have knowledge. What node part was assigned. Yeah, okay. + +Maxime Beauchamp: I'll try to find exactly with the details about the requests but From my memory. It was Venice. Not sure. + +Scott Carruthers: Okay, so we've had very somewhere requests to be I'm in the past for like some applications needing Knowledge of what they're External IP addresses if they're using IP leases, so now I understand that the issue. + +Maxime Beauchamp: Yeah. + +Scott Carruthers: I'll speak with artwork and do some further investigation on this but I'll just assign it to myself for All right? Yeah. Thanks. + +Maxime Beauchamp: Yeah, sure Arthur. It told me to create the issues. So he's aware of it. + +Scott Carruthers: So he's aware of it as Okay, I'll sign both of us and + +Scott Carruthers: Yeah that makes more sense. Okay, and with that, I believe that we have now. Tackled all the awaiting Treehouse issues. Are there any other issues on the board that may have been assigned prior on and that anyone wants to discuss further + +Scott Carruthers: okay with that. I'll hand it back to you Tyler. + +Tyler Wright: Perfect. Thank you very much Scott's. again, if anybody is listening to this later. If you have any questions about any specific issues, feel free to drop that question as a comment inside the respective issue and we could talk about it during the six support call or async with members of the community and Courtney. + +Tyler Wright: Cool, just as an aside. We talk about the top of the call, but I always love to shut up Max if anybody has any issues related to console again, you could drop those inside the console repo and they cost Network organization Max B who's on the call here today as well as Max seeing the rest of the team do a great job of responding to any issues and addressing them solving them in a time. They fashion. So again, if anybody has any issues related to console there is an ecosystem console Channel inside Discord as well as the console repo where you can create an issue leave a comment and again get a fast response from Max B or somebody else. + +Tyler Wright: cool moving along during this part of the agenda. I usually call upon some insiders to see if there's anything worth discussing in terms of support inside of Discord or any other channels. Again Discord is akash's main communication hub for all developers. There are some other channels and Telegram and elsewhere, but for those that are looking to build on their custom Network for use the accost Network in a technical way again, we try to push those folks to Discord where you can get real time support from members of the community Akash insiders Akash vanguards Etc. But I just want to see if there's anything on the support side or a Discord that might be worth discussing here live. + +Tyler Wright: I know that damir has previously seen some hikes in certain terms that are being used and Discord and as an Insider / Vanguard has done a great job of sharing those and making sure that we can improve the Auto mod to kind of block some of those terms. So damir shout out to you rodri. That's the same thing. I just want to see if anything on that front that maybe I haven't seen that needs to be added to restricted words inside of the Akash Network Discord server. + +00:20:00 + +Tyler Wright: excellent + +Tyler Wright: excellent Is there anything else on the support front that anybody wants to talk about here today? + +Tyler Wright: One thing I will ask is I know that many of these folks on this call are also provider focused. There is a Sig provided monthly meeting that I'll be happening in 38 minutes. There will be some discussion and… + +Rodri R: . + +Maxime Beauchamp: Thanks. + +Scott Carruthers: Thanks. + +Tyler Wright: updates from Jigger and Duval and where Prater is and again from the next steps in terms of console. So it'll be some power-up discussion on the provider build improvements led by Scott on this call and just any other provider related discussions. I know there's a group all called SC Prime looking to give a demo at the sick providers monthly meeting in August and there's been doing some behind the scenes work. But again, you all can join that supervised monthly meeting that would be great. And then there's a steering committee happening tomorrow as usual last Thursday of the month. + +Tyler Wright: But again look for the six support Cadence to change as we move this back to a monthly meeting. There will be some follow-ups about a new Sig or two that will house the triage process. But again much appreciated everyone's time and efforts today. If you have any comments about any issues again, feel free to drop them in a respective issue Meetings online. Thank you all. Have a good rest of the day. + +Meeting ended after 00:21:14 👋 From 919003cf3b4f24c1f6d62737af203ebce82047a9 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 19 Aug 2024 22:49:33 +0000 Subject: [PATCH 119/138] Create meeeting notes for Sig-community #18 (#660) * Create meeeting notes for Sig-community #18 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 018-2024-08-14.md added transcript Chore: add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-community/meetings/018-2024-08-14.md | 577 +++++++++++++++++++++++ 1 file changed, 577 insertions(+) create mode 100644 sig-community/meetings/018-2024-08-14.md diff --git a/sig-community/meetings/018-2024-08-14.md b/sig-community/meetings/018-2024-08-14.md new file mode 100644 index 00000000..5ceedeb6 --- /dev/null +++ b/sig-community/meetings/018-2024-08-14.md @@ -0,0 +1,577 @@ +# Akash Network - Community Special Interest Group (SIG) - Meeting #18 + +## Agenda +- Update on EthCC, Paris, and Brussels +- Upcoming Q3 Events +- Akash Insiders Program Overview +- Community Engagement and Opportunities for Contribution +- Update on Cosmos Event in Buenos Aires +- Discussion on Hackathons +- 2025 Event Working Group Preparation +- Follow-up on Hackathon Teams + +## Meeting Details +- Date: Tuesday, August 14, 2024 +- Time: 11:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#Transcript) + +## Participants +- Abhinav Gupta +- B S +- Damir Simpovic +- Dominikus Brian +- Fenil Modi +- oo o +- Piyush +- Robert Del Rey +- Rodri R +- SACHIN JHA +- Tyler Wright +- Ved Mohan +- Zeke E + +## Meeting Notes +### Tyler Wright +- **Welcome:** Tyler Wright hosted the meeting in Adam Wozney’s absence, who is on paternity leave. +- **Previous Meeting Recap:** Discussed updates from the EthCC event and events in Brussels. +- **Upcoming Events:** Busy season ahead with multiple blockchain conferences in the fall, including Korea Blockchain Week, Token 2049, Mainnet, and Devcon. +- **Akash Insiders Program:** + - A program for those wanting to be more involved in Akash's ecosystem. + - Developed by Adam Wozney, it offers opportunities for both technical and non-technical contributions. + - The program is aimed at developing ambassadors who can support events and grow the community. +- **Community Engagement:** Emphasized the importance of participating in Discord for those interested in applying to the Akash Insiders Program. +- **Update on Cosmos Event:** Amanda and Zach are traveling to a Cosmos event in Buenos Aires to collaborate with the Latam region and engage with new providers. + + ### **Hackathons Discussion:** + - **Sachin Spark Hackathon:** Discussed community pool spend and engagement with the hackathon. + - **Fenil Modi's Update:** Provided insights on the hackathon’s outcomes and mentioned ongoing efforts. + - **Piyush’s Update:** Reached out to winning teams, offering internships and continued support. Teams are exploring Akash and Artemis for further projects. + - **New Hackathon Proposal:** Ved Mohan introduced a new hackathon in New Delhi, with over 1500 registrations. + - **Sponsorship Request:** Seeking support from Akash for monetary sponsorship and mentorship. + - **Event Details:** 24-hour in-person event with various tracks, including a special track for beginner teams and women-led teams. + - **Sponsorship Breakdown:** 40% for prizes, 60% for event logistics and management. + - **Platform:** Using Quest platform for the hackathon. +- **2025 Working Group:** Plan to create a working group to discuss potential Akash events and representation for 2025. Community members are encouraged to suggest events. +- **Follow-up on Hackathon Teams:** Explore showcasing successful projects from the hackathon and potential marketing opportunities. + + + +**Community Engagement:** +- **Tyler Wright :** + - Encouraged community members to get involved in ongoing discussions. + - Highlighted the importance of critical questions and active participation. + - Mentioned specific team members (Domi and Rodri) for their exemplary involvement. + - Emphasized using community funds effectively to support meaningful projects. + +- **Zealy Platform and Developer Onboarding:** + - **Background:** + - Robert Del Rey and Benjamin previously discussed and piloted a developer onboarding program using Zealy. + - Initial funding was obtained from the community pool, with additional support from Greg at Overclock Labs. + - The project moved from discussions to a successful pilot, leading to a proposal for Phase Two funding. + + - **Current Status:** + - The first month of the three-month campaign is underway. + - Zealy is being used to drive demand and engage new developers in the Akash ecosystem. + - The program aims to attract developers through tasks and missions, offering rewards. + + - **Shoutout:** + - Thanks given to Robert and Benjamin for their efforts. + - A "secret word" was announced: **Marketplace Compute** (c o m p u t e). + + + +**Future Discussions and Event Planning** +**Tyler Wright:** +- **Upcoming Focus:** + - The next SIG Community call will focus on events, particularly for 2025. + - Discussions will include Akash’s presence, effective strategies, and what has worked or not worked in 2024. + +- **Event Prioritization:** + - Need to prioritize which events to attend and consider having more presentations. + - Discuss the balance between web3 and traditional web2 conferences. + +- **Demand vs. Supply:** + - Emphasized the importance of solving the demand side of the network to drive supply. + - Focus on teams and individuals building products that increase demand for Akash Network resources. + - Noted that as demand grows (e.g., from large users like Netflix), supply-side resources (CPUs, GPUs) will be utilized more effectively. + +- **Web3 vs. Web2 Presence:** + - Evaluating when to focus more on web2 conferences versus web3 events. + - Considerations for attending Kubernetes and traditional web2 conferences. + - Thinking about where Akash’s presence will be most valuable and impactful. + +**Announcements and Updates** +**Tyler Wright:** +- **Upcoming Testnet Opportunities:** + - Watch for announcements regarding the Cosmos SDK47 testnet. + - Looking for technical folks, validators, and general participants to help with testing. + - Not incentivized in the traditional sense, but there will be incentives from Overclock Labs for contributors. + +- **Busy September Ahead:** + - Key events: + - Career Blockchain (early September) + - Masari Mainnet (mid-September) + - Token 2049 (end of September) + - Additional events through October and beyond. + - Core team and community members will be active at these events. + +- **Hackathon Opportunities:** + - Potential hackathon in early September and other hackathon opportunities to explore. + +- **Engagement and Discussions:** + - Encourage involvement in ongoing discussions, including technical discussions such as Discussion 656. + - Critical questions and active participation are highly valued. + + +**Next Steps:** +- Monitor for announcements and updates regarding the testnet and upcoming events. +- Engage in community discussions and contribute to planning efforts. +- Stay updated on hackathon opportunities and event schedules. +- Continue discussions on event strategy and planning in upcoming SIG Community calls. +- Monitor and adjust strategies based on feedback and emerging trends in the industry. + + + +## Action Items +1. **Event Participation:** Encourage community members to get involved in upcoming events (Korea Blockchain Week, Token 2049, Mainnet, Devcon). +2. **Akash Insiders Program:** + - Promote the Akash Insiders Program to potential ambassadors. + - Ensure community members applying to the program are active on Discord. +3. **Cosmos Event:** Await updates from Amanda and Zach about their experience and collaboration efforts in Buenos Aires. +4. **Hackathon Follow-up:** + - Continue support for winning teams from the Spark Hackathon. + - Develop case studies or marketing content showcasing successful hackathon projects. + - Review the new hackathon proposal from Ved Mohan, including potential sponsorship and support. +5. **2025 Working Group:** Prepare for the creation of a working group to plan Akash’s presence at events in 2025. Collect suggestions for potential events. +7. Ved Mohan to create a document summarizing the new hackathon proposal and share it in the Sig Community chat for further discussion and feedback. +8. **Involvement in Testnet:** + - Prepare for involvement in the Cosmos SDK47 testnet. + - Keep an eye out for specific announcements and details. +9. **Event Participation:** + - Prepare for a busy September and October with various events. + - Plan engagement strategies and participation accordingly. + +# **Transcript** + +Tyler Wright: All right, welcome everybody to Sig e monthly It is August 14th. 2024 much appreciate everyone's time for being here again. Usually he's meetings are run by Adam Watson ahead of community for overclock labs. Usually there's a number of insiders as well as this General community members here. I am going to be running the meeting in his absence. He should be back shortly. He's out on paternity leave. So again respecting his time. + +Tyler Wright: there's a couple of items last meeting we talked about ECC we talked about Paris. We got update from Amanda and all things that happened. Excuse me out in Brussels rather. + +Tyler Wright: We talked a little bit about the upcoming period and the Q3 events support proposal that went on chain and has since passed. I know we're about to get into a very very busy season where There's a number of events happening in the fall including Korea blockchain week token 2049. I'm sorry mainnets Devcon Etc. So again, it's a bit period as many of there are opportunities for + +Tyler Wright: folks from the community to join and participate in support some of these conferences. There is an Akash insiders program, which people can apply to it's a program for those that want to get more involved in Akash and again development support users that are trying to get more involved join sigs and working troops groups. There's a number of Technical and non-technical ways to contribute and so a caution scientist is a program first developed by Adam to kind of be a home for those that are looking to be ambassadors and again through the Tires program there's additional opportunities for folks to get involved with in real life events hosting their own events Etc. + +Tyler Wright: If anybody sees anybody in the community that wants to get more involved again, there is a page on the website where people can apply The Insider program. There is an emphasis on people inside our program that actively participate in Discord. It's hard for me to follow up with somebody or anybody that's helping out with the inside applications when that person doesn't have any activity in Discord. So just something to note for yourselves. And again people that she may come across in the community. + +Tyler Wright: There are a couple of items that I wanted to make sure that we touched on as a group Amanda is actually on her way to travel to a verse event in Buenos Aires happening. I think it's a cosmo first lot. I am event both Amanda and Zach will be representing Akash looking to again collaborate with people in the ladam region continue to get more providers and on from that region as well as deployers. So again, we'll get an update from them. I probably have the next Sig community meeting and maybe prior to that the steering committee meeting. In terms of agenda items as previously mentioned there was a couple of things that I want to make sure that were covered at this event here today. There was a couple of + +Tyler Wright: events that have happened Including Sachin spark hackathon that happened. There was some community pool spend that was used for that. There was a discussion fenil who I think is on the call was there are a couple other hackathons actually that are up for discussion right now, and I want to see if anybody from those discussions also here to talk to the community about their small efforts so we can get some again Community feedback beyond that when Adam wozni returns again, I want to start to prepare for what could be a working group around 2025. I think we're getting to the point where + + +### 00:05:00 + +Tyler Wright: It'd be great for folks to come together from the community to start to talk about potential events that Akash should be at in 2025 what our President should look like at these events and Beyond. So again, we'll probably create a working group in September October to cover 2025 and start to get a bench signaling proposals kind of geared up. So again, if anybody knows of any events that they think a cost should be at to be represented that please start to write those things down so that we can get those things ready for our next Sig Community call and subsequent working group. + +Tyler Wright: All I do want to start with some follow-up and I'll drop in some notes from discussion again. I know that there was a hackathon where there was some and Spark hackathon. That was run by fenil who is in Akash Insider. He was also somebody that participated in the last Akash hackathon the cosathon too and So I wanted to get an update because I know there was some again community pool spend thank you very much for all that. You've done in a reporting you and piyush who's also in the call also an Insider active member in the community who's been working on a number of things from website revamp to console support, but for now, I just want to get a check in with you. See how things went with the hackathon. + +Tyler Wright: And any next steps and maybe piyush I know that you were all there in person. So feel free to chime in on finding some winnings Etc from the spark hackathon that happened Believe at the end of last month. + +Tyler Wright: Thank you for Question for you. Did any of the teams are they continuing to use the caution in any way or have any new team showed interest in getting more involved in Discord and supporting the growth of a cost. Have you been able to follow up with any teams and see how things have been going since the hackathon? one go ahead. Peace. + +Tyler Wright: + +Piyush: Yeah, so basically we used out to some of the winning teams and we also put them internships as well to basically continue the work that they are doing since they are a student I think offering them some good in Concepts and elements and all could be a great opportunity for them to learn and move forward with their carry so they're all so using for attending elements and all they are exploring how they can use Akash and Artemis continue to support them so with proper funds and all that's all + + +### 00:10:00 + +Tyler Wright: Excellent piyush. + +Piyush: Be yeah, so yeah, I will get a panel to the silicone of the proper block and… + +Tyler Wright: I know that this but if you see anything that's worth sharing from a marketing standpoint,… + +Piyush: I think we can ask this was the first time button sponsored by a cartoon in India. + +Tyler Wright: certainly because a blog or… + +Piyush: I think this can be a great boost for others… + +Tyler Wright: some sort of case study following some of the work from the winning team. + +Piyush: who wants to use in India. So this work with panel and… + +Tyler Wright: So again, this… + +Piyush: come up with the proper blocks very specifically. + +Tyler Wright: but if there's any way for us to continue to Showcase some of the great work from some of the individuals during the hackathon, please keep those front of mind so we can think about how to execute that. + +Ved Mohan: Hey. Hey, how are you? + +Ved Mohan: Anonymous yeah, I'm good. How are you? + +Ved Mohan: Hello, I'm So as the piyush about the hackathon that our sponsor for the first time so I would just to bring you another opportunity or… + +Tyler Wright: excellent + +Ved Mohan: Akash Network that we are doing a hackathon also it will be here 24 hours in person icon with over 300 folks in New Delhi the capital of India and… + +Tyler Wright: Adrian I see a hand Go ahead Ved. + +Ved Mohan: the new for that I cannot like on is triple it it's really pretty steam Institute of India. + +Tyler Wright: Good, how are you? + +Ved Mohan: And we have already got more than 1500 plus registration for the hackathon. + +Tyler Wright: Good good. + +Ved Mohan: So I was just wondering if Akash Network can support this hackathon by any + +Ved Mohan: yeah. Yeah, we were doing a conversation but I don't know due to some error with sending the links the GitHub account got suspended. So we continued the discussion on telegram that we have created a group with Akash on Telegram. + +Tyler Wright: 's been started? Is there a discussion that you've already your first? + +Ved Mohan: yeah. + +Tyler Wright: excellent All right. + +Tyler Wright: I see a hand up. I know this is a new discussion. I think is there any way you can drop a web page or something in the chat for folks in the community real quick peers before you have your hand up in bed before you continue again? It'd be great to drop some links in. I just want to if anybody had any questions or comments about the spark hackathon that was run by fenil and supported by piyush and… + +Ved Mohan: No, it's from GitHub side. + +Tyler Wright: India before we move on to any other hackathon related topics. + +Ved Mohan: It's gonna not from our passenger. + +Tyler Wright: All Yeah again I know that you originally put a Converse a discussion up but I think there's been an issue with GitHub. + +Ved Mohan: Yeah, that's the registration page. + +Tyler Wright: I'm trying to track it on to see… + +Ved Mohan: You can look through the registration page and… + +Tyler Wright: if it's Akash Network organization related issue… + +Ved Mohan: find some details about that. Also if you want we can share the website of the animal. + +Tyler Wright: which I don't think it is. + +Tyler Wright: But again much appreciate you being here. + +Ved Mohan: But 24 hours. + +Tyler Wright: This is a group where people live and we'll be able to look at the recording. It'd be great to have a little bit more information. + +Ved Mohan: Yeah. It will have two plus web 3 hackathon and… + +Tyler Wright: Okay, I get to drop in a link here. + +Ved Mohan: we have some with responses dissolved on request. + +Tyler Wright: Cool, so the hackathon is about 24 days out. + +Ved Mohan: Probably monitor monetary sponsorship and some mentorships and… + +Tyler Wright: Okay submission closes in 24 hours,… + +Ved Mohan: all about that. + +Tyler Wright: but it's September 7th and… + +Ved Mohan: I was also building a project about cloud gaming and… + +Tyler Wright: 8th, right? Okay, it's in New Delhi. + +Ved Mohan: I was just wondering throughout the different places… + +Tyler Wright: It's a 24-hour hackathon. + +Ved Mohan: where I can get some support whether that's… + +Tyler Wright: What is the theme of the hackathon? Like what? + +Ved Mohan: where I got to know about the Akash like that. I can build my product Network also, but that's a different topic. But yeah. + +Ved Mohan: Not really. + +Tyler Wright: Okay, and what are you looking for from the Akash team? + +Ved Mohan: I was just looking through it. I was using Azure for right now, but I was just looking through the Akash and I am thinking it would be great if I can do with Akash also. + +Tyler Wright: Okay, so have you been using a cache yourself as a event organizer? + + +### 00:15:00 + +Ved Mohan: We can surely take any person at the venue or… + +Tyler Wright: Okay, is the idea that there would be included with the spot potential sponsorship there would be somebody from the Akash community that would be joining the event to provide on the ground supporter. + +Ved Mohan: we can do online workshops to teach them about Akash and something like that. + +Tyler Wright: How do you envision being able to support users that are asking about Akash without having built on it yourself,… + +Ved Mohan: I guess it was thousand attached opens as far I remember I was not talking I would never was talking. I don't know. Are you here? + +Tyler Wright: I guess. + +Abhinav Gupta: Here, I'm like just doing The discus on guitar, but from some sanding some importance and actually heavy is asked for some importance link. + +Tyler Wright: And… + +Abhinav Gupta: So I share that some Lanes so from the GitHub,… + +Tyler Wright: then what is the amount that the sponsorship? + +Abhinav Gupta: my account is suspended but in the discussion, I also mentioned that we are expecting around 1000 akt it's a network tokens. So we use these tokens to provide a prizes to the parts. Sprints so doing some support in the logistic. + +Tyler Wright: Okay, so the 1000 akt tokens. You said the breakdown what percentage would be broken down for? + +Abhinav Gupta: Yeah, we are dividing the amount in the percentage of 40% We allocated to the price fund and… + +Tyler Wright: Giving to hackers to use versus management costs. Do you have a breakdown of that? + +Abhinav Gupta: 60% of the monetary support. + +Tyler Wright: So for the people because again, we have no problem of there being a management cost. + +Abhinav Gupta: We are covering the event Arrangements including venue logistic and… + +Tyler Wright: We don't want people to be necessary working for free,… + +Abhinav Gupta: supplies and… + +Tyler Wright: but we want to be very clear what's going to go towards people deploying slash rewards for the project versus what's going to be going to the team that's putting on the hackathon. + +Abhinav Gupta: that makes the part spent experience more better. + +Ved Mohan: It was 60% 40 for the prices and 64 the other logistics menu for any other things that we have arranged for the Packers. + +Ved Mohan: Yeah apart from that. We have done few special things. we have put it 30% seats reserve for the beginner so that we can make our hackathon being a friendly and… + +Tyler Wright: Okay, so he said 40% for rewards and… + +Ved Mohan: we have included a special track price for all Best Fitness. + +Tyler Wright: prizes 50% for a venue and… + +Ved Mohan: If you scroll down you can see that pricing and we have also a special track for all test best all girls team. Yeah. + +Tyler Wright: other costs and then what was the last 10% I'm sorry. + +Ved Mohan: It was just scroll down you can see in the reward session. Just a little bit about All investing you can see also we have included a game development track. + +Tyler Wright: Got you. Okay. + +Ved Mohan: best dignity August + +Ved Mohan: Yeah, we are hosted around three to four different hackathons. if I tell about our community, we are a group of different Community leaders and we all came up together to organize this account. So yeah, as a community. We have all stood around to the icons, but why the different organizers? + +Tyler Wright: Good, do you have experience hosting hackathons previously or is this your first effort? + +Piyush: Yeah, so I have a question for both web and been over so as I can see the value you guys have decided is to collect so I just like to know who is the student at reply to be responsible for taking care of all permissions from the management and… + +Tyler Wright: Okay. + +Piyush: all so a little bit of the team is in important… + +Tyler Wright: does anyone else have any questions for? + +Ved Mohan: Yeah, okay. + +Piyush: if you want it you can share + +Tyler Wright: Bed and the team go ahead piyush. + +Ved Mohan: Yeah, okay, as I already told you we are a group of different Community leaders and we have students throughout different state of India and different colleges of India. And for the venue. + +Piyush: presentation + +Ved Mohan: We have partnered with the IEEE chapter of tribality Delhi so that they are helping us to get the ring. + + +### 00:20:00 + +Ved Mohan: Yeah. I + +Ved Mohan: understand + +Ved Mohan: we will do that. Yeah, thanks for that huge. + +Tyler Wright: Does anyone else have any other questions about this proposal? + +Tyler Wright: Go ahead from you. + +Fenil Modi: Yeah, I have custom for today as per you said you have organized I had done in past. So can you just name that hackathons? + +Ved Mohan: Yeah back with India had no wait, and what was in my forward one name like? + +Abhinav Gupta: our reorganized Yeah,… + +Ved Mohan: You know what this? + +Abhinav Gupta: I'm also the organizer of hat with India and second one is I have no wait five and… + +Ved Mohan: right + +Abhinav Gupta: third one is a build with Delhi and fourth one is a hack with Kelly. So for these four hackathons and the organizer on this accounts. + +Ved Mohan: Yeah, it would just share the links here so that they can just see. + +Fenil Modi: yeah. + +Abhinav Gupta: Yeah, give me a second. I'm saying that. + +Tyler Wright: That would be great. + +Tyler Wright: Anyone else have any questions? For Ved and the rest of the team. + +Fenil Modi: Which was a platform you used for the hosting the icon therefore what? + +Ved Mohan: Here for the previous one it was defolio for this one yet sequest like headquarters just started hosting hackathon. So this is their first Community hacking on also. + +Fenil Modi: Okay, yeah. request + +Abhinav Gupta: And we find it hack Quest it's starting so it's like providing a good features. That's why we are using that. + +Fenil Modi: for my account request also a great for color presentation, but they are trying to Google update with me the else are selling their courses to our hackathon hekinom participant and that's why I said no toequest like that. I am asking why are organized on a quest platform? + +Ved Mohan: Yeah, but they didn't tell us something like that because this was their first account. So they just wanted to host them and on their platform. + +Fenil Modi: Okay. + +Abhinav Gupta: right + +Ved Mohan: Also, I guess request doesn't sell courses. They are free of cost anyone can learn about the three as far as I know and see. + +Fenil Modi: Because they also reached out to meet for the heck, but all sparkly some organization request, but they're trying to save the hotel. I don't even in the forehead request and Mars Market our courses and get 1,000 decision on our courses and… + +Ved Mohan: yeah. + +Fenil Modi: they are asking for that way. + +Ved Mohan: I don't know Did this kind of deal? We just want it as a platform since they also know about … + +Fenil Modi: Okay. + +Ved Mohan: what people will like, no one wants to see this kind of partnership. + +Fenil Modi: Can you show your last second of pages one day for you? + +Abhinav Gupta: Yeah, I still like a happy link on a check. + +Fenil Modi: Can you open this trailer? + +Fenil Modi: second office + +Abhinav Gupta: You some website. Also, I shared a defolially. + +Tyler Wright: I think piyush has a great next step of because discussions are blocked. If you can just make a dock including all this information and we can continue this conversation in the Sig Community chat. That would be a great neck great next step. I do appreciate you all taking the time to join this call. I will drop this recording into Sig Community as well just for other people to weigh in just as a note because we just want to hear what the community thinks about this and the fenil proposal didn't come from community pool spend it came from different pools of money that are available. But again, we want to use this as a place for people to + + +### 00:25:00 + +Tyler Wright: Some gauge interests again. There's so many people in the community that I just wanted to get it out and open and see where the involvement just necessarily wouldn't come from community pool because it's a smaller akt request but again I do want to get the opinion of the community continue to vet this team very similar to that. We did with the spark hackathon team and then determine if this is an opportunity worth pursuing. So again bad if you all can put a conversation in a doc together in sick community, that would be very helpful. The quicker you do that the quicker will get conversation going and again we can figure out next steps from there. + +Tyler Wright: any other questions on this hackathon or any other hackathons before we move on to some other topics? + +Tyler Wright: All right. + +Tyler Wright: Shameless plug time for again as a part of the community efforts. We're always looking for people to get involved in discussions. There are a couple of discussions that are active right now that have been active that have been created in the last couple days. I'm going to drop those in the chat. There's a couple of teams I think that some of our court team members meant out in Denver that are looking to get more involved in Akash and have talked about basically an idea that they're looking to explore so I would be great for people to get involved in these discussions. Ask critical questions. Shout out to Domi who always does a great job of doing that rodri also is active. But again, please please get involved in the discussions that goes for any Community member if anybody wants to see additional opportunities in which they see pushing their cost Network again a great sign to show + +Tyler Wright: whether or not something needs community pool spend something should be actively worked on. please please feel like you should get active in those discussions at critical questions hold people accountable, but we do want to continue to use Community funds and the community pool to support the proper projects that are looking to advance that cost Network. So, please get involved in those discussions. that is also a natural segue into I know there's a specific working group for this but + +Tyler Wright: There was again some time ago Robert Del Rey and Benjamin from the community from insiders talked about a developer onboarding platform. They looked at zeely. There was some initial pilot spend because it's a small dollar amount similar to some of these hackathon efforts that were provided to Robert to do initial Pilots of the developer onboarding program. There was successful in that developer onboarding program from there. There was discussions made their Roberts and Benjamin talk to the steering committee and then they put up a proposal for funds from the community pool. They got those funds in the community pool. And then Greg from the overclock Labs team also matched some of those funds the phase one and… + +Robert Del Rey: Hey Tyler, Don. Thanks. And hi everybody. I believe you put it perfectly the process of having these idea and… + +Tyler Wright: I proposal was successful and again that launched then creating a discussion around two phase two proposal went on chain and… + +Robert Del Rey: then making it to our reality. It was exactly as you describe it we started just talking about the idea. + +Tyler Wright: that proposal. + +Tyler Wright: Pass on chain. And so now again we've gone through this kind of path of again discussions discussions turn into a pilot program pilot program turns into a success of that private program turns into community pool spend and… + + +### 00:30:00 + +Robert Del Rey: Then we went on and decide to do a pilot then when discussions then went on chain and the rest of the history. So yeah. We are on our way to complete week number two of the first month. It's gonna be a three month campaign. + +Tyler Wright: we can continue to again use the open source framework and… + +Robert Del Rey: So there is enough time for everybody to join and do the missions. + +Tyler Wright: the governance to get funds. + +Robert Del Rey: I actually wanted to have just one minute to say the secret word or… + +Tyler Wright: Shout out to Robert and Benjamin for all the work they do I know there's a working group,… + +Robert Del Rey: the community working group mission. + +Tyler Wright: but I just want to see if there's anything that you want to highlight on the developers onboarding program here today for the community call. + +Robert Del Rey: And The Secret World guys. I hope you're paying attention. I know you are rodri the secret word. It's gonna be Marketplace compute c o m p u t Yes, I sent an in the chat. + +Tyler Wright: Thank you Again. There's zeely working group sessions. There's a Discord Channel. There's entire platform with the intention of again getting new developers from the zeely ecosystem or just new developers that are looking for specific awards for different tasks to get more involved really trying to drive Demand on the network as well as continue to find new developers that can help out with very sigs working groups Etc. So much appreciate Robert Benjamin for all their efforts. Any questions on zeely before we continue on with the agenda? + +Tyler Wright: I wanted to see if there's anything else that anybody wants to talk about again with Amanda on our way to traveling towards Buenos Aires. I think we'll focus on the events at the next Sig Community call unless anybody has any objections again, I'm going to and we could talk about the next Sig Community call, but I think we're gonna make another working group that has a meeting or two for events in 2025, talking about our presentation talking about the Akash presence, talking about things that have worked and haven't worked maybe at events in 2024… + +Dominikus Brian: One going to be sort of a little bit more prioritize. + +Tyler Wright: what events we should be at? do we need to have more presentation? + +Dominikus Brian: Do you know anything about that or? + +Tyler Wright: We need to be more events,… + +Dominikus Brian: in general + +Tyler Wright: we can have all those discussions following our next Sig. but yeah, I just wanted to again see if there's anything else that anybody wants to talk about Community facing at this time. I think that's a community question. I think that's a great question. If you want to hear my answer, I believe that it should be demand. I believe that once you solve the problem of demand then there's going to be a whole bunch of Supply that is we know is sitting idle that is going to be spun up very quickly. So for me, I'm always interested in teams and individuals that are building products that as they grow. Go ahead Their usage of the Akash Network grows. So, we've seen a bunch of companies AI space But even from a workflow standpoint, I won't say that traditional Cloud, but + +Tyler Wright: + +Tyler Wright: again, there are clouds that benefit from demand side of a Netflix using their product as Netflix has more users Netflix has more as their product grows their need to use + +Tyler Wright: Said Central Cloud could grows. I think from a cautious side. That's when you'll continue to adoption and continue to growth on the supply side is when there's so many projects are looking for gpus resources looking for any sort of competing compute resources and it's an easy self for overclock Labs easy sell for people in the community to be like, you have CPUs or you should bring them on because you will make money tomorrow because there's so much demand for it. As you mentioned I think both sides of the marketplace are going to be important, but my vote would be demand and I'll talk a little bit more about that to your point. Don't me? I think another thing to think about is we've + + +### 00:35:00 + +Tyler Wright: As a cost Community, I've spent some time thinking about the web three ecosystem and then we think about when it's a time to focus a little bit more on to developers web to ecosystem. When is that right time to go to some more web to conferences? So continuing to think about that where our presence is most valuable and… + +Dominikus Brian: Great totally agree. + +Tyler Wright: web 3 where it's most valuable and around the deep in narrative, how that ties into web 3, or maybe we need to be doing kubernetes conferences more traditional web 2 conferences and thinking about those questions holistically and more specifically what events we should be at would be great things to start thinking about + +Tyler Wright: any other topics that anybody wants to discuss that haven't been discussed. + +Tyler Wright: look out for some announcements over and next week or two. There's gonna be some opportunities for people in the community to get involved in testnet for Cosmos 47 or customers. That's okay 47. It's not like an incentivized test net like we've done previously where there's a bunch of people that can come in you can get rewards but we are looking for technical folks validators providers just general people that can work with the CLI work with consoles to help with testing. There are some incentives that are going to be from overclock labs to help with the testing to help the core engineering but again, + +Tyler Wright: It's not going to be centiv testing it has been incentivized testing it has been traditionally but we do need some Hands-On deck. So look out for announcements there again, the schedule of the next couple weeks will get truncated. Next Thursday will be the steering committee because as you all know September is going to be extremely busy from an event standpoint with career blockchain at the beginning of the month Masari maintenance in the middle of the month talking 249 at the end of the month and then a whole bunch of other events happening into October and Beyond actually, I'm sorry. I mean it might be at the end of the month as well. So just a whole lot going on that's again that core team and members of the community will all be active out. So yeah, and then again, there's also potential opportunities for a hackathon in the beginning of September other hackathon opportunities. So there's a whole lot going on among some console up. + +Tyler Wright: It's core product updates. So, please look out for updates. Please get involved in discussions. There's several couple of really good interesting discussions again one. I'll drop in the chat discussion 656 from a technical team that I have. Connected with so please get involved in this discussion ask critical questions… + +Ved Mohan: Yeah sure that. + +Tyler Wright: because again continuing to drive demand is on everyone's mind and some of these teams might have in front of mine, but they're always looking for on people that get involved in discussions. + +Tyler Wright: All right, if there's nothing else then I'll certainly let you all go a couple minutes early. + +Robert Del Rey: Right. Thanks guys. Stay safe everybody. + +Tyler Wright: But again much appreciate the conversation around hackathons around events, please Ved get involved create that document that doc so we can continue that conversation in the Sig Community Discord Channel and… + +Rodri R: today + +Tyler Wright: look to get something figured out sometime soon. + +Tyler Wright: much appreciate everyone's time today again great conversations. As always. Hopefully Adam will be back next time we meet so you don't have to deal with me anymore. But again, it has been a pleasure to be here in Adams absence. Thank you all very much. See you all in the metaverse. + + +### Meeting ended after 00:39:49 👋 From 67598e702f308f67b5cf5f99618a5d48ef365bbf Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 23 Aug 2024 01:31:04 +0000 Subject: [PATCH 120/138] Create meeting notes for sig-chain #19 (#659) * Create meeting notes for sig-chain #19 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 019-2024-08-13.md added transcript chore: add recording link Signed-off-by: Drinkwater * Update 019-2024-08-13.md added recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-chain/meetings/019-2024-08-13.md | 104 +++++++++++++++++++++++++++ 1 file changed, 104 insertions(+) create mode 100644 sig-chain/meetings/019-2024-08-13.md diff --git a/sig-chain/meetings/019-2024-08-13.md b/sig-chain/meetings/019-2024-08-13.md new file mode 100644 index 00000000..db870f4c --- /dev/null +++ b/sig-chain/meetings/019-2024-08-13.md @@ -0,0 +1,104 @@ +# Akash Network - Chain Special Interest Group (SIG) - Meeting #19 + +## Agenda +- Introduction and overview of the meeting purpose +- Update on Cosmos SDK 47 upgrade +- Network upgrade preparations and timeline +- Community engagement and validator participation +- Open floor for additional discussions + +## Meeting Details +- Date: Tuesday, August 13th, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://bcp7f4xex34ci3vtw7rfaeonelh52dkaqdb26xjfs67jojmips7a.arweave.net/CJ_y8uS--CRus7fiUBHNIs_dDUCAw69dJZe-lyWIfL4) +- [Transcript](#transcript) + +## Participants +- Artur Troian +- B S +- Robert Del Rey +- Rodri R +- Scott Carruthers +- Tyler Wright + +## Meeting Notes +- **Introduction (Tyler Wright):** + - This is the monthly meeting for the Sig Chain Special Interest Group focused on the Akash blockchain and related topics. + - Discussion covered Akash blockchain, core code, network upgrades, and anything related to the Akash SDK and the broader Cosmos ecosystem. + +- **Cosmos SDK 47 Upgrade Update (Artur Troian):** + - The team has completed the migration to the latest SDK 47 version, including successful unit tests and joint migration tests. + - Current focus: preparing the testnet and test cases for the upcoming network upgrade. + - Internal issues have caused slight delays; the upgrade might extend to next week. + - Validators will be encouraged to simulate load on the testnet for comprehensive testing. + - Expected to finalize upgrade details by the next meeting. + +- **Network Upgrade Preparations (Tyler Wright):** + - The core engineering team, led by Artur, has been working hard on the upgrade. + - Testnet participation from the community, especially validators, will be crucial. + - Upcoming announcements will provide specific requirements and structure for the testing phase. + - Community calls may increase in frequency as the network upgrade approaches due to the significant scope of the upgrade. + +- **Community Engagement (Tyler Wright):** + - Validators and community members are encouraged to stay engaged and prepare for the SDK 47 upgrade. + - The upgrade will involve changes across the entire code base, requiring coordinated efforts from all participants. + +- **Zealy Mission Announcement (Robert Del Rey):** + - Robert wished the team good luck with the network upgrade efforts. + - Introduced the secret word for the Zealy mission related to the Sig Chain working group call. + - Secret word: **"November"** spelled out as N (November), O (Oscar), V (Victor), E (Echo), M (Mike), B (Bravo), E (Echo), R (Romeo). + - Participants can use the secret word in the Zealy mission to earn additional AKT points while engaging in Akash Community initiatives. + +- **Closing Remarks (Tyler Wright):** + - Recapped that the meeting was about to end and summarized key points for Rodri, who joined late. + - Reiterated the importance of community involvement in the upcoming testnet phase. + - Validators, especially technical members, are encouraged to participate in spinning up testnet nodes to enhance the testing process. + - Acknowledged the hard work of Artur, Scott, and the core engineering team. + - Announcements will be shared over the next few days into the following week as preparations for the testnet advance. + - Tyler thanked everyone for their time and participation, indicating the meeting was adjourned. +## **Action Items** +1. **Artur Troian:** Continue preparing testnet and test cases for SDK 47 upgrade. +2. **Tyler Wright:** Reach out to community members and validators interested in participating in the testnet. +3. **Core Engineering Team:** Finalize the testnet requirements and ensure readiness for the upgrade by the next meeting. +4. **All Participants:** Stay engaged with the community and prepare for the upcoming network upgrade; watch for announcements on specific requirements. +5. **Tyler Wright:** Schedule additional community calls as needed leading up to the network upgrade. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to Sig chain monthly. This has been a monthly meeting for some time. It is August 13th 2024 during the special interest group for the Akash blockchain. The group goes over anything related to cost blockchain or the core code as well as Anything related to network upgrades? We also talked about things related to cost us SDK in general. So anything from the Costco's ecosystem. I know there's some folks that have joined this call that a validators and other change. It might have experiences there that we can take into One of the big items that Sig chain has been tracking is been around the cosmos 47 Or problems sdk47 upgrade I will drop in. + +Tyler Wright: The project there, but I'll hand it over to hartchurch just talk about anything related to Cosmos. That's the k47 upgrade or anything else that he wants to talk about Sig chain related. So Archer feel free to take it away. + +Artur Troian: I'm sorry. Hello Alrighty, so the sdk47 which would be named topic of discussion for the last couple chains. Last week we have robbed up the code base migration so much actually, as well as not repo have migrated to the latest sdk47 question and all of the tests including unit tests and Joint last dollars migrations person Which is quite a good sign. So this moment stream is preparing testnet as well as test cases on how we going to run and you ate actual upgrade. + +Artur Troian: we are running a little behind you to couple internal hydrology issues that means to be solved. So I think initially we planned to Personal this week, but we might actually be trying to next week, which is not quite a big deal. + +Artur Troian: but anyways, we're gonna try this week to publish that's not the requirements that we would like To have and as well as there is a thought that we might ask holidays to vulnerabilitator. This is mainly predators to start a mods on the testnet as well just to simulate Lord as much as you can. wrapping that up I would say This is over there. How free today? Hopefully by the next time we meet here in the school. You should have more or less finalized date of when actual brings happen. questions + +Tyler Wright: Thank you Archer and Artur not only update overclock Labs core engineering team will make them updates. + +Tyler Wright: As comments on all the progress. I think there's been constant tracking of that inside the project that I just dropped in the chat. But in addition to that I as Artur mentioned there will be members of insiders the validated community and just a general community that will be participating in various test that's coming up soon. So there'll be announcements following up shortly on specific requirements. I'll be reaching out to individuals that have already showed interest in helping out and again can provide value and then we'll just provide again structure on how that will happen. So I know it's been a lot of work happening with the core team, many late nights long weekends so much appreciate all the work from Artur really led by Archer with support from the rest of the core engineering team. I know there's gonna be a lot of work that happens now on during the testing phase and make sure + +Tyler Wright: ready for a network upgrade + +Tyler Wright: Both does anyone have anything? Chain related that they want to discuss right now. Again, look out for announcements coming soon. There will be potentially an increase Cadence for some of these Community calls as we get closer to network upgrade again to produce such a big Network upgrade and so many things are being touched really the entire code base. So please stay tuned if you're listening to this recording if you're here and you're an Insider barrier and you're very involved in the community just again. + +00:05:00 + +Tyler Wright: Continue to remind people to stay engaged around the Castle's sdk47 upgrade because again, they'll be really at all hands on deck effort to make sure we're ready for the upgrade so much appreciate everyone's time today. If there's nothing else go ahead Robert. We have your hand up. + +Robert Del Rey: Sure, a brief introduction. First of all, good luck everybody in these work of taking the network if there's anything we can do to support. We are right here and I went to drop the secret For the silly mission for the six chain working group call. And the secret call sorry and the secret word. It's gonna be no. + +Robert Del Rey: Know anything November I was in All-Star Diaz in Delta. E as in Echo. You can hear not now or you can listen to the word in the recording so meet the secret word in the silly mission to earn some extra akt points. While you're getting involved in other cash Community initiatives like this one. Yeah, that's all for me. + +Tyler Wright: Excellent. Thank you Robert. And again, this is for rodri who just joined us. We're about to hop off. + +Tyler Wright: Archer gave us a quick announcement again. We'll be moving into a test net phase sometime over the next couple of days to a week. There will be a number of announcements that are shared in Discord and Elsewhere for those that will be participating again. we will be looking for some validators to help spin up test that nodes to simulate again a better experience for testing. So a project I know you're a validator but we'll make sure to again get all the appropriate people involved during those steps make announcements anybody here that sees anybody in Discord or elsewhere that is Technical and has been involved what's again involved in testing process, please Point them alive direction or reports the sick chain, and we can follow up there. + +Tyler Wright: But again much appreciate all the effort from Archer Scott and the rest of the core engineering team. There'll be some more announcements coming soon as we get closer to again publishing information and starting the testnet. So look out for information over the next couple of days into next week, but appreciate everyone's time here today. Enjoy the rest of your day, and we'll follow up very soon. Thank you again. Bye. + +Robert Del Rey: Thank you as they said guys until next time. + +Meeting ended after 00:08:15 👋 From c0a7853a0359e1768caf22b6abcd51e1ded62818 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 23 Aug 2024 01:41:55 +0000 Subject: [PATCH 121/138] Create meeting notes for sig-Analytics #13 (#663) * Create meeting notes for sig-Analytics #13 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 013-2024-08-15.md add transcript Chore: add recording link Signed-off-by: Drinkwater * Update 013-2024-08-15.md added recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-analytics/meetings/013-2024-08-15.md | 192 +++++++++++++++++++++++ 1 file changed, 192 insertions(+) create mode 100644 sig-analytics/meetings/013-2024-08-15.md diff --git a/sig-analytics/meetings/013-2024-08-15.md b/sig-analytics/meetings/013-2024-08-15.md new file mode 100644 index 00000000..686a528f --- /dev/null +++ b/sig-analytics/meetings/013-2024-08-15.md @@ -0,0 +1,192 @@ +# Akash Network - Analytics Special Interest Group (SIG) - Meeting #13 + +## **Agenda** +- Introduction and overview of the Analytics Interest Group +- Updates on the open-source indexer solution +- Feedback from the community +- Open floor for additional topics + +## **Meeting Details** +- Date: Thursday, August 15th, 2024 +- Time: 09:00 AM PT (Pacific Time) +- [Recording](https://j3ac6jsjcqd3hmfii6dophi4gunxiuqqxdeslkehhz6fpnvvgkta.arweave.net/TsAvJkkUB7OwqEeG550cNRt0UhC4ySWohz58V7a1MqY) +- [Transcript](#transcript) + +## **Participants** + +- B S +- Maxime Beauchamp +- Maxime Cyr +- Robert Del Rey +- Rodri R +- Tyler Wright + +## **Meeting Notes** + +**Introduction and Overview of the Analytics Interest Group (Tyler Wright)** +- Tyler Wright introduced the meeting as part of the ongoing efforts of the Analytics Interest Group. +- He highlighted the group's historical focus on developing an open-source indexer solution, which is now available as open-source. +- Tyler mentioned that updates on the indexer and other relevant topics would be discussed, with community feedback encouraged. +- He informed participants that information from the index service is available on [stats.Akash.network](https://stats.akash.network/) for tracking and monitoring. + +**Updates on the Open-Source Indexer Solution (Maxime Cyr)** +- Maxime Cyr provided an update on recent changes to the indexer: + - The team added tracking for persistent storage alongside FML storage. Currently, persistent storage is combined in the UI, but it will be separated into its own graph in the future. + - The retry interval for time checks on providers was reduced, enabling providers to come back online sooner after a failure. + - A small bug was found and fixed in the indexer, which affected only 0.0001% of the value, having no significant impact on the statistics. +- Tyler Wright asked Maxime Cyr to share a [link](https://github.com/akash-network/console/tree/main/apps/indexer) where people can track these changes for visibility. + +**Community Feedback and Discussion (Tyler Wright, Maxime Beauchamp)** +- Tyler Wright shared feedback from a Telegram user regarding the daily USD chart on the stats page: + - The user mentioned that the chart appears "messy" in the all-time view, and the 30-day view is too short. + - The suggestion was made to add a 90-day view and improve zoom-out functionality for easier viewing. +- Maxime Beauchamp acknowledged the feedback and mentioned that an issue had been created to address these concerns. + - He suggested that updating the graph library could improve chart functionality and invited community members to contribute to this effort. + - Maxime emphasized the importance of aligning on the library choice and implementation, and encouraged community involvement. + +**Discussion on Meeting Frequency (Tyler Wright, Maxime Beauchamp)** +- Tyler Wright asked if there were any additional topics or updates that needed to be covered before concluding the meeting. +- Maxime Beauchamp brought up the possibility of changing the meeting frequency from bi-monthly to monthly. +- After a brief discussion, it was clarified that "bi-monthly" means every two months, and the current schedule would remain unchanged. +- Tyler Wright mentioned that the decision to keep the meetings every two months was based on the current level of updates and contributions, but they could revisit the frequency if needed. + +**Open Floor for Additional Topics (Tyler Wright)** +- Tyler Wright encouraged participants to bring up any final topics or updates. +- He emphasized the importance of community involvement and reminded attendees to use Telegram and Discord for ongoing discussions. +- Tyler offered to organize one-off working group sessions for those interested in contributing more actively to the indexer or other projects. + +**For Maxime Cyr:** +- Share the link to track recent changes to the indexer for visibility among the group. + +**For Maxime Beauchamp:** +- Continue working on improving the chart functionality, including adding a 90-day view and zoom-out features. +- Support and engage with the community regarding contributions to the indexer and other analytics-related projects. + +**For Tyler Wright:** +- Facilitate any one-off working group sessions as needed for community members interested in contributing more actively. +- Ensure that meeting notes and resources are shared with the community to encourage involvement. + +**For All Participants:** +- Stay engaged with the analytics Discord channel and other platforms to provide feedback and suggestions for future meetings and projects. + +# **Transcript** + +Tyler Wright: alright, welcome everybody to the analytics by monthly meeting during + +Tyler Wright: Interest group for analytics the group has historically come together initially again to help develop a open source index or solution the cloud most team had one again that solution is now open source when we discussed some updates there. So I will hand you over to Max shortly to talk about any updates in addition, we get feedback from the community if there's any questions we're sharing again a lot of the information from the index service displayed on stats.com network so you can track some information there. if anybody has anything that they want to cover during this meeting feel free to drop it in. I know there's some conversation that's been going on this again analytics Discord channel, so I will bring up some of the topics there but + +Tyler Wright: Max I just want to see if there is anything I know we don't meet that often. So I know that you've been working on some things related to the indexer. I just want to see if there's anything that was worth sharing with the group here today and we're with those that might be listening to the recording or watching recording later on. + +Maxime Cyr: Yeah, sure and just looking the recent changes we did and the tracking for the r persistent storage. So previously when we Regularly provider to track available resources in previously. We were on the tracking FML storage. So now we're tracking persistent storage as well. It's combined in the UI for now, but eventually it will be a separate graph for it. And we also reduce the vitri interval when A Time check fails on the providers. So if I provide the the is down for whatever reason. + +Maxime Cyr: we try it more than so that it can come back online sooner when it's fixed. And we also found a small bug in the indexer about how we compute resources list and spent. akts it's fixed, but we did an analysis and Found out it on the affected 0.0001% of the value. So the didn't affect the stats. in any + +Maxime Cyr: significant way + +Maxime Cyr: I think that's all the changes with the recently. since last meeting + +Tyler Wright: Thank you very much Cool. does anyone have any questions about some of the updates from maxi? + +Tyler Wright: max if you don't mind when you get a chance, if you can just drop in the attach that work organization where people can kind of track some of these changes that happen just for again visibility sick. + +Tyler Wright: The perfect thank you. There is one question that came in be a telegram and I just want to just get some on the record kind of feedback here today from this big analytics from a couple days ago. it was offered a suggestion that daily USD chart on the staff page looks a bit. + +Tyler Wright: Quote unquote Messier noisy on the all view in the 30 day view is a bit short. So it'd be nice to have maybe a 90 day view of the USD chart. + + +### 00:05:00 + +Maxime Beauchamp: Yeah, I created an issue on the console people for that matter. + +Tyler Wright: They also talked about maybe some more in zoom out functionality for the charts this for easy viewing. + +Maxime Beauchamp: But yeah, we definitely could use an updated library for displaying the graphs. + +Tyler Wright: I don't know if that's something that other people can contribute to or something that Maxes you all have thought about and… + +Maxime Beauchamp: There's a lot of them available right now… + +Tyler Wright: maybe move in another direction for a number of reasons. + +Maxime Beauchamp: where you can zoom in. + +Tyler Wright: But again,… + +Tyler Wright: I just want to pass along that feedback from a telegram user as transcribed in Discord. + +Maxime Beauchamp: And do some custom ranges. + +Maxime Beauchamp: So yeah. The issue is there. We'll get to it at some point or… + +Maxime Beauchamp: someone from the community. You want to implemented their more than welcome to do it. + +Tyler Wright: I see a hand up. + +Tyler Wright: Go ahead. + +Maxime Beauchamp: if someone wants to do it for sure the best way to approach this would be to do a short meeting with us so that we're aligned with The library choice in the implementation. + +Tyler Wright: Thank you Max, I guess from that perspective because I know being Max C are working on a number of things is that an issue that you think a Community member can tackle and… + +Maxime Beauchamp: So yeah. + +Tyler Wright: has a sense of resources to be able to tackle right now or do you think somebody might have some questions and should ask them before getting started? + +Tyler Wright: excellent + +Tyler Wright: All right. + +Tyler Wright: Thank you Max Steve. Does anyone else have any questions again? We got to update on Max C and he's dropped in chat some of the PRS that have been worked on recently much appreciate that as well as how folks can kind of track the repo and monitor and again how folks get involved if they so desire to help continue to improve indexer and some of the things around the indexer. So again, if anybody wants to get involved on is listening to this or again is getting feedback from somebody in the community. Feel free to reach out to myself Maxi or Max B and Discord because set up some time to connect with you, help you get on boarded and then, aligned on projects and then off the races. It's certainly supportive needed. Excellent. Thank you Robert. again, if anybody from the community again, there's a zeely community where there's a number of bounties and missions that are available to folks. So if anybody wants to get involved there's a working group. There's a entire daily dashboard. So feel free to get involved Is there anything else that anybody wants to discuss that hasn't been discussed on the analytics front? + +Tyler Wright: + +Tyler Wright: Max B. Mac said I just want to see if there's anything else to potentially you want to cover for this edition of the buy monthly meeting. If not don't feel applies, but it's fun to give you the platform because I know that she goes working on a number of things. Go ahead Robert. + +Tyler Wright: + +Tyler Wright: If not, Go ahead Max. + +Maxime Beauchamp: Bad nothing for me. So I wanted to make that here. + +Tyler Wright: I appreciate All if there's nothing else again, we try to have this meeting by monthly just to connect with the community if there's some Community involvement again appreciate some of the questions that have been coming in summer suggestions through telegram through Discord keep that up. And again, if you want to get more involved there'll be something in the notes be available for folks that want to contribute some more go ahead next. + +Maxime Beauchamp: I think it could be a monthly meeting for analytics. I don't know what you think about it. + +Tyler Wright: You think go back to being a monthly meeting from monthly? + +Maxime Beauchamp: Why yeah was it it was a monthly and then it got to buy monthly. + +Tyler Wright: Yeah, yeah, it was monthly for a while and I think as of six months ago we changed it to every other month because some people thought there was mostly just you and Maxie giving updates and at that time there was less updates to be had. I have no problem. If we want to get more contributions and meet more consistently to have it every month. But I really leave that up to you and Max C because you all are the greatest contributors to the indexer as of right now. + + +### 00:10:00 + +Maxime Beauchamp: By monthly is every two months my bad. + +Tyler Wright: Yeah. + +Maxime Beauchamp: I mixed it up with weekly. + +Tyler Wright: Yeah by monthly it's every two months yeah + +Maxime Beauchamp: But yeah, every two months is + +Maxime Beauchamp: okay, my bad. Yeah, it's fine like this. + +Tyler Wright: No problem. No problem. + +Tyler Wright: + +Tyler Wright: Yeah, so we'll keep this again at every other month. And again, if anybody has any comments concerns again, please get involved in this again analytics Discord Channel, we can create some sort of one-off working group sessions, especially at folks want to get involved and contributing to the indexer like we've done the past. So again, if you desire to get involved and contributing look at some of the repos and preset Maxi has dropped in as well as this again familiar familiarize yourself with the console in general. + +Robert Del Rey: Thank you. Thanks, Max and stay safe everybody. + +Maxime Cyr: That's good. So + +Tyler Wright: And then again, we'll look to connect every two months as just an update on what's going on in the analytics side and see if there's anything worth discussing it more detail live. But much appreciate everyone's time today. Thank you again Robert for dropping in the daily word for this call. Hope everyone has a great rest of the day and thank you to those listening to the recording later. Feel free to get involved when you can. Bye-bye. + + +### Meeting ended after 00:24:11 👋 + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + From 59bc1879650d75daedd6f822387ac94fda611512 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 23 Aug 2024 01:44:08 +0000 Subject: [PATCH 122/138] Create meeting notes for Sig-Client #17 (#668) * Create meeting notes for Sig-Client #17 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 017-2024-08-20.md added transcript Chore: add recording link Signed-off-by: Drinkwater * Update 017-2024-08-20.md added recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-clients/meetings/017-2024-08-20.md | 301 +++++++++++++++++++++++++ 1 file changed, 301 insertions(+) create mode 100644 sig-clients/meetings/017-2024-08-20.md diff --git a/sig-clients/meetings/017-2024-08-20.md b/sig-clients/meetings/017-2024-08-20.md new file mode 100644 index 00000000..a0d74c55 --- /dev/null +++ b/sig-clients/meetings/017-2024-08-20.md @@ -0,0 +1,301 @@ +# Akash Network - Clients Special Interest Group (SIG) - Meeting #17 + +## Agenda +- Updates on Clients Built on Akash +- Terraform and Go Client Libraries +- Updates from the Console Team +- Discussion of Console 2.0 +- Open Floor for Questions and Additional Agenda Items + +## Meeting Details +- Date: Wednesday, August 20, 2024 +- Time: 08:30 AM PT (Pacific Time) +- [Recording](https://4mgemilgnadqtihidt2lpu7ocnkirkq4voj2pabf64hw5zdlqh3a.arweave.net/4wxGIWZoBwmg6Bz0t9PuE1SIqhyrk6eAJfcPbuRrgfY) +- [Transcript](#transcript) + +## Participants +- Anil Murty +- B S +- Dominikus Brian +- Jigar Patel +- Maxime Beauchamp +- Maxime Cyr +- Rodri R +- Tyler Wright +- ⻲人小河 + +## Meeting Notes + +### Introduction +- **Tyler Wright:** + - Welcomed participants to the bi-monthly SIG Clients meeting. + - Focus of the meeting was on updates and developments related to clients being built on the Akash Network. + +### Updates on Clients +- **Tyler Wright:** + - Provided an update on Cloudmos, now rebranded as Console, which continues to be the primary deployment tool on Akash. + - Mentioned the upcoming Cosmos SDK 47 upgrade and its potential impact on both Terraform providers and Go client libraries. + - **Terraform Providers and Go Libraries:** + - Work is already planned to address compatibility and functionality with the SDK upgrade. + - Detailed discussions on these updates will be deferred to future meetings. + +### Changes in Meeting Cadence +- **Tyler Wright:** + - Announced a change in the meeting frequency from monthly to bi-monthly. + - **Reason:** The availability of updates from other sources, including the steering committee and product/engineering roadmap, reduced the need for monthly meetings. + - Emphasized the importance of the SIG Clients Discord channel as a primary communication and update platform. + - Encouraged members to share ideas for improving the user experience or adding new features to Console via Discord. + +### Console Team Updates + +- **Tyler Wright:** + - Transitioned the discussion to the Console team for updates on recent work and future plans. + +#### Updates from Maxime Beauchamp: +- **Managed Wallets on Console:** + - Significant progress has been made toward enabling managed wallets on Console. + - The feature is designed to abstract away the complexity of managing on-chain wallets, making the platform more accessible to users. + - **MVP (Minimum Viable Product):** + - Near completion, with plans to release it to production shortly. +- **Bug Fixes:** + - The team has been actively addressing bugs reported by users. + - Focus has been on improving the overall user experience, especially as the platform sees increased usage. + +#### Updates from Anil Murty: +- **Trial Wallet Implementation:** + - Focused on the implementation of managed wallets and the integration of credit card payments on Console. + - **Trial Wallet:** + - Allows users to experience Console without needing a wallet or login. + - Currently in beta testing within Overclock Labs, with plans to extend testing to a broader audience soon. + - Potential use in an upcoming hackathon in India as part of the extended testing phase. +- **Shared Packages:** + - The codebase has been reorganized to separate shared packages. + - **Impact:** + - This restructuring allows for parallel development of different components, such as the new user interface for the provider console. +- **Persistent Storage Tracking:** + - Persistent storage is now being tracked in Console's statistics, in addition to ephemeral storage. + - **Benefit:** + - Enables more accurate monitoring and reporting of storage usage across providers. +- **Exponential Backoff Algorithm Update:** + - The algorithm has been updated to improve the user experience by ensuring new providers appear online more reliably and quickly. +- **CICD Progress:** + - Significant progress has been made in enhancing the CICD (Continuous Integration/Continuous Deployment) pipeline. + - **Features:** + - Users will be able to connect their repositories (GitHub, Bitbucket, GitLab). + - Automatic building and deployment of applications. + - Triggering redeployments based on new pull requests. + +### Discussion and Feedback + +- **Tyler Wright:** + - Expressed gratitude for Anil’s updates and invited attendees to ask questions regarding the Console team’s progress. + - Highlighted the work of Jigar and Duval in integrating the Prater app into Console. + - Mentioned that more details would be discussed in the upcoming SIG Providers call. + +- **Dominikus Brian:** + - **Positive Feedback:** + - Praised the new SSH key generation feature, describing it as user-friendly and convenient. + - **Concerns:** + - **Bid Availability:** + - Reported issues with selecting providers due to configuration mismatches. + - Suggested that instead of failing bids, there should be an option to select lower configurations when the requested ones are unavailable. + - **Connection Stability:** + - Noted occasional instability with connections when using Console. + - **Suggestions:** + - Proposed implementing a system to show available bids that are close to the requested configurations. + - Suggested exploring the integration of Docker files to provide more detailed assessments of requirements for Dockerized applications. + +- **Anil Murty:** + - **Bid Availability:** + - Acknowledged the issue with filtering out some providers based on default values. + - Mentioned ongoing work to update the value from 1000 to 10,000 to include more providers, with changes currently in progress. + - **Design Choices:** + - Discussed the intention behind certain design choices aimed at simplifying the user interface for less technical users. + - Appreciated the feedback on potentially adding more detailed options and raw data views. + - **Persistent Storage and GPU Configuration:** + - Confirmed ongoing updates aimed at improving the visibility and management of persistent storage and GPU configurations. + - **CICD Pipeline Integration:** + - Reiterated the exciting developments in the CICD pipeline, including automatic Dockerization and repository integration. + +### Awesome Akash Templates + +- **Tyler Wright:** + - Encouraged contributions to the "Awesome Akash" repository. + - Mentioned that templates from this repository automatically integrate with Console. + - Invited attendees to contribute any Dockerized templates that might be valuable for others in the Akash ecosystem. + +### Client Contributions + +- **Tyler Wright:** + - Highlighted the ongoing efforts of contributors and the community in addressing smaller issues related to Console. + - **Community Pool Support:** + - Acknowledged the financial support from the community pool, which has been instrumental in funding CICD improvements. + - **Good First Issues:** + - Emphasized the availability of "good first issues" for those interested in contributing. + - Advised newcomers to start by running Console locally on their machines and exploring the available documentation. + +### Call to Action + +- **Tyler Wright:** + - Reminded attendees to stay involved by participating in discussions within the SIG Clients and Console ecosystem channels on Discord. + - Reiterated the importance of community feedback and engagement in the ongoing development of Console. + +### Feedback from Dominikus Brian + +- **Help and Guidance in Console:** + - Suggested implementing a help button or agent within Console to assist users by suggesting requirements and guiding them through various tasks. + - This feature would improve the overall user experience, especially for those unfamiliar with the platform’s intricacies. +- **Future Enhancements:** + - Expressed openness to contributing more ideas as he continues to use and test Console, particularly around making the tool more intuitive. + +### Acknowledgements and Next Steps + +- **Tyler Wright:** + - Extended thanks to George for supporting with meeting notes and to Maxime, Anil, and Dominikus for their contributions. + - Emphasized the importance of community involvement. + - Announced that more detailed discussions on Console 2.0 will take place in the SIG Providers meeting. +- **Looking Ahead:** + - The SIG Clients group will reconvene in two months, with ongoing updates provided via social media and the product and engineering roadmap. + +### Closing Remarks + +- **Tyler Wright:** + - Thanked participants for their contributions and updates. + - Encouraged staying connected between meetings via the SIG Clients Discord channel. + - Mentioned that any additional updates from other teams would be shared in the Discord channel before the next meeting. + +## Action Items + +- **Anil Murty:** + - Continue working on improving bid availability and capturing more scenarios related to bid issues. + - Review and potentially integrate Docker file assessments into the Console experience. + - Oversee the broader beta testing of the trial wallet feature and ensure readiness for the upcoming hackathon. + +- **Maxime Beauchamp:** + - Proceed with planned updates to the bid filtering system. + - Continue finalizing the MVP for managed wallets and prepare for its production release. + +- **Tyler Wright:** + - Share meeting notes and recordings with attendees. + - Prepare for the upcoming SIG Providers meeting focusing on Console 2.0. + - Coordinate with teams working on Terraform providers and Go client libraries to ensure updates are made ahead of the Cosmos SDK 47 upgrade. + +- **Console Team:** + - Explore the possibility of integrating a help agent within Console to assist users with real-time suggestions and guidance. + - Continue to engage with the community for feedback and contributions. + - Provide further updates on their work and future developments, particularly related to Console 2.0. + +- **Dominikus Brian:** + - Test different GPU and storage options and provide feedback. + +# **Transcript** + +Tyler Wright: All right, welcome everybody to Sid clients by monthly meeting. During this special interest group for clients the group here gets together to discuss anything that's going on with any clients being built on Obviously one of the first clients that was built on top of Akash was Cloud most which is now again update on Console being that again. It's the leading deploy tool for how people Deploy to + +Tyler Wright: I know there's some folks that usually join us that can't make it here that talk about terraform and also the gold client libraries. I know there's going to be a fair amount of work that goes on there as we move into the cosmos SDK 47 upgrade. So again when that test net starts some of the themes behind terraform providers as well as the go client libraries, we'll have again some additional work cut out for them in terms of making updates to those clients ahead of the network upgrade. So again, that work already been mapped out and discussed. I'm sure we'll have Some further discussion between meetings if not the next meeting. + +Tyler Wright: As a last couple of months, we've changed a Cadence where this used to be a a monthly meeting just because again, there's a number of other places including the steering committee the product and Engineering roadmap where you can get updates from the Consulting all the work that they've been doing on the client side. Again, there's a number of other teams that are building various clients on top of Akash or having the past getting them to join this meeting sometimes difficult because again, they have other responsibilities so we look for updates from anybody that's building any clients on top of Akash to again, feel free to chime in to the Sig clients Discord channel to give updates. If you're cannot make these meetings or if you have ideas for things that you want to add to console or things that you want to add to the user experience and maybe a form of another client again, always + +Tyler Wright: Looking for folks that are building the cost to join these conversations get involved talk about problems that they're facing Etc. + +Tyler Wright: you can also track many of the past meetings in the community repo. There's a sick clients folder where you can track again some of the stuff going on. I know there's been a big plan that was discussed at the last meeting about everything happening with console 2.0. So again, we'll just get update on some of the work on console and then if anybody has any questions or any agenda items that they want to talk about feel free to drop those in the chat and then we can talk about those here today. + +Tyler Wright: But I do want to hand it over to the console team again. We take a part of this agenda to get updates on all the work that the console team is doing across a number of different initiatives. We've talked previously about some of the work related to the indexer during this again analytics by monthly meeting. So we don't have to necessary talk about that here, but I want to hand it over to their Consulting. Maybe Max Anil to talk a little bit about some of the advancements over the last couple of months and look ahead of maybe what's to come? + +Maxime Beauchamp: Sure Anil you want to go? I can go. + +Anil Murty: Sure, or you can go first. + +Maxime Beauchamp: But yeah, I will wait in the past month and there's been a lot of effort and progress towards enabling managed I will on console. so users will soon be able to make complete abstraction the Wallets on chain. So everything will be so a lot smoother for users. So that is almost. The MVP is done, and we're almost there to release it on production. + +Maxime Beauchamp: We've been working in hard as well on fixing bugs that customers are facing right now. There's an more usage more bugs that we find and we work hard on fixing these and just improving in the overall experience for her console users. + + +### 00:05:00 + +Anil Murty: So I know I can jump in a little bit. But yeah as Max said the big Focus for the core team has been to implement the first phase of managed wallets Plus Credit Card base payments in console. The very first phase of that is basically implementing what's called a trial wallet. And so the idea here, is that a user that comes into console? Should not have to have a wallet. She not even have to log in and can just try console without having to literally do any sort of sign up or login. and then once they try it and maybe do one or two deployments then they can choose to obtain to either a custodial wallet solution where we manage your wallet for them and they play using credit cards or a self-cously you want it where the experiences exactly the way it is right now in console. + +Anil Murty: So the very first phase of that is the trial wallet portion and that portion is currently in beta test within the ocl codeine with an overclock lab score team. So we're going to spend a few days later testing it outside of the engineering team within the broader or Cloud lab scheme here. And I'm hopeful that in the next few days, we'll be able to open up the beta for insiders as well as for. Potentially a upcoming hackathon that's going to be happening in India. So if you don't find any major issues with the trial experience this week, we're hoping we can actually use this for the hackathon. What's happening in India? So that's the big update. Other than that, if you look at the project board that Tyler shared some of the other big updates you'll see that Max talked about + +Anil Murty: which are in the bucket of enhancements as well as bug fixes. + +Anil Murty: some of the things we have done is we have carved out all the shared packages into a separate section inside the code base. And the reason we have done this is so that we can build things more in parallel across the team particularly as the pretor team is starting to work on the fronting new contained user interface for provider console, which will be basically a portion of console that is going to sit inside consort network, but it's going to be basically a new front-end for spinning up providers. So all that work can happen in parallel. Now that the shared packages are shared out and we can reuse components across the deployment console as well as the provider console. So that's issue number 230 on the list and then one of the other things that was added, I think since the last time we met here was persist in storage of being tracked now in the stats app as well as in So when you went to Stats or to console providers + +Anil Murty: stories that you'd see there was only ephemeral storage and in the last few months, you've added a bunch of providers with a lot of persistent storage and it was important for us to start tracking all that as well. So even though it's not broken up into its own thing into its own donut chart the storage overall storage now reflects both FML storage as well as persistent storage. So if you notice a little spike in the stories, that's what that is. and then the third significant thing worth calling out is we have also updated What's called the exponential back of algorithm for a new providers that are coming on to the network. So what this does is basically + +Anil Murty: improves the user experience of how fast a provider shows up on the network while it being set up and also if for some reason a provider failed to check before the exponential back of algorithm would back off to a day or more and that would sometimes cause the provider to show up offline even though it's technically online. And so that was a pretty big fix that Maxi made and that's one of the board right there. There's other things that are happening on the cd side. I don't see the human HQ team on here, but there's a bunch of progress that's happening on implementing. Basically what I call a versatile style experience within console and push and the human HQ team and as we sync up pretty regularly on those between these meetings and the pretty close to having a solution that'll work really beautifully within console where the user will be able to come in connect to a GitHub or big Market or lab repository be able to pull in their + +Anil Murty: application code and then have the backend basically the software build it for them deployed onto console and just give them a main point so that way they don't have to authorize their application. They don't have to write an sdl none of that. And then also basically Trigger for being able to redeploy the application every time there's a new pull request into the Repository. So that exciting stuff is coming as well. And in the context of that they're also going to be looking at some testing out some logging improvements of sending console logs to a third party logging service and then cleaning up the logs and thinking in the back into console. So I'm hopeful that those changes will get more into console before the next time we come here if not much sooner than that. So I think the crcd work combined with the trial wallets and the custodial payment solution is going to be a huge driver of option on Akash in the coming months. + + +### 00:10:00 + +Tyler Wright: You Max Ben. Thank you Anil for those updates. Does anyone have any questions on all the work that the client team has been doing in terms of console and again bringing members of the community to also help? + +Tyler Wright: Cool as Anil mentioned as well there with all the work that jigar and Duval have been doing on bringing the Prater app into console, but we'll talk a little bit about that a little more detail there in the state providers call happening tomorrow. But again just another shout out to all the work that they're doing to unify the console experience. Go ahead dummy. + +Dominikus Brian: Hi everyone. Thanks for the update guys. It's very great. I'm in this console is becoming more and more. I mean, I have just tried several of one concern with this plane Linux with SSH so I tried it several other days, I mean Using trying to SSS there. I love this, generate key function. that's a perfect thing and then everything is just there. You can download it. Then I can just copy the public key and stuff. That's as easy as it gets. I mean, you don't even need to generate it yourself and that's nice. I love it but there is some issue with choosing this providers. So most of the times depending on the configuration I asked for the building is not always available. + +Dominikus Brian: And then I need to sort of manually downgrade instead of getting an options to if say I'm not sure which one is not affordable. Maybe I'm asking too much of memory if it's asking too much of something. so the GPU is already pretty General I'm asking only for NVIDIA and then I'm not sure whether it's the storage too big and other things. I need to just keep trying several times. I think this is a things that can be improve. So either doesn't show a bidding for that. I will be shown some beading for lower, + +Dominikus Brian: Great for instance. I asked for 300. There is an options like 300 is not available. How about 200? And in this bidding is also there you don't need to show everything but I mean the closest one to that will be a nice thing because sometimes it's a bit irritating to close all the deployments bidding. And then I go again trying to with lower quality one. I mean that's a thing. I mean that maybe can help accelerate where people feel it's like failing other it's just a little bit of requirements. So yeah, that's one thing and another thing with this connections when connecting to that sometimes it's not stable. I'm not sure why + + +### 00:15:00 + +Anil Murty: the nice words on the SSH option or the VM option basically, but yeah, we have heard very similar things from a lot of other users in customers as well for the longest time people would struggle with setting up their SSH from their own terminal and giving them this option and then also having the references deal in Akash is going a long way these days in terms of getting those customers onboarded. So we've heard very similar things where people are This is very much like the experience where we get to see in front if not, ec2 itself. So that's great. I want to address the two things that you mentioned or the I think the first thing you mentioned was something around. Not being able to get bids and not being able to sometimes adjust your parameters. So I think + +Anil Murty: there's a couple of things there and I want to make sure I capture your feedback. So one is in two places in the rent GPU page as well as in the page. What we were doing was we were defaulting the ukt value to 1000 and that filters off some of the providers that are more expensive some of the G2 providers are more expensive and so as we speak Max B's actually going to make this change. In fact here request open right now for updating all the awesome Akash SDS as well. And that will basically up this value from 1000 to 10,000. So it is an exit and so you should be getting pretty much every provider covered with that. So no provider should be getting filtered out. So that's one the second is I know that in the + +Anil Murty: as well as in the rim GPU, I'm just gonna check this again as I do this, but in both of these options, we actually don't show the noise here. That's just a design time choice that we made. we have to go with some more thing. We wanted to keep it as easy as possible with the assumption that these users are relatively less technical compared to the other users or something like that. So we hit the raw. I see from the ram GPU page as well as from the VM template, but if you think that that is something that we should consider adding that is something we can certainly look adding into that as well. It's something that we have another templates. So that's number two. There was another question that you had that I think I've kind of lost track of but just want to pause their see if you have any feedback. + +Dominikus Brian: Yeah, that's great. I mean I tried that video akt it doesn't help at the time. Maybe the other is busy. But I haven't tried much with other options with the friend GPA GPU directly without the get used to the STL. But yeah, I'll check and try the other ones and see whether it can give me more options. I'll write it back when I've tried more of them. + +Anil Murty: Yeah, that'd be great Both of them have all the options for adjusting everything. The only thing they don't have is the actual rise deal. so you should be able to change everything. It's like the GPU weapon will storage all of that but + +Dominikus Brian: Yeah, that's going to be very nice functions. Yes. + +Dominikus Brian: Sounds great. + +Tyler Wright: Perfect. Anything else go ahead. + +Dominikus Brian: And maybe it can go up together with the docker eyes. I mean you guys mentioned that in the future soon enough, we'll have this, Auto docorization from GitHub and everything. so there is the same functions that makes just describe what actually helps, giving users assessments of What's the requirement for this Dockers as the storage wise and things like that? So it will be nice if it's combined together. I guess that's all from me. Thank you. + + +### 00:20:00 + +Tyler Wright: Academic go ahead and deal. + +Anil Murty: Yeah, so on that point and I had forgotten what the third question was. Thanks for reminding Max B. So on the topic of how do we increase the likelihoods of bits being received? I actually created an issue to basically collect all the possible scenarios where that problem can happen. So if you have any other Feedback or other situations where you think this could happen or other ways of handling it feel free to comment on that issue as well. But I try to capture all the possible scenarios in + +Tyler Wright: Queen anything else on console and he wants anything anybody wants to discuss. Pardon me? + +Tyler Wright: I know it's been much discussion about awesome Akash as well. So again, please feel free to look at awesome occasion of the templates from Austin makash automatically go into console as well. So again, feel free to contribute to the awesome Akash repo if you see anything that you think might be great to dakarize and again put an awesome Akash for others in the Akash ecosystem again, feel free to contribute there as well. + +Tyler Wright: Are there any other discussion points that anyone wants to talk about related to clients on Akash? + +Tyler Wright: make sure that the notes are made available. Again. This is a monthly meeting much appreciate the updates from Max B from Anil the commentary from Domi all that is very thankful for all the work that the client team has been doing on the Shout out to whom who was also been supporting with some efforts on the CIA cicd side after getting some money from the community pool to support console. They're also been some contributors that have been getting involved in tackling some small issues related to console. So again, as more of those smaller issues get started or are made available, we'll have the core engineering team continue to work on a number of the big efforts continue to + +Tyler Wright: time to connect with the community talk about updates talk about all the work that they're doing get more people involved and again, there will be continued to be good first issues. One thing that we always ask if anybody wants to get involved in contributing to console. One of the first things to do is again, Look in the console repo and download our get console locally on your machine. That's a great first touch point to look at the again documentation and be able to run console locally. And then again, once that's done feel free to reach out to myself and Sid clients Channel or look in the issues inside the console repo and see if there's any good first issues for Community contribution. Go ahead and kneel. + +Tyler Wright: Sorry, excellent. Thank you very much Anil for sharing that and putting that together. Great again, if there's nothing else then we can certainly wrap up if there's any other notes or updates from any other teams. I'll make sure that those get added inside the stick client Discord channel in between meetings. Again, if anybody has any questions or conversation or any ideas, feel free to continue to drop those inside of the Sig clients Channel again, if it's specific to the console, there's an ecosystem console Channel as well where you can talk about any active issues again, we talk about some of that stuff during the six support. But again, there's all the issues that you can kind of track on the console side that's been dropped in chat here and yeah, I'm sure there will be a lot more to go ahead dummy. + + +### 00:25:00 + +Anil Murty: and so it would fit with AC clients even though You may be crunching data from the network and stuff like that to figure out which is a provider. + +Dominikus Brian: I Thank you for it. But yeah, because I think that's a great thing when you can have so in your say consoles a kind of help. Button, and then this agent basically, assists You actually need to do this or do that or things like that? I mean suggest you a little bit on requirements and stuff. But you need to train a lot of things maybe in the future if I have something on that are updated here. Thank you. Okay, that's it I guess. + +Tyler Wright: Mason excellent again, I'll make the notes in the recording available on very shortly again. Shout out to Gorge for all of the support with some of the notes again much appreciated the update from Max B from Anil some of the questions and comments from Domi great conversation. We'll talk a little bit more around the provider side of console during the sick providers a discussion where jigar and Devol will talk a little bit more about all the work that they've been doing relates to council 2.0. So look out for that sick providers meeting happening tomorrow. + +Tyler Wright: But yeah again much appreciated everyone's time today will reconvene in two months. But in the meantime, we have Sid clients, we have the product and Engineering roadmap that gets updated fairly frequently and look out for a number of updates in various channels on social media related to all the work that again the core team is doing as well as human HQ and many other teams that are working on console and other clients but much appreciate everyone again. Hope everyone has a great rest of the day. Thank you very much. + +Jigar Patel: Thanks. + +Maxime Beauchamp: Thanks, everyone. + +Anil Murty: Thanks, everyone. + + +### Meeting ended after 00:42:00 👋 From e36445154a570d5f6acfdba904e41c3ccc331fd8 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 26 Aug 2024 08:45:29 +0000 Subject: [PATCH 123/138] update notes with additional info (#669) Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> --- sig-chain/meetings/019-2024-08-13.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/sig-chain/meetings/019-2024-08-13.md b/sig-chain/meetings/019-2024-08-13.md index db870f4c..2470cad6 100644 --- a/sig-chain/meetings/019-2024-08-13.md +++ b/sig-chain/meetings/019-2024-08-13.md @@ -46,7 +46,7 @@ - **Zealy Mission Announcement (Robert Del Rey):** - Robert wished the team good luck with the network upgrade efforts. - Introduced the secret word for the Zealy mission related to the Sig Chain working group call. - - Secret word: **"November"** spelled out as N (November), O (Oscar), V (Victor), E (Echo), M (Mike), B (Bravo), E (Echo), R (Romeo). + - Secret word: **"Node"** spelled out as N (November), O (Oscar), D(Delta), E (Echo) - Participants can use the secret word in the Zealy mission to earn additional AKT points while engaging in Akash Community initiatives. - **Closing Remarks (Tyler Wright):** @@ -57,11 +57,11 @@ - Announcements will be shared over the next few days into the following week as preparations for the testnet advance. - Tyler thanked everyone for their time and participation, indicating the meeting was adjourned. ## **Action Items** -1. **Artur Troian:** Continue preparing testnet and test cases for SDK 47 upgrade. -2. **Tyler Wright:** Reach out to community members and validators interested in participating in the testnet. -3. **Core Engineering Team:** Finalize the testnet requirements and ensure readiness for the upgrade by the next meeting. -4. **All Participants:** Stay engaged with the community and prepare for the upcoming network upgrade; watch for announcements on specific requirements. -5. **Tyler Wright:** Schedule additional community calls as needed leading up to the network upgrade. +- **Artur Troian:** Continue preparing testnet and test cases for SDK 47 upgrade. +- **Tyler Wright:** Reach out to community members and validators interested in participating in the testnet. +- **Core Engineering Team:** Finalize the testnet requirements and ensure readiness for the upgrade by the next meeting. +- **All Participants:** Stay engaged with the community and prepare for the upcoming network upgrade; watch for announcements on specific requirements. +- **Tyler Wright:** Schedule additional community calls as needed leading up to the network upgrade. # **Transcript** From 74f870fd43a3b2cef49d736efd9bc194a9c02c8b Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 27 Aug 2024 08:26:24 +0000 Subject: [PATCH 124/138] Create meeting notes for Sig-Support #36 (#671) * Create meeting notes for Sig-Support #36 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 036-2024-08-21.md added transcript Chore: Add recording link Signed-off-by: Drinkwater * Update 036-2024-08-21.md added recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-support/meetings/036-2024-08-21.md | 318 +++++++++++++++++++++++++ 1 file changed, 318 insertions(+) create mode 100644 sig-support/meetings/036-2024-08-21.md diff --git a/sig-support/meetings/036-2024-08-21.md b/sig-support/meetings/036-2024-08-21.md new file mode 100644 index 00000000..307142ba --- /dev/null +++ b/sig-support/meetings/036-2024-08-21.md @@ -0,0 +1,318 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #36 + +## Agenda + +- Review issues awaiting triage in the support repo +- Discuss any open issues or support-related topics +- Update on console-related issues +- Community support and Discord updates +- Any other support-related items + +## Meeting Details + +- Date: August 21, 2024 +- Time: 07:00 GMT-7 +- [Recording](https://wrx26ds6t7sofpahkzy5iphq7eqtfu3jln6xf5idxmrr2url4m5q.arweave.net/tG-vDl6f5OK8B1Zx1Dzw-SEy02lbfXL1A7sjHVIr4zs) +- [Transcript](#transcript) + +## Participants + +- Tyler Wright +- Scott Carruthers +- Andrey Arapov +- Maxime Beauchamp +- Rodri R +- Zeke E +- Other attendees (not explicitly mentioned in discussion) + +## Meeting Notes + +### Review of Issues Awaiting Triage + +- Scott Carruthers led the review of issues awaiting triage in the support repo + +- Packet forwarding issue: + - Opened by Tyler Wright + - Awaiting Cosmos SDK 47 upgrade + - Classified as P2 priority + +- Lack of visibility for deployers on exit codes of failed deployments: + - Opened by Andrey Arapov + - Assigned to provider repository + - Classified as P2 priority + - Considered a good feature for users to see reasons for deployment exits + +- GPU device plugin issues with inventory operator: + - Opened by Andrey Arapov + - Assigned to provider repository + - Issue occurs when NVIDIA GPU device plugin marks devices as unhealthy + - Mainly observed on Oblivious H100 PCIe provider + - May be related to virtualized environments + - Recovery methods discussed: bouncing NVIDIA device plugin, rebooting node + +### Console-related Issues + +- Maxime Beauchamp brought up issue #227 regarding exposing manifests via API: + - Proposal to add an endpoint to fetch manifests + - Would solve issues with local storage and device changes + - Potential to add more metadata to manifests (e.g., deployment name) + - Discussion on progress of storing manifests on-chain (still in idea phase) + +### Community Support and Discord Updates + +- Increase in Discord scammer activity: + - Rodri R noted an increase in scammers engaging in channels and DMing users + - Tyler Wright acknowledged the issue and mentioned it would be discussed further in Insider office hours + +- General increase in Discord activity: + - More people joining provider and deployment channels + - Possibly due to recent events or increased awareness + +### Snapshot Service Update + +- Zeke E provided an update on the new snapshot service: + - Fully in production at snapshots.akash.network + - Pull request submitted for website documentation + - Requested feedback from users + - Will provide snapshots for upcoming Cosmos SDK 47 testnet + +### Cosmos SDK 47 Testnet Update + +- Tyler Wright provided an update on the Cosmos SDK 47 testnet: + - Currently on hold due to focus on provider-related issues and active workload concerns + - Code is mostly complete with some initial internal testing done + - Plan to create a Discord channel for testnet testing + - Looking for volunteers with extra infrastructure for testnet participation + +### Additional Notes + +- Scott Carruthers highlighted the importance of the new hourly snapshot service for providers, noting it will significantly reduce sync times +- Andrey Arapov made a recent announcement in Provider channels about updating to Provider Services version 0.6.4 + +## Action Items +- Tyler Wright to create a Discord channel for Cosmos SDK 47 testnet testing. +- Tyler Wright to follow up with the website team on merging the snapshot service URL. +- Core engineering team to continue work on provider-related issues and active workload concerns. +- Community members to test and provide feedback on the new snapshot service. +- Interested parties to look out for updates on Cosmos SDK 47 testnet testing. +- Discuss Discord scammer activity further in Insider office hours. + +# **Transcript** + +Tyler Wright: Alright, welcome everybody to Sig support. This is now a monthly meeting. August 21st 2024 During the special interest group for support the group goes over a number of things related to the core repos and oftentimes a console repo really the goal of the support is to have members of the Court engineering team go over any issues that are awaiting triage in The support repo is we're all issues related to the core code base for our costs the blockchain ETC live. So again members of the core engineering team + +Tyler Wright: go over any issues of waiting triage people on the call can talk about any open issues and again ask any questions about open issues if they want to get involved in helping to solve some of the again, this is a place to ask questions get involved talk about your skill set Etc oftentimes again, we cover issues related to console but I know some members that team may not be here again, if anybody has any issues related to the Akash console, there's a console repo as well as a Discord Channel. I know that the team behind console does a great job of staying up to date and staying very active in that repo. + +Tyler Wright: After we go over any issues awaiting triage, I usually see if there's anybody from the Akash insiders vanguards or anybody in the general community that maybe has some themes related to support that they see a Discord telegram or other facing channels. And then if anybody has any other comments questions concerns related to issues in the core code base or console again, feel free to drop those inside the chat and we can make sure that they get discussed. + +Tyler Wright: Without further Ado. I'll hand it over to Scott who will lead us through issues related to again the support repo and any issues we're waiting To Scott take it away. + +Scott Carruthers: All right. Thanks I share my screen. + +Scott Carruthers: Okay, so everyone able to see my screen in the open issues? so prior to the call,… + +Tyler Wright: Yes. + +Scott Carruthers: I was reviewing open issues specifically those awaiting triage, so I currently just have the Issues with that filter awaiting tree Ash pulled up. So as we can see we have three issues to review. So first one Tyler the packet forwarding I know that this is a issues that you opened. This is a waiting day Cosmos SDK. 47 upgrade before we can continue. Do you want me to just leave this in awaiting treehouse for the moment or do you want me to take it out of waiting triage and Do further assignment? + +Scott Carruthers: Do you want me just leave it as a yummy classified as a P2 for now? Okay. + +Scott Carruthers: Okay, so we have that one checked off and either and again, I reviewed these issues and it's already familiar with these but reviewed. These two issues prior to the call. both of these waiting triage. Once that are remaining our both opened by when a record team members Andy who may want to just speak further. So we don't have to Deep dive into them now, but if you have any comment I'll take so first of all, they lack of visibility for a deployer on the Akash Network to get the exit code of a failed appointment. So I think that's something that we've discussed recently and obviously would be + +Scott Carruthers: a great knowledge point to add to the network. So if a pod access because of out of memory or something of that nature, they deployer can get some feedback. So We're with that. Prelude anything for that you want to I'll take this out of a waiting triage and assign it into the provider repository. I'm doing that. Do you have any further comments or anything further on this that you want to discuss? + + +### 00:05:00 + +Andrey Arapov: No, it's good. Go ahead. Thank you. + +Scott Carruthers: Okay. Sure. + +Scott Carruthers: What would you prefer the classification on this a P2 P1? + +Andrey Arapov: It's definitely like Peter or something lower just like extra functionality for the users to see the reason the deployments are exiting with just kind of Good feature to her. So I'll be doing good. + +Scott Carruthers: Yeah. Yeah,… + +Andrey Arapov: Thank you. + +Scott Carruthers: absolutely. Okay, I'm gonna assign both our turn myself to this. I've classified as a P2 and then they provide a repository. + +Scott Carruthers: So now going back to open issues and essentially with the top so I don't even need to filter so again, so this is a matter that when they + +Scott Carruthers: the provider has Nvidia and the DP device plug-in issues on the inventory operator is not picking up on the fact that there are issues with that plug-in. So again, I'll assign this to the provider repository and as I'm going through the labeling assignment anything further you want to discuss on this issue. + +Andrey Arapov: My little shortly. It's basically when you have some issues with GPU and that module automatically marks the device for GPU devices are unhealthy. This event is quite rare so far. We have only served it on the oblivious h100 PSE provider. They're working on it to fix it and likely the issues related to the fact that provider is running in Puma virtualized environment and passing through the PSE h100 device through it as someone reported the same having the same. + +Andrey Arapov: Let it has seen the same issues on the Media Forum they started so in this installs we often see this kind of things are happening and that's how I actually noticed this issues at all. I just was watching no other was reporting HTTP so available and after querying it again after the GPS market on health by this model and assuming the price is still reported into Chris are available. But in fact it was like We'll say one GP was available and… + +Scott Carruthers: Okay, sure and decide I noticed in the issues. + +Andrey Arapov: wasn't picking it up. So yeah, because + +Scott Carruthers: You said that rarely you can recover from this occurrence by bouncing the mvdp device plugin. if that doesn't work? how have you been able to recover from this situation? + +Andrey Arapov: I + +Scott Carruthers: Otherwise by bouncing the inventory operator? + +Andrey Arapov: am it's like let me think. So basically the nvp device plugging is the one that is responsible for marking at gpus and healthy or detecting them at all. And when it detects the GPU you can actually keep cattle common describe notes or describe notes specific note if you're wondering and then you can see the amount of resources that com/gpu resource and we can see the amount of them and basically what an Android operator does he means I think information from there actually so kind of needs to, keep updating this information either from an old or from this. + +Andrey Arapov: Plugin directly, but in order to recover from it. First of all, we need to detecting this issue. So normally you would query the provider status on point and you would see it https are available, but the only way how to objective. Basically it's a chain of actions, which is someone is deploying the EGU workload on that particular note and then you notice You cannot access your department. We don't see your deployment is ever becoming ready. And when you are asking provider to check the provider side and Humanities point a few you want is that your board is basically stuck for our pending and what's happening in conversation that it cannot spawn because it needs more GPS but reports less GPS available as you can very good describe mode. + +Andrey Arapov: But then you see providers to reports all of them already and that's where this synchronization is at and to recover from it. It depends how bad presentation is. So They're two ways to recover it only Simply bouncing this invisibility model and hope that it actually doesn't Mark the GPU. That is unhealthy again. Sometimes it works. Sometimes it's not it depends how bad situation is and if it still marks the gpus unhealthy, you would have to reboot the note entirely simply on a simply unloading and video and reloading and video model. It's possible to do I want to talk for it if you're wondering but even that doesn't help in India semi reset command to gpus doesn't help low level so + + +### 00:10:00 + +Andrey Arapov: Yeah, and it's another factor that says in favor of the tissue is related to the visualization. So something has to do with the qmi or the way how the egpu has been passed through x-ray. + +Scott Carruthers: Yeah. + +Andrey Arapov: It's a good point here discussing it right now something to highlight. Yeah. and once you done this and the note is back up again, you can basically see old reviews are present normally which again highlights that it's issue likely is the firmware or the way how it's being passed through the key in my because physically is always back after the book. And there is another thing issues opened for this kind of issue for the inventory operator. I think with missing. + +Andrey Arapov: Was it? + +Andrey Arapov: I think it was 240. I think that a couple of issues similar to this but they're different so you need to Detective. In life mode and the other issues is that when you finish the inorder book that nvdp and with the device plugging in it takes some time to initialize about, three to five minutes and an entry operator starts earlier. And where is the information earlier and sometimes you would see the provider is supporting zero to use are available. in fact, if you roll out to start inventory operator deployment, it will correctly detect it. So I think this kind of precious are connected so it just needs to I believe frequently all the information from the note. + +Scott Carruthers: Yeah, I sense and good to go through that inside personally. Haven't hit the fdp device in issues. good to hear your series of events. So if restarting the mvdp vice plugin doesn't work reboot in the note preview booting the node entirely as prevent to cure the issues. So yeah good to walk through that and I guess there's any providers that on the call or listen to the recording that haven't encountered that yet. So yeah. + +Scott Carruthers: Yeah. + +Scott Carruthers: Yeah, okay. Yeah, thanks for that review and I'll make sense. So that brings us through the issues that were previously awaiting triage. Does anyone have Questions about any of those issues that you want to Deep dive in a little further or possibly any questions about issues that we haven't covered so far. + +Scott Carruthers: Okay, if there's nothing else I'll hand it back to Utah. + +Tyler Wright: Excellent. Thank you very much Scott again. I just want to see if there's anything else from the support repo that anybody wants to discuss. + +Tyler Wright: I know there's a representative from the consult team, one of the original developers of clouds, which is our console. So always want to shout out Max. Does anyone have any issues related to the console repo that they want to discuss are any issues and console that they want to discuss at this time? Of your hand up. Go ahead rodri. + + +### 00:15:00 + +Tyler Wright: Yeah, I've noticed this too. We've talked to some insiders and we try to tighten up on some of the mod words. But to be honest some of this behavior. I'm not really sure what we're gonna do. I think we'll talk about a little bit more about it during The Insider office hours, again, they cost insiders is a special group of ambassadors that works on volunteer basis to provide support in Discord a number of other channels both non-technical support. So again, we'll take some time during the entire office hours to discuss this a little bit more and see if there's anybody that has any specific strategies. I know that Max dropped an issue prior to that. Is there any other? + +Tyler Wright: Items on the support side that I've seen really a lot more people in providers channel is also and also unemployment's channel. So I think again whether they're coming off of events or just general awareness there seems to be a fair amount more people in Discord. I've heard from a I've heard from some Partners recently as well that it getting involved in Discord. There's + +Maxime Beauchamp: Thanks Yeah, I talked about this issues with Arthur and I think I just want to bring it up to Scott as well out of you wherever it but yeah, It's probably not that big of a change to implement, but yes to expose the manifests. to the API so the way that we like query the logs are the events with the certificate. We would add an extra point to get the Manifest. So that way instead of storing it in the local storage like we do in console. + +Maxime Beauchamp: And if you change device or browser, it doesn't follow you and connect your wallet. if we had an endpoint to this we would just fetch it and then that problem would be solved and also. Arthur was talking about + +Maxime Beauchamp: Art, there is aware. Just wanted to put a little bit more light on the issues. + + +### 00:20:00 + +Scott Carruthers: Yeah, thanks for reviewing that Max and completely makes sense. as you were described in that I now have a little bit for their Insight. So we've talked at different points about story and manifests on chain. So someone could to ease the friction on deployment to a new provider or obviously there could be automation built around that as well. But the current focus of + +Scott Carruthers: Having a manifestive API so that's the part that wasn't following initially is why that helps if life for automations schemes and past conversations where we're going to have the manifests possibly on chain or stored elsewhere so that in automation you could redeploy to another provider easily. So I wasn't sure how exposing the manifests who are provider API would solve that issue issues that we're currently trying to solve is instead of storing it The sdl and local storage. So if someone brings up console on another device console want to have access to it that use case makes complete sense. I'm glad you went over that and yeah, I'm a little clearer now and as you said, I know the Archer is aware of this issues. So I think we're Contemplating how we're going to move forward. + +Maxime Beauchamp: Cool. Thanks Scott. + +Tyler Wright: It looks like even as quick as recently as yesterday. There's been some reference of this issue on the provider side. So thank you again Max for bringing this up and talking about a little bit more. Is there any other action that you want done or I guess I've looked at the issue and you've mentioned a number of the items at the top of it. But it is there any other specific functionality that maybe is not an issues 227 that you want to make sure it's very clear for the core engineering team. I know you already talked to Archer and obviously just recently brought it back up to Scott. But is there anything that can be added to that issue just to make sure that everything you're looking to be solved is sold or is it pretty much up to date? + +Maxime Beauchamp: They just pretty much up today. There's an image to it. Unless some Scott you think. + +Tyler Wright: . + +Maxime Beauchamp: It's not clear enough, but I think it's pretty straightforward. Yeah. + +Scott Carruthers: Yeah, no. Yeah, especially with the further conversation. I'm definitely Claire so I think we're good. + +Maxime Beauchamp: Is there any progress today and storing the Manifest unchain, or is it still just an idea? + +Maxime Beauchamp: Yeah, no worries. Just wanted to ask. + +Tyler Wright: I thought two hands up. I don't know what order. + +Tyler Wright: Perfect. + + +### 00:25:00 + +Tyler Wright: Excellent. Thank you Roger. + +Rodri R: The get with my turn now. + +Tyler Wright: Go ahead. + +Rodri R: Look Andrew said and Scott and Maxim makes it great idea to store the Manifest unchain. Not sure if this has anything to do with this, but just two weeks ago. I learned I deployed for my new address and console didn't ask me to Create a new manifest. Is this something that was added recently because before in Cloud moves, I remember we had to sign the first grade. I mean, I would have to create a manifest and they would deploy Kepler or Wale whatever and I would have to pay for that and now I just deployed without creating. I'm a manifest. + +Rodri R: Asking because Melton the others know that it's not necessary anymore. Am I correct? + +Maxime Beauchamp: Wait a minute. I'm not sure what exactly you're referring to and you're saying there's no need for a manifest. + +Rodri R: Yeah, like I said, I recently created a new wallet two weeks ago. I deployed from console and it did not ask me to sign up any manifest. It was a new wallet. + +Rodri R: So I was kind of surprised because I thought it was a new feature. And I didn't have to sign manifest before on Club moves. + +Maxime Beauchamp: Like the SEO you mean? + +Rodri R: No if you remember in Cloud mode Before even deploying you had to pay I don't know 0.0001 akt to create a manifest. And now he created it automatically for me in console. + +Maxime Beauchamp: I mean the certificate. + +Rodri R: Okay, it's different. Yeah certificate. Yeah, my bad. + +Rodri R: Okay, my Yeah is the certificate so this is different. + +Tyler Wright: awesome All right, again, we've talked about any issues that are awaiting triage and we went over some of those issues from the support repo. + +Tyler Wright: We've talked a little bit about inside and saw if there's any questions for anything console related Max brought up an issue that will have an effect for client side. Many users issues issues number 227. We're just discussing that we talked to members of the Insiders about just against support in Discord and some things that we've been noticing over the last couple of weeks. I want to see if there's anything else anybody wants to discuss related to support again. This used to be a weekly meeting where we change it to monthly just because there's again many things being worked on we have the product and Engineering roadmap. And then again, if anybody has any questions between these monthly meetings we can discuss them in the Sig support Channel or people can leave comments under a specific issue and again that can get some traction. You see a hand Go ahead Zeke. + +Zeke E: Yeah, I got two things first thing. I just wanted to give an update on the snapshot service. So it's fully in production. Now, you can access it at snapshots.cost.network. I did a pull request in the GitHub repo for the website for the documentation such as waiting to get approved. So that way we can start using that more widely. If you have any questions or feedback if you use it, I'd appreciate it as we continue to scale it up. And then just is there any update regarding the cosmos sdk47 testnet? + + +### 00:30:00 + +Tyler Wright: As of right now there is no update the hope is that over the next couple of days to a week. We will get that started. I know we've said that previously but there's just been a couple of other issues. I think you could see some of the commits that have been going on from the core engineering team, but there's some other provider related issues and some other issues related to active workloads that the core engineering team has been focusing on over the last two weeks and that has put next steps in terms of the cosmos SDK 47 upgrade on hold temporarily again, we're in a point where mostly we're code complete. There's been some initial testing done internally that's like automated testing and to Zeke's point. We're starting to gather some folks together that are technical that can help us. + +Tyler Wright: Test out the cosmos SDK 47 migration Scott and I were actually talking about a plan yesterday. So again, in terms of next steps, I'll start to put together a group. I know there's some people on this call and some people in the community that showed interest and initial testing. I'll create a specific Discord channel for that testing and then again over the next couple of days. we'll share some instructions and next steps. There are some validators and some providers that again if they had some extra infrastructure, we would love to leverage for the testnet. But again, I've reached out to folks there, but please look out for updates in various channels. And again, I appreciate everyone understanding and being patient as again our core team of + +Tyler Wright: Three and a half Engineers on the core engineering side has been working relentlessly on a number of different fronts. So I've been trying to limit Scott and Archer and the rest of teams sleep schedule,… + +Zeke E: And then just one other thing I will. + +Tyler Wright: but apparently they need to sleep to live. So we're working as quickly as we can. + +Zeke E: I will be perfect. I will be providing snapshots for the testnet once that gets started up. + +Tyler Wright: So I go ahead Zeke. + +Tyler Wright: Yeah, that's gonna be instrumental and I think that would be the snapshot that gets used for those that are helping to test things and participate in that testnet. So thank you Zeke's for all the work that you've been doing over the last couple of months to provide it again additional snapshot service. That stacked out by the core engineering team. Obviously, we have the poker Chief snapshot service and number of other avenues but having a snapshot service control by kind of overclock labs in the core engineering team that has some of more + +Tyler Wright: more often Cadence around snapshots is going to be very helpful, especially when core engineers and other members of the community are setting things up testing things Etc. So appreciate all the work you've been doing there Zeke. + +Tyler Wright: I'll follow up. I've already followed up with the website team on just the URL making sure that gets merged. But again, thank you for all the work there. + +Tyler Wright: Any other support related items? + +Scott Carruthers: but I was just gonna agree with Zeke the fact that we have snapshots available every hour. + +Tyler Wright: Go ahead Scott. + +Scott Carruthers: So I'm sure there's probably a number of people on the call that can understand the frustration or just challenges with you trying to build a New provider especially with the scripting that I created. I think a majority of the time waiting for the provider to come up was waiting for the dedicated notice zinc. So that process was actually longer than building in a cash provider. So having them. Available every hour and be able to sink Within. 30 seconds is obviously going to be huge going forward. and that's probably good update is I'm not sure that everyone on this call was aware of this new. Snapchat service that we have created Zeke doing all the work on the back end, but obviously that's going to be very important going forward. + + +### 00:35:00 + +Tyler Wright: Excellent any other discussion topics that anybody wants to talk about here related to support? + +Tyler Wright: if not again, please continue to follow the support repo for all things related to the core code base follow the console repo for all things going on relate to the cash console much appreciate all the Insiders vanguards members of the community here on the call and listening in later and just involved in continuing to provide support to existing users teams and projects and companies are trying to integrate with the cash again much appreciate all that efforts. Just a reminder the Sig providers monthly meeting is going to be starting in about 22 minutes or 21 minutes at this point. We'll get an update from Jigger and the ball and all the work that they've been doing related to console 2.0 and integrating crador into the Akash console experience. If anybody has any other topics related to provider again, please feel free to join that call and we can talk about those. + +Tyler Wright: Those in more detail and about 20 minutes. But again, thank you everybody for their time today. Make sure this recording and transcript is available shortly. But again another great call. Thank you all and we'll continue to update in between meetings in specific tickets or again. Look out for some announcements in Discord elsewhere. I believe actually Andrey correct me from wrong, but you did put an announcement Provider channels as recently as today with updates for folks on how to update to provide a Services version 0.6.4. So again, if anybody has any questions there what we'll talk about in more detailed and providers, but again, it also touches support in looking at those updated instructions, so + +Tyler Wright: Look out for the provider announcements and again much appreciate everyone's time and energy today. Hope to see many of you and sit providers the steering committee that originally tomorrow is now scheduled again for August 29. So again, no steering committee tomorrow. There will be a steering committee as normal on August 29th at the same time next Thursday, but hope to see you all around the community and thank you all for all that you do. Have a great rest of your day. + +Zeke E: Thanks everybody. + +Tyler Wright: Hope to see many of you and stick providers. + +Rodri R: See you in a bit. + +Scott Carruthers: Thanks. + +oo o: live long and prosper + + +### Meeting ended after 00:51:13 👋 From 2fc5b279984d10e05329c4c20b650c49a8bba795 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 27 Aug 2024 08:29:08 +0000 Subject: [PATCH 125/138] Create meeting notes for sig providers #20 (#670) * Create meeting notes for sig providers #20 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 020-2024-08-21.md added transcript Chore: add recording link Signed-off-by: Drinkwater * Update 020-2024-08-21.md added recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-providers/meetings/020-2024-08-21.md | 214 +++++++++++++++++++++++ 1 file changed, 214 insertions(+) create mode 100644 sig-providers/meetings/020-2024-08-21.md diff --git a/sig-providers/meetings/020-2024-08-21.md b/sig-providers/meetings/020-2024-08-21.md new file mode 100644 index 00000000..5f7bc40f --- /dev/null +++ b/sig-providers/meetings/020-2024-08-21.md @@ -0,0 +1,214 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #20 + +## Agenda +- Introduction and overview of meeting topics. +- Updates on the Praetor App and Console 2.0 development. +- Discussion on Provider Services v0.6.4. +- Implementation details of the new Snapshot Service. +- Review and update of provider-related documentation. + +## Meeting Details +- Date: Wednesday, August 21, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://eyppjrj4mhnx5sbrndju5rgjpdcmejx3c76cn4d7isytmkhceq7q.arweave.net/Jh70xTxh237IMWjTTsTJeMTCJvsX_Cbwf0SxNijiJD8) +- [Transcript](#transcript) + +## Participants +- Andrey Arapov +- B S +- Deathless +- Deval Patel +- Jakob Hürlemann +- Jigar Patel +- oo o +- Rodri R +- Scott Carruthers +- Tyler Wright +- Zeke E + +## Meeting notes +- **Praetor App and Console 2.0 Integration:** + - Jigar Patel provided updates on the progress of integrating the provider process into Console 2.0. + - The current focus is on transitioning from k2 to k3s, improving the visual and functional flow for users managing Akash providers. + - The new scripts developed for Praetor are being tested internally, showing positive results. These scripts ensure compatibility for both multi-node and single-node setups on k3s. + - There is excitement about moving these changes into production. The new Console 2.0 dashboard will include features such as real-time lease monitoring, CPU and memory utilization statistics, and financial data related to leases. + - The upcoming version 0.6.4 of Praetor will support easy upgrades from version 6.2. The update is expected to roll out shortly, and feedback from the community will be sought to refine the experience further. + +- **Snapshot Service Integration and Helm Chart Updates:** + - Zeke E highlighted the need to update the Helm charts on GitHub to incorporate the new snapshot service, which provides hourly snapshots. This service is expected to enhance the speed of environment setups and testing for Akash providers. + - Scott Carruthers suggested a cautious approach to adopting the new snapshot service as the default in Helm charts. He recommended a testing period to ensure there are no connectivity or stability issues before making it the default. + - Andrey Arapov supported the idea of a testing phase and suggested updating the Helm charts after verifying the snapshot service's reliability. + +- **Migrating from K8s to K3s**: + - Zeke E asked about documentation and support for migrating from a K8s setup to K3s. + - Andrey Arapov explained that while technically possible, such migrations could be complex due to differences in container runtimes, configuration files, and networking setups. + - He suggested that in most cases, it might be easier to announce a maintenance window and rebuild the cluster rather than migrate. + +- **Documentation Updates:** + - Rodri R pointed out that some sections of the provider documentation, particularly those related to hardware requirements, are outdated and need revisions. + - Tyler Wright agreed and mentioned that this would be added as an action item. There will likely be a pull request (PR) made to update the documentation to reflect current needs accurately. + +- **Community Acknowledgement and Support:** + - Tyler Wright expressed appreciation for the continuous support provided by community members like Andrey, Scott, Tampa, and Deathless, who actively engage in the provider channels to assist new users and share their expertise. + - Deathless was specifically mentioned for his ongoing support in answering questions, sharing success stories, and helping new members navigate the provider landscape. + +- **Cosmos SDK 47 Testnet Participation:** + - Tyler Wright invited participants to join the testnet for the upcoming Cosmos SDK 47 upgrade. This testnet aims to thoroughly test the network, review documentation, and ensure all components function correctly. + - Participants with available bandwidth are encouraged to get involved. AKT rewards are available for those who contribute significantly to the testing efforts. + - Interested individuals should contact Tyler Wright or express their interest in the public channels. Announcements and updates related to the testnet will be shared soon. +**Next Steps:** +- Monitor the implementation and testing of the new snapshot service and any updates from the Praetor team. +- Ensure timely updates to the provider documentation. +- Engage with the community to gather feedback on new features and encourage participation in testnet activities. + +**Closing:** +- Tyler Wright thanked all attendees for their contributions and ongoing support. +- He encouraged continued collaboration in the provider channels and reminded everyone to stay tuned for updates on the snapshot service and upcoming testnet activities. +- The meeting concluded with expressions of gratitude from several participants. + +## **Action Items:** +- **Jigar Patel & Deval Patel**: + - Continue working on the integration of the Praetor app into Console 2.0. + - Prepare and communicate the release of Praetor version 0.6.4, encouraging community members to test and provide feedback. + +- **Zeke E**: + - Proceed with plans to update the GitHub repository for Helm charts with the new snapshot service, following a period of testing to ensure stability and functionality. + - Monitor the performance and reliability of the snapshot service, and report any issues encountered during testing. + +- **Scott Carruthers & Andrey Arapov**: + - Participate in the testing of the new snapshot service as part of the Cosmos SDK 47 testnet activities. + - Decide on the appropriate timing to update Helm charts based on test outcomes and community feedback. + +- **Tyler Wright**: + - Ensure that documentation updates are prioritized and completed, possibly through submitting a pull request. + - Facilitate community involvement by sharing resources and updates related to the new snapshot service and other developments. + - Coordinate feedback and participation for the Cosmos SDK 47 testnet and engage with interested community members. + +- **All Providers**: + - Review the new Console 2.0 dashboard features when they become available and provide feedback. + - Continue engaging in community discussions and provide support to new users and other providers. + +- **Cosmos SDK 47 Testnet Participants**: + - Reach out to Tyler Wright or express interest in public channels to participate in the testnet and contribute to testing and feedback activities. + +# **Transcript** + +Tyler Wright: All right, welcome everybody to providers monthly meeting. It's August 21st 2024. + +Tyler Wright: During the special interest group for providers monthly meetings the groups discuss anything related to being a cost provider in the past. We've gotten updates from jigarette DePaul and all the work that they've been doing on Trader app is one of the preferred ways to build a provider on the Akash Network making it significantly easier to do that as of the last four or five months jigar and the ball have joined the overclock Labs 14 and are now building pretor into console as a part of the console 2.0 effort. So again console in the future will be a place where folks can both deploy and build and manage providers. We'll get an update from jigarette ball and all the work that they've been doing and some of the next steps. + +Tyler Wright: We all discuss a little bit about Andre recently put an updates in the provider announcements Channel around Provider Services version 0.6.4 documentation again, as also getting updated as of now, but again, there's clear path for folks to upgrade their providers. If anybody has any questions again, feel free to ask them here, but I know that's some overclock Labs manage providers or in the process of being upgraded if not already upgraded. So again, we'll discuss that if there's any other topics that anybody wants to discuss feel free to drop them in chat. I know there are some teams that may not be able to make it this month, but there are some teams that are building provider related. + +Tyler Wright: Support Solutions and are talking about providing Demos in September. So again, I'm sure there will be a lot of messaging going on in various Discord channels leading up to some of those potential demos. It'd be great to have many of the folks here on this call who again run providers and are very just In tune with the provider experience on Akash to get some feedback to those teams and individuals. Again, if anybody has anything that they want to specifically provider will also discuss that. again + +Tyler Wright: One other thing that we'll discuss and we kind of discuss it during six support is in shoutout to Zeke who just joined us. There is a new snapshots service and it'll be available at snapshots at a cash dot Network. This is a service act out by the core team that again has a snapshot on an hourly basis that providers and others can use Zeke. I see your hand Go ahead and Zeke. + +Scott Carruthers: Andy may have some thoughts here as well. I had thought about that as well that Snapchat service could be our default in Helm charts. I don't know if we want to give some period time to and I can't imagine there's going to be but a snapshots are working they're working, but we could give it a little period of time to Ensure there are no issues like connection issues maybe necessarily even core snapshot related. So Andy, I don't know if you have any thoughts if we want to update the home charts immediately or possibly give it a short period and then update. + +Andrey Arapov: Let's give it some good. + +Tyler Wright: I'll put that in action either but I was thinking the same thing maybe we could just do a couple of tests as we're getting into this test net for the cosmos SDK 47 upgrade. And then once we feel a little bit more comfortable, even though I know that many people are using it currently like Scott Zeke's some others. Then we can update their home charts accordingly. + +Tyler Wright: But again, there will be some links shared for that snapshot service that is available to anybody in the community again, there's still a snapshot service and Pikachu and some other members of The Wider Community. But this spec for the specific snapshot service was again something that could be overclock managed just in case, there's ever any issues with poker shoe or anybody else from the community, being that they are managing their own businesses as well as the desire to have snapshots available and an hourly basis because that it greatly increases the speed of for those that are looking to set up providers or looking to do a number of tests. Go ahead Andrey. + + +### 00:05:00 + +Andrey Arapov: I just wanted to add something about the snapshot. So sometimes when we are creating the network we have High knowing that maybe would stop at the height and then all the notes expecting the new Akash version + +Andrey Arapov: and sometimes it's very rare, but it can happen. if they're great those bad that we need to recover from this snapshot up until that I lost last one. So it would be really nice if there's some short service will have this kind of ability to kind of detect the software upgrade proposals that were approved and based on that night in this particular photograph a great proposal that would make this kind of snapshots and so that they would last for longer than let's say an hour what or others like a week or so just in case some things going bad. So we have always listening thought before the third grade. + +Andrey Arapov: That's amazing. Thank you very much Zeke. + +Tyler Wright: terrific All right again, before we jump into any updates from Digger and Deval on all the work. They're doing related to the provider side of console 2.0. I do want to hand it over to Andrey again. He dropped an announcement for folks to upgrade their providers. I just want to see if there's any questions one from anybody here on the call or Andrey if there's anything that you wanted to specifically call out related to provide our upgrades. + +Tyler Wright: excellent Thank you as always Hunter. + +Tyler Wright: Thank you for that context Again, if anybody has any questions, feel free to drop them in the provider builds Channel again, I said this at six supports I'll just say it again especially related to folks that are looking to build providers. I've seen a great deal of support from just members of the community answering questions in a timely fashion so much appreciate obviously Andre Scott Tampa for all the work that they do, but I know that there's a number of people in the community that are offering advice on builds. and just supporting new users are trying to get involved in the provider side. So + + +### 00:10:00 + +Tyler Wright: shout out to those people and just saying involved in conversation. I know that he doesn't like to be talked about but I often see deathless in there too. Just like making sure that people are in tune, answering questions providing feedback talking about their success stories, things that they're working on so much appreciate that kind of constant conversation and collaboration with other members of the cash community. + +Tyler Wright: All right without further Ado I get me talk about snapshots. We talked about provider service upgrades. I do want to kick it over to jigarette and Deval who have been doing a great deal of work, obviously on Trader to this point and then are continuing to do more work on getting Prater into console 2.0. So Yeah, I'll just kick it over to jigarette and Deval to talk a little bit about what's been going on over the last month and kind of a look ahead and what they're looking what they're working on over the next month. + +Jigar Patel: Hey, thanks Yeah, so currently we are working on bringing the whole provider process into console to row and we are actually currently working on making sure that multi-node and the single node works on k3s and converting that process from k2k3s and Visually streamline the whole thing. Yeah, so + +Jigar Patel: Current the work is on making sure that power is being built or using this new scripts. There has worked on and whether it's very great. it's working great. We're internally on testing one some of the providers so far. So there is no issue on it. So we are actually moving them into production for our console provider process. And once that's like the whole continent already you're able to see the dashboard. It will see the lazy's that your product and currently holds on it able to pick up radio Provider from it. You're able to make new provider from the process. And yeah, we excited to be working. + +Jigar Patel: On Disney process. Once that's done. I will obviously post unto the ecosystem predator and also the provider channels so + +Jigar Patel: You can test it out the new process. Obviously. We look forward for any feedback that comes with it. In the meantime. We are also upgrading our Predator based the providers to the new the new 0.6.4, which is we're gonna Just Launch that in and a couple of hours. We're just doing fire testing. So you able to upgrade your printer Provider from six to two six to four pretty soon probably today and so once that's ready we'll also post that update into the ecosystem predator and our Channel as well. So yeah, look for that as well. Yeah and in general + +Jigar Patel: Being doing good been very welcome entertained. And we are excited to bring this new updates and upgrading the broader experience in terms of ux in terms of General process in terms of for simplifying a lot of stuff using k3s. So yeah really excited for it. + + +### 00:15:00 + +Jigar Patel: Yeah, so basically we are planning to Have dashboard and this Statistics. + +Jigar Patel: You don't have to install anything, right you will able to see all the leases in the past you're able to see your CPU memory utilization based on the leases. In the future. We are planning to add these feature where you will able to use your community file to just see your Cube statistics, right? But for now, you'll be able to see all the lazy related statistics all the financial related statistics. Also, you're able to see your CPU utilization every relation based on the release they get the provider. + +Zeke E: What about the ability to close leases from that dashboard so there's someone running and that I don't like or whatever. + +Zeke E: Great. Thank you. + +Zeke E: So with this new documentation and the student build process, will there be an option documentation to be able to migrate a current provider running K8? S and move over to k3s. if there's even any benefit to doing so + + +### 00:20:00 + +Scott Carruthers: Yeah, yeah, definitely. yeah, I don't yeah, I would have to give it some more thought. + +Andrey Arapov: Alec on the + +Tyler Wright: Go ahead rodri. I'll go ahead and go first and… + +Tyler Wright: then we'll have rodri follow up. + +Andrey Arapov: I don't just was wondering about this myself. + +Andrey Arapov: I think on the application. it's about like you can actually stop the cash provider service but the older manifest to move them to the new to build cluster, but actually that's gonna be quite complex and I'm not sure will be possible because once you have the container pots up and running and I know that 3s is using low level or container runtime. + +Andrey Arapov: it's all about how they can connect and I know that has specific config files which are different from Caterers. So there can be a bunch of mass in configs and also doing how they configure Telecom Network cni container networking interface plugin. I believe there will be so much pain to actually do this migrations mostly and it will be difficult the technique on different provider configurations because some providers may be using different settings. Let's say my cubes pray deployed before version 2.19 which was the distancing a year ago. It was set to I think Conflict for Calico now, it doesn't use it. long directly. So it's just one thing to just highlighted how complicated he could be. So + +Andrey Arapov: in my view it's easier to just destroy the cluster and rebuild it by announcing from maintenance window or just like you keep it running these cubes free as well. + +Tyler Wright: And we appreciate that Zeke. + +Andrey Arapov: Okay. + +Tyler Wright: Go ahead rodri. + +Tyler Wright: Great call out. I'll make sure it's as an action item. I'll probably with simple to make a PR when they have some time to update that as So thank you Roger for calling it up. + +Tyler Wright: I wanted to see if there's anything else related to a cost provider to anybody wanted to discuss right now. + +Tyler Wright: Again, I'm just tracking the provider Channel again. I know some teams are talking about presenting some solutions over the next month or so, but again just continues to be constant conversation that providers channel so much appreciate that and the providers build channel so much appreciate that. yeah, is there anything else anybody wants to discuss have to let you all go a little bit early and I know there's some next steps that will take in terms of Provider documentation. I know that again prayers going to be making some updates in terms of Provider service upgrades sometime very soon, but I want to see if there's anything else related to the hash provider anybody want to discuss at the time. + +Tyler Wright: If not, then again, I will follow up with some folks if anybody wants to get involved in testing for the cosmos SDK 47 upgrade. That'll be happening sometime very soon. Please reach out to me or just drop a note in a public Channel and I'll follow up with you again. Testing will include everything I think the idea is to + + +### 00:25:00 + +Tyler Wright: Have folks that want to participate in a testnet look at all of the documentation. Make sure that every part of the network works and then again from there. We'll do some more advanced testing with some strategic partners and some other folks and other clients in the community, but really looking to have folks that again have some bandwidth. There are akt Awards available, but have some bandwidth to test deployments test out things in the console and that would be highly appreciated over the next couple of weeks. But I'll drop some notes and announcements when we get to that time, but if anybody wants singing get involved again, feel free to reach out. + +Tyler Wright: If there's nothing else provide a related then again much appreciate the conversation. There's a number of action items. We'll take from this meeting. We're looking forward to seeing again updates from jigarette and Deval next month because I know that they work again diligently again jigars a new dad and he's still out there grinding. I hope he's getting some time for himself but much appreciate the work for the Prater team much appreciate all that Andre Scott's and everybody else on this call does in helping out the ecosystem as a whole so Thank you. All again. If anybody needs access to the provider build scripts the case way again, feel free to reach out to me or Scott there dropped in the chat here and you can share those as a beta path. But again much appreciated everybody. Look out for updates on a snapshot service coming very very shortly. + +Tyler Wright: Thank you all again for all that you do. We'll talk online for sure. See you soon. + +Scott Carruthers: Thanks, everyone. + +Jigar Patel: Thanks. + +Zeke E: Thanks everybody. + +Rodri R: See you soon. + +oo o: live long and prosper + + +### Meeting ended after 00:27:19 👋 + + From 32f8c36a74243f153e6c2285b3c500be94a4b2de Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 27 Aug 2024 08:31:10 +0000 Subject: [PATCH 126/138] Create meeting notes for Sig-Design #20 (#667) * Create meeting notes for Sig-Design #20 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 020-2024-08-20.md added transcript Chore: add recording link Signed-off-by: Drinkwater * Update 020-2024-08-20.md added recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-design/meetings/020-2024-08-20.md | 279 ++++++++++++++++++++++++++ 1 file changed, 279 insertions(+) create mode 100644 sig-design/meetings/020-2024-08-20.md diff --git a/sig-design/meetings/020-2024-08-20.md b/sig-design/meetings/020-2024-08-20.md new file mode 100644 index 00000000..a3a954fd --- /dev/null +++ b/sig-design/meetings/020-2024-08-20.md @@ -0,0 +1,279 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #20 + +## Agenda +- Review of ongoing design projects +- Discussion of Akash website updates and issues +- Product design advancements for Akash Console +- Merchandise and giveaways for events +- Working group for YouTube content creation +- Akash Shopify store and potential expansion to other platforms + +## Meeting details +- Date: Wednesday, August 20, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://t3sgdqvogazfp5dgoxojhngj43wccndepjg5f7ajo35y5h4z32oq.arweave.net/nuRhwq4wMlf0ZnXck7TJ5uwhNGR6TdL8CXb7jp-Z3p0) +- [Transcript](#transcript) + +## Participants +- B S +- Denis Lelic +- James Kano +- Marian Gheata +- oo o (Oakley) +- Oyase +- Robert Del Rey +- Tyler Wright +- ⻲人小 河 + + +## **Meeting Notes** + +- **Review of Ongoing Design Projects:** + - Denis Lelic welcomed everyone and provided an overview of the meeting's purpose. + - The group discussed the ongoing design initiatives, focusing on the improvements and updates made in the past month. + +- **Akash Website Updates:** + - Denis Lelic mentioned the creation of several issues related to the Akash website on GitHub. + - Key areas of focus include the pricing page, where users will have a unified experience for GPU pricing and usage calculators. + - The group is working on a new menu experience to enhance user navigation. + +- **Product Design Advancements for Akash Console:** + - Denis Lelic shared updates on product design advancements for the Akash Console, an open-source deployment tool. + - Credit card payments are being integrated, along with new features from the Praetor app. + - Shared product and engineering [roadmaps](https://github.com/orgs/akash-network/projects/) for more detailed information on upcoming features. + - The goal is to create a comprehensive tool for users to provide compute and deploy on the platform. + +- **Upcoming Events:** + - Denis Lelic highlighted several upcoming events in September and October, with the Akash community involved in designing booths, giveaways, and merchandise. + - Tyler Wright suggested ideas for new event giveaways, such as trucker hats and specific gifts for token249, like moon cakes. + +- **Merchandise and Giveaways for Events:** + - The group discussed the types of Akash-branded merchandise available, including shirts, hats, and pins. + - Tyler Wright encouraged contributions to the Shopify store, noting that it serves as a marketing tool with profits directed to the community pool if any arise. + +- **Working Group for YouTube Content Creation:** + - Robert Del Rey provided updates on the YouTube working group, including the creation of short samples and responding to comments on the YouTube channel. + - The group is working on uploading steering committee call videos with proper branding and thumbnails, with assistance from other members like B S and Oakley. + - Robert encouraged members to join the working group if interested in video editing, creating thumbnails, or other content-related tasks. + - Denis Lelic [shared a link](https://akash.network/brand/resources/) to the Akash logo kit for those needing brand assets for video production. + - Denis addressed the distribution of an open-source font used in the videos, ensuring no license violations. A [download link](https://www.fontshare.com/) for the font was provided.\ + - A Canva project was created to collaborate on the graphics, which will be shared with Denis for feedback. + - The group plans to finalize the graphics and upload the Steering Committee Calls videos once completed. + +- **Akash Shopify Store and Potential Expansion:** + - Tyler Wright reiterated that the items sold on the Shopify store are at cost, with any potential profits going to the community pool. + - Oakley suggested expanding to platforms like Redbubble, which the group agreed to explore further. + - Denis Lelic and Tyler Wright emphasized managing efforts and ensuring that community contributions align with Akash's overall goals. + +- **Community Contributions and Opportunities:** + - Tyler Wright highlighted ongoing community contributions, particularly in creating content for the Akash website and YouTube channel. + - A new mission in Zealy will involve designing Akash-branded swag, with a reward of 15 AKT for selected designs. + - Members were encouraged to participate in various working groups and contribute ideas for future initiatives. + +- **Recaps of SIGs Content:** + - Tyler Wright introduced the idea of creating recaps for the Special Interest Groups (SIGs) on a weekly or monthly basis. B S has been assisting with this effort. + - The recaps will be hosted on the Akash website as blog posts, summarizing key activities in SIGs and working groups, with links to notes and a look ahead. + +- **Akash Zealy Missions:** + - Robert Del Rey announced a mission on Akash Zealy related to the SIG Design call. The secret word for the mission is "SWAG." + - Robert also discussed an upcoming mission for designing Akash swag, where community members can submit designs for the Akash shop. The mission will be part of Sprint 2, and selected designs will be rewarded with 15 AKT. + +## **Action Items** +- Oakley will explore and potentially test Redbubble for Akash merchandise, with findings to be reported in the next meeting. +- Attendees are encouraged to engage with Akash Zealy missions, including the secret word "SWAG" and upcoming swag design missions. +- Community members are invited to participate in the upcoming mission on Zealy to design Akash-branded swag, with a reward of 15 AKT for selected designs. +- Members interested in frontend development or design are encouraged to join the Akash website working group meeting on Thursday. +- B S to continue developing recaps for SIGs, with feedback from Tyler Wright, and publish them as blog posts on the Akash website. + +# **Transcript** + +Denis Lelic: Hey everybody and welcome to today's Sikh design meeting. As usual we meet on a monthly basis where we discuss everything design related and sometimes we even touch topics such as content creation and so on and so on. So I'm glad. Some new community members are joining so welcome if you're here for the first time. I'll just get us. Going and maybe we cover some of the stuff we've done in the past month So maybe we start with. + +Denis Lelic: So for those of you who are attending working group for a cash website. There was a lot of issues created. I'll just drop a link from our GitHub. Website report here in the chat section. So there was a lot of shoes created which is good. I think everyone is just trying to evolve the website improved the experience. So we're trying to work on several areas. + +Denis Lelic: just to highlight a few maybe pricing page where we're gonna offer one unified experience on one single page where users could switch between GPU pricing usage calculator and if a user decides they want to Contribute compute they can also calculate how much would they earn? + +Denis Lelic: Maybe the next one I think. That's gonna have a positive impact and it's gonna improve the user experience is probably the new menu experience. So you can just go through some of these issues and of course if you're interested in any way of contributing just drop a comment there and will connect offline + +Denis Lelic: Let's Yeah, the next topic would be maybe product design. So on the product side. We're making some advancements on. A cash console for those of you that are maybe new or not aware of it. It's like deployment tool. + +Denis Lelic: Which is also open source. So everyone. Can you just give me a second? I'll share Maybe. + +Denis Lelic: Product and Engineering roadmaps, you can see what's happening in more detail right here in this link that I dropped in the comment section. So yeah, we're working on a bunch of stuff on that front. Credit card payments are on the way. There's gonna be + +Denis Lelic: some new features added and the app is gonna grow. So we're looking to add some of the functionalities from the Prater app. and I believe this is gonna + +Denis Lelic: Be a great way for users to have one tool. So either provide compute and on the other side they can deploy. + +Denis Lelic: Yes, and Tyler just mentioned. So anyone interested in having a more detailed. Walkthrough you can join sick clients later today. + +Denis Lelic: Okay, moving forward. There's a lot of events happening in the next couple of months. So in September and October, there are covered a couple of them. Maybe I'll just share. + +Denis Lelic: So here's the Community page from our website and hear all the upcoming events. You can find the link in the chat section. Yeah, so on the event side we try to support all the community members in core team members that are attending these events. so we've been involved I can designing booths giveaways like stickers. and merge and so on and so on and + + +### 00:05:00 + +Denis Lelic: yeah. That's it from the event side. + +Denis Lelic: Yeah talking about Merchant and all the giveaways. Yeah, Tyler you want to say something about the events? + +Tyler Wright: Yeah, I just want to throw out some ideas, obviously in the past we've had shirts socks pins and some of those things that have been given away at events insiders have worn and they seem to have gotten a lot of positive response at the most recent event in Buenos Aires for Cosmo verse that just happened. It seemed like there's some trucker hats the cash made obviously all this stuff is in the vein of just continuing to spread awareness around Akash what it is how people can use it one of the things that some people from overclock as well. As some people in the community have talked about is potentially specific gifts for token 249 because I think that's a special period so they were talking about many moon cakes for some events happening there. I know that there's a booth happening Atoka 24:9 a hacker house. I think some VIP events as well. So there's + +Tyler Wright: Is around very specific products that again can be a cost-branded and given a way to folks as Denis mentioned. If anybody has an ideas about products that they think should be added to the Shopify store. That's an effort that's ongoing and we talk about here, obviously the shop data cost.network stories quite basic, obviously much of the group is focused on building a blockchain and a core product and permissionless decentralized Marketplace for compute. But again, as a part of Sig design, there are opportunities to help out with the website, whether it be pitching ideas of our student at the shop pitching ideas of products that you want to be added that you think should be a class branded or the layout of the shop, all ideas are welcome and + +Tyler Wright: recommended and again, it's Denis mentioned for those that want to participate in creating content whether it be videos Graphics Shopify helping out with some of the working groups like The working group for the class YouTube. They're working group for the college website. There are again opportunities to contribute and earn akt, so we're always looking for folks that want to contribute. + +Denis Lelic: Thanks Yeah, I just shared the link from Swag shop data network. Feel free to check it out, but hopefully in the next week's. We're going to try to make this a little better experience and with some new Place there as well. Yes. I am. Not sure if you talked about the newly formed working group for YouTube. So it was set up I think two or three weeks ago, Robert's has been pretty much involved there. Fortunately. I couldn't make it to some of these meetings. I had a conflict. + +Denis Lelic: Robert if you're able to talk feel free, so otherwise I'll just give + +Denis Lelic: a call to action for everyone who's interested in any kind of possible videos out there like shorts and long form or editing or creating thumbnails, please join that working group. What's up? Yes, Robert. Go ahead. + +Robert Del Rey: Thank you is. So in today's call we basically recup. What we did last week. + +Robert Del Rey: We have spoke about the short samples. we showcase one the participants in the call. let me look for the notes happy We also talk about responding comments in the YouTube channel. + +Robert Del Rey: and yeah, basically, the one thing that was not completed was overloading the steering Comedy Calls videos into the YouTube channel. We wanted to add an opening a screen and a closing screen along with Brandon thumbnail before uploading those videos. + + +### 00:10:00 + +Robert Del Rey: The main reason why it's because you cannot edit a video Once you upload it. So the video has to be ready before upload the video. And I really wanted to follow up on that b s I believe he's in the call and also Oakley they both offer to help out with this Graphics. So then I know sometimes you have lots of stuff going on your side and I want to let you know that we have people here ready to support you with a graphics. What I would thinking is that they could get some draft going and show them with you for your feedback. I created a kamba project. I share that with BS and we are. + +Robert Del Rey: Together in that project so we can share the link with you as well and you can see the changes there or maybe we can share that in the cash YouTube channel or in The Design Channel, whatever Channel you prefer. Yeah, so once we have those Graphics already we can set uploading the informally calls star shipping out how the videos will look. + +Robert Del Rey: Around it doesn't all make sense. + +Denis Lelic: Thanks, That sounds good. And I'm happy that group is growing and there's interest in contributing for anyone who might need a cash brand assets. I'm just gonna share here link where you can download logo kit so you can find everything there. + +Denis Lelic: So feel free to play around with it, and I'm also available on Discord if you need anything. + +Denis Lelic: Just like a feedback or if you need any additional assets. Feel free to DM me or just drop it in the channel sick design. + +Denis Lelic: Yes, I don't know. Who's first Robert or Tyler. Go ahead. + +Tyler Wright: No, Robert was first Robert goes. + +Denis Lelic: Yeah, the reason it's why it's not added is I would just like to Distributing that font it's open source. I'll share it here. So if I believe in that kid, there's also a manual Which font is used and you can just download it here fawnshare.com. Yeah, and as I said, I just wanted to avoid any conflict with foreign chair team, even though it's open source. I just thought it would be more safer not to include it there. So we wouldn't violate any of their licenses. + +Denis Lelic: Or you can download it here. I provided Link in the chat section. Tyler + +Tyler Wright: Yeah, the one thing I want to add. I'm not really sure if we talked about it at I think design quite yet, but + +Tyler Wright: be maybe we have but b s at another down team has been helping out and I owe him some feedback, but he's been helping out to create basically Recaps of the cigs on a monthly slash weekly basis. We're figuring out the Cadence. Now those ideally should be needed via the website. So again, as blogs that can kind of recap for folks what's been going on the six in the working group front a paragraph on each with some of the highlights with links to the notes and maybe even sometimes a look ahead. So I want to shout out the work that he's continuing to do. I think it'll be very impactful for folks. I know everyone here is busy but folks have showed a desire to help contribute and obviously the only way that a class will grow to where we all wanted to go is he is by getting contrib + + +### 00:15:00 + +Tyler Wright: from a number of different kinds of people. So just look out for blogs. Hopefully coming soon. I think he'll ask some more questions either to piyush or come to the working group session and look out for those soon. If anybody else wants to contribute again, whether it be video or other kinds of content, please feel free to reach out. There's plenty of opportunities. + +Denis Lelic: Thank you time. So yeah, we covered a lot of stuff that's been done. I think all of these initiatives are just continue to work on in the next month or so. + +Denis Lelic: But I would like to. Just open the floor if anyone has any questions anything, maybe you want to start working on maybe you want to create a new initiative. + +Denis Lelic: Feel free to talk now or you can always as I said DME or just drop your ideas in this Design Channel. + +Denis Lelic: Okay, cool. I just see a lot of claps. I guess you support all the initiatives that are happening currently there is many but + +Denis Lelic: Hi. Did you want it to say anything else? Did you had anything else to discuss? + +Denis Lelic: Thank you Agree on everything. So anyone who's Feel free to join the meetings. I can also share. I'm not sure if I shared it, but I will now the community calendar where you can subscribe and + +Denis Lelic: you won't miss any of the future meetings. Just give me one second to + +Robert Del Rey: Ahead and share the secret word for the sick design called mission in a cash ceiling. Their cash series support all we have missions to engage with the cash community and new members and one of those missions is attending to this type of calls. so the secret word for this particular call it's going to be swag As w a g assassin said obvious and whiskey as in Alpha and G as in golf swag, that's the secret word for this or you can put it in now or when you listen to the recording of this call. + + +### 00:20:00 + +Robert Del Rey: In another topic. it's related to see you guys attending this call. You will get the alpha. We actually are working on a mission. I will take over the screen if you don't mind this. We're working on a mission. About designing a cash swag for the Akash shop. This Niche is going to be available in the Sprint number two and using my screen. Yeah, I believe you can. + +Robert Del Rey: Yeah, So this Mission we plan to launch it on a Sprint number two, it's their cash slog designer as you can see we want people to create Unique Designs that can be used by their cash community and either to use one of your designs Denis as an example here. I hope you don't mind and there are also resources where people can go for example, they can get the same thing that you share for the brand assets. It's right here. and the price for each selected winners gonna be 15 akd this can be discussed. But at the moment this is how it's looking right now and to release this on a screen number two and hopefully get The best designs that we can from the cash community and reward them for it. So I'm just gonna drop that offer here in the Channel with you. And yeah. + +Robert Del Rey: that's only guys that's + +Denis Lelic: Go ahead. + +Tyler Wright: So one quick caller on the record anybody who wants to participate with the shop, right now the items are sold at cost. So nobody's making any profit the idea is that if there were ever profits from any of the products sold to the Shopify store. They would just go to the community pool. So just putting that out there on the record. I think that's mention that number of times but always want to clarify why the shop store exists again as a awareness and marketing tool and then where the funds go from the Shopify store. So just putting that on the record again. + +Denis Lelic: Thank you someone raised their hand, but I can see and… + +oo o: Yeah, that was me. + +Denis Lelic: I go ahead please. + +oo o: yeah about the shop that Tyler just spoke about I know if you have seen swag on Redbubble and similar size before us and is there anything that's stopping a cat from also displaying the Swag there in places like that. + +Denis Lelic: Then you drop the link. Of the shop use just mentioned here in the chat section, please. + +oo o: Redbubble One of those pop art sites here. + +Denis Lelic: Okay, I got it here. Is that like? + +oo o: yeah, essentially one of those sites where essentially you can find all sort of stuff, from your favorite TV show to just something with you whimsical? but I've actually seen a few startups t-shirts on it before + +Denis Lelic: Yeah, it's something I guess we could. consider but as Tyler mentioned where not looking to create + +Denis Lelic: to make profit out of the shop. It's more like support the community or anyone who's Interested in Akash and likes the design maybe in purchase it. But yeah, maybe we can consider this. + +Denis Lelic: And we can drop a couple of designs here in the future. just to see + + +### 00:25:00 + +Denis Lelic: How it is going to go? What do you think time? + +Tyler Wright: Yeah, I would agree. I'm always down to try new things. The only thing that we're trying not to do is again, but because there's so many efforts around Sig design. We're just trying to manage our efforts. So if anybody here is I really think that this should be on Redbubble or any other platform then we can discuss it at one of these calls or maybe async and then go from there. I've seen Redbubble before I thought it was a site where it's kind of like Etsy where anybody can just throw up a design that's non-incorporated. if a member of the community didn't want to attend to Sig design, they could just make their own Akash merch and then throw it up on Redbubble. That's how I thought it was used. But again, I'm happy to continue to explore + +oo o: I think a lot of it is like that… + +Tyler Wright: Okay, Excellent. + +oo o: but I've actually seen official Marvel and DC mark on it. + +Tyler Wright: That's good to the only other thing I think about is the customer. + +oo o: Yeah. Yeah. + +oo o: Robert never,… + +oo o: I've never put anything. + +Tyler Wright: Go ahead. Sorry. + +oo o: Okay, Yeah, Robert put up a question. He was asking if it cost anything how much it costs are your clothing? I've never actually put a design up on Redbubble. I'm mostly been a customer. never a seller. creator You may go gone. + +Denis Lelic: Yeah. As Tyler mentioned maybe if you're interested, you can just give it a try see what happens and you can share. + +Denis Lelic: Everything you found on in our next meeting. + +oo o: over + +Denis Lelic: cool okay guys, so + +Denis Lelic: I think we've covered pretty much everything. I'm glad we had a couple of new discussions. Thanks, Robert and I can't see your name. There's just like two o's, so thank you. Double o + +Robert Del Rey: let's hopefully + +Denis Lelic: Oakley okay Oakley. Thank you. + +Denis Lelic: but I think maybe you have this information. I'm not sure if working group for their cash website is happening this week on Thursday. So everyone is welcome to join. There's a lot of stuff happening there. So if you're interested in either front end development or you want to contribute as a designer, please for you free to join our next meeting sync design is gonna happen next week next month. + +Denis Lelic: I hope we'll see each other. Next month as well. So thanks again for joining today and Have a great day. + +Robert Del Rey: Thank you Denis. + +Tyler Wright: Thank you all. + +Denis Lelic: Thank you. + +oo o: live long up + +Robert Del Rey: I say everybody. + +Denis Lelic: Bye-bye. Thank you. Bye. + + +### Meeting ended after 00:28:36 👋 + From f3fe81608d4cc3b0cd14e16b31666f1c5220d53f Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 29 Aug 2024 12:52:36 -0400 Subject: [PATCH 127/138] steering committee Update README.md add meeting details for July 2024 Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index dded03a4..edf7401f 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -31,7 +31,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, May 02, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md#transcript) |[Link](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) | Thursday, June 06, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md#transcript) |[Link](https://capv32vqn7vrb5u3qvsjn3n6y6swnjkba32ukvydflmqqhrxbswa.arweave.net/EB9d6rBv6xD2m4Vklu2-x6VmpUEG9UVXAyrZCB43DKw) | Thursday, June 27, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/017-2024-06-27.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/017-2024-06-27.md#transcript) |[Link](https://upv27tytyope2fseqvgnnre2au6nmmo65bs2c2fvuxtohsr5bpjq.arweave.net/o-uvzxPDnk0WRIVM1sSaBTzWMd7oZaFotaXm48o9C9M) -| Thursday, July 25, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, July 25, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/018-2024-07-25.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/018-2024-07-25.md#transcript) |[Link](https://vowukrgkuwsl7fdoune7kqruamcwsbhm7bh4aic6dse6vyussagq.arweave.net/q61FRMqlpL-UbqNJ9UI0AwVpBOz4T8AgXhyJ6uKSkA0) | Thursday, August 29, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, September 26, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, October 31, 2024 11:00 AM PT (Pacific Time) | | | From cee7872b03186c835e3afbbe46c8f8334b5b4414 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 6 Sep 2024 09:06:02 +0000 Subject: [PATCH 128/138] update readme table and wg akash youtube notes (#676) --- sig-analytics/README.md | 6 +- .../{013-2024-08-15.md => 014-2024-08-15.md} | 0 sig-chain/README.md | 2 +- sig-clients/README.md | 2 +- sig-community/README.md | 2 +- sig-design/README.md | 2 +- sig-providers/README.md | 4 +- sig-support/README.md | 2 + wg-Akash-youtube/meetings/001-2024-07-23 | 86 +++++++++++++++++++ wg-Akash-youtube/meetings/002-2024-07-30 | 70 +++++++++++++++ wg-Akash-youtube/meetings/003-2024-08-06 | 74 ++++++++++++++++ 11 files changed, 241 insertions(+), 9 deletions(-) rename sig-analytics/meetings/{013-2024-08-15.md => 014-2024-08-15.md} (100%) create mode 100644 wg-Akash-youtube/meetings/001-2024-07-23 create mode 100644 wg-Akash-youtube/meetings/002-2024-07-30 create mode 100644 wg-Akash-youtube/meetings/003-2024-08-06 diff --git a/sig-analytics/README.md b/sig-analytics/README.md index 65cb43d1..6856adbb 100644 --- a/sig-analytics/README.md +++ b/sig-analytics/README.md @@ -31,9 +31,9 @@ Analytics Special Interest Group is dedicated to defining and building tools tha | #9 | Thursday, October 12, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/009-2023-10-12.md) | [Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/009-2023-10-12.md#transcript) | [Link](https://v5ixigio4enkf7qhvlmzfptnlx6zkdite2skrznyil2d3xih6ana.arweave.net/r1F0GQ7hGqL-B6rZkr5tXf2VDRMmpKjluEL0Pd0H8Bo) | #10| Thursday, December 14, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/010-2023-12-14.md) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/010-2023-12-14.md#transcript) | [Link](https://ek6ahcmxfv2mnwpitrfidefkzfm6razh4zlv7cuowuue5tnrqy4q.arweave.net/IrwDiZctdMbZ6JxKgZCqyVnogyfmV1-KjrUoTs2xhjk) | #11| Thursday, February 15, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/011-2024-02-15.md) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/011-2024-02-15.md#transcript) | Coming Soon -| #12| April 18, 2024 09:00 AM PT (Pacific Time) | | | -| #13| June, 2024 09:00 AM PT (Pacific Time) | | | -| #14| August, 2024 09:00 AM PT (Pacific Time) | | | +| #12| April 18, 2024 09:00 AM PT (Pacific Time) | coming Soon | Coming Soon | Coming Soon +| #13| June 20, 2024 09:00 AM PT (Pacific Time) |Coming Soon |Coming Soon | Coming Soon +| #14| August, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/014-2024-08-15.md) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/014-2024-08-15.md#transcript) |[Link](https://j3ac6jsjcqd3hmfii6dophi4gunxiuqqxdeslkehhz6fpnvvgkta.arweave.net/TsAvJkkUB7OwqEeG550cNRt0UhC4ySWohz58V7a1MqY) | #15| October 2024 09:00 AM PT (Pacific Time) | | | | #16| December, 2024 09:00 AM PT (Pacific Time) | | | diff --git a/sig-analytics/meetings/013-2024-08-15.md b/sig-analytics/meetings/014-2024-08-15.md similarity index 100% rename from sig-analytics/meetings/013-2024-08-15.md rename to sig-analytics/meetings/014-2024-08-15.md diff --git a/sig-chain/README.md b/sig-chain/README.md index e9dbd75c..4f8da0ec 100644 --- a/sig-chain/README.md +++ b/sig-chain/README.md @@ -31,7 +31,7 @@ date: 2023-1-09T00:19:20-08:00 | #16| May 21, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/016-2024-05-21.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/016-2024-05-21.md#transcript) |[Link](https://t7vun4ttnoelbnwkis4rf7eacagljw7a5tsobsuujmsiycgjdpna.arweave.net/n-tG8nNriLC2ykS5EvyAEAy02-Ds5ODKlEskjAjJG9o) | #17| June 11, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/017-2024-06-11.md)| [Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/017-2024-06-11.md#transcript)|[Link](https://g6qelhldnaj52ry4xc56kge2wjrswqfgxrqs4iduth4cpqpndlfq.arweave.net/N6BFnWNoE91HHLi75RiasmMrQKa8YS4gdJn4J8HtGss) | #18| July 17, 2024 09:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/018-2024-07-17.md) | [Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/018-2024-07-17.md#transcript) |[Link](https://556xxz5f7wcokgit5qlznxtkdvmdkcrafobpcwztrytgflmcifjq.arweave.net/731756X9hOUZE-wXlt5qHVg1CiArgvFbM44mYq2CQVM) -| #19| August, 2024 09:00 AM PT (Pacific Time) | | | +| #19| August 13, 2024 09:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/019-2024-08-13.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/019-2024-08-13.md#transcript) |[Link](https://bcp7f4xex34ci3vtw7rfaeonelh52dkaqdb26xjfs67jojmips7a.arweave.net/CJ_y8uS--CRus7fiUBHNIs_dDUCAw69dJZe-lyWIfL4) | #20| September, 2024 09:00 AM PT (Pacific Time) | | | | #21| October 2024 09:00 AM PT (Pacific Time) | | | | #22| November, 2024 09:00 AM PT (Pacific Time) | | | diff --git a/sig-clients/README.md b/sig-clients/README.md index cdec57ef..fd661f9a 100644 --- a/sig-clients/README.md +++ b/sig-clients/README.md @@ -48,7 +48,7 @@ The goal of this SIG is to foster a community around each of these clients that | #14| March 27th, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/014-2024-03-27.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/014-2024-03-27.md#transcript) | Coming Soon | #15| April 24th, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/015-2024-04-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/015-2024-04-24.md#transcript) |[Link](https://j3gehsinfdsmtozvozl7ne3dv2w255mnewbmwe3unblpiayao3ya.arweave.net/TsxDyQ0o5Mm7NXZX9pNjrq2u9Y0lgssTdGhW9AMAdvA) | #16| June 25th, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/016-2024-06-25.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/016-2024-06-25.md#transcript) |[Link](https://g4sync4igp5y56x5cxfhh45vo4elgdzmcptwja4z33gcjhzkkoqq.arweave.net/NyWGi4gz-476_RXKc_O1dwizDywT52SDmd7MJJ8qU6E) -| #17| August, 2024 10:30 AM PT (Pacific Time) | | | +| #17| August 20th, 2024 10:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/017-2024-08-20.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/017-2024-08-20.md#transcript) |[Link](https://4mgemilgnadqtihidt2lpu7ocnkirkq4voj2pabf64hw5zdlqh3a.arweave.net/4wxGIWZoBwmg6Bz0t9PuE1SIqhyrk6eAJfcPbuRrgfY) | #18| October 2024 10:30 AM PT (Pacific Time) | | | | #19| December, 2024 10:30 AM PT (Pacific Time) | | | | #20| January, 2025 10:30 AM PT (Pacific Time) | | | diff --git a/sig-community/README.md b/sig-community/README.md index 3c92ff05..ffbde371 100644 --- a/sig-community/README.md +++ b/sig-community/README.md @@ -33,7 +33,7 @@ This SIG (Special Interest Group) is designed for Akash community members to pro | #15| May, 2024 11:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon | #16| June 11, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/016-2024-06-11.md)|[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/016-2024-06-11.md#Transcript)|[Link](https://nl4ez6metcnz3sdkdgvxj6b2opl74ywekhhfqfj3smj6m4in3e2a.arweave.net/avhM-YSYm53IahmrdPg6c9f-YsRRzlgVO5MT5nEN2TQ) | #17| July 09, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/017-2024-07-09.md) |[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/017-2024-07-09.md#Transcript) |[Link](https://x6pq6krlnowidy2qpsxdgyrnx7gz5i4ypuxxeemqsynsvipvhoaa.arweave.net/v58PKitrrIHjUHyuM2Itv82eo5h9L3IRkJYbKqH1O4A) -| #18| August, 2024 11:00 AM PT (Pacific Time) | | | +| #18| August 14, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/018-2024-08-14.md) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/018-2024-08-14.md#Transcript) | Coming Soon | #19| September, 2024 11:00 AM PT (Pacific Time) | | | | #20| October 2024 11:00 AM PT (Pacific Time) | | | | #21| November, 2024 11:00 AM PT (Pacific Time) | | | diff --git a/sig-design/README.md b/sig-design/README.md index 67c53019..13718d6c 100644 --- a/sig-design/README.md +++ b/sig-design/README.md @@ -34,7 +34,7 @@ date: 2023-1-09T00:19:20-08:00 | #17| May 08, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/016-2024-05-08.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/016-2024-05-08.md#transcript) |[Link](https://utgdid3tyicjsjmgvznzalfhes33oqqzoytow53oaqvlgg6nbmlq.arweave.net/pMw0D3PCBJklhq5bkCynJLe3Qhl2Jut3bgQqsxvNCxc) | #18| June 12, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/017-2024-06-12.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/017-2024-06-12.md#transcript) |[Link](https://ifqou2kkf6gqtmise2kelunxe2wc4xrcssgptlx3oh25flm7tcea.arweave.net/QWDqaUovjQmxEiaURdG3JqwuXiKUjPmu-3H10q2fmIg) | #19| July 17, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/019-2024-07-17.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/019-2024-07-17.md#transcript)|[Link](https://ifqou2kkf6gqtmise2kelunxe2wc4xrcssgptlx3oh25flm7tcea.arweave.net/QWDqaUovjQmxEiaURdG3JqwuXiKUjPmu-3H10q2fmIg) -| #20| August, 2024 08:00 AM PT (Pacific Time) | | | +| #20| August 20, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/020-2024-08-20.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/020-2024-08-20.md#transcript) |[Link](https://t3sgdqvogazfp5dgoxojhngj43wccndepjg5f7ajo35y5h4z32oq.arweave.net/nuRhwq4wMlf0ZnXck7TJ5uwhNGR6TdL8CXb7jp-Z3p0) | #21| September, 2024 08:00 AM PT (Pacific Time) | | | | #22| October 2024 08:00 AM PT (Pacific Time) | | | | #22| November, 2024 08:00 AM PT (Pacific Time) | | | diff --git a/sig-providers/README.md b/sig-providers/README.md index aa757fd6..9eb5be2f 100644 --- a/sig-providers/README.md +++ b/sig-providers/README.md @@ -33,8 +33,8 @@ Provider SIG covers everything pertinent to Providers on Akash Network. This inc | #16| April, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/016-2024-04-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/016-2024-04-24.md#transcript) | Coming Soon | #17| May 22, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/017-2024-05-22.md)|[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/017-2024-05-22.md#transcript) |[Link](https://a6qm5qjrbhmjkmbmsfldmoqzdspsaxypsgfq26wfw6ysnw3xp7cq.arweave.net/B6DOwTEJ2JUwLJFWNjoZHJ8gXw-Riw16xbexJtt3f8U) | #18| June 26, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/018-2024-06-26.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/018-2024-06-26.md#transcript) |Coming Soon -| #19| July, 2024 08:00 AM PT (Pacific Time) | | | -| #20| August, 2024 08:00 AM PT (Pacific Time) | | | +| #19| July 24, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/019-2024-07-24.md) | [Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/019-2024-07-24.md#transcript) |[Link](https://aa2i7ytftmtlehngryvt4m6jnaxvu5ku72e34u5akdetalzdimja.arweave.net/ADSP4mWbJrIdpo4rPjPJaC9adVT-ib5ToFDJMC8jQxI) +| #20| August 21, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/020-2024-08-21.md) | [Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/020-2024-08-21.md#transcript) |[Link](https://eyppjrj4mhnx5sbrndju5rgjpdcmejx3c76cn4d7isytmkhceq7q.arweave.net/Jh70xTxh237IMWjTTsTJeMTCJvsX_Cbwf0SxNijiJD8) | #21| September, 2024 08:00 AM PT (Pacific Time) | | | | #22| October 2024 08:00 AM PT (Pacific Time) | | | | #23| November, 2024 08:00 AM PT (Pacific Time) | | | diff --git a/sig-support/README.md b/sig-support/README.md index 547b4e75..d1b4161f 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -50,6 +50,8 @@ sig-support is responsible for defining mechanics of how support works at Akash | #32 | Wed, May 01, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/032-2024-05-01.md) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/032-2024-05-01.md#transcript)|[Link](https://fp4bufbowjh5thinihsyy52ddcyesjk2yofv4fgjmrhnkahxg5ua.arweave.net/K_gaFC6yT9mdDUHljHdDGLBJJVrDi14UyWRO1QD3N2g) | #33 | Wed, May 15, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/033-2024-05-15.md)|[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/033-2024-05-15.md#transcript)|[Link](https://qc3gxtikakjsqoqohkver467q5u675nuwy7ovtc6j4ajicy7vwna.arweave.net/gLZrzQoCkyg6DjqqSPPfh2nv9bS2PurMXk8AlAsfrZo) | #34 | Wed, June 26, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/034-2024-06-26.md) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/034-2024-06-26.md#transcript) |[Link](https://edy24xoc5isqb4ilutntgush3jmsnlcnfjaajdnsr2f5d34caktq.arweave.net/IPGuXcLqJQDxC6TbM1JH2lkmrE0qQASNso6L0e-CAqc) +| #35 | Wed, July 24, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/035-2024-07-24.md) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/035-2024-07-24.md#transcript) |[Link](https://aa2i7ytftmtlehngryvt4m6jnaxvu5ku72e34u5akdetalzdimja.arweave.net/ADSP4mWbJrIdpo4rPjPJaC9adVT-ib5ToFDJMC8jQxI) +| #36 | Wed, July 24, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/036-2024-08-21.md) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/036-2024-08-21.md#transcript) |[Link](https://wrx26ds6t7sofpahkzy5iphq7eqtfu3jln6xf5idxmrr2url4m5q.arweave.net/tG-vDl6f5OK8B1Zx1Dzw-SEy02lbfXL1A7sjHVIr4zs) ## Leadership diff --git a/wg-Akash-youtube/meetings/001-2024-07-23 b/wg-Akash-youtube/meetings/001-2024-07-23 new file mode 100644 index 00000000..a7223cf6 --- /dev/null +++ b/wg-Akash-youtube/meetings/001-2024-07-23 @@ -0,0 +1,86 @@ +# Akash Network - Akash Youtube Working Group (WG) - Meeting #1 + +## Agenda + +- Review the plan of action for overhauling the Akash Networks YouTube channel +- Discuss Phase 1 and Phase 2 of the YouTube channel improvement project +- Determine timeline for Phase 1 completion + +## Meeting Details + +## Meeting Details +- Date: Tuesday, July 23, 2024 +- Time: 08:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + +## Participants + +- Tyler Wright +- Robert Del Rey +- Rodri R + +## Meeting Notes + +### Background and Objectives + +- The YouTube Working Group emerged from the Special Interest Group (SIG) for Design +- Main goal: Overhaul Akash Network's YouTube channel to increase discovery and usability for new and existing users +- Robert Del Rey shared a [document](https://docs.google.com/document/d/1yA1V6HKoRhnXs29h_peTFRnlVUHARx7qfRM6eTHPz7w/edit?usp=sharing) with a plan of action in the Discord channel + +### Current State of Akash YouTube Channel + +- Inconsistent thumbnail designs across videos +- Limited categories displayed on the home page +- Outdated welcome video for non-subscribers +- Inconsistent video descriptions, some lacking detail +- Underutilization of relevant keywords like AI, DePIN, and blockchain + +### Phase 1 Plans + +- Improve overall look of thumbnails for visual consistency across the channel +- Optimize keywords in video descriptions and titles for better discoverability +- Update video descriptions to ensure consistency and include relevant keywords +- Revamp playlists into key topics: + - Deployments and tutorials + - Events (panels and other events) + - Akash Community videos + - Steering committee videos +- Create and upload a new welcome video for non-subscribers +- Update the channel banner to reflect current branding and information + +### Phase 2 Considerations (for future discussion) + +- Determine optimal frequency of video uploads +- Develop a strategy for creating and utilizing YouTube Shorts +- Explore options for remastering existing content +- Plan for creating new, original content + +### Timeline and Next Steps + +- Aim to complete Phase 1 in the next 20-30 days, with a target date of September 1st +- Transition into maintenance mode after the initial revamp +- Schedule a follow-up working group session for next week +- Continue asynchronous discussions in the Discord channel + +### Key Performance Indicators (KPIs) + +- Track and aim to increase overall channel viewership +- Monitor and work to increase channel subscriptions + +The meeting concluded with an agreement to continue discussions asynchronously and to involve other interested teams in future efforts for the YouTube channel improvement project. + +## Action Items + +- Robert Del Rey to obtain access to the Akash YouTube channel +- Robert to begin creating new categories and organizing existing videos +- Robert to work on keyword optimization and description updates for current videos +- Tyler Wright to provide Robert with access to steering committee and Akash Accelerate videos +- Team to collaborate on improving the YouTube channel banner +- Create a GitHub issue to track progress and assign tasks +- Discuss Phase 2 questions and strategies in the Discord channel +- Robert to share the planning document link in the GitHub issue + + + +## Transcript \ No newline at end of file diff --git a/wg-Akash-youtube/meetings/002-2024-07-30 b/wg-Akash-youtube/meetings/002-2024-07-30 new file mode 100644 index 00000000..634bee82 --- /dev/null +++ b/wg-Akash-youtube/meetings/002-2024-07-30 @@ -0,0 +1,70 @@ +# Akash Network - Akash Youtube Working Group (WG) - Meeting #2 + +## Agenda + +- Review access and documentation for Robert Del Rey +- Discuss YouTube channel improvements with Denis Lelic +- Review thumbnail designs by Robert Del Rey +- Discuss short-form content strategy +- Plan next steps and action items + +## Meeting Details +- Date: Tuesday, July 30, 2024 +- Time: 08:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + + +## Participants + +- Tyler Wright +- Denis Lelic +- Robert Del Rey +- Alex Pedersen + +## Meeting Notes + +- Tyler Wright provided an update on granting Robert Del Rey access to the Akash YouTube channel as a manager + +- Areas for improvement on the YouTube channel were discussed: + - Updating the main banner + - Revising the "Sovereign infrastructure that Scales" messaging + - Updating playlists and video content + - Improving thumbnails and descriptions with calls to action + +- Denis Lelic offered support for creating graphics and suggested reaching out to the community for additional design assistance + +- The group discussed adding branded intro/outro screens to community-created content when uploading to the Akash Network channel + +- Robert Del Rey presented three thumbnail design concepts: + - Design featuring large text and imagery + - Design including larger logos + - Design aligning with current YouTube trends, featuring a large host image and short title + +- Denis Lelic suggested collaborating on designs to ensure brand consistency across platforms + +- The group discussed creating short-form content (1-2 minute videos) from existing long-form content for distribution on YouTube and other platforms + +- Tyler Wright clarified the difference between the community contributions page on the website and the more formal Akash Network YouTube channel + +- The team agreed to move the next meeting to one hour earlier + +## Action Items + +- Robert Del Rey to compile a list of design assets needed for Denis Lelic's review + +- Robert Del Rey to send an announcement in the YouTube chat about future meetings + +- Robert Del Rey to create a short video on "How to deploy on Akash" for next week's review + +- Robert Del Rey to work on descriptions for videos, coordinating with Zack for specific content + +- Tyler Wright to provide access to steering committee videos for Robert Del Rey + +- Team to consider creating additional short-form content on topics like becoming a validator, Akash Accelerate highlights, and how to contribute to the project + +- Discuss updating the community contributions page on the website during the Website Working Group meeting + +- Robert Del Rey to check YouTube access and notify Tyler Wright of any issues + +## Transcript \ No newline at end of file diff --git a/wg-Akash-youtube/meetings/003-2024-08-06 b/wg-Akash-youtube/meetings/003-2024-08-06 new file mode 100644 index 00000000..174b17c5 --- /dev/null +++ b/wg-Akash-youtube/meetings/003-2024-08-06 @@ -0,0 +1,74 @@ +Here are the meeting notes in the requested format: + +# Akash Network - Akash Youtube Working Group (WG) - Meeting #3 + +## Agenda +- Review Akash YouTube plan document +- Discuss video descriptions and titles +- Update YouTube video playlists and add sections +- Community-generated content +- Shorts content +- Multi-language content + +## Meeting Details +- Date: Tuesday, August 06, 2024 +- Time: 08:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + +## Participants +- Tyler Wright +- Denis Lelic +- Robert Del Rey +- Fenil Modi +- Minh Tâm Nguyễn +- Rodri R +- B S + +## Meeting Notes + +### YouTube Channel and Content Plans +- Robert Del Rey provided an update on gaining access to the Akash YouTube channel and presented the Akash YouTube plan documents. He made changes to the channel, focusing on reorganization. +- Robert Del Rey highlighted updates to descriptions and the need for consistent branding across videos, including adding timestamps and thumbnails for easier navigation. + +### Enhancing Video Descriptions and Titles +- Robert Del Rey shared ideas for improving YouTube video descriptions to include more detailed content and ensure consistency. The descriptions are designed to lead viewers to relevant Akash content. +- Tyler Wright suggested adding deployment links in video descriptions for easier access to the Akash Console. + +### Playlists and Channel Organization +- New playlists were created: + - *Deployments and Tutorials* - contains tutorials like "Running the BLM on Akash." + - *Akash Events* - for event recordings like *Akash Accelerate* and *Decentral 2022*. + - *Community Contributions* - includes videos by community members like Shimpa. +- Tyler Wright recommended conducting an audit of older videos to decide which ones to keep or remove, possibly archiving outdated videos. +- Rodri R and Tyler Wright agreed that community-generated videos that meet the channel's quality and branding standards could be included in the main Akash YouTube channel. + +### Use of Disclaimers +- Tyler Wright and Robert Del Rey discussed the appropriateness of disclaimers. +- They agreed that educational content on Akash tools should not carry speculative disclaimers (e.g., NFA - Not Financial Advice), as they may deter new users. + +### Community Contributions and Feature Options +- Robert Del Rey proposed three options for featuring community content: + 1. Upload videos directly to the Akash YouTube channel. + 2. Feature community-created videos in a playlist. + 3. Add feature channels, highlighting contributors like Europlots. +- Rodri R and Tyler Wright supported maintaining a high standard for community content featured on the channel. + +### Short-form Content and Future Additions +- Robert Del Rey mentioned the creation of short-form content (YouTube Shorts) and promised to present sample shorts in the next meeting. +- The need for multilingual content was raised, with Rodri R supporting the idea of creating language-specific playlists rather than separate channels. + + +## Action Items + +- Robert to continue refining video descriptions and applying timestamps to existing videos +- Group to audit existing videos for potential archiving or removal +- Robert to create sample YouTube Shorts for review in the next meeting +- Tyler to reach out to community content creators (e.g., Shimpa) about featuring their content +- Tyler to initiate discussions on including community-generated content with proper credits and branding. +- Robert to research best practices for multi-language content organization on YouTube +- Group to consider creating an Akash channel on Omniflix TV +- Robert to update the Akash YouTube planning document with meeting outcomes +- All participants to contribute ideas for new video content in the Discord channel + +## Transcript \ No newline at end of file From 84f637fb1a71a0e4f8a7c87a1a0267743d5df3ec Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 10 Sep 2024 14:27:31 +0000 Subject: [PATCH 129/138] rename wg-akash-youtube meeting files to add ".md" (#677) rename wg-akash-youtube files --- wg-Akash-youtube/meetings/{001-2024-07-23 => 001-2024-07-23.md} | 0 wg-Akash-youtube/meetings/{002-2024-07-30 => 002-2024-07-30.md} | 0 wg-Akash-youtube/meetings/{003-2024-08-06 => 003-2024-08-06.md} | 0 3 files changed, 0 insertions(+), 0 deletions(-) rename wg-Akash-youtube/meetings/{001-2024-07-23 => 001-2024-07-23.md} (100%) rename wg-Akash-youtube/meetings/{002-2024-07-30 => 002-2024-07-30.md} (100%) rename wg-Akash-youtube/meetings/{003-2024-08-06 => 003-2024-08-06.md} (100%) diff --git a/wg-Akash-youtube/meetings/001-2024-07-23 b/wg-Akash-youtube/meetings/001-2024-07-23.md similarity index 100% rename from wg-Akash-youtube/meetings/001-2024-07-23 rename to wg-Akash-youtube/meetings/001-2024-07-23.md diff --git a/wg-Akash-youtube/meetings/002-2024-07-30 b/wg-Akash-youtube/meetings/002-2024-07-30.md similarity index 100% rename from wg-Akash-youtube/meetings/002-2024-07-30 rename to wg-Akash-youtube/meetings/002-2024-07-30.md diff --git a/wg-Akash-youtube/meetings/003-2024-08-06 b/wg-Akash-youtube/meetings/003-2024-08-06.md similarity index 100% rename from wg-Akash-youtube/meetings/003-2024-08-06 rename to wg-Akash-youtube/meetings/003-2024-08-06.md From 6dfdea036a45ca5d32ffb450d7f92e65210a7fa2 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 16 Sep 2024 01:52:29 +0000 Subject: [PATCH 130/138] Create meeting notes for wg-website 32 (#657) --- wg-akash-website/meetings/032-2024-07-25.md | 188 ++++++++++++++++++++ 1 file changed, 188 insertions(+) create mode 100644 wg-akash-website/meetings/032-2024-07-25.md diff --git a/wg-akash-website/meetings/032-2024-07-25.md b/wg-akash-website/meetings/032-2024-07-25.md new file mode 100644 index 00000000..fe65f0cf --- /dev/null +++ b/wg-akash-website/meetings/032-2024-07-25.md @@ -0,0 +1,188 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #32 + +## Agenda +- Chat API Integration +- Navigation Redesign +- Pricing Page Improvement +- Documentation and Blog Updates +- Open Discussion + +## Meeting Details +- Date: Thursday, July 25, 2024 +- Time: 6:30 AM PT (Pacific Time) +- [Recording](https://j3ixq4a45f2dpivp7gmzyecplzctrglme5j4ea2dfvbvad2dsfma.arweave.net/TtF4cBzpdDeir_mZnBBPXkU4mWwnU8IDQy1DUA9DkVg) +- [Transcript](#Transcript) + +## Participants +- B S +- Denis Lelic +- Hiroyuki Kumazawa +- James Kano +- Kumar +- Robert Del Rey +- Tyler Wright + +## Meeting Notes +- **Introduction and Welcome:** + - Tyler Wright opened the meeting, highlighting the purpose of the working group. + - Emphasized the open-source nature of the Akash website and encouraged community contributions. + +- **Chat API Integration:** + - **Denis Lelic:** Announced the launch of the Chat API and suggested integrating it into the website. + - Shared a link to the Chat API and created Issue #316 for adding it to the ecosystem showcase page. + - Suggested assigning the task to Hiroyuki Kumazawa (Hiro). + - The task involves creating a new tile with a link, graphic, and description as provided in the issue. + +- **Navigation Redesign:** + - **Denis Lelic:** Discussed improving the main and secondary navigation to avoid overcrowding and enhance user experience. + - Suggested redesigning the menu to add new items without cluttering. + - Shared two issues: one for the main navigation and another for secondary navigation. + - Proposed dropdown menus for subpages to improve mobile experience and make the tooling section more prominent. + - Assigned the redesign task to Piyush, who has experience with the website. + +- **Pricing Page Improvement:** + - **Denis Lelic:** Discussed the need to improve the visibility and usability of the pricing page. + - Suggested adding a new menu item called "Pricing" to make it more accessible. + - Proposed adding GPU pricing and a user pricing calculator, as well as a provider earn calculator. + - Mentioned assigning this task to Hiroyuki Kumazawa (Hiro) once updates are posted. + +- **Documentation and Blog Updates:** + - **Tyler Wright:** Encouraged contributions to documentation and mentioned coordinating with Robert Del Rey on adding videos to documentation. + - **B S:** Announced working on a SIG/WG monthly recap blog, delayed due to internet issues but will draft over the weekend. + - **Tyler Wright:** Suggested starting with a monthly recap blog and potentially moving to a weekly recap based on interest. + +- **Open Discussion:** + - No additional topics were raised by attendees. + - **Denis Lelic:** Wrapped up the meeting and confirmed the next meeting in two weeks. + +**Action Items:** +1. **Hiroyuki Kumazawa:** + - Implement Issue #316 by adding the Chat API to the ecosystem showcase page. + - Work on improving the pricing page, including adding GPU pricing, a user pricing calculator, and a provider earn calculator. + +2. **Piyush:** + - Work on the navigation redesign, ensuring the new design is aligned with the discussed improvements. + - Update the events page with the latest information. + +3. **Denis Lelic:** + - Monitor and coordinate the implementation of the Chat API integration and navigation redesign. + - Finalize details regarding item listing on subpages and the new horizontal tab for development items. + - Post updates and tag Hiroyuki Kumazawa on the pricing page improvement issue. + +4. **Tyler Wright:** + - Follow up on integrating YouTube content into the website. + - Coordinate with the core team on updating the events page. + - Guide B S on creating the SIG/WG monthly recap blog. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the working group for the Akash website. Today is July 25th 2024 during this working group for the cost website the group. Goes over any issues and talks about anything related to the Akash website as well as the Akash documentation, which is now under the new revamped website that came into fruition at the end of 2023. + +Tyler Wright: this is an open source effort where anybody from the community can contribute to continuing to improve the Akash website. Obviously, it's a hub for all things related to how to use the product different ways to integrate how to contribute Etc. Obviously everything in Akash is open source. So as much information is made transparent as possible is always So again always happy to have more contributions if anybody wants to get involved. There's a number of issues inside the website repo as well as if there's anything that you see that maybe needs to be improved we can talk about it during these meetings as well as again creating issue and we could talk about an async in between meetings. + +Tyler Wright: Denis usually runs these meetings and I support him as well as Oxbow Panther a pieush who helps to maintain the website. he and his team human HQ did the website revamp as a part of some community pool funding on their secured in late 2023 and again have delivered the website that you see today. + +Tyler Wright: I know that Pierce is currently traveling to a hackathon so he will be unavailable today. But I'll kick it over to Denis to talk about any issues. I know that hero on the call has been helping a lot with various issues. And so I just want to see if there's any questions or concerns that he has and then I know that Robert has been supporting. There's another working group that came out of sync design called the working group for the Akash YouTube where the effort is to revamp and improve the Akash YouTube channel. That's a part of that. I know that there's going to be video content that's added to the YouTube from various community members and it might be good to think about adding some of that video content to places like the documentation or other parts of the website as well. So + +Tyler Wright: Just something to keep it back in mind that we don't necessarily have to talk about today. With that said I'll kick it over to Denis to get us started with any topics. He wants to discuss or any open issues. + +Denis Lelic: Bye. And welcome everybody to today's meeting one thing. I want to mention and as some of you probably noticed a couple of days ago chat API was launched. I'm just gonna share a link here in the chat section. and yesterday I was just thinking, how can we + +Denis Lelic: Add that to the website, so it's reachable through the website as well. So it's not a page living on its own. I cannot isolated island and one of the easiest ways would probably be just to create a new child and + +Denis Lelic: ecosystem showcase page Sharing link again to this page as you see we have Akash chat there already and as the Excel on so I just created. + +Denis Lelic: an issue again sharing care and chat section + +Denis Lelic: So it's issue 316 and so the task would be to add a cost chat API to the ecosystem page. So basically adding the description X. I've provided here and the issue along with the graphic. I know some community members were involved in a lot of discussions and they showed interest To taking some of the issues taking tackling some of the tasks. So I suggest I just assigned this one to Hero so here I'm just gonna + +Denis Lelic: tag you to this issue. + +00:05:00 + +Denis Lelic: Okay, So hero I've tagged you in this issue. It's kind of like a low hanging fruit Easy task to do. Basically, you just have to create a new tile provide a link provide a graphic and at the text there so everything. + +Denis Lelic: It's already in the issues here under the comment section. So yeah, the other thing would be where? Could we add these? goals different kind of tools to the main nav bar, so I'm always worried when we have to add things to The Nail part because I don't want Things to get crowded it's not really nice experience where you have to go through a bunch of items to find something. So a while ago, I introduced to redesign the whole menu experience just to give us this additional canvas where we could add new items without creating the + +Denis Lelic: this overcrowded experience. So I'm just going to share this issue again here. So as you see you got to share my screen. + +Denis Lelic: So yeah, we have two issues here one is for the main navigation and the other one is secondary navigation, which is + +Denis Lelic: positioned + +Denis Lelic: vertically on each of these Pages subpages we have and it's a kind of a clumsy experience on the mobile as well. So I suggested just to drop down menus for each of these items and that will give us some space to work with new items. And as I said, we're missing the tooling section, that could be much more prominent. It's kind of Now hidden. Here in the Showcase section. So yeah, that's something I just had. to this issue and + +Denis Lelic: probably in the next couple of days. I would like to start off with this one. I would assign this one because it's kind of a bigger thing to do a bigger tasks to designed it to peers because he has experience. With the website and basically he put together the existing website and I think it would be much easier for him to tackle this one. + +Denis Lelic: Yeah time. + +Tyler Wright: David design that you have is that the design in the issue that's already. finalized or any and pieces has implemented. Is that the Pain point right now, okay. + +Denis Lelic: Yeah, the design is pretty much. there we just have to align on the + +Denis Lelic: On some of the items, let me see we talked about it in the previous meeting. + +Denis Lelic: Yeah, Pierce was just saying what happens if we + +Denis Lelic: only have the dropdowns without the secondary nav on the sub pages, but that's just a matter of days. I've think. Avoiding additional Clicks in the main navbar and searching through the images. We could just list them on each of the sub pages. So we would create a new horizontal lab. So for example when you click on Development you would already have different items stated here without necessity of going through the drop-down again. But yeah, as I said, I just have to figure out what happens with. + +00:10:00 + +Denis Lelic: Some of the items that we're currently trying to resurface such as tooling and pricing and so on and so on regarding the pricing, let me see. + +Denis Lelic: I think pricing. + +Denis Lelic: Okay, can't find the pricing. if anyone sees + +Denis Lelic: pricing + +Denis Lelic: Okay, improve pricing. + +Denis Lelic: Okay, this is the next issue. I'm going to work on so we have to resurfers the pricing page some of the community members and let's just communion members, but just users that were scrolling through the website found it hard to find the pricing and I agree. So currently it lives here + +Denis Lelic: so you have to go Network about and then go to the pricing and what I'm suggesting here is just to have additional menu item called pricing and we have to mention gpus as well. Because it's always a Hot Topic and then we would have GPU pricing here or some sort of a tab as well. not a tap like a switch where users could switch between GPU pricing and user pricing calculator and there's one additional item and that's like It's called provider earn calculator. So we're just offer one unified experience where users could either. what are the offerings for gpus? What's the cost per usage? + +Denis Lelic: and if some of the users want to provide compute they could also just hit this additional third item which would provide an estimate for basically How much would you earn if you provide computer Akash Network? + +Denis Lelic: So I already worked on this thing a little bit. I just didn't have time unfortunately to put it together and share here. But I see hero was already active in the comment section. So when I post an update hero, I'm just gonna tell you if you're willing to take this issue as well. + +Denis Lelic: anything else you guys want to discuss? + +Tyler Wright: Don't feel obliged, but I see a couple of folks that haven't been at the last couple of meetings and if they wanted to again, this is a open source group. There's usually about + +Tyler Wright: Anywhere from five to ten participants that help out with the website. This is a major again marketing point of major marketing tool. It's just like a cool for new and existing users to interact with Akash Network find out share information access console Etc. So again, this is a very important touch point and we're always looking for more contributions. I think our issues right now are just at the scale of what we can handle but if we can get more folks that can help out with implementation of design implementation of how about with ux, that would be greatly appreciated and there are akt rewards those that want to give their time to help. So again, I just want to make that clear to some folks maybe having been + +Tyler Wright: Year as a recently and if they want to introduce themselves either in chats or on mic, don't feel obliged, but I'm happy to have you. And I also did just add an issue around the events page and I'm going to coordinate with a member of the core team on the event side because I know there's a number of other events. We're going to in the fall and I just want to make sure that page is up to date. + +00:15:00 + +Denis Lelic: yeah Green Tyler regarding the events page. I talked to pierce couple of days ago. So I just have to create. an issue to add + +Denis Lelic: a couple of events that are missing currently. And anyone who's joined for the first time today? Feel free to chime in or you can always join on our Discord. We have a channel there going on and you can always join the discussions here under the issues. So akashed akashment for GitHub and the repo website. + +Denis Lelic: Okay. cool + +Denis Lelic: Yeah, so I think from my side I pretty much covered everything for today. Unfortunately, I didn't find time to make some progress on a couple of issues. I was planning to I got caught up in some other work, but I'll get back to it as soon as possible. And as I said I'm tagging hiroyuki Echo some of these issues. + +Denis Lelic: you guys agree we could wrap it up for today. Unless you want to talk about something else. + +Tyler Wright: No again, I'll coordinate with Robert about some of the videos. I think we should add to documentation. If anybody sees anything in documentation, I think needs to be upgraded or if anybody wants to participate in writing new documentation updating documentation again, feel free to reach out to me or Denis and make some suggestions on where you would want to add value. But yeah, again there's a number of issues open here and we'll continue to talk about them. + +Tyler Wright: Yes, that's a great call out b s that's something that we've talked about a cigs as working group monthly recap. I actually heard from a couple of people recently that I've reached out to me and thought it'd be cool to have a weekly recap. I think maybe we start with monthly and see where we go from there. But I know there's a number of interested parties that want to keep up to date on the six and working groups. So yes, the way that will get added is via blog. So you'll make a PR and you can follow the instructions in the repeat file in the website repo, but we can talk about that offline. But yeah that is in the right place but much appreciate you and those efforts. + +Denis Lelic: Thanks that. + +Denis Lelic: Okay, so Thanks everyone for joining today. I think we'll see each other again in two weeks. but hopefully you will Talk Sooner either on GitHub or Discord. Have a good day. + +Tyler Wright: Thank you. + +Denis Lelic: Thank you. Bye. + +Robert Del Rey: Thanks. Stay safe everybody. Bye. + +James Kano: Thank you. + +Meeting ended after 00:19:17 👋 From 060a8a1e24b31eb2c1539014007cb00cc7cb3614 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 16 Sep 2024 01:58:23 +0000 Subject: [PATCH 131/138] Create meeting notes for wg-website #33 (#662) * Create meeting notes for wg-website #33 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 033-2024-08-08.md added transcript Chore: Add recording link Signed-off-by: Drinkwater * wg-akash-website Update 033-2024-08-08.md add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-akash-website/meetings/033-2024-08-08.md | 324 ++++++++++++++++++++ 1 file changed, 324 insertions(+) create mode 100644 wg-akash-website/meetings/033-2024-08-08.md diff --git a/wg-akash-website/meetings/033-2024-08-08.md b/wg-akash-website/meetings/033-2024-08-08.md new file mode 100644 index 00000000..77b02cff --- /dev/null +++ b/wg-akash-website/meetings/033-2024-08-08.md @@ -0,0 +1,324 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #33 + +## Agenda +- Review of ongoing issues and updates +- Main menu navigation redesign +- Pricing page improvements +- Blog writer filter functionality +- Case studies page +- Integration content for Akash network +- Open Discussion + +## Meeting Details +- Date: Friday, August 08, 2024 +- Time: 6:30 AM PT (Pacific Time) +- [Recording](https://liyj2hy26ggvtqigr7b753rkz3eo7aigtfbxwzn7cw5yabkrdtvq.arweave.net/WjCdHxrxjVnBBo_D_u4qzsjvgQaZQ3tlvxW7gAVRHOs) +- [Transcript](#Transcript) + +## Participants +- B S +- boldpanther +- David Mikulecky +- Denis Lelic +- Hiroyuki's Notetaker +- oo o +- Robert Del Rey +- shiny dev +- Tyler Wright + +## Meeting Notes +- **Review of Ongoing Issues and Updates:** + - Denis Lelic provided a summary of the status of ongoing issues and updates from previous meetings. The focus was on current issues and their progress. + +- **Main Menu Navigation Redesign:** + - Denis Lelic discussed the main menu navigation redesign. He shared Figma drawings for both the main and mobile versions of the navigation. + - Piyush has been assigned to work on this redesign. The new navigation aims to enhance user experience across the website. + +- **Pricing Page Improvements:** + - Hiro is working on improving the pricing page, which will include features such as GPU pricing, usage pricing calculator, and a provider earnings calculator. + - The updated pricing page will allow users to see GPU stats, use sliders for pricing calculations, and compare prices with Amazon, Google, and Microsoft. + - Progress on this update is anticipated in future meetings. + +- **Blog Writer Filter Functionality:** + - The draft for adding writer filter functionality to the Akash blog is awaiting feedback from Zach. This functionality is intended to enhance content management and user experience on the blog. + +- **Case Studies Page:** + - A draft for a new case studies page was shared. This page will include tiles with basic information and calls to action for detailed case studies. + - Feedback from Zach is pending. + - Tyler Wright is expected to provide content for this page, including information on how projects can integrate with the Akash network. + +- **Integration Content for Akash Network:** + - Keto is responsible for providing content and relevant links for integration into the Akash case studies page. + - A draft will be prepared to include this content and see how it fits into the case studies page. + +- **Open Discussion:** + - **Community Involvement:** + - Attendees were encouraged to join Discord and review the calendar of working groups and special interest groups. + - Tyler Wright offered additional information on these groups and their activities. + - **Legal Protections:** + - David Mikulecky raised concerns about protecting Akash from issues like phishing, trademark concerns, and user-generated content problems. + - He proposed a separate discussion to draft terms of use and strategies for brand protection. A 15-20 minute discussion was suggested. + - **Process for Handling PRs:** + - The process for reviewing PRs on GitHub was explained. This includes security checks to prevent malicious content from being merged. + - **Bounty Boards and Blog Drafts:** + - B S inquired about where to upload blog drafts for review and noted discrepancies between GitHub and Akash site bounty boards. + - It was suggested to contact Zach on Discord for draft review. + - A community contributions page is being developed to host blog content. Markdown is supported for blog drafts. + - An issue should be created to address syncing between GitHub and the Akash site bounty boards. + - **Licensing and PR Requirements:** + - Tyler Wright noted that recent updates require PRs to be signed by contributors. He suggested updating repository files to guide non-developers on how to sign their commits. + - The documentation working group has merged with the website working group. Issues with documentation should be reported via the website repo with a "documentation" label. + +## Action Items +- **David Mikulecky:** + - Schedule and lead a 15-20 minute discussion on legal protections and terms of use. + - Review the provided link and contact Tyler or Denis for further discussions. +- **Tyler Wright:** + - Provide additional details on working groups and special interest groups. + - Create an issue to address the syncing of bounty boards between GitHub and the Akash site. + - Update repository files to clarify the PR signing process for contributors. +- **Denis Lelic:** + - Review the shared issue and arrange a separate meeting if necessary. + - Follow up on the development of the community contributions page for hosting blog content. +- **B S:** + - Share blog drafts with Zach on Discord for review. + - Monitor updates regarding the community contributions page and bounty board synchronization. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Denis Lelic: Everybody and welcome to today's working group meeting for a college website. So as usual, I'm just gonna get us started with. + +Denis Lelic: A passionate or website repo and the issues that we usually go through. so let me know if you can see my GitHub. + +Denis Lelic: Let's screen. So I see what's going on. I get it's good. Yeah, so a couple of fishes we mentioned in our last sessions. + +Denis Lelic: Maybe we start up. With the main menu nav redesign, so it's for those of you that are familiar with it. You're probably seeing this in our previous sessions and for all the newcomers. I'm just going to share the issue here in the chat section. So please from I have a Sigma drawing for basically all the navigation so as you'll see stated here to + +Denis Lelic: to navigations one would be a main nav, and another one would be the Horizontal and of course mobile version as well. So I got them all drawn and I think peers here said he would be willing to take this issue. So I'll share figma drawings with you. So yeah, this is one of the issues that it's kind of like been bugging me for a while and I think it's gonna really improve our user experience and across the whole website another issue we have I think Hiro working on it. + +boldpanther: Rising + +Denis Lelic: That's improve pricing page visibility and experience. So I'm just gonna share it again in + +Denis Lelic: In the chat section if you want to read through. So we started off this was the first draft we had some discussions around modules in these pages and I provided all of the pigment drawings to hero and I believe he's already started working on it. So the new pricing experience would take the users into three different ways one would be + +Denis Lelic: the display GPO pricing usage pricing calculator and provider earn calculator so with Gpus it would basically list all available gpus and some stats around it and a call to action where users are able to rent them then we have another one. That's the usage pricing calculator. So if user wants to have something Beyond gpus they can play around with these sliders here and They would How much would it To have these resources rented and we also price compare with Amazon Google and Microsoft. + +Denis Lelic: And the third one will be if a user wants to provide compute where again they could use these sliders and have a look how much would they earn if they decide to provide compute on the network? So yeah Heroes already working on it. Hopefully we'll see some progress soon maybe in one of our next sessions. + +Denis Lelic: from the previous meetings I think all of the events were updated by Pierre. So thank you for that. I think that was already closed. And there are some. + +Denis Lelic: Some issues that we need. Input from other community members or core team members one would be to implement writer filter functionality for Akash blog, I think. + +00:05:00 + +Denis Lelic: Let me Yeah Pierce and here basically HD human HQ provided a draft for it and where waiting just for Zach's. thoughts + +Denis Lelic: and basically feedback for this draft here. There is another one. + +Denis Lelic: I'm not this one. Okay studies. So we have a draft for case studies here. + +Denis Lelic: So here it is. We would add a page. we would showcase case studies so we would have A tile with some basic information and a call to action where we would have a detailed page and I've listed some possible. Blog posts that could serve as a case study as well. So with waiting for the Zac to provide feedback on this one. and I think + +Denis Lelic: this issue that was created by It could be part of the case study as well. So Tyler's page for how projects can integrate in a caution network with relevant links to Akashi. So yeah, I think Keto said if you can provide the contents and even I said if you can provide a list of these relevant things so we can maybe prepare a draft see how this could live in the Akash case studies page. + +Denis Lelic: I think that's it from the issues that we've kind of touched in the last week or so and as usual I would Leave the second part of this session just for open discussions. If you want to talk about anything if you found any bugs, if you think we should create a new issue add something take away something so feel free to join the discussion + +Denis Lelic: Yeah, thanks for Happy to hear you happy to have you here. We have a lot of either. Working groups or special interest groups. So I suggest if you're not already there to join our Discord and there's also + +Denis Lelic: community. + +Denis Lelic: I'll share just the calendar with you so you can have a look at other movies that are happening. So here it is in the chat section. So if you scroll down a little bit, you're gonna see all the idea of working groups or special interest groups that are happening from now on. But yeah, we have Tyler on our call and He basically knows everything that's going on with these groups. So he'll provide more information. Go ahead type. + +00:10:00 + +David Mikulecky: Yeah, no, that's helpful. I opened the link. I'll review the sessions and I have a DM Tyler with a questions. + +David Mikulecky: Yeah, again I'll love your perspective as to where can I plug in? I'm product lawyer by training so blend of try and crypto lawyer. So, I understand. This is an open source where I'm coming from was more like, okay, how do you guys think about If you allow user generated content how you think about, people meddling with the features of the side is any tools to protect from that inserting links that can, lead to some full design. So that's what I'm sort of thinking how. You guys may want to the protection of akashi's right? But let me read the link. And take it from there. Sounds good. + +Denis Lelic: that sounds good. And thanks Tyler for providing some information. Yeah, all Panther. Go ahead. + +boldpanther: Yeah, thanks for joining David. So I love your perspective on how we can product Akash brand the layers one question that you asked how we protect. + +boldpanther: How we protect the Akash from contributors who may insert some fishing links to the car, So as the project is open source on GitHub. So whatever the PR's are being created on the GitHub repo they are being revealed by the casting as well as contributors before merging them to the Akash net website. There is a complete process which we follow so whatever the user is basically contributing to the cost was they have to request on the issues that they want to contribute and then when they create a PR so we go through and total review process where we see if the coding breakfast are being followed properly and also the links are the information that is there is a hundred percent correct and there are no official links and all so yeah, this is how we protect I + +boldpanther: the attacks + +David Mikulecky: okay, that's + +boldpanther: I hope that answers your question. + +David Mikulecky: Yeah fishing is you want one of the concerns? I don't want to take much of your time. Maybe, spending just 15 minutes with somebody who's interested chatting about how to think about creating a sort of contract with any user who accesses the side and Akash, maybe helpful, right? It's not just fishing links. It can be how to protect + +David Mikulecky: I probably trademark silently. I don't know if somebody were to copy it and use it, for their own business. I don't know if that's a concern right but you have trademark issues. It can be content. That's inappropriate that you may want to eliminate those are the types of protections that I'm referring to right and the way to do it you can easily, insert terms of use that create binding contract between Akash and any user who accesses the website, right? + +David Mikulecky: If there are different modes how the user can accept that contract but basically just Akash has a privacy policy that sort of one type of product, protection. The other is So that's the terms of uses the contract that I'm referring to between Akash and the users who use the website, right and there are whole slew of things that you Akash may want to protect. But again, maybe it's for just the 10 minutes discussing with a subset of this group. I don't want to multiply This and this is probably not of your priority list anyway, + +boldpanther: Hey here,… + +Denis Lelic: yeah, I've + +boldpanther: so you can definitely reach out to Tyler who is basically managing all the things related to Akash and also Denis as well who looks after all the design things and I think that would give you a more. High level overview of how the cautious working right? Thank + +David Mikulecky: Sounds good. + +Denis Lelic: yeah, there is this issue of copycats and + +00:15:00 + +Denis Lelic: someone trying to manipulate akashes a brand but it's often something that either the code base is out of our reach. So it's not happening in Akash Network repost. So it's somewhere external and maybe just + +Denis Lelic: maybe we would need someone if that happens just to reach out and + +Denis Lelic: basically informed and to take it down because they're like How to call that thing, but I guess it's against a lot to a copycat someone else's Brian even though it's open source. + +David Mikulecky: Yeah, it depends on a protocol right how do you want to protect it? Do you want to protect it? That's one thing the other angle could be right somebody claims that something that's posted on akash's website can impede someone else's rights and they want to sue the protocol the founders whoever right the terms of use will give you the right to defend yourself the protocol and say hey, I'm going to contract in terms of use you agreed that let's say, the binding law is love of New York or the venue is whatever else then text us. + +Denis Lelic: No, it's… + +David Mikulecky: Right … + +Denis Lelic: how helpful. + +David Mikulecky: we disclaimed,… + +Denis Lelic: I think it's necessary conversation. + +David Mikulecky: our obligations. + +Denis Lelic: Maybe yeah as we thought a couple of minutes ago. + +David Mikulecky: This is open source protocol. Everything is no guarantees. + +Denis Lelic: You can DM me in Tyler here as well so we can find or… + +David Mikulecky: Sue if you have to but you're gonna lose that type of protection I'm talking about right and… + +Denis Lelic: put together a group where we can. + +David Mikulecky: you can make it you can bake that in the terms of use. + +Denis Lelic: Form a better discussion just around that topic and… + +David Mikulecky: So again, + +Denis Lelic: have dedicated time for it. + +David Mikulecky: just something to think about it's very easy to do as long as what you want to achieve how you want to protect the brand and how you want to sort of defend how you think about defenses if somebody comes in right? And so I know this is very boring legal talk but I just + +David Mikulecky: Sounds good. And what I'm thinking about 20 minutes is all I need to walk you guys through that… + +Denis Lelic: Yeah, that sounds good. Okay. + +David Mikulecky: why to do it and then get some additional information as to… + +Denis Lelic: back to a couple of these issues we talked about and… + +David Mikulecky: which way you're taking the protocol and… + +Denis Lelic: yeah, we said + +David Mikulecky: without the needs. What is it that you're really need and… + +Denis Lelic: We would leave it for open discussion… + +David Mikulecky: do we have the right parties right at the table good. + +Denis Lelic: if anyone has anything. + +David Mikulecky: Does anybody need to chime in so 20 minutes is probably all we need and… + +Denis Lelic: to talk about either the issues that are already open or… + +David Mikulecky: if there is interest happy to start Drafting and… + +Denis Lelic: if you think we need to + +David Mikulecky: crafting based on akash's needs and… + +Denis Lelic: Create a new one and… + +David Mikulecky: then set up additional 15 20 minutes to walk you through the proposed document before it. + +Denis Lelic: on So please feel free to chime in. + +David Mikulecky: It's put to the community. So that's how I'm envisioning it. But I have Tyler I've Denis and… + +boldpanther: Dennis I've shared one issue in the chat + +David Mikulecky: we can take it from there. + +Denis Lelic: Yes. + +Denis Lelic: I'll go through it. Let me see. + +Denis Lelic: Okay, but I don't see a PR here. + +boldpanther: It's the last one in the issues. the + +Denis Lelic: Okay, maybe I'll go through it and I can talk. In a separate meeting. I'll just through DMs. + +boldpanther: equation + +Denis Lelic: Okay, cool, so yes has a two questions I agreed to writing a sick working group meetings Recap blog I did enough for July meetings and I'm keeping up with August so far. Is there somewhere to upload to perhaps grab some GitHub for review and the devs was still getting my sea legs, but while wrapping the blog and others that there was a GitHub Bounty port. But that isn't replicated on outside bounty board these separate boundaries boards, or just need to be synced for the question. Number one. I think that's something you can talk with Zach core team on Discord and just share. + +00:20:00 + +Denis Lelic: Your writings with him, so he'll have a look and get back to you. And for the Bounty boards. Let's see. + +Denis Lelic: It says it's not To community. Okay, and this one? List of bodies. Yeah, they're not populated here. + +Denis Lelic: And I'm not sure the first link that I did something wrong. it's still not working. + +Denis Lelic: Yeah, Robert, go ahead. + +Denis Lelic: Thanks. Thanks, I believe. + +Tyler Wright: B s i don't look at this bounty links because that's an issue soft power over there. Maybe we should create an issue for that if it's not already one created and I can follow up there and then I've already shared. the initial draft so copy is a question more about the formatting BS of how to create a new blog. + +Denis Lelic: Regarding the bounties. I see there in this issue that you've posted this. we got new message coming up from here. So yes, if the draft is okay. I'm just wondering where to upload it. It looks like markdown is supported. Yes. It's supported and there's one of the issues that we created a while ago and So, let me see. I'll just share it here and it's chat section. So we have this community contributions page and we create an issue where users or community members could write their own blogs there at the moment. You can only set up a link and have the content somewhere externally, but when this issue is + +Denis Lelic: we've done an implemented this could live on the website as well. So yeah. It's in the making so hopefully soon. trademark + +Denis Lelic: Okay, anything else you guys want to talk about? + +Denis Lelic: Yes, I go ahead. + +Tyler Wright: Star I pulled the last minute. Yeah, again, there'll be a number of new issues that get added. So please take a look. I know there's a number of new contribute contributors here today one thing and this might be more of a question for pH. I know we put in update the licensing pretty recently. I know for other repos now. It's a requirement for PRS to be signed by the contributor. I'm not sure if you've seen anything used with any of the contribution coming into the website, but if so, maybe we want to make it update the repeat file just to make it easier for people that may not be as well versed in GitHub to know how to sign their commits. So just want to + +boldpanther: They posture. + +Denis Lelic: things that okay. + +Denis Lelic: We're still have time, but I guess we covered a lot in this short period of time. So, thanks again. for joining we'll see each other and in two weeks, I think so. + +00:25:00 + +Denis Lelic: Keep an eye on the Discord on the channel working group for the website and you can always ask questions Share your thoughts share your issues or whatever. You think it's worth sharing. And you can always if you need any support from design perspective. Yes. I see someone's hand went up. So please go ahead. + +oo o: Yeah. I'm assuming it's my hand you are talking about. what you call it the doume Is it working group or it is wggo Sig? Yeah, what is the meeting? I know it's now once a quarter. When is it? + +Denis Lelic: We merged the working group for the documentation with the working group for a car website. So we covered everything that is website related and as you'll see now when we redesigned the website a cash docs are basically part of the website. That's why we're had these meetings combined. + +oo o: Website, okay. + +oo o: that's what okay. Thank you. + +Denis Lelic: That's always. + +Tyler Wright: So yeah again, feel free if you got any questions or any comments right to documentation. This is the meeting to talk about it. So now if you see any issues and documentation again, you can create an issue with a website repo and then just add a tall or a label for documentation, but we can talk about any of those items here and I'd much appreciate your contributions that you've already made on the documentation side. + +Denis Lelic: things like so we're going to wrap it up or today, and we'll see each other in two weeks. So thanks again for Have a good day. Bye. + +boldpanther: Thank you. Have a good day. Bye. + +oo o: live long and prosper + +David Mikulecky: Thanks guys. + +Robert Del Rey: Stay safe guys. Bye. + +Meeting ended after 00:29:47 👋 From 1c338975e1f3d2937af6214c013d94415617fb9c Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 16 Sep 2024 02:00:39 +0000 Subject: [PATCH 132/138] Create meeting notes for wg-zealy #13 (#661) * Create meeting notes for wg-zealy #13 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 013-2024-08-12.md added transcript Chore: Add recording link Signed-off-by: Drinkwater * wg-zealy Update 013-2024-08-12.md add video recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-zealy/meetings/013-2024-08-12.md | 311 ++++++++++++++++++++++++++++ 1 file changed, 311 insertions(+) create mode 100644 wg-zealy/meetings/013-2024-08-12.md diff --git a/wg-zealy/meetings/013-2024-08-12.md b/wg-zealy/meetings/013-2024-08-12.md new file mode 100644 index 00000000..c59ef23a --- /dev/null +++ b/wg-zealy/meetings/013-2024-08-12.md @@ -0,0 +1,311 @@ +# Akash Network - Zealy Working Group (WG) - Meeting #13 + +## Agenda +- Recap of the initial campaign setup and communications strategy +- Discussion on campaign development and scalability +- Review of the first week of the campaign +- Planning for new missions and upcoming sprints +- Open floor for questions, feedback, and additional topics + +## Meeting Details +- Date: Monday, August 12, 2024 +- Time: 6:00 AM PT (Pacific Time) +- [Recording](https://5rakdvpt3sei3x6byxuc3roh4lpiz4mucxketzy2pmvphvhkipza.arweave.net/7ECh1fPciI3fwcXoLcXH4t6M8ZQV1EnnGnsq89TqQ_I) +- [Transcript](#transcript) + +## Participants +- B S +- Benjamin B +- Kaylem +- Maxime Beauchamp +- Quentin 72 +- Robert Del Rey + +## Meeting Notes +- **Campaign Recap:** + - Campaign launched on Thursday, with follow-up on Friday and Monday. + - First week saw 19 participants, 13 of whom were new members. + - Positive outlook despite slow traction due to market conditions. + - Proposal went on-chain, and funding was secured for rewards. + +- **New Missions:** + - Sprint structure: Three sprints, one each month, allowing participants to complete missions and earn AKT prizes. + - Focus on maximizing participation and ensuring rewards are distributed. + +- **Scalability and Reporting:** + - Discussion on how to scale the campaign and improve reporting mechanisms. + - Emphasis on gathering more community engagement and ensuring proper documentation. + +- **Submissions Update:** + - **Zealy Dashboard:** Robert mentioned that he will provide an update on the total number of submissions during the next call, as he did not have the current figures available. + - **Mission Participation:** Observations indicate that members are particularly interested in missions related to joining working group calls. + - Participants are motivated by earning points for submitting a "secret word" shared during the call, which contributes to their leaderboard rankings. + - High attendance reported in recent working group calls, with 9 people joining the Economic SIG-Economics and 7 people joining the Website Working Group. + - **Reminder:** Robert reminded attendees that submissions must include the correct secret word to be accepted. Incorrect submissions will be rejected, but members will have another chance to resubmit. + +- **Technical Missions:** + - There were mentions of technical missions, such as deploying RPC nodes on Akash, but Robert has not yet reviewed these submissions. No additional insights were provided during the meeting. + +- **Mission Participation and Rewards:** + - **Benjamin B:** Noted that even though the rewards for missions are not high, there is significant user participation. + - **Robert Del Rey:** Emphasized the balance between prize value and participation. Although current participation might be lower, he is optimistic about the quality of submissions that will benefit the community. + +- **Mission Review Process:** + - **Feedback for Benjamin B:** + - Robert encouraged Benjamin to share any observations or improvements regarding mission reviews in the Zealy Discord channel. + - Benjamin agreed and suggested updating mission descriptions if issues are found, such as the need for more specific instructions. He mentioned that initial missions might be approved despite errors if they are due to unclear instructions. + +- **Community Involvement:** + - **Robert Del Rey:** + - Stressed the importance of community feedback for improving the campaign. He encouraged participants to provide suggestions to enhance the campaign for everyone involved. + - Highlighted that the campaign is not only for the Akash community but also reaches the broader Zealy community, which helps with visibility and engagement. + +- **Secret Word for Zealy Mission:** + - **Robert Del Rey:** Shared the secret word "DeCloud" (same as last week) for attendees to submit for extra points in the Zealy mission. Reminder that submissions are allowed only once per month, and previously approved submissions cannot be resubmitted. + +- **Upcoming Calls for Extra Points:** + - Robert outlined four upcoming calls that are part of the Zealy missions: + - **Tuesday:** SIG Chain Monthly Call and SIG Community Monthly Meeting. + - **Wednesday:** SIG Design Call. + - **Thursday:** SIG Analytics Monthly Meeting. + - Participants attending these calls will be able to earn extra points by submitting the correct secret word shared during the call. + +- **Opening More Missions Mid-Sprint:** + - **Robert Del Rey:** Proposed opening up additional missions halfway through the Sprint to maintain engagement and attract more community members. + - Idea to release two new missions related to building on Akash: one for deploying a Lava RPC node on Akash Mainnet and another for creating a trusted community RPC node for Akash. + - Robert emphasized the importance of announcing these new missions to ensure community awareness and drive participation. + +- **Twitter Campaign Updates:** + - Robert mentioned that a tweet about the campaign is going out today, and a tweet asking for feedback will be published next Monday. + +- **Q&A Session:** + - **Encouraging Questions:** + - Robert Del Rey invited participants to ask questions if they are facing roadblocks or need help with their missions. He emphasized that the community is eager to support members in completing their builds and learning how to use Akash. + - Suggested reaching out for help in group channels, Akash’s Discord, or community chats. + + - **Mission Support:** + - Robert highlighted that the goal of the Zealy campaign is to guide people through the process of discovering and using Akash, not just to distribute rewards. + - Encouraged members to invite others who might be interested in Akash or in earning AKT tokens while learning about the platform. + + - **Unique Campaign Focus:** + - Unlike typical campaigns on Zealy.io that focus on social media tasks, Akash's campaign stands out by offering missions related to building on the platform. + - Robert expressed excitement about the campaign’s future and the potential for growth within the Akash community. + + - **Call for Involvement:** + - Robert hinted at the possibility of expanding the team as the campaign grows, indicating that more community members could get involved in the future. + +- **Kaylem's Input:** + - **Support for Content Creation:** Kaylem expressed enthusiasm for Akash's efforts to involve more than just builders in the community. He offered to help push content creation missions to his followers and assist with sourcing articles, indicating that he has a consistent following that engages with his posts about Akash. + - **Concerns About Overlapping Efforts:** Kaylem raised a concern about participants taking on similar tasks, such as writing multiple staking guides, which might result in redundant submissions. He suggested limiting repetitive tasks like guide creation to avoid duplication of effort and participant frustration. + +- **Benjamin B's Response:** + - **Open to Suggestions:** Benjamin encouraged Kaylem and others to suggest ideas for shaping missions that would resonate with their followers and help drive participation. He emphasized that the team is open to collaboration on creating missions that fit the community's needs. +- **Referral Mission Suggestion:** + - A participant suggested reintroducing a referral mission to help attract new members to the Akash community. + - Robert acknowledged the suggestion, noting that referral missions were used in a previous campaign. However, they didn't see much success, with only a few participants completing the mission. + - He expressed openness to revisiting the idea in the second Sprint, possibly tweaking the goal numbers to make the mission more appealing and achievable. + +- **- **Closing Remarks:**** + - **Content Creation Discussions:** Robert agreed with Kaylem's points and proposed having a follow-up conversation to shape content creation and social media missions. He highlighted the importance of leveraging community energy to keep the momentum going. + - **Future Calls:** Robert mentioned that there will be two more calls this month, one next Monday and another on the 26th. He suggested that the call on the 26th could be a special working group call to review the analytics of the campaign, share the dashboard with participants, and officially close out the first Sprint. + - **Potential Schedule Adjustment:** Depending on how things progress, the team may consider switching to bi-weekly calls instead of weekly ones. + - Robert encouraged participants to stay engaged and provide feedback through the Akash Zealy working group channel on Discord. He emphasized the importance of community input in making the initiative successful. + - He also reminded everyone of the other working group calls happening during the week, where participants can earn extra points. + +**Next Steps:** +- **Consideration of Referral Mission:** Robert and the team may revisit the referral mission concept in the second Sprint, with adjustments based on previous experiences. +- **Community Feedback:** Participants are encouraged to continue providing feedback and suggestions to improve the campaign. + + +## Action Items +- **Robert Del Rey** to monitor campaign progress and participant growth over the coming weeks. +- **Group** to focus on improving traction through better communication strategies and adapting to market conditions. +- **Robert Del Rey** to prepare documentation for campaign scalability and reporting mechanisms. +- **Robert Del Rey** to provide an update on the number of submissions in the next call. +- **Robert Del Rey** to review technical mission submissions, particularly those related to deploying RPC nodes on Akash. +- **Group** to continue encouraging participation in working group calls by highlighting the benefits of earning points through missions. +- **Robert Del Rey** to ensure announcements are made to inform the community about the new missions. +- **Kaylem and Robert Del Rey** to connect after the call to discuss content creation and social media missions. +- **Robert Del Rey** to plan for the special working group call on Monday, August 26th, to share campaign analytics and close out the first Sprint. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Robert Del Rey: Right, Scott Has been arrived. Thank you so much for joining everybody. Happy Monday. And This is a relief the second. City working group call that we have on this season 2. Very excited over all about what is happening and what is yet to come? So last week we spoke about the initial campaign setup the launching. We also went over our Communications strategy. We're gonna document this campaign and how we're going to share information about this campaign with the rest of the community. + +Robert Del Rey: Besides that we also spoke about reporting. The expansion of this campaign it's scalability. So that is all week for this week a very different topics. I want to discuss. a few things the development of this campaign during the last week was the first week of this campaign. So let's do a brief recap about how we want. Then after that, we're gonna spoke a little about opening up, New Missions. During this Sprint and doing the next Sprints that we're going to have. For those of you that don't know we're gonna have three. strings + +Robert Del Rey: Each month we're gonna have one different just to give a chance as many people as possible to complete the missions earn as many points as they can and subsequently get ATT prices. And by the end we're gonna have A session as always I'll be happy to answer all the questions or doubts I'd be happy to hear any feedbacks. You guys are if any also after that, we're gonna open it up just that anybody can contribute with any topic they see valuable for this conversation So without word though as you know, we started the campaign on Thursday first, then we went to Friday 2nd and then on Monday 5th the market when cracks. + +Robert Del Rey: But still it always recovers. I believe that could be a reason why we didn't get much traction during the first days. But we live to fire another day. It's how you end. That's what I say. So the proposal went on chain after we started this campaign we were confident we were gonna get the support needed to make the proposal pass. And also we had enough funds to make sure people get rewarded in case they do missions. But the proposal pass and for this first screen. I was checking on Friday before I log off. And we had 19 people. doing the missions + +Robert Del Rey: and out of those 19 people. We have 13 new members, which is something to celebrate. So first week 13 new members. Let's see how it goes through in the rest of the month. + +Robert Del Rey: About the submissions. Let me open up the city dashboard you weekly. I honestly don't know how many submissions we have so far. I guess I can get you that number for next call. But something I noticed is that people seem to like the joining working group and see missions just to give you a little context in those missions. We are motivating members to join the different working group calls we have on a cash. And the way we are motivating them is by offering some points. So They hear a secret word that I've shared during the call. They submit that word and they get some extra points and those extra points help them find the leaderboard. + +Robert Del Rey: Let me tell you last week. I joined the website Which both had these kind of missions? And the guys from the court team they were saying they were asked why the attendance was so high. B s was there in economic school. I believe we have nine people joining and in the website working group. Also, we have seven people joining. So I really feel Community these missions of view of them have submitted the secret word. I don't know if I send this reminder Let me see what I said on Friday. yeah. Let me just say that reminder here for the recording. + +00:05:00 + +Robert Del Rey: Remember guys, I tell you a secret word so you can submit that You can listen to that word life or during the recording when it's uploaded them, but remember guys if you submits anything. different than the secret word your submission is gonna be rejected. You will have another chance to submit the word again. But remember you have to submit the word if I say the secret word is I don't know. a passionate work That's the secret word you have to submit. Otherwise, we're gonna reject that mission. Hopefully you can understand that. but overall we have a really really big audience. + +Robert Del Rey: I haven't reviewed the kind of the technical missions. For example, there are a few submissions about deploying RPC node on a cache. + +Robert Del Rey: Maybe I don't know if you have any insights of those technical missions. If not, that's okay. I can go ahead and move on the next topic. Go ahead. + +Benjamin B: Even though the missions don't pay a lot. We're able to get quite a big number of the users participating in the world. + +Robert Del Rey: Yes, let's see how it goes. usually people just get in to see. How much money they can get as easy as possible. So during this campaign we try to balance out a little bit the prices and the participation. Something I think is that maybe we don't get as much participation or member counts during this time, but I'm confident we're gonna get a few submissions that we can share with the rest of the community. + +Robert Del Rey: I want to tell you Benji when you're reviewing those missions. If you see something can be done better. I don't know if people are specify. This will help you review missions. All right. Let me rephrase What I'm trying to say is that if you see anything that you believe it works easy reviewing missions share that in the group Maybe people read the instructions in the missions. + +Robert Del Rey: And they do things in a certain way, but only after they submit and after you review you're gonna be able to realize if that's the best way to submit or maybe if you need other pieces of information to complement your review. I said a lot of words there, but I hope that makes So long story short, if you find something that helps you make your job better or makes your job easier. Feel free to share that as an advice in the Discord Channel we have in the city description Channel we have my gosh this group. + +Benjamin B: Yeah, I understand. I also think that it makes sense to if I see something that's wrong with how we want the submissions to be done. I can change the descriptions as we go right now. We have one Mission and they run up similar to sdxl on a course. and I think we originally intended this one to be that you need to create your own now, and didn't specify it enough. We're going to approve the first missions that don't students because on our end. It's our fault and then for future submissions. We can have the description be changed. + +00:10:00 + +Robert Del Rey: All right, And that's another thing we're not going to know at all. We are learning as we go. So that's why I believe it's very important guys you listen in life right now. And anybody listening to the reporting if they listen to the recording if you find anything that you believe is gonna make these campaign better not only for you for me or a cash, but better for anybody that participating this feel free to drop that comment in the shots, maybe right now, it's just Benjamin I officially in this but still there is an office space for you to get involved any and try to make these better. + +Robert Del Rey: these is not only for the cash Community. This actually is shared in the city communities as well. They have a few hundred thousands of community members and two or three times a month. They share our community in their page which get us extra culture. so That's why I believe it's super important. We have commissions looking easy to understand and hopefully make them convincing enough for people to try this out. Even though they are not coming from the cash Community initially. So yeah good stuff. If there are other questions about the missions or the reviewing Mission process now, it's a great time to ask. Otherwise I can move on to the next Topic in the agenda. + +Robert Del Rey: All right, one, two three. And since we are 15 minutes in this call, let me go ahead and share this secret work with you. There is a city working group mission in a cash City. So if you submit this secret word, you will get some extra points. If you already did it the system won't let you submit the word again. So you can only do permissions once a month. So I guess giving you the reminder. All right, so the secret Works gonna be The same as last week, it' it's the ecl o u d the cloud like this centralized Cloud be Cloud. Thank you so much Benjamin. you can submit the word now. + +Robert Del Rey: Because you're listening in Life or you can listen to the recording and still submit the work and that's gonna be totally fine. The only condition is that if you're ready to submitted and we approve you and we run to do the points. you can assume it again. That is what I'm trying to say. any friendly reminders in case you want to get involved with other calls this week, we're gonna have + +Robert Del Rey: three calls which are part of the City Mission schools. Tomorrow we have the shame the same chain monthly call. And the Sikh Community monthly meeting. Those calls tomorrow will give you the chance to earn some extra points. If you submit the correct secret word. + +Robert Del Rey: okay, what's my mistake instead of three calls? There are four calls actually this week the third call is happening on Wednesday 14th. That's the sick design call. And on Thursday the 15th. We have the sick Analytics. Being monthly meeting. I didn't know it was on Democrat. It was the monthly but those four calls chain and analytics community and Design. + +Robert Del Rey: In there, you will hear the secret war and you get some extra points. Hopefully we get a High attendance this week as well. It was a great feeling. Last week, hopefully we can repeat it this week. And yeah, that was the second word the cloud. So moving on to the next topic. I wanted to share Benjamin with you. How would you feel about opening up a few more missions during this Sprint? And here's my recently. We have in Around 20 to 25 Commissions in total ready. + +00:15:00 + +Robert Del Rey: But for the Sprint number one. we only release three missions for building and two missions for content. And the rest of the missions just for the working group called Solutions. so I believe for example. If we go ahead and open up two more missions, let's say for next Monday in the middle of this Sprint. We can create a little bit more High. And maybe we can attract more community members to try the missions out because maybe something that happened. Is that people join the dashboard in the first day and they only find missions and they thought + +Robert Del Rey: I cannot do this missions. So I'm gonna disregard this. And if they disregard this they're gonna miss out on the other missions that we will have available. So I believe releasing the Sprint and then halfway during the Sprint release one or two more missions that can keep people more motivated into frequently based in the dashboard to see if we have information. I also plan to share an announcement just to make sure everybody is a word that we're gonna release the missions. it's not like and I still Mission We're Not Gonna open it up and just leave it there without letting nobody know we're gonna open up those missions and let everybody knows. So hopefully we can attract more people and we can increase the participation halfway through the spring. + +Robert Del Rey: So yeah, that is what I wanted to drop to kick off this discussion. Go ahead. Thank you. + +Benjamin B: last week + +Robert Del Rey: The Twitter is going out today is the first one that in people know that we started this campaign already. The Tweet about asking for feedback is going to go live on next Monday. Just so you'll be aware. But yeah again any feedback storm and it's not really welcome. + +Robert Del Rey: But yeah about Nations idea that I believe we can release halfway through the Sprint. + +Robert Del Rey: I honestly don't know Yes, I do. I was thinking about one last week log on network. It's already on Main net. I noticed I don't know if it was limokus or someone else that share a guide about posting the lava RPC note on a cash. So I'm really thinking we could release that Pathway to the Sprint so we could support lava mainnet or also since there is already a guide available more people can get a feeling of the process of deploying on a cash using that existing guide. That's one Mission I did idea have as far as building goes. + +Robert Del Rey: and for Content creation + +Robert Del Rey: Are I don't know I believe we shouldn't release another one about content creation. Maybe for now. We should keep it for the next train, but I'm down to open up more building on a cash relations. the lava one. and the other one is + +Robert Del Rey: create a trusted Community RPC node for a cash. That one is on draft. We can put it live also and that will be to build on a cash missions halfway through the screen. That's the initial idea. I have and those missions are already created. Meaning that we don't have to spend time thinking and creating animation. So the two missions that I recommend that there are already created and ready. + +00:20:00 + +Robert Del Rey: All what else? Are we missing something? Let's see. + +Robert Del Rey: Okay, The third topic I have on the agenda. It's the Q&A session. So + +Robert Del Rey: Yeah, let's open it up to that. + +Robert Del Rey: That's a one good question. It's anyone stock. I mean are you building right now? And you feel like you're in a roadblock? You cannot move forward. That's another thing guys. Let's say you are interested in A Max numbers and thank you for joining. so as I was saying, maybe just started a mission maybe you're Don't know how to move forward. + +Robert Del Rey: Don't be afraid of asking for help in the group. we want you to ask for help in the group or in any other groups of a cash, for example on this or there are deployments There is There is a community chat. There is the general shuttle. So in case you have questions, feel free to drop Any word of those channels? Or sellers at the end and we will be happy to help you complete your bill. because again What we really want is make people discover a Learn how to use a cash and go all the way to the process. For me silly. It's like a formal. We get people in arrested in a cash at first and then we are filtering out. + +Robert Del Rey: we see who knows how to deploy. All the way until the end and they hopefully become an outstanding Community member since they're gonna go through this process of discovering a cache knowing how to deploy on a going back to the topic to the point. if you have questions need assistance, feel free to share that in the group. We are more than happy to help you with your real. Because we don't really want you to get those akt. I mean that was a proof by the community. If we don't use them, that's okay. But the plan is to use this rewards and make people learn about a cash. So yeah, don't be afraid to ask where we're eager to help you complete your bill. + +Robert Del Rey: In and don't be afraid to let other people know if other people. That maybe are interested about a cash or maybe are interested in getting I don't know some dollars Some AKP tokens, right just for testing out and messing around. This is a great place to get started. What I like about these ceiling campaign is that it's different to anything but I've seen before honestly, if you go to sealy.io and you find you take the top three communities. you're gonna see that they offer Just Twitter missions go to Twitter like this tweet retweet these tweet create it to their threat. You are not going to find missions about building stuff. + +Robert Del Rey: And that is what impresses me about this campaign. We are Builders. We are attracting Hunters. Get these bills and to get paid the AKA. So yeah again don't be afraid to ask questions. Don't be afraid to share this with other people, that might be interested and again don't be afraid to get even more involved because again right now it's only Benji and I but maybe in the future this company grows so big that we need. An extra guy helping out or maybe two extra people helping out. I'm just saying out loud. I'm not confirming anything, but I'm just giving you the heads up about + +Robert Del Rey: how we see this and how we believe that this has future within the cash community. So yeah, that's sorry for the band I guess or maybe not. But yeah, that's my new ones guys. Overall. I'll feel very excited and thankful for the support that we have. And we just want to make this as fun and learning as possible for Benjaminophen to add anything more to that or if people in the audience has questions. otherwise we can end this now. + +00:25:00 + +Robert Del Rey: Okay, I'm gonna assume the thumbs up is that you don't like me That's right. And We're just kidding. All… + +Kaylem: Hey guys. + +Robert Del Rey: All right. + +Kaylem: Hey Robert. I just want to add one thing or maybe it's a comment rather than a question because I caught the tail end of this meeting and I heard you mentioned how you're involving more than just Builders and whatnot. And so I just want to say that that is absolutely incredible work there. And I think that that's the direction to go. So when I do my informative posts about Akash, I do have a set of followers that seem to consistently, what's the word interact or engage upon and I would love to see more of these quests in order for me to help push them so that does that mean if you need 50 articles written right? Maybe I can help Source those out. Does that make sense with the people who follow me on the post that we do make and so I just want to encourage more of that and I think I sent you a private message already regarding a + +Robert Del Rey: Yeah. + +Kaylem: Guide, I foresee that people might take easy ones and you might have 15 staking guys, you know what I mean? And so I know that that's not… + +Robert Del Rey: Thank you so much skylene before I let you Benji I want to quickly say thank you to Auto. + +Kaylem: what you want. But my fear is that people would have spent the work to do it anyway, right and then they're gonna feel like… + +Robert Del Rey: Kaylem. He's from the page. + +Kaylem: because you're not gonna be a reward ten States taking guy. + +Robert Del Rey: You might seen it a cash Alpha… + +Kaylem: Sorry. + +Robert Del Rey: which is a hell of a page. + +Kaylem: so I don't know I saw again I missed a whole meeting so I'm not sure… + +Robert Del Rey: I appreciate a lot of the work you do man,… + +Kaylem: if there's any way to make sure that people aren't like working on,… + +Robert Del Rey: and I haven't seen your message. I saw the notification. + +Kaylem: all at once or… + +Robert Del Rey: I know you sent me something… + +Kaylem: once it's submitted I noticed that there was one submission that was accepted… + +Robert Del Rey: but I haven't gotten to that post yet. + +Kaylem: but for… + +Robert Del Rey: But since you're already gives me a brief overview I learned with you and… + +Kaylem: what type of article and so those are just some of the questions that I have regarding that + +Robert Del Rey: and people tend to take the easiest tasks first. So I agree maybe we could just remove how to say guides from there if it comes that's great, but we're not gonna leave it there as an idea for people because again, it's gonna be the easiest route to go. So thanks I agree. And yeah, let's do it. Go ahead Benjamin. + +Benjamin B: Be able to say two things here. The first thing is that if you want to Help shape some of the missions. We are of course taking suggestions on how to create these missions if you have a way where you think that your followers might be Able to join zealy and complete missions if we create them in a specific way. Feel free to reach out and we can try to + +Benjamin B: go back and forth from these ideas. For the second thing. + +Robert Del Rey: Thanks. Thank you. + +00:30:00 + +Robert Del Rey: All right. I love it. Thank you so much. Kaylem. And maybe when you and I can speak After this call to shape up. Those content creations and those social media missions, which is super important as well and an internet agree with kaylem. I believe the words you use we should tap into that energy. and they can advantage of that energy and keep the goal rolling, right? That's what we want. + +Robert Del Rey: on writing guys Right. Mmm + +Robert Del Rey: Let's see for the rest of the month. We're gonna have two more calls. We have a call next Monday that I think and then another one the 26 at the moment. We're gonna do a weekly call. Depending on how it goes. Maybe we can change that. bye weekly call. but yeah, I'm thinking that by the end of the month on Monday 26, we can have a special working group call where we can go ahead with the attendees Some analytics about Akash ceiling. Maybe we can share the dashboard and show them. How many people submitted and how many members are there? + +Robert Del Rey: and just officially close out the first campaign the first Sprint. Let's see. I'll think about it. But with that being said, I don't have anything more to add Benji anything else to + +Robert Del Rey: if not Okay, I see a question in the chat things are Quentin 72. Have you think about a referral Mission? It could be a great way to attract people Yeah, We actually had referral missions in the first season of this. + +Robert Del Rey: We honestly didn't consider it. this campaign, but I do agree with you that it's a great way to attract people. So, I don't know maybe when I can discuss about this. If it, maybe we can bring it in the second Sprint and see how we behaves. But yeah. last + +Robert Del Rey: in the first campaign if I recall correctly. only two or three people completed that mission + +Robert Del Rey: because for example silly has a template you can create a referral Mission very easily. and they ask you how many people is the goal you want them to invite only five people only 10 people. I believe that's all. And in the last campaign, we set it up to invite five people and I believe only two people completed that so maybe we can rethink those numbers and release again if we can really sit again, but yeah, thanks for the suggestion. I appreciate it. And I agree with it's a great way to attract people officially. Because now you you can invite anybody to the community. but if we invite someone and the person comes to the community. There is not going to be a record of that. however, if you invite a person through your personal link + +Robert Del Rey: through your personal silly link You can create a record of that then and get points get XP and find the letter. so yeah. Thanks coach. Good one. + +Robert Del Rey: All guys, I just hope that you enjoyed this time with us today. Thank you for participating again. If you have questions, there is be a cash silly working group channel on a crash Discord my DMs are open. + +Robert Del Rey: And yeah, hopefully I can see your feedbacks. We can continue working together and make this super awesome Community itiative. So don't forget the other working group calls. We have this week and the chance to earn some extra exploits. And yeah, that's all for me from right now. + +00:35:00 + +Robert Del Rey: I don't know. you see you in developers right seeing them. Whatever. Stay safe guys. Happy to see you and wish you a good week ahead. Bye. + +Meeting ended after 00:35:48 👋 From 15bbfdb314985174adab8ec49b5a864f61a96606 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 16 Sep 2024 02:02:20 +0000 Subject: [PATCH 133/138] Create meeting notes Sig-economics #18 (#674) * Create meeting notes Sig-economics #18 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 018-2024-08-07.md add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-economics/meetings/018-2024-08-07.md | 102 +++++++++++++++++++++++ 1 file changed, 102 insertions(+) create mode 100644 sig-economics/meetings/018-2024-08-07.md diff --git a/sig-economics/meetings/018-2024-08-07.md b/sig-economics/meetings/018-2024-08-07.md new file mode 100644 index 00000000..6badb33a --- /dev/null +++ b/sig-economics/meetings/018-2024-08-07.md @@ -0,0 +1,102 @@ +# Akash Network - Economics Special Interest Group (SIG) - Meeting #19 + +## Agenda +- Review of previous meeting topics +- Discussion of current proposals +- Provider Incentive Program (PIP) update +- Open discussion + +## Meeting Details +- Date: Wednesday, August 07, 2024 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://qextbwdkzexp6rjoxd43vbxe4gmojck4wartnjykb3lsjbwtoemq.arweave.net/gS8w2GrJLv9FLrj5uobk4ZjkiVywIzanCg7XJIbTcRk) +- [Transcript](#transcript) + +## Participants + +- B S +- Cheng Wang +- Cristiano +- Dev Composer +- Kaylem +- oo o +- Robert Del Rey +- Robert Koschig +- Scott Carruthers +- Scott Hewitson +- Scott Hewitson's + +## Meeting Notes +### Introduction and Previous Meeting Review + +- Scott Hewitson welcomed attendees and those who may watch the video later +- Last month's meeting was brief (about 15 minutes) and covered PIP updates and the inflation proposal + +### Current Proposals + +#### Inflation Update Proposal + +- Cheng Wang provided a detailed update: + - Originally proposed to reduce inflation and increase community tax + - Initial proposal suggested increasing community pool tax from 20% to 40% (or 10% to 40%, exact figures not recalled) + - After community feedback, the proposal was modified to only adjust inflation + - Reducing inflation would also result in a reduction of APR for staking + - The new inflation rate is set to take effect the day after the meeting + - Reasons for the adjustment: + - Community pool is well-funded despite recent market volatility + - Current emissions are ahead of the original schedule + - The community pool tax increase was removed from the proposal due to community pushback + - Original goal was to have community pool tax at roughly 50% + - Community suggested separating inflation parameter adjustment from community pool adjustments + - Spreadsheet calculations now take into account staking ratios for more accurate projections + +#### Developer Onboarding Funding Proposal + +- Referred to as "Developer onboarding funding proposal number two" +- Robert is running this proposal, which is a continuation of a successful version one +- The proposal is currently on-chain and open for voting +- Scott encouraged those who haven't voted to do so + +### Provider Incentive Program (PIP) Update + +- Cheng Wang provided a comprehensive update on PIP: + - PIP One Phase One is nearing completion + - PIP One launched in February of the current year + - Major initiatives funded by the community pool in 2024: + - PIP One Phase One (approximately 3 million tokens, or $3-4 million at the time) + - Coinbase Learn and Earn program (about $7 million) + - Final funds from PIP One are being committed, including for new H100 GPUs + - Detailed reporting and invoicing are being prepared for transparency + - Spreadsheet updated to take into account staking ratios for accurate calculations + - Challenges with implementing the liquidity pool phase due to the need for verified resources + - Concerns about potential spoofing of resources (e.g., fake H100 GPUs) by scammers + - PIP Two discussions to begin in the coming 3-6 weeks + - PIP One had three phases: committed phase, liquidity pool phase, and R&D phase + - PIP Two will likely focus on another committed batch + - Learnings from PIP One will be applied to PIP Two + +### Zealy Campaign Update + +- Robert Del Rey discussed the ongoing Zealy campaign: + - Aims to increase participation in SIGs and working groups + - Extra XP points offered for attending calls like sig-economics + - XP points can be exchanged for AKT + - Secret word can be submitted even if heard from the recording + +### Open Discussion + +- No additional topics were raised by participants +- Scott mentioned always thinking about ways to better progress the network + +### Closing Remarks + +- Cheng Wang encouraged community participation in upcoming PIP Two discussions +- Cheng emphasized the importance of sharing thoughts and questions in Discord, Steering committee, and SIG economics +- Scott Hewitson thanked everyone for joining and closed the meeting + +## Action Items +- Cheng and Scott to prepare and share a detailed PIP One spending report. +- Community members to watch for and participate in upcoming PIP Two discussions on GitHub, Discord, and in future SIG meetings +- Group to monitor the implementation of the new inflation rate set to take effect the day after the meeting + +## Transcript From 2ee90ea4b279c385ae65cd76e2e26cf78bac2463 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 16 Sep 2024 03:15:32 +0000 Subject: [PATCH 134/138] Create meeting notes for wg-Zealy #15 (#678) * Create meeting notes for wg-Zealy #15 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 015-2024-08-26.md added transcript Signed-off-by: Drinkwater * Update 015-2024-08-26.md added recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-zealy/meetings/015-2024-08-26.md | 169 ++++++++++++++++++++++++++++ 1 file changed, 169 insertions(+) create mode 100644 wg-zealy/meetings/015-2024-08-26.md diff --git a/wg-zealy/meetings/015-2024-08-26.md b/wg-zealy/meetings/015-2024-08-26.md new file mode 100644 index 00000000..7c365a6c --- /dev/null +++ b/wg-zealy/meetings/015-2024-08-26.md @@ -0,0 +1,169 @@ +# Akash Network - Zealy Working Group (WG) - Meeting #15 + +## Agenda +- Review of Sprint 1 progress and submissions +- Updates on content creation missions +- Preparation for Sprint 2 +- Monthly report and campaign statistics +- Update on RPC Node mission + +## Meeting Details +- Date: Monday, August 26, 2024 +- Time: 6:00 AM PT (Pacific Time) +- [Recording](https://hptrexukvlr4pusvwjqanuzqoir26icxztgxgoocffukadhuigfq.arweave.net/O-cSXoqq48fSVbJgBtMwciOvIFfMzXM5wilooAz0QYs) +- [Transcript](#transcript) + +## Participants +- B S +- Benjamin B +- Lussi Petelius +- Quentin 7200 +- Robert Del Rey +- Shiny + +## Meeting Notes + +### Sprint 1 Progress and Review + +- Robert Del Rey provided an update on the first sprint: + - This is the last week of the first sprint of the campaign + - Approximately 25-30 submissions have been received so far + - Content creation missions have been reviewed, with solid submissions overall + - Feedback is being provided to participants to help improve their submissions + +### Submission Dynamics and Rewards + +- Robert Del Rey explained the submission and reward process: + - Low-quality submissions will be redacted + - Submissions meeting the standards will be marked as successful + - The best submissions will be compiled into a single document to share with the community + - AKT rewards calculation will be done after the sprint ends + - Winners will be announced, and rewards paid out within 1-2 weeks after the sprint end + +### Sprint 2 and Reporting + +- Robert Del Rey outlined plans for Sprint 2 and future reporting: + - Sprint 2 is scheduled to start on Monday, September 2nd + - A comprehensive one-month report will be released, including: + - Number of participating members + - New members joining the Akash community + - Total number of builds submitted + - Highlights of the best builds + - There's a possibility of extra prizes for the best submissions + +### Community Growth and Participation + +- Robert Del Rey shared community growth statistics: + - There are 45 total participants in the current sprint + - 30 new members have joined the Akash community through this initiative + +### Mission Updates + +- Robert Del Rey announced changes to missions: + - Increased rewards for Trusted Community RPC Nodes mission from 15 AKT to 20 AKT + - Reduced the number of people who can claim the RPC Node mission from 50 to 25 + - Currently, there are 7 submissions for the RPC Node mission + +### Technical Missions + +- Benjamin B's role in technical missions was highlighted: + - He is reviewing technical missions + - Available to help participants with technical questions about Akash + +### RPC Node Mission Clarification +- Benjamin B provided clarification on the RPC Node mission: + - Participants do not need to code an RPC node from scratch + - Deploying and running an RPC node is sufficient for the mission + - Mission payout may be delayed until the end of the campaign to ensure long-term operation of the nodes + +## Action Items + +- Participants are encouraged to submit final entries for Sprint 1 before it ends on Friday, August 30th +- Robert Del Rey will prepare the comprehensive one-month report +- Robert Del Rey will set up Sprint 2 and determine reward amounts +- The team will review all missions and process payouts after the sprint end +- Benjamin B will update the RPC Node mission description to improve clarity +- Participants are encouraged to join the Steering Committee call on August 29th + +# **Transcript** + +Robert Del Rey: All right, and welcome everybody. The Cash City Working Group call today Monday, August the 26th. briefly ago, I sent a message in the group. This is the last week of the first grade of these campaign, We've seen lots of summations so I would say roughly. We had I don't know. More than 2530 submissions. I used to give you a rough. + +Robert Del Rey: We're very happy about that. keep it up, guys. This is the last week. If you haven't submitted A Build your planning to submit one. this is the last week to do, so, if you don't submit your bill now, That's fine. Some missions are going to roll over to the next sprint. So, If you don't get the points now, you're still good. Will have a chance to get the points in the springs. Number two, or the sprint number three, So yeah. Some things we did this last week, we reviewed some missions. + +Robert Del Rey: Some of the content creation missions. The submissions have been very solid so far. And we are reaching out back to some of the people to give them some feedbacks and make the submissions better. We're starting to have you, we're super happy that you're getting involved. the next part of the plan is making things. That are gonna be valuable for the wider. We want people outside of this to look at This submissions. And feel like Hey I cash definitely has something going on. Let me check it out. That is the kind of feel. We want to give the people about this campaign in the solutions that we We open up a new document, which is gonna help us Maybe. + +Robert Del Rey: Keep I mean, also missions are going to be reviewed. If there are low quality, they're going to be redacted, if they meet the standard, they're gonna be a success, But of the best missions. We're going to compile them into a single document and we're gonna share that with a community. Once the company is over or maybe sooner. Let's see. One thing about that is that when the screen is over, we're gonna do the math, we're gonna see how much AKP you got. The winners will be announced and + +Robert Del Rey: in one or two weeks after the spring ends, those rewards should be paid out. At the same time, the sprint, number two is going to start right away. This is strength and this Friday on the 30th or Saturday, I'm not sure now. But this three. Number two, should I start on The second So on Monday, we're going to have to screen number two. and also the City Working Group, but yeah, I'm a stop real quick. I know I said a lot. yeah, that's it about the screen. Number two and the submissions dynamics. I will stop really quick. In case anybody has a question. I will give you time. + +Robert Del Rey: if there are no questions, totally fine, if we do, send it in the shaft or later when you think about it in the Akash physical group, Hey, yes, I see you. So going back guys. Yeah. one thing we're gonna do in this train number one, which we didn't in the last campaign, we're going to release one month report and in that report, We're gonna add information about how many members are participating in the spring. How many new members join the cash community? How many builds we had? And also, we're going to highlight of the best fields. let me tell you if your build is selected as the best if we see the quality is + +Robert Del Rey: on a whole new level level right and you make it to one of those lessons, the best submissions, I don't know, maybe it's some extra prices. I don't know if I'm saying too much money but yeah, it pays you to do the best work you can do. So let's do the best word that we can guys. Also if you feel like there is something we can improve Again, My DMs are open, feel free to reach out. So yeah, that one month report is gonna contain all that information, hopefully have that information. + + +### 00:05:00 + +Robert Del Rey: Will give. An idea to the people of the future seeing these campaign and they can look back and see the things we did. And what it's gonna Remained through the history, So yeah, there's going to be the one month report by the end of the three months, we're gonna have a three month campaign report, but every single month, we're gonna let you know all the numbers about this campaign. Yeah. that. + +Robert Del Rey: Any. Race. it's again. Okay, DMV here, guys. Thank you for joining me. I wouldn't say it's quite big today. Appreciate that. + +Robert Del Rey: Mmm, so yeah, so far we got paid in new members. Joining this print. And 45 participants in total. So in the current stream, there are 45 people participating. Out of those 30 people. Community? Which I believe in something to celebrate. It's just the first month, right? So yeah. I'm very stuck about that. Some updates about the last week. We heard the + +Robert Del Rey: in order to do some of the missions, you needed to pay in a cash. So of course because we want them to be on the So if your submission is on mainland you will have to pay some provider for your deployment, So we decided to Create a Trusted Community RPC Nodes for a cash. So, we increase the price for that. Instead of 1580, it's gonna be 20 Akt. if I'm not mistaken, so those five X-ray KT. Should help you out with those deployment costs. Wirelessly with some. + +Robert Del Rey: 80 prices, right? So yeah. That's one update about that. + +Robert Del Rey: However, we reduced the amount of people that can claim the required. So in the past I believe it was 25 people. I don't remember. + +Robert Del Rey: Yeah, it was 50 people and we reduced the number 25. So only 25 people will be able to play this throughout the campaign at the moment. I believe we have seven submissions about these nation. So you guys will get increased rewards. And get throughout the campaign. Only 25 people will be able to create this mission. So, All Work 10 minutes in this call. Let me say the secret word for the Sealy Working Group mission. Just to give you a little context because I'm seeing new faces in this call and also for the people listening to the recording. We have missions about joining the cash, especially in this groups, and their cash working groups calls. + +Robert Del Rey: So, when you join those calls, I will say out loud a secret word. And you just need to go to a cash Seeley. Find the mission about the call that you were and submit the secret word. So, for the silly mission, the secret word is gonna be the same. It's a The cloud, the E C L O u D. Right? I believe I got it right. I will send it in the chat anyway so you guys can see Obviously, you're listening to this now. If you listen to the recording, you can submit the world. When you listen to the record in this missions, will remain open throughout the screen. But you can only claim it once. That's the cash, if you claim it now. + +Robert Del Rey: You cannot claim it again. I believe that's so For this week, we're gonna have the steering commit In the sitting comedy call that is going to be a secret word for you to submit and get some extra aka. + + +### 00:10:00 + +Robert Del Rey: Yeah. that. + +Robert Del Rey: yeah. Does anybody has a question something you want to bring to the table? I will be a good audition. If not. Again, that's totally fine. The group is certainly open. I'm actually very happy when I just enter a cash discord. I go to the city working group and almost 100% of the time. There is any message waiting to be. so, I'm loving the engagement so far in this campaign, I remind you guys. There is a mission about referring people to attach a ceiling. If you refer to friends and those three friends complete at least one mission each, you will get some extra points and some extra So that's something good to know about. + +Robert Del Rey: For this week. I'm done. Yes. So I'm done with this call. So for this week what I will do, I will work in the one month report. I will set up the screen. Number two, we will maybe and I will determine the rewards amount. And pay out those after we review all of the missions. Again, the screen is going to end. On the daily this week. It's Friday. so, if you make your submissions, After the spring ends. Those points are not going to count for the security number one, so if you want to make as much points as you can, in one screen, purchase you make everything in this spring. New missions will open up in the springs. Number two, so a sales level + +Robert Del Rey: And yeah, this Friday and events. Let me see. Yeah, August earlier. So at that time, the sprint number one, it's gonna have. And the spring, number two starts on Monday, the second. so yeah, Benjamin Sorry, for which on the spot. But is there anything you want to add about the missions or that review? You have done so far. Then this guy actually reviewing the technical missions. So if you guys have a questions Technicals about a cache, then it's the guy to help you out. So I will give it to you but they don't know if you want to add anything. + +Robert Del Rey: It's good to hear, man. + +Robert Del Rey: if you see something that stands out, Remember to put in the content solution. Document. And we should a document with you guys when we have a complete ready, right? + +Robert Del Rey: And yeah, that. Thank you so much money. I didn't say the day of the Call the city in community college, it's gonna happen this Thursday, the 29. I guess so, if you join and you listen to the secret word, you'll be able to get some extra XP points, the more XP, the more I think you get and I believe this color is gonna be short today, baby, don't you say unless anybody has something to add I guess we can just end it here. You guys have any questions or anything you want to stop in a mission or something? + +Robert Del Rey: That's fine. + +Robert Del Rey: All right, that I just will say this before we go. Okay, I have a question here. My guy Quentin. + +Robert Del Rey: 7200. Do we need to code an RBC note from a scratch? Or deploying, you're a fast reader. go ahead, and if you are gonna reply, + + +### 00:15:00 + +Benjamin B: yeah, I just wanted to say that this mission we had some feedback on this on how we best, could make sure the people actually created for the long term. + +Benjamin B: Chance of your question. Just deploying it. It's enough. I'm running it. You don't have to code anything, you just have to get it running. But because of the mission of wanting to create some long-term RPC servers. And I think this one, we should wait until the end of the campaign to pay out because then we can track that. the RPCODE has actually been active for longer than just maybe. Until it's reviewed. + +Robert Del Rey: Thank you Hope the answers your question and thank you baby. For the support. + +Robert Del Rey: All right. + +Robert Del Rey: It's Monday, We're gonna make it happen. If we survive them, Monday, we're gonna survive the week and told you that. And so yeah. I'm gonna leave it here again. Thank you for your question. Thanks Benji About the missions reviewing. And guys. Remember to join the steering community. Call. For more chances to earn expert tokens, the screen. Number one ends this week so make it happen. If you have questions, go to the Cash CV, Working Group chat in a cash discord. And yeah, I said another question, maybe could it be precise on the missions for the people? + +Robert Del Rey: Yeah yes sure Nice catch up. Let's go ahead and add that to the mission bendy so it can be more clear for more participants. This is the work in progress, right? we're gonna get better as we go but we cannot definitely get better without you guys. Not helping. And stepping in, this is the first innovation I guess. This is something that we want to do long-term. And our cities in the future is that this is gonna be a channel where we can introduce a cash all kinds of people. So they're better. We do this. Now, the parent is gonna be the future when more and more people can access to these + +Robert Del Rey: So yeah, it's a little inspiration for you and this week. So yeah, guys again, thank you for doing anything. The recording and the notes will be available in Github shortly. If you have questions, my DMS are open. The group chat is open. And we should chat again in the next Monday. And when we start the springs, number two, Yeah, thank you b s for joining. Have a good one, guys. + +Benjamin B: Thank you. + + +### Meeting ended after 00:18:32 👋 + From bae8a3aa000d80a76b24b37c4b8c562d299d765e Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 16 Sep 2024 03:20:35 +0000 Subject: [PATCH 135/138] Create meeting notes wg-zealy #14 (#672) * Create meeting notes wg-zealy #14 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 014-2024-08-19.md Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 014-2024-08-19.md added transcript and recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-zealy/meetings/014-2024-08-19.md | 299 ++++++++++++++++++++++++++++ 1 file changed, 299 insertions(+) create mode 100644 wg-zealy/meetings/014-2024-08-19.md diff --git a/wg-zealy/meetings/014-2024-08-19.md b/wg-zealy/meetings/014-2024-08-19.md new file mode 100644 index 00000000..1e792c63 --- /dev/null +++ b/wg-zealy/meetings/014-2024-08-19.md @@ -0,0 +1,299 @@ +# Akash Network - Zealy Working Group (WG) - Meeting #14 + +## Agenda + +- Akash Zealy Campaign Overview and Progress +- Current Sprint Status +- Mission Updates and New Missions +- Working Group Call Attendance +- New Mission Strategy +- Project Showcase +- Q&A and Discussion + +## Meeting Details +- Date: Monday, August 19, 2024 +- Time: 6:00 AM PT (Pacific Time) +- [Recording](https://ywvlgtl7bqzi5c2tibnbvs6j4rufukc2cwa5p7dsp33ulbiusiha.arweave.net/xaqzTX8MMo6LU0BaGsvJ5GhaKFoVgdf8cn73RYUUkg4) +- [Transcript](#transcript) + +## Participants +- Robert Del Rey (Host) +- Austin Hardnett +- B S +- Benjamin B +- Fenil Modi +- Poroburu +- Rodri R +- Other unnamed attendees + +## Meeting Notes + +### Akash Zealy Campaign Overview and Progress + +- The first of three sprints commenced on August 1st, 2024 +- Current sprint is scheduled to conclude on August 30th, 2024 (Friday) +- A brief interval will follow the sprint's end before the next one begins +- During this interim period, Robert will: + - Review completed missions + - Calculate associated rewards + - Process payments for participants +- The upcoming second sprint will introduce additional missions to engage participants + +### Current Sprint Status + +- The campaign has attracted a total of 38 participants +- Among these, 25 are new members to the Akash community +- Despite recent market fluctuations, participation levels remain robust +- Robert expressed satisfaction with the strong participation, especially considering the campaign is only two weeks old + +### Mission Updates and New Missions + +#### Twitter Writer Mission Modifications: + +- The "how to stake" guide has been removed from the list of suggested topics +- Emphasis has been placed on content originality +- Remaining topic suggestions include: + - First-time deployment processes on Akash + - Tutorials on using Akash console and praetor + - Compelling use case stories featuring Akash + - Comparative analyses between Akash and similar crypto projects + +#### Newly Introduced Missions: + +- Invite Friends Mission: + - Participants are tasked with inviting 3 friends to successfully complete at least one mission + - Successful completion rewards 15 XP points (equivalent to 1.5 AKT) + - This mission can be undertaken once per month for a three-month period + - A stern warning was issued against inviting bots to participate + +- Lava Network Provider Mission: + - Participants are challenged to become a Lava Network provider for any supported blockchain + - The provider service must be deployed on the Akash network + - Successful completion offers a substantial reward of 50 AKT (500 XP points) + - This mission aims to foster integration between the Lava Network and Akash + - Supported networks encompass Cosmos, Axelar, Celo, Filecoin, among others + +### Working Group Call Attendance + +- A notable increase in attendance for working group calls has been observed +- This uptick is attributed to the integration of working group call missions in the campaign +- Upcoming calls featuring missions include: + - Design Working Group scheduled for Tuesday, August 20th + - Steering Committee meeting set for Thursday, August 22nd +- Participants can earn additional points (8 tokens) by submitting secret words from these calls +- Those who have already submitted words for previous calls must wait for the next sprint to earn points again + +### New Mission Strategy + +- The campaign is adopting a dynamic approach by introducing new missions throughout the sprint +- While an initial set of missions was published at the campaign's outset, additional challenges will be released as the sprint progresses +- This strategy aims to re-engage participants who might have initially felt certain missions were beyond their capabilities + +### Project Showcase + +- Rodri R provided a live demonstration of deploying an RPC node for the Tia network on Akash +- The demonstration utilized the devnet on the Akash sandbox +- A GitHub repository containing detailed instructions was shared with attendees +- Rodri noted that the process could be adapted for other Cosmos SDK-based blockchains with minor adjustments +- A discussion ensued regarding potential improvements for mission requirements and rewards: + - Suggestions included allowing the Lava Network Provider mission on the Sandbox to mitigate costs + - Proposals were made to adjust rewards based on whether deployments occur on mainnet or sandbox environments + +### Q&A and Discussion + +- Robert encouraged participants to propose ideas for custom missions +- The campaign's primary focus on showcasing Akash's capabilities and pushing its limits was reiterated +- Participants were invited to utilize the Akash Discord channel for questions, suggestions, and ongoing discussions + +### Additional Notes +- The next meeting is scheduled for Monday, August 26th, at the same time +- Robert will dedicate time after the meeting to review content creation submissions + +## Action Items + +- Participants to complete current sprint missions by August 30th +- Robert to review and process rewards for completed missions after the sprint ends +- Team to implement and communicate the new Invite Friends and Lava Network Provider missions +- Participants encouraged to join upcoming Design Working Group and Steering Committee calls +- Benjamin B to evaluate allowing Lava Network Provider mission on Sandbox to reduce participant costs +- Robert to continue reviewing content creation submissions post-meeting +- All participants to consider and submit ideas for custom missions via Akash Discord +- Team to prepare for the launch of the second sprint, including new mission rollouts + +# **Transcript** + +Robert Del Rey: right recording and transcribing or write everybody. Thank you for joining and welcome to these. version of the cash developer rewarding campaign on ceiling you got excuse me today. I'm feeling like a little sick. Maybe that's why. + +Robert Del Rey: Also my chest hurts, I don't know what's going on. so in this call guys, we're gonna follow up and discuss all things around the cash silly company. the first of three sprinters started on the first of this month of August. And we're approaching the end of the first spring. I wanted to give you the heads of the screen and on Friday the 30th. So participants have a little over. One weekend something almost. + +Robert Del Rey: Almost the weeks. Yeah. + +Robert Del Rey: To speed up and make sure those two missions are made. Once the spring ends. The next one is going to start. a few days after doing that time I will continue reviewing missions calculating the rewards and at the same time paying those rewards after we do the math for the first state. + +Robert Del Rey: so second experience is gonna bring more missions Beyond the lookout for that. But let's speak about the correctly guys. at the moment there are 25 new members in the community participating in the silly company in a total of 38 members participating in this spring. So we are very eight people participating in the Stream in 25 out of those 38 are new people in the ash community. Which is something to celebrate, I believe I mean the spring that started two weeks ago and we had a makeup in the market. I don't know if you guys remember so that didn't stop people for joining up this campaign and I believe we have a solid number just two weeks into his campaign. + +Robert Del Rey: I will stop for a quick second unless Anybody has anything to add about the second screen and how it's going so far guys. Are you liking Missions at the moment? Do you think we could do? Something better. I like to hear some of your voices today. + +Robert Del Rey: that's not really fine. Remember to drop any suggestion chat in cash Discord almost available in the DMs. So, yeah, let's move on. Tell me I don't know if you don't know me. He's an attached Insider. He has suggested two missions actually, and then we're gonna shut about those. + +Robert Del Rey: I wanted to say it's pretty cool. One of them is actually about deploying and hosting your personal website on a cache. We don't have a mission about that. So it will be cool. To bring that up and there is another one that I have about later. But yeah, we beat a quick fix in one of the missions. It's called the writer in the Twitter writer Michel just to give your little context. + +Robert Del Rey: We are requesting people. To write anything about a cash it can be an use cases about tutorials. about all the things that you can do on a cash Network. one of those things though was how to escape guide But with figure last week that since we already had a lot of that content about how to stay on a cash, we would remove that out of the list. So in the list you're gonna find the topics like how to do your first deployment on a cache how to use their cash console pretor. case of stories about a cash like I mentioned Or comparing the cash to similar crypto projects + +Robert Del Rey: and other topics, basically the originality is the key in these missions. So yeah, Let's see what you come up with but how to take Mission they help just take a mission. That one was removed. Artification just going to give you the heads up. + + +### 00:05:00 + +Robert Del Rey: Thank you so much guys. + +Robert Del Rey: All right moving up in the India again that guys in the past two weeks. We have been noticing and increase in the attendance in the working group calls. And we feel very good about that because we think that it has With the working group called missions that we have In those missions, we are invited people to join the seeds and working group calls that a cash has throughout the weeks. And we've seen a substantial increase in attendance. So keep up that work guys and besides the points you get for those missions when we really want is you to get involved in the different aspects of Action Network. so yeah, everybody happy about the attendance so far for this week. There are going to be only two calls. + +Robert Del Rey: That have missions one of them is the The Design working group. it's happening tomorrow Tuesday. And the steering committee It's happening on Thursday. I believe confirm. it's happening on Thursday the second. So those two calls are gonna have If you submit that secret word, you will get some extra points some extra 80 tokens. If you're already submitted the word it's not gonna work. I get it. You have to wait. For the next Sprint if you want to just leave the word again. So, guys. And yeah, those are most of the topics that I have. I wanted to get those out of the way and showcase you the two new missions, we're gonna have + +Robert Del Rey: Something that we decided to improve upon during these campaign was they continuity about the mission? How we need it in the NASA screen is that we had a set of missions. We would just publish that And yeah, that was still. But in this campaign, we're going to do it a little bit different. We're gonna open up the street with a few set of missions. + +Robert Del Rey: I'll wait through the Sprint. We're gonna release New Missions for you guys. We believe that can motivate people to try again. Maybe you saw the missions in the first week and you talk to yourself that you couldn't do them. So we're going to release that next batch of missions and hopefully that can give people a chance to participate in this company. So I will share my screen real quick. So that you can see the two new missions we're going to have for you. + +Robert Del Rey: So that's + +Robert Del Rey: all righty. + +Robert Del Rey: I'm trying to screen now. Let me know if you guys. + +Benjamin B: I can see. + +Robert Del Rey: Thanks All right, so the First new Mission it's gonna be available as soon as this call and this region is gonna be able it's about inviting your friends to see this was actually a suggestion we had in one of the working group calls. I believe it was last weekend. But invite three friends to do the missions. They have to do at least one Mission successfully or the invite account. And after you complete the three invites you will get 15 XP points, which is 1.58. It's not much but it's a good price. All right. + + +### 00:10:00 + +Robert Del Rey: Yeah. numbers of invitations require so you can copy your invite link here. That is what you share with your friends. when they click on your link and do one mission that is gonna count here. You don't have to submit anything you need to come here then invite the people and when doing by the tree the mission is gonna build you. + +Robert Del Rey: Sure. + +Robert Del Rey: yeah. you have + +Robert Del Rey: yeah, man, you're right. Let's do that right away that makes more sense. Nice catchment thank you for that. So yeah guys three invites and you get the extra points. And again this is gonna be available to you monthly. So for the whole three months, you can do these three times, please don't invite Bots to the server, please invite real people. All right. + +Robert Del Rey: It also So I hope you that you like the next mission more. This one is more exciting. I don't know if you heard the news lava Network. It's on magnet and then good job. So this is the mission guys we want. participants To become a lava network provider. He can be any network. And as long as it's deployed on a cash. And you run it. + +Robert Del Rey: You will get this price. Let me give a little context for lava. Maybe you heard about lava, maybe not so let me provide you a little context. So lava network is like an RPC Network. So the promise is that you can become an obviously provider for any let's say you want to provide services for Solana. And you can have that on lava if you have that provider on lava, you will get lava tokens and you can do that with. I don't know a few networks. I've seen ethereum Solana and a few others. So basically this is going to require more effort guys. But you can get double rewards you will get rewards from the Akash side as you can see. The reward is 50 AKP. You heard that right 50. + +Robert Del Rey: or 500 XP points + +Robert Del Rey: So you might need to get into lava Discord. You might need to get into a cash list to ask questions. You might need to get extra documentation. But we want you. To make this as well as it works. We don't care how you do it right just follow up the instructions here. the first requirement says use your creativity as long as your bill integrates, the two networks. The submission will be good. I'm not saying it's gonna be a truth right away, but it's gonna be with for sure. So again, you become a lava Network provider of any support chain that they have and you host that on a cash and you will win. Let me see that. A brief second and go to the level documents. + +Robert Del Rey: Real quickly. So as you can see, these are the networks that they support you see Cosmos UC based acceler and most file coin. There is lower cash one though. Maybe we could do another mission about creating an Akash file for here. Who knows but yeah, these are the networks and you can provide RPC services. So we want you to get one of these. Run it. And host it on a cash for it to count. So yeah, Maybe it doesn't make sense. We want to see what you guys can build. Remember that the whole model of this new city campaign is pushing a cash to the limits showcasing the possibilities of a cash. So let's build guys. Let's feel I want to take a moment and say that if you + +Robert Del Rey: Come up with a crazy idea you want to build? I don't know feel free to reach out to us and let us know what you're building and we might create a custom mission for you so you could make 80 tokens. Alright? Remember guys, this is all about building. So yeah, I will stop right now. I already shared that two new missions with you. Hopefully that makes you want to do more missions. And Remember Sprint number two is coming on then screen number three and then it's gonna be lots. We have 25 to 30 missions so you can do it, but we're gonna do it progressively little by little so yeah, that is all that I wanted to say on this call. If I'm not mistaken. This is the agenda. Am I still sharing the screen I know. yeah, I want to take + + +### 00:15:00 + +Robert Del Rey: Sorry, I wouldn't. I want to open up for some Q&A questions or session that will be a good time and also will be enough time before Benjamin has to drop off this call, which is coming soon. + +Rodri R: That I didn't hear… + +Robert Del Rey: Nobody, that's all… + +Rodri R: what you were asking. + +Robert Del Rey: Saving the day. What's up, man? + +Rodri R: But I don't have a question,… + +Robert Del Rey: No,… + +Rodri R: but I did want to showcase one of the missions that I tried deploying a RPC. + +Robert Del Rey: are you said that? Is somebody had a question? Now it's a good time to drop your questions. + +Rodri R: I told this to then a few days ago, and I'm wanted to do this puzzle right now because I had to leave in about 10 minutes. So awesome let me see how + +Robert Del Rey: That'd be awesome to make sure sure. + +Rodri R: or for sharing the screen here + +Robert Del Rey: Can you share the screen? + +Rodri R: present now + +Robert Del Rey: You're gonna be the reactions like the Emoji. + +Robert Del Rey: it's right next to the race and… + +Rodri R: Okay. + +Robert Del Rey: In between the hand rays and the emoji for the reactions. + +Rodri R: I'll see so I already give the repo. + +Robert Del Rey: There you go. + +Rodri R: on the mission for this network of Tia, which This is just one of the ways that you can run this RPC. You can also do it with the ugly worlds option. to make this quicker I already deployed the RPC here on devnet on the sandbox As you can see, this is the same. sdl As you can find here in the repo. + +Rodri R: if this one + +Rodri R: like I said that because I have to go in a few minutes. I already did all the steps. for the Snapchat you use a snapchat to catch up quicker with the network. + +Rodri R: This one is As already changed I got you. It's a new Snapchat. It changes I guess every day or so. And here's the note running. + +Rodri R: if you see here the new snapshot. + +Rodri R: Yeah, all the instructors are in the repo. And this will work for that for other. people This will work for other cosmosis Decay based blockchains the same as the will only need to. Change the snapshot that has been used. + +Rodri R: So yeah. + +Robert Del Rey: awesome, brother Thank you so much, This looks really cool. + +Rodri R: All Awesome that then I'll be having this one too. I'll be most two two, but just wanted to share this. Other form of deploying Cosmos as the case and on a cash and yeah, everything's playing here. + + +### 00:20:00 + +Robert Del Rey: And thank you for your example. … + +Rodri R: No problem. + +Robert Del Rey: this is what we want to see in this type. Of course, we want you to step in and show us what you're building. Let me ask you Brody to make the mission better. Maybe for the participants. What do you think about the relation between the effort you did for this mission? They cost you pay and the price that you will get. + +Robert Del Rey: Do you think the prices for the process or… + +Rodri R: I really don't even remember… + +Robert Del Rey: when the new modification could be improved? + +Rodri R: what the price is, but I do remember asking you and then that it should probably be allowed to run on Sandbox. because if we have to keep the deployment going I guess for a week or two. I mean for this one as you can see it cuts. 11 on Sandbox I'm not sure probably will go about the same one. a mainnet, so That's why I rented here. + +Robert Del Rey: All right. Thanks for sharing. I guess Benjamin I can go over that and Maybe if it makes more sense to have this mission on the sandbox best to that. because I want people to get motivated for the price but Maybe the cost to do this could be an issue. So maybe the sandbox is more attractive option if you want people to test this out. + +Rodri R: Yeah. and… + +Robert Del Rey: So yeah,… + +Rodri R: I mean just I… + +Robert Del Rey: thanks for sharing an experience. + +Rodri R: I mean If I was gonna spend five akt maybe or for one or two weeks until we all can have time to review the submission. for some people might not want to leave it running I believe the price is 15 AKA or something that Excel remember it would be like you have part of the price maybe for running on Main? or at least two or… + +Robert Del Rey: Yeah. + +Rodri R: ATT Europe something that + +Robert Del Rey: Thanks, All right. + +Robert Del Rey: Let's see if any other get a topics. All right. thanks for joining then. You're right. Talk to you of line. + +Robert Del Rey: And yeah guys, I mean I run over my topics already right now. I'm reading having this call. But after this call, I will continue reviewing the content creation submissions. One of the community members I wrote those. He did a really good guy deploying Golan ethereum in the castle remember exactly what but it was very solid. Yeah. Besides that I don't have any other optic for you guys. Just thank you again for joining again. If you come up with a questions or ideas we have these per channel in a cache Discord the cash CD Channel and yeah, we're gonna meet again. + +Robert Del Rey: Next Monday at the same time and it's gonna be a few days before the print ends. Good luck for the In this first Sprint and let's keep on working guys. How about I go ahead? + +Robert Del Rey: Hey, thanks guys. + + +### Meeting ended after 00:24:49 👋 + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + From d8358b45a054d1596dca48c1fb84a10e6b79612b Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Fri, 20 Sep 2024 10:11:58 -0400 Subject: [PATCH 136/138] steering committee Update README.md added recording link for Aug 29th, 2024. Waiting on Notes and transcript. Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index edf7401f..e05e33f5 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -32,7 +32,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, June 06, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md#transcript) |[Link](https://capv32vqn7vrb5u3qvsjn3n6y6swnjkba32ukvydflmqqhrxbswa.arweave.net/EB9d6rBv6xD2m4Vklu2-x6VmpUEG9UVXAyrZCB43DKw) | Thursday, June 27, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/017-2024-06-27.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/017-2024-06-27.md#transcript) |[Link](https://upv27tytyope2fseqvgnnre2au6nmmo65bs2c2fvuxtohsr5bpjq.arweave.net/o-uvzxPDnk0WRIVM1sSaBTzWMd7oZaFotaXm48o9C9M) | Thursday, July 25, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/018-2024-07-25.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/018-2024-07-25.md#transcript) |[Link](https://vowukrgkuwsl7fdoune7kqruamcwsbhm7bh4aic6dse6vyussagq.arweave.net/q61FRMqlpL-UbqNJ9UI0AwVpBOz4T8AgXhyJ6uKSkA0) -| Thursday, August 29, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, August 29, 2024 11:00 AM PT (Pacific Time) | | |[Link](https://7rl44hv4pys2lipofrsxd22xmnvysihwvhfn3lttrx6w47u67w5q.arweave.net/_FfOHrx-JaWh7ixlcetXY2uJIPapyt2uc439bn6e_bs) | Thursday, September 26, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, October 31, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, November 28, 2024 11:00 AM PT (Pacific Time) | | | From 3371f63806eee93c0c27d162d5ff5b284c6ba40c Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 23 Sep 2024 12:43:46 +0000 Subject: [PATCH 137/138] Create meeting notes for Sig-Design #21 (#682) * Create meeting notes for Sig-Design #21 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * sig-design Update 021-2024-09-11.md added recording link and transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-design/meetings/021-2024-09-11.md | 261 ++++++++++++++++++++++++++ 1 file changed, 261 insertions(+) create mode 100644 sig-design/meetings/021-2024-09-11.md diff --git a/sig-design/meetings/021-2024-09-11.md b/sig-design/meetings/021-2024-09-11.md new file mode 100644 index 00000000..994586f2 --- /dev/null +++ b/sig-design/meetings/021-2024-09-11.md @@ -0,0 +1,261 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #21 + +## Agenda + +- Website updates and issues +- Recent and upcoming events +- YouTube working group update +- Zealy missions update + + +## Meeting details +- Date: Wednesday, September 11, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://rb6ghk5hubdwgm4s2todp2hvnwi55k6mtld6kyrrp222miwf7a6q.arweave.net/iHxjq6egR2MzktTcN-j1bZHeq8yax-ViMX61piLF-D0) +- [Transcript](#transcript) + +## Participants +- Denis Lelic +- Robert Del Rey +- Tyler Wright (mentioned, not confirmed as speaking) +- Copeland Bomzy +- John Doe +- Jovan Popovic + + +## Meeting Notes + +- Denis Lelic reported on website progress: + - Several website issues have been resolved + - New Pull Requests are in progress to enhance user experience + - Link to Akash network repository issues was shared in the chat for reference + +### Events Update + +- Denis Lelic provided an overview of recent and upcoming events: + - Korean Blockchain Week was held in early September + - Token2049 in Singapore is scheduled for the upcoming week + - Massari and Rey Summit are planned for the end of September + - Permissionless and Cosmosverse events are scheduled for the following month +- SIG design has been actively supporting these events by providing: + - Merchandise + - Giveaway items + - Booth designs + +### Swag Shop Redesign + +- Denis Lelic discussed plans for updating the Akash swag shop: + - The shop will continue to use Shopify as the platform + - Plans include refreshing the available items + - A theme change is being considered to improve visual appeal + - The overall goal is to elevate all brand touchpoints + +### YouTube Working Group Update + +- Robert Del Rey presented progress on the YouTube initiative: + - Demonstrated a new video thumbnail and intro design for Steering Committee calls + - Current focus is on uploading and formatting Steering Committee call videos + - Plans are in place to upload 3-5 videos with different concepts (currently set as unlisted) + - The working group includes Robert, Tyler, and potentially other members + - Future phases will involve expanding to different types of video content + +### Zealy Missions Update + +- Robert Del Rey provided an overview of the new Zealy initiative: + - A new mission called "Akash Swag Designer" has been launched + - The mission offers rewards for up to 10 winners + - Each winner can receive 15 AKT as a reward + - As of the meeting, 86 submissions were pending review + - Example submissions were discussed, highlighting quality and creativity variations + - A new rule was added: "AI generated content submissions will not be accepted" + - Community members are encouraged to submit original, creative designs for various merchandise types + +### Community Engagement + +- Denis Lelic noted increased community participation: + - Various working groups have seen growth in member involvement + - Community members are actively contributing to solving issues and improving the ecosystem +- Upcoming working group meetings were announced: + - Akash Website working group meeting scheduled for next Thursday + - Zealy working group meeting planned for next Monday + - YouTube working group meeting set for next Tuesday +- A link to the Akash community calendar was shared for easy access to meeting schedules + +## Action Items + +- Denis Lelic to review and provide feedback on Zealy swag design submissions +- Robert Del Rey to continue overseeing and developing the YouTube and Zealy initiatives +- Denis Lelic to finalize designs for upcoming events, including Token2049 and others +- SIG design to continue supporting upcoming events with necessary design assets +- Consider adding a clear statement about AI-generated content not being accepted for Zealy missions +- Explore options for updating the Akash swag shop website + +# **Transcript** + +Denis Lelic: Hey, everybody, and welcome to. Today's Sick Design meeting SIG design is a special interest group dedicated just for design related things. And we meet on a monthly basis, where we discuss everything. Design related that's happening around Akash network. So just as usual I'm just gonna cover a couple of things that were happening in the past. So + +Denis Lelic: Some website issues. were assault and we have a couple of new PRs that are kind of just one second. I just want to share the + +Denis Lelic: just wanted to share the link to the old issues, so some of the issues already have been solved and we have a couple of new PRs that are hopefully gonna enhance the user experience across the website. So anyone who's interested or who might be looking at this recording, I dropped the + +Denis Lelic: Akash network repo, and link to the issues. So, please have a look. The next thing would be events. It's been a busy month for events. A lot of them happening this September. so, + +Denis Lelic: some of the core team members and as well community members were attending Korean Blockchain week in the beginning of this month. And next week, we have token 249 happening in Singapore and the end of the month, there's Masari and Rey Summit happening at the same time. So sick design, kind of supported all of these events with either, merge, giveaways, booth, designs, anything. Basically that's been requested by Events So yeah, using month ahead and as well. Next month, there's going to be + +Denis Lelic: Some events as I think Permissionless and Cosmos are happening. So yeah, a lot of work has been done on that front and while I was talking about the website I just realized I'm missed one thing and hopefully we're going to cover that. In the next month and that's the Swag shop redesign. So I'm thinking we're still gonna use the shopify. We're just going to update the items, maybe change the theme to another one. Make it a bit more visually pleasing. And yeah, we're just trying to elevate all the brand touchpoints. + +Denis Lelic: I'm home. Okay, The next one, we covered website. We covered events. But I want to hand it out to Robert and Robert was involved in a newly formed group Akash, YouTube working group. And another one, which is working for easily and Robert's been pretty much Involved there and leading the whole thing with Tyler, I guess as well. So both of them are here. If you guys want to talk about it, please go ahead. + +Robert Del Rey: Sure, thanks. Denis. Let me start off with YouTube. + +Robert Del Rey: so, Let me share my screen. I speak better visually. Let's say I would recover Dennis if you don't mind. + +Robert Del Rey: So here you can see the YouTube studio for a cast YouTube channel. This is a video I uploaded yesterday just to see how the designs would look in YouTube and in the screen. So, first off is the thumbnail. So you can see, it's very simple talking about the steering company. Call number one in that India, Cash logo. I don't know if I can. Put it bigger. it's a bigger there, so yeah, really simple. But the magic is, when you click On this video to watch it, let me open up on your tab now. This is typical video. We try to put up together an intro card about these. + + +### 00:05:00 + +Robert Del Rey: About these calls or this kind of videos, so this one specifically for You say a steering code, you see a steering comedy. And also says, Community call and the date. Since it's a monthly called, BS and I picture out to be as by the way, is also helping a lot with this. I'm just putting it together, but he's the guy living in the feedback and everything + +Denis Lelic: Hey, Sorry to jump in. + +Robert Del Rey: What? + +Denis Lelic: Can you just switch the tab? + +Robert Del Rey: man, I'm so sorry. Thank you for flying then it's one second. No, what happened there? I just share one tablet, specifically instead of the window. This question should work better. Let me know when you're into the YouTube video. + +Robert Del Rey: Okay, infinite mirror with one So as I was saying Yeah the thumbnail is super simple. When you click it, it jumps kind of the same thumbnail. Just with this information is different. It says, Community calls. It's monthly. We just added a month in the year. This one was the first call. Ever. I don know I don't see the description here, but I will go into Latina second. But yeah, when you click on next, we transition today, + +Robert Del Rey: I hope you were able to hear that. So yeah, it's we can simple intro, the five seconds and it jumps right into the call. I actually edited a little bit because the recording has started and then it was just like saying You want to take it off on you. So the yield right into these. I guess this is more related to the YouTube working group called. This Is Not much related to designs. But yeah, I just wanted to show off a little bit, the design for this kind, of course, and that thumbnail. And the other one is about Seeley. Maybe if you have questions About YouTube, we can answer those. And then we can get to see. + +Denis Lelic: True. Thanks Robert for sharing that. Are you planning to do more videos? Not just the steering committing. + +Robert Del Rey: In the next places of this program, we definitely want to Upload more videos and different kinds of videos. But at the moment, we're working in these stating community called videos, specifically So yeah, next week in the YouTube working group called It's Next Tuesday, I guess we're gonna go over that and see the next steps At the moment. I'm planning to upload three to five videos with different ideas These videos are only listed so nobody else can see them. Yes. Just And yeah that's basically hope I covered your question, man. + +Denis Lelic: Yeah, For those who, Were not able to attend these meetings. So, part of the working group is you Tyler I guess as well. Yes, I know he was involved in creating the graphics. So anyone else you want to mention? + +Robert Del Rey: Probably as well. he joins The YouTube called many calls and usually, we have one new community member going in and looking around. so yeah, that's basically + +Denis Lelic: Sounds good. Yeah, I've been pretty busy with just designing some of these events stuff lately. But I think what the most attention is gonna for this month, There's gonna be around. I pretty much wrapped up token, funny, 249. So I'm just waiting to finalize some things for the sorry and I'll join as well. I want to be part of that group and hopefully I'll attend more meetings. So sorry for not being there. + +Robert Del Rey: A certified and + + +### 00:10:00 + +Denis Lelic: Yeah. We can move to Zealy, I guess, unless Tyler has something to say, but + +Robert Del Rey: I see thumbs All right. Thanks. + +Robert Del Rey: I will take over the screen again, then It's used to thank… + +Denis Lelic: Sure, go ahead. + +Robert Del Rey: It's just to show off the Cash slug designer mission to give a little context on city for those listening. The recording. This is a community initiative, and we basically have missions to Motivate People To get involved in the different areas of a cache. There are missions about building on a cache deploying a stock on a cache. Creating Content of Arakash and now we're doing something new. And it's about having the community members design. the cash swag, we want to see their talent. So we came up with this, mission up to 10 winners. We'll wait this + +Robert Del Rey: and yeah, there is a 1580 rewards, so we had a few. You can see here, we have five submissions already for this missions. Maybe we can go over them and so you can have a look and stuff, be awesome. If you can have a look to this missions. + +Denis Lelic: Yeah, please share. + +Robert Del Rey: Go let me filter here. You can see we have 86 mission spending review so it's really easy, we're happy for that. So I really** filter Give me one second. + +Denis Lelic: Sounds good. + +Robert Del Rey: On the same side. So I designed okay. + +Robert Del Rey: Viewquest claims. All right, as you can see, we also are prone to having a spamming submissions. You can spot them. Maybe right away like This is not even on a T-shirt. So yeah. + +Robert Del Rey: we're talking for example in the mission description, we told people that They can design, whatever. As long as it's appealing, right. But they can create T-shirts, stickers, hoodies, and any other form of merchandise. So get creative. So yeah, this is the last submissions we got so far. It's a mall Apparently. They can upload up to five images of their designs. Believe that something good to know. + +Robert Del Rey: Here says they're all around some computer. But I Wrong on coffee, whatever. But you run on coffee, I guess. I don't know if it's a cash we want some coffee or maybe both. Okay, I can see here. I catch No, that's nice. yeah, I it. I would post possibly maybe reject this one. And let's see what we have here. Okay. + +Robert Del Rey: I can give you access to this Denis and you can specifically review the missions yourself, although I know you are super busy. so, + +Denis Lelic: Yeah, I can have a look, although this one is AI, so I'm not sure if we should take any AI submissions. + +Robert Del Rey: Yeah, that one. It's Super Ai. I believe I should add that as I said that I really first,… + +Denis Lelic: Yeah. + +Robert Del Rey: the only one I missed. No Ais stopped. + +Robert Del Rey: All right, then we have here. Okay This is a high as well but it looks a bit better. The letters,… + +Denis Lelic: Yeah. + +Robert Del Rey: give it away, always for me. + +Denis Lelic: The thing is we can't use these as printfiles to producing anything anyway. So + +Robert Del Rey: These are the example of his family submissions, they really like we don't read. + +Denis Lelic: Yeah. + +Robert Del Rey: This was first of the first submission we got. It's a very simple bank. I don't know if I love it. But I kind of like it. + +Denis Lelic: Yeah, simple, but it works. + +Robert Del Rey: Let's actually so yeah, that was sort of designs, feel free to drop your ideas. maybe if you have ideas about designs, you can drop them in the designs working group shots. maybe that way Denis, it's easier for you to maybe have a look. If questions are posted in the designs questions, right? Well. + +Denis Lelic: Yeah. + + +### 00:15:00 + +Robert Del Rey: You're? Briefly. + +Denis Lelic: I mean. + +Robert Del Rey: Go ahead and + +Denis Lelic: Yeah, yeah. What I would add maybe just like a one sentence that says something about. + +Denis Lelic: AI generated graphics. So I believe some of them would be good, but it's kind of hard to reproduce them. It's either low rest. there's no vectors in there. So to print them on a certain application. I've T-shirt up or anything, so maybe just some one sentence. That's kind of like Mentioning that we can't accept AI. And generated graphics. + +Robert Del Rey: You guided Man, your wish is my command. I just added AI generated content. Submissions will not be accepted. Really. That's your work. + +Denis Lelic: Right. + +Robert Del Rey: I just added to the mission right now + +Denis Lelic: Maybe we can just do a shout out in sick design. If anyone is willing to join And do some of these. + +Denis Lelic: I'm missions, I guess. + +Denis Lelic: They're cool. + +Robert Del Rey: Sounds good. + +Denis Lelic: Yeah. + +Denis Lelic: Yeah. + +Robert Del Rey: Then it's what one last thing since I have the mic already. Let me reveal the secret call for this meeting. in most of the working group calls, we have a secret word, which you can Add to a cash ceiling for a chance to earn extra points or extra 80s. So the secret word for the design Seek call it sgger. You can listen it now or in the recording and enter Swag Swag. And you can get extra points on City. + +Denis Lelic: Should it be capitalized or… + +Robert Del Rey: All right, that's all for me. that is thanks again. + +Denis Lelic: lowercase? Doesn't matter. + +Robert Del Rey: No matter. + +Denis Lelic: Okay, Yeah, thanks Robert for all the updates. A lot of the work you've put in both of those groups. So we appreciate you. Since a lot of team members have been traveling in the previous week, some of them are still traveling either back home or to the next events. I suggest I keep this meeting a bit shorter than usual. + +Denis Lelic: maybe a call to action to join working group meetings for either YouTube website is something as well. There was a lot of participation. In the previous meetings, We have a lot of new community members that are willing to contribute in either. So many new issues, fixing some of the stuff on the website, It's happening as well on the console side. the product side. So I know a lot of people are not in this meeting, but if anyone's listening or watching this recording, just want to thank you for + +Denis Lelic: Either participating in the meetings or just trying to solve some of these issues. So, yeah, communities not just growing, but being just actively involved in different kind of groups. Let me just see when is the next meeting happening for the poor green group. and yeah, next Thursday, there's a working group meeting happening for + +Denis Lelic: Akash website. there's a working group Zealing meeting happening next Monday, And Akash YouTube meeting happening Tuesday. So if anyone is interesting to join any of these meetings, let me just share the calendar really quickly. + +Denis Lelic: So I drop a link right here in the Chat section. When you click on it, just give it a little scroll and you'll see the Akash community groups and the calendars. So you can also subscribe to the calendar. So you won't miss any of these meetings. + + +### 00:20:00 + +Denis Lelic: So Thanks for joining today. We'll see each other either on discord or github or many different channels we use. So, thanks again for joining. And I appreciate you. + +Denis Lelic: Have a good day, bye-bye. + +Robert Del Rey: Things that stay safe, guys. From a4a3ca9f961ee73e37ea2b16b2080c838f2d4ca4 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 23 Sep 2024 13:02:27 +0000 Subject: [PATCH 138/138] Create meeting notes for sig-community #19 (#683) * Create meetig notes for sig-community #19 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * sig-community Update 019-2024-09-10.md added recording link and transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-community/meetings/019-2024-09-10.md | 350 +++++++++++++++++++++++ 1 file changed, 350 insertions(+) create mode 100644 sig-community/meetings/019-2024-09-10.md diff --git a/sig-community/meetings/019-2024-09-10.md b/sig-community/meetings/019-2024-09-10.md new file mode 100644 index 00000000..e4b2d771 --- /dev/null +++ b/sig-community/meetings/019-2024-09-10.md @@ -0,0 +1,350 @@ +# Akash Network - Community Special Interest Group (SIG) - Meeting #19 + +## Agenda +- Updates on team activities and reflections on recent events. +- Discussion of strategies for hackathons and potential sponsorships. +- Review of updates for the community and insider programs. +- Overview of upcoming events and establishment of working groups. +- Open discussion on structuring event sponsorship proposals. + +## Meeting Details +- Date: Tuesday, September 10, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://7m4voozzewq7nnzhoteyc7zbeuvc72pb2fpou57f72etmypu7ulq.arweave.net/-zlXOzklofa3J3TJgX8hJSov6eHRXup35f6JNmH0_Rc) +- [Transcript](#Transcript) + +## Participants +- Adam Wozney +- Amanda Keay +- Tyler Wright +- Andrew Gnatyuk +- Fenil Modi +- Maxime Beauchamp +- Richard Genis +- Robert Del Rey +- Zeke E +- Neta DAO Academy +- Poroburu +- Joao Luna +- Dimokus +- 亀人小河 + + +## Meeting Notes + +### General Updates +- Adam Wozney returned after a long break and acknowledged the excellent efforts by the team during his absence. +- Adam highlighted the need for updates on hackathons, community engagement, and proposed improvements in the insider program. +- Adam briefly mentioned the goal of restarting various initiatives, such as insider discussions and hackathon planning. + +### Event and Hackathon Updates + +- Amanda Keay provided a summary of recent and upcoming events: + - Korea Blockchain Week was successful in boosting brand awareness in Asia. + - The team is gearing up for Token 2049 in Singapore, including hosting a summit that will showcase product demos and integrations with Akash. + - Massari Mainnet in New York is also a key upcoming event, where Akash will sponsor the main event and host side events. + - Participation in Cosmoverse in Dubai will round off the month, with a focus on blockchain collaboration and community outreach. + +- Tyler Wright expanded on hackathon strategies: + - Encouraged participation in planning for next year's events. + - Shared insights on trial wallets and fiat payment testing for the Akash network, which will enable more diverse event participation. + +- Fenil Modi outlined plans for the Hack the Mountain Hackathon in India: + - Fenil proposed including Akash in the prize pool and distributing swag at the event. + - Plans to manage an Akash booth and engage with participants by collecting emails and hosting discussions. + - Highlighted the need for Akash’s presence to ensure a connection with the developer community and broader engagement. + +### Community and Insider Program Updates +- Tyler Wright gave an update on the Akash Insiders program: + - Emphasized the importance of active participation in Discord and other community platforms for those seeking to become insiders. + - Encouraged community members to contribute to Akash’s ecosystem to be considered for insider status. + +- Adam Wozney shared future plans for the insider program: + - Adam plans to relaunch and improve the Insiders program to better support community members and foster deeper engagement. + - The upcoming changes aim to streamline activities, refine requirements, and enhance support for individuals contributing to the network. + - Adam plans to gather feedback from existing insiders to ensure the next version of the program meets community needs and expectations. + +## Action Items +- Fenil Modi: + - Prepare a detailed document with cost breakdowns and expected outcomes for Akash’s sponsorship at the [Hack the Mountain Hackathon](https://hackthemountain.tech/). + - Include details about the booth setup, prize distribution, and participant engagement strategy. + - Share photos and insights from the event for social media and potential blog content. + +- Adam Wozney: + - Develop a standardized framework for future event sponsorship proposals, including hackathons, to streamline decision-making and funding requests. + - Organize a working group to finalize plans for the next hackathon and improve the Insiders program. + +- Tyler Wright: + - Oversee coordination for Akash’s sponsorship at Hack the Mountain Hackathon, working with Fenil on execution. + - Work with community support to finalize and approve sponsorship funds. + +- Amanda Keay: + - Continue to manage logistics for Token 2049 and Massari Mainnet, ensuring Akash’s visibility and engagement at these global events. + + +# **Transcript** + +Adam Wozney: Know what's going on? Still half. The team is traveling for all the events happening in September. So catching up with them. It's kind of like sending a message to Mars and waiting + +Adam Wozney: A 24 hour to get a response because everybody's in different time zones So I'm like way I don't know what's going on right now. I'm just trying to do some stuff trying to get my head back into the swing of things So Tyler Robert you're absolutely right, I'm rusty. But yeah I mean I created a very simple agenda really. I was gonna lean on maybe Tyler and I see it. Thank you Amanda for joining the call because I think you guys have a lot more probably to cover or updates on your guyses. but what I wanted to do today was have Tyler and Amanda Quick give their kind of quick updates. I want to spend a majority of the time just kind of hearing from y'all on how things have been going. I've been away so maybe some things that are working, some things that aren't working. I'm planning on doing some one-on-one insider calls for folks that are watching the recording that aren't insiders. It's our kind of ambassador community, it's like people on the tip of the spirit of the Akash, I don't know. We want to call + +Adam Wozney: on war for depend. So, I want to kind of give a little bit of updates on an insider framework. That I've been thinking on while I've been gone for the past two and a half months. And then I wanted to briefly talk about potentially an upcoming HACKATHON, or maybe even series of hackathons. I know we've done them in the past. We're starting to sponsor some hackathons, but I'm just thinking through what are Hackathon kind of strategy. Could look like on the community side and how community members can get involved or just be updated on what's going on there. But, that's really kind of my very rough agenda for the day. Is there anything anybody else would want to cover? feel for your raise your hand. And I'll add it to the agenda here today. + +Adam Wozney: No. + +Fenil Modi: Yeah, yeah, I have talked about this thing about food trailer. There is one. HACKATHON happening in India, called Hectic Mountain, instead of fifth season, and I was a participated as a hacker, but I thought should be part of the second one. So, I asked to Taylor to some kind of sponsor this packet on yeah,… + +Adam Wozney: Cool, I'll add all that to the agenda and… + +Fenil Modi: you said + +Adam Wozney: we can cover what that looks like. + +Tyler Wright: Yeah, that was a part of my talking points that I was going to go through. + +Fenil Modi: yeah. + +Tyler Wright: I was gonna talk about that and then I was just going to talk a little bit about some working groups that I think will come out of this. And then I was going to hand it over to Amanda to talk about events. So that was the only thing I was going to cover. + +Adam Wozney: Go forward. Tyler, you're up. + +Tyler Wright: again, much appreciate everybody joining here today. I'm very happy to be in the process of handing this all back to Adam while he was gone, much appreciated. Everyone's participation we've talked about everything from Zeely to potential events As we look ahead to 2025. Amanda's done, a great job of giving us updates on all the events that we've been participating in through the summer, while Adam's been gone, there's been everything from all the events happening in Brussels, to, just a number of things that have happened to Buenos Aires Korea Blockchain week, which I'm sure she'll talk about a little bit and then look forward to some of the event. So I know Amanda's been a woman on fire, going all over the world and just raising awareness and just like having kickass events on behalf, the Akash network much, appreciate all the insiders that have also been participating and supporting as well. + +Tyler Wright: Major shout out to Domi, who I know is been participating with the career blockchain week, as well as token. 2049 has been instrumental in helping out with some of the merch and some other things as we get ready for those events. But real quick, I'm just remind folks as we move into the next couple of weeks, if anybody has any potential of events that they want to talk about for 2025, I think we'll start to put together a working group Adam will leave these efforts maybe over like October or November to start to think about planning because I know we'll start to put up props for 2025 at the end of the year. So we'll have to get that kind of stuff, ready, I'm sure there's a lot of learnings that we have from this past year. So I just want to again just get there to participate. + +Tyler Wright: there again, Adam talked about the insiders I dropped in a note for the insiders program as for those that want to apply, again, while Adam's been gone. I've been looking at applications and just reaching out to folks that I think kind of meet the criteria. I know there's a number of folks that apply, but again continue to look out for emails from myself, for Adam, as we move forward, for those looking to get involved, but it is a highly scrutinize and very elite group that I cautions either so that for those are looking to participate but they haven't participated or even got an active and discord. I think that's a good way to show your involvement in the community for entire application is when one of us looks at your application, looks at your discord and can see you actively in the discord, a cost just court commenting on that goes a long way. but again one + + +### 00:05:00 + +Tyler Wright: Of the programs pun intended, Akash insiders is the ringmasters program. I think that's something that Adam has been thinking about, in will continue to fine-tune, but I know that Fenil who had just mentioned a little bit. Again, Fenil came in through the Akash HACKATHON 2. This past year was a winner of, I think a prize, I think for a second or third place, correct me from wrong. I might even first place. But again, came into the cost. Hackathon, had joined the insiders because he wanted to get more involved in on the cash project. He led Akash hacker. He let a HACKATHON this past summer called the Spark HACKATHON. Where, a lot of people use Akash Piyush who is insider and community member gave a talk at that HACKATHON. We've got some email lists that we've collected from. + +Tyler Wright: Hackathon from I think over 1500 registrants but I know Fenil has another potential HACKATHON that he wants to participate in on behalf of Akash that's coming up in the next couple of weeks. And so, I thought it might be good for him to talk to the community here about what the HACKATHON is and what is exactly looking for. And then, from there, again, I was going to pass over to Amanda to talk about some of the events, like Korea and making token 249. And then finally, just get out of the way for Adam, to take it over But before I hand over to Fenil, I see Amanda's hand up, so Amanda go ahead. + +Amanda Keay: Hey, I have to actually go and pick up my daughter from school. So do you mind if I do my events update right now? Instead of second, Okay. Apologies. + +Tyler Wright: Of course. Sorry. We'll get to you right after. + +Amanda Keay: So as Tyler was saying, We have been all over the world in the last few months. the team just most recently got back or some people are still over there at Korea. Blockchain week, It was a really good success. We had a couple of events that we were sponsoring ourselves as well as sponsoring. We sponsored the main conference and had a lot of good feedback. From that some good connections. I think one of our key takeaways was just improving our brand awareness in Asia. So that's something that we're looking to do even in Singapore next week as well getting connected with more. + +Amanda Keay: Different avenues and things that we don't normally think about when we are doing events over here in the Really good from what I've heard from the team. I think everyone is still kind of recovering and getting ready to hop on planes in the next two days to go to Singapore. So yeah, token 2049 is Everything starts next week and Akash is doing if you're following the main socials, which I'm sure everyone here is. We're hosting an powered summit, which is going to be similar to Akash accelerate. It's just gonna be four hours Shorter just very high, level panelists and speakers coming and doing mostly product demos and presenting using a projects that are using a caution the integration. So we are excited for that. It's gonna be happening on the 17th. + +Amanda Keay: Greg has a couple really awesome opportunities to speak on the main stage at Token 2049. So we're excited about that. And we're gonna get a lot of coverage there as well as sponsoring the main event and participating in 22, official side events. So we are crazy. And I think everyone on the team is gonna be just, hitting the ground running and thank you for all the insiders that are coming and looking forward to meeting you guys next week. I actually start hopping on a plane on Thursday, so I am really excited for that and then we get a little bit of recovery after token and then we're hopping right into New York City for Massari Mainnet, which is happening. The end of this month, finishing up our pin summer series and have a really great lineup of panelists and speakers. Yes, Tyler. + +Tyler Wright: Sorry, I was gonna let you finish and then I was gonna add something, I just didn't want to go ahead. + + +### 00:10:00 + +Amanda Keay: Yeah, no problem. so yeah we're sponsoring them the main event at Massari doing some side events and then we're also participating in Cubesummit, which is the day, right after? Sorry Mainnet. And it's hosted by the Yale Blockchain Club and a lot of different blockchain. University Club members and speakers are coming and presenting there, which gives us an opportunity to get connected into those universities and hopefully talk to people who are looking to use really excited about that. And then Just I mean very briefly. We have so much going on. We're gonna be in Permissionless a couple weeks after that heading over to Dubai for Cosmo, verse the end of the month in October. And then I think we have a little bit of a breather in November so excited for that as well. But yeah, I have been putting some high level event. + +Amanda Keay: Bullet points in some of our channels, happy to do some more on Github. And if you guys have any questions, I'm here and available. what is it called? I'm not on discord as much as I should be. It's one of my social medias that is a good so many other. As you can see, I'm sure you can hear everything at my house right now is blowing up with messages. So yes, I will promise to get back to you if you have any questions. I think that's it. + +Tyler Wright: The only thing I was going to add is I know that folks like Max who's on this call and a couple other folks will be a race summit. This is a little bit of Alpha but it's also on the record, which is dumb. But I know that the product team which Max is instrumental to folks that are helping to build a console. There's been some testing around trial wallets. I know at a HACKATHON just last month, Hack, India there was some testing around trial laws through console + +Tyler Wright: I know that the consult team is working very, very hard by the time I'm sorry, I may net and the race summit Expect Fiat payments, also be available via console. So that's something that's being actively tested. Right now. As far as again, we move into the end of the month. consoles should have fiat payments again, there'll be some testing over the next couple of days weeks to make that available. But then again, as we think about 2025 events and where we want to be, I know in the past we've shied away from some of the non crypto events, because it's been hard for people to abstract the way that layer. But again with Fiat payments coming to console. I think that's going to open up a number of new opportunities for where we should go in 2025, but again, Max B and some others from the core team and Logan from other members of the community will be at Race Summit directly prior to Massari main net. So just want to shout out those things and just shout out again. + +Tyler Wright: To Amanda and all that she's been doing to organize lead some of these efforts, bring people together and put on some of the best experiences. shout out to Amanda but look to get involved in that working group around an event 2025 which I'm sure will be forming over the next month or so any ideas can go in discord prior to that, though. + +Adam Wozney: I think that. Thank Anything else Amanda before you have to jump? + +Amanda Keay: No, I think that's it. Thanks, Tyler for mentioning, Rey summit. It was one of the ones. It was happened to be the exact same time as Massari, but yes, we are going to be there as well. No, I think that's it for my end. Thanks. Adam. + +Adam Wozney: Thank Tyler and Amanda. Let's move on to finale. I want to make sure Am I say your name right? Fenil. + +Fenil Modi: Yeah, it's absolutely yeah. so, + +Adam Wozney: Excellent Yeah, give us a kind of a overview of the hack, the mountain. + +Fenil Modi: Yeah, so I have set the link of the modern website so they are organizing HACKATHON and this is the fifth season of that. I have a direct one in the last year, so it's all the excellent and the most of Indian tech projects or came out from this HACKATHON. And this year, they already go to six hours, 6500 position in the second one, and it will be a hybrid board. So there will be a 400 folks in person and other will be joining from online. So I will be going there in person and I think I should be one of the high school money and I guess would be a part of the second one. + +Fenil Modi: but I have approached them. So they said they are closed their initial for a sponsors and all. So I have convinced them to add a cash to be in their prize pool so there will be okay and they are saying Make some kind of amazing and cool, good stuff. Just soak Can be a price would. So I have talked with them and I have added if the game name let me talk on. Have you heard anyone? Candidates. It is a trending game so it was a many hype came and currently it is trending. So the price will be added up from the Best hack from Akas and for the person and for them online. So there will be a two prize money going from August. I have connection to them so I like to have in there. + + +### 00:15:00 + +Tyler Wright: Can you drop in the game that you were talking about? And then I know you were talking about adding a prize pool for a cash. + +Fenil Modi: Yeah. + +Tyler Wright: I know it'd be interesting to know… + +Fenil Modi: it's + +Tyler Wright: what you're thinking that prize pool would be, and then I'm sure members on the call here, members of community would be interested in for class I guess sponsoring a potential track. + +Fenil Modi: yeah. + +Tyler Wright: What does Akash sketches akash get a number of emails? What other opportunities are you going to be speaking on half of Akash and then be introducing people and walking people through the experience? Just a couple more details on the value ad for the Akash network and the community would go a long way and especially again, what the potential? Akt amount that you're interested in again, having a cost sponsor. + +Fenil Modi: Yeah, sure, So basically they close the sponsory sponsor industry as I said. So they would be not give us any kind of email of the participant but they will give a good space for a showcasing arcus as well. And I can promote archas of You having some kind of a panel discussion throughout you can say. So I pass what is going and all and how does helping in community, and that's how it does. And I can collect emails, who are the station for the akas specifically, and I can communicate with them and I can forward our custom community. + +Tyler Wright: Cool arm. Then I understood that I did not hear a Akt amount, but maybe I'm Yeah,… + +Fenil Modi: Yeah, so yeah, yeah. … + +Tyler Wright: you're fine. + +Fenil Modi: sorry, sorry I said but they send me that. Yeah. You cannot big charge up of money from the sponsoring apart because I have guys cannot sponsor this hackathon. So the kind of the steam key price is the $50. It can be equivalent to 24, 25 18. + +Adam Wozney: Wait, so we can't sponsor it but we can sponsor it. + +Fenil Modi: Yeah. Now we are not sponsoring but we can be a community partner. Yeah, we can,… + +Adam Wozney: I see there's a community partner section. + +Fenil Modi: we can add some kind of price pull up in that. + +Adam Wozney: Got it. for 50 US dollars which is 23 or 24 Akt. + +Fenil Modi: Yeah. + +Adam Wozney: It'll add as a community partner and then + +Fenil Modi: and we have also promote why our specs swag distribution so that will cost around the kind of 150 150k. + +Adam Wozney: Do we get? And then you said that you would be kind of the Akash representative there. + +Fenil Modi: Yeah, yeah. So we have to install a booth and all + +Adam Wozney: So there would have to be a booth as well. Got it. + +Fenil Modi: Yeah. + +Adam Wozney: How much is the booth cost to put together? + +Fenil Modi: so the both will be caught out to nothing but the license and sticker will be pushed around, all things will be managed in the 158 + +Adam Wozney: Got it. Do you have a dock on Github that you propose this or is this? You've only brought it up with Tyler and Dms and then in the call right now? + +Fenil Modi: No, I don't have anything like but we have done in VMs. It's better. + +Adam Wozney: Got it's coming up pretty quick. It's in,… + +Fenil Modi: Yeah. Yeah. + +Adam Wozney: what is it, three or three days? the sponsorship amount. I think we could pull from bony funds. I don't think anyone would be upset by that because I think it's still beneficial to a caution that's not an issue. I think it' be Here's what it's gonna cost to know be listed as a community partner. Here's the cost for a Here's who's going to manage that booth and their understanding of basically like a one sheeter, just a document that lists Here's how much it's gonna cost for each item, Here's how I'm going to manage each item and then here is what we can expect in terms of outcomes. I'm no, we're going to be able to collect, 50. + + +### 00:20:00 + +Adam Wozney: Emails from this that we can follow up with participants our sponsored track for example,… + +Fenil Modi: Thank you. + +Adam Wozney: it sounds like we get a sponsored track, that's part of it as well. Cool. So the sponsored track. + +Fenil Modi: Yes. + +Adam Wozney: I would like to know, what it is. We're at requesting people to do because there's a lot of different things that people could contribute to on the network, could be helping people become provide Could be helping people. Deploy could be contributing to cosmos omnibus on Github. It's just like knowing exactly what we're wanting them to do. that needs to be kind of sorted out. Because my fear is we responsor an event and… + +Fenil Modi: Okay. + +Adam Wozney: we just kind of throw money at it but it's like how is it supporting the ecosystem and the community just like something like that is listed out on paper. + +Adam Wozney: and a little bit more detailed than we got the akash logo on billboard that's boring. It's like, we're gonna be able to help 25 university students, deep dive into Akash through a workshop and here's the RSVPs to that workshop. That's interesting. So basically if you can create a pretty simple one-page document. That's Here's how much it's gonna cost to be listed as a community partner. And what that means what a community partner gets or what that means is it just a logo on the website? Or do we get branding? Is it a five minute talk up on stage. So, really just kind of listing out, all the things that are required from us to give and then what the expected, outcomes of it will be, I think listing that out. I think we can make a better case for, getting the resources. I don't think it should be an issue because it doesn't + +Adam Wozney: Gets that much. Compared to a lot of the events that were participating in but there still should be something that says Here's what we should do. And as we've been talking about this, I've been thinking it seems like while I've been gone and even right before I left, we started getting message by different individuals looking to get sponsorship dollars from us. Not just hackathons, but events in general. Tyler maybe something we can rough draft and then bring up in the next Sig community. Call is onboarding basically an application like you want a cautious sponsor your event, + +Adam Wozney: Give us your email. How much is sponsorship? Give us your deck and what we would get out of it and then we will review and follow up if we think we can plug it into what's already been approved As a part of the HACKATHON governance proposal budget, or the events, proposal budget, from the community. I think that might be a way to kind of go about doing this. Andrew can't, just spend money. Yeah, I used to work and my dad's small business. So dollars and cents add up to me. So I always think that way but yeah. + +Tyler Wright: I, + +Adam Wozney: So that's my quick thoughts on what we're talking about right now. I don't know. Go ahead, Tyler. + +Tyler Wright: I was gonna say I would agree. I know that again I can speak for Fenil as an Akash insider and their community member but we did not talk about any dollars and cents. I think at this dollar amount if we just put together, the document that Adam has a quick document with some of those bullets laid out as Adam mentioned, then I think Scott, he would soon. And I can green like this from the community support budget because it's just a small amount of Akt and push it from there especially because it's coming around the corner. But it would be great to have that document just as a reference point that we can add to the bounty board to just track against the community support funds. But again, that + +Adam Wozney: I think that's the one thing. I think I'm gonna take away from this. And I agree with you Tyler because this is coming up in this, four days. I don't think there's time to kind of put together a very detailed proposal but + + +### 00:25:00 + +Adam Wozney: I think this is something that I should kind of create the community. here's what a HACKATHON proposal template looks like. And then for anyone and not just hackathon proposal, it's like event sponsorships. If you want us to sponsor something, there should be a framework for approvals for that because otherwise, it'll keep being this where it's like, Here's an event that's coming up, let's throw some money at it and hopefully something gets out of it. We need it to be framed. So that way, it filters out, the things that we know we shouldn't do and it encourages things that we know we could like the network and, benefit from. So, that's something I can do after this. I just made a note to kind of come up with, a event sponsorship, Hackathon proposal kind of a template. But for this, I think it's fine to go with it because, you mentioned Tyler. It seems like it's pretty low dollar amount. It's not gonna knock out the budget for community support that we already have. + +Adam Wozney: So I mean, for me I think it sounds cool but Tyler I guess ultimately you'll probably the one requesting the funds for this. So + +Adam Wozney: It proposal. + +Tyler Wright: No, Adam. I think that framework makes a lot of sense. what, to this point, we just been having people use github discussions and then get the community involved and then have them come to a sick community meeting to talk live to the members of the community, but I like the idea of having a framework in place for our events like side sponsorships, HACKATHON events, all that kind of stuff and having a document that we can have people reference and then once we have those things that we could talk about those things like the application kind of during the sick community call or whatever. So I think that's a great next step that we can conquer. + +Adam Wozney: yeah, I'm glad you brought up Github. I think that's probably the place to put it rather than an application form on the Akash website. Just put in similar to how we have best practices for grub props have best practices for events sponsorship, proposals, whether it's conference or a HACKATHON, so that's something I can kind of work on and then propose to the community to kind of review, poke holes in. And then once people sing cool with it, we'll put it up and it'll live and that'll be the process for kind of getting sponsorship dollars for events. I think that makes sense but because this one is on such a short timeline, I guess I've put it in your court Tyler. I don't know how to handle This, how to get it paid for and support it. Other than saying, I'm cool with it. I'm still getting up to speed on things. So Tyler, what do you think? + +Adam Wozney: You're muted. If you're talking, maybe it's not needed. while we're waiting for Tyler to respond. Maybe I'm offline. Does anybody else have thoughts on what we've been discussing? + +Tyler Wright: Sorry, I was unmute. + +Adam Wozney: You're good. Go for time. yes,… + +Tyler Wright: What would you want me to respond to? + +Adam Wozney: because this is such a short timeline and I'm not sure what next step started to help get this supported so we can kind of move it along. how are you guys doing it now is just you and Scott basically say Sounds good, Fenil, work with Tyler to kind of get sponsorship. Tyler's okay? + +Tyler Wright: Yeah, yeah, no. I'll put together a document. As you describe drop it in the sick community group. If anybody has any objections, they can make them hurt here now or they can make him hurt there. But if there's no objections, I would push to move this forward because again of Fenil's track record in the dollar amount then if there's no objections and Scott and I can coordinate via the community support and then we'll just add this to the bounty board for visibility. And Then again from there between meetings we will work on the framework for all events and HACKATHON asks as we move into Q4 and 2025. + +Adam Wozney: Cool. + +Tyler Wright: Andrew just asked if he can get photos for Neil and if we move forward with this, and you can put that document together, the more photos we can get out. That's a great action item that we can again put on social media, it would even be good if you can take some notes that maybe we can turn into a blog or something. Some sort of deliverable that we can put on the website so that would be terrific. + +Fenil Modi: Yeah, I will. + +Tyler Wright: Awesome. + +Adam Wozney: Any other thoughts on kind of what we've been discussing around this HACKATHON and kind of how we can approach upcoming potential. Not just hackathons sponsored events but just sponsored events in general. Any thoughts on that? + + +### 00:30:00 + +Adam Wozney: All right, cool. Let's see. So I think we went through everyone else's agenda items unless there's any other thoughts. I just wanted to quickly cover, we kind of been talking about hackathons already, but one of the things, I think I can kind of without needing much updates from anyone kind of get out the door because we've run them in the past and we have budget for it from the beginning of the year is another HACKATHON. + +Adam Wozney: Another cost HACKATHON. I don't know what it looks like quite yet. I don't know what the goals or the outcomes will be quite yet. The high level thinking would be around. What can we do with within the HACKATHON? Kind of framework to increase long-term deployments on Akash, get more people excited and using Akash network for long-term. Deployments not just like you're in, and you're out but things that will last So that's the high level thinking around it beyond that it's just in my brain. but I think over the next few days here, I'm going to start putting together. Some rough kind of Ideas around what this HACKATHON could look like. + +Adam Wozney: will probably end up still using door hacks as our platform for this because we have some leftover budget with them that we can use for price allotments and we still have some budget from our HACKATHON Gov property at the beginning of the year. + +Adam Wozney: So I think this will be kind of our last big hackathon for the year. We have, September so in a perfect case scenario by October. So within, three to four weeks we can have this thing actually live. I'm kind of in the idea of calling it like a holiday hackathon. It's a risk. We've never done. I don't know many people do that and I'm open to your guys's thoughts or feedback. But the idea behind this is like, Hey get away from your relatives, for a minute and start hacking do something productive. Instead of just eating turkey around the Christmas tree here, wherever you're celebrate. So we're calling maybe holiday hacks. But again this is all very much up in the air It might be worth. Setting up another HACKATHON. Specific working group call, we haven't done that in a while. + +Adam Wozney: But before we do that, I probably want to get a rough framework. Or here's the idea very high level. we're trying to get long-term deployments we probably want to do it over the holidays. Who do we want to get for What support do we need it as needed. So just kind of putting a rough framework on that and then once I have that in a good spot, I can kind of maybe set up a working group call for anyone that wants to get involved or learn more kind of understand it. And then from there, push it out the door and then hopefully sometime and October or really November, we could actually kick out our final hackathon of the year and to see how it goes. The last one I think and I'm sure Pybrid would probably agree. I think was that Much better than the first one A lot of key learning, still things that we get it done better but each time we do them. I think they're getting a little bit better time. + +Adam Wozney: So maybe for this next one it won't be as giant as the first or second one was maybe it'll be kind of a very fast quick and dirty let's put together a hackathon that's very focused on one particular item and see what people do but that's kind of the rough idea around Any thoughts on that any feedback? + +Adam Wozney: All And then the last thing is so while I was on parental leave and actually No, I won't do it. I'm gonna save an introduction to the new baby for the insiders call. So that's gonna encourage people who aren't insiders to apply. I've been thinking a lot about just the insiders program to me at the end of the day Akash wouldn't be in the kind of lead I would say within Deep End and Crypto and AI if it wasn't for the community for you guys. And for me I view the insiders program as the most important thing Akash or Overclock Labs is supporting and participating in right now. + +Adam Wozney: From creating sdxl on Akash to a cost chat to provider, support to event participation, none of this stuff would have been possible wasn't for the community at the end of the day. so I've been thinking through, what is working within the insiders program? What could we take out or remove, How can we better support individuals? How can we get more individuals to want to become part of the community? And in between changing diapers and not sleeping very much during my parental leave? That's what I was kind of thinking about + + +### 00:35:00 + +Adam Wozney: So I've been putting together over the last week and in this week since I've been kind of back a very rough idea around kind of a insiders 2.0, if you will, a reframing of what the insiders program is, How we support individuals that want to get involved activities, requirements, and kind of what that all looks like. And that goes from the top of the level. We're just like insiders. And then it goes to, the subcategories of kind of people that are a part of this all vanguards bring masters which kind of needs a bit of a revamp, because I was a way I launched it right before I left, which is probably a big mistake, but I was like, this will work. So that was my fault. so kind of just a real launch of the insiders program from soup to nuts, but I can't do that without your guys's feedback. So people that want to get involved in the program for anyone listening, that's not an insider apply and then + +Adam Wozney: Can kind of get involved in this but my goal is over the next, few days weeks here. I want to try to set up as many one-on-one calls with a caution siders as possible to kind of get their individual thoughts on what's working. Who did they like, working with? What do they want to do more of? What are some ways we can better support? What are some upcoming events that they're interested in and just kind of get general? + +Adam Wozney: By checks from all the akash insiders. And then take that feedback, and plug it into this rough framework, and then share it with the insider community for more feedback. And if people are liking it, then we kind of relaunch it. I'm hoping to get that out the door within the next, a couple weeks here. There's definitely a lot of things. I want to think through and put together before, I feel like it can share with everyone just because I want everyone's feedback and thoughts before we can kind of launch this thing but really the goal of it is now that Amanda's been here, which is honestly incredible. I'm glad she's here now. It's getting me away from events which I've mentioned many of you probably in the past that it takes up a lot of my time managing an event for anyone who's participated in any of the Akash events. I think you understand just getting swag out the door, can be difficult, just getting an event, then you lock down, can be difficult, just getting speakers and insiders that support the event. It takes a lot of time and effort. So now with Amanda who's kind of helping manage. + +Adam Wozney: That it's given me the time to rethink, how can we really scale up the Akash insider community? So that's this is kind of what I've been thinking about a lot of since I've been away. And I'm hoping again over the next couple weeks. I'll have something I can share with folks, and hopefully get out the door because I feel like + +Adam Wozney: even though I've been gone a while, I still feel like the Akash community, at least, within the deepest defense space, and maybe I'll give feedback from other people. That's not this way. I think it's the strongest community within deepen, and Besides maybe Nvidia, I don't think Nvidia has a community today. I don't know. I'll find out when I talk to you guys. So, that's what, I want to spend the next couple weeks. Kind of sorting through is How can we really support and scale out the insiders community to make a cautious? exponentially grow. And I think the hackathon that I mentioned and reframing and relaunching, insiders to point out, I think that could actually be the way to move forward. But, I won't know until I get your guys's feedback, but until I can get the feedback, I need to finish putting together. My rough idea around this and I've started it. So hopefully over the next few weeks here for folks that are caution siders. I'll start reaching out and start setting up quick little calls, just to kind of get updates and feedback from you guys. And how are things going? And we'll go from there. So + +Adam Wozney: That's my update for while I've been away. Any ideas. Anything else you'd like to cover on what we've discussed here today? + +Adam Wozney: Looks like we're good with that. + +Adam Wozney: Yeah, I really don't have anything else to cover. next community call will be next month, so we're October the beers almost over, which is pretty crazy. But as always, if you guys do have questions, thoughts, concerns head over to the discord over to the SIG Community, Channel finale, feel free to send over that kind of very quick rough and dirty, kind of like overview of the half the mountain sponsorship to the SIG community chat, and Tyler. Feel free to tag me as Just so we're aware. And once he has anybody else on this call, I want to get feedback or thoughts. Feel free to put it in the discord. but beyond that, that's all I got. Thank you guys for joining. Robert. Go for it. + + +### 00:40:00 + +Robert Del Rey: Chair it's been a great call. Happy to see you again and looking forward to see how the insiders programs. Gets better, there is always room for improvement. So looking forward for that, + +Robert Del Rey: this is my interception for the silly mission about the monthly community call. It came in a little later today. Sorry about that. But the secret word is gonna be the same as last month. Compute. C O M P. U p e, right? Yes compute. And if you submit that word in the City mission for the Community monthly call, you will get extra EXP points and extra 80 rewards. That is something that we definitely need to catch up our series doing and more. So yeah, stay safe everybody. Thanks Adam. + +Adam Wozney: For sure, Robert, thank you for the update. definitely all the work you've been doing on Zillow. I've been away, it's definitely hasn't gone to notice so keep it up. Pretty cool stuff. Big fan of zeely. My friend is still trying to poach us over to Galaxy which is the ethereum. It's not just a theory, but the other Web 3 kind of zeli, but that's something that we could discuss later and there's no rush on that. But keep up the good work. Thank you, Robert. But I'm beyond Any other thoughts questions before? We jump out of today's SIG call + +Adam Wozney: All right, cool. we'll see you guys next month in the meantime be good to yourselves and each other and we'll see in the Metaverse. Take it easy, everybody. + +Tyler Wright: Clear, he's back. + +Robert Del Rey: It's definitely, but if everybody + +Adam Wozney: you guys. + + +### Meeting ended after 00:42:17 👋