Event Notes - November 10, 2026

Mario Di Dio at DAS London: Carrier Growth and the HNT Value Question

How Helium's network and enterprise software fit together, why carriers are buying indoor capacity, and what remains unresolved for HNT holders.

SourceBlockworks X broadcast
Duration28m 35s
SpeakerMario Di Dio, Helium CEO
ModeratorMax Rennillo, Blockworks

Executive Summary

  • HNT's connection to enterprise value remains unresolved: Mario said the software products generate revenue and the team is exploring how token holders might participate in that value. He had nothing to announce: no revenue-sharing arrangement, equity entitlement, buyback, or implementation date.
  • The carrier pitch combines capacity and control: Helium supplies indoor connectivity without carriers building every part themselves. HeliumOS supplies visibility and control over the subscriber experience, helping carriers trust third-party Wi-Fi.
  • Mario reported almost two million daily users and shorter sales cycles: He described carrier discussions moving from roughly 18-24 months toward 9-12 months, supported by demand and the AT&T and Telefonica relationships. He disclosed no new signed contracts or revenue totals.
  • Indoor Wi-Fi complements cellular and satellite: Mario argued that rising mobile usage and constrained carrier capital favor existing venue networks, with stadiums, airports, casinos, and other dense locations central to the strategy.
  • Brazil combines strong demand with greater cost pressure: Mario expects broader adoption in the U.S., Mexico, and Brazil over the following six months. He linked Brazil's opportunity to lower carrier revenue per subscriber, but did not announce a new commercial launch.

What Happened

Mario Di Dio joined Max Rennillo, Blockworks' head of customer success, for Telecom's Capital Shift on the main stage of Digital Asset Summit London on November 10, 2026. The official agenda identifies the session and speakers. The conversation covered Helium's business model, carrier economics, software products, token-holder value, and international expansion.

The interview appears at approximately 03:15:10-03:43:45 in the Blockworks main-stage broadcast, including the introduction and closing remarks. The 28m 35s duration refers to this segment, not the full stream. Timestamps in these notes and the transcript refer to the original broadcast.

Mario outlined his telecom background, his arrival at Helium in 2022 to work on mobile strategy, and his move into the CEO role in 2026. The interview revisited the infrastructure focus discussed in his June 17 Blockworks fireside chat, now with HeliumOS in market and the token-versus-company-value question directly on the agenda.

HNT, Software Revenue, and Company Equity

At 03:34:27, Mario raised the possibility of connecting token holders more directly to enterprise value. He said the SaaS product suite is generating revenue and that the team is exploring ways for token holders to participate in the value being created on that side of the business. His qualification was explicit: "nothing to announce just yet."

Max pressed the underlying issue: Helium has a publicly held token, while the venture-backed company has equity shareholders. If the infrastructure and software businesses succeed, how does that success flow back to HNT, and how should token and equity ownership coexist?

Mario described the two as operating in parallel. The token supports the supply of network capacity; the company's software products provide the control layer. His argument was that they reinforce one another: selling HeliumOS tools can bring carriers and traffic to the network, while network usage supplies evidence that helps sell the tools.

That explains how the network and software can support each other, but does not establish a right for HNT holders to receive software revenue or company equity. Mario said potential ways to connect them are under discussion, subject to regulatory constraints including SEC rules. He did not disclose a structure, eligibility criteria, allocation, approval process, or delivery schedule.

This continues an unresolved discussion rather than introducing a completed solution. In the October 7 written Q&A, Mario addressed platform revenue and said there were no near-term plans for on-market HNT buybacks. The November 5 council report also separated deployer offload revenue from platform products supporting Nova's sustainability, while leaving the longer-term token-versus-equity relationship open.

Why Carriers Need Capacity and Control

Buying Capacity Instead of Owning Every Layer

From 03:17:31, Mario framed the carrier problem as a widening gap between mobile data demand and the capital available to serve it. He cited an Ericsson estimate of 22% more data usage in 2026 than in 2025 and four times as much by 2030, alongside roughly $200 billion in annual telecom capital spending that he described as declining. These were the industry estimates he used to explain the opportunity, not new Helium network measurements.

His proposed answer is a shift from capital expenditure to operating expenditure: carriers purchase usage on infrastructure supplied by others rather than owning and financing the entire stack. At 03:23:16 he compared this to the move from company-owned server rooms to cloud services.

Mario linked telecom consolidation and successive generations of cellular investment to pressure on that ownership model. In his view, Helium offers an additional source of capacity that can expand with demand without requiring the carrier to build every indoor network itself.

Reliable Offload Requires More Than Available Wi-Fi

Mario argued that capacity alone is insufficient. A carrier must know what experience its subscriber receives when moving from an outdoor cellular connection to indoor Wi-Fi, and it needs control over whether and how that connection happens.

He contrasted familiar guest Wi-Fi friction, including passwords and unpredictable quality, with automatic connections for participating carrier subscribers. AT&T in the U.S. and Telefonica in Mexico were his named existing partner examples. The software layer is meant to give carriers confidence in using coverage they do not own, rather than treating every reachable access point as equally suitable.

Indoor Wi-Fi and Satellite Serve Different Needs

At 03:19:57, Max asked where Helium fits alongside investment in satellite connectivity and SpaceX's wireless ambitions. Mario's response emphasized indoor service, citing an estimate that 80% of mobile traffic is consumed indoors. He presented Wi-Fi as complementary to outdoor cellular and direct-to-device satellite coverage.

Using a hotel as an illustration, Mario contrasted conventional indoor cellular infrastructure at around $6 per square foot with Wi-Fi at around $0.25 per square foot. These were illustrative deployment-cost comparisons, not universal installation quotes or a calculation of an individual hotspot's return.

His point was that venues often already have Wi-Fi. If a carrier can trust its quality and connect subscribers automatically, that existing infrastructure can supply useful indoor capacity. He expressed interest in serving both incumbent carriers and new entrants, but announced no SpaceX or Starlink agreement.

Helium's Three Business Phases

From 03:25:16, Mario described the company's evolution as three stages:

  1. Incentivize network supply: The original IoT model used token rewards to motivate people to deploy radios. He cited the historical scale of about one million hotspots as evidence that the incentive model could create distributed coverage. That figure was not a count of active mobile access points today.
  2. Create demand through a consumer carrier: Launching Helium Mobile brought customer acquisition, plans, and marketing into the business, with the aim of creating demand for the mobile network from within.
  3. Serve existing carriers with capacity and software: Rather than concentrating on building its own subscriber base, the business is packaging the network and tools for carriers that already have customers. Mario described paying carrier relationships in the U.S. and Mexico as evidence of this model, with Brazil part of the expansion effort.

This shift also changes the deployment focus. Mario described moving from smaller locations such as coffee shops and restaurants toward dense venues, naming Hudson Yards, Resorts World, Fontainebleau Las Vegas, BWI Airport, Bryant-Denny Stadium, and the MLB stadium in Arlington, Texas.

He reported almost two million people a day connecting to the network, often without knowing Helium is involved because their carrier handles the connection. That is a reported network-use figure, not a count of HNT holders, new customers acquired by Nova, or paid Helium Mobile subscriptions. Naming a venue also does not establish its carrier-tier classification or premium payout rate.

HeliumOS and the Carrier Sales Cycle

At 03:29:23, Mario identified HeliumOS as the product suite behind the control side of the strategy. It was launched on September 1, 2026, not at this event. The September community call covered that launch and the distinction between the software platform and the physical network.

Mario described the enterprise products as an onboarding path for carriers to use network capacity, with visibility into user experience and the ability to manage transitions between networks. He also highlighted chief network officer Joey Padden's work in standards bodies as part of the team's telecom expertise.

At 03:31:18, Mario said carrier sales cycles are getting shorter. He contrasted a typical 18-24 months with roughly 9-12 months in the work he is seeing, including Brazil and other U.S. carrier discussions. He attributed that change to the urgency of the capacity problem and the credibility supplied by the AT&T and Telefonica relationships.

Mario expects more proof points, adoption, and recognized revenue over the following six months. The shorter cycle describes his experience in ongoing discussions, not a guaranteed turnaround for every carrier. No contract values, software revenue totals, margins, or new named carrier agreements were disclosed.

Who Pays Whom When a Subscriber Connects?

At 03:32:39, Max asked how the economics work when someone uses a participating venue's Wi-Fi. Mario gave this high-level sequence:

  1. The subscriber connects automatically to the network, and the session is measured.
  2. Helium charges the subscriber's carrier for the traffic.
  3. The carrier settles with Helium, and Helium settles with the deployer providing the coverage.

For a venue, the appeal is both better connectivity and the ability to earn from infrastructure it already owns. Mario illustrated this with the conference hotel, explicitly conditioning the commercial example on an agreement with a local UK carrier. It was not confirmation of a live UK carrier partnership.

He described the token's role as incentivizing growth in network supply and said enterprises can interact through different arrangements, including stablecoin rewards in some cases. This was not a new universal payout policy for hotspot owners. The answer did not set out the complete HNT burn and reward mechanics, a new per-GB rate, or the split of revenue among the parties.

Brazil and the Next Six Months

Where Mario Expects Adoption to Grow

From 03:37:39, Max asked what the next DAS conversation might look like five or six months later. Mario expects broader carrier adoption in the U.S. and across multiple carriers in Mexico and Brazil. He described commercial conversations moving from whether the technology works toward its cost and how quickly it can be deployed.

Those comments describe his outlook, not signed commitments from every carrier in those markets. The November 5 call had placed Brazil at the field-trial stage with two of the country's three mobile network operators through Mambo WiFi. This interview did not announce that those trials had become commercial launches.

Why Select Emerging Markets Despite Limited Resources?

At 03:40:17, Mario acknowledged the execution tradeoff: a focused team has limited time and resources, so international expansion must be selective. He argued that some markets experience the need for lower-cost capacity more urgently than the U.S.

Brazil was his main example. He described strong mobile-data demand alongside carrier average revenue per user, or ARPU, at roughly one-fifth of U.S. levels. In his assessment, similar usage pressure with less revenue and more constrained access to capital makes the value proposition more urgent and brings discussions to senior decision-makers faster.

His anecdote about paying a beach vendor by phone illustrated widespread mobile use. His description of Brazil as about two years ahead of the U.S. referred to the urgency of the economic problem, not a technology lead or a deployment deadline.

Key Themes

  • Commercial usefulness is the organizing principle: Mario's pitch starts with carrier costs, indoor service, and subscriber experience, with crypto supporting the network underneath.
  • Software and network demand can reinforce each other without being the same asset: More software customers may bring network traffic, but that does not itself grant token holders a claim on company revenue or equity.
  • Venue quality matters alongside coverage: The strategy depends on making existing Wi-Fi usable and trustworthy for carriers, not simply counting deployed radios.
  • The next proof points are commercial: Carrier agreements, sustained paid traffic, recognized revenue, and a defined answer on token-holder value would make the strategy more measurable than adoption forecasts alone.

Open Questions

  • Will a concrete mechanism connect HNT holders to enterprise value? If so, what rights would it create, how would it be funded, and what regulatory or governance approvals would be needed?
  • How much revenue comes from software versus network traffic, and how does each activity benefit deployers, HNT holders, and company shareholders?
  • Which carrier discussions will become signed commercial agreements, with what coverage scope and launch dates?
  • Will Brazil's field trials convert to sustained paid usage, and what local economics will deployers receive?
  • How is the almost-two-million daily-user figure defined, and how does that usage translate into traffic, revenue, and HNT demand over time?
  • Can the reported shorter sales cycles be sustained while the team expands into larger venues and additional markets?

Sources

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