<p>Native tokens supplies are indeed unbounded integers. While the current implementation relies on GHC native Integers, the practical limit is much lower since it needs to fit in a transaction for which there's a maximum size of a few kilobytes.</p>

CC BY-SA 4.0
2021-08-23T17:38:35.793Z
"it needs to fit in a transaction" -- Depending on your minting policy, you could create tokens in multiple transactions. There is a max in a single transaction, but I don't know if there is a limit to he number of transactions that create that token.
Mitchell Turner
CC BY-SA 4.0
2021-08-24T10:59:38.117Z
That is correct, but, if you wanted to group those tokens into one UTXO, the output would need to fit in a transaction. Still, you're right, in a system doing some aggregation across the entire set, the number could be arbitrarily large.
KtorZ
CC BY-SA 4.0
2021-08-23T16:53:34.620Z
2021-08-23T16:53:34.620Z
KtorZ
<p>Is there a limit to the integer size representing a native token supply in  Plutus? Does it share the same limit as Haskell GHC's native <code>Integer</code> representation of ~16GB (if I am not wrong). Does Plutus also use the <a href="https://gmplib.org/manual/Nomenclature-and-Types#Nomenclature-and-Types" rel="noreferrer">GMP</a> library for token supply?</p>

<native-assets>
Is there a limit to the integer size representing a native token supply?
# Is there a limit to the integer size representing a native token supply?

(Asked by: username_0 on 2021-08-11)

Is there a limit to the integer size representing a native token supply in Plutus? Does it share the same limit as Haskell GHC's native `Integer` representation of ~16GB (if I am not wrong). Does Plutus also use the [GMP](https://gmplib.org/manual/Nomenclature-and-Types#Nomenclature-and-Types) library for token supply?

**Tags:** native-assets

---

## 1 answers

### Answer by username_1 on 2021-08-23. Score: 3 | Accepted answer

Native tokens supplies are indeed unbounded integers. While the current implementation relies on GHC native Integers, the practical limit is much lower since it needs to fit in a transaction for which there's a maximum size of a few kilobytes.

> **Comments:**
> **username_2**: "it needs to fit in a transaction" -- Depending on your minting policy, you could create tokens in multiple transactions. There is a max in a single transaction, but I don't know if there is a limit to he number of transactions that create that token.  
> **username_1**: That is correct, but, if you wanted to group those tokens into one UTXO, the output would need to fit in a transaction. Still, you're right, in a system doing some aggregation across the entire set, the number could be arbitrarily large.  

---

