diff --git a/committee-steering/README.md b/committee-steering/README.md index 9134cc61..5c011418 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -6,11 +6,11 @@ date: 2023-1-26T00:20:10-08:00 # Akash Network - Steering Committee (SC) -The Steering Committee is a special SIG that periodically evaluates the list of projects, prioritizes/adds/removes items and decides which SIG or WG is best suited to tackle the project. The Steering Committee also regularly meets to incorporate learnings to improve how the Akash Network community operates and will perform conflict resolution as necessary. +The Akash Steering Committee serves as a key advisory body, regularly engaging with the community to evaluate ongoing projects, provide feedback, and align efforts with the Akash roadmap. It supports active discussions, AEPs, special interest groups, and working groups to ensure cohesive progress across various initiatives. ## Meetings -### Meetings usually happen [on the last Thursday of each Month at 11am Pacific Time](https://calendar.google.com/calendar/u/0?cid=Y18yNWU1ZTM3NDhlNGM0YWI3YTU1ZjQxZmJjNWViZWJjYzBhMDNiNDBmYjAyODc4NWYxNDE1OWJmYWViZWExMmUyQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20) +### These are open community meetings, that usually happen [on the last Thursday of each Month at 11am Pacific Time / 7pm UTC](https://calendar.google.com/calendar/u/0?cid=Y18yNWU1ZTM3NDhlNGM0YWI3YTU1ZjQxZmJjNWViZWJjYzBhMDNiNDBmYjAyODc4NWYxNDE1OWJmYWViZWExMmUyQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20) ### Next Meeting: January 30th, 2025 @@ -38,11 +38,13 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, September 26, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/020-2024-09-26.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/020-2024-09-26.md#transcript) |[Link](https://otgpsa4db4kpmdhoccmt3giweyqevheemhwjovjfmva2vrsjgtsq.arweave.net/dMz5A4MPFPYM7hCZPZkWJiBKnIRh7JdVJWVBqsZJNOU) | Thursday, October 31, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/021-2024-10-31.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/021-2024-10-31.md#transcript) |[Link](https://h5r73bah365pqfr4x62x5sdut5px4wpprsnd6lu2hcej3x42jkxa.arweave.net/P2P9hAffuvgWPL-1fsh0n19-We-Mmj8umjiInd-aSq4) | Thursday, December 05, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/022-2024-12-05.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/022-2024-12-05.md#transcript) |[Link](https://xkr2kbywumiw7y7cclz2z7uorfwxdwm6gsx4kvqqt3uy4qeirjya.arweave.net/uqOlBxajEW_j4hLzrP6OiW1x2Z40r8VWEJ7pjkCIinA) -| Thursday, January 09, 2025 11:00 AM PT (Pacific Time) | | | +| Thursday, January 09, 2025 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/023-2025-1-09.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/023-2025-1-09.md#transcript) |[Link](https://kjr75weuxisrplpudutxpyrioof6353hwzpecxnift7y4e24ekdq.arweave.net/UmP-2JS6JRet9B0nd-Ioc4vt92e2XkFdqCz_jhNcIoc) | Thursday, January 30, 2025 11:00 AM PT (Pacific Time) | | | +| Thursday, March 06, 2025 11:00 AM PT (Pacific Time) | | | +| Thursday, March 27, 2025 11:00 AM PT (Pacific Time) | | | -### Typical Agenda +### Typical Akash Steering Committeee Meeting Agenda - Review/ discuss/ address any community feedback, greviances or conflicts. - Review [Akash Project Boards](https://github.com/orgs/akash-network/projects) and prioritize/ add/ remove if necessary. @@ -56,9 +58,9 @@ The Steering Committee is a special SIG that periodically evaluates the list of - Open up the floor to any other questions from the participants. - Look ahead at special interests groups (sigs) and working groups (wgs) for the following month. -## Steering Committee +## Akash Steering Committee -The Steering Commitee is initially comprised of the following members who have the most familiarity with Akash Network but the meetings are public and anyone is welcome to attend and listen-in. +The Steering Commitee is initially comprised of the following members who have the most familiarity with Akash Network. - Anil Murty, Overclock Labs - Artur Troian, Overclock Labs diff --git a/sig-economics/meetings/022-2024-12-04.md b/sig-economics/meetings/022-2024-12-04.md new file mode 100644 index 00000000..856a6dd9 --- /dev/null +++ b/sig-economics/meetings/022-2024-12-04.md @@ -0,0 +1,208 @@ + + +# Akash Network - Economics Special Interest Group (SIG) - Meeting #22 + +## Agenda +- Recap of the previous meeting +- Updates on PIP01 and PIP02 +- Discussion of live proposals and funding mechanisms +- Open floor for ideas, feedback, and questions +- Reflections on 2024 and plans for 2025 + +## Meeting Details +- Date: Wednesday, December 04, 2024 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://thgwrtxurj52vxm35t2hd6p4uq55bfjhvyvdv7kwd4szgn4qqgxa.arweave.net/mc1ozvSKe6rdm-z0cfn8pDvQlSeuKjr9Vh8lkzeQga4) +- [Transcript](#transcript) + +## Participants +- Scott Hewitson +- Cheng Wang +- Ahmet Recepoğlu +- Andrew Gnatyuk +- B S +- Maxime Beauchamp +- Poroburu +- Rodri R +- Yakup Altay + +## Meeting Notes + +### Recap and Updates +- **PIP01 and PIP02**: + - PIP01 nearing full commitment, with the focus on high-performance GPU onboarding. + - Remaining PIP01 contracts being finalized; a dashboard tracking commitments, expenditures, and revenue shared with attendees. + - Revenue from providers supported under PIP01 is being returned to the community pool. + - PIP02 has been passed and is moving forward. Focus remains on balancing supply and demand for GPUs on the Akash network. + +- **Provider Incentives**: + - Providers' subsidies are structured to add value to the network while being transparent. + - Liquidation methods for AKT include OTC trades and algorithmic selling to maintain market depth without adversely impacting token value. + +- **Developer Onboarding Program**: + - The third iteration passed successfully, continuing community-driven efforts to onboard developers into the Akash ecosystem. + +- **Live Proposals**: + - Discussion on the log forwarding proposal; currently failing due to alignment issues with the core team's requirements. + +### General Discussion +- **Transparency in Proposals**: + - Concerns raised about the loss of GitHub proposal discussions if accounts are deleted. Suggestions include storing discussions on IPFS or taking snapshots for permanent reference. + - Efforts are ongoing to centralize proposal reporting for better community access and transparency. + +- **2024 Reflections**: + - Significant growth in daily network fees (near 2000% over the year). + - Introduction of features like credit card payments aimed at lowering barriers for Web2 developers to use Akash. + +- **Looking Ahead to 2025**: + - Plans to expand the core team and attract more builders and contributors. + - Emphasis on striking while the market momentum is favorable to grow the network and its capabilities. + - Encouragement to bring skilled developers, artists, and contributors into the ecosystem. Suggestions for a referral bounty program to incentivize community recruitment. + +### Closing Remarks +- Attendees encouraged to share feedback, concerns, or ideas for improvement. +- Emphasis on community contributions as vital to Akash Network’s success. +- Wishes for a happy holiday season and anticipation for continued growth in the coming year. + +## Action Items +- **Scott Hewitson**: + - Finalize and share updated dashboards for PIP01 and PIP02 by year-end. + - Address transparency concerns by exploring ways to preserve proposal discussions permanently. + - Centralize reporting for all community pool proposals. + +- **Cheng Wang**: + - Collaborate on launching the credit card payments marketing campaign. + - Develop and implement a referral bounty program for recruiting contributors. + +- **Community Members**: + - Review PIP dashboards and provide feedback. + - Participate in ongoing proposals and discussions on GitHub. + - Refer potential contributors to the Akash ecosystem and share credit card payment updates widely. + +## Transcript + +Scott Hewitson: All right, everybody. This is the last SIG economics call of 2024. Been doing these things for almost two years now. So, it's pretty cool. you kind of just getting in a rhythm and then realize that you're two years into it. So, it's pretty sweet to see. typically, so for those that are either listening for the first time or recording, typically we go over what we talked about last call, then any kind of props that have come up, any discussions. and then I like to open it up to folks for any kind of feedback or if there's any ideas, anything at all that you'd like to talk about, I like to give an open floor. + +Scott Hewitson: one of the reasons why AOSH is so strong and our community is so strong is because we have these working groups and special interest groups where people are free to join and free to contribute in any way. And I do think as a community we do a pretty good job of helping those that are providing value to get funding in whichever way that is. So let's see last call I think we talked and Chang's going to jump on here in a little bit. I think if not I can just kind of cover some stuff So last call we talked a little bit about PIPO too. So that's the provider incentives second iteration of that that went on chain and passed. it's a sizable amount of funds and those funds are going to be used to incentivize putting up more high performance GPUs on the network. + +Scott Hewitson: it's kind of this chicken the egg problem, cold start problem where, you don't want too much supply because then it's underutilized, but you want enough to where people are using it. So, I think, it's a little hands-on and manual at the moment, but I think we're doing a decent job of growing demand and supply together. I mean, there's no perfect science to it, but I think we've done a pretty decent job. So, PIP PIPO2 has passed and we put one contract together for some providers or for some GPUs. PIP01 is almost fully committed and I'll drop the dashboard in chat if anyone wants to check that out. I was doing some work on that last night getting actuals and everything. + +Scott Hewitson: So here is so yeah, I mean you can see we committed quite a bit. We spent quite a bit. and then the cool thing about all this is ers are out there on the network and they're earning AKT and we're any AKT that those providers are earning are going sent back to the community pool. It's not going to be, one to one. we spend a million dollars, get a million dollars back. and we'll be able to get a good metric at the end of PIP01. But, as long as we're making we're making some money, the incentivization is working in my opinion. let's see. So, yeah, that's recap on PIPO one. Pipo 2 is going live. + +Scott Hewitson: I do all these dashboards for a bunch of different props that we put up. So I'm hoping to have stuff pretty up todate by the end of the year. I know events and community support and some of those other ones hackathon, we'll send back funds at the end of the year to kind of close out the prop for the year. and so you'll be able to check all that. It'll all be on chain verifiable. let's see Anything last week outside of Pipo one and Pipo 2? Those have kind of been the big things we've been focusing on for a while and I mean growth of the network. it's clearly doing good for the network. yeah, I think that's all I got from from last week. So then recent props that have gone up. the pito 2 went up had passed. + +Scott Hewitson: We had the developer onboarding program. that's the third iteration of that that went up and passed that it's a community program to get people learning about Akos. it's completely communitydriven. So it's pretty sweet that folks can do that. and I will say if anyone is trying to put up a prop to get funds from the community pool we've done it quite a bit. So, if you have ideas, get them in the GitHub discussions, ping me on Discord. let's talk in SIG economics. again, I love helping folks help the network. it's wins for everybody. there is a live proposal on log forwarding. I know it's currently not passing. Yeah, it will be rejected. + + +### 00:05:00 + +Scott Hewitson: I don't know too much on the specifics of that, but I think it is just refining requirements to make sure it all aligns with what the core team's doing and what these folks are putting up. So let's see. Those are the live props. yeah, I think so. I don't really have anything too much outside of PIPO one or PIPO two. Yeah, let's see. Can you explain the PIP01 dashboard a little bit more? I'm just looking at it now. Not sure how to read committed liquidated revenue columns. Yeah, know that's perfect question. so basically, we requested funds, we get all this AKT, right? I mean, we're incentivizing providing subsidies, if you will, to these providers. Not everybody wants to take AKT as payment. + +Scott Hewitson: a lot of folks are still with good reason, They're like, "All right, we want cash instead." So, some of those funds we have to take and liquidated to fiat or US dollars or stable coins. so we've got three main columns here and so above you got the proposal link, the wallet address that was requested, the total amount. I've got live balances which is not let me live balance is good so the committed side committed is basically we have signed a contract for x amount of dollars. so it may not be money spent but there's been a signed contract. So you sign a contract for a million dollars. You've committed a million dollars. You haven't spent a million yet. + +Scott Hewitson: you might spend that million over the next 12 months. spent to date is literally what has been spent. is there any questions on the committed aspect? If not, So on the liquidation side, again kind of goes into the u not everybody wants AKT to put up machines. it's a newer concept for folks. not everybody is hip to crypto yet. I will say there's at least one who is taking AKT in chunks, which is kind of cool. but yeah, so we've had to liquidate some funds and basically so you have the amount liquidated and then the proceeds. So that's the stables or fiat that we've gotten for that. + +Scott Hewitson: So really what when I'm looking at this and it's a lot of moving numbers the AKT price is moving contracts are going what at the end of PIP 01 we want committed to equal proceeds essentially and then one other thing I will say about committed there are some that are 12-month contracts there are some that are month-to-month that have been going for a while so we're getting towards the end of PIP01 and adding supply and then it'll cut over to PIPO too. So that's why I'm really trying to get it kind of cleaned up as much as possible just so that we are being transparent and showing everything. How are the funds liquidated? Yeah. So couple ways we can liquidate funds. + +Scott Hewitson: You can do OTC deals which is basically hey here's 500 grand of tokens here's 500 grand they call them T OTC desk exchange some exchanges have them some market makers have them so you can sell tokens like that the way we predominantly do it is through algorithmic selling via some market makers traders essentially just adding depth + +Scott Hewitson: to the order books on the sell side. and traders and people who are trying to invest in a cost they could see it. So when you put up a bunch of limit orders going up they can say there's 100 a grand or 200 grand that I could buy without raising the price a ton. So we try to do it in a way where we're adding depth where it's actually strengthens the market and it allows bigger players to see it and enter positions. I won't say not once, but never I'll do little swaps here and there, a couple grand, but that was before we had some of these other apparatus set up. U, but yeah, typically I'd say 99% of the time it's all u, limit orders adding depth. So, we're never dumping into a market. + + +### 00:10:00 + +Scott Hewitson: and the good thing is we have time to liquidate right so you can kind of set your orders and wait u for the market to come to you and I think we've been done a pretty good job of that so far let's see is there any other questions on that yeah never market sales never let's see okay then revenue is basically so these providers they've been paid to put up on the network. people are deploying to them we may or may not know who's deploying to what but what we do know is we put up this provider it's earned 10,000 AKT over this amount of time. the provider was paid for it by the community pool. + +Scott Hewitson: So those funds should go back to the community pool because the community technically owns these providers. so basically any funds that the providers get that are getting paid on the front end are any funds that get to them get returned to the community pool. So I think the last send to the community pool is in September. So there should be a large trunch going back to the community pool across multiple providers by the end of the month. I kind of wanted to do it at the end of the month so it's kind of clearcut. yeah, so that explains the revenue stats. Hey any other questions on the dashboard? does that make awesome. All righty. Yeah. + +Scott Hewitson: + +Scott Hewitson: So Kang, we just kind of went through last call. any props that were up. I talked a little bit about PIPO one, PIPO 2. I shared the PIPO1 dashboard. It's pretty much up to date. U and then we had a question on basically what the D the committed the liquidation and the revenue stat. So we walked through all that and then there was a question about OTC or how we're liquidating funds. And I said it can be a mix of algorithmic selling, market makers. but the big point is we're never market selling. We're only adding depth. and so it's actually healthy for markets to do it this way. I think you're caught up now. + +Cheng Wang: + +Scott Hewitson: Is there anything … + +Cheng Wang: Thank you. + +Cheng Wang: Sorry for being late. + +Scott Hewitson: no. You're fine. is there anything you want to add or talk about in particular or anything coming up? + +Cheng Wang: Yeah, I think just as this year another year draws to a close 2024 and looking ahead to 2025. and we have a bull market tailwinds now but behind us really looking forward to what we can build. I think one thing definitely want to emphasize and leave for the group here and others listening later on hopefully or reading is we need to strike the iron while it's hot right and so we're looking to really expand the core group where sorry I think something interrupted my call apologies we're looking to expand the core team we're looking to obviously expand our community members and get builders in here building and contributing + +Cheng Wang: to AOS network to continue to advance features, capabilities, resource avail, right? So, as we all know we're on the march towards And getting closer to par means being able to host more workloads, being able to serve more robust and bigger customers and clients onto network and bring usage on, Over year, we've grown near 2,000% as far as daily network fees go. I would love to there's no reason why we couldn't do that again, this time next year. And so we're though the number seems pretty big at 10K a day where that's what a little over three million a year or something like that, right? In terms of total network revenue, that's a drop in the bucket. So I think we can easily, more than definitely 100x that, If we I think put all of our competitive juices to build the product that the Kosh network is fast becoming. + +Cheng Wang: and the feedback from the community has been absolutely outstanding. We're going to be launching the marketing campaign and NPR stuff with credit card payments this week starting tomorrow. So, keep an eye out for that. Amplify share with your community, share with builders, we have credit card payments. So, there's no excuse for web two devs anymore for using your kosh. so that's what I really want to emphasize. And bring if people who are good let myself know, let Max, let Huie, etc. and we'd love to see if they can contribute in some meaningful way and be happy to if they add value and they're good, I think we can probably set up some sort of a referral program too. buyback. No. + + +### 00:15:00 + +Cheng Wang: So the way the credit card payments work is someone swipes credit card it basically in instantiates through oz a kosh on the back end and that goes to the provider. So it's either aos on the back end or USDC and either way right that's why we instituted the take fee with AKT 2.0 I know Andrew right? So no matter what currency is being used value is always accreating to the network. + +Scott Hewitson: All I mean, yeah, appreciate all that. And I just will echo, it doesn't matter how small of a contribution you want to make. Today I paid an AKT contribution that was on a bounty. We have, 10K a month in bounty dollars. Tai does a great job of wrangling folks. And, there's tons of stuff to be done. there's lots of lowhanging fruit. we don't have enough engineers. we don't have enough folks to do everything. so even if you don't think that, what you can contribute is useful. It probably is in some way, shape, or form. so I just encourage you to, hit me up or hit Ty up or hit anyone up and just kind of say, "Hey, these are my skills. This is what I'm good at." and, we'll go from there. All right. + +Scott Hewitson: right now I'd like to open it up to the floor if anyone has anything they want to say or any comments, questions, If you have concerns about how we're doing this, how we're operating. would I'd love to hear any feedback or ideas. I know Andrew's got something for me. + +Andrew Gnatyuk: + +Andrew Gnatyuk: No, I'm good. I'm just like, came to see what's popping. + +Scott Hewitson: Yeah. + +Andrew Gnatyuk: Do we still have talks on buy bags, burns, some mechanisms, so I could give it to retail and say, hey, they're going to pumps the talk and just wait for it, No, I'm kidding. the one thing I wanted to say is that we recently had So there was a proposal on the cash it passed but then the discussion about this proposal was deleted. + +Andrew Gnatyuk: So basically the question is can we make some sort of rule that even if the proposal passed could people not to delete the discussion about the proposal or something like that + +Scott Hewitson: whatever reason their GitHub account got deleted. so they had to make a new GitHub account but their post disappeared from it. so I don't know exactly how to recover that if it's possible. that's why I try to because GitHub is not forever right if it's on chain it's forever. So we try to put as much info as you can on chain. but yeah, then you're missing out on the discussions, the points people bring up or, the things that they say they're going to do and then didn't do or did do. yeah, I 100% agree with you, Andrew. I know some other projects they'll do a IPFS link so it's like a permanent link on there, but again it doesn't have discussions. + +Scott Hewitson: So, maybe something we could do is screenshot or save the discussions at some point, and then yeah, I don't know. it's a kind of a one-off case, but yeah, you should be able to look back at everything for posterity. + + +### 00:20:00 + +Andrew Gnatyuk: + +Andrew Gnatyuk: it's one of case. Yeah, for sure. but if it's going to repeat itself sometimes in the near future, people will like hey there is a proposal it passed it has lots of funding and we don't know what is it about and that's just a concern about that. Okay. Yeah. + +Scott Hewitson: a way to solve that or a way to just kind of ensure that doesn't happen. again, I'm all ears. I know Tai's thought about it as well. + +Andrew Gnatyuk: If I have any idea, I will share for sure. + +Scott Hewitson: Thank you. got a question There's no dumb questions here. These are all Everyone's welcome. Ask anything if you don't know. The only dumb question is a question that you don't ask. is there a unified budget? no. So, I would say no. So, you've got the community pool and I got little let me find this. I tried to put somewhere community pool spin reporting. so the thing is you've got multiple teams requesting funds from the community pool. Overclock Labs is just one of the teams doing it. + +Scott Hewitson: and so it's kind of like you can see all the props that we put up. Overclock has, our own treasury. We have employees, contractors. we put up props for various things. but yeah, some of the Zelia campaign that's completely communityowned. I know the website prop was community owned. So those are anyone can put up a prop at any time. It's permissionless. So, BS, if you had a thousand AKT, you could put up a prop for anything. I will say this, I made this a little while ago and it needs some tender love and care for sure, but this community pool spend reporting. It's kind of just a place where can compile, any funds that have been requested and received from the community pool. + +Scott Hewitson: So part of what I need to do is, fill in more for what Overclock has put up so far, but then anyone can, put up a PR to say, "Hey, this is the reporting that I'm doing and you can have it here." So we just wanted to have a centralized spot to look at this. But yeah, to your point, there's no unified budget across the pool. I mean, you could make something, I guess, using onchain data. but yeah, that's kind of where we're at. And It's cool that, anyone can request funds. ideally, in the perfect world, overclock is, we're a smaller and smaller percentage of the people requesting funds over time. No worries. Good question, too. + +Scott Hewitson: All does anyone else have anything they'd like to bring up? Any questions, concerns? Nope. All right. Chang, any last thoughts? Correct. + +Cheng Wang: wins continue. But like I said, seriously, I know I say this all the time and very few people come through with suggestions and recommendations, but please bring people into the ecosystem. I think internally I'll drop it here first, but we should definitely sort out a bounty program of some kind like a referral program where if you refer a really good developer who we don't know about and bring them into even if they're in the community in the periphery but they're not really participating and you surface them up then they can really contribute meaningfully. We should absolutely have rewards for that. So yeah, take that to the bank. We'll definitely put something there out for it to add additional help whether it's developer, artist, whatever it is community me just anything of the sort. + +Cheng Wang: + +Cheng Wang: If you think they can add value to Akos, please let us know. + +Scott Hewitson: Alright I'll give one more chance to let anyone raise a hand or drop something in chat. Otherwise, we can end things a little early and… + +Scott Hewitson: give everyone back some time. Last All everybody have a good rest of the year. Happy holidays. I'm looking forward to seeing everyone in January. Appreciate you all. + + +### 00:25:00 + +Cheng Wang: Thank you. + +Cheng Wang: Appreciate you all. + +Maxime Beauchamp: It's yours. + +Andrew Gnatyuk: Have a nice day. + +Cheng Wang: Take care. + +Scott Hewitson: right. Thank you. + +Cheng Wang: Have a Good rest of the year. + + +### Meeting ended after 00:25:28 👋 diff --git a/sig-economics/meetings/023-2025-01-08.md b/sig-economics/meetings/023-2025-01-08.md new file mode 100644 index 00000000..c0b62698 --- /dev/null +++ b/sig-economics/meetings/023-2025-01-08.md @@ -0,0 +1,355 @@ +# Akash Network - Economics Special Interest Group (SIG) - Meeting #23 + +## Agenda +- Recap of previous meetings and updates +- Transition between PIP01 and PIP02 +- Transparency in community pool spend reporting +- Open floor for community questions and suggestions +- Plans for 2025 and discussion of roadmap + +## Meeting Details +- Date: Wednesday, January 8, 2025 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://kb66isbh5o5doxrcarv5wxlay3ik3aumfrso344igrpzvj5estqq.arweave.net/UH3kSCfrujdeIgRr211gxtCtgowsZO3ziDRfmqeklOE) +- [Transcript](#transcript) + +## Participants +- Scott Hewitson +- Andrew Gnatyuk +- B S +- Lucia Ijeoma +- Luna +- Rodri R + + +## Meeting Notes + +### Recap and Updates +- **PIP01 and PIP02 Transition**: + - PIP01 is nearly fully committed, with remaining funds allocated to ongoing provider contracts. + - PIP02 implementation is underway, focusing on scaling high-performance GPUs on the network. + - Dashboards for PIP01 and PIP02 are being updated to ensure transparency and tracking. + +- **Community Pool Spend Reporting**: + - Reporting for 2024 is complete, but earlier data from 2023 and before still needs to be added. + - A centralized repository tracks all proposals, their discussion links, and outcomes for full transparency. + +- **Live Proposals and Approvals**: + - Recent proposals include community activities and programs funding for insiders, vanguards, navigators, and alchemists. + - Discussions continue on the refinement of proposals for maximum alignment with the community's goals. + +### Community Questions and Suggestions +- **Credit Card Payments and USDC Integration**: + - Questions raised about the performance of credit card payments and the $10 free trial feature. + - Concerns over bot abuse in the free trial system are being addressed by the engineering team. + - Statistics on the impact of USDC credit card payments are requested, and updates will be shared in future meetings. + +- **2025 Roadmap**: + - General anticipation for the roadmap; priorities being finalized internally before public release. + - Discussion on potential new features like secret management, DNS, and AI integrations as part of the broader network vision. + +- **Community Engagement**: + - Importance of community contributions emphasized, with calls for ideas and proposals from members. + - Suggestions for leveraging the community pool for exchange listings and promotional activities discussed. + +### Key Discussion Points +- **Fraud Prevention**: + - Challenges with fraudulent activity on credit card payment systems. + - Collaboration with Stripe to identify and mitigate abuse while maintaining the integrity of the platform. + +- **Promotional Activities**: + - Debate on using community funds for exchange-based promotions, with examples from past initiatives. + - Suggestions for linking promotions to key events or milestones for greater impact. + +- **Community Program Growth**: + - Encouragement for individuals to apply to roles like insiders and vanguards as programs expand in 2025. + - Adam Wozny highlighted as the point of contact for onboarding new community members. + +### Closing Remarks +- Open invitation for community feedback, ideas, and suggestions to improve SIG Economics operations. +- Continued commitment to transparency and ensuring community funds are used effectively. +- Thanks extended to all attendees, with plans to address outstanding action items in the next meeting. + +## Action Items +- **Scott Hewitson**: + - Update dashboards for PIP02 and complete PIP01 reporting. + - Gather and share statistics on credit card payments and free trial performance. + - Follow up on 2025 roadmap updates and share timelines when available. + +- **Community Members**: + - Engage with SIG Economics to propose new ideas or provide feedback on current initiatives. + - Participate in community roles and programs, contributing to the network's growth. + - Review and discuss live proposals in SIG channels. + +- **Andrew Gnatyuk**: + - Explore opportunities for exchange promotions and consider drafting a proposal for community funding. + - Share insights on market trends and potential promotional strategies with SIG Economics. + +## **Transcript** + +Scott Hewitson: All right, GMGM everybody. It is the 8th of January, 2025, the first SIG economics call of the year. looks like we have a little lighter of a crowd. I know there's some other internal meetings going on where some other folks can't make it. I know Chang won't be here, but we wanted to have the call get things recorded. for any folks that are listening in later, thank you for listening if you do. I don't know how many people actually, listen later, but yeah, it's a good time. So, to, last call we talked majorly about provider incentives one and two. I looked and the notes are not up for that. + +Scott Hewitson: the video recording is up but those notes should come up soon in the transcript as well. but really that one I kind of was talking about PIPO one giving status updates for that and then as we transition to PIPO 2. So we've kind of committed most of PIPO one. there's a little bit left we could commit or return back. I'm still trying to figure out because there's a transition period of some of these providers that we're paying for. We'll switch over to PIP 2 funding. and then some will just stay on PIP one. it's just kind of, I'm matching what we've committed, what we spent to what we have in those buckets. So, it's just kind of a bucketing exercise. Nothing too crazy. + +Scott Hewitson: I'm trying to be pretty transparent with everything. I think last time I said I would update the community pool spend reporting page which I did. I'll drop a link here to that. So that is just basically any and I only did it for 2024. I need to take some time and go back before then. But basically it's a place where folks anyone who receives community pool funding can we track it out call it out a to the discussions a link to the actual proposal and then to any kind of reporting just for transparency you'll see some of them don't have links to it I know for provider incentives pilot 2 I'm actually working on that one right now but some of those other ones and + +Scott Hewitson: and some of them, overclock doesn't put up. So, it's up to anyone who wants to add any reporting. It's just the idea behind this is just to make sure that we are making good use of community pool funds and maintaining that high transparency. we overclock me whoever are putting forward things and we hope that others will too who take funds from the community pool. It's a pretty cool mechanism that we have that we can operate with in web 3. So yeah max transparency and we're good to go. What's going on Happy to have you. Thanks for jumping in early this year. + +Scott Hewitson: kind of lighter group. We're just kind of going through last call I was talking about the community pool spend reporting page has been updated working on no worries. provider incentives pilot one that dashboard is up to date and PIP2 dashboard should be coming out within the next couple days. I will say so PIPO one I think we're at a little over almost 5 million committed. That whole total request was about 10 million. there was a buffer put in for liquidation. so there's quite a bit of funds left on that and it'll all be linked in the dashboard so everyone can check that from the standpoint of props that are up there. + +Scott Hewitson: Let's see if there was a couple props since the last call. There was a log forward a couple that There was a marketing support team proposal and then logger for forwarding integration. I think the teams that are behind everyone's been talking in respective sig working groups to see how either refining those and making them better just or moving on to something else. There are two props we've got that live in the voting period should end in two days. the community activities and community programs. + + +### 00:05:00 + +Scott Hewitson: these are headed by Adam WNY or head of community activities are bounties hackathons I think small communityled events and then the programs cover the community member we've got the insiders vanguards there's the I think alchemists what else is there's the navigators so there's funding behind all these groups if insiders is the top of funnel as you go down and specialize. yeah, we're being able to pay folks for their contributions, which I think is awesome. those props will be up quarterly. and any addition or surplus or surplus or shortfalls will be accounted for in subsequent props. yeah, that's kind of it on a recap of last call. + +Scott Hewitson: highlighting PIP 01 and O2 because those are big dollar amounts spent from the community pool and then some live proposals. I won't go into discussions that there's quite a few things out there and I think there is a steering committee call later this week tomorrow. So, hopefully some folks, if there's any discussions or anything, the people will bring it up there as well. So, that was a quick little rundown. nothing too crazy. everyone's kind of getting back in the swing of things, so I'm guessing next month will be a little bit more exciting as things get going. Yeah, nice to have you here. + +Scott Hewitson: sorry if I'm butchering it, ucia. all these calls are open. Everyone's welcome to voice their opinions. we get actually a lot of great ideas out of these calls or if you would want to drop your notes in and Discord and Sik economics channel. I'm looking at everything. I'm open to everything. those that my whole thing is if you're providing value to the network. if you're doing things that progress the network and grow the network, then there's ways to get funding. And I'm always happy to help folks refine ideas, put up props, whatever it may be. So, open invite for anyone. yeah. So, at this time, I kind of did a recap. + +Scott Hewitson: want to open it up in case there's any questions, comments, concerns. It can be how we're doing these calls, any suggestions for these calls, or if you have any ideas as it relates to SIG economics and the community pool and any kind of u funding that drives us to that, goal of cloud parody at some point. Andrew, I know you got one for me. + +Andrew Gnatyuk: Yep. so yeah,… + +Scott Hewitson: There it is. Sorry for CES 2025. Okay. + +Andrew Gnatyuk: great question. do we have some stats on the CC payments? do we know how much USDC was spent when we launched the stuff? Is it For the C T125 was just like job, It's ongoing. So yeah, I'm still looking for money, to buy some stuff for work,… + +Andrew Gnatyuk: of course. No, no, I'm talking about this is the credit card payments with the USDC. + +Scott Hewitson: Credit card payments. + +Andrew Gnatyuk: Maybe we have some stats when we launched it and… + +Scott Hewitson: So you want just kind of a general update and how that's running or Yeah. + +Andrew Gnatyuk: how it boosted the cash payments how many USDC was spent on the cash for example + +Scott Hewitson: So, it was built and It's currently live. We've been not me personally, but the team overclock has been dealing with some abuse issues, So, you got two things going with stable payments, right? You have free trials, and that's where anyone can spend $10 without anything. and then you've got the credit card payments. + +Scott Hewitson: We've seen a little bit of, fraud from credit cards. So, we're working with Stripe and, it's just like anytime you build something that can be gamed, people are going to try to game it. So, I'd say it's a little bit early to get some good hard numbers, other than the fact that it's working. The apparatus is working and it's flowing, which is good. So, I can see if we can pull something together for you, Andrew, though. because yeah, I'm curious as well, too. yeah,… + + +### 00:10:00 + +Scott Hewitson: Rodri, go ahead. is that I mean, I know I didn't really answer the best I could. I just don't really have the answer. Yeah. + +Andrew Gnatyuk: Yep. It's all good. + +Andrew Gnatyuk: All good. + +Rodri R: I just want to ask is the $10 trial going to last forever or… + +Rodri R: is there planned to end at some point? someone on Discord a few days or last week? + +Scott Hewitson: Yeah,… + +Scott Hewitson: I mean as of right now it's open. It's still running. I don't see I mean the idea is to give people a frictionless experience to just test it out. an ideal flow is they go on, they deploy something, they're like, " cool. It actually works. I didn't have to do anything. They like it, and then they can you convert them over by using a credit card." So, I think as much as we can, we'd like to keep the free trials open as long as we can. I know there's been some abuse on some bots and… + +Rodri R: Yeah, I heard some of that,… + +Scott Hewitson: miners and all that stuff. So, all What's that? + +Rodri R: Yeah,… + +Scott Hewitson: Yeah. Yeah. So I mean it's again anytime you build something that can be gamed people are going to try to gain it. so the team engineering is looking hard at solutions and figuring out what best about that. + +Rodri R: Yeah. No, I mean Yep. Just wanted to know… + +Scott Hewitson: Yeah. Yeah. + +Rodri R: if there was a end date for this. But yeah, I know other platforms have similar promos that been lasting for years. So guessing it can be here + +Scott Hewitson: Yeah, I think the idea is to keep it there as long as it makes sense. Awesome. All right,… + +Scott Hewitson: Andrew, another question. + +Andrew Gnatyuk: Yeah. So yeah,… + +Andrew Gnatyuk: another question. what's up with 2025 road map? is like some Yeah. + +Scott Hewitson: 2025 road map. + +Andrew Gnatyuk: at So can we see it when can we see it? + +Scott Hewitson: I would love to see it myself. So, yeah, I know Greg's been working real hard on kind of distilling his thoughts and, where we're ing, direction we're heading. I have not seen any drafts or anything. I know it's being worked on. I know the goal is to get it out, ASAP. So, again, I can't help you with that question. + +Scott Hewitson: But as soon as I see it's usually once we see it internally it'll go out quick quickly thereafter. + +Andrew Gnatyuk: All good. + +Scott Hewitson: So Yeah. + +Luna: Yeah, I'd like to add that for technical stuff, we have some breadcrumbs here and there. They sometimes get dropped on some channels. So, we kind of have an idea of what the network might support in the future. I'm just not sure if it's 2025. So things like secret management, DNS, all that sort of stuff. I'm pretty sure it's part of the road map, but not sure if it's 2025. But some of these things you can already kind of expect to come in the future. + +Scott Hewitson: For Yeah. I mean, at the end of the day, right, it's open- source software. + +Scott Hewitson: anything can be built onto it. and hopefully all of these things will be added as features at some point as we're go going towards cloud parody. We're going towards, what the giants have right now. Akos is still relatively new. So, it's cool to see that progress, but yeah, I think there's the problem is there's so many things that you could do and it's just, if there's a hundred things, it's and you can only do 15 of them in a year, then you got to prioritize. So, I think that's the exercise that's kind of going on right now. + +Scott Hewitson: and you match that to, which any customers or, people that want to use the network or yeah, it's just kind of a little bit driven by what people are wanting and needing and how things are shaking out. I know the AI agents thing is kind of picking up steam as a narrative. so we'll see if there's some stuff regarding that on the road map. I don't know but maybe I do but I really don't. So yeah as soon as hopefully and I can also ask Andrew and Luna for if we have any updated timelines on getting the road mapap out. + + +### 00:15:00 + +Scott Hewitson: If Chang was here, he'd probably have a better answer. so I'll take note to ask that and drop it in sig economics for the alpha. + +Andrew Gnatyuk: Yeah, that's awesome. Thanks. Sig economics sharing alphas,… + +Scott Hewitson: I don't That's right. + +Andrew Gnatyuk: and insights. + +Scott Hewitson: That's Economics and all the inner working alpha, + +Andrew Gnatyuk: Yeah. s economics, we have everything, because we have money. + +Scott Hewitson: Yes. Yeah. + +Andrew Gnatyuk: All good. + +Scott Hewitson: I mean, yeah. what's it called? Everything touches money at some point. + +Andrew Gnatyuk: Yeah. Yeah. Totally. + +Scott Hewitson: So even if it's not really SIG economics, we can, kind of touch on it a little bit. yeah, Lucy, I saw so you filled out the insider application form. That's awesome. I know W has a ton of folks Adam WNY is reviewing a bunch of folks as always. + +Scott Hewitson: and I know, especially with these new community programs coming up, there's more funding for different things. So, I know he's trying to get as many folks as possible. so hopefully you can hear something soon. if you don't in maybe a week, if you want to ping me, and SIG economics, I can ping him and you can use me as your touch point if you'd Awesome. All right. Does anyone have any other questions or comments or concerns as it relates to SIG economics, the money, AKT, the token, the community pool, anything at all? Andrew + +Andrew Gnatyuk: So, yes. So, about the futures promo I've been writing about with Binance. So, we had a discussion that it's as all promos, we will have some volume at the time of the promo it goes right out and it will fall down eventually to probably some levels. We hope it going to be higher than it was when we started, right? But do we have some for example expectations of what we do want to see from previous use cases from Binance? Let's say for example if their promise has boosted the volume for the token for example on 50% and it ended to be still up by 10% by the end of the promo. + +Andrew Gnatyuk: Is it still good for us? + +Scott Hewitson: I don't know if this was in Vanguards or in chat, but there was so Andrew brought up an opportunity. There's a Binance per competition where a couple grand towards it's a trading competition. So the idea is to boost volume on a certain exchange, certain pairs. and then the idea is you do it and then it brings enough people in to where afterwards there's still some sustained trading and volume. typically, we haven't overclock, funded things. we don't typically do these kinds of competitions unless it coincides with an event maybe I know when there was all those Korea exchanges that added stuff I think we added a small amount to just kind of boost those because it was at launch. + +Scott Hewitson: So I think timing it with another event that brings things in and for that it was like a new market so it's like all right get as many people in as you can while it's brand new. + +Scott Hewitson: We're on futures not on Binance spot. there's no saying a win when or… + +Andrew Gnatyuk: Yeah, it's really like spot futures probably. Yeah. Yeah,… + +Scott Hewitson: if we'll be on spot. It's just with some of these exchanges it's just tough. you can talk with them all you want and you can submit things and you don't hear anything. + +Scott Hewitson: That's just kind of… + +Andrew Gnatyuk: don't worry. + +Scott Hewitson: how it is. personally I think doing something like that if we got a spot listing or whatever doing something just kind of boost it it's a new spot to trade. I think that's a little bit more compelling than just all right pick a random week and let's do this. unless there is some kind of catalyst or some other kind of and it could be something with the road map or it could be something with some new features whatever. but I think we did do try to do something like that. I try to tie it in together with some other event that's already kind of driving some traffic and… + + +### 00:20:00 + +Scott Hewitson: then this just pours gas on it if that makes sense. + +Andrew Gnatyuk: Yeah. and… + +Andrew Gnatyuk: in this regards for example some exchanges write to me from time to time, And I'm not talking about the one that just want to sell their marketing stuff But the one that writes hey we are planning to list Akash can we count on you to retweet it and maybe you have funds to boost this stuff with us as a promo do we negotiate with this people should we make a group or… + +Andrew Gnatyuk: something with new exchanges I'm not saying it's like top tier exchanges probably Indian exchanges or some Asia exchanges maybe top 100 coin market cap or something like that but do We complete all this stuff. + +Scott Hewitson: Yeah, I'd say I mean so coming from overclock lab side we've got a million things that we're trying to get done and… + +Scott Hewitson: and sometimes I mean it's good you want the word to get out. You want distribution. You want eyes and mind space. sometimes if it's not targeted or it's not done in a certain way, it may be not a waste of funds, but just like a less good use of funds, if that makes sense. + +Scott Hewitson: we typically in overclock, if you look at on Twitter, Greg said we don't pay for listings. we don't do any of that stuff. I think that's helped our brand a little bit. because we're not, a paytoplay in everything. that being said, it might be something to look at and this is honestly, if you have high conviction in this, Andrew, and you can always put up a governance proposal and say it's for 10 20 grand, whatever the number is, and say, "Hey, I want to do these things." I think it would be better if it came not from overclock. + +Scott Hewitson: cool thing is that there's a community pool with, a bunch of money in it. so anyone could put up a prop for it. if you had some kind of strategic plan to do it across multiple different avenues, multiple different exchanges, or just hey, this is a pot of money to, we're going to throw a couple grand as opportunities come in, we'll throw a couple grand here, and just report on it all. + +Scott Hewitson: I know from overclock side it's not a priority but community right it could be and there's community funds so yeah I don't think I wouldn't say I don't want to like poo on it or say it's not a good idea which because I think it could help very well it's just not the priority of overclock labs at the moment but if you want to throw up a crop and + +Scott Hewitson: you're like, "Hey, I got 15 different exchange. I've got all these things and you coordinating this whole thing like that, that could be compelling and, you throw it up to vote and see what people think." That's why we got the community pool. so does that help a little bit? + +Andrew Gnatyuk: Yep. Yeah. + +Andrew Gnatyuk: Yeah. Yeah. That's At least I see the picture now, Very good. + +Scott Hewitson: Yeah. Yeah. and if it's something cuz cuz you've got developers and people using AOS and then you've got more like the crypto moonboys and a little bit more speculators. That might be something that they all, support a ton and in marketing, why no marketing? Why know that? + +Scott Hewitson: So if you put up a prop and there's a lot of I mean the end of the day validators vote… + +Scott Hewitson: but people when you can override a vote with your tokens right it's default to whatever the val validator says but if you got a lot of support from token holders great send Yeah. + +Andrew Gnatyuk: Yep. + +Andrew Gnatyuk: People are writing about the marketing every time the token just goes down so it's like common stuff you can do whatever you want you can do lots of advertisement and marketing and everybody can talk to you but it doesn't matter if the token falls down so That's right. + + +### 00:25:00 + +Scott Hewitson: Yeah. Yeah. I mean, it's crypto. + +Scott Hewitson: everyone's happy when token is up and everyone's pissed when token's down. So, you kind of just gota, battle through that. and keep moving forward with utility. And, the reason I'm still here at working on a because I believe in… + +Scott Hewitson: what we're trying to do. there's a lot of projects out there that, just don't do anything. so it's cool to be a part of something that does something even if it's early, … + +Andrew Gnatyuk: So… + +Andrew Gnatyuk: where do you see a cash in 10 years? + +Scott Hewitson: 10 years a I see blocks still producing. That's what I see. + +Scott Hewitson: So yeah,… + +Andrew Gnatyuk: This is good. + +Scott Hewitson: who knows price-wise, though. Awesome. + +Andrew Gnatyuk: Okay. Sure. + +Scott Hewitson: No, thanks for that. again, always always happy to chat through things like that. and if you get to a point you need some help on, putting up a prop or just putting some ideas together, ping me, or do it in SIG economics and anyone can see and help and dive in with you. + +Andrew Gnatyuk: We'll do. I'm just trying to get some stuff start from the exchanges as we talked to just know… + +Andrew Gnatyuk: how the things works And then we can discuss it. Sure. + +Scott Hewitson: Yeah. Love it. + +Scott Hewitson: I love All does anyone else have anything they want to bring up? Any other questions? concerns about how do we do these calls anything at nope. All right. + +Scott Hewitson: Not too short of a call, but I mean we still got some good stuff in. So, I'm gonna moving forward, so next up, I guess, things that I owe this group is I'm going to get PIP O2 up by the next call. so, that dashboard will be live. I'm going to keep updating PIP01. I don't know if I'll all the community pool spend that o. Again, I said 2024 is all in there. At some point when I have some time, I'll start putting in some stuff from 2023 just further back. But those dashboards live and you can find them in discussions and whatnot. But I think that's it from my end. any last comments,… + +Andrew Gnatyuk: Yeah. + +Scott Hewitson: concerns? That's right. + +Andrew Gnatyuk: And yeah, you owe us alpha on when the road map is going to be. + +Scott Hewitson: That's right. + +Andrew Gnatyuk: Yeah. and… + +Scott Hewitson: That's all. + +Rodri R: Yeah. + +Andrew Gnatyuk: you and some info on the USDC CC payments. + +Scott Hewitson: Yes. So, I'll work on asking about some stats on C payments. anything that we can share on that because I think that's important on the road map timelines. + +Andrew Gnatyuk: Yeah. Yeah,… + +Scott Hewitson: So, I will drop that into city economics and tag you. + +Andrew Gnatyuk: that's awesome. That's nice. Thank you. + +Scott Hewitson: Thank you everyone as always for joining. I like running these calls. I like seeing talking with folks. It's fun part of my job. and looking forward to continue doing it and continue to progress in the network, continue to make things better. and again, anyone who wants to contribute or has ideas, at the very least, I'll listen to you, + +Rodri R: That's good. + +Scott Hewitson: So, yeah. Yeah. Well done. + +Rodri R: Awesome. Thank you. + +Scott Hewitson: All right. Thanks everybody. + +Rodri R: Looking forward. + +Luna: Thank you. Have a good one. + +Scott Hewitson: Have a good one. Take care. + +Rodri R: Three guys. + + +### Meeting ended after 00:29:06 👋 + diff --git a/sig-support/meetings/039-2024-11-20.md b/sig-support/meetings/039-2024-11-20.md new file mode 100644 index 00000000..4ade3fb2 --- /dev/null +++ b/sig-support/meetings/039-2024-11-20.md @@ -0,0 +1,175 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #39 + +## Agenda +- Review of Issues Awaiting Triage +- Updates on Bid Storm Mitigation and Provider Pods +- Community Moderation and Hackathon Support +- Vanguards Program Update for 2025 +- Open Floor for Feedback + +## Meeting Details +- Date: November 20, 2024 +- Time: 07:00 GMT-7 +- [Recording](https://ne52qcczeqfriujvlfvwgehotnrdeyafkoiwfsoctoohul6n3f3q.arweave.net/aTuoCFkkCxRRNVlrYxDum2IyYAVTkWLJwpucei_N2Xc) +- [Transcript](#transcript) + +## Participants +- Tyler Wright +- Scott Carruthers +- Adam Wozney +- Maxime Beauchamp +- Damir Simpovic +- Rodri R +- Forbes Analos +- B S + +## Meeting Notes + +### Opening Remarks +- Tyler Wright welcomed participants to the monthly SIG Support meeting. +- Emphasized the focus on triaging issues in the support repository and providing updates on community and technical support programs. +- Acknowledged contributions from Maxime Beauchamp and the core product team in resolving console-related issues. + +### Review of Issues Awaiting Triage +- Scott Carruthers reviewed two issues awaiting triage in the support repository: + - **Bid Storm Mitigation:** This issue arose due to increased bot activity targeting trial wallets. Existing mitigation measures include signed attributes for trial SDLs, ensuring only participating providers bid on trial workloads. Scott proposed adding further safeguards against future bid storms at the blockchain level. + - **Provider Pod Termination:** An issue where pods stuck in the "terminating" state after a node outage are not rescheduled. Scott outlined possible adjustments to provider builds to ensure forced termination and immediate rescheduling. + +### Updates on Bid Storm Mitigation and Provider Pods +- Tyler Wright emphasized the importance of addressing bid storms and ensuring provider stability as key to maintaining network reliability. +- Scott Carruthers committed to updating the issues with additional remediation details and testing outcomes. + +### Community Moderation and Hackathon Support +- Adam Wozney announced upcoming changes to the Vanguards program for 2025: + - Vanguards will document recurring support issues monthly to inform the development of better documentation and support resources. + - Participation in SIG Support meetings will be added to their responsibilities, with flexibility for global time zones. +- Rodri R highlighted ongoing support for the Akashathon: + - Noted increased activity and questions about hackathon submissions across Discord channels. + - Confirmed that technical queries are being directed to the dedicated hackathon support manager, PiberDev. + +### Vanguards Program Update for 2025 +- Adam Wozney discussed plans to reframe Vanguard responsibilities: + - Focus on documenting recurring support themes. + - Provide feedback through structured forms and meeting participation. + - Strengthen community support and technical onboarding. + +### Open Floor for Feedback +- Participants shared feedback on current support practices: + - Rodri R noted improved spam management but recommended clearer moderation roles and the potential addition of a "Moderator" tag for better visibility. + - Adam Wozney acknowledged these concerns and committed to evaluating role clarity and anti-spam measures. + +### Wrap-up and Action Items +- Tyler Wright thanked participants for their insights and contributions to the discussion. +- Reiterated the importance of ongoing collaboration to address community concerns and improve support systems. + +## Action Items +- **Scott Carruthers:** Update bid storm mitigation and provider pod issues with additional testing and remediation details. +- **Tyler Wright:** Work with Adam Wozney to finalize Vanguard program updates for 2025, including structured documentation and meeting participation. +- **Adam Wozney:** Evaluate and implement improvements to moderation practices, including role clarity and visibility for new users. +- **Community Team:** Direct hackathon-related queries to PiberDev and monitor ongoing support themes. +- **Maxime Beauchamp:** Continue addressing console-related issues and providing feedback to the support repository. + + +## **Transcript** + +Tyler Wright: All right, welcome everybody to sync support. This is a monthly meeting now. It is November 20th, 2024. During the special interest group for members of the community and members of the core team go over any issues in the support repo that are awaiting The support repo is where all issues that pertain to the Akash blockchain There is another the console repo for all things related to the Akash console. I know Max who's on this call here now and others from the core product team actively monitor issues, respond to people that want to help contribute etc. So always want to shout out Max and all the work they do. + +Tyler Wright: again the console repo there's issues in there where you can see if anybody wants to get involved there's usually good first issues and ways for people to get involved. outside of that again Scott from the core engineering team usually leads us through any issues that are awaiting triage inside of the support repo. So I will hand it over to Scott and we can get going. + +Scott Carruthers: All right, thanks I have a very minor cold. It's not really feeling bad, but it's just enough to affect my voice. So hopefully it's not too bad. let me share the screen. Is everyone able to see the issues I'm seeing some thumbs up. so I sound great as always. Thanks. Thanks, W. My Darth Vader voice with a little bit of a cold. Sounds great. so I looked at this prior and there's just two issues that are awaiting triage. So we could probably go through these pretty quickly. + +Scott Carruthers: so the first one as you can see the one that was mo opened most recently was by one of our close community providers. and the title as you can see is bid storm mitigation. So this came up when trials were introduced on the Akash network and with the introduction of trials and trial wallets we saw a lot of bot activity. and when we have a provider that has a number of available GPUs, these bots might try to request a number of GPUs in a very short period of time. and just the trial activity in aggregate which producing a lot of bid activity. Max who's on the call can attest to this because we looked at this very closely with the console team to come up with some remediation. + +Scott Carruthers: So based on our current remediation, I think that we have mostly stemmied the immediate need and we did that by assigned attribute for console related trial SDLs. So there's now a signed attribute for that only providers that are participating in trials are signed with So basically a provider which is a majority of the community providers on the network would no longer bid on trial SDLs. So we've largely mitigated this. the person that created this issue is not currently on the call. So I don't know if anyone else in the community Rodri or Max or any community members would have any perspective on this. + +Scott Carruthers: so I think at this point, and I'll probably do this after the call just so that I don't have to type it in real time, but as soon as we're done with the call, I'm going to put a comment into this that this issue has largely been remedied by the introduction of signed attributes. So again, community providers that are not participating in the trial will no longer bid. so there was a concern prior from the community members that bid activity had gone up to I think somewhere between $50 to $75 a day in provider fees just from this storm of bids that we had on the network. But again that's largely been remediated by steps taken. So what I'm going to update this issue with is the details of what we've taken to this immediate concern. And then I think the question is do we still believe that there's a utility on the network for guarding against bid storms? + +Scott Carruthers: I don't think we have this concern again with trials any longer, but possibly to safeguard against other, new kinds of bid storms within the network. possibly we want to introduce some type of safeguard. So again, I'll detail this case just for our immediate purposes. I'm going to take this out of awaiting triage and I'll put it into the provider repo. and I'll assign myself to it initially. so again, does you can just comment in the issue if you would rather and not or if you want to discuss it live here, that's fine as well. Does anybody have an opinion with the remediation that we've taken and now styate the immediate concern over trial bids? + + +### 00:05:00 + +Scott Carruthers: Does anybody have an opinion on if this issue still needs attention and we still need safeguards on bidtorm activity? But no one really has an opinion on that. on this caller live again I will update this issue immediately after and if anybody has an opinion I'll try to provoke comment from the original author to see if they believe there's cause to look at this issue any further. + +Scott Carruthers: + +Tyler Wright: and I'll circulate it with some other folks that have talked about this issue in the past,… + +Tyler Wright: and I'll share with them and see if the issue still persists for them as well. + +Scott Carruthers: Okay. + +Scott Carruthers: There's obviously already ways to safeguard against this if your bid scripts only so this is very prevalent with most of our GPU providers on the network have safeguards in place so that they will bid on very low workloads. So if I create a Man SDL and have 0.1 CPU and very low memory and very low storage. So we're talking about extremely low cost workloads. there's already mechanisms in place that a provider could enact that they won't build on those workloads because they really only want to bid on GPU relevant and AI relevant workloads. + +Scott Carruthers: So there's already some safeguards against this but if we want to do it at a blockchain level we would have to investigate further. And with that this is actually from the same author which is DC North again one of our close community providers. So I read through this issue before the call. and the concern here is if you have a pod running on a Kosh provider and for some reason that node were to go offline in maintenance activity or unexpected power outage just of a single node. So we're not talking about a clusterwide event but just a specific worker node goes offline. the concern here is that the pod will get stuck in terminating and won't be rescheduled on a different node. + +Scott Carruthers: so, there's possibly some ways in our provider build that we could make some adjustments so that defininity is not active and to ensure that as soon to force the termination of a pod when it goes into the terminating state and to reschedule immediately. so I'll take this out of awaiting triage and put it in the provider repo. Again, I'll assign this to Archer and myself. Anyone have any opinions or thoughts on this issue? So, I'm just going to finish the assignment on this, but besides that, Tyler, I think we're all set. + +Scott Carruthers: + +Scott Carruthers: So as I always offer, along with the issues that we just covered, if there's any other open issues that weren't awaiting triage, but, anyone in the community and… + +Tyler Wright: Go ahead, Adam. + +Scott Carruthers: on this call wants to discuss any other issues, feel free to speak up and we can cover any other issues that are on anyone's mind. + +Adam Wozney: yellow. So, not really an issue, but just something that I've been working on. So, as a part of kind of my 2025 community audit update governance proposal that I've been working on, specifically with the Vanguards, I've kind of reworked the requirements and some of the things that they are going to be needing to do going into 2025. And one of those things is documenting support issues that they are dealing with across Discord or Telegram. so the idea is once a month at the end of the month they'll fill out a form that will have kind of the top themes of the month and then putting in any notes from specific individuals or things that they're noticing that are popping up. I thought this would be useful for many reasons. One is just to kind of document support issues that might not be noticed. + + +### 00:10:00 + +Adam Wozney: two is, taking some of this feedback and maybe creating documentation around, some of these support issues. and a few other things that I've been thinking about that are kind of relevant to this. So, I just wanted to kind of call that out. I'll probably reaching out to you, Scott, and maybe some of these other folks in this call to, see if this is something that, would be useful or making sure that this form that I'm creating would have the right information for folks to find useful. So, just wanted to call that out. Go ahead, Ty. + +Tyler Wright: I think that that's a great idea. part of the agenda for this SIG support call which is why Rodri BS and some people are oftentimes here is we get feedback from insiders and potentially vanguards in the community on things that they're seeing in Discord and other channels to see if there's any themes. I think writing those themes down would be great. I would also love if possible for Vanguards to potentially be able to join this call sick support so it could be a way for them to connect with the community so we can get issues that are awaiting triage from the core engineering team and then anything else people can talk to Vanguards live we can start to talk about some of those themes and then have next steps where we can start to move them so I would love to see this + +Tyler Wright: + +Tyler Wright: move forward. Again, we have a preliminary thought around that, but I think you're putting more structure around that. So, yeah, I would love to include again having Vanguards be more a part of this SIG support, which is a monthly meeting. Now, we have other meetings that are more frequent,… + +Tyler Wright: but if they can join this meeting as a part of their responsibilities, that would be Something to talk about. + +Adam Wozney: Yeah, that's actually No,… + +Adam Wozney: no, that's a great idea. I've been taking out I'm just kind of reframing a lot of the requirements and rewards for a lot of the different kind of community programs and that's actually a great idea to add this as a requirement. at a minimum watch the recording and leave feedback because they're around the world and this might be too late for some folks or whatever. But making it a requirement I think is easy. so that's a great idea. I'm going to add that to the requirements. + +Tyler Wright: And we can always change this time. we try to do it this time because it works for most people across the world except for people on the West Coast, but we're always happy to adapt this time for you, Adam. Cool. + +Adam Wozney: Don't worry about it. I've been up since 2:00 a.m. This baby won't sleep. + +Tyler Wright: This is a great segue though because again after we triage any issues that are waiting triage in the support repo if there's nobody that has anything that they want to talk about in the support repo or the console repo I usually see if anybody here on the call I see a couple of folks that are very involved in the community here. if there's anything on Discord, Telegram, or in other channels themes or things that you've seen over the last month that might be worth calling out. + +Tyler Wright: I know Roger always gives his feedback on spam and some other things and we take some of those conversations to the insider office hours. But again, just want to see if there's anything that any insiders vanguards or just community members have seen in Discord, Telegram, or elsewhere over the last month that might be worth calling out. Go ahead, Roger. + +Rodri R: Besides the usual spam and everything, which seems to be getting a little more or better every time. over the last past few weeks, there's quite a bit of attention over the hackathon. there's people asking about submitting and getting help with that several channels. And I've also seen some people reporting that they've experienced some errors with predator app but tried to help and in the end I think it was PV and me and that replied to several of them and we sent them over to the parap channel because seems to be an issue with their RPC or something. + +Rodri R: Other than that, all good there. Haven't been much in Telegram. + +Adam Wozney: I can briefly talk to the hackathon support. So PyDED is our official technical community support manager for the Akashathon. So if you do see any hackathon questions that aren't getting responded to, just feel free to tag him and as soon as he's back online, he'll respond to those questions. + + +### 00:15:00 + +Rodri R: For sure. + +Tyler Wright: + +Rodri R: Yeah. Sending people over to the hackathon support channel as well. + +Tyler Wright: Any other support call outs that anybody wants to make at this time? + +Tyler Wright: Is there anything else that folks want to talk about in terms of support? Again, there are some folks that have been joining other SIGs and working groups that have been talking about filing support tickets. Again, what we usually do is we usually have folks bring up issues that they're finding inside of Discord. Discord is where the builders are. + +Tyler Wright: And so there's a wide range of people in the community, insiders, vanguards as Adam has mentioned that are there almost 247 365 to provide again technical support if there's something that again can't seem to be solved by that group. There's an escalation path towards the core engineering team and folks can make issues that go in the support repo. So again, if you see something and it's been escalated to that path and you've talked about it in another sacred working group, we ask that you make an issue inside the support repo so that we can talk about these things on a monthly basis during this call and look to get them rectified. People can talk about prioritization of issues as well. + +Tyler Wright: so again as always feel free to join this monthly call or get involved in side of the Discord channel. Cool. I know some folks are just joining us, but again we've talked about issues in the support repo. We've gotten some feedback on what's going on in Discord and other communities. Adam has talked a little bit about the Vanguards program and some of the other programs around the community coming in 2025 or not even coming in 25 but continuing in 2025. just want to see if there's anything else that anybody want to talk about as it pertains to support before I let you all go. Most likely we will have another meeting next month because this is a monthly meeting and again there's always stuff going on. + +Tyler Wright: So we'll most likely have another meeting where if there's anything that's awaiting triage over these next couple of weeks. we'll again talk about at that time. Cool. If there's nothing else then I'll certainly let you all go. Again please stay engaged. There is a form on the website for those that's looking to get more involved and join the insiders. again, Adam talked about many updates coming to the community programs as we enter 2025. So look out for that recording and discussions there. Thank you to Scott as always for leading us through issues awaiting triage. Thank you to Max as always for addressing and being a part of the team that addresses any issues on the akash console side. appreciate everybody in the community as well for all your participation support of others. Hope everyone has a great rest of the day. + +Tyler Wright: There is a working group for the events 2025 later on today. I've just added to Discord. But again, appreciate everybody and we'll continue to talk online. Yes. Feel better, Scott. Bye-bye everybody. + +Scott Carruthers: Thanks. Bye, guys. + + +### Meeting ended after 00:18:37 👋 + +*This editable transcript was computer generated and might contain errors. People can also change the text after it was created.*