Event Notes - November 5, 2026

Helium Community Call: Brownfield Quality Metrics, Carrier Tiers, and IoT Transition

Quality metrics from Ubiquiti and Cisco Meraki venue networks, the return of Catalyst rewards, carrier negotiations, and the next steps toward an IoT operator agreement.

SourceDiscord call, presentation, and written updates
Duration64m 38s
ParticipantsNova Labs, Advisory Council, and community

Executive Summary

  • Quality metrics now extend to Ubiquiti and Cisco Meraki venues: Collection is live at the first supported brownfield sites, meaning existing venue Wi-Fi networks. WOX is using these newly available metrics for production connection decisions; this is an expansion of its inputs, not WOX's initial launch. Initial policies are conservative, deployer onboarding continues, and Aruba and Cisco Catalyst metrics integrations are next.
  • Cisco Catalyst rewards have resumed for applicable sites: Helium introduced its own accounting workaround on October 22 while waiting for Cisco's official fix. Offload service continued throughout the reward pause. This updates the unresolved issue from the October 7 call; it is not confirmation that Cisco's permanent fix has shipped.
  • The deployment opportunity is growing, but higher tier payments are still pending: Slides showed about 60,400 APs in unclosed opportunities and 41,300 in backlog, totaling 101,700. These are not 101,700 active APs. Carrier qualification requirements and commercial terms remain under negotiation, and Mario confirmed that no venue was being paid as Tier 1 yet.
  • IoT has multiple letters of intent and a November term-sheet target: Nova is negotiating operating plans, with a goal of finalizing a term sheet by the end of November so it can name the proposed operator. A detailed HIP would follow, explaining the effects on hotspot and device-network operators. Joey Hiller put Q1 2027 as the latest target for that HIP, not a completed handoff date.
  • The council supports Nova's direction but has not resolved token-versus-equity value: JB reported open access to relevant information and a positive assessment of cost control and supplement use. He emphasized offload revenue benefiting deployers while platform products support Nova's sustainability. The longer-term relationship between HNT value and company equity remains an active discussion, with no new mechanism announced.
  • Deployer visibility and international trials are progressing: World is being developed to show carrier-submission status and support re-review of rejected hotspots; the underlying data is already available, including through HeliumGeek. Brazil is moving toward field trials with two of its three MNOs through Mambo WiFi. Neither the World feature nor a new commercial carrier launch received a firm release date.

What Happened

The November 5 community call covered product releases, carrier negotiations, venue traffic, the IoT operator search, a council report, and community questions. Keenan hosted, with updates from Mario Di Dio, Joey Padden, Joey Hiller, Scott, Marc Nijdam, and council representative JB. Mario presented the offload and venue material prepared for Woody, who was traveling.

The discussion followed the September HeliumOS launch and IoT operator-search update and October's focus on onboarding, venue tiers, and the Catalyst accounting problem. This time, quality-metric collection had expanded to the first Ubiquiti and Cisco Meraki venues, with WOX acting on those metrics in production, while the IoT process had advanced to operating-plan negotiations. Converting those steps into commercial agreements and sustainable deployer earnings remained the central challenge.

Keenan reiterated the warning about impersonation scams and unsolicited wallet-support messages. Questions were collected through the community AMA page. The next monthly call did not yet have a confirmed date.

Brownfield Quality Metrics Expand WOX's Inputs

Ubiquiti and Cisco Meraki Are the First Supported Venue Platforms

Joey Padden announced that quality-metric collection is live on the first Ubiquiti and Cisco Meraki brownfield sites: existing venue Wi-Fi networks connected to Helium. In the October call, Helium hotspots were the supported metrics source and these brownfield integrations were still in development. The new support extends per-access-point quality visibility to those venue networks, rather than just reporting whether authentication succeeded.

The presentation illustrated a Ubiquiti deployment using read-only access through a private VPN to collect utilization, client counts, and link rates. Those measurements feed Helium's quality engine. It also described Ubiquiti test firmware that sends standards-track RADIUS metrics natively without a VPN, building on Helium's WBA and IETF contributions. That native path was a next step, not a claim that every installed AP already supports it.

Ubiquiti and Meraki deployers should expect outreach from sales engineering over the following weeks to months to enable collection. Aruba was next on the integration list, followed by Cisco Catalyst. The team expects measured quality to become part of the standard intake requirements for higher-value venue tiers.

WOX Acts on the Newly Available Brownfield Metrics

That week, WOX began using the newly integrated brownfield metrics for connection decisions in production. WOX predates this rollout; the update was its use of these additional metrics from supported venue networks. It checks sessions against policy in real time, using AP telemetry to allow a connection or steer a subscriber away from unsuitable Wi-Fi. Policies can be adjusted AP by AP, with decisions logged.

The rollout starts with conservative rules and thresholds so the team can observe network behavior, and Joey expected it to be largely transparent to deployers and subscribers. The example thresholds on the slide illustrated the decision flow; they were not announced as universal network limits.

The practical aim is to give carriers confidence that an offload session delivers a good experience. Venue and carrier demo interest, including international interest, was reported, but no additional WOX customer or revenue figure was announced on this call.

Cisco Catalyst: Rewards Return Through a Workaround

The October call documented inflated Catalyst usage reports and a rewards pause. Joey now reported that Helium deployed its own workaround on October 22, 2026, allowing rewards to resume for applicable sites while Cisco works on the underlying software fix.

The presentation gave this sequence:

  • September 28: Helium flags anomalous usage reports.
  • October 2: Rewards are paused and the community is notified.
  • October 5: A second operator confirms the problem is not limited to Helium.
  • October 8: Cisco confirms the root cause of the long-running accounting error.
  • October 22: Helium's workaround restores rewards for applicable sites. Offload service was never stopped.

The slides described the flaw as dating to 2016 and linked it to phones rotating their identity between sessions. That is the team's updated account of the bug's history, rather than the shorter estimate discussed in October. Mario reiterated in the Q&A that accounting is now corrected for the workaround-enabled deployments and that Cisco is under pressure from multiple operators to deliver a permanent fix.

No permanent-fix release date, corrected historical hospital traffic total, or policy for compensation during the pause was supplied. Restored rewards should not be read as retroactive validation of the withdrawn 145 TB hospital claim.

Carrier Tiers and the Deployment Pipeline

Mario described returning from another round of carrier negotiations, including work on the qualification criteria and intake forms needed for higher-value tiers. Some signed venues are waiting for the new rates before completing activation. Others still need to pass the higher-tier approval process.

No venue was being paid as Tier 1 at the time of the call. Asked about the casino featured in a recent article, Mario said those contracts still need to be finalized. He also argued that activating premium venues at ordinary rates before negotiating their value could weaken Helium's leverage. Some backlog therefore reflects commercial sequencing as well as technical onboarding.

The HIP 150 framework permits multipliers, but does not make an estimated venue category an approved premium payout. The HIP 150 FAQ explains the mechanics; the October call records the draft venue definitions and carrier-approval requirements. This call did not announce final tier rates or a launch date.

What the 101,700 AP Figure Includes

Access Points in the November Presentation
CategoryAPs, approximatelyMeaning
Open pipeline60,400Network-expansion opportunities not yet closed; AP counts estimated per venue.
Backlog41,300Partner networks onboarded but below 10 MB of AT&T traffic in the 30 days to November 4; partner-reported AP counts.
Combined101,700Open pipeline plus backlog, not active traffic-carrying APs.

The slide estimated tiers from venue type, treating hospitals as Tier 2. Its rounded breakdown placed 57,500 open-pipeline APs in Tier 2, 2,600 in Tier 1, and 200 in Tier 3. Backlog comprised 24,500 Tier 3 APs, 10,200 Tier 2, 200 Tier 1, and 6,400 unclassified. Rounded category figures need not add exactly to the rounded headline total. These classifications are pipeline estimates, not proof of carrier approval.

Carrier Approvals Versus Hotspots Unplugged

A separate chart reported 44,000 partner APs enabled for AT&T from January through September, compared with 8,100 Helium hotspots unplugged. September alone accounted for about 20,500 partner APs enabled and 700 hotspots unplugged. October figures were not final and were omitted.

The two series measure different things: partner-reported APs by carrier-approval month, versus U.S. and Puerto Rico Helium hotspots whose last heartbeat fell in that month, using a 14-day aging rule. They should not be subtracted and presented as a precise net increase in active network coverage. Approval also does not establish how much traffic an AP carries.

Asked whether carriers were frustrated by slow expansion-zone deployment, Mario estimated that Helium had filled about 1.2% of the requested locations and said it was progressing faster than other roaming partners. He wanted faster coverage but did not see the pace damaging the relationship. These were his assessments, without a published comparative dataset on the call.

Venue Traffic and Coverage Examples

Bryant-Denny Stadium

The Alabama stadium spotlight reported 16.8 TB of carrier traffic since September 22, 7,051 users on the peak day, September 26, and 6.75 TB in its biggest week, the week of October 5. These are separate cumulative, daily-user, and weekly-traffic measures.

Mario described the stadium as a place where Wi-Fi can complement an existing distributed antenna system, with quality metrics and WOX helping calibrate that role. He reported interest from more than the carriers already active on Helium, without announcing a new agreement. The official stadium case study and October event notes provide the deployment background.

Corelogix and Municipal Coverage

The Corelogix presentation covered indoor playgrounds, restaurants, and event spaces across five states, anchored by eight Hyper Kidz locations. It reported 3.76 TB over 30 days, with Main Street Ballroom in Ellicott City, Maryland, the top venue at 662 GB over 30 days.

Mario connected that example to municipal connectivity, describing existing work in several communities and exploratory discussions around Boulder and Longmont. Helium's Ellicott City article explains Corelogix's plan to extend connectivity along Main Street from a small number of internet-connected buildings. The district-wide plan is distinct from traffic already measured at individual venues.

Wakefern Grocery Stores

The first Wakefern grocery stores are live through SignaConnect, carrying carrier traffic over existing store Wi-Fi without new hardware. Mario framed retail as a market where carrier-funded Wi-Fi can address indoor coverage when a DAS upgrade is difficult to fund. The Wakefern case study gives further background. No chain-wide rollout completion or premium tier payment was announced.

IoT: Multiple Offers, a Term Sheet, Then a HIP

The September operator search and October 15 letter-of-intent deadline have progressed to detailed discussions. Joey Hiller confirmed that Nova received multiple letters of intent describing how prospective operators would run the IoT network. Names remain confidential while technical and commercial plans are evaluated.

The goal is to finalize a term sheet by the end of November 2026, allowing the proposed operator to be identified publicly. Mario clarified that this is the immediate milestone. It is not a promise that the network transfer will be complete in November.

A detailed HIP would then describe the operating plan and its effects on hotspot owners, device operators, and network operators. Joey said he should have that HIP no later than Q1 2027, while hoping to move faster. He expressed confidence in the November target but acknowledged that negotiations and contract revisions could change the schedule.

Joey characterized the candidate models positively, but the call did not disclose a selected operator, final economics, a reward increase, restored PoC, or completed transition arrangements. Those details need to be assessed when the proposal is public. For the distinction between today's rewards and future stewardship, see the IoT and HIP 149 FAQ.

Joey's Same-Day Discord Follow-Up

In #iot-general on November 5 at 18:09 UTC / 1:09 PM ET, Joey confirmed the multiple letters of intent and said a HIP would be authored once plans become concrete. Input from LoRaWAN network-server (LNS) operators will inform the proposal that comes to a vote.

Diligence work has also produced public improvements in Helium World's IoT view: hotspot RF models, data-traffic breakdowns, and usage maps. Joey reported onboarding three new OUIs that week. That is evidence of ongoing operator activity, not a count of three candidates to take over the network.

Council Report: Funding, Deployer Revenue, and HNT

Mario committed to reserving a regular council slot in monthly calls, alongside high-level agenda updates in Discord. JB, who described himself as a previously critical community voice, reported that Nova had been forthcoming with information relevant to the council's mandate. He said the council had not needed to invoke formal information-demand procedures.

JB gave a positive assessment of Nova's cost control and its use of the HIP 149 supplement to balance financial stability with growth opportunities in the U.S. and abroad. He did not report a major new council action or disclose spending totals, runway, or audited financial statements.

On the distinction between platform and offload revenue, JB said the council's intent is for offload revenue to benefit deployers, with Nova actively negotiating for better rates. Platform tools such as WOX are intended to support Nova's longer-term sustainability. This was a statement of direction, not a new reward formula or a commitment to distribute every dollar of platform revenue to HNT holders.

The token-versus-equity question remains unresolved. JB said people are working on the longer-term relationship, but no solution had been agreed. No equity conversion, buyback, or new token-holder revenue entitlement was announced. The July council town hall and August follow-up explain the oversight remit, while the October written Q&A covers Mario's earlier answers on platform revenue and buybacks.

Community Questions

How Can a Deployer Tell Whether a Site Is Stuck in Carrier Approval?

The question asked for queue status, typical timelines after demand sampling, and early warnings about problems before a site goes to AT&T. Joey Hiller said the underlying data problem has been solved and that World work is underway to expose the submission phase for hotspots, with deeper details in the owner's dashboard and a way to request re-review after rejection.

The feature had appeared intermittently in beta but was not available there at the time of the call. No production launch date or standard carrier-approval turnaround was supplied. Joey also noted that HeliumGeek had begun consuming the available data as another interface for deployers.

Mario distinguished Tier 3's demand-sampling and queue process from the additional venue requirements being negotiated for Tiers 1 and 2. The longer-term plan is to bring more of the carrier-submission process into HeliumOS, reducing spreadsheet and CSV handoffs.

November 14 follow-up: Keenan's quality-of-service announcement introduced Offload Status in Helium World and described the original plan to end Demand Sampling, set backhaul minimums, and require location trust for offload activation on Helium Mobile Hotspots. It did not give a launch date for re-review requests or guarantee approval times.

November 16 update: Nova CTO Marc Nijdam clarified that only the new speed-test thresholds are on hold. Hotspots with a location trust score below 1 are being removed from carrier offload, and hotspots not sending heartbeats will lose offload. See the November offload FAQ for what is still in effect and what to check in HeliumGeek.

November 17 update: Marc's revised speed-test plan replaces the pause with separate requirements for new and active hotspots. New hotspots need 100 Mbps download, 10 Mbps upload, and latency of 50 ms or less for carrier submission. Active hotspot floors increase on December 1, January 1, and March 1. The staged approach gives deployers time to improve backhaul after community feedback while moving toward carrier-grade quality. The offload FAQ has the full dated schedule; location trust and heartbeat requirements remain in effect.

Does SpaceX's Wireless Strategy Threaten Helium?

Asked about SpaceX and Qualcomm, Mario argued that indoor connectivity remains a different problem from extending satellite coverage. He emphasized the capital required to build a mobile network, the difficulty of attracting subscribers, and Helium's potential role in providing indoor capacity to any carrier, including a future satellite-led entrant. These were strategic views, not an announced SpaceX partnership.

Helium's October article on satellite coverage and indoor capacity provides the background to that argument. After the call, Mario shared an X post reporting a Deutsche Telekom CEO estimate of at least $200 billion to enter wireless, in #general at 18:14 UTC / 1:14 PM ET. That was a third-party cost estimate he shared, not a Helium forecast or a disclosed SpaceX budget.

How Is Nova Responding to Security Risks?

Marc Nijdam described regular internal reviews, on-chain program updates, hotspot firmware monitoring, and fixes for reported vulnerabilities. He said a couple of reported exploits had been addressed before use during the preceding month or so.

Marc also described an initial contract sweep associated with the Solana Incident Response Network and a STRIDE assessment covering security practices around contracts and oracle operations. He explicitly qualified the exact participation status. This was an update on work in progress, not a completed audit or a guarantee that no vulnerabilities remain. Solana's overview of STRIDE and SIRN explains the two programs.

Why Not Prioritize a One-Click Helium Switch in Every AP?

Mario put native quality metrics ahead of a one-click enrollment toggle in discussions with manufacturers. His reasoning was that metrics can unlock carrier confidence and tier economics, whereas the team can already configure some enterprise networks in about 15 minutes with their IT staff. That setup example does not mean carrier approval or full commercial activation takes 15 minutes.

What Is Happening with T-Mobile and Brazil?

On a possible T-Mobile partnership, Mario described carrier conversations at different proof-of-concept stages and said a future arrangement could emphasize Tier 1 and Tier 2 venues rather than broad access. No new contract or return date was announced. The August offload-removal notes explain why a replacement arrangement matters.

In Brazil, Nova is activating field trials through Mambo WiFi with two of the country's three MNOs, across roughly seven Mambo sites. One integration uses the Helium Wi-Fi Toolkit SDK in the operator's app; the other uses a carrier bundle and takes longer. Mario framed this as progress through a long telecom sales cycle, not a nationwide commercial launch. The September call had outlined the planned Q4 field trials.

Will Outdated Token Information Be Corrected?

A question highlighted stale post-HIP-149 supply information and outdated Mobile and IoT descriptions on CoinMarketCap and CoinGecko. Mario took an action to follow up with Scott, noting that the team had already contacted the services. He also acknowledged community feedback that had led to suggested corrections to Blockworks reporting. The call did not establish that the listings had been corrected or set a completion date.

Research, Industry Outreach, and Recognition

Joey highlighted Helium's public DAS versus Passpoint report as a tool for discussions with venue owners. The presentation quoted 98% of U.S. phones in use as ready for data over Wi-Fi, 88% ready for voice, and an 81% spectrum match for a typical legacy DAS. These are modeled compatibility measures, not measured throughput or the percentage of people who have service. The report distinguishes spectrum match from basic connectivity: it estimates that a typical legacy DAS still serves 99% of phones, and that Passpoint capability does not prove a venue has enabled it.

Mario's account of the WBA Wireless Global Congress in Vienna emphasized reliability and quality of service rather than speed alone. He reported useful U.S. and international carrier leads, without naming new customers. Scott outlined the planned Digital Asset Summit appearance in London, including a fireside conversation between Mario and Blockworks' Max Rennillo. Mario framed that outreach around long-term infrastructure financing rather than near-term token-market promotion.

The slides also reported two Fierce Network Innovation Awards finalist positions: WOX Gateway in Network Testing, Assurance & Observability, and HeliumOS in Telecom Cloud & Edge Infrastructure. Winners were scheduled to be announced November 19 at Broadband Nation Expo. These were finalist announcements, not awards already won.

Key Themes

  • Measured quality is becoming a commercial requirement: Telemetry and WOX connect the technical product to carrier trust and higher-value deployment negotiations.
  • Pipeline, approval, traffic, and payout are separate milestones: Large AP totals and recognizable venues do not establish active use or premium rewards.
  • IoT continuity depends on a public operating plan: Multiple offers are progress, but hotspot and device operators still need a named partner, economics, and a proposal they can evaluate.
  • Oversight and value distribution are different questions: A positive council assessment of Nova's operations does not settle how value should accrue between deployers, HNT holders, and company equity.

Open Questions and Follow-Ups

  • Will the IoT term sheet be finalized in November, when will the proposed operator be named, and what will the HIP specify about continuity, funding, governance, and rewards?
  • When will carrier-tier agreements be signed, what will the final qualifications and rates be, and how will deployers verify approval?
  • How much of the 60,400-AP open pipeline and 41,300-AP backlog will convert to sustained carrier traffic?
  • When will Cisco's permanent fix arrive, and will historical traffic corrections or compensation for the rewards pause be published?
  • When will the remaining metrics integrations and native Ubiquiti support reach deployers, and what performance results will WOX's use of brownfield metrics show?
  • When will World's submission-status and re-review features launch, and will they include reliable approval-time estimates? November 14 follow-up: Offload Status has since been announced; re-review availability and guaranteed decision times remain unconfirmed in that announcement. See the November offload FAQ.
  • What proposal, if any, will address the unresolved token-versus-equity relationship, and what financial detail can the council make public?
  • Will Brazil's field trials and other carrier discussions produce commercial agreements, and on what deployment scope?
  • What security assessment results can be shared, and when will the outdated third-party token descriptions be corrected?

Sources

These notes and the transcript were prepared with AI assistance. Sources are listed for verification.