Like most blockchains, Helium has a system of transaction fees. All transactions in the Helium blockchain are paid in Data Credits (DCs). Data Credits are produced via burning some amount of
HNT using an on-chain transaction. And thanks to a system called "Implicit Burn", users (typically) don't need to manually supply
DCs to pay fees. As long as the Helium wallet being used to submit the transaction contains enough
HNT to burn to
DCs to fund the transaction, the burn will happen implicitly, requiring no user intervention.
The following is a list of the current set of fees required for various transactions, along with their details. Transaction fees are paid in Data Credits.
Required As Of
Transferring HNT from wallet to wallet
Transferring Device Packet Data
Fee paid by device owner when sending or receiving sensor data. Metered per 24 bytes.
Fee paid to add Gateway to the blockchain. (Only applies to non-Helium Hotspots.)
Assert Gateway Location
Required when asserting a Gateway's location. (The first location assertion for Helium Hotspots is paid by Helium Inc. )
Purchasing a blockchain OUI
Buy an OUI from the Helium blockchain
Purchasing a blockchain Subnet
Buy a Subnet from the Helium blockchain
As noted above, the
DC cost of a
Sendtransaction is variable. The precise cost is based on the size of the transaction, in bytes. Once the size calculated, we apply a
5000x multiplier. For a typical send transaction, where one wallet is sending to one wallet (like this one here), the complete transaction is made up of the following:
Component Size (Bytes)
Payer Wallet Key
Payee Wallet Key
3 (approximate; ranges from 2-4)
6 (approximate; ranges from 4-8)
In total, this is
24 bytes requires one Data Credit (as is the case when you're transferring device packet data).
24 results in
6 Data Credits.
We then apply our 5000x multiplier, and the result is a transaction fee
This results in a
30000 Data Credit cost for the above transaction.
The Helium blockchain uses something called
implicit burn when paying fees.
Thanks to Implicit Burn, if you have enough HNT to pay the transaction fee in your wallet, the Helium Mobile Wallet (or the Helium Wallet CLI) will calculate the DC cost of your transaction and the blockchain will automatically burn the precise amount of HNT to supply the required DCs for the transaction. For example:
You need to send
10 HNT from a Helium Wallet that contains
The cost for this
send transaction is
Let's assume the
HNT/$USD Oracle Price is
$.35 at the time you send the
HNT. This means that you'll need to supply a
1HNT to fund the
35000 DCs for this transaction.
When you send the
10 HNT, the Helium Wallet automatically supplies the
1 HNT to be burned into
After the transaction is submitted and processed, your resulting Helium Wallet balance will be
In the above example, had you attempted to send
10.0001HNT with only.
11 HNT in your wallet, this transaction would have failed as burning
.999 HNT would only result in
34965 DCs, a bit short of the
35000 required for a
Transactions in the Helium blockchain are
atomic. In short, this means that they either succeed entirely or they don't. So, if you attempt to send HNT from a Helium Wallet without enough HNT to supply the required Data Credits, the transaction will fail after being submitted to the blockchain API by your wallet. And your
HNT balance will be the same. No
DCs were burned (or harmed) in this failed transaction.