A network can ship new code without attracting paying users, and a token can trade without capturing a meaningful share of a product’s value. Those distinctions matter more than short-term price targets. This edition reviews three comparatively under-followed infrastructure projects with different sources of demand: decentralized blockchain data access, sensor-derived mapping, and programmable infrastructure for connected devices.
Research reviewed on November 15, 2026 (Japan time). Release dates and published roadmap claims are identified separately from demonstrated adoption. Where up-to-date transaction volume, customer revenue, order-book depth, or final chain activation cannot be independently verified, no figure is asserted.
Three Projects at a Glance
Pocket Network (POKT): A supplier-and-gateway system for blockchain RPC requests. A newly published November release is a concrete engineering signal, but profitable customer demand and the economics of suppliers remain the harder test.
Hivemapper (HONEY): A decentralized mapping and sensor-work marketplace. Developers commission data collection or local processing through Work Orders; the question is whether recurring buyer purchases turn map coverage into economic demand.
IoTeX (IOTX): An EVM-compatible network positioned around connected devices and physical AI. Its recent Zanzibar upgrade preparations matter for protocol reliability, while commercially productive applications remain a separate requirement.
Why These Projects
These systems address real infrastructure problems rather than promising a new general-purpose chain for its own sake. Developers need dependable historical blockchain data; mapping companies need repeatedly refreshed observations; sensor and robotics applications need verifiable device events and predictable settlement. Each problem has established centralized competitors. Decentralization only adds value if it reduces supplier concentration, improves permissionless availability, or lets smaller operators compete without making the user experience worse.
The token tests also differ. POKT is consumed for data relays and rewards suppliers; HONEY is burned when buyers obtain Map Credits and can be re-minted in part to contributors; IOTX is used in the blockchain’s staking and transaction economy. None of those mechanisms, by itself, proves positive cash flow for holders. Fees can be tiny, incentives can outweigh commercial demand, and liquidity can evaporate exactly when investors need it.
Pocket Network (POKT)
What it does
Pocket Network’s Shannon architecture connects applications and gateways to independent suppliers that answer blockchain remote-procedure-call requests. A user of an application sees an endpoint, while routing, session accounting and proof settlement happen behind the scenes. The Foundation’s public API documentation describes keyless endpoints across supported networks. That is useful distribution, but free access alone is not evidence of recurring commercial revenue.
Recent development
The project’s primary GitHub release history records v0.1.37 on November 12, 2026. Its brief public release label should not be confused with proof that every operator has deployed it. The more detailed v0.1.36 release, published October 20, scheduled a consensus-breaking upgrade for October 27 at block 983,087 and required coordinated validator, supplier and gateway changes. It described faster processing of claim-heavy blocks and a service-cap mechanism shipped disabled pending governance pricing. Those are specific engineering improvements, not measured demand growth.
Potential
The opportunity is a neutral data-transport layer for application developers, indexers and AI agents that need information from multiple chains. If independent gateways offer predictable response quality at competitive cost, the protocol could make a specialized wholesale market out of demand currently served by a few centralized RPC vendors. The Foundation’s tokenomics documentation states that relays burn POKT while suppliers and other actors receive issuance, with a 97.5% re-mint ratio under the deflation mechanism. Protocol burn should be compared with total effective issuance and service pricing, not presented as a guaranteed return.
Risks and what to monitor
A consensus-breaking upgrade raises operational coordination risk: mismatched node and signing versions can interrupt relays or cost suppliers rewards. Watch completed deployment evidence, independently measured gateway reliability, paying relay demand, the concentration of supplier capacity and the actual value of burns. Pocket’s exchange documentation lists venues but dates its table to April 2026; current liquidity, spreads and withdrawal support must be checked at execution time. Those unverified market conditions are material rather than a footnote.
Hivemapper (HONEY)
What it does
Hivemapper uses participant-operated capture devices to provide fresh geospatial observations. Its market has evolved beyond a single centralized image product toward a network in which developers request specific locations and data-processing workloads. The network’s May 5, 2026 terms describe Work Orders, device-side computation, validation and data delivered to commissioning developers. A large mapped territory would not be enough if few businesses pay for refreshes.
Recent development
The Foundation’s HONEY protocol page publishes an explicitly dated on-chain supply snapshot from October 16, 2026; it must not be relabeled as today’s circulating supply. The same page records an important August change: Bee Maps made USDC the default reward in the Bee application and no longer supports HONEY rewards there. That does not mean the HONEY protocol was discontinued. It does mean the distinction between app-level incentives, contributor earnings and the protocol token has become more important to scrutinize.
Potential
The strongest commercial case is not a one-off global map but paid, frequent updates for navigation, traffic verification, autonomous systems and location-sensitive AI. Under the Foundation’s described burn-and-mint design, buyers obtain Map Credits through HONEY burns, with a portion potentially re-minted as consumption rewards. Developer spending could therefore create a usage-linked token flow. However, users may buy with fiat, the network intermediates conversion, and higher credit demand does not mechanically translate into higher token prices.
Risks and what to monitor
The network must keep imagery useful, respect personal privacy, detect fraudulent or low-quality submissions, and compete with established mapping datasets. Work Orders can also be uneven across locations, leaving hardware operators with uncertain earnings. Evaluate paid orders, repeat commercial customers, token burns arising from purchases, reward distribution, mapping freshness and the spread between traded volume and executable order-book depth. The Foundation’s network overview describes coverage, but coverage should not be used as a proxy for recognized revenue.
IoTeX (IOTX)
What it does
IoTeX provides blockchain settlement and verifiable coordination tools for connected machines, with a broader positioning around decentralized physical infrastructure and real-world AI. It is a separate technical proposition from Hivemapper: an underlying programmable chain and infrastructure stack rather than one specific map marketplace. IOTX is tied to chain transaction and staking activity, not a direct claim on the revenue of every device or application using IoTeX-adjacent tools.
Recent development
The project’s official iotex-core releases show v2.5.1 published October 4, 2026, described as a recommended maintenance update containing stability and validation fixes and the Zanzibar hard-fork changes from v2.5.0. Documentation placed the mainnet activation target at block 53,533,081, estimated for October 19. A separate Binance notice dated October 14 said transfers would be suspended for the planned upgrade while trading remained available. These sources establish a release and scheduled event; they do not independently establish the final activation time or post-upgrade uptime.
Potential
A reliable base chain can reduce friction for projects that need to attest sensor readings, distribute incentives or coordinate device identities. The Zanzibar changes include on-chain voter-reward distribution, according to the project’s operator guidance, giving governance participation another operational dimension. Commercial upside depends on useful deployed applications, active node operators and real settlement demand. Builders should compare total hardware, connectivity and verification costs with simpler centralized alternatives rather than relying on claims about a future machine economy.
Risks and what to monitor
IoTeX faces developer competition, cross-chain security exposure and possible gaps between application-level success and value captured by IOTX. Its earlier ioTube bridge incident, covered in its official security updates during 2026, is a reminder to separate the base chain’s condition from connected services. For the recent upgrade, seek independent post-activation block and validator evidence, software adoption by node operators, application fee activity and the state of bridge security and compensation commitments. Verify live exchange depth rather than extrapolating from a maintenance release.
What to Watch Next
For Pocket, the next useful checkpoints are confirmed v0.1.37 uptake, RPC quality under demand spikes, and an externally reproducible relay-to-burn trail. For Hivemapper, seek disclosed repeat buyers, paid Work Orders, HONEY burn receipts and evidence that contributor compensation is sustainable when incentive campaigns subside. For IoTeX, look for a documented Zanzibar post-activation review, independent validator behavior and real applications whose settlement requires IOTX.
The comparison should be normalized: recurring paying customers, usable service volume, operating reliability, token capture after rewards, and realistic market liquidity. Press releases, Github tags, coverage maps and network dashboards measure different things and should never be collapsed into one broad ‘adoption’ number.
Final Assessment
Pocket has the clearest recent code-release checkpoint; Hivemapper offers a legible customer-to-token consumption mechanism but a harder customer-revenue measurement problem; IoTeX has a verifiable upgrade package yet must demonstrate that physical-AI applications need its chain. Each has a plausible infrastructure use case, and each could disappoint even if its technology works.
The decisive evidence over coming months will be repeat, non-subsidized usage; transparent operational reliability; controlled token issuance or burn mechanics; and sufficient exchange liquidity for price discovery. None of the three can be assessed responsibly from release headlines alone. This assessment is technical and economic commentary, not a recommendation to buy, sell or hold any token.
