# Do ASAs created in the group have consecutive IDs?

**URL:** <https://forum.algorand.co/t/do-asas-created-in-the-group-have-consecutive-ids/5764>\
**Category:** General\
**Tags:** asa, smart-contracts\
**Created:** [January 17, 2022, 3:22pm UTC](https://forum.algorand.co/t/do-asas-created-in-the-group-have-consecutive-ids/5764 "2022-01-17T15:22:44Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![plasmatech8](https://avatars.discourse-cdn.com/v4/letter/p/45deac/32.png) [@plasmatech8](https://forum.algorand.co/u/plasmatech8)\
**Post date:** [January 17, 2022, 3:22pm UTC](https://forum.algorand.co/t/do-asas-created-in-the-group-have-consecutive-ids/5764/1 "2022-01-17T15:22:44Z")

</div>

Since applications have a max of 64 slots for global storage, I was imagining how smart contracts can efficiently store multiple asset IDs for later reference in the application code.

Perhaps there is a better way to do this than storing the ID of every individual asset and using precious global storage space.

Is it possible send a transaction group of 15 asset config transactions and to store only the ID of the first asset in global storage? Is this behavior “guaranteed” and/or would it be considered bad practice? Or are there smarter ways to compact data?

---

_[View the full topic](https://forum.algorand.co/t/do-asas-created-in-the-group-have-consecutive-ids/5764)._