meeting notes sig-support #58

sig-support/meetings/058-2026-07-15.md

@@ -0,0 +1,192 @@
+# Akash Network - Support Special Interest Group (SIG) - Meeting #58
+
+## Agenda
+
+* Support repository updates
+* Issue triage and community contributions
+* Upcoming provider and network releases
+* Burn-Mint Equilibrium (BME) updates
+* Provider feature roadmap
+* Community support trends
+* Console redesign and onboarding improvements
+* Open discussion and contributor opportunities
+
+## Meeting Details
+
+* Date: July 15, 2026
+* Time: 07:00 PDT
+* Recording: Coming Soon
+* [Transcript](#transcript)
+
+## Participants
+
+* Tyler Wright
+* Scott Carruthers
+* Joe Deng
+* Joseph Chalabi
+* Rodri R
+* Siva Naik Kethavath
+* Zeke Ezagui
+
+## Meeting Notes
+
+### Opening Remarks & Support Repository Updates
+
+* Tyler Wright welcomed attendees and explained that the Support SIG serves as the primary forum for discussing support-related issues across the Akash Network.
+* The **Support Repository** continues to be the central location for issues relating to the Akash blockchain, provider services, node software, and core infrastructure.
+* Console API users were reminded that API-specific issues should be submitted through the dedicated Console repository.
+* Tyler encouraged community members to actively participate by commenting on GitHub issues, proposing solutions, and collaborating with the Core Engineering team.
+* Community pull requests continue to be reviewed, with several community contributions expected to be included in the next provider release.
+
+### Issue Triage & Community Contributions
+
+* Scott Carruthers reported that, for the second consecutive month, there were **no issues awaiting triage**.
+* The absence of untriaged issues reflects improvements in the issue management workflow rather than manual cleanup before the meeting.
+* New issues are now being categorized correctly at creation, assigned appropriate labels, and routed directly to the responsible engineering teams.
+* The improved workflow has significantly reduced issue backlog and accelerated response times.
+* Scott encouraged contributors to continue discussing implementation ideas with the Core Engineering team before beginning work on larger community contributions.
+* Tyler reiterated that developers interested in contributing to the node, provider, or Console projects can coordinate through GitHub issues, Discord, and the Support SIG channel.
+* Technical contributors may also qualify for community bounties after discussing implementation plans with the engineering team.
+
+### Upcoming Provider & Network Releases
+
+* Tyler shared that a new provider release is expected shortly, combining both Core Engineering improvements and community-submitted enhancements.
+* Providers were encouraged to monitor official announcements and upgrade promptly once the release becomes available.
+* Community Provider Console users will receive upgrade guidance and documentation to simplify the migration process.
+* Scott outlined several important infrastructure updates scheduled over the coming weeks.
+* A new network upgrade will be required to support changes to the Burn-Mint Equilibrium pricing oracle following backend updates within the Pyth Network.
+* The upgrade will primarily introduce updated smart contracts required for the revised oracle infrastructure.
+* Scott confirmed that these activities are expected to take place over the next few weeks.
+
+### Provider Feature Roadmap
+
+* Scott announced that the upcoming provider release will introduce support for **Trusted Execution Environment (TEE) confidential computing**, enabling confidential compute workloads on the Akash Network.
+* Support for **InfiniBand networking** will also be included, allowing GPUs located on separate physical hosts to communicate more efficiently for distributed AI workloads.
+* These capabilities represent significant infrastructure improvements for high-performance GPU deployments and AI applications.
+* Additional details regarding these features will be shared during the upcoming Provider SIG meeting.
+
+### Community Support Trends
+
+* Rodri R reported that most recent community support requests involve provider setup and installation issues.
+* The majority of reported problems were traced to deployment or configuration mistakes rather than software defects.
+* Community members continue requesting updates regarding the provider verification and audit process.
+* Rodri also highlighted a recent scam attempt within Discord where malicious users shared fake airdrop images and fraudulent links.
+* The incident raised questions about improving Discord moderation and automated scam detection.
+* Tyler noted that the Core Engineering team continues to improve the provider verification process to make audits more automated, scalable, and accessible for providers.
+
+### Console Redesign & Onboarding Improvements
+
+* Tyler announced that the Akash Console is undergoing a significant redesign together with improvements to the onboarding experience.
+* Existing documentation and getting-started guides will require updates once the redesign is released.
+* Contributors interested in technical writing, documentation, React, or TypeScript development were encouraged to participate.
+* The redesigned onboarding flow will undergo additional usability testing during an upcoming hackathon.
+* Community members from Akash Club have already participated in early testing and provided valuable feedback.
+* The hackathon will provide an opportunity to observe how first-time users interact with the redesigned Console experience before its broader release.
+* Tyler explained that documentation updates will become an important part of the wider go-to-market strategy following the redesign.
+
+### Community Contribution Opportunities & Closing Remarks
+
+* Tyler encouraged developers interested in Go, React, and TypeScript to become more involved in Akash's open-source ecosystem.
+* Contributors were reminded that implementation discussions should begin through GitHub issues before development starts.
+* Community members were encouraged to remain active within Discord, particularly the Support SIG channel, between monthly meetings.
+* Tyler reminded attendees about the Economics SIG later that day and the upcoming Provider SIG meeting the following week.
+* Members were asked to watch Discord for announcements regarding provider releases, Console improvements, and other technical updates.
+* The meeting concluded with thanks to contributors, Core Engineering members, and the wider Akash community for helping maintain a responsive support process.
+
+## Action Items
+
+### Scott Carruthers & Core Engineering Team
+
+* Continue maintaining rapid issue triage and assignment workflows.
+* Prepare the upcoming network upgrade supporting the updated Burn-Mint Equilibrium pricing oracle.
+* Release the next provider version with confidential computing and InfiniBand support.
+* Continue improving the provider verification and audit process.
+* Coordinate technical documentation for upcoming infrastructure releases.
+
+### Tyler Wright
+
+* Publish provider upgrade announcements and migration guidance.
+* Coordinate community testing for the redesigned Console onboarding experience.
+* Continue encouraging open-source contributions through GitHub and Discord.
+* Promote upcoming Provider SIG and Economics SIG meetings.
+* Share updates regarding provider releases and Console improvements through official community channels.
+
+### Joe Deng
+
+* Coordinate community contributors interested in documentation and technical writing.
+* Continue identifying contributors eligible for technical bounties.
+* Support documentation updates for the Console redesign.
+
+### Rodri R
+
+* Continue monitoring community support channels for recurring provider issues.
+* Assist with Provider Console upgrade documentation.
+* Report recurring support trends to the Core Engineering team.
+
+### Community Contributors
+
+* Continue submitting bug reports and implementation ideas through GitHub.
+* Participate in provider release testing after deployment.
+* Contribute documentation updates following the Console redesign.
+* Help test the new onboarding flow during community hackathons.
+* Join the Support SIG Discord channel to collaborate with Core Engineering and other contributors.
+
+## Transcript
+
+Tyler Wright: All right, welcome everybody to SIG support monthly meeting. Today is Wednesday, July 15, 2026. During the special interest group for support, the Accasha network community comes together to talk about any support related issues. Again right now the support repo is where all issues related to core or anything related to the node or the provider is managed. again instead of having issues repos inside node and issues repos inside our providers the support repo is where all issues related to the core akos network blockchain and the provider live.
+
+Tyler Wright: There is also an issues area air repo. So again anybody that's using console API feel free to submit issues inside that repo in the class network organization. If anybody has any specific issues that they want to talk about, feel free to drop them in the chat or Roger, I know that you do a good job of collecting information from the community for folks that can't make it. so again, if there's anything that you're seeing that needs extra attention, feel free to bring it up. Otherwise, as we always do, there's three members of the Akash core engineering team from Overclock Labs here.
+
+Tyler Wright: Scott usually leads us through any issues that are awaiting triage. and then we can open it up to any other issues that anybody wants to get discussed. I'm sure again those very knowledgeable people between Scott and Zeke and Joseph here that can help support or answer any questions. Anybody wants to get involved in solving issues again please leave a comment under a specific issue. I know that Chilabi and Zeke have been looking at a couple of PRs from community members that are actually value ad and we'll be pushing those through I believe in the next provider release. So again if anybody wants to get more involved just please feel free to drop a message in the SIG support channel and discord drop a comment under a specific issue reach out to a member of the core team. Without further ado, I'll hand it over to Scott.
+
+Tyler Wright: to see if there's any issues that are awaiting triage that need to be triaged and…
+
+Tyler Wright: then we can discuss any issues that anybody wants to discuss.
+
+Scott Carruthers: All right,…
+
+Scott Carruthers: thanks so for the second consecutive month, this is a very quick exercise. So there is nothing in awaiting triage. And this again is not artifacts of me going in and taking a lot of things out of awaiting triage before the meeting. doing any housekeeping. This is just the state. as it was when I first reviewed it this morning. So I think this is just a remnant of when issues are created. as a core team, we are just more attentive in the way that issues are created. it's very less likely that things are going to be unassigned and they're from their creation land with the right labels and assigned to the correct team members.
+
+Scott Carruthers: So just to prove this real quickly, if I go into awaiting triage, we'll see that there's no issues awaiting triage. So, no need to actually go through this exercise this morning. and everything is assigned again to the and also to the proper core team members. so no triage activity necessary. so with that, I'll just open it up. so obviously there have been a number of issues created since we last met for sig support. so if there's any issues that are not in awaiting triage but just we can discuss those with the core team nice and easy Tyra I'll hand it back to you.
+
+Scott Carruthers: Maybe some other discussions will come up either now or obviously after the call as well. If anybody in the community that wants to discuss these issues with the core team, just reach out to us and in Discord. But with that, nice and easy and I'll hand it back to you, Tyler.
+
+Tyler Wright: Thank you, I guess it's support adjacent because it's provider, but again, there's been a lot of work that's been going on provider related. and I believe there's a new release with some fixes from the core team, some fixes from the community and some new features that will be launching soon. I'm sure we'll talk about it a little bit more during SIG providers next week, but I believe it should be released before then. so any again providers or any folks on this call that actively work with providers just look out for any announcements that come down over the next couple of days and make sure that all community providers are upgrading again the provider console team will have an upgrade path for those that use provider console.
+
+
+### 00:05:00
+
+Tyler Wright: It'll be made easy from instructions from most likely Rodri, just want to go ahead, Scott.
+
+Scott Carruthers: So to that point just as this is the one time that we come together I'll just throw out some upcoming activity just to make sure that we have that recorded and see if anybody has any questions. So we have a number of network activity coming up. So there's a update that's necessary for BME and our pricing oracle. so basically the Pyth feed that we get pricing updates from is changing their backend strategy which makes us need to adjust our smart contracts.
+
+Scott Carruthers: And then we will do a associated network upgrade to activate those new smart contracts on chain. not probably that that needs to happen over the next couple of weeks. so there'll definitely be a new network upgrade mostly associated with smart contract updates. so that's coming up. And then as Tyrone mentioned, there's a number of provider I think there actually all be bundled in one release, but there's also some provider upgrades that will be released shortly to primarily enable confidential compute. So obviously that is exciting on the network.
+
+Scott Carruthers: So that's a big one and a couple of other also Infiniband for the ability to access GPUs across different physical host is going to be introduced. So those are the two major things that we're going to be releasing a new provider versions very shortly TEE confidential compute support and also infiniband support for GPU access across host. so I just thought I would mention since we're all together, those are the primary activities that are going to be upcoming over the next couple weeks or next few weeks.
+
+Tyler Wright: Thank you, Rodri, as we always do, as a key member of the Akash club, Akash insiders, for a long time, I know that as well as Joe, who's Akash community manager, really have an ear to the ground on what's going on in some of the builder channels like, Discord and some other channels like Telegram. I just want to see Joe Roger if there's anything that you have seen in terms of support themes that may be worth talking about here or any other items that might be worth discussing as it pertains to Go ahead, Roger.
+
+Rodri R: So on this court just mostly people asking about provider setup issues but I think there were mostly on their end not following instructions as they should and there was this weird scamming attempt that I don't know why the Discord bot didn't identify it and ban as it usually does, but the user update uploaded several images and they were pointing to an airdrop and some scams. not sure how it went by those and other than that only people asking about provider audits as well but that's still on the work I believe.
+
+Tyler Wright: Yes. As you mentioned, I know the core team has been working and testing provider verifications which is the improved provider audit process. again currently the process is still fairly manual but core team has been working on a longer more robust version that again anybody that qualifies will be able to do provider verifications. So be a more open process as well. Thank you Rodri.
+
+
+### 00:10:00
+
+Tyler Wright: Is there anything else that anybody wants to make sure that we talk about in terms of support? Again, we looked at any issues that are There were none that were awaiting triage. again, if anybody wants to get more involved in solving issues, please feel free to leave a comment under a specific issue. Obviously, the code base for a node and provider are open. so again, you can see how things are done. and then talk about what an implementation plan would look like, talk to members of the core team. and if that plan is approved then certainly support and move into execution phase. And again we can work with Joe on bounties. I know he's always looking for folks in the community that can be helpful from a technical standpoint.
+
+Tyler Wright: One other item that I will put out here, and I've already talked to Joe about this, is there are some changes being made to the  console onboarding flow and console is going through a redesign. Again, we talked about this in SIG clients. There are opportunities for folks that want to get involved in updating the console air and console documentation as well as getting started. I know that again some of the information will be out of date. there will be a wider go to market strategy for this coming soon. But again the console team wants to do some testing and there's a hackathon happening later this week. so it's a perfect opportunity to share with a bunch of folks in the community. I know that folks,
+
+Tyler Wright: on the Akash club have done some testing. So big shout out to everyone that's been involved in testing. But again, Friday at the hackathon will be an opportunity to test onboarding flow with people that are not as familiar with console or the Akash network and see how they interact with it. Any other questions, topics related to support that folks want to make sure gets brought up as members of the core team or just with the community at large? All right. If not, then you all can get some time back again. we'll meet next month. there is a sick economics meeting today.
+
+Tyler Wright: And then the state providers meeting next week. But again please look out for updates and announcements inside Discord because there's a number of features whether it be on the console side or provider side that are imminent. So again if you're a provider look out for announcements. if you are a technical developer and want to get more involved in a class network project this is a perfect sig to join. Again, there's a number of ways to get involved with open issues if you're a Go developer. or again, if you want to React or TypeScript, get more involved with the console team. All right, I hope everyone has a great rest of their day. Again, thank you, Scott, for walking us through issues in the support repo and look forward to seeing you all online in future meetings.
+
+Tyler Wright: If anybody has any questions in between meetings, you feel free to drop them in SIG support or just feel free to reach out to myself, Joe, who's Caleum on Discord, Roger, any other members of the, Vanguards, Akos Club, etc. Much appreciate everyone's time today. Hope everyone has a great rest of their day. Thank you all.
+
+Joseph Chalabi: You guys.
+
+Scott Carruthers: Yes, everyone.
+
+
+### Meeting ended after 00:15:05 👋
+