Helium Community Call October 7, 2026 Source: Helium Discord Duration: 59m 00s [00:00:02] Okay, one more minute and I guess we'll get started. [00:00:08] I feel like the ping hasn't gone out yet though, this is very strange, seems a little delayed. [00:00:14] The audio? [00:00:17] I'm sorry? [00:00:20] You mean the audio? [00:00:21] Or like, what's happening? [00:00:22] Oh, like the notification for people to make a call, usually it's like, sometimes it's [00:00:27] instant, sometimes it's like 10 minutes later and you'll see a wave of a hundred people [00:00:31] come in. [00:00:33] I feel like it hasn't- oh, maybe it's starting to go up, there we go. [00:00:38] Now you can see all the people joining, now the ping has gone out. [00:00:41] All right. [00:00:42] So let's give it a couple more minutes, then. [00:00:44] I think it's important. [00:00:47] There we go. [00:00:48] Can you see the screen? [00:00:50] Just changing this. [00:00:53] Yes. [00:00:55] Wait, did he do a PDF? [00:00:59] It's OK. [00:01:00] It doesn't matter. [00:01:01] I can just-- [00:01:01] Sorry, that's the-- [00:01:03] Oh, that's the other one. [00:01:05] Yeah. [00:01:06] You're on the wrong one. [00:01:09] All right. [00:01:10] One moment, I'll post it in the gear. [00:01:15] So you have a couple more minutes. [00:01:18] I mean, that's the last one that you shared to me this morning, [00:01:22] right? [00:01:23] Yeah, I was making some edits. [00:01:24] Try that one there. [00:01:28] OK, thank you. [00:01:35] Thank you. [00:01:36] Thank you for the beautification of the deck this morning. [00:01:43] Yeah, that's the one. [00:01:48] Oh, now I see people coming. [00:01:51] Let's go. [00:01:52] Awesome. [00:01:52] Yeah. [00:01:53] Awesome, awesome, awesome. [00:01:55] OK, and now this is the right one. [00:01:58] OK. [00:01:58] Perfect. [00:01:59] Yeah. [00:02:00] Oh, I edited the right deck. [00:02:04] I think so. [00:02:05] I think so. [00:02:06] You did. [00:02:07] You did. [00:02:07] You did, yeah. [00:02:08] Sorry, I my bad for confusing people on that. [00:02:12] You totally did, but that's OK. [00:02:15] Alright, so let's I would say let's get started and we have [00:02:18] a lot of things to cover. There's a lot of questions I [00:02:21] want to get to in the AMA part, so maybe you want to kick us off [00:02:27] and then I'll kind of take it from there. I'm going to start [00:02:29] like going around the block. [00:02:32] Absolutely. OK, I'm just going to give you my quick spiel here [00:02:34] as I usually do every time. So this call is recorded. It will be [00:02:39] posted after this call is finished in the Helium general channel, you'll see it [00:02:43] pinned. I'll also have a transcript and an AI summary for you as well, so don't [00:02:49] worry if your audio breaks or you have to step away for a minute, we'll [00:02:53] have you covered. A couple of housekeeping things as well. Scammer [00:02:59] warning, as you've seen in the crypto versus, I mean this is nothing new, but [00:03:03] scammers are out in full force even just this morning, I'm squashing them all over [00:03:09] the place please please please if anyone is DMing you that they can help you with [00:03:14] your wallet to click on some link that will take you to Phantom anything like [00:03:19] that please be very weary of what it is 99% of the time it's a scam if you have [00:03:25] any questions about the helium wallet please post it in general and we'll [00:03:29] answer your questions in there you'll see people cloning like myself or a [00:03:35] moderator making themselves look like a moderator just be weary of that please [00:03:38] Don't click any unsolicited links. [00:03:41] And lastly, where to ask questions for this call. [00:03:44] So I'm going to put it one more time in the chat. [00:03:48] We have ama.helium.com. [00:03:53] Put it in the chat here. [00:03:57] There you go. [00:03:58] If you have any questions, pop them in there. [00:04:02] And we'll get to them at the end of the call. [00:04:04] Otherwise, unless I'm forgetting anything here, [00:04:08] I think we're good to go. [00:04:11] We're going to move to the next slide, actually. [00:04:15] two slides. We'll have a little agenda there. [00:04:17] >> Yeah. I already did this. [00:04:21] >> There we go. That's today's agenda. [00:04:25] >> Let me start from here if you want, Keenan. [00:04:27] Thank you for kicking us off. [00:04:29] Thank you everybody for joining us. [00:04:32] What I want to do today with the team here is to give [00:04:35] an update on a little bit of product update, [00:04:39] an update on the growth of the network, [00:04:41] some deployer spotlights, [00:04:43] an update on IoT divestiture efforts, [00:04:47] and then it would open up the floor for a Q&A. I'm going to call up different members of the team [00:04:53] to cover different aspects. This is not just me being lazy. Actually, I do want to give recognition [00:05:01] to people that are actually doing the work and also for everybody to know who those people are. [00:05:06] And I think it creates even more transparency and more trust, hopefully, into the team that [00:05:14] is running the show. So let's start from the product technology update. You might have noticed [00:05:22] that we started to push more and more content around how DAS, our Wi-Fi and Passpoint, which [00:05:30] is the technology stack that Helium uses for offload, compares or complements or can play [00:05:38] together with DAS. DAS for the ones that it's not familiar with, DAS stands for Distributed [00:05:45] antenna system. It's a fairly old technology stack that is being traditionally used in indoor [00:05:53] venue to distribute cellular signal inside. So you have to think of that a little bit as a [00:06:01] almost like a dripline, like a irrigation dripline in which you have a centralized backroom when [00:06:07] where all the they call it signals, the radios are hosted and then there is cables, both fibers and [00:06:14] coax, they run across all the all the venue and they're just like a drip line, they leak [00:06:21] coverage, they leak radio frequency, radio transmissions inside the building. That's traditionally [00:06:29] it was as it was funded by carriers to ensure that is a good coverage inside venues. Of course, [00:06:38] from things like airports down to shopping malls, college and and all sorts of different venues, [00:06:45] Over the years though, the cost of those DAS system continues to go up in terms of installation, [00:06:52] radio, maintenance. And so what we see is that the upgrade cycles of DAS has slowed down [00:07:01] significantly in the past 15 years. The result of that is that when you think about DAS, [00:07:09] you don't, if you go behind a little bit, DAS means one thing, which is a distribution [00:07:16] model. But, you know, in the world of cellular, there is different bands, there is different [00:07:22] frequency inside that bands, and over the years, the phone have supported more and more bands, [00:07:29] more and more frequencies, because, you know, the demand, the mobile demand for cellular data is [00:07:34] increased. So every time there is a new band that needs to be supported, the DAS system should be [00:07:41] upgraded in order for that for that phone to work optimally. And so this is one of the the team, [00:07:49] the technical team led by Joey Padden, put together a report, a comprehensive report on [00:07:57] DAS and Passpoint, and you can see that essentially over time if the DAS system does not get upgraded, [00:08:06] which means the carrier won't pay for it or the venue won't pay for it, the amount of spectrum [00:08:13] that that DAS system supports goes down over time, because essentially phones continue to [00:08:19] support more and more bands, but that DAS system doesn't. And so together with that, [00:08:24] that goes the performance, of course, of the system. And so you can see here there is, again, [00:08:31] just this one plot showing our never upgraded DAS that was covering 100% of the bands in 2011. [00:08:38] Now in 2026 only covers 18%, which means that the capability of the phones is you're only using 18% [00:08:46] of the capability on new phones. A typical DAS system is at the 81% is what we have today, [00:08:54] which is what in the report is called Track B, which is a replacement cycle between two and five [00:08:59] years, an upgrade cycle between two and five years, so you're still lagging behind. This is also the [00:09:05] other big part. Every time there is a new band that gets issued for cellular, essentially there is [00:09:13] almost a three to five years delay into that system, even the one that get upgraded, to actually [00:09:19] pick it up. And that costs performance and support to that system. Wi-Fi on the other end, [00:09:27] you know, the replacement cycles are different, of course, but the Wi-Fi 6 and Wi-Fi 7, sure, [00:09:35] you do have a 6 GHz replacement cycle in Wi-Fi 7, for example, but it's just a very different [00:09:41] type of beast because it works in big chunk of spectrums. And so every time there is a big [00:09:47] big technology shift from 2.4 to 5 to 6, it's just a little easier to track, and the stack, [00:09:54] which is the Passpoint stack, is keeping up with that because it goes across, cuts across [00:09:59] the different version. [00:10:02] And you can see here how this is, to me, is the most important part of the report, is [00:10:09] that the amount of phones that support Passpoint, how that curve was essentially zero in 2011, [00:10:17] And when the standard got launched, it started to go up. [00:10:20] And then now we are almost 100% of the phone, [00:10:22] they are Passpoint OS capable. [00:10:25] And that is kind of like goes together with this, [00:10:27] like the DAS, with an intersection with the DAS system [00:10:32] supporting less bands. [00:10:33] So that's the opportunity. [00:10:34] That gap is the opportunity [00:10:36] that Wi-Fi is covering essentially. [00:10:42] All this work on DAS and Wi-Fi only makes sense. [00:10:48] It only makes sense if you can trust Wi-Fi. [00:10:51] The only way that gap will be deemed trustworthy, [00:10:57] will be deemed usable, [00:10:59] will be deemed worthy of carrying service traffic, [00:11:04] it will be only if Wi-Fi can be trusted. [00:11:07] And a big part of that trust in Wi-Fi [00:11:10] comes from network metrics. [00:11:14] We've been working with the WBA for a long time [00:11:17] this point to since the very inception of this access network metrics group and now we just turn [00:11:25] the corner into a very interesting report which is everybody should download this report, it's now [00:11:31] public. The way the WBA works is that we say we really, Joey Padden as our chair in the group [00:11:39] works on a bi-weekly basis into that group that eventually all the findings will roll up into a [00:11:46] white paper for internal use. So this white paper was released for internal use at the WBA [00:11:52] some months ago and then now is available publicly. And so maybe I want to stop a second [00:11:58] and I'm going to turn to Joey to tell us what do you think is the most important part [00:12:06] of this phase three for network metrics that got released by the WBA? [00:12:11] The most important part is the collaboration in public with a tier one operator to put quality [00:12:30] metrics into productions. So this paper explains how we worked together with AT&T to improve [00:12:55] their production system with quality metrics? [00:13:01] >> That is pretty clear. [00:13:03] This is a snapshot from the WBA website. [00:13:06] The 17,000 access points, [00:13:08] those are the helium access points. [00:13:10] Those are the helium hotspots, [00:13:11] the greenfield helium hotspots, [00:13:13] and the 250,000 daily active users, [00:13:16] the ones that those hotspots are serving. [00:13:17] Yeah, this paper was finalized in February, and that's why those numbers have a delta [00:13:42] from our current offloaded users and active radios. [00:13:51] Thank you, Joey. And also another important differentiation, on the road to trust Wi-Fi [00:14:02] more, everything starts with metrics in terms of monitorability. But monitorability without [00:14:10] taking action is not a complete service offering. And that's why we launched [00:14:19] WOX, which is our Wi-Fi Offload Experience gateway, because beyond monitoring the quality [00:14:26] metrics, the most important part is act on those quality metrics and be able to take decision [00:14:33] that allows operator and venues, we can talk about that in a second, to decide how to steer [00:14:42] traffic between cellular and Wi-Fi or in the case of an indoor venue between DAS and Wi-Fi. [00:14:49] So, for the ones that are not familiar, WOX is one of the products that are part of the HeliumOS [00:14:56] platform. And WOX essentially is an engine, is a decision engine that on one end collects [00:15:06] metrics coming from the Wi-Fi network. And right now it's from the Helium hotspots. We are working [00:15:14] to have at least a couple of our brownfield OEMs as well. I think I don't even know. [00:15:22] Joey, please correct me. I think it's Ubiquiti and Meraki that we are playing with to get [00:15:27] metrics out of it. Yes. Right? It's Ubiquiti and Cisco Meraki. And so on one end, it collects [00:15:34] metrics from the Wi-Fi. On the other end, it collects metrics also from the cellular stack. [00:15:39] and then based on that quality of experience scoring across these two accesses it makes a [00:15:47] decision about do we want the user to connect the wi-fi, do we want to keep that user on the wi-fi, [00:15:54] so it's not just about can the user connect, it's about should be the user connecting to the wi-fi [00:16:00] and should it stay connected to the wi-fi, which is there are two different things. There's one [00:16:05] thing to decide if you want to allow a user to connect to Wi-Fi and then another thing is that [00:16:10] once the user is connected, shall the user stay connected to Wi-Fi based on the quality of [00:16:15] experience that he has. So pretty exciting to me to see how the industry is reacting. [00:16:25] We'll talk about a little bit, Hopefully Woody will touch on a little bit how this is playing a role [00:16:30] in our carrier partnership, both in the US, beyond our AT&T one, also with others, or [00:16:38] is that all the WOX is taking in those conversations, as well as in the venue world and the real [00:16:44] estate world, there is a lot of venues that are interested in using WOX because, going [00:16:50] back to this, if you are a venue that stays between the typical and the never upgraded [00:16:56] in this region here, and the carrier won't pay anymore for upgrade, you have a problem. [00:17:02] And that means that you have to complement your DAS with Wi-Fi, but you want to do that [00:17:07] in a smart way so that the users don't complain about the user experience. [00:17:11] So WOX can be used from the carrier in a centralized fashion, can also be decentralized [00:17:18] or distributed and be working on a venue by venue basis. [00:17:23] So that is another thing that we are exploring with some of the venue owners and some of [00:17:27] the venues to essentially also monetize and bring in additional revenue by installing [00:17:35] WOX at venues on the localize, an unlocalized way, I should say that's the right word for [00:17:40] it. [00:17:44] I'm going to turn it over to Woody to give us an update on carrier partnership and what [00:17:48] is the growth of the network, some interesting metrics to look at and then what can you do [00:17:54] to help? [00:17:56] Absolutely. So I know that many people on this call have been wondering when can I tier [00:18:03] realign my venue? When can I tap into these awesome reward multipliers that we passed [00:18:09] in the hip? And for those of you who've already spoken with me or members of my team about [00:18:14] it, you know, the answer is, oh, we're working on it. We're working on it, right? We are [00:18:18] in the late stages of a renegotiation, specifically with AT&T, about implementing that higher [00:18:27] reward per gigabyte for more strategic venues, right? As you can imagine, this is [00:18:36] a very bureaucratic process and it takes time. My best guess is that we will get this done [00:18:43] by the end of the year, but it will continue to be a process. The good news is that we're [00:18:51] pushing them and we're really demonstrating how valuable Wi-Fi data can be, and we're [00:18:59] kind of changing the story. Like Mario talked a lot about DAS and how DAS is on the decline. [00:19:06] Well, I think Wi-Fi is really going to eat that market, and that's a market which traditionally [00:19:11] was billions of dollars, right? So there is absolutely a shift in the way that people are [00:19:18] approaching Wi-Fi, and we're working with carriers to formalize that shift into money that we can [00:19:24] route to deployers, right? So bear with us there. Really awesome things are happening with AT&T. [00:19:31] Also, there are certainly conversations in earlier stages that they're happening with other large [00:19:37] carriers here in the United States, who I'm going to refrain from saying the names of, but I'm sure [00:19:42] that you can guess. And that across the market, for all of the giant carriers, and certainly for [00:19:49] MVNOs as well, we're seeing a shift in the way that they approach Wi-Fi and seeing it as significantly [00:19:55] more strategic in the same way that traditionally you might have looked at the distributed antenna [00:20:00] system, right? But I think Wi-Fi is in the process of being born from an experimental thing [00:20:09] into a mission-critical thing. And that will, I think, bode really well for the network. [00:20:16] I'm going to talk about network growth in the backlog in a second, because there are two slides [00:20:21] that I'm going to share. And then after that, I'll talk a little bit about how you can help. [00:20:26] So can we go to the next slide? All right. So first I want to talk about signing new venues. So [00:20:37] those red bars at the bottom here are people unplugging radios, right? So they're slightly [00:20:44] different shades of red or orange there for whether it's brown field sites getting turned off, [00:20:48] whether it's green field sites getting turned off. But a really important trend for you to notice, [00:20:54] well, hey, people aren't really unplugging very much anymore. And we went from having people [00:20:59] on plugging hundreds of APs worth of coverage to people doing it sort of not at all anymore. [00:21:07] And that's a great shift. I would love to see that continue. And I think that has something to do [00:21:12] with rewards per gigabyte going upwards, right? Another thing you'll see in there is those two [00:21:19] very large green bars that you have, which are the last two full weeks that we have data for, [00:21:24] we're signing a lot of new sites, right? [00:21:29] So things have absolutely been ripping on the deployment side, [00:21:33] and we have had amazing channel partners and [00:21:38] community members that have been bringing us into accounts, [00:21:40] as well as a bunch of deals that we've been signing directly with venues, [00:21:43] to bring some awesome tier 1 and tier 2 venues onto the network, [00:21:47] and to bring thousands of additional APs of coverage on. [00:21:52] So the trend could not be more positive [00:21:56] in terms of signing new venues. [00:21:58] One thing to note, however, about Brownfield [00:22:00] is that when you sign a new venue, [00:22:03] it doesn't mean that they are suddenly online [00:22:05] and sending data. [00:22:06] And herein lies the rub. [00:22:08] Can you go to the next slide? [00:22:12] So we have this really big backlog, right? [00:22:16] And this is pretty normal actually, right? [00:22:18] You sign a large strategic venue [00:22:21] and you have process that you need to go through [00:22:24] to help them on board. [00:22:26] And as much as it seems as though the onboarding [00:22:29] should be pretty easy [00:22:30] and we can get it done in a 20 minute call, [00:22:31] the more complex and the larger the organization is [00:22:37] that you've signed with, [00:22:38] the more work that it takes [00:22:40] to actually get that onboarding done. [00:22:41] And we're in a state now [00:22:43] where there are almost 40,000 access points [00:22:48] that are signed and the ink is dry, [00:22:50] but we have not yet actually onboarded them [00:22:52] onto the network, right? [00:22:55] There is good news to share here as well. [00:22:57] If you look at this chart, the green striped bar [00:23:02] is the number of access points worth of coverage [00:23:05] that are leaving the backlog. [00:23:08] And the blue bars are the numbers [00:23:09] that are getting added to it. [00:23:10] So what you can see is that recently [00:23:12] we have had a pretty significant change [00:23:14] where we are now pulling things out of the backlog faster [00:23:18] than we are moving things into the backlog. [00:23:22] And this is actually a silver lining [00:23:24] around the loss of T-Mobile coverage that we had, [00:23:29] or the temporary loss of T-Mobile coverage, [00:23:30] because a lot of people in the backlog [00:23:32] were simply waiting for clarity [00:23:34] in terms of when they were going to get T-Mobile coverage. [00:23:36] So being able to say, all right, listen, [00:23:40] you're not going to get that immediately, [00:23:41] we're working on it, but let's get AT&T onboarded, [00:23:45] has allowed us to begin to really clear [00:23:46] a lot of that backlog out, right? [00:23:49] Now to the question of, [00:23:51] well, how can community members help us here? [00:23:53] First of all, if you are a member of this backlog, [00:23:57] and I know there are plenty of people online here [00:23:59] that have signed deals with my team [00:24:02] to bring a venue on board, [00:24:04] please help us to move these forward [00:24:06] and get those onboarding calls scheduled, right? [00:24:09] We are staffed up and ready to assist [00:24:12] from a sales engineering standpoint. [00:24:14] And the faster we can move through this backlog, [00:24:17] also the faster that this will layer on more leverage [00:24:22] for us to push other carriers onto the network [00:24:24] and to maximize the dollars per gigabyte [00:24:27] that we're getting out of them. [00:24:29] And that I know that there are tons of deployers out there [00:24:32] who have very full pipelines of amazing strategic venues, [00:24:37] more hospitals, more universities, [00:24:39] more tier one venues like stadiums and concert halls. [00:24:45] Please lean on my team and be transparent with them [00:24:48] about what you're working right now [00:24:51] so that we can get ahead of it [00:24:52] and make sure that we extract as much as possible [00:24:56] out of the carriers on your behalf. [00:24:58] And also we have visibility into your accounts [00:25:00] so that we can set them up for success, right? [00:25:03] One of the biggest failure cases that we can run into [00:25:06] is the deployer coming to us last minute saying, [00:25:09] "Hey, I've got this strategic venue. [00:25:10] I want to sign it up tomorrow," right? [00:25:13] And that's just simply not how the carriers operate. [00:25:16] They're really slow moving behemoths. [00:25:18] And so being able to socialize a strategic venue in advance [00:25:22] makes a huge difference. [00:25:24] But anyways, the TL;DR from my side is tons of good news [00:25:28] and more on the way. [00:25:30] All right, thanks. [00:25:31] - Thank you, Woody. [00:25:32] And I wanna double down on that call out. [00:25:35] Like if you have venues that need to be onboarded, [00:25:38] get together with the team, [00:25:39] send an email to business@helium.com or to Woody or for myself, [00:25:43] like let's get that backlog clear. [00:25:46] And also strategic venues, [00:25:49] if you are even in early conversations, [00:25:52] you should have a little more the early conversation, but if you're approaching, I would say, closure [00:25:56] with a venue that you think is going to tier one and tier two categorization, talk to us, [00:26:02] because we can start circulating that internally with our carrier partners so that we can get [00:26:10] there, you know, internally there is a lot of processes that are happening. [00:26:13] Just like we are doing our own processes, there are their own processes that as wi-fi is getting [00:26:19] more and more strategic. There's a lot of processes across departments that roll up to different SVP [00:26:24] inside of a gigantic organization like AT&T that they are getting formed, which is a great news. [00:26:30] It's great news, but also means that sometimes we need more time in order for that venue to be [00:26:35] evaluated to get in touch with the RAN market that manages that venue and eventually to get it out [00:26:42] and to get it updated and to get it turned on. Even when it gets turned on, I'm sure there was [00:26:48] some venue, for example, the stadium is one of them, we will see iterations of how much traffic [00:26:53] the carrier would love to see on wi-fi versus DAS and it will be an iterative process. I know that [00:26:59] it seems that we've been back at this for like two years. In reality, we were very early and I [00:27:06] think it was great because we got in at the beginning of this new wave of Passpoint. Now is [00:27:13] where the wheel has started to turn into processes and SOPs inside carriers to capitalize on [00:27:19] that growth. So, I still want to make sure that everybody understands clearly what I'm [00:27:24] saying that we're still early in many ways, and some of those processes are just getting [00:27:30] started in those companies. So, that's why things like tier one and tier two assignments [00:27:36] and contract negotiation for that, they're still pretty much ongoing. I don't think there [00:27:42] there's never been a tiered structure before [00:27:45] until like six months ago when this started to become a thing. [00:27:51] I wanna also give some spotlights on deployments. [00:27:54] Some of you that already follow our social, [00:27:57] they're familiar with this, but I think it's good to, [00:28:01] it's good to go over what I think are [00:28:03] one of the biggest opportunities and also I wanna thank, [00:28:08] I wanna thank the community that makes this possible. [00:28:10] I mean, the reason why we have those deployment spotlights, [00:28:13] spotlights is because we do have people and companies [00:28:18] that go out there and they close these venues for us. [00:28:20] So early this month, we announced this ocean side coverage [00:28:26] by ocean properties. [00:28:29] We have almost, if I recall, 23 or 35 properties. [00:28:34] They are now part of Wi-Fi offload. [00:28:37] You can see, you can hear, you can see more into the website, [00:28:42] the blog post but some of the number like we're still talking we're talking of tens of tens of [00:28:48] thousands of user of unique of unique users these are just some of the example and these are just [00:28:53] for the 30 days ending in September 9th which is when the blog post was published so this is a lot [00:28:59] of data that those properties are doing we have many more into the pipeline that we're going to [00:29:04] feature but it was one of the one that we that was featured on our blog post then moving on [00:29:11] I want to talk about this SSM Health. And I'll talk both about what's awesome and also, of course, [00:29:17] I'm going to touch on the OEM bug that we saw. So we signed up with a gigantic deal. It's more than [00:29:25] 10,000 access points at 28 locations. And it's interesting because hospitals is one of those [00:29:32] situations. It's one of those verticals. I'll be honest and open. I was not ready for it because [00:29:40] of the sensitivity around network equipment. Now, I know that we're not touching network [00:29:47] devices in here, but in general, if you ever had any conversation with an IT director at a hospital, [00:29:54] you immediately understand how much more scrutiny and how much more risk aversion there is in that [00:30:00] vertical. So I wasn't ready for that yet. Instead, it's very great to see that that [00:30:05] technology stack has gotten so much more trust from IT directors to the point, and now they're [00:30:10] able to turn it on into hospital locations. But what we did, we turned them all on with them, [00:30:20] with a channel partner, which I think is Talus, and we covered 28 locations, over 10,000 [00:30:29] access points, and we published this book post saying that we were seeing an incredible amount [00:30:34] of traffic, about 145 terabytes of traffic. So let me get into that. That number is wrong. [00:30:40] And the reason why the number is wrong is because this was by far our first big venue [00:30:50] that uses Cisco Catalyst. Cisco Catalyst is an OEM, it's their own brand. And especially in a [00:30:57] location like the hospital, when you have multiple access points with a lot of people migrating from [00:31:04] one access point to another, a roaming between access point, we discovered there is an accounting [00:31:10] bug inside the Cisco catalyst. [00:31:13] And we discovered it now because this is the first big size Cisco deployment that we have [00:31:21] done. [00:31:22] And I also want to say I want to thank the technology team at Helium because actually [00:31:30] it was very tough. [00:31:31] reason why it's tough is because that bug presents itself in different forms depending on the [00:31:39] configuration and it can make it more or less impactful on the accounting error. So the way I [00:31:45] don't want to get into many details because I'm happy to maybe later, but essentially there is [00:31:51] some extra accounting records that get sent and it will greatly change depending on the configuration [00:31:57] or what kind of roaming or many of those roaming events happen between access points. [00:32:02] So the end result was that the number was wrong. [00:32:06] But to give you an idea, as we jumped on it, [00:32:11] as soon as we realized that that was actually wrong, it was very hard to spot. [00:32:15] It took some time to do it because, again, when you don't have consistency, [00:32:20] even for the same OEM across different deployments, it's very hard to actually do it. [00:32:26] So as of October 2nd, we actually stop rewards while service is still on to all Cisco catalyst [00:32:33] sites while we work with Cisco on a resolution. Cisco is already plugged into the bug. And the [00:32:41] reason, one thing that you're not seeing, but again, it's being captured by Joey Padden and the team [00:32:46] is that there is a lot in the industry that happened because of this bug, meaning there is [00:32:50] a lot of other deployments affected beyond Helium. And so there is a lot of focus from [00:32:57] Cisco on the bug. So that's why we are very, why we don't have an ETA on the fix right now, [00:33:02] we feel very comfortable with that Cisco will issue a bug fix soon. So I just want to say, [00:33:12] this is the reason behind that number. And, you know, we can spend a lot of time saying how good [00:33:19] the industry is going towards Wi-Fi, which I truly believe, you know, the standard, the Passpoint, [00:33:25] penetration in the phones that I shared at the beginning and the tier definition and all of that, [00:33:33] but there is still a lot. And this is one example of how much work there needs to be made on the [00:33:40] standardization front. And that's why we're spending our time and effort in the WBA and in those [00:33:48] forums, because there is still a lot of work that needs to be done for standardizing interfacings, [00:33:54] standardizing configuration. To be honest, this was a bug on a standard, meaning like there is a [00:34:00] standard for accounting and this was a bug implementation on the implementation of that [00:34:06] standard. But in general, that tells you that certification programs and things that need to be [00:34:11] spun up. I've been talking to the WB leads for a long time now about how we do need some sort of [00:34:17] certification programs, not just regarding a pass point per se, but around accounting, for example. [00:34:24] And so things will happen and will happen over time. [00:34:27] So this will be the last time we see this. [00:34:30] Probably not. [00:34:32] The commitment from us is that we [00:34:34] will do always better into catching this earlier [00:34:39] and as early as possible. [00:34:41] I think it was actually the fact that a team of literally [00:34:46] few people was able to, with effort, [00:34:49] to figure out there was something problematic [00:34:52] present this to a giant carrier like AT&T or other partners within the AT&T Wi-Fi roaming that have [00:34:59] not spot the bug in years because right now got an estimate from Cisco that that bug has been around [00:35:05] for three years. So it's a big kudos and tells you a much bleeding edge work we are doing on helium. [00:35:12] Of course I don't want to downsize the fact that there is a lot of impact and we're trying to [00:35:17] As we are trying to minimize that impact, we are doing the absolute best that we can for that. [00:35:23] On other news, and then I'll pass it over to Joey Hiller, you know, another case study yesterday [00:35:29] with the University of Alabama College Football Stadium. We had our first game through our partner [00:35:35] Cell Dwell, channel partner Cell Dwell. We have our first game on Saturday. It's a huge, huge effort [00:35:44] to be able to turn on a place like a stadium in for something like that because of the presence of a [00:35:49] of a DAS system in there and how much wi-fi traffic should and could be taken by the wi-fi [00:35:55] versus the DAS the work the channel partner needs to go need to do together with the venue to get [00:36:00] this turned on so more for this to come but i just wanted to give you an idea of the size of the [00:36:05] venues that we're getting into and and the complexity of turning those venues and how much [00:36:13] of the work that we are doing with WOX and with metrics and with qualifications on the venue, [00:36:19] both on the sales side as an inbound as well as the processing side, is helping, is helping [00:36:24] greatly moving those deals forward. All right, I'm going to pass it on to Hiller to give us an [00:36:31] update on the IoT side and then we'll go into AMA. Yeah, with any luck if I do my job right here, [00:36:43] this call will become 100% mobile focused. We do all sorts of cool stuff on that side of things. So [00:36:50] just a little bit of a recap here for anyone that may have missed it. But on September 2nd, [00:36:56] so roughly a month ago, we announced our plans for the IoT network, which is to find a new custodian [00:37:03] and innovator for the IoT network. So there's a lot of really cool things happening with the network, [00:37:10] but we need our focus on mobile and the IoT network needs its focus from a [00:37:17] qualified operator in that regard. So with that, I went and engaged basically the entire network [00:37:23] of folks that I have met over the last five plus years working on the IoT network and have been [00:37:31] met with some incredible reception to these queries. So I've got effectively a pipeline of, [00:37:38] well let's call it six now, I had one drop out, but highly qualified operators, these are sort [00:37:45] of brand names, people that are familiar within the community, etc, all incredibly qualified to [00:37:54] become the full custodian of the IoT network. I had a bunch of meetings with these folks in person [00:38:01] week and a half ago in Amsterdam for the Things Conference, so the timing of this conference [00:38:08] lined up really nicely to be able to go and engage these folks directly, given that they're all sort [00:38:12] of in one place. So I have been doing a lot of work on the back end. There's a full diligence [00:38:20] package. There's decks, you name it, in educating everyone from C-suite execs to understand what [00:38:27] the Helium IoT network is, to making sure that more teams that are further along in this process [00:38:35] access, have full access to the data that they need. [00:38:39] One of the nice fallouts, and I'll sort of skip ahead here, is that as I've built all [00:38:44] of these data pipelines to sort of help these candidates understand what it is that they [00:38:49] would be taking on, I've just gone and turned those into resources and tools for the community. [00:38:56] So for folks with IoT hotspots, take a look at World. [00:38:59] There's a bunch of cool new stuff in there that helps you understand what your hotspot [00:39:04] is up to. Of course, we always want to see hotspots staying online, continuing to serve [00:39:11] those use cases. There are a lot of use cases deployed on the network. And one of the cool [00:39:16] things is the usage map that we put on there to sort of help you see where those highest [00:39:20] demand areas are. And then I'll just close this out. I talk fast. I'm sorry. But the [00:39:30] The timeline that we're looking at here is to have effectively a letters of intent from [00:39:35] these candidates by mid this month. [00:39:39] So October 15th is the timeline that we've set for folks. [00:39:45] And at that point, we will evaluate those internally, make the best decisions that we [00:39:51] can on the future direction of the network, we'll lock in with one of those, make full [00:39:56] presentations and updates to the community so you understand all of the thought process [00:40:01] and what the future opportunity is. I can say from what I've seen from these early drafts that [00:40:08] they are thinking really strongly about reworking the economics of the IoT network in a way that [00:40:15] should make all of the deployers and operators very happy. So hold out for that. We'll have some more [00:40:22] updates coming and we'll keep you updated. I guess in another month I'll do a similar [00:40:28] update with some some very clear direction for where things are at. [00:40:32] Thank you so much, Joey. Thank you for driving this and hopefully this is clear enough for [00:40:39] in terms of intent and where we are where we are in the process. I would say let's go [00:40:47] with some Q&A now. I'm just going to post the AMA one more time. If you have questions, [00:40:54] pop them in here. I will say take a look through the posted questions already just in case there's [00:41:00] something that's someone's already asked what you're looking to ask. Yes, I'm gonna open, [00:41:11] shall we go, how do we usually do, Keenan, do most recent or we do from the top down? [00:41:19] There's, it depends however you like, there's a bit of a voting system. [00:41:22] Yeah, so let's go from the top down with the voting then. I think it's important that we [00:41:27] we assign importance for questions that people want to hear and I think we have enough time to [00:41:32] to go through all of them. [00:41:33] So, okay, so when T-Mobile does come back, [00:41:38] do we expect them to want indoor only [00:41:40] or was that an Ameriband decision? [00:41:46] Well, I like the optimism, of course. [00:41:48] I mean, I am optimistic too, to be clear. [00:41:50] It's just that I love the when. [00:41:53] Thank you for using that [00:41:55] because that's the right mindset. [00:41:57] I think that the indoor coverage [00:42:00] is really the key in many ways. [00:42:03] So I definitely expect that this will probably restart when and how it restarts. [00:42:11] It will be mostly focused on indoor and tier, higher tier venues. [00:42:17] The stance is very different on Wi-Fi as I wrote. [00:42:22] And I think there is an important part of showing value in tier one and tier venue for indoor [00:42:31] that is pretty clear. It's easy to understand and easy to get by in internally. Maybe also, [00:42:38] I'd love to hear from Woody because Woody has been also the one having a lot of these conversations. [00:42:43] Yeah, so I would say that outdoor coverage in a Tier 1 or Tier 2 venue is more likely to be [00:42:51] of interest to carriers than outdoor coverage in a Tier 3 location or just sort of ambient outdoor [00:42:58] coverage we may as we build trust with carriers we may find that they are willing to share [00:43:05] more explicitly with us which towers are overloaded right so the main value of outdoor coverage is [00:43:12] just simply in reducing tower load and we know that there are some towers in the united states [00:43:17] that simply are overloaded right because they've oversold fixed wireless or they just simply have [00:43:22] not been able to to build where they needed to and people have been moving around right but today [00:43:29] The core value proposition that we're able to bring to any of these carriers is not about [00:43:33] reducing tower load because that's like top secret and the carriers don't want to admit [00:43:37] that the towers are ever overloaded. Whereas it's easy for them to admit that physics prevents [00:43:43] macro coverage from penetrating into indoor spaces. So if you're out there thinking about [00:43:48] where to deploy, deploy indoor and deploy at the highest tier venue you have access to. [00:43:53] Thank you, Woody. So yeah, tier over type. I mean, a stadium is probably considered outdoor, [00:44:01] technically, right, if it's not covered. So still a tier. And so I can see how that would be of [00:44:06] interest for a carrier to do it. So does helium or Nova Labs hold any patents on pending patents [00:44:12] related to cellular-to-Wi-Fi offload? The carrier dashboard and helium world appear to [00:44:16] be unique, but utilizing the Passpoint technology is not. What's the market differentiator for helium? [00:44:22] So we do have some pending patents on some of the time, some of the [00:44:30] parts of the Wi-Fi Offload Experience gateway. And I think that's where the differentiator is, [00:44:36] is in the metrics part. Whoever wrote this question correctly, it is correct. The Passpoint [00:44:42] technology is not. The way you utilize it, it is. And I don't think it's just the dashboard. Of [00:44:49] course, to me, it's about the metrics, it's the quality, it's how the decision is made based on [00:44:57] that quality. So for all that aspect we do have we do have patent pending patents that we are [00:45:04] but we're being also very you know patents are important but also at the same time sometimes [00:45:11] they play different roles from an offensive to a defensive play depending on where you are in the [00:45:15] industry. Let me say differently the best outcome for a for a Nova Labs patent would be to get part [00:45:22] to be part of a standardization pool, which means being part of a pool of patents, they are part [00:45:30] of future standard, because that's where you get access essentially to potential royalties from [00:45:36] people implementing that standard. That's their main strategy from monetization for a lot of [00:45:43] years has been trying to get as many patents as possible as part of the patent pool for 3GPP, [00:45:49] which is the standardization for cellular. So yes, some of it, not all of it, the one that it [00:45:55] matters. Also, you have to be strategic about why and what part of that stack can be part of those [00:46:03] potential standard pools in the future. So what's the current status of carrier offload, [00:46:09] of the carrier offload tiers, are tier-based rates live and being paid to the deployers? If so, [00:46:14] how can operators confirm their location or site tiers and rates? If not, what is the expected implementation [00:46:18] date? So they are implemented. They are not right now paid because this is part of the negotiation [00:46:26] with carriers that they are ongoing. Like Woody said, we are expecting to have that [00:46:36] being live pretty soon in the next few months. Nobody can read the future though, especially [00:46:42] when it comes to big enterprise. One thing that I did write into the chat and I think we should [00:46:48] share with the communities the definition of tiers as we are agreed on with with a carrier. [00:46:55] It's in the chat right now. I want to be really clear about something. So there is sort of a [00:47:02] common definition of tiers that is shared across carriers, right? This is not a concept that we've [00:47:08] created here, but they are really subject to negotiation and the actual tier approval, [00:47:14] particularly for Tier One, it happens in a conversation with carriers. So if anyone has [00:47:19] worked through Tier One approval on this call, and I know that we've had a handful of deployers that [00:47:22] have, there are all sorts of questions that we need to answer. Is there a DAS that's present? [00:47:28] What's the quality of the backhaul? We'll need a bunch of details about the network, and it really [00:47:33] becomes a discussion about replacing DAS. So think of Tier One as replacing DAS with high quality of [00:47:40] service and something that will be much, much more than just is my venue a stadium? Therefore, [00:47:46] I should get the tier one rate. This will be like a business development process that you'll need [00:47:51] to engage in with Helium. Thank you, Woody. So yeah, while the definition is understood, [00:47:57] the implementation of that definition grossly depends on the venue. Meaning, [00:48:03] I'll give you like an extreme example. If you are able to get someone on a stadium, [00:48:10] there's a brand new DAS that reaches every seat and you can do speed tests from every seat [00:48:15] of 500 megabit per second, then it doesn't matter. There is a tier one and there is Wi-Fi [00:48:21] availability because the carriers just won't pay for that traffic. So the tier definition can be [00:48:28] shared. The actual implementation will be on a case-by-case basis in many cases. [00:48:32] Oh, with one exception, which is the expansion zones that they're live. Those are all considered [00:48:40] essentially Tier 2 by virtue of those Expansion Zones being asked to us to cover. [00:48:51] Hopefully that covered that question. [00:48:54] Of course that Tier 2 reward multiplier going live does not happen until some later stage, [00:49:04] not because it's there today, it immediately automatically qualifies for Tier 2, right Mario? [00:49:10] Yeah, correct. But still needs to be, yeah, that's correct, they qualify for Tier 2, [00:49:16] but it's still subject to the final renegotiation of our contract. [00:49:24] Any further activity in legislative realm and the ongoing debate with crypto regulation clarity, [00:49:32] any updates on the E911 interest? I mean, if Sarah is on the call, I would love her to take this one [00:49:41] because she's the one that she's the closest. Sarah, you want to jump on stage? I don't know [00:49:47] if you're like if you're in a place that you can take the call otherwise I can cover it. Yeah she's [00:49:57] asking to get on stage. He raised her hand. Yeah yeah she's coming. Here folks introduction. The [00:50:05] king of law is coming on stage. Everybody behave please I'm joking. So Sarah. Hello. I uh I'm trying [00:50:17] Okay, hello. So sorry, which we are looking at the question. Any further activity in the legislative realm and the ongoing debate with crypto regulation clarity? Any updates on the 9-1-1 interest? Okay, so clarity by all accounts is dead. That's okay. It's pretty rough. What happened is that people couldn't get over the ethics issue right or wrong, but that's what killed it. [00:50:50] We are focusing for our own purposes, right now I'm drafting comments to the SEC's Reg [00:50:59] Crypto, which is their proposed rulemaking that came out. Those comments are due October 20th. [00:51:05] Reg Crypto is not great. [00:51:07] I think there will be a lot of issues, a lot of commenters pointing out that it doesn't [00:51:12] actually solve the problem of determining who falls into the category of commodity versus [00:51:20] security when you're a token. That's still like a threshold determination and there's no guidance [00:51:26] on how to make that other than reverting back to the Howey test. And then it sets out a lot of [00:51:31] exemptions if you are security, like the startup exception and others. But the problem with all [00:51:36] those is that in order to take advantage of them, you have to admit that you're a security in the [00:51:41] first place, which we've always held the position that HNT is not. There's no language about DePIN [00:51:46] at all. So my comment is kind of all focusing on that. And frankly, I think it's kind of [00:51:53] a giant waste of time, but I have to do it because I can't let it slide that DePIN [00:51:57] not in there, because we've been fighting for the amendment. On the 911 stuff, we are [00:52:03] getting a lot of traction from first responders primarily who are really interested in what [00:52:10] the technology can offer for them in emergency situations. We are very close to launching [00:52:16] some pilots in some locations in municipal buildings, schools in Florida, who have some [00:52:24] on-the-ground tests and comparisons between Wi-Fi offload for first responders versus [00:52:31] DAS offload and kind of status quo offload. [00:52:36] Once we have that in hand, we're going to be able to shop those test results, the pilot [00:52:41] results out to decision makers in municipalities working with [00:52:46] Woody's team on that and our and our lobbying efforts to find [00:52:50] venues where we can start really showing off that technology, [00:52:54] but we're the bottleneck right now is getting those pilots [00:52:57] started. So that answers the question. [00:53:08] Thank you. Thank you, Sarah. This is great. Thank you for [00:53:11] joining us. I was actually getting back to the questions. [00:53:16] - Okay, I know there'll be a few minutes left. [00:53:18] I'll try to go through that, [00:53:20] but I don't know if we're gonna be able [00:53:21] to get through everything. [00:53:24] What is the marketing strategy for this product? [00:53:26] Are we reaching out to those who might need this project? [00:53:31] Yes, the marketing strategy, I mean, [00:53:34] definitely much more of a B2B sales progress. [00:53:40] The marketing strategy goes through both [00:53:42] proactive outreach through like media, [00:53:46] Mostly for medium presence as well as a little bit of social media and is specifically about linkedin for the enterprise b2b [00:53:53] some conference participation ad hoc within reason for smaller conferences you [00:53:59] You will hear me saying that all the time. I think that's where the real value is is smaller conferences [00:54:06] They are much cheaper to get to much more meaningful conversation like the the biggest one that we were on a couple weeks ago [00:54:12] we're still receiving inbounds. There were literally 45 people at that conference. [00:54:17] And we're going to the WBA, which is still considered a small conference into the Telco world. [00:54:23] So yeah, so a combination of media presence with a PR agency, as well as social targeting, [00:54:29] social and outbound. I have to say the inbound engine has been incredible. Like we're getting [00:54:36] very quality, a lot of quality inbounds from the HeliumOS page, which is a kudos to the marketing [00:54:42] team to Scott Siegel and team to really double down on our SEO and how the website is getting [00:54:49] better and better and capturing these. Of course, that is always better. And you'll see some very [00:54:54] good updates in the next couple of months in terms of mission and vision there. So stay tuned there. [00:54:59] I'm going to move on to the next. Mexico updates. Is there anything to report? Nothing on the [00:55:04] Movistar side. We're still in those expansion zone. As you know, Movistar is going through [00:55:09] through a transition in terms of ownership. [00:55:12] So there is a lot of things that are kind of frozen [00:55:14] in their organization as you might expect. [00:55:17] We are in active conversation and not just conversation. [00:55:20] We're acting lab trial and field trial [00:55:22] with a couple of more carriers in Mexico. [00:55:25] So I would say the update is steady on. [00:55:28] The good news about that is that [00:55:30] they're going extremely efficiently [00:55:32] in terms of load for the team, [00:55:35] those conversations with those carriers. [00:55:37] So nothing to report just yet. [00:55:40] Hopefully, soon enough, we'll be able to update the community. [00:55:45] The goal is to bring more carriers, [00:55:46] because the concentration of users of Movistar alone, [00:55:52] it's not enough. [00:55:53] It's not enough, I think, for Jumpstart, the flywheel [00:55:57] that we have in the US. [00:55:59] Also, if you're interested in deploying Mexico, [00:56:02] we are doing a revised version of the Mexico grant program [00:56:06] for people they are, they want to deploy in Mexico, [00:56:09] in those expansion zones. [00:56:10] So reach out to me or to Woody. [00:56:13] Again, it's a small program and we're doing more of an ad hoc [00:56:16] because again, we don't see a lot of participation yet, [00:56:20] given the fact that the Movistar alone, [00:56:24] concentration of users in the expansion zone, [00:56:27] it seems to be lagging for multiple reasons. [00:56:30] One of them is also that a lot of those people [00:56:32] have older phones and older phones needs to be [00:56:35] manually activated. [00:56:36] Movistar continues to push weekly text messages [00:56:41] for people they are connecting close to the expansion zone [00:56:44] to get them to do the manual activation [00:56:47] of the Passpoint profile. [00:56:49] The campaigns are going well in terms of read rate. [00:56:52] We have a read rate of 35 to 40% in many of those. [00:56:55] The installation profile, I think, is very slacking. [00:56:58] It's just the struggle of getting to a specific user base [00:57:03] there is a pretty old carrier bundle, I would say, [00:57:09] because they are Passpoint capable, [00:57:11] but they need to do it manually as opposed to like [00:57:13] in the US where everything is automatic and carrier bundle. [00:57:15] They also have carrier bundling in Mexico, [00:57:18] just that doesn't reach 100% of the population. [00:57:23] We are over time. [00:57:24] How do we wanna do this, Keenan? [00:57:26] - So the questions can roll over to the next community call. [00:57:34] Let me give you, let me tell you this. [00:57:36] I don't want to wait one month to answer those questions. [00:57:38] So here's what I'm going to do. [00:57:40] I'm going to jump because I do a hard stop [00:57:43] for another meeting. [00:57:45] Can we, I'm going to take these questions. [00:57:49] I'm going to answer all of them. [00:57:51] We're going to post it in general [00:57:52] and we're going to tag everybody, okay? [00:57:54] So I'm going to answer them in writing by today. [00:57:57] That is my commitment to you, okay? [00:58:00] Thank you so much everybody. [00:58:02] And thank you so much for joining. [00:58:04] you so much for helping. Thank you for the patience as we go through this. This is a long, [00:58:09] this is the marathon, so we're here to be the ones that make it up at the end of the marathon. So [00:58:14] thank you so much. I appreciate everyone coming. Just a quick note before we do close out. So like [00:58:20] Mario mentioned and is very kind for doing so, he's going to answer those questions. I'll have [00:58:24] them in the Discord in the general channel and we'll make sure that they're pinned and everyone [00:58:28] can see them. The next community call hasn't been selected yet, the date of that. I will pick that, [00:58:34] post it in the events page. You'll see it on X or Twitter as well as Reddit. So when we do pick [00:58:41] that date, please sign up and come to the next one. And that is it. This call is recorded. It [00:58:46] will be posted in general and pinned in general as well with a transcript and a AI summary shortly. [00:58:52] And yeah, thank you all for joining and we'll see you at the next one. Appreciate everyone coming.