diff --git a/committee-steering/README.md b/committee-steering/README.md index c7eb35e3..9c97b688 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](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) | | | | Thursday, July 25, 2024 11:00 AM PT (Pacific Time) | | | 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 👋 + 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 👋 + 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 👋 + 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 👋 + 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 👋 + 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) | | | 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 👋 + diff --git a/sig-support/README.md b/sig-support/README.md index 467c5586..a7dc5dc9 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -44,12 +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) | | | -| #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) | | | +| #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) | | | 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 👋 + 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 👋 + + 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 👋 +