Helium Network on Solana Integration for IoT

Helium Network Integration on Solana

Helium is no longer just an IoT network with tokens. After migrating to Solana, the architecture changed radically: it's now a set of subDAOs with the Helium Program Library (HPL), not a separate L1. We've seen this disconnect when clients come with the task of "connecting devices to Helium": the documentation is outdated, code examples are written for the old blockchain, and the new HPL architecture requires understanding the Solana Account Model. Our integration experience helps avoid typical mistakes and accelerates deployment. We've been developing blockchain solutions for over 5 years, and Helium is one of the most frequent topics in IoT projects.

Architecture After Migration to Solana

Key HPL Programs

Helium operates through three main on-chain programs:

helium_entity_manager — manages hotspot NFTs (ENTITY). Every hotspot after migration is a compressed NFT (cNFT) per the Metaplex Bubblegum standard. This matters: Merkleized NFTs are not stored in regular token accounts — their state is proven via Merkle proof. Using cNFTs instead of regular NFTs reduces storage costs by 10x.

helium_sub_daos — manages subDAO economics (IoT, MOBILE, ENERGY). Rewards, epoch transitions, delegation — everything is here.

data_credits — manages Data Credits (DC). DC is burned when transmitting data. The burn rate is fixed: $0.00001 per 24 bytes of payload. DC cannot be transferred — only burned.

How Data Transmission Works

Device → Hotspot (LoRaWAN/5G) → Router/OUI → Data Credits burned → Payload delivered

OUI (Organizational Unique Identifier) — an on-chain entity you must register to route traffic. Registering an OUI costs 1,000,000 DC ($10) plus staking 0.5% of the total DC balance in the organization's account. If the task is only to send data from devices without your own OUI, there are community-operated Network Servers (Chirpstack-based), but you lose control over routing rules and data privacy.

How to Register an OUI and Configure Routing?

The OUI registration process involves several on-chain transactions: creating a Maker account, staking HNT, calling register_oui from the data_credits program. After that, you must configure the packet router to receive data from specific devices. Our team ensures correct routing rule setup and integration with your backend.

Integration: Practical Patterns

Working with Helium API and Oracles

After migration, Helium removed its own blockchain explorer and API. Data is available via:

• Solana RPC — directly, but you need to know program addresses and deserialize Anchor structures.
• Helium Foundation oracles — off-chain services for location/reward claims.
• @helium/helium-react-hooks and @helium/spl-utils — official libraries.

import { init } from '@helium/helium-entity-manager-sdk'
import { AnchorProvider } from '@coral-xyz/anchor'

async function getHotspotInfo(hotspotKey: PublicKey, provider: AnchorProvider) {
  const program = await init(provider)
  
  // Hotspot is compressedNFT, search via asset proof
  const hotspot = await program.account.hotspotV0.fetchNullable(hotspotKey)
  if (!hotspot) throw new Error('Hotspot not found or migrated to cNFT')
  
  return {
    location: hotspot.location?.toString(16), // H3 hex index
    elevation: hotspot.elevation,
    gain: hotspot.gain,
    isFullHotspot: hotspot.isFullHotspot,
  }
}

Onboarding a New Device

Adding a hotspot is a multi-step process with several on-chain transactions:

1. Create Maker account — device manufacturer gets Maker NFT, stakes HNT.
2. Issue hotspot — mint cNFT for the specific device via issue_entity.
3. Assert location — bind H3 geohash to the hotspot (costs DC).
4. Config hotspot — pass gain/elevation data.

Each step requires signatures from both the maker and the owner. This is a Helium design decision to prevent device spam.

Decentralized Network Server

If building your own Network Server (for enterprise IoT), the recommended stack:

• Chirpstack v4 — open-source LNS, supports Helium packet routing.
• Helium packet router — service for routing LoRa packets (Rust, open-source).
• gRPC endpoint — to receive uplink packets from the router.

# Chirpstack configuration for Helium backend
[network]
net_id="000024"  # Helium net_id

[[regions]]
name="EU868"
common_name="EU868"

[backend.basic_station]
bind="0.0.0.0:3001"

The packet router uses ED25519 keys for authentication — the same keys as the Solana keypair (Ed25519 curve), simplifying management.

Why Automate Data Credits Replenishment?

A critical production question: how to ensure uninterrupted operation when DC burns. Scenario: you have 1000 sensors, each sending data every 15 minutes → ~2.8M transactions/day → ~2.8M DC/day ≈ $28/day. Without automation, you risk stopping the network when the balance drops. We implement monitoring with a 20% threshold and auto-replenishment via burn-and-mint, saving up to 40% of time on manual management.

import { burnAndMint } from '@helium/data-credits-sdk'

async function ensureDCBalance(
  provider: AnchorProvider,
  targetDC: BN,
  currentDC: BN
) {
  if (currentDC.lt(targetDC.muln(0.2))) {  // less than 20% of target
    const hntToBurn = await estimateHNTForDC(targetDC.sub(currentDC))
    
    const tx = await burnAndMint({
      program: dcProgram,
      burnAmount: hntToBurn,
      recipient: oracleAccount,
    })
    
    await tx.rpc()
  }
}

The HNT→DC rate updates via Oracle Price every 6 hours. Do not use a hardcoded rate — that's a common mistake.

Testing and Devnet

Helium has a testnet on Solana devnet. However, there's a nuance: testnet hotspots do not earn real rewards and do not appear in the production explorer. For development, we use the following command to configure:

# Solana CLI with Helium devnet
solana config set --url https://solana-devnet.rpcpool.com
export HELIUM_NETWORK=devnet

# Get test tokens
helium-admin create-maker --name "TestMaker" --staking-amount 1000000

What's Included in the Integration

Typical integration timeline is 3 to 6 weeks depending on device count and Network Server requirements. Get a consultation for your project — we will assess the scope and propose an optimal solution. Certified specialists with over 10 successful integrations guarantee quality.

Source: official Helium Foundation documentation

Blockchain Infrastructure Deployment: Nodes, RPC, Indexing

Subgraph fell at 3:47 AM. By morning users saw outdated balances, transactions "hung" in the UI, support received 47 tickets in an hour. Cause: the handler in the subgraph failed on a transaction with a non-standard event log — and the entire index stopped. We have encountered such situations dozens of times. Our experience shows: blockchain infrastructure does not forgive gaps in observability. Guaranteeing uptime without multi-layered monitoring and fault-tolerant architecture is impossible. Over 8 years working with Ethereum, Polygon, and Solana, we have developed an approach that allows predictable deployment of infrastructure of any scale — from a single node to a multichain grid with dozens of subgraphs.

RPC Layer Architecture

Every dApp interaction with the blockchain goes through RPC — the JSON-RPC API provided by a node. Three options:

Managed providers — Alchemy, QuickNode, Infura, Ankr. Minimal operational costs, SLA, built-in monitoring. Limits: rate limits (Alchemy Free: 300 RU/sec), vendor lock, potential downtime during provider incidents. For most projects — the right choice at the start.

Self-owned nodes — full control, no rate limits, no third-party dependence. Cost: archive Ethereum node requires 2.5–3TB SSD, a strong server, and DevOps support. Sync from scratch on Ethereum via Geth/Nethermind — 3–7 days. Justified under high load or latency requirements.

Hybrid — self-owned node as primary, managed provider as fallback. Standard for protocols with high TVL. Proper load balancing can reduce costs by 20–30% compared to pure managed setup. Under high monthly request volume, hybrid saves significantly.

How to Set Up an RPC Layer Without a Single Point of Failure?

At least two providers, DNS round-robin with health check every 5 seconds, automatic fallback when latency >500 ms. In practice, this gives 99.99% availability during any provider failure. For protocols with high TVL, we recommend a custom HA-proxy (nginx or Envoy) in front of two managed providers.

Why Is a Hybrid RPC Scheme More Cost-Effective Than Pure Managed?

At high request volumes, managed providers can be very expensive; a hybrid using a self-owned node as primary and a managed fallback cuts costs significantly without losing SLA.

Ethereum Node Clients

Execution clients: Geth (most used), Nethermind (C#, fast sync), Besu (Java, enterprise), Erigon (fastest sync, efficient archive mode ~2TB instead of 3TB).

Consensus clients (post-Merge): Lighthouse (Rust), Prysm (Go), Teku (Java), Nimbus (Nim). Each node after The Merge requires a pair of execution + consensus clients.

For DevOps: eth-docker — Docker Compose configurations for all client combinations. Setting up monitoring via Grafana + Prometheus is mandatory; a standard dashboard is available in each client's repository.

The Graph: Event Indexing

The Graph Protocol — decentralized indexing. A subgraph describes which events from which contracts to index and how to transform them into a GraphQL schema.

Subgraph structure:

• subgraph.yaml — manifest: contract addresses, startBlock, events to handle
• schema.graphql — GraphQL schema of entities
• src/mapping.ts — AssemblyScript event handlers

dataSources:
  - kind: ethereum
    name: UniswapV3Pool
    network: mainnet
    source:
      address: "0x88e6A0c2dDD26FEEb64F039a2c41296FcB3f5640"
      abi: UniswapV3Pool
      startBlock: 12370624
    mapping:
      eventHandlers:
        - event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
          handler: handleSwap

AssemblyScript handlers — not TypeScript. No nullable types, no closures, no many standard APIs. An error in the handler stops the subgraph indexing on that transaction. Important: add try-catch for operations that can fail (e.g., store.get() for an entity that may not exist).

How to Avoid Subgraph Indexing Stops?

Graph Node logs are monitored in real-time; on hasIndexingErrors = true an alert fires and an automatic node restart (via systemd or Kubernetes). Typical downtime on error — 150–300 seconds to recover. Additionally, for production we set up a watchdog that restarts Graph Node if subgraph lag exceeds 50 blocks.

Choosing Between Hosted Service and Decentralized Network

Graph Hosted Service (free, centralized) is deprecated in favor of Subgraph Studio + Graph Network. For production: deploy on Graph Network with GRT curation signal — the subgraph gets indexers proportional to curation.

Alternatives to The Graph: Ponder (TypeScript, self-hosted, easier to debug), Envio (ultra-fast indexer, supports EVM + non-EVM), Subsquid (TypeScript, own network), Moralis Streams (managed, webhook-based). Our experience shows: for high-load projects with unique logic, Ponder or Envio are more effective — they give full control over the process and do not require GRT tokenomics.

Webhooks and Real-Time Notifications

Alchemy Webhooks and QuickNode Streams allow receiving events in real-time via HTTP webhook or WebSocket. For monitoring addresses, new transactions, mints — this is faster than polling RPC.

Tenderly — platform for monitoring and alerts. You can set up an alert for a specific contract event, balance change, function call with certain parameters. Transaction simulation via Tenderly API is invaluable for debugging.

Monitoring and Observability

Minimum monitoring stack for a protocol:

On-chain: OpenZeppelin Defender Sentinel — watches contract events, triggers webhook or Autotask when conditions are met. Forta Network — community-maintained bots detect anomalies (large withdrawals, flash loans, governance attacks).

Infrastructure: Grafana + Prometheus for nodes, Datadog or Grafana Cloud for managed metrics. Alerts on: node is 10+ blocks behind, RPC latency >500ms, subgraph lag >100 blocks.

Uptime: Better Uptime or PagerDuty on RPC endpoint and subgraph health endpoint (The Graph provides _meta { hasIndexingErrors, block { number } }).

Why Is Monitoring Without Tenderly Insufficient?

Tenderly provides transaction simulation and detailed traces — critical for debugging subgraph and smart contract errors. Forta focuses on network anomalies, not your infrastructure. The combination of Tenderly plus a custom Grafana dashboard covers 90% of incident scenarios.

Multichain Infrastructure

A protocol on 5 chains = 5 separate RPC endpoints, 5 subgraphs, 5 monitoring configs. Manageable but requires deployment automation.

For subgraph multi-network deployment: graph deploy --network mainnet, graph deploy --network arbitrum-one etc. with a unified codebase and network-specific addresses in separate config files.

Chainlink CCIP and LayerZero for cross-chain messaging require monitoring of both chains and transactions on intermediate relayers. A reorg on the source chain after a confirmed mint on the target chain is a classic bridge problem. Solution: wait for finality (on Ethereum ~15 minutes after Merge for economic finality) before confirming on the target chain.

Infrastructure Setup Process

1. Audit current stack — determine chains, request volume, latency and availability requirements.
2. Architecture design — select providers, load balancing, redundancy.
3. Subgraph development — manifest → schema → handlers → testing on local Graph Node → deploy to testnet → mainnet.
4. Monitoring configuration — Tenderly alerts, Grafana dashboard, PagerDuty integration.
5. Documentation and runbook — what to do when: subgraph falls behind, RPC downtime, node desync.
6. Handover to operations — team training, access transfer, first month support.

What's Included

• Deployment of managed or self-hosted Ethereum, Polygon, BNB Chain nodes
• RPC layer setup with primary/fallback and load balancing
• Subgraph development and deployment for your protocol
• Monitoring connection (Tenderly, Grafana, alerts)
• Runbook and operations documentation
• Team training (up to 4 hours online)
• 30-day support after delivery

Timeline

All projects are managed in a GitHub/GitLab repository with CI/CD; configuration code stays with you. Order infrastructure deployment — we'll show how to cut costs by 20–30% without losing reliability. Get a consultation — we'll demonstrate how we deployed infrastructure for a protocol with large TVL on Ethereum and Arbitrum. Contact us.