Key findings
- Installed, available and paid-for capacity are different sets.
- Token burns can include activities other than end-customer service consumption.
- Analyze recurring external demand separately from rewards paid to suppliers.
Network growth has two meanings
More devices can mean more potential supply, not proven demand. Suppliers may join for token incentives as well as future service fees. Installation growth during a reward-rich period cannot establish sustainable customer demand.
Keep supply and consumption accounts separate: uptime, resources actually used, billed activity and cash paid by external customers. Recycling rewards into network spending is economically different from independent customer purchases.
The measurement lesson in Helium Data Credits
Helium documentation describes Data Credits as a unit used for network fees, including data transfer and certain other actions such as Hotspot onboarding. HNT can be burned to create DC, but all DC activity is not end-customer communications consumption. [1]
Registration-driven burning and recurring service usage have different persistence. Classify the purpose and payer before interpreting aggregate burns. Token accounting and service accounting should connect without becoming interchangeable. [2]
| Stage | Established | Still unproven |
|---|---|---|
| Installed | Supplier participation | Paying customer demand |
| Available | Technical capacity | Actual use |
| Consumed | Resources used | Independent payer |
| Billed | Priced usage | Cash collection net of subsidies |
| Repurchased | Repeated demand | Persistence after rewards fall |
CBK analysis. This is an analytical framework, not observed customer performance or a market benchmark.
A supplier can survive on rewards
Suppose a device produces 30 units in monthly customer fees, costs 50 to operate and receives rewards worth 40. Total income of 70 can sustain participation, while service fees alone leave a 20-unit deficit. This identifies subsidy dependence; it does not prove the network will fail.
Subsidies can help bootstrap both sides. The question is which customers and assets remain when they decline. Separate revenue, rewards and costs by location, device type and customer before deciding where to expand.
| Item | Value |
|---|---|
| External service fees | 30 |
| Operating cost | −50 |
| Service contribution | −20 |
| Token rewards | +40 |
| Balance including rewards | +20 |
Unitless illustration; not a return estimate for Helium, peaq or actual hardware.
High uptime is not high demand
Availability can show reliability without showing paid consumption. A device needed only during particular hours may be valuable despite low average utilization. Match supply to where and when the resource is required.
If hypothetical region A uses a device for 100 hours and region B for 20, profitability remains unknown. Prices, energy and connectivity costs, repeat contracts and service levels can differ. Fix the service unit and cost-allocation rules before ranking locations.
| Supply | Demand | Economics |
|---|---|---|
| Installed and available time | Requested customer usage | Collected service fees |
| Serviceable locations | Locations of actual demand | Location-specific delivery costs |
| Token rewards | External customer repurchase | Contribution excluding rewards |
CBK analysis. This is an analytical framework, not observed customer performance or a market benchmark.
Find the buyer before recruiting hardware owners
A Korean corporate customer may want connectivity quality, reliable data and clear outage responsibility rather than token exposure. Specify why it would switch from an existing supplier: cost, quality or access.
Some networks must deploy supply before demand becomes observable. Even then, define the test location, duration and measurement method. Repeat usage and willingness to pay in one area can be more useful than a nationwide installation total. Network effects do not eliminate the need to measure.
Scope & limitations
Official charging mechanisms are analyzed; network revenue and device utilization were not independently measured. Numerical examples are hypothetical and do not value HNT or another token.
CryptoBridge Korea analysis based on public materials. Source facts are distinguished from interpretation and hypothetical calculations. References to organizations or projects do not imply their sponsorship or review of this paper.
Sources & scope
- Helium documentation, Data Credits ↗Fee structure includes non-transfer uses such as device onboarding.
- Helium documentation, HNT token ↗Reward and burn mechanics, not measured network revenue.